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
  • CDC and RDC Interview Prep30
    • CDC/RDC Whiteboard Framework
      • The Answer Framework
      • Drawing a Crossing
      • Naming the Failure Mode
      • Grading Rubric
    • CDC/RDC Framework Drills
    • Scenario: Metastability Bug
    • Scenario: Metastability Escape in Silicon Bring-up
    • Scenario: Async FIFO Pointer Mismatch
    • Scenario: Waiver Debate
    • Scenario: RDC Waiver Under Tapeout Pressure
    • CDC/RDC Interview Q&A Bank
    • CDC/RDC Interview Q&A Bank (Expanded)
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹CDC/RDC Whiteboard Framework
  1. Topics
  2. CDC & RDC
  3. CDC and RDC Interview Prep
  4. CDC/RDC Whiteboard Framework
  5. Naming the Failure Mode

Part 10 · Interview Prep · All levels

Naming the Failure Mode

Say which of the five failure modes you are solving before proposing any fix.

On this page

    Strong candidates name the failure mode in their first or second sentence; weak candidates propose a fix for an unnamed problem. Naming it first does three things: it proves you diagnosed rather than guessed, it constrains which fixes are legal, and it tells the interviewer which follow-up to ask, which keeps you on ground you chose.

    The five names and their fix families

    Failure mode

    One-sentence mechanism

    Fix family

    Metastability escape

    Capture flop resolves late and fans different values to downstream logic.

    Legal synchroniser: two or three flops, no logic between them.

    Lost event

    A fast pulse falls between two slow sampling edges.

    Toggle or stretch synchroniser, or handshake.

    Duplicated event

    A slow level spans two fast edges and is counted twice.

    Edge detect after synchronising, or handshake.

    Torn bus

    Several bits change at once and the destination mixes old and new.

    Gray code, handshake, FIFO, or qualified quasi-static capture.

    Stale data

    Destination captures before the new data has settled.

    Hold data until acknowledged; handshake or FIFO discipline.

    The mapping is many-to-one in reverse: one fix family can cover several modes, but one mode never accepts every fix. A two-flop synchroniser answers metastability escape and nothing else. Saying "two flops" to a lost-pulse question advertises that you never named the mode. The symptom-to-cause table in Failure Modes is the drill sheet for this habit.

    How to practise

    Take any symptom, a missed interrupt, a double register write, an impossible bus value, a lockup that never reproduces, and force yourself to say the mode before the fix, out loud, in one sentence. Then add the evidence you would cite: structural check for the synchroniser, formal proof for the protocol, constraints for the timing. That sentence pair is a level-3 answer already; the rubric explains why.

    Interview

    "Describe a CDC bug." Start with the symptom, name the mode in sentence two, give the mechanism in two more sentences, then the fix. Interviewers score this shape even when the bug itself is simple.

    Check yourself A status bus shows a value its counter never held. Name the mode and the fix family.

    Torn bus: several bits changed at once across per-bit synchronisers. Fix with Gray code, a handshake, or a FIFO, not with more synchroniser stages.

    Check yourself Why does naming the mode first help even when you know the fix?

    It proves diagnosis, it rules out wrong fixes before they are proposed, and it steers the interviewer's follow-ups onto ground you chose.

    Related topics

    • Next: Grading Rubric

    • Failure modes reference

    Previous

    148 / 179

    Next: Grading Rubric

    Up next

    Up nextGrading Rubric

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • The Answer Framework