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

Seeed-Jetson-DevelopTool / jetpack-ota-update

AGENTS.md57 starsChanged 4 months agoMITView on GitHub

Perform an image-based OTA update on Seeed Jetson devices to upgrade from JetPack 5.1.3 to JetPack 6.0. Requires Ubuntu 20.04 host PC and USB-C cable. Demonstrated on reComputer J3010.

The file

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

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run one phase at a time. After each phase:

    line 18
  2. Very specific:

    If output contains [STOP] → stop immediately, consult the failure decision tree

    line 19
  3. Very specific:

    If output ends with [OK] → tell the user "Phase N complete" and proceed

    line 20
  4. Distinctive:

    If the device doesn't already have JP5.1.3:

    line 71
  5. Distinctive:

    After completion, reboot the device:

    line 151

≈ “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

JetPack Image-Based OTA Update (5.1.3 → 6.0)

Upgrade Jetson Linux from JetPack 5.1.3 to JetPack 6.0 using NVIDIA's image-based over-the-air update mechanism. Demonstrated on reComputer J3010.

Hardware: reComputer J4012/J4011/J3010/J3011, USB-C cable Software: Ubuntu 20.04 host PC, internet connection

Execution model

Run one phase at a time. After each phase:

  • If output contains [STOP] → stop immediately, consult the failure decision tree
  • If output ends with [OK] → tell the user "Phase N complete" and proceed

Board-specific variables must be set based on the Jetson module:

ModuleBOARDIDBOARDSKUFABBOARDREVCHIP_SKU
Orin Nano 4G37670004300N.200:00:00:D6
Orin Nano 8G37670003300N.200:00:00:D6
Orin NX 8G37670001300M.300:00:00:D4
Orin NX 16G37670000300G.300:00:00:D3

Phase 1 — download JP5.1.3 BSP (~10 min)

mkdir -p jp5 && cd jp5
wget https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v5.0/release/jetson_linux_r35.5.0_aarch64.tbz2
wget https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v5.0/release/tegra_linux_sample-root-filesystem_r35.5.0_aarch64.tbz2

[OK] when both files download successfully.

Phase 2 — build JP5.1.3 system image (~15 min)

tar xf jetson_linux_r35.5.0_aarch64.tbz2
sudo tar xpf tegra_linux_sample-root-filesystem_r35.5.0_aarch64.tbz2 -C Linux_for_Tegra/rootfs/
cd Linux_for_Tegra
sudo ./apply_binaries.sh

Generate the system image (replace variables per the table above):

sudo BOARDID=<BOARDID> BOARDSKU=<BOARDSKU> FAB=<FAB> BOARDREV=<BOARDREV> CHIP_SKU=<CHIP_SKU> \
  ./tools/kernel_flash/l4t_initrd_flash.sh \
  --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_nvme.xml \
  -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg" \
  --no-flash --massflash 5 --network usb0 \
  jetson-orin-nano-devkit external

[OK] when mfi_jetson-orin-nano-devkit.tar.gz is generated in Linux_for_Tegra/.

Phase 3 — (optional) flash JP5.1.3 to device

If the device doesn't already have JP5.1.3:

sudo tar xpf mfi_jetson-orin-nano-devkit.tar.gz
cd mfi_jetson-orin-nano-devkit
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 1 --network usb0 --showlogs

[OK] when device boots JP5.1.3.

Phase 4 — download JP6.0 BSP + OTA tools (~10 min)

cd <root_dir>
mkdir -p jp6 && cd jp6
wget https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v3.0/release/jetson_linux_r36.3.0_aarch64.tbz2
wget https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v3.0/release/tegra_linux_sample-root-filesystem_r36.3.0_aarch64.tbz2
wget https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v3.0/release/ota_tools_R36.3.0_aarch64.tbz2

[OK] when all three files download successfully.

Phase 5 — build JP6.0 system image (~15 min)

tar xf jetson_linux_r36.3.0_aarch64.tbz2
sudo tar xpf tegra_linux_sample-root-filesystem_r36.3.0_aarch64.tbz2 -C Linux_for_Tegra/rootfs
cd Linux_for_Tegra
sudo ./apply_binaries.sh
sudo BOARDID=<BOARDID> BOARDSKU=<BOARDSKU> FAB=<FAB> BOARDREV=<BOARDREV> CHIP_SKU=<CHIP_SKU> \
  ./tools/kernel_flash/l4t_initrd_flash.sh \
  --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_nvme.xml \
  -p "-c bootloader/generic/cfg/flash_t234_qspi.xml --no-systemimg" \
  --no-flash --massflash 5 --network usb0 \
  jetson-orin-nano-devkit external

[OK] when image generation completes.

Phase 6 — generate OTA payload package (~10 min)

cd <root_dir>/jp6
tar xf ota_tools_R36.3.0_aarch64.tbz2
cd Linux_for_Tegra
sudo BASE_BSP=<root_dir>/jp5/Linux_for_Tegra \
  ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh \
  --external-device nvme0n1 -S 80GiB jetson-orin-nano-devkit R35-5

[OK] when ota_payload_package.tar.gz appears in Linux_for_Tegra/bootloader/jetson-orin-nano-devkit/.

Phase 7 — apply OTA on device (~15 min)

Copy the OTA package to the Jetson device and run on the device:

scp <host_path>/jp6/Linux_for_Tegra/bootloader/jetson-orin-nano-devkit/ota_payload_package.tar.gz <user>@<jetson_ip>:~

On the Jetson device:

wget https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v3.0/release/ota_tools_R36.3.0_aarch64.tbz2
sudo mkdir -p /ota
sudo mv ~/ota_payload_package.tar.gz /ota
tar xf ota_tools_R36.3.0_aarch64.tbz2
cd ~/Linux_for_Tegra/tools/ota_tools/version_upgrade
sudo ./nv_ota_start.sh /ota/ota_payload_package.tar.gz

After completion, reboot the device:

sudo reboot

[OK] when device boots into JetPack 6.0.

Failure decision tree

SymptomAction
BSP download failsCheck internet. Verify URLs are still valid at NVIDIA's download page.
apply_binaries.sh failsEnsure rootfs was extracted with sudo tar xpf. Re-extract and retry.
Image generation failsVerify BOARDID/BOARDSKU/FAB/BOARDREV/CHIP_SKU match your module.
OTA package generation failsEnsure BASE_BSP path points to the JP5.1.3 Linux_for_Tegra directory.
nv_ota_start.sh fails on deviceCheck disk space (df -h). Ensure OTA package is in /ota/.
Device won't boot after OTARe-flash JP6.0 directly using standard flash method as fallback.

Reference files

  • references/source.body.md — Original Seeed wiki with board-specific variable tables and screenshots

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