Jetson Orin Nano 8GB DevKit - NVMe PCIe error on custom board

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
,
1

Hello,

I’m working since few weeks with a NVIDIA Jetson Orin Nano 8GB DevKit (JetPack 6.0 - Jetson Linux 36.3) mounted on a custom board.

After having flashed the QSPI and NVMe, it asked to log in with the default user, but after ~30 seconds it crashed. Afterwards, no more serial logs, no more NVMe detected.

nvme_crash.txt (1.8 KB)

It looks like the problem was a PCIe error, which let me think about SIGNALS issues, and then hardware-side defect, but before this I would exclude the problem is software-side.

To exclude SOM 8 GB DevKit/NMVe problem I mounted them on a DevKit, flashed, and everything is working.

I would appreciate some hint about what most likely the problem is, if software-side on kernel customization, or hardware side.

Best regards,

Simone Contorno

2

Hi,

Just want to explain some terms first

A devkit means Orin SOM + NVIDIA official carrier board. So there is actually nothing called you mount a devkit on a custom board. This kind of description is not correct.

I guess you are talking about putting a Orin SOM on your custom board.

If so, then please review your hardware design of PCIe C4. Such error is generally not related to software.

3

Hello,

thanks for the correction. Yes, I confirm that is what I meant — I was referring to the Orin SOM mounted on my custom carrier board. I highlighted “DevKit” only because, as far as I understood, the SOM may pick up a different DTB depending on whether it is a DevKit SOM or not.

Could you please give me a bit more detail about your hint? If the issue is related to PCIe C4, why is the NVMe device detected at first and even flashable, but then the system crashes and afterwards the NVMe is no longer detected? Replacing it with a new NVMe makes it visible again.

Thanks in advance.

Best regards,
Simone

4

This does not matter. It is same SOM on your board or NV devkit. Carrier board change does not affect it.
Same dtb is in use.

Could you please give me a bit more detail about your hint? If the issue is related to PCIe C4, why is the NVMe device detected at first and even flashable, but then the system crashes and afterwards the NVMe is no longer detected? Replacing it with a new NVMe makes it visible again.

There is nothing more to check here. This is just experience. If same NVMe won’t trigger any PCIe bus error on a devkit but on your custom board, as the software is same, it could only be related to hardware design on your board.
Such case always happens on custom board.

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.