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
    • RDC Methodology
    • Reset-aware Simulation
    • Chip-level RDC Closure
    • RDC Signoff Dashboard
      • What to Track
      • Reading RDC Progress
      • Waivers in RDC
      • Final Signoff Package
  • Debug and Case Studies11
  • CDC and RDC Interview Prep30
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹RDC Signoff Dashboard
  1. Topics
  2. CDC & RDC
  3. RDC Signoff
  4. RDC Signoff Dashboard
  5. What to Track

Part 8 · RDC Signoff · All levels

What to Track

RDC signoff metrics and the question each one answers.

On this page

    Every metric on the dashboard exists to answer one question. A metric without a question is decoration, and a question without a metric is a guess. The table below is the minimum set: small enough to maintain, complete enough to catch every common way RDC closure goes wrong.

    The metrics

    Metric

    Question it answers

    Open defects

    How many findings still need fixes? The one number that must reach zero.

    Unclassified findings

    How many findings still need judgement? Unclassified means open.

    Waiver count and oldest waiver age

    How much closure rests on argument, and is any argument ageing?

    Blocks with clean analysis on current RTL

    How much of the chip has actually been checked, on this RTL?

    Dynamic-check pass state per reset

    Which resets have proven behaviour, and which only have structure?

    Coverage holes

    Which required reset scenarios never ran?

    RTL or intent changes since last clean run

    Is the evidence stale? Any change re-opens this row until re-check.

    Review actions open

    How many review decisions are still waiting for their evidence?

    What the metrics deliberately avoid

    No thresholds appear in this table, and that is on purpose: what counts as an acceptable waiver age or how many blocks per week a team closes depends on the project, so the course states no numbers. Track direction and completeness instead: defects trending down, unclassified at zero, every block accounted for on current RTL. Targets Belong to the project plan, not to the methodology.

    What the checks and the review look for

    The review reads the dashboard the way it reads reports: directly, not via summaries. It checks that every metric points at current evidence, that the block list matches the chip hierarchy with nothing excluded silently, and that waiver age is measured against expiry rather than against when the waiver felt recent.

    Common pitfall

    Adding metrics that nobody owns turns the dashboard into wallpaper. Each metric needs an owner who updates it and a review that reads it, or it will go stale exactly when it matters.

    Check yourself The dashboard shows open defects at zero but unclassified findings at twelve. Is the design closed?

    No. Unclassified findings are open findings: without a disposition nobody knows whether those twelve are defects. Classify them first.

    Check yourself Why does the table track waiver age instead of just waiver count?

    Because a waiver is an argument with an expiry. An old waiver may rest on changed RTL or expired approval, so age signals when the argument needs renewal.

    Related topics

    • Reading RDC progress

    • Waivers in RDC

    • RDC closure criteria

    Previous

    131 / 179

    Next: Reading RDC Progress

    Up next

    Up nextReading RDC Progress

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Waivers in RDC
    • Final Signoff Package