Jetson Orin NX initializaition

I have working system with Jetson Orin NX. When I replace the Orin NX not new one, the ssytem is not opreational. It starts work only complete install by SDK manager. What is the right step to make new Oring NX operational without complete reinstall? Regards, Vladimir

Each Jetson module ships with no software pre-installed; you attach it to a carrier board designed or procured for your end product, and flash it with the software image you’ve developed.

Hi, please correct me if I make any mistake. As far I understand and what we are doing:

  • Image flash we do to the NVME disk in our system.
  • It is not required to flash any data to Orin Nx
  • After we flash software image to our system with Orin Nx module installed, I try to change Orin Nx module to new one. In this case the system doesn’t start.
  • Same system starts work with new image flash.
  • It take too long to flash new image each time. We clone the NVME disk for our product line.
  • The question is following: How can we speed up Orin Nx module initialization process ?
    Best regards, Vladimir

Hi,
In the module there’s QSPI for some system partitions, so the module has to be present while flashing the system. Flashing QSPI is a must-have step and it may take some time.

Hi, we want to produce same system in same configuration some hundreds times.
We clone disks and want to installl the new Orin Nx modules.
The problem is following: NEW ORIN NX module is not operational from very beginnging. We have to make complete installation of full system!
The questions:

  • How can we avoid complete image flash to our system?
  • How can we spead up and automate the process of system release?
    Vladimir.

Hi,

Two options for you:

  1. Apply this patch and make a massflash package with our backup/restore tool:
    Backup restore, workflow #3 massflash jetson orin nano problem - #5 by DaveYYY
    Refer to Linux_for_Tegra/tools/backup_restore/README_backup_restore.txt for more detail.
  2. Flash only the QSPI bootloader with this command. This should be much faster than flashing the entire disk.

sudo ./flash.sh --no-systemimg -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

Thanks, I’ll try.
Vladimir