Seeed-Jetson-DevelopTool / backup-restore
AGENTS.md57 starsChanged 4 months agoMITView on GitHub
Backup and restore a reComputer Jetson system image using the L4T backup/restore script. Requires Ubuntu host, USB-C cable, and the matching JetPack BSP package.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- bkraad47/ramentheir own version, first seen Nov 1, 2026
- davekilleen/Dextheir own version, first seen Aug 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- davekilleen/Dex★ 509same name
- bkraad47/ramen★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository297 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-nvrAGENTS.md
- allxon-ota-updateAGENTS.md
- allxon-setupAGENTS.md
- alwaysai-setupAGENTS.md
- bsp-source-buildAGENTS.md
- clawdbot-developmentAGENTS.md
- cochl-sense-setupAGENTS.md
- cvedia-setupAGENTS.md
- dashcamnet-xavier-nx-multicameraAGENTS.md
- deciai-setupAGENTS.md
- deepseek-quick-deployAGENTS.md
- deploy-deepseek-mlcAGENTS.md
- deploy-depth-anything-v3AGENTS.md
- deploy-diaAGENTS.md
- deploy-efficient-vision-engineAGENTS.md
- deploy-frigateAGENTS.md
- deploy-live-vlm-webuiAGENTS.md
- deploy-nvbloxAGENTS.md
- deploy-ollama-anythingllmAGENTS.md
- deploy-riva-llama2AGENTS.md
- developtool-deviceAGENTS.md
- disk-encryptionAGENTS.md
- diy-bsp-buildAGENTS.md
- ethercat-communicationAGENTS.md
- ethercat-setupAGENTS.md
- finetune-llm-llama-factoryAGENTS.md
- fix-browser-snap-jetsonAGENTS.md
- gapi-setupAGENTS.md
- generative-ai-introAGENTS.md
- gpt-oss-liveAGENTS.md
- gr00t-n1-5-deploy-thorAGENTS.md
- gr00t-n1-6-deploy-agxAGENTS.md
- hardhat-setupAGENTS.md
- hybrid-bsp-dk-to-recomputerAGENTS.md
- imx477-a603-setupAGENTS.md
- j501-viola-fruit-sortingAGENTS.md
- jetpack5-ssd-boot-fixAGENTS.md
- jetpack-flash-wsl2AGENTS.md
- jetpack-jetson-overviewAGENTS.md
- jetpack-ota-updateAGENTS.md
- jetson-ai-toolsAGENTS.md
- jetson-docker-setupAGENTS.md
- jetson-faqAGENTS.md
- jetson-pc-wired-shareAGENTS.md
- jetson-project-galleryAGENTS.md
- jetson-resource-indexAGENTS.md
- jetson-tutorial-exercisesAGENTS.md
- ko-module-buildAGENTS.md
- l4t-differencesAGENTS.md
- langchain-output-formattingAGENTS.md
- lerobot-env-setupAGENTS.md
- llama-cpp-rpc-distributedAGENTS.md
- llm-interface-controlAGENTS.md
- local-chatbot-multimodalAGENTS.md
- local-chatbot-physicalAGENTS.md
- local-llm-text-to-imageAGENTS.md
- local-rag-llamaindexAGENTS.md
- lumeo-setupAGENTS.md
- maskcam-nanoAGENTS.md
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 14
Run one phase at a time. After each phase:
- Very specific: line 16
If output contains [STOP] → stop immediately, consult the failure decision tree below.
- Very specific: line 17
If output ends with [OK] → tell the user "Phase N complete" and proceed to the next phase.
- Distinctive: line 35
Do these steps in order:
- Distinctive: line 43
Verify on the host:
- Distinctive: line 110
Ensure the device is in force recovery mode (redo Phase 1), then:
≈ “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.
Files
Backup and Restore reComputer Jetson System Image
Hardware required: Ubuntu host PC, USB-C cable, reComputer J3011 (JetPack 5.1.3). The backup and restore operations use the same script with different flags — complete Phases 1–4 for both operations.
Execution model
Run one phase at a time. After each phase:
- Relay all command output to the user.
- If output contains
[STOP]→ stop immediately, consult the failure decision tree below. - If output ends with
[OK]→ tell the user "Phase N complete" and proceed to the next phase.
Prerequisites
| Requirement | Detail |
| Host OS | Ubuntu 20.04 or 22.04 (native, not VM) |
| Cable | USB-C data cable ≤1.5 m |
| BSP package | Jetson_Linux_R35.5.0_aarch64.tbz2 (JetPack 5.1.3) |
| Flashing package | mfi_recomputer-orin (Seeed massflash image) |
| Disk space | ≥64 GB free on host for backup image |
Phase 1 — Enter force recovery mode (physical steps, no commands)
Do these steps in order:
- Power off the reComputer J3011 completely.
- Locate the REC (recovery) button and GND pin on the carrier board.
- Hold the REC button (or short REC to GND with a jumper).
- While holding REC, connect the USB-C cable from the Jetson to the Ubuntu host.
- Apply power to the Jetson; wait 2–3 seconds, then release REC / remove the jumper.
Verify on the host:
lsusb | grep -i nvidia
# Expected: Bus 00x Device 00x: ID 0955:7045 NVIDIA Corp. APX[OK] when the NVIDIA APX device appears. [STOP] if it does not — see failure decision tree.
Phase 2 — Download and extract BSP
Download Jetson_Linux_R35.5.0_aarch64.tbz2 from the NVIDIA L4T archive, then extract:
tar -xvzf Jetson_Linux_R35.5.0_aarch64.tbz2
# Produces: Linux_for_Tegra/[OK] when extraction completes without errors and Linux_for_Tegra/ directory exists.
Phase 3 — Merge BSP into flashing package
Copy BSP files into the Seeed massflash package without overwriting existing files:
sudo cp -rn Linux_for_Tegra/* mfi_recomputer-orin/[OK] when the command completes with no errors.
Phase 4 — Confirm board name
Find the correct board config name before running backup or restore:
cd mfi_recomputer-orin
ls | grep "\.conf"
# Note the board name, e.g. recomputer-orin-j3011.conf → board name is recomputer-orin-j3011[OK] when you have identified the .conf filename to use as the -b argument.
Phase 5a — Run backup
# Run from inside mfi_recomputer-orin/
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b recomputer-orinReplace recomputer-orin with the board name identified in Phase 4 (without .conf).
Expected: script prints progress and ends with a success message. The backup image is written to the backup/ subdirectory.
[OK] when the script exits cleanly. [STOP] on any error — see failure decision tree.
Phase 5b — Run restore (optional, only if restoring)
Ensure the device is in force recovery mode (redo Phase 1), then:
# Run from inside mfi_recomputer-orin/
sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r recomputer-orinReplace recomputer-orin with the same board name used during backup.
[OK] when the script exits cleanly and the device reboots. [STOP] on any error — see failure decision tree.
Failure decision tree
| Symptom | Action |
lsusb shows no NVIDIA APX device | Device not in recovery mode. Redo Phase 1. Try a different USB port. Confirm cable is data-rated (not charge-only). |
| Recovery mode entered but device disappears mid-operation | Insufficient power or bad cable. Use the official power adapter and a cable ≤1.5 m. |
l4t_backup_restore.sh: No such file or directory | BSP merge incomplete. Rerun Phase 3 and confirm tools/backup_restore/ exists inside mfi_recomputer-orin/. |
| Script fails with "board not found" or config error | Wrong board name passed to -b. Redo Phase 4 and use the exact filename stem from ls *.conf. |
| Backup script stalls or times out | USB instability. Flash from bare-metal Ubuntu (not a VM). Reconnect USB and retry from Phase 1. |
| Restore completes but device won't boot | Backup image may be corrupt or from a mismatched board. Verify the backup was taken from the same device and board config. |
Reference files
references/source.body.md— full Seeed Wiki tutorial with screenshots and additional context (reference only)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

