rtl-debugging

Guide engineers from verification failures to RTL root causes.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MameMame777/FT4232Hmin --skill rtl-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rtl-debugging
Source: https://github.com/MameMame777/FT4232Hmin/tree/main/.github/skills/rtl-debugging
Command: npx skills add https://github.com/MameMame777/FT4232Hmin --skill rtl-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured methodology for debugging RTL designs, enabling engineers to identify and resolve failures in verification results, assertions, and scoreboards.

Core Features & Use Cases

  • Structured debugging workflow: trace failures from monitors and scoreboards to RTL signals and state machines.
  • Evidence-to-RTL mapping: categorize verification evidence into interface, datapath, and control issues and infer root causes.
  • Hypothesis-driven experiments: design minimal reproducers and targeted stimuli, plus assertion-driven isolation to validate fixes.
  • Workflow documentation: maintain traceable debugging notes linking test evidence to RTL changes.

Quick Start

Run a failing RTL simulation, collect waveform data, assertion outputs, and scoreboard results, then apply the RTL-debugging workflow to identify the root cause and create a minimal reproducer to verify the fix.

Frequently Asked Questions about rtl-debugging

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

FAQPage Schema
How do I debug RTL failures from simulation waveforms and UVM scoreboards?

To debug RTL failures, trace evidence from UVM scoreboards and waveforms to RTL signals, categorize issues into interface, datapath, or control domains, and infer root causes using hypothesis-driven experiments.

What is the best way to find the root cause of an RTL verification failure?

Finding the root cause of an RTL verification failure requires evidence-based tracing from test results to state machines, isolating the defect through assertion monitors, and generating minimal reproducers to validate the fix.

How do I create a minimal reproducer for an RTL bug found during simulation?

Create a minimal reproducer for an RTL bug by designing targeted stimuli based on waveform analysis and assertion-driven isolation, ensuring the reproducer accurately triggers the specific verification failure.

Can I use this RTL debugging workflow with UVM-based testbenches and assertion monitors?

Yes, this RTL debugging workflow applies directly to simulation-driven verification across UVM-based testbenches, waveform analysis, and assertion monitors to triage causes and map evidence to RTL fixes.

Why does my RTL debugging process lack traceability between test evidence and fixes?

Your RTL debugging process lacks traceability because it does not maintain structured debugging notes linking test evidence to RTL changes, which is required to enforce traceability from verification failures to fixes.

How do I triage RTL control and datapath issues from verification monitor outputs?

Triage RTL control and datapath issues by categorizing verification evidence from monitor outputs into interface, datapath, and control domains, then applying evidence-to-RTL mapping to infer the underlying root causes.