Which Jetson × JetPack pairs does NVIDIA actually support?
Method v1.0 · dataset 2026-09-07 · verified 2026-09-07 · last updated September 2026
9 Jetson modules across 16 JetPack / L4T releases (JetPack 5.1.2 through 7.2.1), for the default SDK Manager flash + TensorRT runtime configuration. 105 of 144 pairs are supported. Install methods, Super Mode enablement and every known issue are sourced from NVIDIA release notes, the Jetson Linux Developer Guide or a developer-forum staff reply. Download the whole registry as JSON with provenance, or read the methodology.
Modules × JetPack releases
Verdict for the SDK Manager flash + TensorRT runtime configuration. Click a SUPPORTED cell for the full breakdown — compute stack, checks, verify plan, remediations and known issues for that exact pair. Click a module name for its supported range, per-release stack, install methods and nvpmodel presets.
JetPack ↔ Jetson Linux (L4T) ↔ compute stack
Every JetPack release NVIDIA has published, with the Jetson Linux (L4T) build and the CUDA / TensorRT / cuDNN / Ubuntu versions it ships. A dash means the archive lists the release but the compute-stack figure was not independently verified this pass — see gaps.
| JetPack | L4T | CUDA | TensorRT | cuDNN | Ubuntu | Release date | Source |
|---|---|---|---|---|---|---|---|
| 5.1.2 | 35.4.1 | 11.4.19 | 8.5.2 | 8.6.0 | 20.04 | 2023-08-25 | NVIDIA · nvidia-docs:jetson/jetpack-archived/jetpack-512 · verified 2026-09-07 |
| 5.1.3 | 35.5.0 | 11.4.19 | 8.5.2 | 8.6.0 | 20.04 | — | NVIDIA · nvidia-docs:jetson/jetpack-archived/jetpack-513 · verified 2026-09-07 |
| 5.1.4 | 35.6.0 | 11.4.19 | 8.5.2 | 8.6.0 | 20.04 | 2024-09-04 | NVIDIA · nvidia-docs:jetson/jetpack-archived/jetpack-514 · verified 2026-09-07 |
| 5.1.5 | 35.6.1 | 11.4.19 | 8.5.2 | 8.6.0 | 20.04 | 2025-03-12 | NVIDIA · nvidia-docs:jetson/jetpack-archived/jetpack-515 · verified 2026-09-07 |
| 5.1.6 | 35.6.4 | — | — | — | 20.04 | — | NVIDIA · nvidia-dev:embedded/jetpack-archive · verified 2026-09-07 |
| 5.1.7 | 35.6.5 | — | — | — | 20.04 | — | NVIDIA · nvidia-dev:embedded/jetpack-archive · verified 2026-09-07 |
| 6.0 | 36.3 | 12.2.12 | 8.6.2 | 8.9.4 | 22.04 | 2024-05-30 | NVIDIA · nvidia-docs:jetson/jetpack-archived/jetpack-60 · verified 2026-09-07 |
| 6.1 | 36.4 | 12.6.10 | 10.3.0 | 9.3.0 | 22.04 | 2024-12-16 | NVIDIA · nvidia-docs:jetson/jetpack-archived/jetpack-61 · verified 2026-09-07 |
| 6.2 | 36.4.3 | 12.6.10 | 10.3.0 | 9.3.0 | 22.04 | 2025-01-15 | NVIDIA · nvidia-docs:jetson/jetpack-archived/jetpack-62 · verified 2026-09-07 |
| 6.2.1 | 36.4.4 | 12.6.10 | 10.3.0 | 9.3.0 | 22.04 | 2025-06-26 | NVIDIA · nvidia-docs:jetson/jetpack/release-notes · verified 2026-09-07 |
| 6.2.2 | 36.5.0 | — | — | — | 22.04 | — | NVIDIA · nvidia-dev:embedded/jetpack-archive · verified 2026-09-07 |
| 6.2.3 | 36.5.2 | — | — | — | 22.04 | — | NVIDIA · nvidia-dev:embedded/jetpack-archive · verified 2026-09-07 |
| 7.0 | 38.2 | 13.0.0 | 10.13.2.6 | 9.12.0 | 24.04 | 2025-08-25 | NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.0 · verified 2026-09-07 |
| 7.1 | 38.4 | 13.0.0 | 10.13.3.9 | 9.12.0 | 24.04 | 2026-01-06 | NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.1 · verified 2026-09-07 |
| 7.2 | 39.2 | 13.2.1 | 10.16.2 | 9.20.0 | 24.04 | 2026-06-02 | NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.2 · verified 2026-09-07 |
| 7.2.1 | 39.2.1 | 13.2.1 | 10.16.2 | 9.20.0 | 24.04 | 2026-08-11 | NVIDIA · nvidia-dev:blog/nvidia-jetpack-7-2-1-adds-agentic-video-skills-and-t3000-emulation · verified 2026-09-07 |
Install methods
| Method | Modules | JetPack range | Notes | Source |
|---|---|---|---|---|
| SDK Manager (host flash) | 11 | all | Host-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). | NVIDIA · nvidia-docs:jetson/r36.4.4/DeveloperGuide · verified 2026-09-07 |
| SD card image | 1 | 5.1–7.1 (removed in 7.2) | Only the Jetson Orin Nano Developer Kit carrier board has a microSD slot on the module; Orin NX and production Orin Nano modules have no SD/eMMC and require NVMe or SDK-Manager flashing instead. JetPack 7.2 discontinued the SD Card image entirely in favor of the unified ISO image. | NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.2 · verified 2026-09-07 |
| ISO image (target-side) | 9 | 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. | NVIDIA · forums.developer.nvidia.com/t/372627 · verified 2026-09-07 |
| apt upgrade / OTA | 9 | minor/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. | NVIDIA · forums.developer.nvidia.com/t/280782 · verified 2026-09-07 |
| flash.sh / Jetson Linux BSP | 11 | all | Command-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. | NVIDIA · nvidia-docs:jetson/orin-nano-devkit/user-guide/latest/update_firmware.html · verified 2026-09-07 |
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
- NVIDIA · forums.developer.nvidia.com/t/372627 · verified 2026-09-07 · NVIDIA Developer Forums — 25W and MAXN SUPER not seen in JetPack 7.2 (staff reply, DavidDDD) · class A
“Currently, the ISO image cannot upgrade a device from non-Super Mode to Super Mode.”
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
- NVIDIA · forums.developer.nvidia.com/t/280782 · verified 2026-09-07 · NVIDIA Developer Forums — Expected JetPack 5 to JetPack 6 Upgrade paths (staff reply, linuxdev) · class A
“Correct, you won't be able to OTA update from 5 to 6. You'll be able to upgrade minor upgrades only. You'll need to flash (in”
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”
no sd card jp72
Affects: Jetson Orin Nano 8GB · JetPack 7.2+
Symptom: No SD Card image download option for the Orin Nano Developer Kit starting with JetPack 7.2.
Cause: NVIDIA discontinued the SD Card image format for the Orin Nano Developer Kit in favor of a single unified ISO image flashed via USB stick.
Remediation: Use the unified ISO image and a USB stick to flash the Orin Nano Developer Kit target-side; SDK Manager/flash.sh from an x86 host remains available as an alternative.
Sources
- NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.2 · verified 2026-09-07 · JetPack SDK Downloads and Notes Archive — 7.2 · class A
“There is no more SD Card image for Jetson Orin Nano Developer Kit. Use the unified ISO image to flash the developer kit using a”
thor requires jetpack7
Affects: Jetson Thor T5000, Jetson T4000 · JetPack 7.0 minimum for T5000; 7.1 minimum for T4000
Symptom: Jetson Thor modules cannot be flashed with any JetPack 5.x/6.x image.
Cause: Thor is a new SoC generation (Blackwell-class GPU, SBSA-aligned firmware/bootloader) with its own L4T line (R38+) starting at JetPack 7.0; T4000 specifically was not supported until JetPack 7.1 (Jetson Linux 38.4).
Remediation: Flash Thor T5000 with JetPack 7.0 or later; flash T4000 with JetPack 7.1 or later.
Sources
- NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.1 · verified 2026-09-07 · JetPack SDK Downloads and Notes Archive — 7.0 and 7.1 · class A
“Jetson Linux 38.4 ... Jetson AGX Thor Developer Kit, Jetson T5000, Jetson T4000.”
cuda13 thor only
Affects: Jetson Thor T5000, Jetson T4000 · JetPack 7.0+
Symptom: A container or wheel built against CUDA 12.x (the Orin-generation stack) fails to run or link on a Thor device, or vice versa.
Cause: JetPack 7.x on Thor ships CUDA 13.x (13.0.0 at 7.0/7.1, 13.2.1 at 7.2/7.2.1) while the Orin-generation JetPack 6.x line tops out at CUDA 12.6.10 — the two SoC generations are not binary-compatible at the CUDA toolkit level.
Remediation: Build/select containers and wheels tagged for the correct Jetson family (Thor vs. Orin) and JetPack major version; do not mix a JetPack-6-built CUDA 12.x artifact onto a JetPack-7/Thor target or vice versa.
Sources
- NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.0 · verified 2026-09-07 · JetPack SDK Downloads and Notes Archive — 7.0 · class A
“The latest AI compute stack includes CUDA 13, cuDNN 9.12, and TensorRT 10.13.”
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
- NVIDIA · nvidia-dev:embedded/jetpack/downloads/archive-7.0 · verified 2026-09-07 · JetPack SDK Downloads and Notes Archive — 7.0 · class A
“Jetson Linux 38.2 ... Ubuntu 24.04 LTS ... L4T Ubuntu 24.04.”
Research gaps
- JetPack 5.1.6 and 5.1.7 compute-stack versions (CUDA/TensorRT/cuDNN/VPI) not verified — only L4T mapping confirmed from the JetPack Archive listing page.
- JetPack 6.2.2 and 6.2.3 compute-stack versions not verified beyond the L4T mapping already present in edgeaistack-api/src/v2/data/power_modes_data.js JETPACK_L4T.
- JetPack 5.1.5 has two L4T revisions listed across sources (35.6.1 and 35.6.2); which is canonical/latest for the 5.1.5 label is unresolved.
- DeepStream version mapping is only confirmed for JetPack 6.1 (DeepStream 7.1, official) and inferred/unconfirmed for 6.2, 6.2.1, 7.0, 7.1, 7.2 — no NVIDIA-published DeepStream↔JetPack 7.x compatibility matrix was found; forum threads (e.g. 'DeepStream 8.0/7.1 compatibility issue on Jetson Orin Nano Super with JetPack 7.2') suggest active incompatibility as of this writing.
- No official JetPack release date found for 5.1.3, 5.1.6, 5.1.7, 6.2.2, or 6.2.3 (left null).
- onnxruntime, llama_cpp, ollama, and mlc runtime/version/install specifics were not independently researched this pass — flagged with jetpack:null in runtime_compat and should be a follow-up topic.
- `ls /dev/nvhost*` expected output and the ollama/llama.cpp CUDA-detection verify commands have no NVIDIA-published canonical reference; recorded as best-effort community patterns or left as explicit gaps.
- Jetson T3000 is mentioned in JetPack 7.2.1 release material only as 'emulation' support, not a shipping module — deliberately excluded from module_ids per the task's module list; a real T3000 launch (if any) is a gap for future research.
- Legacy modules (jetson_xavier_nx, jetson_agx_xavier, jetson_nano) 'last supported JetPack' facts: Xavier NX and AGX Xavier last appear in JetPack 5.1.7 (L4T 35.6.5) per the archive listing; Jetson Nano's last JetPack (4.6.6, L4T 32.7.6) was not independently re-verified this pass (carried over from general JetPack Archive listing, 4.x series, not deep-checked against a dedicated Nano EOL notice).
Method and data
- Engine: Jetson Configuration Checker — pick any module, JetPack, install method, runtime and power mode and get the live breakdown.
- Methodology: check catalogue, status vocabulary, verdict rule and verify plan.
- Dataset: jetpack-config.json — every release, install method, verify command, runtime pairing and known issue with its provenance record.
- Power modes: Jetson power modes by module and JetPack.
Check your exact configuration.
Pick the module, JetPack, install method, runtime and power mode — the engine builds the checks and verify plan live and gives you a permanent link.