Date: Sun, 3 Jan 2021 20:16:50 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Andy McClements <ajm@ip-ether.net> Cc: freebsd-arm@freebsd.org, Emmanuel Vadot <manu@freebsd.org> Subject: Re: RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ? Message-ID: <20210103201650.e84bee4065888be792c25c05@bidouilliste.com> In-Reply-To: <eb72b668-7a02-c873-5af8-b292b5eb12a5@ip-ether.net> References: <007c8658-b7b6-6852-536c-9c36af64506b@ip-ether.net> <D22EDD0F-8A8E-466C-BCEC-C8E2B3EA9A6B@googlemail.com> <aaefd44f-9dfd-be08-b446-d85c1df185a9@ip-ether.net> <5B626DCC-6F7C-4554-803C-F488A1ED9BEB@googlemail.com> <56d10ea4-3284-3e4c-9521-8bf1008caa2b@ip-ether.net> <26D146B8-0362-4008-9A1F-A6CD6B1479BB@googlemail.com> <6610c9a3-1e61-b7e5-c537-3080dd7ee8ae@ip-ether.net> <eb72b668-7a02-c873-5af8-b292b5eb12a5@ip-ether.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Jan 2021 18:29:34 +0000 Andy McClements <ajm@ip-ether.net> wrote: > On 03/01/2021 11:43, Andy McClements wrote: > > > HW: RPi4b 8GB, late 2020 purchase, Sept 3rd EEPROM > > OS: > > FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224-3cc0c0d66a0-255241.img.xz > > Boot device: 128GB USB3 SSD > > > I am happy to say that, WITH PATCH D26853, all of these will > > successfully allow FreeBSD 20201224 to boot from USB SSD. Also that the > > vanilla 20201224 img (which I have checked includes the 20201201 > > firmware) also works fine, WITH PATCH D26853. > > > > I have also double-checked that the current firmware release, 20201227, > > with the patch, DOES NOT WORK. As previously reported, I just see a > > crash-loop in U-boot, if attempting to boot from USB SSD. > > Further on this, I have just done another test by replacing only: > > bcm2711-rpi-4-b.dtb > > on the FreeBSD 13.0-CURRENT 20201224 img, with the one from the RPI > firmware 20201227 release. There is no 20201227 release so I guess you just took whatever is in github at this day ? > This **allows booting from USB**, which fails on the stock 20201224 img. Diffing the dtb present in the ports (and so in the 20201201 release) and the one in git currently (last updated on the 15th of december) I see that the raspberrypi,firmware-reset node is now present. U-boot have a driver for this to reset the vl805 usb chip so I guess this explain that it's needed for usb working in u-boot. https://github.com/u-boot/u-boot/blob/master/drivers/reset/reset-raspberrypi.c > So it seems to me that patch D26853 **is not required**, if the upstream > file is now working OK. > > HOWEVER, the 20201227 firmware release appears to introduce some other > problem, as already reported if ALL the files on the DOS partition are > replaced with those from 20201227, it results in a crash in U-boot. > > To summarise then, on the hardware mentioned above: > > 1. Vanilla FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224 > > " starting USB... > Bus xhci_pci: probe failed, error -110 > No working controllers found " > > Result: disk boot fails, RPi attempts to net boot. > > 2. Vanilla FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224 > > + REPLACE ONLY bcm2711-rpi-4-b.dtb with the version from the 20201227 > release. > > "starting USB... > Bus xhci_pci: Register 5000420 NbrPorts 5 > Starting the controller > USB XHCI 1.00 > scanning bus xhci_pci for devices... 3 USB Device(s) found > scanning usb for storage devices... 1 Storage Device(s) found" > > Result: disk boot succeeds > > 3. Vanilla FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224 > > + REPLACE ALL FIRMWARE FILES with the versions from the 20201227 > firmware release. > > Result: U-Boot crashes: > > U-Boot 2020.10 (Dec 24 2020 - 04:18:29 +0000) > > DRAM: 7.9 GiB > RPI 4 Model B (0xd03114) > MMC: mmc@7e300000: 1, emmc2@7e340000: 0 > Loading Environment from FAT... In: serial > Out: serial > Err: serial > Net: eth0: ethernet@7d580000 > PCIe BRCM: link up, 5.0 Gbps x1 (SSC) > starting USB... > Bus xhci_pci: probe failed, error -110 > No working controllers found > Hit any key to stop autoboot: 0 > Card did not respond to voltage select! > starting USB... > Bus xhci_pci: probe failed, error -110 > No working controllers found This error looks a lot like the one with the old dtb, are you sure you did update everything ? Could you try replacing the file one by one to bisect which one causes the problem ? Cheers, > USB is stopped. Please issue 'usb start' first. > "Synchronous Abort" handler, esr 0x96000004 > elr: 000000000009bae0 lr : 00000000000919dc (reloc) > elr: 000000003b278ae0 lr : 000000003b26e9dc > x0 : 0000000b00000000 x1 : 0000000b00000030 > x2 : 000000003aee9e00 x3 : fffffff53aee9d70 > x4 : 000000003b2d30b0 x5 : 000000003aee9da0 > x6 : 000000003b2d30c0 x7 : 000000003aee9dd0 > x8 : 000000003ae4bd20 x9 : 0000000000000008 > x10: 00000000ffffffd0 x11: 0000000000000006 > x12: 000000000001869f x13: 00000000000069c4 > x14: 0000000000000000 x15: 00000000fffffffe > x16: 0000000000004110 x17: 0000000000000000 > x18: 000000003ae58d90 x19: 0000000000000000 > x20: 0000000000000000 x21: 000000003aee9db0 > x22: 0000000000000000 x23: 0000000000000002 > x24: 0000000000000000 x25: 0000000000000000 > x26: 0000000000000028 x27: 0000000000000003 > x28: 000000003b2e4e94 x29: 000000003ae4c1c0 > > Code: f85f0000 91004086 cb000063 8b000021 (f9400860) > Resetting CPU ... -- Emmanuel Vadot <manu@bidouilliste.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210103201650.e84bee4065888be792c25c05>