Massflash in orin NX

Hi Nvidia!

We are using a custom board based on the Jetson Orin NX module, running JetPack 6.2, which includes Jetson Linux 36.4.3 (Kernel 5.15) and an Ubuntu 22.04 root file system.
we tried massflash using command
sudo BOARDID=3767 BOARDSKU=0001 FAB=300 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml -p ‘-c ./bootloader/generic/cfg/flash_t234_qspi.xml’ --flash-only --showlogs --network usb0 --massflash 2 jetson-orin-nano-devkit nvme0n1p1

But it fails.
flash_3-1_1_20250704-121517.log (3.3 KB)
Could you suggest a better method to do the massflash?

Hello,

Thanks for visiting the NVIDIA Developer forums.

Your topic will be best served in the Jetson category, I have moved this post for better visibility.

Cheers,
Tom

Hi,

Please refer to below topics to check first.

Thanks

Hi David,

Although we successfully mass-flash two devices using the mentioned command, we had encountered a flash failure earlier.

Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for device to expose ssh …Waiting for device to expose ssh …Timeout
Cleaning up…

log :
flash_1-1_0_20250711-105248.log (6.2 KB)

However, this device was successfully flashed once the Ethernet cable was connected during the mass flashing process.
How did the device get flashed after connecting the Ethernet cable?

The time taken to mass flash two devices was approximately 10 minutes and 27 seconds, which is similar to the time taken when flashing them individually. Is this the expected behaviour?

Hi David,

Could you please confirm whether the mass-flashing process is sequential, and whether it has any dependencies on the build or the number of units being flashed simultaneously?

We observed that it takes around 5 minutes to flash one device and about 10 minutes for two devices(is this the expected behaviour).

why is a separate build required based on the number of devices to be mass-flashed?

We have noticed that the image size increases as the number of target devices increases.Could you clarify the reason for this and whether it’s expected?

Hi abdul.sabiq,

We noticed your massflash commands look different from official doc.

Take Orin NX for example

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 --no-flash --massflash <x> \
  -c  tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal

Then

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash <x> --showlogs --network usb0

Thanks

Hi David,
Thank you for your comment and additionally may i know :
Is the mass-flash process sequential for each device?
Will the total time taken to mass-flash multiple devices be the same as flashing them individually, or should we expect any time optimisation?
We have observed that the build image size increases with the number of devices selected for mass-flashing. Is there a known dependency between the number of devices and the build image size?

Hi,

Are you using the mentioned commands to mass flash your device?
They are supposed to flash your device in parallel.

Thanks

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