On 2024-01-12, Michael Fladischer wrote: > I was able to boot my Hifive Unmatched Rev B board via SPI from NVME with > u-boot-sifive-2023.07+dfsg-1. After upgrading to 2024.01+dfsg-1 u-boot is no > longer able to see any NVME drives: ... > U-Boot 2024.01+dfsg-1 (Jan 10 2024 - 21:34:04 +0000) > > CPU: rv64imafdc > Model: SiFive HiFive Unmatched A00 > DRAM: 16 GiB > Core: 34 devices, 21 uclasses, devicetree: separate > MMC: spi@10050000:mmc@0: 0 > Loading Environment from SPIFlash... SF: Detected is25wp256 with page size > 256 Bytes, erase size 4 KiB, total 32 MiB > *** Warning - bad CRC, using default environment > > EEPROM: SiFive PCB EEPROM format v1 > Product ID: 0002 (HiFive Unmatched) > PCB revision: 4 > BOM revision: B > BOM variant: 0 > Serial number: SF105SZ233800886 > Ethernet MAC address: 70:b3:d5:92:fe:ea > CRC: d2ac1d5b > pwren_gpio is invalid > In: serial@10010000 > Out: serial@10010000 > Err: serial@10010000 > Model: SiFive HiFive Unmatched A00 > Net: eth0: ethernet@10090000 > Working FDT set to ff72f630 > Hit any key to stop autoboot: 0 > pwren_gpio is invalid > > Device 0: unknown device > pwren_gpio is invalid > > Device 1: unknown device > starting USB... > No working controllers found > USB is stopped. Please issue 'usb start' first. > pwren_gpio is invalid > scanning bus for devices...
I am getting this too. I had tested with a local build of 2024.01~rc6-1~0 and that worked fine, so I am a bit surprised as none of the very few commits between v2024.01-rc6 and v2024.01 seem relevent. I also wonder about opensbi, which was fairly recently upgraded, although I *thought* I tested opensbi 1.4-1 with the ~rc6 build I had done... Hrm. Will look a little deeper. I doubt it ws the removed unmatched-prevent-relocating-initrd-and-fdt.patch, as it is not even detecting the NVMe device... and the symptoms that necessitated that patch are after extlinux.conf is already loaded and the kernel attempts to boot... live well, vagrant
signature.asc
Description: PGP signature
