Agent skill · software engineering · nvidia
jetson-customize-camera
Enable MIPI/GMSL camera sensors on a Jetson Thor or Orin custom carrier by rendering a kernel-DT overlay from the in-tree sensor DTSI. Do NOT use for UPHY lane allocation or ODMDATA edits.
Why this skill is useful
Adds a custom kernel-DT overlay generation script for enabling MIPI/GMSL camera sensors on Jetson platforms, which is not commonly available in public documentation.
What it needs
Requires cpp, dtc, fdtoverlay installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
Customize camera (CSI / MIPI / GMSL sensor bring-up) Overview Tegra264 (Thor) and Tegra234 (Orin) expose a single tegra-capture-vi controller fronted by NVCSI and a fixed set of CSI ports. Camera bring-up is: 1. Sensor selection — picked from the set NVIDIA ships in-tree .dtsi references for on the active platform. 2. Carrier + module support check — verified against the Camera Development Guide, Adaptation Guide §Camera, carrier schematic, Module TRM, and carrier pinmap. 3. Wiring — derived from the in-tree tegra<soc>-camera-<sensor>.dtsi when one exists (the DTSI IS the wiring source of truth); captured per-sensor from the user when the sensor is custom. 4. Kernel-DT overlay — cpp-expand the in-tree DTSI, extract its fragment@N body, append into the composite custom overlay .dts for the active target (per ../../references/bsp-customization-kernel-dtb.md), verify the composite with fdtoverlay. /jetson-build-source compiles the composite and owns the carrier conf's OVERLAYDTBFILE+= registration. Agentic, not table-driven — sensor list is built at runtime by globbing in-tree per-sensor dtbos. No THORCAMERAS dict, no questions.json, no Python renderer in the question path. No ODMDATA edit — cameras don't consume UPHY lanes (CSI is a separate PHY pool). The skill emits only a kernel-DT overlay; the ODMDATA line in the carrier conf is untouched by this skill. The output is one commit: Camera fragment@N block (plus jetson-header-name on the composite root if not already present) appended to the composite custom overlay .dts per ../../references/bsp-customization-kernel-dtb.md → committed to the bspsources/ hardware repo. /jetson-build-source compiles the composite to .dtbo and owns its Makefile + flash-conf registration. When to invoke The user says "enable camera", "configure CSI", "wire a Hawk / Owl / IMX sensor", "MIPI camera", "GMSL camera", or asks to bring up tegra-capture-vi / NVCSI on a custom carrier. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/jetson-customize-camera