hsb-flash

Flashing FPGA firmware on HSB Lattice boards is handled through an automated workflow that detects hardware, selects target versions, and executes the flash inside a container. It uses bundled manifests and safety gates to ensure reliable upgrades and downgrades on NVIDIA devkits.

Yes, flashing Leopard Imaging VB1940 cameras is supported alongside HSB Lattice boards. The process handles board detection, manifest handling, and in-container execution for both hardware paths, including single-step and two-step flashing where applicable.

Yes, the FPGA flashing workflow executes inside a containerized environment using bundled flash tools. This containerized execution ensures end-to-end reliability and safety checks during board detection, target version selection, and post-flash cleanup.

Undocumented FPGA versions are managed through automatic release-notes lookups during the flashing workflow. The system tracks these versions using session state to ensure proper cleanup and maintain reliability after the flash execution.

Flashing safety is enforced through gated user prompts, safety checks, and session state tracking. These mechanisms coordinate board detection, repo checkout, and inside-container execution to prevent errors during firmware downgrades or upgrades.

Results verification is a built-in step in the FPGA flashing workflow that runs after in-container execution completes. It automatically validates the flash operation alongside post-flash cleanup to confirm the HSB Lattice board or VB1940 camera was successfully updated.