https://github.com/raspberrypi/linux/bl ... EADME#L347Well... Ooopsiee then :> I learned that with harsh way. I didn't expected how it can be that delicate. I hope the only thing that damaged is M2 Hat not the Pi 5.Oh also I tought they were different things, Since it didn't powered the M2 Hat, I pressed all the keys to make it workCode:
dtparam=pciex1dtparam=nvme
)
Thanks for your reply!
andpciex1 Set to "on" to enable the external PCIe link
(2712 only, default "off")
https://github.com/raspberrypi/linux/bl ... EADME#L330
To my best knowledge: When using the official M.2 HAT+ you will need none of these as the firmware probes for connected HAT+'s and should enable PCIEX1 once an official M.2 HAT is attached (in case the is no device connected to the HAT you will see a 'blabla pcie link down' message popping up while booting (check your logs).nvme Alias for "pciex1" (2712 only)
The regulator (U1) on the HAT get's supplied by 5V from the Pi (via GPIO), it's enable signal (PW R_EN) is on the FPC. As the PWR LED on the HAT does not light up looks like an issue with U1 (check https://datasheets.raspberrypi.com/m2-h ... matics.pdf and refer to https://www.diodes.com/assets/Datasheets/AP3441-L.pdf)
Statistics: Posted by aBUGSworstnightmare — Mon Jul 01, 2024 11:51 am