← ClaudeAtlas

camera-bringup-debuglisted

Use when a Jetson camera is not detected or gives zero frames, no /dev/video0, i2cdetect shows nothing, v4l2-ctl select timeout, capture hangs, nvargus/Argus fails; walks the ProventusNova camera bring-up isolation flow step by step, interpreting the user's command output at each node. Jetson only (directly-wired MIPI CSI sensors); not for GMSL/FPD-Link serdes cameras or other platforms.
ProventusNovaLLC/pn-tools · ★ 0 · Code & Development · score 67
Install: claude install-skill ProventusNovaLLC/pn-tools
# Camera Bring-Up Debug (NVIDIA Jetson) You are walking the user through ProventusNova's camera bring-up isolation flow. The method is a decision tree: at each node, give the user ONE command, ask them to paste the output, interpret it, and take the branch. Hardware-verified on L4T R36.4.3 (JetPack 6). ## Scope gate (check FIRST) - Directly-wired MIPI CSI sensor on NVIDIA Jetson only. - Camera behind a GMSL / FPD-Link serdes link → stop; that is a different failure domain (link training, serdes config). Point the user to ProventusNova's GMSL debugging guide. - Non-Jetson platforms → this tree's Jetson-specific nodes (N5+) do not apply; say so honestly. - Prerequisite: `v4l2-ctl` is NOT preinstalled on JetPack: `sudo apt install v4l-utils` first. ## How to run the loop 1. Ask which sensor/driver (name, e.g. imx477) and what the symptom is. 2. Start at N1 unless the symptom pins a later node (e.g. "raw capture works but Argus fails" → start at N9). 3. Per node: state the command from `references/jetson.md` (substitute the user's `<bus>`, `<sensor>`, `/dev/videoN`, W/H/FMT values), have them run it, read the pasted output, branch per the reference. 4. NEVER invent register values, DT paths, or error meanings beyond the reference file. If output matches nothing in the reference, say so and use the escalation rule. 5. On fix-loop boxes (A-nodes): after the user applies a fix, re-run the node the reference names; do not skip ahead. ## Node order and