Fpga debugging
Skill a5c-ai/babysitter/library/specializations/fpga-programming/skills/fpga-debugging
Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration
npx -y skills add a5c-ai/babysitter --skill fpga-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
On-chip debugging skill with ILA, VIO, and related FPGA debug tools
SKILL.md
2.2 KB, as published. Nobody here has run it
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