agentleFS
Sign inStart free
Seeed-ProjectsSeeed-Projects/Seeed-Jetson-DevelopTool/skills/claude/imx477-a603-setup/CLAUDE.md

Seeed-Jetson-DevelopTool / imx477-a603-setup

CLAUDE.md57 starsChanged 4 months agoMITView on GitHub

Install IMX477 camera driver on reComputer A603 carrier board. Downloads the JetPack-specific BSP with camera driver included and reflashes the device. Supports JP5.1.2, JP6.0, and JP6.2.

  • Installs packages

The file

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

8 rules. About 0 are common, 4 are distinctive, and 4 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.

  • 4

    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 to the next phase

    line 20
  4. Distinctive:

    After download, verify the archive is intact:

    line 57
  5. Very specific:

    If the listing shows files without errors → [OK] If tar reports an error → [STOP] archive corrupt

    line 62
  6. Very specific:

    If tar reports an error → [STOP] archive corrupt

    line 63
  7. Distinctive:

    Put the device into recovery mode:

    line 71
  8. Distinctive:

    After the device boots, test the IMX477 camera:

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

IMX477 Camera Driver — A603 Carrier Board

The A603 carrier board requires a custom BSP that bundles the IMX477 driver. The correct package depends on your JetPack version. The device must be reflashed after download — there is no in-place driver install path.

Reference: references/source.body.md (Seeed wiki source, BSP download links)

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 to the next phase

Phase 1 — preflight: check JetPack version (~10 s)

Identify the installed JetPack/L4T version to select the correct BSP package.

cat /etc/nv_tegra_release

Expected output contains a line like:

# R35 (release), REVISION: 4.1   → JetPack 5.1.2
# R36 (release), REVISION: 3.0   → JetPack 6.0
# R36 (release), REVISION: 4.0   → JetPack 6.2

Map the result to a BSP variant:

L4T revisionJetPackBSP package
R35.4.1JP5.1.2A603-JP5.1.2-BSP-with-IMX477.tar.gz
R36.3.0JP6.0A603-JP6.0-BSP-with-IMX477.tar.gz
R36.4.0JP6.2A603-JP6.2-BSP-with-IMX477.tar.gz

Tell the user which BSP they need before proceeding. [OK]

Phase 2 — download BSP (~varies by connection)

Download the correct BSP package from the Seeed wiki. Exact download URLs are in references/source.body.md under the matching JetPack section.

After download, verify the archive is intact:

tar -tzf <BSP_PACKAGE>.tar.gz | head -5

If the listing shows files without errors → [OK] If tar reports an error → [STOP] archive corrupt

Phase 3 — flash device (~15–30 min)

This step erases the device. Confirm the user has backed up any data.

Put the device into recovery mode:

  1. Power off the reComputer
  2. Hold the REC button, then connect USB-C to the host PC
  3. Release REC after 2 seconds
  4. Confirm the device is visible on the host:
lsusb | grep -i nvidia

Expected: Bus ... NVIDIA Corp. APX

Extract and run the flash script:

tar -xzvf <BSP_PACKAGE>.tar.gz
cd <extracted_folder>
sudo ./flash.sh

The flash script will take 15–30 minutes. The device reboots automatically when done. [OK] when the device boots to the desktop.

Phase 4 — verify camera (~30 s)

After the device boots, test the IMX477 camera:

nvgstcapture-1.0 --sensor-id=0

A preview window should open. Press q to quit.

# Alternative: check device node exists
ls /dev/video*

[OK] if preview opens or /dev/video0 is present.

Failure decision tree

SymptomAction
[STOP] L4T revision not in tableJetPack version may be unsupported. Check references/source.body.md for updated BSP list or ask user to confirm board revision
[STOP] archive corruptRe-download the BSP package. Check available disk space with df -h
lsusb does not show NVIDIA APXDevice not in recovery mode. Repeat REC button procedure; try a different USB-C cable
Flash script exits with errorCheck host has adb and fastboot installed: sudo apt install android-tools-adb android-tools-fastboot
Device does not boot after flashWrong BSP for board revision. Re-check L4T version and re-flash with correct package
nvgstcapture-1.0 — no such fileGStreamer tools not installed: sudo apt install gstreamer1.0-tools
nvgstcapture-1.0 — no cameras availableCamera cable not seated. Power off, reseat the FPC cable, retry
/dev/video0 missing after bootDriver not loaded. Run `dmesggrep imx477` and share output for diagnosis

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