Agent skill · software engineering · nvidia
jetson-flash-image
Use to flash a promoted BSP image to a Jetson DUT in RCM mode via flash.sh or l4t_initrd_flash.sh. Do NOT use for BSP customization, image promotion, or carrier derivation.
Why this skill is useful
Provides specific commands and workflows for flashing BSP images to Jetson devices that are not commonly known or documented publicly.
What it needs
Requires nvidia-flashing-toolchain installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
Flash BSP Image Purpose Push a promoted bspimage to a Jetson DUT by running the NVIDIA flashing toolchain (flash.sh or l4tinitrdflash.sh) from the in-tree LinuxforTegra/. The DUT must be in RCM (recovery) mode at flash time. This is the flash leg of the BSP overlay deploy chain (/jetson-promote-image → /jetson-flash-image); see the BSP overlay workflow at ../../context/bsp-customization-workflow.md. Design principle. Four invariants govern this skill; each is fully explained in the Instructions step that owns it. Host-side flash variables (<board>, <boot-dev>, flow tool, per-board .conf, boardctl) are resolved from the active profile or the in-tree BSP. Artifact paths (DTBFILE, BPFDTBFILE, partition XML, BCTs, DRAM training) are resolved inside flash.sh / l4tinitrdflash.sh at flash time from boardsku / boardFAB read off the DUT's EEPROM. The DUT's EEPROM is authoritative; the profile is an authoring-time prediction reconciled by the preflight cross-check. Empty EEPROM values are valid, not refusal triggers. The user explicitly confirms a printed resolution before flashing. Out of scope: BSP customization (use the /jetson-customize- skills), promoting the overlay tracker into bspimage (use /jetson-promote-image), and producing a custom carrier's flash conf (use /jetson-derive-carrier). Prerequisites Active target-platform profile resolved per ../../context/target-platform-contract.md with a populated bspimage: block. Refuse and route to /jetson-init-image if missing. <bspimage.rootpath>/LinuxforTegra/ exists on the host and has been through applybinaries.sh (route to /jetson-init-image otherwise). A per-board flash .conf resolvable via the active-block precedence rule (customcarrier.flashconfig → referencedevkit.flashconfig). Refuse and route to /jetson-derive-carrier or /jetson-init-image if absent. For the prior overlay → image leg: /jetson-promote-image has already run (or a standalone re-flash with no promotion changes since the last flash). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/jetson-flash-image