agentleFS
Sign inStart free
Seeed-ProjectsSeeed-Projects/Seeed-Jetson-DevelopTool/skills/claude/l4t-differences/CLAUDE.md

Seeed-Jetson-DevelopTool / l4t-differences

CLAUDE.md57 starsChanged 4 months agoMITView on GitHub

Reference guide for differences between Seeed and NVIDIA L4T Board Support Packages across versions 35.3.1, 35.5, 36.3, 36.4, and 36.4.3. Covers added drivers for CAN bus, Wi-Fi, Ethernet, GMSL, TPM, audio codecs, and USB on Seeed Jetson devices.

The file

We split this CLAUDE.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
  1. Distinctive:

    Run one phase at a time. After each phase:

    line 14
  2. Very specific:

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

    line 16
  3. Very specific:

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

    line 17
  4. Distinctive:

    Check for CAN bus support:

    line 122
  5. Distinctive:

    Check for Realtek Wi-Fi:

    line 128
  6. Distinctive:

    Check for GMSL deserializer (L4T 36.x):

    line 134

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

Differences in L4T between Seeed and NVIDIA

Seeed's Jetson BSPs are based on NVIDIA's L4T with modifications to support Seeed hardware. This skill identifies the specific driver and feature differences per L4T version so users can understand what Seeed adds on top of the NVIDIA baseline.

Execution model

Run one phase at a time. After each phase:

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

Prerequisites

RequirementDetail
HardwareSeeed Jetson device (reComputer series)
JetPackIdentify installed version before proceeding

Phase 1 — Identify L4T version (~30 s)

cat /etc/nv_tegra_release

Or:

dpkg -l | grep -i nvidia-l4t-core

[OK] when L4T version string is displayed (e.g. R36.4.3, R35.5). [STOP] if file not found — device may not be running L4T.

Phase 2 — Identify JetPack version (~30 s)

dpkg -l | grep -i jetpack

Map the L4T version to JetPack:

L4T VersionJetPack
36.4.36.2
36.46.1
36.36.0
35.55.1.3
35.3.15.1.1

[OK] when JetPack version is confirmed.

Phase 3 — Review Seeed BSP differences for your version

Based on the L4T version identified in Phase 1, here are the key additions Seeed makes over NVIDIA's default BSP:

L4T 36.4.3 (JetPack 6.2)

  • MCP251X / MCP251XFD CAN bus controllers
  • Intel Wi-Fi driver (generic + modular + tracing)
  • Microchip LAN743x Gigabit Ethernet
  • PPP protocol support (async serial)
  • Realtek 88-series Wi-Fi (8723D, 8723DU, 8723X, USB)
  • TI TLV320AIC3X audio codec (I²C)
  • MAX9296A / MAX96717 / MAX96724 GMSL deserializers + aggregator
  • CRC-CCITT checksum, advanced video debug interface

L4T 36.4 (JetPack 6.1)

  • MCP251X / MCP251XFD CAN bus controllers
  • Intel Wi-Fi MVM driver (generic + tracing + LED)
  • Microchip LAN743x Gigabit Ethernet
  • PPP protocol support (async serial)
  • Realtek RTW88 Wi-Fi (8723D, 8723DU, 8723X, USB)
  • CH341 USB-to-serial converter
  • CRC-CCITT, compression libraries for PPP

L4T 36.3 (JetPack 6.0)

  • MCP251X / MCP251XFD CAN bus controllers
  • Intel Wi-Fi (generic + tracing), I²C ATR protocol
  • Microchip LAN743x Gigabit Ethernet
  • Realtek 88-series Wi-Fi (8723D, 8723DU, 8723X)
  • TI TLV320AIC3X audio codec (I²C)
  • MAX96717 / MAX96724 / MAX9296A GMSL deserializers + aggregator
  • TPM core + SPI + Infineon I²C, SELinux

L4T 35.5 (JetPack 5.1.3)

  • IMX219 camera compiled into kernel (NVIDIA: module)
  • IMX390 camera disabled (NVIDIA: compiled in)
  • LAN743x compiled into kernel (NVIDIA: module)
  • TI DP83867 Ethernet PHY, NXP PTN5150 USB Type-C
  • nvmem framework, STPMIC1 / TPS65090 power management
  • LM90 temp sensor, NTC thermistors
  • TLV320AIC3X audio codec (I²S + I²C)
  • USB Type-C TCPCI, MT6370 Type-C controller
  • USB console device, CH341 USB-to-serial

L4T 35.3.1 (JetPack 5.1.1)

  • TPM hardware RNG as entropy source
  • /sys/kernel/security mount for SELinux/AppArmor
  • TPM core interface + SPI bus access
  • TPM secure boot and key storage

[OK] — informational phase, no commands to run.

Phase 4 — Verify Seeed-specific drivers are loaded (optional)

Check for CAN bus support:

lsmod | grep mcp251

Check for Realtek Wi-Fi:

lsmod | grep rtw

Check for GMSL deserializer (L4T 36.x):

lsmod | grep max96

[OK] when relevant modules appear for your hardware configuration.

Failure decision tree

SymptomAction
/etc/nv_tegra_release not foundDevice may not be running L4T. Check if this is a Jetson device with uname -a.
L4T version not in the tableSeeed BSP may not be installed. Reflash with Seeed's BSP from their download page.
Expected driver module not loadedCheck if module exists: find /lib/modules -name "*.ko" | grep <driver>. Load with sudo modprobe <driver>.
CAN interface not workingVerify MCP251X hardware is connected. Check dmesg | grep can for errors.
Wi-Fi adapter not detectedConfirm USB/PCIe Wi-Fi adapter is plugged in. Check lsusb or lspci.

Reference files

  • references/source.body.md — Full listing of all Seeed BSP differences per L4T version with additional context (reference only)

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