Agent skill · NVIDIA
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
What it needs
About 7k tokens when loaded.
What this skill does
Validate BSP Image Status: the DUT-access contract is stable; the rest of the validation procedure is a skeleton. Purpose Confirm that a freshly customized BSP landed correctly — both as a static artifact on disk and as a running system on the target — without re-promoting or re-flashing. Forms the validation tail of Deploy in the Setup → Customize → Build → Deploy pipeline (see ../../context/bsp-customization-workflow.md for the pipeline view) and is independently re-runnable. Prerequisites Active target-platform profile with bspimage: resolved (run /jetson-init-image first). For static-only scope: nothing further; the skill reads <bspimage.rootpath> directly. For on-target scope: /jetson-flash-image already pushed the staged BSP to the DUT. dutaccess: block authored in the active profile (or filled interactively at runtime — see ## DUT access). Host tooling per transport: ssh + sshpass for SSH; Python 3.6+ with pyserial for UART. Required env vars resolvable on the host when auth=password or sudo.method=password (passwordenv / sudo.passwordenv name the env var; never inline the secret in YAML). When to invoke After jetson-flash-image has put the BSP onto a target. The user explicitly asks to validate, test, or run smoke / regression checks on a flashed device. As a CI gate before declaring a customization batch shippable. Instructions The procedure below is a skeleton. 1. Read the active target per the prerequisite contract. 2. Choose validation scope — static (against bspimage on disk, no DUT needed) and/or on-target (DUT must be booted from the just-flashed image). 3. Static checks (if in scope): Required artifacts present at expected paths in <bspimage.rootpath>/LinuxforTegra/. DTB / module checksum or signature verification. Partition-layout sanity vs. the per-board .conf's XML. Cross-check overlay-staged outputs against bspimage (they should be identical post-promotion). Initramfs ↔ kernel + rootfs module coherence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/jetson-validate-image