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
    • Gray Code Crossing
    • Reconvergence Analysis
    • Multi-bit Crossing Strategies
    • Reconvergence Debug
      • Reading a Reconvergence Report
      • Worked Reconvergence Example
      • Fix and Recheck
      • Regression Guards
  • Reset Domain Crossing16
  • Architecture and Design Rules16
  • CDC Signoff Methodology24
  • RDC Signoff16
  • Debug and Case Studies11
  • CDC and RDC Interview Prep30
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹Reconvergence Debug
  1. Topics
  2. CDC & RDC
  3. Reconvergence and Gray Coding
  4. Reconvergence Debug
  5. Fix and Recheck

Part 4 · Reconvergence and Gray Coding · All levels

Fix and Recheck

Fix patterns, re-running the structural and the dynamic checks, and avoiding new violations.

On this page

    A reconvergence fix is not done when the RTL looks better; it is done when the finding is gone from the structural report, the dynamic checks still pass, and no new finding took its place. Fixes fail review most often on that third point: the repair adds a crossing the author never checked.

    Fix patterns and their rechecks

    Fix applied

    Structural recheck

    Dynamic recheck

    Synchronise one, derive the rest

    Convergence point gone; derivation logic local to the destination domain

    Derivation covered by destination-domain tests with the strobe at every alignment

    Qualified capture

    Qualifier crossing clean; no second synchroniser on the bundle

    Stability assertion active; bus toggled in every legal window during regression

    Handshake or FIFO

    Request, acknowledge, and pointer crossings each classified synchronised

    Full protocol sequences: stall, backpressure, reset mid-transfer

    Avoiding new violations

    • The added synchroniser needs the standard rules itself: registered source, no logic between flops, destination clock only.

    • A qualifier derived from a second synchronised copy reintroduces the finding under a new name; derive from the crossed signal, not from a copy of the source state.

    • Lengthening a pulse path (extra stages for settling) re-times every consumer of that pulse; recheck pulse spacing and derived enables.

    • Reset changes with the fix (new flops, new domain) need the reset-domain review again, not just the CDC one.

    Close the loop in the finding tracker: link the fixed RTL, the clean structural excerpt, and the passing dynamic run to the original finding id, so the waiver history shows a repair rather than a disappearance.

    Common pitfall

    Fixing only the reported convergence point while a sibling pair nearby shares the same source moment moves the finding one gate downstream. When a report flags one pair, search the same source event for other separately synchronised copies before declaring victory.

    Check yourself After a qualified-capture fix, the structural report is clean but the stability assertion fires in regression. What happened?

    The design is structurally correct but the new stimulus changes the bus inside a previously quiet window. Either the stimulus violates the agreed change protocol (fix the test and document the window) or the window was never real (reopen the finding). The assertion did its job either way.

    Related topics

    • Worked example

    • Next: regression guards

    Previous

    61 / 179

    Next: Regression Guards

    Up next

    Up nextRegression Guards

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Reading a Reconvergence Report