xwave

Analyze hardware waveform traces and RTL source to diagnose simulation failures.

7|Updated May 22, 2026
One-click install
npx skills add https://github.com/Dimen01/skills --skill xwave
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xwave
Source: https://github.com/Dimen01/skills/tree/main/skills/xwave
Command: npx skills add https://github.com/Dimen01/skills --skill xwave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of debugging hardware simulation failures by providing a structured, evidence-based workflow for analyzing waveforms, bus protocols, and RTL signal behavior.

Core Features & Use Cases

  • Protocol Debugging: Specialized playbooks for diagnosing AXI and APB bus hangs, timeouts, and handshake stalls.
  • RTL Correlation: Connects waveform symptoms directly to source code, emitted RTL, or module hierarchy to identify root causes.
  • Use Case: When a simulation hangs due to an AXI write timeout, use this skill to trace the valid/ready signals, identify the stall timestamp, and correlate the behavior with the relevant RTL module to determine if the issue is a state machine deadlock or a data hazard.

Quick Start

Use the xwave skill to load the waveform at path/to/simulation.fsdb and analyze the AXI bus signals for the suspected stall at the specified timestamp.

Frequently Asked Questions about xwave

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

FAQPage Schema
How do I debug an AXI bus hang in my hardware simulation waveform?

To debug an AXI bus hang in your hardware simulation waveform, you trace the valid and ready handshake signals to identify the stall timestamp, then correlate the behavior with the relevant RTL module to determine if the issue is a state machine deadlock or data hazard.

How do I correlate RTL source code with simulation waveform anomalies?

Correlating RTL source code with waveform anomalies involves connecting observed signal behavior symptoms directly to the emitted RTL or module hierarchy to identify root causes during hardware simulation failures.

Can I diagnose APB protocol timeouts using structured waveform data?

Yes, you can diagnose APB protocol timeouts using structured waveform data by applying specialized playbooks to analyze bus handshake stalls and correlate them with the RTL hierarchy.

How do I identify the root cause of a state machine deadlock in an RTL simulation?

To identify the root cause of a state machine deadlock in an RTL simulation, you analyze the hardware waveform traces to trace signal behavior anomalies and verify state transitions against the RTL source code.

Do I need RTL source roots to perform hardware waveform debugging?

You do not strictly need RTL source roots to perform hardware waveform debugging, but providing them enables high-confidence root-cause analysis by correlating waveform symptoms directly with the source code.