Date: Sat, 30 Oct 2021 22:57:12 -0700 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: Free BSD <freebsd-arm@freebsd.org> Subject: Re: Troubles booting Pi2 from USB using bootcode.bin method Message-ID: <97151A41-3077-4507-A477-92318605911F@yahoo.com> In-Reply-To: <20211030213553.GA25712@www.zefox.net> References: <41C0A656-D898-4381-BB81-034D54CA04A0@yahoo.com> <02806205-6685-41FD-B2D1-415C82FBCF92@yahoo.com> <C99139A0-09A9-4A5E-AB53-719E07C16A22@yahoo.com> <20211028191635.GA19540@www.zefox.net> <7AC0733A-3FC9-4FA6-A6D7-0689A8ACB4CA@yahoo.com> <D8DC329F-DFE4-4542-AA4D-87C41A50C8A4@yahoo.com> <20211029182430.GA22414@www.zefox.net> <F1FDAFBC-5CC7-41D0-BC62-9B7AFBC037DD@yahoo.com> <B723533A-A8DD-4F20-A3F0-BAE4D675A304@yahoo.com> <086D6998-A96F-4560-92C5-4E2CE05FF668@yahoo.com> <20211030213553.GA25712@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Oct-30, at 14:35, bob prohaska <fbsd@www.zefox.net> wrote: > On Sat, Oct 30, 2021 at 01:41:52AM -0700, Mark Millard via freebsd-arm = wrote: > . . . > I've captured one failure session at > http://www.zefox.net/~fbsd/rpi2/bootproblems/bootlog-usb3-solo.fail > but cannot reliably reproduce it.=20 Later below I'll list some notes about the failure modes shown in >=20 > http://www.zefox.net/~fbsd/rpi2/bootproblems/ >> When the console offers the >> U-Boot>=20 >> prompt, is that coming from bootcode.bin, or something else? The U-Boot> prompt is from u-boot.bin (i.e., U-Boot itself). This is after bootcode.bin and start.elf do their part of the boot sequence. >> Could anything be learned from trying to boot the armv7-configured >> disk on a Pi3B or B+ ? You could try the same microsd card, USB3 powered hub, and USB3 drive on a RPi3B or RPi3B+ . This would not use the bcm2709-rpi-2-b.dtb = . >> That's a relatively easy experiment. I'm >> trying to use a rather old Pi with a comparatively new USB drive. >> The Pi3s on hand are at least somewhat more modern. >=20 In my RPi2B v1.1 context, when I have access, the USB3 portable SSD is is first generation USB3 as I remember --but does not require a powered hub. Failure mode notes: For: . . . Found 4 ports, multi_tt =3D 0 Enabling PORT POWER on port 1 Enabling PORT POWER on port 2 Enabling PORT POWER on port 3 Enabling PORT POWER on port 4 Waiting for devices to respond to reset Found device on port 1 Found highspeed device Set address 7 Num devices =3D 4, addr =3D 7 get_config_descriptor 85 bytes device class =3D 0 interface_desc[1] =3D 4 Device found: type =3D Mass storage, addr =3D 7 Trying booting from MSD device addr 7 Retrieving the config descriptor Found ep_in =3D 00000001, ep_out =3D 00000002 GetMaxLun returned 0, max_lun =3D 0 Sending and retrying TEST_UNIT_READY Failed to test volume, probably not ready init_msd returned -2 Failed initialising mass storage device Trying booting from Ethernet device addr 5 Trying booting from Ethernet device addr 5 Trying booting from Ethernet device addr 5 . . . This failure mode never even reads a file from the USB3 drive. U-Boot is not relevant. Not even the RPi* firmware on the USB3 drive is relevant. For: . . . U-Boot 2020.10 (Apr 09 2021 - 04:09:01 +0000) DRAM: 948 MiB RPI 2 Model B (0xa21041) MMC: mmc@7e300000: 1 Loading Environment from FAT... In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e980000: USB DWC2 scanning bus usb@7e980000 for devices... unable to get device descriptor = (error=3D-22) . . . This made it to U-Boot. usb_ready_retry, usb_pgood_delay, and/or usb_max_blk use might help? For: . . . U-Boot 2020.10 (Apr 09 2021 - 04:09:01 +0000) DRAM: 948 MiB Error binding driver 'bcm283x_pinctrl': -12 Error binding driver 'serial_pl01x': -12 Error binding driver 'dwc2_usb': -12 Error binding driver 'sdhci-bcm2835': -12 Error binding driver 'simple_bus': -12 Error binding driver 'bcm2835_video': -12 Some drivers failed to bind Error binding driver 'simple_bus': -12 Some drivers failed to bind initcall sequence 3b3e2498 failed at call 0001a270 (err=3D-12) ### ERROR ### Please RESET the board ### This made it to U-Boot but seems to be a different failure mode. I've no clue about the drivers that "failed to bind" or why. I again wonder about unreliable I/O but have not specific evidence. =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?97151A41-3077-4507-A477-92318605911F>