Date: Wed, 27 Oct 2021 09:28:52 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Cc: bob prohaska <fbsd@www.zefox.net> Subject: Re: Troubles booting Pi2 from USB using bootcode.bin method Message-ID: <20211027162852.GA16010@www.zefox.net> In-Reply-To: <20211025034332.GA8398@www.zefox.net> References: <20211025034332.GA8398@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 24, 2021 at 08:43:32PM -0700, bob prohaska wrote: > I've got an early Pi2B (not plus) that has been booting reliably > from a USB2 disk connected via a USB3 hub using just bootcode.bin > and timeout on the DOS partition of the microSD card. > It turns out the USB3 disk boots normally _provided_ the old USB2 disk remains connected. I didn't try that initially both because I didn't need both disks and because the boot order couldn't be obviously controlled. It turns out the new disk is discovered first and boots as desired, so the system is busy building an up-to-date world and kernel. There's room for a ports tree on this disk. Does the ports version of u-boot include support for the bootcode.bin-only mode of USB booting? Right now I'm using the version of bootcode.bin offered at https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#special-bootcode-bin-only-boot-mode Without having the USB2 disk connected the serial console hangs with what looks like "cb" as the only output. It's unclear if u-boot is starting at all. The red and green LEDs remain lit, seemingly indefinitely. Thanks for reading, and any ideas. bob prohaska > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20211027162852.GA16010>