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.
npx skills add NVIDIA/skills --skill jetson-flash-image --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Push a promoted bsp_image to a Jetson DUT by running the NVIDIA flashing toolchain (flash.sh or l4t_initrd_flash.sh) from the in-tree Linux_for_Tegra/. The DUT must be in RCM mode at flash time. It handles selecting the target, flash configuration, and the appropriate flash tool, acting as the flash leg of the BSP overlay deploy chain.
How it works
- Resolve the active target platform profile and require bsp_image root path existence. If missing, route to jetson-init-image.
- Resolve the per-board flash configuration file using active-block precedence (custom_carrier.flash_config or reference_devkit.flash_config) and verify existence under bsp_image/Linux_for_Tegra/. Refuse if absent and route accordingly.
- Bind <board> as the basename of the resolved .conf minus .conf, to be consumed by the flash command.
- During flash-time, flash.sh / l4t_initrd_flash.sh will determine artifacts like DTB_FILE, BPFDTB_FILE, partition XML, MB1 BCTs, DRAM training from EEPROM values (board_sku / board_FAB) read from the DUT in recovery mode.
- Ensure DUT is in RCM mode via boardctl or manual recovery, verifying recovery VID:PID. If not in RCM, refuse downstream flow.
- Perform a sequence of preflight checks, including bsp_image readiness, RCM mode verification, EEPROM cross-check vs profile, and default user staging if needed.
- After confirming resolution, construct and execute the flash command: cd bsp_image/Linux_for_Tegra; sudo ./<flow-tool> [flags] <board> <boot-dev>.
- For T26x/Thor, perform a post-flash reset with boardctl -t <target> reset; for T23x/Orin, reset is internal.
When to use it
- After /jetson-promote-image has updated bsp_image to carry desired customizations.
- Standalone re-flash with no promotion changes since last flash.
- DUT must be in RCM mode before invocation.
What it can touch
- The host-side workspace under <bsp_image.root_path>/Linux_for_Tegra/ where flash.sh / l4t_initrd_flash.sh operate.
- It relies on per-board flash conf, located as <bsp_image.root_path>/Linux_for_Tegra/<flash_config>.
- The process uses boardctl path resolved from the recovery mode procedure.
Caveats
- DUT must be in RCM mode; otherwise image generation and flash will fail.
- Artifact paths are resolved at flash time by flash.sh / l4t_initrd_flash.sh from EEPROM and not by this skill.
- EEPROM is authoritative over the profile; non-empty disagreements refuse.
- No raw-command bypass: cannot bypass the guided flow by pasting commands.
- USB hiccups abort the flow with no automatic retry.
- Post-flash reset is required for T26x; T23x resets internally.
# Flash BSP Image ## Purpose Push a promoted `bsp_image` to a Jetson DUT by running the NVIDIA flashing toolchain (`flash.sh` or `l4t_initrd_flash.sh`) from the in-tree `Linux_for_Tegra/`. 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/b
What does the jetson-flash-image skill do?
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.
How do I install it?
Run `npx skills add NVIDIA/skills --skill jetson-flash-image --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.