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
    • CDC Tool Flow
      • The Generic CDC Flow
      • Setup: Clocks, Resets and Intent
      • Violation Classes
      • Hierarchical versus Flat Analysis
    • CDC Constraints and STA
    • CDC Waiver Policy
    • CDC Review Gate
    • CDC Signoff Dashboard
    • Formal and Simulation CDC Verification
  • RDC Signoff16
  • Debug and Case Studies11
  • CDC and RDC Interview Prep30
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹CDC Tool Flow
  1. Topics
  2. CDC & RDC
  3. CDC Signoff Methodology
  4. CDC Tool Flow
  5. The Generic CDC Flow

Part 7 · CDC Signoff Methodology · Advanced

The Generic CDC Flow

Setup, structural analysis, classification, fix, re-run, and signoff: what each stage does.

On this page

    CDC signoff is a loop, not a single run. The design is checked structurally, every reported crossing is classified, defects are fixed, and the analysis is repeated until the only open items are reviewed waivers. Knowing the shape of the loop matters because each stage answers a different question, and skipping one silently moves its question to tape-out.

    The six stages

    Flowchart of the six CDC signoff stages with a re-run loop back to classification.
    The CDC loop: setup feeds structural analysis, findings are classified and fixed, then the analysis is re-run until signoff.

    Stage

    Consumes

    Produces

    Question it answers

    Setup

    RTL, clock and reset architecture, intent

    Clock list, relationships, constraints

    What should the analysis assume?

    Structural analysis

    RTL plus setup

    Full crossing inventory with classifications

    Where are all the crossings, and what structure guards each?

    Classification

    The inventory

    Defects, items needing waivers, clean crossings

    Which findings are real bugs?

    Fix

    The defect list

    New RTL or corrected constraints

    How is each defect removed?

    Re-run

    New RTL under the same setup

    Fresh inventory to compare

    Is it actually fixed, and did anything else break?

    Signoff

    Clean inventory, waivers, reviews

    Signed record

    Is there evidence for every crossing?

    Why the loop re-runs from the same setup

    A fix changes the RTL, so the previous inventory is stale: a moved synchroniser can expose a new path, and a new block can add crossings nobody classified. Re-running under the same setup keeps runs comparable, which the dashboard topic relies on. Changing the setup and the RTL in the same step makes it impossible to say which change moved the numbers.

    What the flow does not do

    Structural analysis checks that every crossing has a recognised synchronising structure. It does not prove the protocol around the structure is correct, it does not time the paths, and it does not observe the design running. Those are separate methods with their own place in regression, covered in the formal and simulation topic.

    Common pitfall

    Running the analysis once, late, and waiving everything red is the most expensive way to use the flow. The loop is cheapest when setup is reviewed first and the analysis runs from the first integration.

    Interview

    “Walk me through CDC signoff on your last project.” Answer in stages: setup review, structural runs, triage order, what you fixed versus waived, and what the exit criteria were.

    Check yourself The re-run after a fix shows fewer findings but the setup file also changed. Can the two runs be compared?

    No. Either the fix or the setup change could explain the difference. Re-run once more with only one of the two changed before drawing conclusions.

    Check yourself Structural analysis reports zero crossings on a multi-clock design. What is the first suspicion?

    A setup problem: a missing clock definition or an over-broad hierarchy exclusion means the analysis never looked. A flat zero on a design known to have crossings is evidence of blindness, not cleanliness.

    Related topics

    • Setup: Clocks, Resets and Intent

    • Violation Classes

    • Regression Strategy

    Previous

    95 / 179

    Next: Setup: Clocks, Resets and Intent

    Up next

    Up nextSetup: Clocks, Resets and Intent

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Violation Classes
    • Hierarchical versus Flat Analysis