Jetson Validate Image
NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA
- Skill
- Review and audit
- Software development
- Apache-2.0
- Medium risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The jetson-validate-image skill provides a validation layer for customized Board Support Packages (BSP). It confirms that a BSP has been correctly applied by performing static analysis of artifacts on disk and executing smoke or regression tests on a flashed device. It supports both static-only validation and on-target testing via SSH or UART, ensuring that kernel, module, and initramfs components are coherent and correctly deployed.
What it does
- Verifies static artifacts like DTB, module checksums, and partition layouts.
- Checks for coherence between initramfs, kernel Image, and rootfs modules.
- Connects to a flashed device via SSH or UART to confirm userspace boot.
- Detects drift between running kernel modules and those present in the rootfs.
- Compares the running kernel version against the version found in the boot Image.
- Collects logs and test results from the target device.
When to use it
- After flashing a BSP to a target device using jetson-flash-image.
- When you need to perform smoke or regression testing on a flashed device.
- As a quality gate in a CI pipeline before declaring a customization batch shippable.
- To troubleshoot module loading or kernel version mismatch issues.
Advantages
- Supports both static and on-target validation workflows.
- Provides automated detection of common BSP deployment errors like initramfs drift.
- Offers flexible connectivity options including UART for devices without network access.
- Maintains security by using environment variables for passwords instead of inlining them in configuration files.
Usage examples
- “/jetson-validate-image”
- Performs static checks against the staged BSP on disk without requiring a target device.
- “/jetson-validate-image”
- Executes on-target validation tests using the SSH configuration defined in the active profile.
- “/jetson-validate-image”
- Runs validation tests over a UART connection at /dev/ttyACM0 using credentials from the profile.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/jetson-validate-image/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip jetson-validate-image.zip -d .agents/skills
Documentation by Jetson Team
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
bsp_image:resolved (run/jetson-init-imagefirst).For static-only scope: nothing further; the skill reads
<bsp_image.root_path>directly.For on-target scope:
/jetson-flash-imagealready pushed the staged BSP to the DUT.dut_access:block authored in the active profile (or filled interactively at runtime — see## DUT access).Host tooling per transport:
ssh+sshpassfor SSH; Python 3.6+ withpyserialfor UART.Required env vars resolvable on the host when
auth=passwordorsudo.method=password(password_env/sudo.password_envname the env var; never inline the secret in YAML).
When to invoke
After
jetson-flash-imagehas 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.
Read the active target per the prerequisite contract.
Choose validation scope — static (against
bsp_imageon disk, no DUT needed) and/or on-target (DUT must be booted from the just-flashed image).Static checks (if in scope):
Required artifacts present at expected paths in
<bsp_image.root_path>/Linux_for_Tegra/.DTB / module checksum or signature verification.
Partition-layout sanity vs. the per-board
.conf's XML.Cross-check overlay-staged outputs against
bsp_image(they should be identical post-promotion).Initramfs ↔ kernel + rootfs module coherence. Extract
<bsp_image>/Linux_for_Tegra/bootloader/l4t_initrd.imgand<bsp_image>/Linux_for_Tegra/rootfs/boot/initrd; verify three invariants against the promotedbsp_imagestate: (a)<bsp_image>/Linux_for_Tegra/kernel/Imagematches<bsp_image>/Linux_for_Tegra/rootfs/boot/Imagebyte-for- byte — drift here means the "Mirror kernel Image into rootfs" step was skipped and any subsequent initramfs refresh built against the previous kernel. (b) for each module path the two initrd images ship, the bytes / md5 match the file under<bsp_image>/Linux_for_Tegra/rootfs/lib/modules/<ver>/— any drift means modules will be shadowed at early boot. (c) the vermagic stamped on every initramfs*.komatches theUTS_RELEASEreachable from<bsp_image>/Linux_for_Tegra/kernel/Image(e.g. parse theLinux version …string withstrings) — a vermagic skew means the kernelImagewas refreshed without rerunningl4t_update_initrd.sh, and modules will fail to load with "disagrees about version of symbol …". All three failure modes are closed by/jetson-promote-image's gate on eitherkernel/Imageorrootfs/lib/modules/plus the kernel-Image mirror; surface drift here and route the user back to a clean promote. See../jetson-promote-image/SKILL.md.
On-target checks (if in scope):
Connect to the DUT per the
## DUT accesssection below — resolve transport (ssh / uart), credentials, and sudo method from the active profile'sdut_access:block (with interactive fallback when fields are missing / markedprompt), then run the connection probe and refuse if it fails.Confirm boot reached userspace.
Run the selected test suite (smoke, regression, focused per-customization, ad-hoc).
Loaded-module srcversion drift. For modules a customization is known to have rebuilt, compare
cat /sys/module/<name>/srcversionon the DUT against themodinfo /lib/modules/$(uname -r)/.../<name>.ko | awk '/srcversion/ {print $2}'reading. A mismatch means the kernel is running an older copy than the rootfs ships — almost always a stale initramfs (the bootloader-side initrd shipped a pre-customize module, it loaded first, and the rootfs copy cannot replace a live module). Recommend re-running/jetson-promote-imageand re-flashing. Note: some modules don't emitsrcversion; fall back to an md5 check against the binary the kernel loaded by extracting the region under/sys/module/<name>/sections/or by comparing behaviorally (printk / sysfs nodes / DT properties the new version is known to expose).Running kernel vs. rootfs kernel
Image. Comparecat /proc/version(oruname -v) on the DUT against theLinux version …string extracted from/boot/Image(strings /boot/Image | grep -m1 'Linux version'). A mismatch — usually the build timestamp /LOCALVERSION— means the bootloader is running an older kernelImagethan the rootfs holds, almost certainly because a freshImagewas promoted but the initramfs /extlinux.conf/ QSPI boot partition wasn't refreshed. Modules in the rootfs will then have a different vermagic and any subsequentmodprobeof a built-against-the-new-kernel.kowill fail. Recommend/jetson-promote-imageand re-flash.Userspace dmesg readability. Ubuntu 22.04 sets
kernel.dmesg_restrict=1; non-rootdmesgreads return "Operation not permitted" and silently zero hits. Everydmesg-based check must run withsudo(or temporarily lower the restriction viasudo sysctl kernel.dmesg_restrict=0). Surfacing this in the validate layer keeps printk-based customization checks honest.Collect results, logs, artifacts.
Summary: per-check pass/fail, overall verdict, where logs and artifacts landed.
DUT access
The on-target leg needs a way to reach the just-flashed DUT.
Two transports are supported as full peers: ssh (primary) and
uart (fallback for DUTs with no network).
The contract is locked in but lives in
references/dut-access.md to keep this
SKILL.md under the agent-routing budget. That reference covers:
The
dut_access:profile schema (ssh, uart, sudo, workdir).Resolution order (profile → env var → interactive prompt) with the full refusal-trigger table.
The mandatory connection probe (
uname -r+cat /etc/nv_tegra_release) and its output-validation rules.File transfer per transport (
scpvs. base64-over-tty, with the >100 KB warning).Sudo invocation matrix per
sudo.method× transport.UART implementation contract that
scripts/uart_session.pyhonors (state machines for login / exec / push / pull, exit codes, robustness notes).Security notes (password handling, host-key pinning).
Available Scripts
| Script | Purpose | Arguments |
|---|---|---|
scripts/uart_session.py | UART transport black box for the on-target leg: login, command exec (with optional sudo), and base64-over-tty file transfer. Replaces ssh when the DUT has no network or ssh is broken. | --tty <dev> [--baud <n>] --user <name> --password-env <ENVVAR> [--sudo-password-env <ENVVAR>] [--shell-prompt <regex>] [--lock-strategy refuse|wait] <probe|exec|push|pull> [...] |
Invocation (the skill calls scripts as a subprocess — run_script()
in agent-runtime terminology):
# run_script: probe the DUT over UART
DUT_UART_PASSWORD_ENV=DUT_UART_PWD \
DUT_UART_PWD="$(read -rs -p 'UART login pw: '; echo "$REPLY")" \
scripts/uart_session.py \
--tty /dev/ttyACM0 --baud 115200 \
--user ubuntu --password-env DUT_UART_PASSWORD_ENV \
probe
# run_script: exec a sudo command and capture exit code
scripts/uart_session.py --tty /dev/ttyACM0 --user ubuntu \
--password-env DUT_UART_PASSWORD_ENV \
--sudo-password-env DUT_SUDO_PWD \
exec --use-sudo 'dmesg | tail -200'The script's exit code is the contract — see the exit-code table in
UART implementation contract.
Examples
Static-only validation (no DUT needed):
/jetson-validate-image
> static checks only against the staged BSPOn-target validation over SSH after a freshly flashed DUT:
/jetson-flash-image
↓
/jetson-validate-image
> on-target checks via dut_access.sshOn-target validation over UART (no network on the DUT):
/jetson-validate-image
> use the uart transport at /dev/ttyACM0; the dut_access.uart block
in the profile already has the tty and login_password_env wired upLimitations
Placeholder skill — only the DUT-access contract and the
uart_session.pyhelper are locked in. The static-check list, test-suite selection, result-sink layout, and pass/fail policy are tracked under## Open itemsand may change.UART file transfer is byte-banged base64 at ~10 KB/s on 115200 baud — emits a warning for sources > 100 KB but proceeds. For high-volume transfers, switch to the SSH transport.
uart_session.pyopens and closes the tty per subcommand invocation (~1–2 s login per call). Validation passes running10 commands amortize poorly on UART; prefer SSH.
SSH uses
StrictHostKeyChecking=accept-newwith a per-profileknown_hostsfile. A fingerprint change refuses — typically means the DUT was reflashed (host keys regenerated) or the IP was reassigned. Remove the per-profile entry manually rather than auto-accepting.Passwords are never inlined in the profile YAML — only
password_env(env-var name) is persisted.auth=prompt/sudo.method=promptexposes the password in the conversation log, which is the user's responsibility to manage.transport=uartwithlock_strategy=stealis not implemented (would require sending control characters that could corrupt the holder's state).
Troubleshooting
| Error | Cause | Solution |
|---|---|---|
no DUT transport configured (refuse) | On-target scope requested but dut_access.transport unresolved across profile / env / interactive prompt | Author dut_access: in the active profile, or rerun with static-only scope. |
$PASSWORD_ENV is unset (refuse) | auth=password (or sudo.method=password) names an env var that isn't exported on the host | export <ENVVAR>=... before invoking the skill; do NOT inline the password in YAML. |
tty held by another process (refuse, exit 3) | lock_strategy=refuse and fuser reports another holder (minicom, picocom, getty) | Close the holding process (sudo fuser -k <tty> only if you know what's there), or rerun with lock_strategy=wait. |
pyserial import failed (exit 4) | UART transport selected but pyserial not installed in the skill's Python | apt install python3-serial or pip install pyserial. |
| SSH fingerprint refused | DUT's host keys changed since the per-profile known_hosts was pinned (typically a reflash) | Remove the matching line from <workspace>/target-platform/<profile-stem>.known_hosts and rerun — the new key will be accepted on first connect. |
login failed (exit 128) | UART probe couldn't match a login or shell prompt within timeout | Confirm the DUT is powered + booted to userspace; check --shell-prompt override if the DUT carries an unusual PS1; verify the --user matches a real account. |
DUT not booted from the just-flashed BSP (warn / refuse) | /etc/nv_tegra_release on the DUT doesn't match bsp_image.version | Re-run /jetson-flash-image and confirm the DUT actually power-cycled into the new BSP, not the previous one. |
sudo prompt detected but no sudo password configured (exit 130) | --use-sudo passed to uart_session.py exec but --sudo-password-env not set, and DUT user lacks NOPASSWD | Set sudo.method=password + sudo.password_env in the profile, or grant NOPASSWD on the DUT via /etc/sudoers.d/. |
command timed out (exit 129) | Long-running DUT command exceeded the script's timeout | Run the command directly via ssh transport, or split into shorter steps. |
References
references/dut-access.md— full DUT-access contract: profile schema, resolution order, probe, file transfer, sudo, UART implementation, security.../../context/target-platform-contract.md— target-platform contract.../../context/bsp-customization-workflow.md— Workspace edit protocol (this skill is the Deploy tail).../jetson-build-source/SKILL.md— Build builder; produces the artifacts this skill validates.
Files
- ATTRIBUTION.mdAdded by AutoGineer926 B
- BENCHMARK.md3.5 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md13.6 KiB
- evals/evals.json4.0 KiB
- references/dut-access.md15.0 KiB
- scripts/uart_session.pyScript25.0 KiB
- skill-card.md3.5 KiB
- skill.oms.sig4.9 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Python
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Jetson Team
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/jetson-validate-image · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Jetson Team or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download jetson-validate-image.zip