The original thread on this now seems to be locked.
The final couple of posts of solutions now get 404
![:-)]( "Smile")
)
I also bought a pi5 + Arggon5NVMe + 512Gb NVMe at the same time ... on the argon , I used the SD card copier (new UUID) and changed the boot order and it comes up fine on NVMe native boot .
But the same "technique" did not work with the Waveshare. I did the copy and popped the SD card. Looking via a serial console , it always said Failed to open device: 'nvme'
Being a CM4 I had to use rpiboot to add: PCIE_PROBE=1. It didn't help, but I'm now on a very recent bootloader:
....It's set to loop
... so I don't think it's a timing issue (had some of those with u-boot in the past .. forewarned)
I was just thinking the Waveshare simply didn't support NVMe boot ...they don't actually say it does (e.g. boot from eMMC and simply use NVMe) ... I also bought an Orange Pi.CM4 and that totally does NOT work in the waveshare (they have now told me this) ..again they didn't actually say ....
But having seen the precursor thread I see some folks are booting the Waveshare from NVMe ...I'm going to start swapping NVMe sticks ...maybe this one just has some issues
ABTW: I did note:
So maybe this NVMe is "a couple of sandwiches short of picnic".
2TB NVMe =====> Lexar NM610PRO 2TB SSD, NVME 1.4 PCIe Gen3x4 M.2 2280 Internal SSD, Up to 3300MB/s Read, 2600MB/s Write
512Gb NVMe ===> fanxiang NVMe M.2 2280 SSD 512GB, Up to 3200MB/s, 512GB NVMe SSD PCIe Gen3 x4, M.2 SSD
The final couple of posts of solutions now get 404
It's now May 2024. I bought the waveshare (NAS) box a few months ago. It booted fine via SD card and the (2TB) NVMe was accessible and ran speed tests and my own "check it's not a fake" software (sdcardscan ... I know it's not an SDI was able to resolve the issue by using this firmware from the stable branch: (pieeprom-2022-02-08.bin)
https://github.com/raspberrypi/rpi-eepr ... -02-08.bin
)I also bought a pi5 + Arggon5NVMe + 512Gb NVMe at the same time ... on the argon , I used the SD card copier (new UUID) and changed the boot order and it comes up fine on NVMe native boot .
But the same "technique" did not work with the Waveshare. I did the copy and popped the SD card. Looking via a serial console , it always said Failed to open device: 'nvme'
Being a CM4 I had to use rpiboot to add: PCIE_PROBE=1. It didn't help, but I'm now on a very recent bootloader:
Code:
0.10 RPi: BOOTSYS release VERSION:72caf667 DATE: 2024/05/17 TIME: 12:26:58 0.14 BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1715945218 serial 837 0.33 PM_RSTS: 0x00001000 0.33 part 00000000 reset_info 00000000 0.36 uSD voltage 3.3V 0.62 Initialising SDRAM 'Samsung' 16Gb x1 total-size: 16 Gbit 3200Code:
3.55 Boot mode: USB-MSD (04) order f256 3.73 PCI0 init 3.73 PCI0 reset 3.21 PCIe scan 00001b21:00001184 3.21 USB xHC init failed 3.23 Boot mode: NVME (06) order f25 3.27 PCIe scan 00001b21:00001184 3.30 Failed to open device: 'nvme' 3.33 Retry NVME 1 3.35 PCIe scan 00001b21:00001184 3.38 Failed to open device: 'nvme' 3.41 Boot mode: BCM-USB-MSD (05) order f2 3.49 XHCI-STOPCode:
graeme@waveshare:~ $ rpi-eeprom-config [all]# GPV 28May2024 debugging via UART seems usefulBOOT_UART=1WAKE_ON_GPIO=1POWER_OFF_ON_HALT=0# Boot Order Codes, from https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER# Try SD first (1), followed by, USB PCIe, NVMe PCIe, USB SoC XHCI then networkBOOT_ORDER=0xf25641# Set to 0 to prevent bootloader updates from USB/Network boot# For remote units EEPROM hardware write protection should be used.ENABLE_SELF_UPDATE=1# GPV 28May2024 HDMI setting was what was in waveshare originally# Set to 1 to disable the bootloader HDMI diagnostics screen AND# network install e.g. for kiosk devices.DISABLE_HDMI=0# GPV 28May2024 this is my guess as to what is needed to make NVMe visible at boot timePCIE_PROBE=1I was just thinking the Waveshare simply didn't support NVMe boot ...they don't actually say it does (e.g. boot from eMMC and simply use NVMe) ... I also bought an Orange Pi.CM4 and that totally does NOT work in the waveshare (they have now told me this) ..again they didn't actually say ....
But having seen the precursor thread I see some folks are booting the Waveshare from NVMe ...I'm going to start swapping NVMe sticks ...maybe this one just has some issues
ABTW: I did note:
Code:
[ 1.303875] nvme nvme0: pci function 0000:06:00.0[ 1.303907] nvme 0000:06:00.0: enabling device (0000 -> 0002)[ 1.305875] nvme nvme0: missing or invalid SUBNQN field.2TB NVMe =====> Lexar NM610PRO 2TB SSD, NVME 1.4 PCIe Gen3x4 M.2 2280 Internal SSD, Up to 3300MB/s Read, 2600MB/s Write
512Gb NVMe ===> fanxiang NVMe M.2 2280 SSD 512GB, Up to 3200MB/s, 512GB NVMe SSD PCIe Gen3 x4, M.2 SSD
Statistics: Posted by graemev — Wed May 29, 2024 2:26 pm — Replies 1 — Views 38