Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Protocol Metrics Reference
  • Protocols Glossary
  • Reading Path
  • Protocol Fundamentals25
  • AMBA Family (APB / AHB / AXI)17
  • Coherence Fabrics (ACE / CHI)17
  • Memory Interfaces (DDR / LPDDR / HBM)17
  • PCIe & CXL17
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
  • Protocol Verification & Compliance17
    • VIP & Agent Architecture
    • Scoreboard & Checker Strategy
    • Compliance & Coverage Plan
    • Protocol Waveform Debug
      • Protocol Waveform Debug: Concepts
      • Protocol Waveform Debug: Integration
      • Protocol Waveform Debug: Debug
      • Protocol Waveform Debug: Interview
    • Protocol Verification & Compliance: Tricky Q&A
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Protocol Waveform Debug
  1. Topics
  2. Bus Protocols
  3. Protocol Verification & Compliance
  4. Protocol Waveform Debug
  5. Protocol Waveform Debug: Concepts
On this page

    Interface ProtocolsAll levels

    Protocol Waveform Debug: Concepts

    Concepts for Protocol Waveform Debug.

    Core concepts

    Waveform debug methodology

    Start from the failure symptom. Identify the interface. Load waveform with protocol-relevant signals (not every signal in the design). Annotate transaction boundaries using VIP monitor or manual trace.

    Scroll backward from the failure to find the earliest observed point where progress stopped or behaviour diverged from the stated expectation. The timeout 1000 cycles later is an observation; the causal dependency may begin earlier or outside the captured boundary.

    • Signal grouping: one group per channel (AR, AW, W, R, B for AXI).

    • Marker: tag the failing transaction's ID and timestamp.

    • Compare failing vs passing waveform side-by-side.

    Correlating across views

    Waveform shows signals. VIP monitor shows transactions. Firmware log shows software actions. Analyzer shows external protocol view. Align timestamps across all views for the same transaction.

    A signal-level view without transaction context is guesswork. A transaction log without signal correlation can't find the RTL bug.

    • Export VIP monitor to CSV — overlay with waveform markers.

    • Simulation: $display or transaction recording at key points.

    • Silicon: logic analyzer on external pins + on-chip trace buffer.

    Key takeaways

    • Signal grouping: one group per channel (AR, AW, W, R, B for AXI).

    • Marker: tag the failing transaction's ID and timestamp.

    • Compare failing vs passing waveform side-by-side.

    Previous

    144 / 154

    Next: Protocol Waveform Debug: Integration

    Up next

    Up nextProtocol Waveform Debug: Integration

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Protocol Waveform Debug: Debug
    • Protocol Waveform Debug: Interview