Detection issue of M.2 nvme SSD on Jetson AGX Orin

[solo_wh]

Dear Nvidia Team

We face some problems with NVMe SSDs(EXPI4512GB-WP005,M2 2280) on our custom carrier boards. The M.2 Key M Interface is identical to the reference design.

These are my system details:

nv@tegra-ubuntu:~$ uname -a
Linux tegra-ubuntu 5.10.104-tegra #5 SMP PREEMPT Thu Dec 7 14:50:48 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
nv@tegra-ubuntu:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p1 57G 5.9G 48G 11% /
none 15G 0 15G 0% /dev
tmpfs 15G 36K 15G 1% /dev/shm
tmpfs 3.0G 11M 3.0G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 15G 0 15G 0% /sys/fs/cgroup
tmpfs 3.0G 44K 3.0G 1% /run/user/1000
nv@tegra-ubuntu:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 59.3G 0 disk
├─mmcblk0p1 179:1 0 57.8G 0 part /
├─mmcblk0p2 179:2 0 128M 0 part
├─mmcblk0p3 179:3 0 768K 0 part
├─mmcblk0p4 179:4 0 31.6M 0 part
├─mmcblk0p5 179:5 0 128M 0 part
├─mmcblk0p6 179:6 0 768K 0 part
├─mmcblk0p7 179:7 0 31.6M 0 part
├─mmcblk0p8 179:8 0 80M 0 part
├─mmcblk0p9 179:9 0 512K 0 part
├─mmcblk0p10 179:10 0 64M 0 part
├─mmcblk0p11 179:11 0 80M 0 part
├─mmcblk0p12 179:12 0 512K 0 part
├─mmcblk0p13 179:13 0 64M 0 part
└─mmcblk0p14 179:14 0 879.5M 0 part
zram0 251:0 0 1.9G 0 disk [SWAP]
zram1 251:1 0 1.9G 0 disk [SWAP]
zram2 251:2 0 1.9G 0 disk [SWAP]
zram3 251:3 0 1.9G 0 disk [SWAP]
zram4 251:4 0 1.9G 0 disk [SWAP]
zram5 251:5 0 1.9G 0 disk [SWAP]
zram6 251:6 0 1.9G 0 disk [SWAP]
zram7 251:7 0 1.9G 0 disk [SWAP]
nv@tegra-ubuntu:~$ lspci -vvv
(lspci -vvv has no output)

dmesg：
dmesg.txt (70.0 KB)
dts：
tegra234-p3701-0000-p3737-0000.dts.txt (495.8 KB)

board.conf:
orin_ad.conf.txt (319 Bytes)

pinmux is Jetson_AGX_Orin_Series_Pinmux_Config_Template_1.9.xlsm，We haven’t made any changes.

cat /sys/kernel/debug/gpio:
debug-gpio.txt (7.3 KB)

Any help for fixing this would be appreciated.

[WayneWWW]

Release version looks a little old. Suggest to use latest release first.

[solo_wh]

Thank you for your reply. We have already done a lot of work on this version, and upgrading is not a simple task. We plan to upgrade to the latest version after completing the remaining work. I think this issue might not be due to the version.Could you please check our current settings (dts, dmesg, gpio, etc.)?

[WayneWWW]

First, why are you using a Orin devkit module to work on a custom board? You posted a sku0 module device tree here.

Second, the pinmux used on old release is wrong for production module. That is why I said you should upgrade.

[solo_wh]

I went to inquire and it

seems that our product is not Orin devkit module，But I’m not sure if I made any mistakes or if the device tree was used incorrectly。I use “./flash.sh orin_ad internal” to flash(The content of orin_ad can be found in the attachment orin_ad.conf.txt)。If there are any issues, please point them out。

Anyway, I will upgrade first and then try SSD，thanks。

[WayneWWW]

Yes, then issue here is you are using tegra234-p3701-0000-p3737-0000.dts for your modification.

But this dtb is not used for production module.

[solo_wh]

May I ask which DTB can be used for production modules or what modifications should I make to avoid using this incorrect DTB? Can you point it out

[WayneWWW]

Your dmesg already showed that. You can read your dmesg first.

[WayneWWW]

Also, there is no extra software modification needed for a custom board M.2 if it is really “same as devkit”.
If something cannot work, please review your hardware. Or check if your software really matches devkit situation (pinmux/dtb content for PCIe)