Date: Sun, 22 Mar 2020 10:42:57 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: Re: Upgrading u-boot on an rpi3 Message-ID: <20200322174257.GA84906@www.zefox.net> In-Reply-To: <20200319001353.GA70624@www.zefox.net> References: <20200318054243.GA67865@www.zefox.net> <4B4CF1DF-F3C0-4ED3-AAC0-4FC0A8182787@yahoo.com> <20200318172339.GB67865@www.zefox.net> <456B1ED8-B335-405B-AB7B-B65968631323@yahoo.com> <20200319001353.GA70624@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I'd lke to make some "notes to self" for upgrading u-boot on a self-hosted rpi3. Here's what I think got done: Build and install the u-boot-rpi3 port using -DBATCH. Copy the resulting /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin to /boot/msdos/u-boot.bin Following buildworld/installworld copy and rename /boot/loader.efi to /boot/msdos/EFI/BOOT/bootaa64.efi Have I overlooked anything important? As an aside, the Pi3 is now at r359195 and seems to work normally. It does seem to become unresponsive for long periods during svnlite up or any process involving storage I/O despite top reporting ~98% idle. However, it hasn't crashed yet. Thanks for reading, and any comments! bob prohaska On Wed, Mar 18, 2020 at 05:13:53PM -0700, bob prohaska wrote: > On Wed, Mar 18, 2020 at 11:02:43AM -0700, Mark Millard wrote: > > > > > > On 2020-Mar-18, at 10:23, bob prohaska <fbsd at www.zefox.net> wrote: > > > > > On Tue, Mar 17, 2020 at 11:42:09PM -0700, Mark Millard wrote: > > >> > > >> > > > > >> > > >> Those last 2 lines above indicate that it found > > >> your microsd card media and its bootaa64.efi just > > >> fine. > > >> > > >> How old is this file? > > > > > > Rather ancient: > > > > > > -rwxr-xr-x 1 root wheel 637000 Oct 10 2018 /boot/msdos/EFI/BOOT/bootaa64.efi > > > > > > I have a newer version on a 12.x snapshot: > > > -rwxr-xr-x 1 root wheel 609960 Nov 1 02:29 /mnt/EFI/BOOT/bootaa64.efi > > > Is it prudent to simply substitute the newer version for the older? > > > > You may want to extract a more modern one from a snapshot > > if that does not work. > > > > Turns out that the version of bootaa64.efi from the 12.x snapshot did > the trick. > > > >> Have you been updating > > >> it via copying /boot/loader.efi to it as > /boot/loader.efi is updated? > > > Not following here. Loader.efi appears to be a file and seems to update > > > during normal build/install cycles. It's unclear where bootaa64.efi comes > > > from; there's only one copy in the filesystem after repeated OS update cycles. > > > > For the ARM boards involved, efi/boot/bootaa64.efi is a > > copy of /boot/loader.efi . The loader copy used in booting > > is placed on the msdosfs, not on ufs/zfs. > > > > Ahh, now bells are ringing. IIRC there were some messages issued > to this effect during either make or make install for u-boot-rpi3, > at least formerly. > > > > > Example from the RPi4 context: > > > > # file /boot/loader.efi > > /boot/loader.efi: MS-DOS executable PE32+ executable (EFI application) Aarch64, for MS Windows > > > > # file /boot/efi/EFI/BOOT/bootaa64.efi > > /boot/efi/EFI/BOOT/bootaa64.efi: MS-DOS executable PE32+ executable (EFI application) Aarch64, for MS Windows > > > > Thank you very much! > > bob prohaska > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200322174257.GA84906>