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

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Path
  • CDC/RDC Glossary
  • CDC/RDC Metrics Reference
  • CDC/RDC Interview Prep
  • CDC/RDC Signoff Cheatsheet
  • Clock Domains and Failure Modes8
  • Metastability and Synchronizers16
  • CDC Protocols and Handshakes16
  • Reconvergence and Gray Coding16
  • Reset Domain Crossing16
  • Architecture and Design Rules16
  • CDC Signoff Methodology24
  • RDC Signoff16
  • Debug and Case Studies11
    • Reading a CDC Report
    • Classic Bug Anatomy
      • Lost Pulse Bug
      • Torn Bus Bug
      • FIFO Pointer Bug
      • Reset Release Bug
    • Case Studies
  • CDC and RDC Interview Prep30
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹Debug and Case Studies
  1. Topics
  2. CDC & RDC
  3. Debug and Case Studies
  4. Classic Bug Anatomy

Part 9 · Debug and Case Studies · Advanced

Classic Bug Anatomy

Four bugs that escape to silicon on every generation: the symptom, the waveform, the root cause, the finding that would have caught it, and the guard that stops it coming back.

  • 4topics
  • 4lessons

CDC bugs share a shape: silent in simulation, intermittent in the lab, obvious in hindsight. Each lesson below dissects one classic in the same six steps: symptom, what the waveform shows, root cause, the structural finding that would have caught it, the fix, and the regression guard. Learn the shape once and every new failure becomes a matching exercise.

Lesson

After it you can...

Lost Pulse Bug

Explain pulse-spacing violations and read the toggle-cancellation waveform.

Torn Bus Bug

Recognise tearing in debug data and name the structural finding behind it.

FIFO Pointer Bug

Trace wrong full and empty flags to a binary pointer crossing.

Reset Release Bug

Trace first-transaction corruption to release timing or ordering.

Two lessons carry simulated waveforms; the other two link to the lessons that already teach their mechanism and add only the debug angle, so nothing here repeats the course.

Check yourself What are the six steps of each dissection?

Symptom, waveform, root cause, the structural finding that would have caught it, fix, and regression guard.

Related topics

  • Bus Tearing

  • RTL: CDC Verification

PreviousNext: Lost Pulse Bug

Up next

Up nextLost Pulse Bug

Sign in to save progress

Practice this lessonReport an error

See also

  • Reading a CDC Report
  • Case Studies