[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPP3KET3Y4QS09YGCWYPQJ":3,"skill-same:01M7CPP3KET3Y4QS09YGCWYPQJ":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7CPP3KET3Y4QS09YGCWYPQJ","jetson-validate-image",null,"Use after jetson-flash-image to run static BSP checks, on-target smoke\u002Fregression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-validate-image\u002Fskills\u002Fjetson-validate-image\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-validate-image\ndescription: >-\n  Use after jetson-flash-image to run static BSP checks, on-target\n  smoke\u002Fregression tests on a flashed DUT, or both. Not for build\n  or flash steps. Triggers: validate bsp, on-target validation.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  data-classification: public\n  author: \"Jetson Team\"\n  tags:\n    - bsp\n    - validation\n    - test\n    - deploy\n  domain: meta\n---\n\n# Validate BSP Image\n\n> **Status:** the DUT-access contract is stable; the rest of the\n> validation procedure is a skeleton.\n\n## Purpose\n\nConfirm that a freshly customized BSP landed correctly — both as a\nstatic artifact on disk and as a running system on the target —\nwithout re-promoting or re-flashing. Forms the **validation tail of\nDeploy** in the Setup → Customize → Build → Deploy pipeline (see\n[`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md)\nfor the pipeline view) and is independently re-runnable.\n\n## Prerequisites\n\n- Active target-platform profile with `bsp_image:` resolved (run\n  `\u002Fjetson-init-image` first).\n- For static-only scope: nothing further; the skill reads\n  `\u003Cbsp_image.root_path>` directly.\n- For on-target scope:\n  - `\u002Fjetson-flash-image` already pushed the staged BSP to the DUT.\n  - `dut_access:` block authored in the active profile (or filled\n    interactively at runtime — see [`## DUT access`](#dut-access)).\n  - Host tooling per transport: `ssh` + `sshpass` for SSH; Python\n    3.6+ with `pyserial` for UART.\n  - Required env vars resolvable on the host when `auth=password`\n    or `sudo.method=password` (`password_env` \u002F `sudo.password_env`\n    name the env var; never inline the secret in YAML).\n\n## When to invoke\n\n- After `jetson-flash-image` has put the BSP onto a target.\n- The user explicitly asks to validate, test, or run smoke \u002F\n  regression checks on a flashed device.\n- As a CI gate before declaring a customization batch shippable.\n\n## Instructions\n\nThe procedure below is a skeleton.\n\n1. **Read the active target** per the prerequisite contract.\n2. **Choose validation scope** — static (against `bsp_image` on\n   disk, no DUT needed) and\u002For on-target (DUT must be booted\n   from the just-flashed image).\n3. **Static checks** (if in scope):\n     - Required artifacts present at expected paths in\n       `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F`.\n     - DTB \u002F module checksum or signature verification.\n     - Partition-layout sanity vs. the per-board `.conf`'s XML.\n     - Cross-check overlay-staged outputs against `bsp_image`\n       (they should be identical post-promotion).\n     - **Initramfs ↔ kernel + rootfs module coherence.** Extract\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Fbootloader\u002Fl4t_initrd.img` and\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Frootfs\u002Fboot\u002Finitrd`; verify\n       three invariants against the *promoted* `bsp_image` state:\n       (a) `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Fkernel\u002FImage` matches\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Frootfs\u002Fboot\u002FImage` byte-for-\n       byte — drift here means\n       [the \"Mirror kernel Image into rootfs\" step](..\u002Fjetson-promote-image\u002FSKILL.md#mirror-kernel-image-into-rootfs-when-kernel-changed)\n       was skipped and any subsequent initramfs refresh built\n       against the previous kernel.\n       (b) for each module path the two initrd images ship, the\n       bytes \u002F md5 match the file under\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Frootfs\u002Flib\u002Fmodules\u002F\u003Cver>\u002F` —\n       any drift means modules will be shadowed at early boot.\n       (c) the vermagic stamped on every initramfs `*.ko` matches\n       the `UTS_RELEASE` reachable from\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Fkernel\u002FImage` (e.g. parse the\n       `Linux version …` string with `strings`) — a vermagic skew\n       means the kernel `Image` was refreshed without rerunning\n       `l4t_update_initrd.sh`, and modules will fail to load with\n       \"disagrees about version of symbol …\". All three failure\n       modes are closed by `\u002Fjetson-promote-image`'s gate on\n       either `kernel\u002FImage` or `rootfs\u002Flib\u002Fmodules\u002F` plus the\n       kernel-Image mirror; surface drift here and route the user\n       back to a clean promote. See\n       [`..\u002Fjetson-promote-image\u002FSKILL.md`](..\u002Fjetson-promote-image\u002FSKILL.md#refresh-initramfs-when-kernel-or-modules-changed).\n4. **On-target checks** (if in scope):\n     - **Connect to the DUT** per the [`## DUT access`](#dut-access)\n       section below — resolve transport (ssh \u002F uart), credentials,\n       and sudo method from the active profile's `dut_access:`\n       block (with interactive fallback when fields are missing \u002F\n       marked `prompt`), then run the connection probe and refuse\n       if it fails.\n     - Confirm boot reached userspace.\n     - Run the selected test suite (smoke, regression, focused\n       per-customization, ad-hoc).\n     - **Loaded-module srcversion drift.** For modules a\n       customization is known to have rebuilt, compare\n       `cat \u002Fsys\u002Fmodule\u002F\u003Cname>\u002Fsrcversion` on the DUT against the\n       `modinfo \u002Flib\u002Fmodules\u002F$(uname -r)\u002F...\u002F\u003Cname>.ko | awk\n       '\u002Fsrcversion\u002F {print $2}'` reading. A mismatch means the\n       kernel is running an older copy than the rootfs ships —\n       almost always a stale initramfs (the bootloader-side initrd\n       shipped a pre-customize module, it loaded first, and the\n       rootfs copy cannot replace a live module). Recommend\n       re-running `\u002Fjetson-promote-image` and re-flashing. Note:\n       some modules don't emit `srcversion`; fall back to an md5\n       check against the binary the kernel loaded by extracting the\n       region under `\u002Fsys\u002Fmodule\u002F\u003Cname>\u002Fsections\u002F` or by comparing\n       behaviorally (printk \u002F sysfs nodes \u002F DT properties the new\n       version is known to expose).\n     - **Running kernel vs. rootfs kernel `Image`.** Compare\n       `cat \u002Fproc\u002Fversion` (or `uname -v`) on the DUT against the\n       `Linux version …` string extracted from\n       `\u002Fboot\u002FImage` (`strings \u002Fboot\u002FImage | grep -m1 'Linux version'`).\n       A mismatch — usually the build timestamp \u002F `LOCALVERSION` —\n       means the bootloader is running an older kernel `Image` than\n       the rootfs holds, almost certainly because a fresh `Image`\n       was promoted but the initramfs \u002F `extlinux.conf` \u002F QSPI\n       boot partition wasn't refreshed. Modules in the rootfs\n       will then have a different vermagic and any subsequent\n       `modprobe` of a built-against-the-new-kernel `.ko` will\n       fail. Recommend `\u002Fjetson-promote-image` and re-flash.\n     - **Userspace dmesg readability.** Ubuntu 22.04 sets\n       `kernel.dmesg_restrict=1`; non-root `dmesg` reads return\n       \"Operation not permitted\" and silently zero hits. Every\n       `dmesg`-based check must run with `sudo` (or temporarily\n       lower the restriction via `sudo sysctl\n       kernel.dmesg_restrict=0`). Surfacing this in the validate\n       layer keeps printk-based customization checks honest.\n     - Collect results, logs, artifacts.\n5. **Summary**: per-check pass\u002Ffail, overall verdict, where\n   logs and artifacts landed.\n\n## DUT access\n\nThe on-target leg needs a way to reach the just-flashed DUT.\nTwo transports are supported as full peers: `ssh` (primary) and\n`uart` (fallback for DUTs with no network).\n\nThe contract is locked in but lives in\n[`references\u002Fdut-access.md`](references\u002Fdut-access.md) to keep this\nSKILL.md under the agent-routing budget. That reference covers:\n\n- The `dut_access:` profile schema (ssh, uart, sudo, workdir).\n- Resolution order (profile → env var → interactive prompt) with\n  the full refusal-trigger table.\n- The mandatory connection probe (`uname -r` +\n  `cat \u002Fetc\u002Fnv_tegra_release`) and its output-validation rules.\n- File transfer per transport (`scp` vs. base64-over-tty, with\n  the >100 KB warning).\n- Sudo invocation matrix per `sudo.method` × transport.\n- UART implementation contract that `scripts\u002Fuart_session.py`\n  honors (state machines for login \u002F exec \u002F push \u002F pull, exit\n  codes, robustness notes).\n- Security notes (password handling, host-key pinning).\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|---|---|---|\n| `scripts\u002Fuart_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 \u003Cdev> [--baud \u003Cn>] --user \u003Cname> --password-env \u003CENVVAR> [--sudo-password-env \u003CENVVAR>] [--shell-prompt \u003Cregex>] [--lock-strategy refuse\\|wait] \u003Cprobe\\|exec\\|push\\|pull> [...]` |\n\nInvocation (the skill calls scripts as a subprocess — `run_script()`\nin agent-runtime terminology):\n\n```bash\n# run_script: probe the DUT over UART\nDUT_UART_PASSWORD_ENV=DUT_UART_PWD \\\nDUT_UART_PWD=\"$(read -rs -p 'UART login pw: '; echo \"$REPLY\")\" \\\n  scripts\u002Fuart_session.py \\\n    --tty \u002Fdev\u002FttyACM0 --baud 115200 \\\n    --user ubuntu --password-env DUT_UART_PASSWORD_ENV \\\n    probe\n\n# run_script: exec a sudo command and capture exit code\nscripts\u002Fuart_session.py --tty \u002Fdev\u002FttyACM0 --user ubuntu \\\n  --password-env DUT_UART_PASSWORD_ENV \\\n  --sudo-password-env DUT_SUDO_PWD \\\n  exec --use-sudo 'dmesg | tail -200'\n```\n\nThe script's exit code is the contract — see the exit-code table in\n[`UART implementation contract`](references\u002Fdut-access.md#uart-implementation-contract).\n\n## Examples\n\nStatic-only validation (no DUT needed):\n\n```\n\u002Fjetson-validate-image\n> static checks only against the staged BSP\n```\n\nOn-target validation over SSH after a freshly flashed DUT:\n\n```\n\u002Fjetson-flash-image\n   ↓\n\u002Fjetson-validate-image\n> on-target checks via dut_access.ssh\n```\n\nOn-target validation over UART (no network on the DUT):\n\n```\n\u002Fjetson-validate-image\n> use the uart transport at \u002Fdev\u002FttyACM0; the dut_access.uart block\n  in the profile already has the tty and login_password_env wired up\n```\n\n## Limitations\n\n- Placeholder skill — only the DUT-access contract and the\n  `uart_session.py` helper are locked in. The static-check list,\n  test-suite selection, result-sink layout, and pass\u002Ffail policy\n  are tracked under `## Open items` and may change.\n- UART file transfer is byte-banged base64 at ~10 KB\u002Fs on 115200\n  baud — emits a warning for sources > 100 KB but proceeds. For\n  high-volume transfers, switch to the SSH transport.\n- `uart_session.py` opens and closes the tty per subcommand\n  invocation (~1–2 s login per call). Validation passes running\n  > 10 commands amortize poorly on UART; prefer SSH.\n- SSH uses `StrictHostKeyChecking=accept-new` with a per-profile\n  `known_hosts` file. A fingerprint change refuses — typically\n  means the DUT was reflashed (host keys regenerated) or the IP\n  was reassigned. Remove the per-profile entry manually rather\n  than auto-accepting.\n- Passwords are never inlined in the profile YAML — only\n  `password_env` (env-var name) is persisted. `auth=prompt` \u002F\n  `sudo.method=prompt` exposes the password in the conversation\n  log, which is the user's responsibility to manage.\n- `transport=uart` with `lock_strategy=steal` is **not implemented**\n  (would require sending control characters that could corrupt the\n  holder's state).\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|---|---|---|\n| `no DUT transport configured` (refuse) | On-target scope requested but `dut_access.transport` unresolved across profile \u002F env \u002F interactive prompt | Author `dut_access:` in the active profile, or rerun with static-only scope. |\n| `$PASSWORD_ENV is unset` (refuse) | `auth=password` (or `sudo.method=password`) names an env var that isn't exported on the host | `export \u003CENVVAR>=...` before invoking the skill; do NOT inline the password in YAML. |\n| `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 \u003Ctty>` only if you know what's there), or rerun with `lock_strategy=wait`. |\n| `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`. |\n| SSH fingerprint refused | DUT's host keys changed since the per-profile `known_hosts` was pinned (typically a reflash) | Remove the matching line from `\u003Cworkspace>\u002Ftarget-platform\u002F\u003Cprofile-stem>.known_hosts` and rerun — the new key will be accepted on first connect. |\n| `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. |\n| `DUT not booted from the just-flashed BSP` (warn \u002F refuse) | `\u002Fetc\u002Fnv_tegra_release` on the DUT doesn't match `bsp_image.version` | Re-run `\u002Fjetson-flash-image` and confirm the DUT actually power-cycled into the new BSP, not the previous one. |\n| `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 `\u002Fetc\u002Fsudoers.d\u002F`. |\n| `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. |\n\n## References\n\n- [`references\u002Fdut-access.md`](references\u002Fdut-access.md) — full DUT-access contract: profile schema, resolution order, probe, file transfer, sudo, UART implementation, security.\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md) — target-platform contract.\n- [`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants) — Workspace edit protocol (this skill is the Deploy tail).\n- [`..\u002Fjetson-build-source\u002FSKILL.md`](..\u002Fjetson-build-source\u002FSKILL.md) — Build builder; produces the artifacts this skill validates.\n","# Validate BSP Image\n\n> **Status:** the DUT-access contract is stable; the rest of the\n> validation procedure is a skeleton.\n\n## Purpose\n\nConfirm that a freshly customized BSP landed correctly — both as a\nstatic artifact on disk and as a running system on the target —\nwithout re-promoting or re-flashing. Forms the **validation tail of\nDeploy** in the Setup → Customize → Build → Deploy pipeline (see\n[`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md)\nfor the pipeline view) and is independently re-runnable.\n\n## Prerequisites\n\n- Active target-platform profile with `bsp_image:` resolved (run\n  `\u002Fjetson-init-image` first).\n- For static-only scope: nothing further; the skill reads\n  `\u003Cbsp_image.root_path>` directly.\n- For on-target scope:\n  - `\u002Fjetson-flash-image` already pushed the staged BSP to the DUT.\n  - `dut_access:` block authored in the active profile (or filled\n    interactively at runtime — see [`## DUT access`](#dut-access)).\n  - Host tooling per transport: `ssh` + `sshpass` for SSH; Python\n    3.6+ with `pyserial` for UART.\n  - Required env vars resolvable on the host when `auth=password`\n    or `sudo.method=password` (`password_env` \u002F `sudo.password_env`\n    name the env var; never inline the secret in YAML).\n\n## When to invoke\n\n- After `jetson-flash-image` has put the BSP onto a target.\n- The user explicitly asks to validate, test, or run smoke \u002F\n  regression checks on a flashed device.\n- As a CI gate before declaring a customization batch shippable.\n\n## Instructions\n\nThe procedure below is a skeleton.\n\n1. **Read the active target** per the prerequisite contract.\n2. **Choose validation scope** — static (against `bsp_image` on\n   disk, no DUT needed) and\u002For on-target (DUT must be booted\n   from the just-flashed image).\n3. **Static checks** (if in scope):\n     - Required artifacts present at expected paths in\n       `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F`.\n     - DTB \u002F module checksum or signature verification.\n     - Partition-layout sanity vs. the per-board `.conf`'s XML.\n     - Cross-check overlay-staged outputs against `bsp_image`\n       (they should be identical post-promotion).\n     - **Initramfs ↔ kernel + rootfs module coherence.** Extract\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Fbootloader\u002Fl4t_initrd.img` and\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Frootfs\u002Fboot\u002Finitrd`; verify\n       three invariants against the *promoted* `bsp_image` state:\n       (a) `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Fkernel\u002FImage` matches\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Frootfs\u002Fboot\u002FImage` byte-for-\n       byte — drift here means\n       [the \"Mirror kernel Image into rootfs\" step](..\u002Fjetson-promote-image\u002FSKILL.md#mirror-kernel-image-into-rootfs-when-kernel-changed)\n       was skipped and any subsequent initramfs refresh built\n       against the previous kernel.\n       (b) for each module path the two initrd images ship, the\n       bytes \u002F md5 match the file under\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Frootfs\u002Flib\u002Fmodules\u002F\u003Cver>\u002F` —\n       any drift means modules will be shadowed at early boot.\n       (c) the vermagic stamped on every initramfs `*.ko` matches\n       the `UTS_RELEASE` reachable from\n       `\u003Cbsp_image>\u002FLinux_for_Tegra\u002Fkernel\u002FImage` (e.g. parse the\n       `Linux version …` string with `strings`) — a vermagic skew\n       means the kernel `Image` was refreshed without rerunning\n       `l4t_update_initrd.sh`, and modules will fail to load with\n       \"disagrees about version of symbol …\". All three failure\n       modes are closed by `\u002Fjetson-promote-image`'s gate on\n       either `kernel\u002FImage` or `rootfs\u002Flib\u002Fmodules\u002F` plus the\n       kernel-Image mirror; surface drift here and route the user\n       back to a clean promote. See\n       [`..\u002Fjetson-promote-image\u002FSKILL.md`](..\u002Fjetson-promote-image\u002FSKILL.md#refresh-initramfs-when-kernel-or-modules-changed).\n4. **On-target checks** (if in scope):\n     - **Connect to the DUT** per the [`## DUT access`](#dut-access)\n       section below — resolve transport (ssh \u002F uart), credentials,\n       and sudo method from the active profile's `dut_access:`\n       block (with interactive fallback when fields are missing \u002F\n       marked `prompt`), then run the connection probe and refuse\n       if it fails.\n     - Confirm boot reached userspace.\n     - Run the selected test suite (smoke, regression, focused\n       per-customization, ad-hoc).\n     - **Loaded-module srcversion drift.** For modules a\n       customization is known to have rebuilt, compare\n       `cat \u002Fsys\u002Fmodule\u002F\u003Cname>\u002Fsrcversion` on the DUT against the\n       `modinfo \u002Flib\u002Fmodules\u002F$(uname -r)\u002F...\u002F\u003Cname>.ko | awk\n       '\u002Fsrcversion\u002F {print $2}'` reading. A mismatch means the\n       kernel is running an older copy than the rootfs ships —\n       almost always a stale initramfs (the bootloader-side initrd\n       shipped a pre-customize module, it loaded first, and the\n       rootfs copy cannot replace a live module). Recommend\n       re-running `\u002Fjetson-promote-image` and re-flashing. Note:\n       some modules don't emit `srcversion`; fall back to an md5\n       check against the binary the kernel loaded by extracting the\n       region under `\u002Fsys\u002Fmodule\u002F\u003Cname>\u002Fsections\u002F` or by comparing\n       behaviorally (printk \u002F sysfs nodes \u002F DT properties the new\n       version is known to expose).\n     - **Running kernel vs. rootfs kernel `Image`.** Compare\n       `cat \u002Fproc\u002Fversion` (or `uname -v`) on the DUT against the\n       `Linux version …` string extracted from\n       `\u002Fboot\u002FImage` (`strings \u002Fboot\u002FImage | grep -m1 'Linux version'`).\n       A mismatch — usually the build timestamp \u002F `LOCALVERSION` —\n       means the bootloader is running an older kernel `Image` than\n       the rootfs holds, almost certainly because a fresh `Image`\n       was promoted but the initramfs \u002F `extlinux.conf` \u002F QSPI\n       boot partition wasn't refreshed. Modules in the rootfs\n       will then have a different vermagic and any subsequent\n       `modprobe` of a built-against-the-new-kernel `.ko` will\n       fail. Recommend `\u002Fjetson-promote-image` and re-flash.\n     - **Userspace dmesg readability.** Ubuntu 22.04 sets\n       `kernel.dmesg_restrict=1`; non-root `dmesg` reads return\n       \"Operation not permitted\" and silently zero hits. Every\n       `dmesg`-based check must run with `sudo` (or temporarily\n       lower the restriction via `sudo sysctl\n       kernel.dmesg_restrict=0`). Surfacing this in the validate\n       layer keeps printk-based customization checks honest.\n     - Collect results, logs, artifacts.\n5. **Summary**: per-check pass\u002Ffail, overall verdict, where\n   logs and artifacts landed.\n\n## DUT access\n\nThe on-target leg needs a way to reach the just-flashed DUT.\nTwo transports are supported as full peers: `ssh` (primary) and\n`uart` (fallback for DUTs with no network).\n\nThe contract is locked in but lives in\n[`references\u002Fdut-access.md`](references\u002Fdut-access.md) to keep this\nSKILL.md under the agent-routing budget. That reference covers:\n\n- The `dut_access:` profile schema (ssh, uart, sudo, workdir).\n- Resolution order (profile → env var → interactive prompt) with\n  the full refusal-trigger table.\n- The mandatory connection probe (`uname -r` +\n  `cat \u002Fetc\u002Fnv_tegra_release`) and its output-validation rules.\n- File transfer per transport (`scp` vs. base64-over-tty, with\n  the >100 KB warning).\n- Sudo invocation matrix per `sudo.method` × transport.\n- UART implementation contract that `scripts\u002Fuart_session.py`\n  honors (state machines for login \u002F exec \u002F push \u002F pull, exit\n  codes, robustness notes).\n- Security notes (password handling, host-key pinning).\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|---|---|---|\n| `scripts\u002Fuart_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 \u003Cdev> [--baud \u003Cn>] --user \u003Cname> --password-env \u003CENVVAR> [--sudo-password-env \u003CENVVAR>] [--shell-prompt \u003Cregex>] [--lock-strategy refuse\\|wait] \u003Cprobe\\|exec\\|push\\|pull> [...]` |\n\nInvocation (the skill calls scripts as a subprocess — `run_script()`\nin agent-runtime terminology):\n\n```bash\n# run_script: probe the DUT over UART\nDUT_UART_PASSWORD_ENV=DUT_UART_PWD \\\nDUT_UART_PWD=\"$(read -rs -p 'UART login pw: '; echo \"$REPLY\")\" \\\n  scripts\u002Fuart_session.py \\\n    --tty \u002Fdev\u002FttyACM0 --baud 115200 \\\n    --user ubuntu --password-env DUT_UART_PASSWORD_ENV \\\n    probe\n\n# run_script: exec a sudo command and capture exit code\nscripts\u002Fuart_session.py --tty \u002Fdev\u002FttyACM0 --user ubuntu \\\n  --password-env DUT_UART_PASSWORD_ENV \\\n  --sudo-password-env DUT_SUDO_PWD \\\n  exec --use-sudo 'dmesg | tail -200'\n```\n\nThe script's exit code is the contract — see the exit-code table in\n[`UART implementation contract`](references\u002Fdut-access.md#uart-implementation-contract).\n\n## Examples\n\nStatic-only validation (no DUT needed):\n\n```\n\u002Fjetson-validate-image\n> static checks only against the staged BSP\n```\n\nOn-target validation over SSH after a freshly flashed DUT:\n\n```\n\u002Fjetson-flash-image\n   ↓\n\u002Fjetson-validate-image\n> on-target checks via dut_access.ssh\n```\n\nOn-target validation over UART (no network on the DUT):\n\n```\n\u002Fjetson-validate-image\n> use the uart transport at \u002Fdev\u002FttyACM0; the dut_access.uart block\n  in the profile already has the tty and login_password_env wired up\n```\n\n## Limitations\n\n- Placeholder skill — only the DUT-access contract and the\n  `uart_session.py` helper are locked in. The static-check list,\n  test-suite selection, result-sink layout, and pass\u002Ffail policy\n  are tracked under `## Open items` and may change.\n- UART file transfer is byte-banged base64 at ~10 KB\u002Fs on 115200\n  baud — emits a warning for sources > 100 KB but proceeds. For\n  high-volume transfers, switch to the SSH transport.\n- `uart_session.py` opens and closes the tty per subcommand\n  invocation (~1–2 s login per call). Validation passes running\n  > 10 commands amortize poorly on UART; prefer SSH.\n- SSH uses `StrictHostKeyChecking=accept-new` with a per-profile\n  `known_hosts` file. A fingerprint change refuses — typically\n  means the DUT was reflashed (host keys regenerated) or the IP\n  was reassigned. Remove the per-profile entry manually rather\n  than auto-accepting.\n- Passwords are never inlined in the profile YAML — only\n  `password_env` (env-var name) is persisted. `auth=prompt` \u002F\n  `sudo.method=prompt` exposes the password in the conversation\n  log, which is the user's responsibility to manage.\n- `transport=uart` with `lock_strategy=steal` is **not implemented**\n  (would require sending control characters that could corrupt the\n  holder's state).\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|---|---|---|\n| `no DUT transport configured` (refuse) | On-target scope requested but `dut_access.transport` unresolved across profile \u002F env \u002F interactive prompt | Author `dut_access:` in the active profile, or rerun with static-only scope. |\n| `$PASSWORD_ENV is unset` (refuse) | `auth=password` (or `sudo.method=password`) names an env var that isn't exported on the host | `export \u003CENVVAR>=...` before invoking the skill; do NOT inline the password in YAML. |\n| `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 \u003Ctty>` only if you know what's there), or rerun with `lock_strategy=wait`. |\n| `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`. |\n| SSH fingerprint refused | DUT's host keys changed since the per-profile `known_hosts` was pinned (typically a reflash) | Remove the matching line from `\u003Cworkspace>\u002Ftarget-platform\u002F\u003Cprofile-stem>.known_hosts` and rerun — the new key will be accepted on first connect. |\n| `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. |\n| `DUT not booted from the just-flashed BSP` (warn \u002F refuse) | `\u002Fetc\u002Fnv_tegra_release` on the DUT doesn't match `bsp_image.version` | Re-run `\u002Fjetson-flash-image` and confirm the DUT actually power-cycled into the new BSP, not the previous one. |\n| `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 `\u002Fetc\u002Fsudoers.d\u002F`. |\n| `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. |\n\n## References\n\n- [`references\u002Fdut-access.md`](references\u002Fdut-access.md) — full DUT-access contract: profile schema, resolution order, probe, file transfer, sudo, UART implementation, security.\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md) — target-platform contract.\n- [`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants) — Workspace edit protocol (this skill is the Deploy tail).\n- [`..\u002Fjetson-build-source\u002FSKILL.md`](..\u002Fjetson-build-source\u002FSKILL.md) — Build builder; produces the artifacts this skill validates.\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":31,"domain":32,"data-classification":33},[27,28,29,30],"bsp","validation","test","deploy","Jetson Team","meta","public","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fnvidia-skills\u002Fjetson-validate-image\u002Fskills\u002Fjetson-validate-image",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill jetson-validate-image",{"tool":48,"command":49},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill jetson-validate-image",{"tool":51,"command":52},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill jetson-validate-image","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-validate-image\u002Fskills\u002Fjetson-validate-image\u002FSKILL.md",true,[],[57,65,70,77,82,89],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":66,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":78,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":90,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]