On a 1.3B board, my NVMe SSD failed to enumerate on firmware 6.0.0. The NVMe controller is a Phison PS5013-E13 (PCIE 1987:5013).
The VF2 was able to communicate with the device:
StarFive # pci display.b 3.0.0 0x00 0x40
00000000: 87 19 13 50 06 00 10 00 01 02 08 01 08 00 00 00
00000010: 04 00 00 38 00 00 00 00 00 00 00 00 00 00 00 00
but no devices became available:
StarFive # pci info
Scanning PCI devices on bus 0
BusDevFun VendorId DeviceId Device Class Sub-Class
_____________________________________________________________
00.00.00 0x1556 0x1111 Bridge device 0x04
StarFive # nvme scan
StarFive # nvme info
StarFive # nvme device
no nvme devices available
and the uclass remained inactive:
uclass 62: nvme
0 nvme#0 @ f7703a10, seq 0
The immediately older 5.14.1 firmware successfully boots from the same SSD with no changes, so I think this is a regression. The specific versions from the u-boot string are:
Good: U-Boot 2021.10 (May 07 2025 - 15:41:57 +0800), Build: jenkins-github_visionfive2_6.6-10
Bad: U-Boot 2021.10 (Oct 10 2025 - 11:25:33 +0800), Build: jenkins-github_visionfive2_6.12-16
I originally wrote an image to the drive with a 1.2A VF2 but I don't know exactly what firmware version it's running (excepting that it was long enough ago that it almost certainly isn't 6.0.0).
Let me know if there's any other information I can provide.
On a 1.3B board, my NVMe SSD failed to enumerate on firmware 6.0.0. The NVMe controller is a Phison PS5013-E13 (PCIE 1987:5013).
The VF2 was able to communicate with the device:
but no devices became available:
and the uclass remained inactive:
The immediately older 5.14.1 firmware successfully boots from the same SSD with no changes, so I think this is a regression. The specific versions from the u-boot string are:
I originally wrote an image to the drive with a 1.2A VF2 but I don't know exactly what firmware version it's running (excepting that it was long enough ago that it almost certainly isn't 6.0.0).
Let me know if there's any other information I can provide.