I'll start by quoting Jeff Geerling ![:D]( "Very Happy")
"As of now, no. I can see and use an NVMe SSD through a PCIe switch, but I am not able to boot the Raspberry Pi 5 from it, unless it is directly connected (as the lone PCIe device on the bus)."
In theory the 0218 has only one PCIe and no switches... in theory...
https://wiki.52pi.com/index.php?title=EP-0218
Installed today a PINN multiOS image on a 128gb nvme SSD
with Pi imager from a Mac, then installed it in the NVDAC.
Connected the GPIOs and the Pcie cables.
My Main OS boots from a USB 3.1 key.
52Pi Hybrid NVDAC with the MultiOS SSD is now Mounted on my rpi 5 4gb.
PS: I left a little space for ventilation, the GPIO are making contact but are not fully inserted, the
extension 40 Pin provided barely comes out from the HAT; all GPIO should be making good contact,
and the PCIe cable instead has no gaps and seems to be 100% ok.
(PPS: I had after am lsdpi an interrupt message on pin 39, a gnd pin, idk if it's ok or if it was signalling some
kind of problem with the GPIO, the hat connection or what...)
I followed two distinct wikis for the two parts of this Hybrid Hat.
The Hifiberry part for the DAC, and it worked. I have audio out.
nano /boot/firmware/config.txt
dtparam=hifiberry-dacplus,slave
That first wiki however do not cover the nvme part...
So I used a mix of this wiki and Jeff video on adding nvme hats on youtube
https://wiki.52pi.com/index.php?title=EP-0230
nano boot etc... added
dtparam=pciex1
dtparam=pciex1_gen=3
From Jeff I got also this part that is included in the video guide
sudo lspci
but Jeff blog guide is better... detailed...
sudo lspci -vvv
------------- https://www.jeffgeerling.com/blog/2023/ ... berry-pi-5
# Edit the EEPROM on the Raspberry Pi 5.
sudo rpi-eeprom-config --edit
# Change the BOOT_ORDER line to the following:
BOOT_ORDER=0xf416 (I used fx414 )
# Add the following line if using a non-HAT+ adapter:
PCIE_PROBE=1
# Press Ctrl-O, then enter, to write the change to the file.
# Press Ctrl-X to exit nano (the editor).
It seems the console sees a root filesystem on pcie device, but even running jeff curl hdparm stuff doesn't list it in the
devices connected...
I performed a series of updates included eeprom updates
https://wiki.geekworm.com/How_to_update_eeprom_firmware
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-update
I tried to enable the nvme drive but still could not see it...
I am still following Jeff guide to see if I can sort it out...
The drive was already flashed with PINN MultiOs, but because my patchblock OS doesn't see the Nvme M.2 drive,
I can't select it from the boot order. (And also the boot-config works differently on patchblock OS...)
Also rebooting the system with just the NVDAC hat and no other SD or USB OS
did not work...
suggestions??
Jeff made me install HDPARM and other stuff I could now use I hadn't before...
I installed PINN just as a test, there's nothing installed there.
Just wanted to see If could dual boot into another OS, like standard rpi 5 Os bookworm.
Maybe next step could be to install the Pi imager on the Pi5 directly but if I can't see the drive with dolphin nor lsdpi...
Maybe reflash the drive to ms-dos??
"As of now, no. I can see and use an NVMe SSD through a PCIe switch, but I am not able to boot the Raspberry Pi 5 from it, unless it is directly connected (as the lone PCIe device on the bus)."
In theory the 0218 has only one PCIe and no switches... in theory...
https://wiki.52pi.com/index.php?title=EP-0218
Installed today a PINN multiOS image on a 128gb nvme SSD
with Pi imager from a Mac, then installed it in the NVDAC.
Connected the GPIOs and the Pcie cables.
My Main OS boots from a USB 3.1 key.
52Pi Hybrid NVDAC with the MultiOS SSD is now Mounted on my rpi 5 4gb.
PS: I left a little space for ventilation, the GPIO are making contact but are not fully inserted, the
extension 40 Pin provided barely comes out from the HAT; all GPIO should be making good contact,
and the PCIe cable instead has no gaps and seems to be 100% ok.
(PPS: I had after am lsdpi an interrupt message on pin 39, a gnd pin, idk if it's ok or if it was signalling some
kind of problem with the GPIO, the hat connection or what...)
I followed two distinct wikis for the two parts of this Hybrid Hat.
The Hifiberry part for the DAC, and it worked. I have audio out.
nano /boot/firmware/config.txt
dtparam=hifiberry-dacplus,slave
That first wiki however do not cover the nvme part...
So I used a mix of this wiki and Jeff video on adding nvme hats on youtube
https://wiki.52pi.com/index.php?title=EP-0230
nano boot etc... added
dtparam=pciex1
dtparam=pciex1_gen=3
From Jeff I got also this part that is included in the video guide
sudo lspci
but Jeff blog guide is better... detailed...
sudo lspci -vvv
------------- https://www.jeffgeerling.com/blog/2023/ ... berry-pi-5
# Edit the EEPROM on the Raspberry Pi 5.
sudo rpi-eeprom-config --edit
# Change the BOOT_ORDER line to the following:
BOOT_ORDER=0xf416 (I used fx414 )
# Add the following line if using a non-HAT+ adapter:
PCIE_PROBE=1
# Press Ctrl-O, then enter, to write the change to the file.
# Press Ctrl-X to exit nano (the editor).
It seems the console sees a root filesystem on pcie device, but even running jeff curl hdparm stuff doesn't list it in the
devices connected...
I performed a series of updates included eeprom updates
https://wiki.geekworm.com/How_to_update_eeprom_firmware
sudo apt update
sudo apt upgrade -y
sudo rpi-eeprom-update
I tried to enable the nvme drive but still could not see it...
I am still following Jeff guide to see if I can sort it out...
The drive was already flashed with PINN MultiOs, but because my patchblock OS doesn't see the Nvme M.2 drive,
I can't select it from the boot order. (And also the boot-config works differently on patchblock OS...)
Also rebooting the system with just the NVDAC hat and no other SD or USB OS
did not work...
suggestions??
Jeff made me install HDPARM and other stuff I could now use I hadn't before...
I installed PINN just as a test, there's nothing installed there.
Just wanted to see If could dual boot into another OS, like standard rpi 5 Os bookworm.
Maybe next step could be to install the Pi imager on the Pi5 directly but if I can't see the drive with dolphin nor lsdpi...
Maybe reflash the drive to ms-dos??
Statistics: Posted by Zool64Pi — Thu May 15, 2025 7:36 pm