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: Debug
On this page

    Interface ProtocolsAll levels

    Protocol Waveform Debug: Debug

    Debug for Protocol Waveform Debug.

    Primary debug scenario

    Symptom: AXI write timeout after 1000 cycles. VIP shows AW sent but no B response. Need to find why.

    Triage steps

    1. Waveform: AW channel — was AW accepted (awready)?

    2. W channel: did all W beats complete with WLAST?

    3. If W incomplete: find which beat stalled and why (wready?).

    4. If W complete but no B: check slave state machine.

    5. Correlate with VIP monitor timestamp for AW and W events.

    Common pitfalls

    • Debugging the timeout without finding first stalled channel.

    • Loading every signal — focus on relevant channels.

    • Not correlating waveform with VIP transaction log.

    Previous

    146 / 154

    Next: Protocol Waveform Debug: Interview

    Up next

    Up nextProtocol Waveform Debug: Interview

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Protocol Waveform Debug: Concepts