Skip to content
Back to skills

Fpga Debugging

ASecurity

On-chip debugging skill with ILA, VIO, and related FPGA debug tools

  • 1,760 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 2, 2026
ai-agentsbashdebugging

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add a5c-ai/babysitter --skill fpga-debugging --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fpga Debugging?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fpga Debugging
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/a5c-ai-fpga-debugging-babysitter/badge)](https://www.skillsdirectory.com/skills/a5c-ai-fpga-debugging-babysitter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: fpga-debugging
description: On-chip debugging skill with ILA, VIO, and related FPGA debug tools
allowed-tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - Bash
graph:
  domains: [domain:embedded-systems]
  specializations: [specialization:fpga-programming]
  skillAreas: [skill-area:hdl-design, skill-area:fpga-synthesis]
  roles: [role:embedded-engineer]
---

# 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

Files in this skill

  • README.md714 B
  • SKILL.md2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…