hsb-flash

Flash FPGA firmware on HSB Lattice boards and Leopard Imaging VB1940 cameras.

Updated Apr 16, 2026

Search Tags:#firmware #container #flash #FPGA #HSB #Lattice #VB1940

Ready to run

npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill hsb-flash

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hsb-flash
Source: https://github.com/sayalinvidia/sayali-skills-test/tree/main/skills/hsb-flash
Command: npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill hsb-flash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Flash FPGA firmware on HSB Lattice boards and Leopard Imaging VB1940 cameras connected to NVIDIA devkits, enabling safe, manifest-driven upgrades and downgrades.

Core Features & Use Cases

End-to-end flashing workflow including board detection, manifest handling, repo checkout, in-container execution, and results verification.
Supports HSB Lattice and VB1940 paths, single-step and two-step flashing (via gateway 2412) where applicable, with safety gates and user prompts.
Automatic handling of undocumented FPGA versions through release-notes lookups and session state tracking for cleanup.

Quick Start

Execute /hsb-flash with the desired options to begin the FPGA flashing workflow.

Frequently Asked Questions about hsb-flash

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I flash FPGA firmware on HSB Lattice boards connected to an NVIDIA devkit?▼

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.

Can I flash Leopard Imaging VB1940 cameras using this same manifest-driven process?▼

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.

Do I need a container environment to run the FPGA firmware flashing workflow?▼

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.

How does the flashing tool handle undocumented FPGA versions during an upgrade?▼

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.

What safety mechanisms are in place when downgrading FPGA firmware on HSB boards?▼

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.

What is the best way to verify results after flashing FPGA firmware on HSB Lattice boards?▼

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.