Error when attempting to create a Backup Image for Jetson Orin Nano Super DevKit

Hi I am trying to create a backup image for the Jetson Orin Nano Board from Jetpack 6.2.1. I am using the guide and the read me file inside the Linux_for_tegra in the backuup_restore folder. I have followed all the instructions but when I try to run the script it gives me an error saying its an invalid board name. Please help

lidc@SDL3:~/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/backup_restore$ sudo ./l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit
Please install the Secureboot package to use initrd flash for fused board

Entry added by NVIDIA initrd flash tool

/home/lidc/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1(rw,nohide,insecure,no_subtree_check,async,no_root_squash)
rpcbind: another rpcbind is already running. Aborting
Export list for localhost:
/home/lidc/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1
16:16:55.763 - Debug: Checking UFW status and NFS port rules…
16:16:55.798 - Debug: UFW is not active. NFS port is accessible.
16:16:55.799 - Debug: Checking VPN connections…
16:16:55.801 - Debug: IPSec service is not running.
16:16:55.802 - Debug: VPN routes none in tun|tap|ppp|vpn|gpd.
16:16:55.803 - Debug: No VPN connection detected.
/home/lidc/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --initrd --showlogs jetson-orin-nano-devkit internal


  •                                    *
    
  • Step 1: Generate rcm boot commandline *
  •                                    *
    

ROOTFS_AB= ROOTFS_ENC= /home/lidc/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/flash.sh --no-flash --rcm-boot jetson-orin-nano-devkit mmcblk0p1
Error: Invalid target board - jetson-orin-nano-devkit.

Usage: sudo ./flash.sh [options] <target_board>
Where,
target board: Valid target board name or ‘autodetect’
rootdev: Proper root device.
options:
-c ---------- Flash partition table config file.
-d ---------- device tree file.
-f --------- Path to flash application (tegraflash.py)
-h -------------------- print this message.
-i – key for disk encryption support.
-k ----- partition name or number specified in flash.cfg.
-m ------ MTS preboot such as mts_preboot_si.
-n --------- Static nfs network assignments
:::
-o ---------- ODM data.
-r -------------------- skip building and reuse existing system.img.
-t -------- tegraboot binary such as nvtboot.bin
-u ------ PKC key used for odm fused board.
-v ------ Secure Boot Key (SBK) key used for ODM fused board.
-w ---------- warm boot binary such as nvtbootwb0.bin
-x ---------- Tegra CHIPID.
-B ---------- BoardId.
-C ---------- Kernel commandline arguments.
WARNING:
Each option in this kernel commandline gets
higher preference over the values set by
flash.sh. In case of NFS booting, this script
adds NFS booting related arguments, if -i option
is omitted.
-F ---------- Flash server such as cboot.bin.
-G -------- Read partition and save image to file.
-I ----------- initrd file. Null initrd is default.
-K ----------- Kernel image file such as zImage or Image.
-L ------- Bootloader such as cboot.bin or u-boot-dtb.bin.
-M --------- MTS boot file such as mts_si.
-N ---------- i.e. :/my/exported/nfs/rootfs.
-R ------- Sample rootfs directory.
-S ------------- Rootfs size in bytes. Valid only for internal
rootdev. KiB, MiB, GiB short hands are allowed,
for example, 1GiB means 1024 * 1024 * 1024 bytes.
-T —The number of the sectors of the external storage device.
The default value is 119537664 if this option is not set.
-U —The number of the sectors of the internal storage device.
The default value is 119537664 if this option is not set.
-Z -------------------- Print configurations and then exit.
–no-flash ------------ perform all steps except physically flashing the board.
This will create a system.img.
If combined with --rcm-boot, the command will generate rcmboot_blob.
If combined with --read-info, the command will generate readinfocmd.txt.
–external-device------ Generate flash images for external devices
–sparseupdate--------- only flash partitions that have changed. Currently only support SPI flash memory
–no-systemimg -------- Do not create or re-create system.img.
–bup ----------------- Generate bootloader update payload(BUP).
–single-image-bup Generate specified single image BUP, this must work with --bup.
–bup-type ----- Generate specific type bootloader update payload(BUP), such as bl or kernel.
–multi-spec----------- Enable support for building multi-spec BUP.
–clean-up------------- Clean up BUP buffer when multi-spec is enabled.
–usb-instance — Specify the USB instance to connect to;
= USB port path (e.g. 3-14).
–no-root-check ------- Typical usage of this script require root permissions.
Pass this option to allow running the script as a
regular user, in which case only specific combinations
of command-line options will be functional.
–uefi-keys <keys_conf> Specify UEFI keys configuration file.
–rcm-boot ------------ Do RCM boot instead of physically flashing the board.
–sign ---------------- Sign images and store them under “bootloader/signed”
directory. The board will not be physically flashed.
–image --------------- Specify the image to be written into board.
–boot-chain-flash Flash only a specific boot chain (ex. "A, “B”, “all”).
Defaults to “all”, inputs are case insensitive.
Not suitable for production.
–boot-chain-select Specify booting chain (ex. “A” or “B”) after the board is flashed.
Defaults to “A”, inputs are case insensitive.
–pv-crt -------------- The certificate for the key that is used to sign cpu_bootloader
–with-systemimg ------ Generate system images also when using -k option
–pv-enc <enc_key>----- The encryption key that is used to encrypt cpu_bootloader.
–uefi-enc <uefi_enc_key> Key file (0x19: 16-byte; 0x23: 32-byte) to encrypt UEFI payloads
–uda-dir-------------- Directory to store user data that will be encrypted in UDA partition.
–generic-passphrase – Use generic passphrase for disk encryption.
–disable-random-iv — Disable generation of random IV, SALT1, SALT2 and DERSTR.
–read-info ----------- Read and display board related info, fuse info (based on fuse_t234.xml),
and EEPROM content.
–reuse-uuid --------- Reuse uuid which is already generated first time.
–qspi-only --------- Flash QSPI device only.
–read-ramcode ------- Generate read_ramcode script in the flashcmd.txt command script.
–gen-read-eeprom ---- Generate read_eeprom script with all signed binaries. User later can run
read_eeprom.sh from host to dump EEPROM content on a target device after
putting the target device in RCM mode. Since all binaries are signed already,
there is no key needed even the device has PKC fuse burned.
–debug -------------- Enable debug mode.
For now, the debug mode will enable saving of unencrypted and unsigned files
for UEFI encryption/signing debugging.
–hsm ---------------- Enable HSM for signing (and encrypting) images. This option must be used with
-u option (image signing). -v or --pv-enc is optional (image encryption).

Cleaning up…

hello ruthvick2005,

it seems you’re under an incorrect path.
please try moving to ~/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/, where has jetson-orin-nano-devkit.conf availabe.
and, please running backup/restore script for verificaiton.
for instance,
$ sudo ./tools/backup_restore/l4t_backup_restore.sh -b -e nvme0n1 jetson-orin-nano-devkit

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