hsb-flash

This skill flashes the FPGA firmware on an NVIDIA Holoscan Sensor Bridge board connected to a supported devkit. It supports two board types — HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 all-in-one cameras (FPGA versions 2507, 2510) — using release-specific YAML manifests and board-type-specific program commands, and handles both single-step and two-step (via gateway 2412) upgrade paths. It solves the tricky, hardware-critical task of upgrading or downgrading FPGA firmware safely and with the correct release tooling.

Because the operation permanently modifies firmware, the skill is built around strong safety gates. It states repeatedly that Lattice and VB1940 program commands must never be mixed, because using the wrong tool on a board can permanently brick the device, and it must detect and confirm board type before any flash and refuse if the type is ambiguous. It requires SSH_TARGET and REMOTE_ROOT, runs a mandatory token-budget preflight (reserving conservative token budgets so the workflow cannot run out mid-flash), and walks through phases for connectivity and board-type detection, target-version selection, infrastructure and YAML preparation, flash execution with power-cycle verification, a summary report, and artifact cleanup. Every action requires explicit user confirmation, model invocation is disabled, and force flags cannot bypass the preflight.

It targets NVIDIA Holoscan hardware engineers and integrators performing FPGA firmware upgrades or downgrades on sensor bridge boards. The genuine risk here is inherent to the task rather than the skill's design: firmware flashing is a destructive, hardware-modifying operation that can brick a device if misapplied, which is why the skill surrounds it with detection, confirmation, and refusal safeguards.