agentleFS
Sign inStart free
Seeed-ProjectsSeeed-Projects/Seeed-Jetson-DevelopTool/skills/codex/jetpack-jetson-overview/AGENTS.md

Seeed-Jetson-DevelopTool / jetpack-jetson-overview

AGENTS.md57 starsChanged 4 months agoMITView on GitHub

Knowledge base for the relationship between JetPack and Jetson — JetPack components (L4T + SDK), Ubuntu version mapping, supported Seeed products, Super Mode, and JetPack archive links.

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check current version on device:

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Overview of JetPack and Jetson

This is a knowledge-base skill. Use it to answer questions about JetPack composition, version mappings, and Seeed product compatibility.

Execution model

This skill is informational — no destructive commands. Present relevant sections to the user based on their question.

Phase 1 — identify the user's question

Determine which topic the user needs:

  • What JetPack is composed of → Section A
  • JetPack ↔ Ubuntu version mapping → Section B
  • Which JetPack versions Seeed products support → Section C
  • JetPack 6.2 and Super Mode → Section D
  • How to find contents of each JetPack version → Section E

[OK] when topic is identified.

Section A — JetPack composition

JetPack has two major components:

① L4T (Linux for Tegra) — middleware Linux distribution for Jetson:

  • Ubuntu root filesystem
  • Linux kernel (with NVIDIA patches)
  • Drivers (GPU, ISP, CSI, I2C, etc.)
  • Firmware (Bootloader, UEFI, U-Boot, initrd)
  • BSP (Board Support Package) — device trees, boot configs, flash tools

② JetPack SDK — upper software layer for application development:

  • CUDA Toolkit
  • cuDNN (Deep Learning Library)
  • TensorRT (AI Model Inference Engine)

Section B — JetPack / L4T / Ubuntu version mapping

JetPackL4TUbuntu
6.236.4.322.04
6.136.4.022.04
6.036.3.022.04
5.1.335.5.020.04
5.1.135.3.120.04
4.6.632.7.618.04

Check current version on device:

cat /etc/nv_tegra_release

Section C — Seeed product JetPack support

Full compatibility matrix: https://docs.google.com/spreadsheets/d/1Sf7IdmVkKTAUH95XwxHK0ojV5aFq3ItKZ-iT28egzIk/edit?pli=1&gid=0#gid=0

Section D — JetPack 6.2 and Super Mode

Devices flashed with JetPack 6.2 support Super Mode activation. Super Mode is currently available only on select Seeed products.

Section E — JetPack version archive

Official NVIDIA JetPack archive with contents of each release: https://developer.nvidia.com/embedded/jetpack-archive

Failure decision tree

SymptomAction
User unsure which JetPack version they haveRun cat /etc/nv_tegra_release on the Jetson device
L4T version doesn't match any known JetPackCheck NVIDIA archive: https://developer.nvidia.com/embedded/jetpack-archive
Seeed product not in compatibility matrixContact Seeed support or check the Seeed wiki for latest updates

Reference files

  • references/source.body.md — Original Seeed wiki with full version tables and diagrams

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free