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/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 (
,
, flow tool, per-board
.conf
,
boardctl
) are resolved from the active profile or the in-tree BSP.
Artifact paths (
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.
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
bsp_image
(use
/jetson-promote-image
), and producing a custom carrier's flash conf (use
/jetson-derive-carrier
).
Prerequisites
Show more
Installs
700
Repository
nvidia/skills
GitHub Stars
2.4K
First Seen
Jun 22, 2026
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Warn