Date: Sun, 30 May 2021 16:25:23 -0700 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: William Carson <freebsd@dsllsn.net> Cc: freebsd-arm@freebsd.org Subject: Re: Boot from USB on RPi4 8GB? Message-ID: <D578DD89-6973-44C5-AACA-0D280AE0CD13@yahoo.com> In-Reply-To: <2F58272B-BD9C-464B-9A98-BF638971BA86@dsllsn.net> References: <4F3EE8D2-649B-4522-AD5A-7C308291802F@dsllsn.net> <43FAEEAC-EE36-4810-88AA-FF82AFBCC128@yahoo.com> <2F58272B-BD9C-464B-9A98-BF638971BA86@dsllsn.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-May-30, at 10:59, William Carson via freebsd-arm <freebsd-arm at = freebsd.org> wrote: > T. . . >>=20 >>> If I dd Raspberry Pi OS (2021-05-07-raspios-buster-armhf-lite.img) = to the same disk, it boots up no problem. I'm thinking this is a = U-Boot/rpi-firmware problem, but I don't really know where to begin. >> . . . >=20 This does not involve a U-Boot at all --and also is an armv7 boot, instead of an aarch64 boot. It may also be that this manages to use less power on the SSD during booting than a Firmware -> U-Boot -> FreeBSD-Loader -> FreeBSD-Kernel+World would. RaspiOS and RaspiOS64 boot a kernel*.img directly from the firmware, without using U-Boot. We already know that the firmware was working to find, load, and start U-Boot. So this boot does not tell us much new about the boot sequence that is used for FreeBSD (U-Boot and later stages). The issue seems to be tied to U-Boot's stage of activity based on your reports of the notices output. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D578DD89-6973-44C5-AACA-0D280AE0CD13>