Jetson Orin Nano massflush

Hi All,
I produce image backups using this command.
./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b -c jetson-orin-nano-devkit

Produce image packages through this command.
./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --network usb0 --massflash 1 jetson-orin-nano-devkit nvme0n1

An error occurs during batch burning.
./tools/kernel_flash/l4t_initrd_flash.sh -c ./tools/kernel_flash/flash_l4t_nvme.xml --external-device nvme0n1p1 --flash-only --massflash 1 --network usb0

/home/linkdome/ORIN/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --network usb0 --usb-instance 1-1 --device-instance 0 --flash-only --network usb0 jetson-orin-nano-devkit nvme0n1
**********************************************
*                                            *
*  Step 1: Build the flashing environment    *
*                                            *
**********************************************
Create flash environment 0
/home/linkdome/ORIN/Linux_for_Tegra/bootloader /home/linkdome/ORIN/Linux_for_Tegra
/home/linkdome/ORIN/Linux_for_Tegra
Finish creating flash environment 0.
****************************************************
*                                                  *
*  Step 2: Boot the device with flash initrd image *
*                                                  *
****************************************************
/home/linkdome/ORIN/Linux_for_Tegra/temp_initrdflash/bootloader0 /home/linkdome/ORIN/Linux_for_Tegra
./tegraflash.py --bl uefi_jetson_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev  --bldtb tegra234-p3767-0004-p3768-0000-a0.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --cmd "rcmboot"  --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt  --bins "psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0004-3509-a02_with_odm_sigheader.dtb.encrypt; sce_fw camera-rtcpu-sce_sigheader.img.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3767-0004-p3768-0000-a0.dtb"    --bct_backup  --ramcode 4  --instance 1-1
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 

 Entering RCM boot

[   0.0223 ] rcm boot with presigned binaries
[   0.0232 ] tegrarcm_v2 --instance 1-1 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   0.0239 ] BR_CID: 0x80012344705DD5221000000014FD8140
[   0.0303 ] Sending bct_br
[   0.0358 ] Sending mb1
[   0.0363 ] Sending psc_bl1
[   0.0475 ] Sending bct_mb1
[   0.0538 ] Generating blob for T23x
[   0.0554 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[   0.0560 ] The number of images in blob is 18
[   0.0562 ] blobsize is 82509710
[   0.0563 ] Added binary blob_uefi_jetson_with_dtb_sigheader.bin.encrypt of size 3186752
[   0.0820 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 375168
[   0.0827 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 190592
[   0.0829 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 277312
[   0.0831 ] Not supported type: mb2_applet
[   0.0832 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 437264
[   0.0835 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[   0.0838 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 9097216
[   0.0877 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[   0.0898 ] Added binary blob_bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt of size 1027008
[   0.0903 ] Added binary blob_tegra234-bpmp-3767-0004-3509-a02_with_odm_sigheader.dtb.encrypt of size 199936
[   0.0906 ] Added binary blob_camera-rtcpu-sce_sigheader.img.encrypt of size 166304
[   0.0909 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 540000
[   0.0911 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 401008
[   0.0914 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[   0.0916 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1288096
[   0.0919 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[   0.0921 ] Added binary blob_boot0.img of size 64235520
[   0.1249 ] Added binary blob_tegra234-p3767-0004-p3768-0000-a0.dtb of size 347086
[   0.1857 ] tegrarcm_v2 --instance 1-1 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[   0.1864 ] BL: version 1.4.0.4-t234-54845784-e89ea9bc last_boot_error: 0
[   0.2971 ] Sending bct_mem
[   0.3046 ] Sending blob
[   3.4389 ] RCM-boot started

/home/linkdome/ORIN/Linux_for_Tegra
***************************************
*                                     *
*  Step 3: Start the flashing process *
*                                     *
***************************************
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 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 ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
blockdev: cannot open /dev/mmcblk0boot0: No such file or directory
[ 0]: l4t_flash_from_kernel: Serial Number: 1421523004146
[ 0]: l4t_flash_from_kernel: Starting to create gpt for emmc
Active index file is /mnt/internal/flash.idx
Number of lines is 3
max_index=2
writing item=1, 1:3:primary_gpt,0,20480,gptmbr.img,20480,fixed-<reserved>-0,5b366548ad9b193ad79289d31b9a84dd7a8fe3c4
Error: Could not stat device /dev/mmcblk0 - No such file or directory.
Flash failure
Cleaning up...

Because this involves backing up and restoring the camera, the mfi_jetson-orin-nano-devkit directory and tar package will be generated. However, even when I run the command in this directory (/home/linkdome/ORIN/Linux_for_Tegra/mfi_jetson-orin-nano-devkit), the same error still occurs.
Regrads,

Hi,
For information, do you use Jetpack 6.1?

Hi DaneLLL,
It’s Jetpack 5.1.2.

Hi,
Please apply this:

Jetson/L4T/r35.4.x patches - eLinux.org
[Massflash] Create massflash packages with images backed up from external devices

Hi DaneLLL,
I modified l4t_flash_from_kernel.sh yesterday. It successed.

mmcblk0boot0="${MMCBLKB0:-mmcblk0boot0}"
mmcblk0boot1="${MMCBLKB1:-mmcblk0boot1}"
maxcount=60
# mmcblk0="${MMCBLK0:-mmcblk0}"
mmcblk0="nvme0n1"
function fill_device_map
{
        if [[ "${host_mode}" = "0" ]]; then
                return 0
        fi
        device_map["${mmcblk0}"]="nvme0n1"
        device_map["${mmcblk0boot0}"]="nvme0n1boot0"
        device_map["${mmcblk0boot1}"]="nvme0n1boot1"
        if [ -n "${external_device}" ]; then
                device_map["${external_device}"]="${external_device_on_target}"
        fi
}

At the same time, copy the file to the tools/kernel_flash/images/, and the recovery will be successful.

I set up a new JetPack 5.1.2 image flashing environment on another PC running Ubuntu 20.04. However, when running the final step to flash the image, it keeps throwing an error. Unplugging and re-plugging the cable does not help.

**********************************************
*                                            *
*  Step 1: Build the flashing environment    *
*                                            *
**********************************************
Create flash environment 0
/home/mi/Orin/Linux_for_Tegra/mfi_jetson-orin-nano-devkit/bootloader /home/mi/Orin/Linux_for_Tegra/mfi_jetson-orin-nano-devkit
/home/mi/Orin/Linux_for_Tegra/mfi_jetson-orin-nano-devkit
Finish creating flash environment 0.
****************************************************
*                                                  *
*  Step 2: Boot the device with flash initrd image *
*                                                  *
****************************************************
/home/mi/Orin/Linux_for_Tegra/mfi_jetson-orin-nano-devkit/temp_initrdflash/bootloader0 /home/mi/Orin/Linux_for_Tegra/mfi_jetson-orin-nano-devkit
./tegraflash.py --bl uefi_jetson_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev  --bldtb tegra234-p3767-0000-p3768-0000-a0.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --cmd "rcmboot"  --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt  --bins "psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sigheader.dtb.encrypt; sce_fw camera-rtcpu-sce_sigheader.img.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3767-0000-p3768-0000-a0.dtb"    --secondary_gpt_backup  --bct_backup  --instance 1-4
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 

 Entering RCM boot

[   0.1282 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[   0.1282 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[   0.1282 ] rcm boot with presigned binaries
[   0.1309 ] tegrarcm_v2 --instance 1-4 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   0.1335 ] BR_CID: 0x80012344705DD5221000000014FD8140
[   0.1442 ] Sending bct_br
[   0.1513 ] Sending mb1
[   0.1517 ] Sending psc_bl1
[   0.1631 ] Sending bct_mb1
[   0.1695 ] Generating blob for T23x
[   0.1721 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[   0.1730 ] The number of images in blob is 18
[   0.1734 ] blobsize is 82078827
[   0.1736 ] Added binary blob_uefi_jetson_with_dtb_sigheader.bin.encrypt of size 2924608
[   0.2077 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 375168
[   0.2085 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 190592
[   0.2090 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 277312
[   0.2094 ] Not supported type: mb2_applet
[   0.2096 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 438768
[   0.2102 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[   0.2107 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 9097216
[   0.2151 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[   0.2171 ] Added binary blob_bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt of size 1051136
[   0.2180 ] Added binary blob_tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sigheader.dtb.encrypt of size 258688
[   0.2186 ] Added binary blob_camera-rtcpu-sce_sigheader.img.encrypt of size 166304
[   0.2191 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 537952
[   0.2196 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 400864
[   0.2201 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[   0.2205 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1127568
[   0.2210 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[   0.2214 ] Added binary blob_boot0.img of size 64145408
[   0.2580 ] Added binary blob_tegra234-p3767-0000-p3768-0000-a0.dtb of size 346795
[   0.3198 ] tegrarcm_v2 --instance 1-4 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[   0.3207 ] BL: version 1.2.0.0-t234-54845784-562369e5 last_boot_error: 0
[   0.4146 ] Sending bct_mem
[   0.4467 ] Sending blob
[   0.5441 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-4 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Cleaning up...

Hi,
Would like to confirm the status. So now you are able to clone the image from NVMe SSD storage. But cannot flash it to Orin Nano developer kit. Is this correct?

Hi DaneLLL,
I’m sorry. Maybe I didn’t express myself clearly. Now I can successfully perform backup and recovery operations on a PC Ubuntu 20.04.

./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b -c jetson-orin-nano-devkit
./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --network usb0 --massflash 1 jetson-orin-nano-devkit nvme0n1
cd mfi_jetson-orin-nano-devkit/
./tools/kernel_flash/l4t_initrd_flash.sh -c ./tools/kernel_flash/flash_l4t_nvme.xml --external-device nvme0n1p1 --flash-only --massflash 1 --network usb0

Executing the above command can back up and clone a device to flash to another device.


Then I was on another PC Ubuntu 20.04 Built a Jetpack 5.1.2 flash environment.

./tools/kernel_flash/l4t_initrd_flash.sh -c ./tools/kernel_flash/flash_l4t_nvme.xml --external-device nvme0n1p1 --flash-only --massflash 1 --network usb0

Executing the above command resulted in an error.

[   0.4146 ] Sending bct_mem
[   0.4467 ] Sending blob
[   0.5441 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-4 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Cleaning up...

I also tried plugging and unplugging the Type-C cable for this issue. It cannot solve this problem either.
Do you understand my description?

Hi,
So you have two PCs Ubuntu 20.04. Both have Jetpack 5.1.2. On one PC, the steps can be executed successfully. On the other PC, it cannot flash the Orin Nano developer kit. Is this correct?

Hi DaneLLL,
Yes. I only realized yesterday that it was because the contents of the bootloader directory were incorrect. The command to simultaneously produce the flashcmd. txt file is also incorrect.

./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --network usb0 --massflash 1 jetson-orin-nano-devkit nvme0n1

I use the command above. This command comes from Linux_for_Tegra/tools/backup-restore/README_backup-restore.txt

The correct flashcmd. txt file content for production should be:

./tegraflash.py --bl uefi_jetson_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev  --bldtb tegra234-p3767-0004-p3768-0000-a0.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --cmd "rcmboot"  --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt  --bins "psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0004-3509-a02_with_odm_sigheader.dtb.encrypt; sce_fw camera-rtcpu-sce_sigheader.img.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot.img; kernel_dtb tegra234-p3767-0004-p3768-0000-a0.dtb"    --bct_backup  --ramcode 4 

But now the content of flashcmd.txt is incorrect. The content is:

./tegraflash.py --bl uefi_jetson_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev  --bldtb tegra234-p3767-0000-p3768-0000-a0.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --cmd "rcmboot"  --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt  --bins "psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sigheader.dtb.encrypt; sce_fw camera-rtcpu-sce_sigheader.img.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot.img; kernel_dtb tegra234-p3767-0000-p3768-0000-a0.dtb"    --bct_backup

I am currently searching for the cause of this issue.

1 Like

Hi DaneLLL,
./tools/kernel_flash/l4t_initrd_flash.sh -c ./tools/kernel_flash/flash_l4t_nvme.xml --external-device nvme0n1p1 --flash-only --massflash 1 --network usb0 This command does not burn my backed up file system to the hard drive. Please tell me what I should do. I have tried many times already.
flash_1-1_0_20250107-223506.log (8.1 KB)

Hi,
Here are commands for AGX Orin + rootfs on NVMe SSD:
Use Custom Rootfs for Nvme SSD for mass flashing - #6 by makkalot

Please replace flash_l4t_nvme.xml with flash_l4t_external.xml and try again.

Hi DaneLLL,

./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b -c jetson-orin-nano-devkit

./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --network usb0 --massflash 1 jetson-orin-nano-devkit nvme0n1

./tools/kernel_flash/l4t_initrd_flash.sh -c ./tools/kernel_flash/flash_l4t_external.xml --external-device nvme0n1p1 --flash-only --massflash 1 --network usb0

I modified the XML file in my own command. Not successful.

sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b -c jetson-orin-nano-devkit

sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --use-backup-image --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_external.xml  --showlogs  jetson-orin-nano-devkit nvme0n1p1

sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_external.xml  --showlogs  jetson-orin-nano-devkit nvme0n1p1

I executed this command once, but the result was the same. The log output has not changed much either. The file system still hasn’t been burned to the hard drive.

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p "-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1

This command can be used successfully without using a backup image.

sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --use-backup-image --external-device nvme0n1p1 -p "-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1

sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --external-device nvme0n1p1 -p "-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml  --showlogs  jetson-orin-nano-devkit nvme0n1p1
[flash_1-12_0_20250108-190606.log|attachment](upload://507UkZL44dvAXjW56qYIEYovlK0.log) (8.5 KB)

So I replaced the parameters I wanted to change, but still couldn’t succeed.
The file system ultimately did not burn to the hard drive.

flash_1-12_0_20250108-190606.log (8.5 KB)

Hi,
Could you please try Jetpack 6.1? The function is fully ready on Jetpack 6… Would like to confirm if you are able to do this successfully in your environment.