Best use case
fpga-debugging is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
On-chip debugging skill with ILA, VIO, and related FPGA debug tools
Teams using fpga-debugging should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/fpga-debugging/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How fpga-debugging Compares
| Feature / Agent | fpga-debugging | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
On-chip debugging skill with ILA, VIO, and related FPGA debug tools
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# FPGA Debugging Skill ## Overview Expert skill for on-chip debugging using Integrated Logic Analyzer (ILA), Virtual I/O (VIO), and related debug infrastructure for FPGA designs. ## Capabilities - Insert Integrated Logic Analyzer (ILA) probes - Configure trigger conditions and capture depth - Design Virtual I/O (VIO) debug interfaces - Analyze captured waveforms - Use ChipScope/SignalTap for debugging - Debug timing and functional issues in hardware - Remove debug logic for production builds - Configure JTAG and debug hub ## Target Processes - fpga-on-chip-debugging.js - functional-simulation.js - design-for-testability.js ## Usage Guidelines ### ILA Insertion - Identify critical signals to probe - Consider capture depth vs. resource usage - Group related signals in single ILA - Use mark_debug attribute for HDL signals - Configure appropriate data and trigger widths ### Trigger Configuration - Use basic triggers for simple conditions - Apply advanced triggers for complex patterns - Combine triggers with AND/OR logic - Configure trigger position in capture window - Use storage qualification for efficient capture ### VIO Usage - Create debug control interfaces - Inject test patterns dynamically - Override internal signals - Monitor status in real-time - Useful for bring-up and characterization ### Debug Infrastructure - Connect debug hub to JTAG - Configure clock domain for debug logic - Plan for multiple ILA instances - Consider debug access port routing - Document debug signal mapping ### Production Considerations - Use ifdef guards for debug logic - Create debug and release build flows - Minimize debug impact on timing - Remove debug before final release - Maintain debug build configurations ## Dependencies - Debug tool CLI (hw_server, etc.) - JTAG connectivity - Vendor debug IP knowledge
Related Skills
cuda-debugging
Expert skill for GPU debugging using CUDA-GDB and NVIDIA Compute Sanitizer. Detect memory errors, race conditions, uninitialized memory access, validate atomic operations, analyze kernel synchronization issues, and generate debugging reports with recommendations.
systematic-debugging
Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.
debugging-patterns
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.