Detection issue of M.2 nvme SSD on Jetson AGX Orin 32G
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.(PCIe C4 RP, ‘pcie@14160000’)
This SSD can be recognized on another custom carrier board (with another orin 64G)with PCIe C7 RP(‘pcie@141e0000’).
These are my system details:
nv@tegra-ubuntu:~$ uname -a
Linux tegra-ubuntu 5.15.122-tegra #1 SMP PREEMPT Thu Nov 30 10:30:37 PST 2023 aarch64 aarch64 aarch64 GNU/Linux
nv@tegra-ubuntu:~$ sudo cat /sys/kernel/debug/bpmp/debug/uphy/config
[sudo] password for nv:
0x00584000
nv@tegra-ubuntu:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk3 179:0 0 59.3G 0 disk
├─mmcblk3p1 179:1 0 57.8G 0 part /
├─mmcblk3p2 179:2 0 128M 0 part
├─mmcblk3p3 179:3 0 768K 0 part
├─mmcblk3p4 179:4 0 31.6M 0 part
├─mmcblk3p5 179:5 0 128M 0 part
├─mmcblk3p6 179:6 0 768K 0 part
├─mmcblk3p7 179:7 0 31.6M 0 part
├─mmcblk3p8 179:8 0 80M 0 part
├─mmcblk3p9 179:9 0 512K 0 part
├─mmcblk3p10 179:10 0 64M 0 part
├─mmcblk3p11 179:11 0 80M 0 part
├─mmcblk3p12 179:12 0 512K 0 part
├─mmcblk3p13 179:13 0 64M 0 part
├─mmcblk3p14 179:14 0 400M 0 part
└─mmcblk3p15 179:15 0 479.5M 0 part
mmcblk3boot0 179:32 0 31.5M 1 disk
mmcblk3boot1 179:64 0 31.5M 1 disk
zram0 252:0 0 1.9G 0 disk [SWAP]
zram1 252:1 0 1.9G 0 disk [SWAP]
zram2 252:2 0 1.9G 0 disk [SWAP]
zram3 252:3 0 1.9G 0 disk [SWAP]
zram4 252:4 0 1.9G 0 disk [SWAP]
zram5 252:5 0 1.9G 0 disk [SWAP]
zram6 252:6 0 1.9G 0 disk [SWAP]
zram7 252:7 0 1.9G 0 disk [SWAP]
nv@tegra-ubuntu:~$ lspci -vvv
(lspci -vvv has no output)
dmesg:
dmesg.txt (52.9 KB)
dts:
tegra234-p3737-0000+p3701-0004-nv.dts.txt (313.5 KB)
pinmux is Jetson_AGX_Orin_Series_Pinmux_Config_Template_1.9.xlsm，We haven’t made any changes.
tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi.txt (63.6 KB)
we use “sudo ./flash.sh jetson-agx-orin-devkit internal” to flash." jetson-agx-orin-devkit" has no change.
Another issue is that we tested The state of PEX_ L4_ RST_N (J9) will go from low level to high level 1-2 times from the beginning of power on to entering the system, and finally remain low level.Is this a problem?