Requesting help to substitute the developer module with the production module

My current project uses the Jetson Xavier NX developer kit. However, this kit has been discontinued, and the lab’s units are no longer working. As an alternative, I plan to use the production version of the Jetson Xavier NX module, as it’s compatible with the carrier boards from our existing development kits. I’m encountering some issues with the initial boot process using the production modules. If you are able to advise or assist, I would appreciate it. Here are a few questions, regarding this alternative.

  • What does the initial booting process entail?

    • Does it involve using the built-in eMMC memory?

    • Can it be booted and forced into recovery mode when connected to a development carrier board?

  • When flashing using the SDK Manager, which JetPack version is compatible?

    • Would it be compatible with the version used by the Jetson with the SD card?
  • Storage is a big concern for this project.

    • Would substituting the SD card for an SSD be beneficial?

    • Is there a way to initially boot with the SSD, avoiding eMMC altogether?

    • Will the Jetson be able to natively boot from the SSD?

After installation of SDK manager onto Ubuntu 20.04, difficulties were encountered with the SDK Manager GUI. I attempted the installation via the command line as an alternative. However, I cannot put the Jetson into recovery mode, as the PC does not recognize it. The device is not recognized by the PC, regardless of whether it is used to use USB-A to USB-A or USB-A to micro-USB connections. I am wondering if this suggests potential hardware issues, possibly with the module connection to the carrier board.

Check scripts/kernel_flash/README_initrd_flash.txt Workflow 4

JP version will be downloaded based on BSP version automatically.

  • It’s fine use SD card or SSD, but common use case using larger size ssd to build some llm in jetson container
  • Check scripts/kernel_flash/README_initrd_flash.txt Workflow 4

Please change other cable which supports data transfer to cross check whether the issue exist.

Thanks

Hello, I have attempted majority of the steps. I am currently having issues when forcing it into recovery mode. This carrier board does not have reset/power buttons. I have tried the manual force recovery (with the FC REC and GND pins )and the device is not read by my host PC. I have tried several different cable connections.

kourt_ub20@KourtneyCPU:~$ lsusb
\Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hi,

Do you follow the official guide line to set the Xavier NX in recovery mode?

Thanks

Yes I did and still no responses

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