Samsung 980 Pro PCIe 4.0 NVME M.2 500GB & TX2 NX

Hi I got this drive, and added it to my NX carrier bound, which as my TX2 NX module running on it. However, the device is not detected via lsblk, gparted, fdisk -l, nor its controller via lspci. As I understand this works with the AGX and NX devices. Are the NVMe drives on the NX carrier board not workable for the TX2 NX compute module? It is running R32 REV 5.1 JP (the only one that seems to work with it that boots). Any ideas? I tried reseating it a couple times, and the ssd board is single sided and physically fits well. The device powers up just doesn’t see the SSD.

Ryan

also I just swapped the Xavier NX compute module, and it does see the SSD drive on the board - using JP 4.4. So it seems like a TX2 NX compute module issue with SSD.

Could you share the dmesg?

dmesg-tx2nx.zip (21.7 KB) here it is…don’t see any mention of nvme or anything in it.

I’m not positive, but if you are swapping the NX form factor TX2 module and Xavier NX module on the same carrier board, then I’m wondering if that is in itself some sort of compatibility issue. Don’t know.

yes since there is no dev kit carrier board for tx2 nx, this was what was recommended to me. Since this module has such little storage on it, it hurts more the m2 nvme isn’t working with it. It seems like usb storage is about the only option for now (which I am doing).

Could you share the result of lspci -vv?

yep… as I said its not there at all.
lspci -vv
00:01.0 PCI bridge: NVIDIA Corporation Device 10e5 (rev a1) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 376
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport

00:03.0 PCI bridge: NVIDIA Corporation Device 10e6 (rev a1) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 376
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: 40100000-401fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport

02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c822
Subsystem: AzureWave Device 3751
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 451
Region 0: I/O ports at 1000 [size=256]
Region 2: Memory at 40100000 (64-bit, non-prefetchable) [size=64K]
Capabilities:
Kernel driver in use: rtl88x2ce
Kernel modules: rtl8822ce