OpenParable
Skip to content
← Back to skills

Fpga Debugging

Testing & Quality
fpga-debugging

Fpga Debugging is an Agent Skill for testing & quality published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/fpga-programming/skills/fpga-debugging/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/fpga-debugging, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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