RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ?

[Andy McClements]

Hi, I'm new to FreeBSD on the RPI, so have been frantically reading old 
mailing-list posts and so on. I've managed to arrive at a fairly 
'current' configuration which boots, but on which XHCI is broken. So I 
could do with some pointers.

I have:
RPI4B 8GB recent HW, v. 0xd03114
Bootloader: Sep  3 2020
Boot device: 32GB SDHC
SD imaged with:
FreeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20201210-7578a4862f0.img.xz
config_RPI4.txt renamed to config.txt
All RPI firmware files on the DOS partition updated from the Github master:
https://github.com/raspberrypi/firmware/archive/master.zip
U-Boot.bin replaced with the one which is supposed to have XHCI & 8Gb 
support, from:
https://sourceforge.net/projects/rpi4uboot202010-fbsdonly-klaus/files/u-boot.bin

The system boots up but the dmesg shows 'xhci firmware not found'.

Dmesg: https://dmesgd.nycbug.org/index.cgi?do=view&id=5842

Not shown in the dmesg is the U-Boot output (below), wherin I suspect 
lies the smoking gun. I do not like the look of:

"Bus xhci_pci: probe failed, error -110
No working controllers found"

After a brief hunt I became filled with uncertainty about U-Boot and its 
support for FreeBSD on the RPI.

So I though it best to check in here for advice.

I did try the RPI4 SBBR UEFI firmware from https://rpi4-uefi.dev/about/, 
on a USB3.0 SSD, and that worked first time, but I've not yet put an OS 
on the SSD. Maybe that's now a better bootloader option for my needs 
than is U-Boot ?

TIA, Andy

--

U-Boot 2020.10-rc5 (Oct 05 2020 - 03:08:23 +0000)

DRAM:  7.9 GiB
RPI 4 Model B (0xd03114)
MMC:   mmc at 7e300000: 1, emmc2 at 7e340000: 0
Loading Environment from FAT... In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   eth0: ethernet at 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
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found EFI removable media binary efi/boot/bootaa64.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc at 7e300000.blk...
Disk mmc at 7e300000.blk not ready
Scanning disk emmc2 at 7e340000.blk...
** Unrecognized filesystem type **
Found 3 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
1182828 bytes read in 69 ms (16.3 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Booting /efi\boot\bootaa64.efi
Consoles: EFI console
     Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
(Thu Dec 10 12:29:22 UTC 2020 root at releng1.nyi.freebsd.org)

    Command line arguments: loader.efi
    Image base: 0x39e0a000
    EFI version: 2.80
    EFI Firmware: Das U-Boot (rev 8224.4096)
    Console: comconsole (0)
    Load Path: /efi\boot\bootaa64.efi
    Load Device: 
/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,MBR,0xe3c2d5bd,0x81f,0x18fa8)
Trying ESP: 
/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,MBR,0xe3c2d5bd,0x81f,0x18fa8)
Setting currdev to disk0p1:
Trying: 
/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,MBR,0xe3c2d5bd,0x197c7,0x3b58839)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
Loading kernel...
/boot/kernel/kernel text=0x2a8 text=0x88211c text=0x1f2174 data=0x19cd48 
data=0x0+0x5446f6 syms=[0x8+0x117780+0x8+0x13c5ab]
Loading configured modules...
/boot/entropy size=0x1000
/etc/hostid size=0x25
/boot/kernel/umodem.ko text=0x2120 text=0x1390 data=0x6e0+0x10 
syms=[0x8+0xf48+0x8+0xb6e]
loading required module 'ucom'
/boot/kernel/ucom.ko text=0x21a0 text=0x2e20 data=0x880+0x858 
syms=[0x8+0x11a0+0x8+0xb2c]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...