Reference Manual#
Flashing Script Usage (l4t_initrd_flash.sh)#
This section provides detailed information about l4t_initrd_flash.sh command-line options and other aspects of l4t_initrd_flash.sh usage.
Option/Argument |
Description |
|---|---|
-u <PKC key file> |
PKC key used for ODM fused board. |
-v <SBK key file> |
SBK key used for encryption. |
-p <options> |
Pass specified options to |
-k <target_partition> |
Flash only the specified partition. |
-P <dir> |
Specify the output directory when generating a flash package for Jetson devices. |
-r |
Reuse the existing system image. |
<board-name> |
Specify the board to use. |
<rootdev> |
Specify the root device to use. |
--no-flash |
Generate the flash images. |
--flash-only |
Flash using existing images. |
--external-device <dev> |
Generate or flash images for the specified external storage device. If this is used, the |
--external-only |
Skip generating internal storage images. |
--usb-instance |
Specify the USB port where the flashing cable is connected (such as 1-3). |
--sparse |
Use sparse image to flash instead of tar image. |
-c <config file> |
The partition layout for the external storage device. |
-S <size> |
Size of the external APP partition in bytes. KiB, MiB, and GiB shorthand notation is allowed; for example, |
--massflash [<max_devices>] |
Flash multiple devices. Optionally specify |
--showlogs |
Spawn gnome-terminal to show individual flash process logs. Applicable for |
--reuse |
Reuse existing working environment kept by |
--keep |
Keep working environment instead of cleaning up after flashing. |
--erase-all |
Erase all storage devices before flashing. |
--initrd |
Stop after device boots into initrd. |
--network <netargs> |
Flash through Ethernet protocol using initrd flash.
|
--append |
Used only with
|
--direct <dev> |
Flash specified device directly connected to host. Example:
|
--with-systemimg |
Generate system image even when flashing individual partition. |
--pv-enc <key_file> |
The key to encrypt cpu_bootloader. |
--pv-crt <crt_file> |
The certificate for the key used to sign cpu_bootloader. |
-i <enc_rfs_key_file> |
Key for disk encryption support. |
--uefi-keys <keys_conf> |
Specify UEFI keys configuration file. |
--uefi-enc <uefi_enc_key> |
Key file (0x19: 16-byte; 0x23: 32-byte) to encrypt UEFI payloads. |
--odm-image-gen |
Generate ODM payload. |
--mass-storage-only |
Generate OEM payload for NVMe or eMMC. |
--qspi-only |
Generate or flash only the QSPI package. |
--profile |
Specify a chip mapping profile. |
--with-systemimg |
Generate system image even when flashing individual partition. |
--pv-enc <key_file> |
The key to encrypt cpu_bootloader. |
--pv-crt <crt_file> |
The certificate for the key used to sign cpu_bootloader. |
-i <enc_rfs_key_file> |
Key for disk encryption support. |
--ekb-pair |
Flash EKB that corresponds to the serial number of the target. |
--boot-rootfs |
Use flashing kernel initrd to mount |
--hsm |
Enable HSM for image signing/encryption. |
--read-ramcode |
Generate |
--no-root-check |
Skip root check. |
The -p option supports the following options:
Option |
Description |
|---|---|
-b <emc_bctfile> |
Use the specified emc_bct file. |
-c <cfgfile> |
Flash partition table config file. |
-e <bpmp_file> |
Use the specified bpmp file. |
-g <bpmp_dtb_file> |
Use the specified bpmp DTB file. |
-l <tbcdtbfile> |
CPU bootloader DTB file. |
-m <mts_preboot> |
MTS preboot, such as |
-o <odmdata> |
ODM data. |
-w <wb0boot> |
Warm boot binary, such as |
-L <bootloader> |
Bootloader, such as |
-M <mts_boot> |
MTS boot file, such as |
-U <int_num_sectors> |
The number of sectors of the internal storage device. Default is 119537664. |
--boot-chain-flash <c> |
Flash only the specified boot chain (such as |
--boot-chain-select <c> |
Specify boot chain (such as |
--reuse-uuid |
Reuse previously generated UUID. |
--passthrough |
Additional options to pass to the |
--debug |
Enable debug mode and |
The flash script supports some environment variables to override the default behavior.
Environment Variable |
Description |
|---|---|
EXTOPTIONS |
Flash options when generating flash image for external devices. Supports the same options as the |
FLASHING_KERNEL |
Defines the path of the initrd image used for running the flashing process. |
ERASE_QSPI |
Bricks the device when running with |
ADDITIONAL_DTB_OVERLAY_OPT |
Defines the path of the additional DTB overlay file. |
EXTOPTIONS supports the following options:
Option |
Description |
|---|---|
-d <dtbfile> |
Device tree file. |
-n <nfs_args> |
Static NFS network assignments: |
-r |
Skip building and reuse existing |
-C <cmdline> |
Kernel command-line arguments. WARNING: Each option gets higher preference over |
-N <nfsroot> |
NFS root path ( |
-R <rootfs_dir> |
Sample rootfs directory. |
-T <ext_num_sectors> |
Number of sectors of external storage device. |
-K <kernel> |
Kernel image file, such as zImage or Image. |
--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. |
--reuse-uuid |
Reuse previously generated UUID. |
--no-systemimg |
Do not create or re-create |
--passthrough |
Additional options to pass to the |
--debug |
Enable debug mode and |
Finding the USB Instance#
The l4t_initrd_flash.sh script supports the --usb-instance option to flash a specific Jetson device on a host that has multiple devices in recovery mode. This section provides information about determining which USB instance to use.
Place all devices in recovery mode.
Run the following command:
$ grep <idProduct> /sys/bus/usb/devices/*/idProduct
idProductis the USB ID for recovery mode of the device. For example,7023is for Jetson AGX Orin and7026is for Jetson Thor.The result is something like the following:
/sys/bus/usb/devices/1-1.1/idProduct:7026
1-1.1is the USB instance number you want to use to specify which device you want to flash.