Basic Flashing#
Before You Begin#
The following directories must be present:
bootloader: Bootloader plus flashing tools, such as TegraFlash, CFG, and BCT.kernel: A kernel image/Image, DTB files, and kernel modules.rootfs: The root file system that you downloaded. This directory starts empty. You populate it with the sample file system.nv_tegra: User space binaries and sample applications.
Additionally, before running these commands, you must use a USB cable to connect your host computer to the Jetson device’s recovery port.
Initrd flash requires a high-quality USB-C or micro-USB cable. A low-quality cable might make the flashing process fail.
To install the correct dependencies, run the following script:
$ sudo tools/l4t_flash_prerequisites.sh # For Debian-based Linux
Flashing in Two Phases#
Flashing a Jetson device can be performed in two phases:
QSPI-only flashing phase writes the bootloader and UEFI firmware to the device’s QSPI-NOR flash memory. It does not write the operating system, but it is a prerequisite for the second phase, which relies on the QSPI bootloader to start the installer. Refer to QSPI-Only Flashing.
Mass-storage flashing phase boots the installer and installs the operating system and root file system to the device’s main storage, such as eMMC, NVMe, or an SD card. You can perform this phase in either of two ways:
Install using USB: Write the installer ISO image to a USB drive and boot the device from it. This method does not require a network server. Refer to Installing from an ISO Image on a USB Drive.
Install using HTTP: Boot the installer ISO image over the network using UEFI HTTPv4, without writing it to a USB drive. Refer to Installing from an ISO Image on the Network.
QSPI-Only Flashing#
QSPI-only flashing is the first phase of the two-phase flashing process described in Flashing in Two Phases. It writes only the bootloader and UEFI firmware to the device’s QSPI-NOR flash memory; it does not write the operating system. It is a prerequisite for the ISO installation phase, which relies on the QSPI bootloader to start the installer.
This phase has two steps: build the QSPI tarball on an x86-64 Linux build machine, and then flash the QSPI image to the device from the host.
Prerequisites:
An x86-64 Linux build machine.
The NVIDIA sample root file system, or a root file system that you provide.
A USB connection to the Jetson device is not required to build the QSPI tarball.
Building the QSPI Tarball#
Download and install the BSP package
Jetson_Linux_R39.2.2_aarch64.tbz2.Install the NVIDIA sample file system to the
Linux_for_Tegra/rootfsdirectory.Go to the
Linux_for_Tegradirectory and generate the QSPI image in either online or offline mode.Online mode requires the board to be connected and in recovery mode:
$ sudo ./tools/qspi_flash/generate_qspi_for_flash.sh <board-name>
Offline mode does not require a connected board; specify the board identity with environment variables:
$ sudo BOARDID=<BOARDID> FAB=<FAB> BOARDSKU=<BOARDSKU> CHIP_SKU=<CHIP_SKU> ./tools/qspi_flash/generate_qspi_for_flash.sh <board-name>
To find the values for
BOARDID,FAB,BOARDSKU, andCHIP_SKU, refer to Generating a Flash Image Without a Device Connected (Offline Mode).
The script creates the tarball in the following location:
generic_release_aarch64/Linux_for_Tegra/host_tegraflash_R39.2.2.tbz2
Flashing the QSPI Image from the Host#
Extract the tarball:
$ tar -xvf host_tegraflash_R39.2.2.tbz2
Flash the QSPI image to the device by one of the following methods:
Put the board into recovery mode manually, and then run the following command:
$ sudo hostflash/host_flash_qspi.sh
Pass
-bto thehost_flash_qspi.shscript to use theboardctltool to put the board into recovery mode:$ cd Linux_for_Tegra $ sudo ./hostflash/host_flash_qspi.sh -b
Options for Building the QSPI Tarball#
To generate a QSPI tarball for a different board configuration, or to sign and encrypt the image for an ODM-fused (Secure Boot) board, pass additional options to generate_qspi_for_flash.sh:
Usage: [env={value},...] generate_qspi_for_flash.sh [[-u <PKC key file>] [-v <SBK key file>]] [-p <options>] [-f <flash-mode>] <board-name>
The options are as follows:
-u <PKC key file>: PKC key used for an ODM-fused board.-v <SBK key file>: Secure Boot key (SBK) used for an ODM-fused board.-p <options>: Options passed directly toflash.sh.-f,--flash-mode <mode>: Flash host type. The options areLinux,BMC, andWindows; the default isLinux.
For the full list of options and per-board examples, run the following command:
$ sudo ./tools/qspi_flash/generate_qspi_for_flash.sh -h
Mass-Storage Flashing#
Mass-storage flashing is the second phase of the two-phase flashing process described in Flashing in Two Phases. It boots the installer and installs the operating system and root file system to the device’s main storage. You can install from an ISO image on a USB drive or from an ISO image on the network.
Installing from an ISO Image on a USB Drive#
You can perform the ISO installation phase by writing the installer ISO image to a USB drive and booting the Jetson device from it. Unlike network installation, this method does not require a DHCP or HTTP server; it requires only a host computer to prepare the USB drive, a display, and a keyboard.
Prerequisites:
A host computer running Windows, macOS, or Linux, with at least 25 GB of free storage.
A USB flash drive with a capacity of 16 GB or more.
Preparing the Bootable USB Drive#
Download the Jetson installer ISO image from the JetPack download page.
Important
The ISO image downloaded from the JetPack download page is not signed by UEFI keys nor encrypted. Therefore, the QSPI image generated in the QSPI-only flashing phase must not include UEFI signing or encryption—do not pass
--uefi-keysor--uefi-encin the-p <options>argument togenerate_qspi_for_flash.sh.Write the ISO image to the USB drive with a disk-imaging tool such as balenaEtcher:
Install and launch balenaEtcher.
Select the downloaded ISO image.
Select the USB drive as the destination.
Start the write operation.
Note
You cannot install the image by copying the ISO file to the USB drive with a file manager. Use a disk-imaging tool that writes the image to the raw device.
Booting and Installing from the USB Drive#
Connect a display, a USB keyboard, and a USB mouse to the Jetson device.
Insert the bootable USB drive into a USB Type-A or USB Type-C port, connect the power supply, and power on the device.
The device should boot from the USB drive automatically. If it does not, select the USB drive as the boot device:
Press Esc repeatedly during the NVIDIA logo screen to enter the UEFI menu.
Go to Boot Manager and move the USB drive to the top of the boot order.
Save the change and exit.
When the installer boot menu appears, select the install option for your target storage device, such as NVMe, eMMC, or an SD card.
Important
The installer erases the target storage device. Be sure to select the correct device.
The installer writes the operating system to the target device. This process takes approximately 10 minutes, after which the device reboots.
Before the device boots again, remove the USB drive. Otherwise, the device boots from the USB drive instead of from the newly installed system.
Complete the initial configuration with
oem-config.
Installing from an ISO Image on the Network#
This section assumes that you understand how to set up your network and the configuration requirements.
The UEFI firmware on Jetson supports UEFI HTTPv4. With UEFI HTTPv4, the UEFI firmware downloads a bootable ISO image from an HTTP server over the network, registers it as a RAM disk, and boots it as if it were a locally attached USB drive or CD-ROM. This lets you boot and install an ISO image, such as the Jetson installer ISO, entirely over the network without writing it to a USB drive.
Unlike PXE boot, UEFI HTTPv4 does not require a TFTP server or an NFS server. It uses only two components:
DHCP server: Provides the IP address information and the URL of the ISO image to download.
HTTP server: Hosts the ISO image.
Important
UEFI HTTPv4 boot requires a Jetson device with at least 16 GB of RAM. Because the UEFI firmware downloads the entire ISO image into memory and boots it as a RAM disk, the device must have enough RAM to hold the image and run the installer.
A Jetson device with less than 16 GB of RAM (for example, an 8 GB module) cannot use this method. On such devices, install from a USB drive instead (refer to Installing from an ISO Image on a USB Drive), or use PXE boot with an NFS root file system, so that the image is not loaded entirely into memory.
Setting Up the DHCP Server#
The DHCP server must be configured to return the ISO image URL to UEFI HTTPv4 clients. This section provides a sample configuration for the isc-dhcp-server package on an Ubuntu host. Modify it to match your network configuration.
A UEFI HTTPv4 client identifies itself with a vendor class identifier that begins with HTTPClient. The DHCP server must match on this identifier and echo the HTTPClient vendor class identifier back to the client; otherwise the UEFI firmware ignores the response. The filename option must be set to the full HTTP URL of the ISO image.
Note
Replace <jetson-installer>.iso with the actual filename of the ISO image downloaded from the JetPack download page. The filename includes the version and a build timestamp; for example, jetsoninstaller-r39.2.0-2026-05-28-03-43-24-arm64.iso.
Sample configuration:
# /etc/dhcp/dhcpd.conf
authoritative;
default-lease-time 600;
max-lease-time 7200;
class "httpclients" {
match if substring (option vendor-class-identifier, 0, 10) = "HTTPClient";
# Required: echo the HTTPClient vendor class identifier back to the client.
option vendor-class-identifier "HTTPClient";
# The full URL of the ISO image hosted on the HTTP server.
filename "http://192.168.0.1/<jetson-installer>.iso";
}
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.11 192.168.0.20;
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
}
Set the interface that the DHCP server listens on in /etc/default/isc-dhcp-server:
INTERFACESv4="<interface>"
<interface> is the host network interface connected to the Jetson device. Assign a static IP address in the configured subnet (for example, 192.168.0.1) to this interface so that the URL in the filename option is reachable.
Validate the configuration and start the server:
$ sudo dhcpd -t -cf /etc/dhcp/dhcpd.conf
$ sudo systemctl restart isc-dhcp-server
$ sudo systemctl enable isc-dhcp-server
Setting Up the HTTP Server#
Host the ISO image on any HTTP server reachable at the URL configured in the filename option. For a simple setup, you can serve the directory that contains the ISO image with Python:
$ cd <directory containing the ISO image>
$ sudo python3 -m http.server 80 --bind 192.168.0.1
The URL path in the filename option is relative to the directory from which the HTTP server is started. With preceding command, the file <jetson-installer>.iso in the served directory is available at http://192.168.0.1/<jetson-installer>.iso.
Before you boot the Jetson device, verify that the image is reachable:
$ curl -sI http://192.168.0.1/<jetson-installer>.iso
The response should report 200 OK and the Content-Length of the ISO image.
Note
The Python http.server module is single-threaded and is suitable only for occasional use. For repeated use, host the ISO image with a dedicated web server such as Apache or nginx.
Enabling UEFI HTTPv4 on the Jetson Device#
After you finish configuring the DHCP and HTTP servers:
Reboot the Jetson device and press Esc during boot time to access the UEFI menu.
Confirm that a RAM Disk Configuration entry is present under Device Manager. Its presence indicates that the UEFI firmware can boot an ISO image from a RAM disk.
Return to the Boot Manager menu. A UEFI HTTPv4 boot option appears for the network device.
Select the UEFI HTTPv4 option for the network device that is connected to the DHCP and HTTP server.
The following example shows the Boot Manager menu, which lists the UEFI HTTPv4 boot option:
/------------------------------------------------------------------------------\
| Boot Manager |
\------------------------------------------------------------------------------/
Device Path :
Boot Manager Menu VenHw(1E5A432C-0466-4D
31-B009-D4D9239271D3)/
UEFI WDS250G3X0C-00SJG0 195045803046 1 MemoryMapped(0xB,0x141
UEFI PXEv6 (MAC:48B02DB7EAB9) 60000,0x1417FFFF)/PciR
UEFI PXEv4 (MAC:48B02DB7EAB9) oot(0x0)/Pci(0x0,0x0)/
UEFI HTTPv6 (MAC:48B02DB7EAB9) Pci(0x0,0x0)/NVMe(0x1,
UEFI Shell F8-A1-93-46-8B-44-1B-0
UEFI HTTPv4 (MAC:48B02DB7EAB9) 0)
Use the <^> and <v> keys to choose a boot option,
the <Enter> key to select a boot option, and the
<Esc> key to exit the Boot Manager Menu.
/------------------------------------------------------------------------------\
| |
| ^v=Move Highlight <Enter>=Select Entry Esc=Exit |
\------------------------------------------------------------------------------/
The UEFI firmware obtains an IP address and the ISO image URL from the DHCP server, downloads the ISO image over HTTP, registers it as a RAM disk, and boots it. The boot menu of the ISO image then appears, the same as when you boot from a USB drive:
GNU GRUB version 2.12
/----------------------------------------------------------------------------\
|*Install Jetson ISO R39.2.2 |
| Boot from next volume |
| UEFI Firmware Settings |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\----------------------------------------------------------------------------/
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
Select Install Jetson ISO R39.2.2 to continue. A menu for selecting the installation target device then appears:
GNU GRUB version 2.12
/----------------------------------------------------------------------------\
|*Install on NVMe |
| Install on USB |
| Install on eMMC (for AGX Orin) |
| Install on microSD (for AGX Orin, Orin Nano/NX) |
| Boot Into Rescue Shell |
| Check Disc for Defects |
| |
| |
| |
| |
| |
| |
\----------------------------------------------------------------------------/
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line. ESC to return previous
menu.
Before you select which device to install the operating system to, press e and then edit the GRUB command:
GNU GRUB version 2.12
/----------------------------------------------------------------------------\
|setparams 'Install on NVMe' |
| |
| linux /casper/Image autoinstall fsck.mode=skip force-bootdisk=nvme0\|
|n1 mminit_loglevel=4 clk_ignore_unused pd_ignore_unused firmware_class.path\|
|=/etc/firmware fbcon=map:0 nospectre_bhb efi=runtime rd.driver.blacklist=no\|
|uveau nouveau.modeset=0 cloud-init=disabled loglevel=debug subiquity.debug |
| initrd /casper/initrd |
| |
| |
| |
| |
| |
| |
\----------------------------------------------------------------------------/
Append root=/dev/ram0 ramdisk_size=1500000 ip=dhcp url=<jetson-iso-http-url> to the end of the linux /casper/Image ... line, where <jetson-iso-http-url> is the URL of the ISO image on your HTTP server (the same URL set in the DHCP filename option). These parameters tell the kernel to use a RAM disk, obtain a network address by DHCP, and download the ISO image from the HTTP server.
The edited GRUB command is shown in the following example. Replace <jetson-installer>.iso in the url= parameter with the actual filename of the ISO image downloaded from the JetPack download page:
GNU GRUB version 2.12
/----------------------------------------------------------------------------\
|setparams 'Install on NVMe' |
| |
| linux /casper/Image autoinstall fsck.mode=skip force-bootdisk=nvme0\|
|n1 mminit_loglevel=4 clk_ignore_unused pd_ignore_unused firmware_class.path\|
|=/etc/firmware fbcon=map:0 nospectre_bhb efi=runtime rd.driver.blacklist=no\|
|uveau nouveau.modeset=0 cloud-init=disabled loglevel=debug subiquity.debug \|
|root=/dev/ram0 ramdisk_size=1500000 ip=dhcp url=http://192.168.0.1/<jetson-\|
|installer>.iso |
| initrd /casper/initrd |
| |
| |
| |
| |
\----------------------------------------------------------------------------/
Minimum Emacs-like screen editing is supported. TAB lists
completions. Press Ctrl-x or F10 to boot, Ctrl-c or F2 for a
command-line or ESC to discard edits and return to the GRUB menu.
Press Ctrl+X or F10 to boot. The installer downloads the ISO image, installs the operating system to the selected device, and reboots.
Flashing by Using a Convenient Script#
NVIDIA provides a convenient flashing script that automatically detects the Jetson device’s type of carrier board:
$ sudo ./nvsdkmanager_flash.sh [--storage <storage> ]
The value of <storage> can be nvme0n1p1 or nvme1n1p1 for flashing to an external NVMe SSD, sda1 for flashing to an external USB storage drive, or mmcblk0p1 or mmcblk1p1 for flashing to an external SD card, depending on the target device.
Without --storage option, the Jetson device’s default storage is flashed.