From nobody Fri Dec 17 01:36:13 2021 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B8D3818E7301 for ; Fri, 17 Dec 2021 01:36:10 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JFWls6YYbz3rBw for ; Fri, 17 Dec 2021 01:36:09 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 1BH1aEC5005097 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 16 Dec 2021 17:36:14 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 1BH1aDDP005096 for freebsd-arm@freebsd.org; Thu, 16 Dec 2021 17:36:13 -0800 (PST) (envelope-from fbsd) Date: Thu, 16 Dec 2021 17:36:13 -0800 From: bob prohaska To: Mark Millard via freebsd-arm Subject: Re: Saving environment variables in u-boot Message-ID: <20211217013613.GA4452@www.zefox.net> References: <20211216180704.GA4173@www.zefox.net> <214132DD-A095-4349-BB81-B79CB8CF6B0C@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <214132DD-A095-4349-BB81-B79CB8CF6B0C@yahoo.com> X-Rspamd-Queue-Id: 4JFWls6YYbz3rBw X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-1.09 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.991]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-ThisMailContainsUnwantedMimeParts: N On Thu, Dec 16, 2021 at 11:12:01AM -0800, Mark Millard via freebsd-arm wrote: > > > On 2021-Dec-16, at 10:07, bob prohaska wrote: > > > U-Boot> saveenv > > Saving Environment to FAT... Failed (1) > > I expect that is based on there being a microsd card with > a FAT file system on it, possibly containing the u-boot that > is in use. I doubt that it supports saving to a FAT on USB > media. Do you have an appropriate microsd card in place? > Yes, the microSD contains a dd of FreeBSD-13.0-RELEASE-arm64-aarch64-RPI.img The DOS partition is writeable, AFAIK. > But that was for the u-boot-rpi4 or u-boot-rpi-arm64 ports. > (They also later mentioned using "usb_pgood_delay=2000\0" > instead, a figure they found in a bunch of configrations.) > The Pi3 in question is capable of booting from solid-state USB storage without any microSD card, but fails to detect a mechanical disk. Which is the appropriate u-boot-rpi3 port to tamper with? I tried sysutils/u-boot-rpi3 as an upgrade but that simply froze. The u-boot from FreeBSD-13.0-RELEASE-arm64-aarch64-RPI.img finds the USB mechanical disk, but erratically. > So something somewhat analogous might help if you are willing > to build and use your own u-boot port variant. Obviously, that's a fraught enterprise at my skill level.... I'm still somewhat hazy on the actual boot sequence when chaining from microSD to USB. Indeed, it's unclear how or if u-boot plays a role in starting RasPiOS. The term u-boot isn't found on the Raspberry Pi doc website, and the Pi isn't mentioned in the Denx manuals. Those discoveries surprised me. Thanks for replying! bob prohaska