HomeCompatibility › Jetson Thor T5000
Jetson Configuration Compatibility · Jetson Thor T5000

Jetson Thor T5000: 4 supported JetPack releases.

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

JetPack 7.0 through 7.2.1. Jetson Thor T5000 platform page. Power-mode presets: Jetson Thor T5000 on the power-modes page.

Supported releases and compute stack

JetPackL4TCUDATensorRTcuDNNDeepStreamUbuntu
7.038.213.0.010.13.2.69.12.024.04
7.138.413.0.010.13.3.99.12.07.124.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
JetPack 7.0 (Jetson Linux 38.2 / 38.2.1)MAXN0
JetPack 7.0 (Jetson Linux 38.2 / 38.2.1)120W1120default
JetPack 7.1+ (Jetson Linux 38.4 and later)MAXN0
JetPack 7.1+ (Jetson Linux 38.4 and later)120W1120default
JetPack 7.1+ (Jetson Linux 38.4 and later)90W290
JetPack 7.1+ (Jetson Linux 38.4 and later)70W370

Power-mode sources

Full detail: Jetson Thor T5000 on the power-modes page.

Known issues

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

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

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 →