HomeCompatibility › Jetson Orin Nano 4GB
Jetson Configuration Compatibility · Jetson Orin Nano 4GB

Jetson Orin Nano 4GB: 14 supported JetPack releases.

Method v1.0 · dataset 2026-09-07 · verified 2026-09-07 · last updated September 2026

JetPack 5.1.2 through 7.2.1. JetPack 7.0, 7.1 do not support this module. Power-mode presets: Jetson Orin Nano 4GB on the power-modes page.

Supported releases and compute stack

JetPackL4TCUDATensorRTcuDNNDeepStreamUbuntu
5.1.235.4.111.4.198.5.28.6.020.04
5.1.335.5.011.4.198.5.28.6.020.04
5.1.435.6.011.4.198.5.28.6.020.04
5.1.535.6.111.4.198.5.28.6.020.04
5.1.635.6.420.04
5.1.735.6.520.04
6.036.312.2.128.6.28.9.422.04
6.136.412.6.1010.3.09.3.07.122.04
6.236.4.312.6.1010.3.09.3.022.04
6.2.136.4.412.6.1010.3.09.3.022.04
6.2.236.5.022.04
6.2.336.5.222.04
7.239.213.2.110.16.29.20.024.04
7.2.139.2.113.2.110.16.29.20.024.04

Install methods

MethodJetPack rangeNotes
SDK Manager (host flash)allHost-driven flash from an x86 Ubuntu machine (or a Docker container per NVIDIA's SDK Manager Docker image). Only method that can flash the Super flash configuration and the JetPack 6.x/7.x QSPI-firmware bridge update; required to change flash configuration (e.g. move a non-Super Orin Nano to jetson-orin-nano-devkit-super).
ISO image (target-side)6.0+USB-stick installable image, flashed target-side (no x86 host required). Cannot upgrade a non-Super device to Super Mode (must reflash from an x86 host / SDK Manager, or hand-edit TNSPEC/COMPATIBLE_SPEC in /etc/nv_boot_control.conf). JetPack 7.2's ISO image is the sole install path for the Orin Nano Developer Kit now that the SD Card image is gone.
apt upgrade / OTAminor/point releases within the same major L4T line only (e.g. 6.0→6.2.x, 7.0→7.2.x)In-place `apt update && apt dist-upgrade` (or NVIDIA's OTA image mechanism) works only within the same L4T major version. Crossing a major boundary (5.x→6.x, 6.x→7.x) is unsupported and requires a full reflash because the bootloader/kernel/rootfs and base Ubuntu version all change.
flash.sh / Jetson Linux BSPallCommand-line flashing (`sudo ./flash.sh <board_config> mmcblk0p1` or `tools/kernel_flash` scripts) using the Jetson Linux BSP tarball + sample rootfs extracted on an x86 Ubuntu host, in recovery mode over USB. Underlies SDK Manager's GUI flash and is the only way to pass a custom board/flash configuration string (e.g. jetson-orin-nano-devkit-super) without the GUI.

nvpmodel power-mode presets

Flash configurationModenvpmodel idWatts
Standard flash configuration10W010default
Standard flash configuration7W_AI17
Standard flash configuration7W_CPU27
Super flash configuration (JetPack 6.2+)10W010
Super flash configuration (JetPack 6.2+)25W125default
Super flash configuration (JetPack 6.2+)MAXN_SUPER2

Power-mode sources

Full detail: Jetson Orin Nano 4GB on the power-modes page.

Known issues

iso no super upgrade

Affects: Jetson Orin Nano 8GB, Jetson Orin Nano 4GB, Jetson Orin NX 16GB, Jetson Orin NX 8GB · JetPack 6.2+ (still true as of 7.2)

Symptom: 25W and MAXN_SUPER power modes not offered by nvpmodel after installing via the ISO image.

Cause: The ISO image flashes in place without changing the board's flash configuration (TNSPEC/COMPATIBLE_SPEC); it cannot convert a non-Super-flashed device to Super Mode.

Remediation: Reflash from an x86 host using SDK Manager (or flash.sh) with the jetson-orin-nano-devkit-super / -super-maxn configuration, or manually correct /etc/nv_boot_control.conf's TNSPEC/COMPATIBLE_SPEC to carry the -super suffix.

Sources

jp5 to jp6 no ota

Affects: Jetson Orin Nano 8GB, Jetson Orin Nano 4GB, Jetson Orin NX 16GB, Jetson Orin NX 8GB, Jetson AGX Orin 32GB, Jetson AGX Orin 64GB, Jetson AGX Orin Industrial, jetson_xavier_nx, jetson_agx_xavier · JetPack 5.x → 6.x

Symptom: `apt upgrade`/OTA cannot move a device from JetPack 5.x to 6.x; the device stays on 5.x or breaks partway through.

Cause: JetPack 5 and 6 use different L4T major versions (R35 vs R36), different base Ubuntu (20.04 vs 22.04), and a different bootloader/kernel — no in-place upgrade path exists across major L4T versions.

Remediation: Reflash the device fully via SDK Manager or flash.sh with the JetPack 6.x BSP; only same-major-version point-release OTA (e.g. 6.0→6.2.x) is supported.

Sources

jp72 orin nano firmware prereq

Affects: Jetson Orin Nano 8GB, Jetson Orin Nano 4GB · JetPack 6.x and 7.2.1

Symptom: Orin Nano Developer Kit fails to boot a freshly flashed JetPack 6.x or 7.2.1 image; hangs or fails at boot.

Cause: Some Orin Nano devkits shipped with factory UEFI/QSPI firmware older than the JetPack-6.x-generation firmware baseline (pre-36.0); that older firmware cannot boot a JetPack 6.x/7.2.1 image.

Remediation: Check firmware version; if older than 36.0, run the JetPack 6.x QSPI/UEFI firmware update path (via a JetPack 5.1.3 bridge image, per NVIDIA's documented procedure) before flashing the target JetPack release.

Sources

  • NVIDIA · nvidia-docs:jetson/orin-nano-devkit/user-guide/latest/update_firmware.html · verified 2026-09-07 · Jetson Orin Nano Developer Kit User Guide — Update Firmware · class A
    “Some developer kits shipped with factory firmware that cannot boot JetPack 6.x or JetPack 7.2.1. If the firmware version is older than 36.0, update the”

ubuntu2404 jetpack7

Affects: Jetson Thor T5000, Jetson T4000, Jetson Orin Nano 8GB, Jetson Orin Nano 4GB, Jetson Orin NX 16GB, Jetson Orin NX 8GB, Jetson AGX Orin 32GB, Jetson AGX Orin 64GB, Jetson AGX Orin Industrial · JetPack 7.x

Symptom: apt packages, PPAs, or container base images built for Ubuntu 22.04 (JetPack 6.x) fail to install or behave differently on JetPack 7.x.

Cause: JetPack 7.x moved the root filesystem to Ubuntu 24.04 LTS with Linux Kernel 6.8, up from Ubuntu 22.04 / Kernel 5.15 on JetPack 6.x.

Remediation: Rebuild or re-pull container images and packages targeting Ubuntu 24.04 / L4T R38+ when moving a workload from a JetPack-6 (Orin) deployment to JetPack-7 (Thor or unified Orin+Thor 7.2+).

Sources

Every JetPack pairing

Check an exact configuration.

Pick the JetPack, install method, runtime and power mode — the engine builds the checks and verify plan live.

OPEN CONFIGURATION CHECKER →