Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
Passed 22 of 25 test cases with the skill, and 12 of 25 without it.
and 9 more in the full report
10 fixed12 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Host preflight check for `Linux_for_Tegra` finds the folder exists, but `rootfs/etc/nv_tegra_release` is missing because binary packages were not applied. What action should be taken?
| Checked | Without skill | With skill |
|---|---|---|
| Refuses preflight due to missing nv_tegra_release and routes to jetson-init-image. | Missed | Passed |
The instructions your model reads when the skill loads.
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/bsp-customization-workflow.md.
Design principle. Four invariants govern this skill; each is fully explained in the Instructions step that owns it.
<board>, <boot-dev>, flow tool, per-board .conf, boardctl) are resolved from the active profile or the in-tree BSP.DTB_FILE, BPFDTB_FILE, partition XML, BCTs, DRAM training) are resolved inside flash.sh / l4t_initrd_flash.sh at flash time from board_sku / board_FAB read off the DUT's EEPROM.Out of scope: BSP customization (use the /jetson-customize-* skills), promoting the overlay tracker into bsp_image (use /jetson-promote-image), and producing a custom carrier's flash conf (use /jetson-derive-carrier).
../../context/target-platform-contract.md with a populated bsp_image: block. Refuse and route to /jetson-init-image if missing.<bsp_image.root_path>/Linux_for_Tegra/ exists on the host and has been through apply_binaries.sh (route to /jetson-init-image otherwise)..conf resolvable via the active-block precedence rule (custom_carrier.flash_config → reference_devkit.flash_config). Refuse and route to /jetson-derive-carrier or /jetson-init-image if absent./jetson-promote-image has already run (or a standalone re-flash with no promotion changes since the last flash).boardctl or by manual recovery + reset buttons./jetson-promote-image has updated bsp_image to carry the desired customizations.bsp_imageResolve the active profile per
../../context/target-platform-contract.md.
Refuse if bsp_image: is missing or <bsp_image.root_path>/Linux_for_Tegra/
does not exist (route the user to /jetson-init-image).
test cases passed, vs 12 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.