Does NVIDIA support this configuration?

Pick a Jetson module, JetPack/L4T release, install method, runtime and power mode. The checker compares every part against NVIDIA's published release notes, developer guide and power-mode registry and returns SUPPORTED, SUPPORTED WITH RISKS, NEEDS VALIDATION or UNSUPPORTED — the worst individual check decides the verdict — plus the on-device commands that settle anything the published data can't.

01 · Define configuration

Module & JetPack

Platform

Loading hardware catalog…

JetPack / L4T

Select a platform first

Install & Runtime

Install method

Runtime

Runtime version

Power & Deployment

Power mode

Select a platform first

Super flash configuration

Not sure

Yes

Deployment

Bare metal

Containers

Advanced

Artifact CUDA

Artifact Ubuntu

Devkit

Not sure

Yes

Select a platform to continue

03 · How this works

Every check is a published fact, not a guess

Each check compares the requested configuration against NVIDIA's own facts — the JetPack archive and release notes, the Jetson Linux developer guide, the power-mode registry, and developer-forum replies from NVIDIA staff for the gaps the docs don't cover. PASS means it is a published pairing; VERSION RISK means it works in practice but is not the officially paired version; REQUIRES VALIDATION means the published data can't decide it either way; UNSUPPORTED means NVIDIA says it does not work; UNKNOWN means the input isn't in the registry at all. The overall verdict is always the worst individual check.

The verify plan is the point

Every check names the on-device command that settles it, de-duplicated and ordered so one command (usually cat /etc/nv_tegra_release) resolves several checks at once, with the expected output pattern so you know what a pass looks like before you run anything.

JetPack left blank means "latest for this module"

If no JetPack is chosen, the checker assumes the latest release that lists your module as supported and says so in the result (jetpack_defaulted: true) — it never silently assumes a release your module can't run.

Full formulas, source list and what invalidates a result: methodology. Static tables: Jetson compatibility by module and JetPack. Raw dataset: datasets/jetpack-config.json. Power-mode presets: Jetson power modes by module and JetPack.

04 · FAQ

What does SUPPORTED WITH RISKS mean?

The configuration works in practice but is not the version pairing NVIDIA officially tested — for example DeepStream 7.1 running on JetPack 6.2 instead of its paired 6.1, or a power preset needing a Super flash configuration that was not confirmed. It usually runs; verify with the listed commands.

What does NEEDS VALIDATION mean?

NVIDIA's published data does not say either way — no documented pairing exists for that exact combination. The verify plan gives the exact command and expected output that settles it on the board.

Where do the compatibility facts come from?

NVIDIA's JetPack archive and release notes, the Jetson Linux developer guide, the power-mode registry, and NVIDIA-staff replies on the developer forums for gaps the docs don't cover — every check names its source with a class (A vendor specification through E engineering heuristic) and a link.

Why does it grey out some JetPack releases instead of hiding them?

A release your module doesn't support is still a useful answer — UNSUPPORTED, with the reason and the nearest release that works — so it stays selectable rather than disappearing from the list.