Dear sir i am facing issue of detection of M. 2 in my jetson unit can you sugget me to come out from this problem? My m. 2 is gen3 x4 lane
What your M2 device is?
How do you connect it on TX2 devkit?
M.2 device is
M.2 NVME GEN3 X4 SSD 240GB PART NUMBER-CSSD-F240GBMPS10
WE HAVE OWN PRODUCT INCLUDES 8GB JETSON AGX XAVIER MODULE IN OUR PRODUCT
Is that TX2 a devkit? Why you file a topic in jetson TX2 forum while you are telling me you have AGX Xavier?
Regardless of if it is AGX Xavier or Nano, you would still need a full serial console boot log to see what PCIe does during boot (including prior to the Linux kernel loading, and so
dmesg would be insufficient). Once fully booted you would also need the log from:
sudo lspci -vvv 2>&1 | tee log_lspci.txt
log_lspci.txt” to the forum and the serial console boot log)
An early comment, without knowing if this has anything to do with it (there are no logs): Signal quality can cause a device to disappear, but if device tree is wrong (and a different device tree is needed for different modules, plus a different tree is needed for different carrier boards), then the host will basically be looking for devices on the wrong wire (and that definitely makes things disappear). You would need to make sure the device tree is modified for your carrier board and module combination.
Moving it into AGX Xavier forum.
Is this still an issue to support? Any result can be shared? Thanks
M. 2 not detectes in our jetson agx module carrier board. I want to know what’s nvme enable or disable in bootloader? How to do that? Is it impact on m. 2 detection?
If you use jetpack with version >= 4.6, then nvme is already enabled in bootloader. No need to configure on your side.
And also I am using C5 pcie controller of my jetson agx module 8GB for the interface of nvme m. 2.guide me how to check the status of nvme in bootloader. Is there any command?
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.