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. Reading RDC Progress

Part 8 · RDC Signoff · All levels

Reading RDC Progress

Trend, false-clean risks, and how to keep progress honest.

On this page

    Progress in RDC signoff is not a line going down: it is a line going down for honest reasons. Defect counts can fall because defects were fixed, because findings were reclassified without evidence, or because scope was quietly excluded. Reading progress means telling those apart.

    Reading the trend

    What you see

    Honest cause

    Dishonest lookalike to rule out

    Open defects falling

    Fixes landing and re-analysis confirming them.

    Defects reclassified as acceptable with no new evidence.

    Unclassified falling

    Classification sessions working through the report.

    Findings closed in bulk without per-finding dispositions.

    Clean blocks rising

    Blocks analysed on current RTL with final intent.

    Blocks marked clean on stale RTL or draft intent.

    Coverage holes closing

    New sequences running and logging their seeds.

    Rows marked covered by tests that never moved reset.

    False-clean risks

    Five honest mistakes produce a clean dashboard over an unclosed design: intent incomplete so the analysis checked nothing, blocks excluded from scope so their findings never appear, everything waived so argument replaced proof, a stale run predating the latest RTL change, and resets tied off in simulation so dynamic checks passed vacuously. The dashboard counters each one only if its metrics are wired to current evidence: intent revision, scope list, waiver records, run revisions, and per-reset activity.

    How to stay honest

    Re-run analysis after every RTL or intent change and say so on the dashboard. Audit scope against the chip hierarchy each week: every block is either clean on current RTL, open with actions, or explicitly out of scope with a recorded reason. And treat sudden improvement as suspicious: a defect count that halves overnight should trigger an audit of dispositions, not a celebration.

    Common pitfall

    Presenting the trend line without its causes invites pressure to move the line rather than the work. Always present the trend with what changed: fixes landed, classifications made with evidence, scope changes with reasons.

    Interview

    Expect: your RDC defects hit zero a week before tape-out. Do you trust it? Answer: only after ruling out the five false-cleans, intent, scope, waivers, staleness, tied-off resets, and only if the dispositions behind the trend survive an audit.

    Check yourself Open defects fell from forty to four overnight with no RTL changes. What do you audit first?

    The dispositions: which findings were reclassified, what new evidence each reclassification cites, and who approved it. Fixes without RTL changes deserve scepticism.

    Check yourself A block is clean but its last analysis predates three RTL changes. How should the dashboard show it?

    As not clean: the change-delta row is open for that block until analysis re-runs on current RTL. Stale clean is not clean.

    Related topics

    • What to track

    • Final signoff package

    • RDC closure criteria

    Previous

    132 / 179

    Next: Waivers in RDC

    Up next

    Up nextWaivers in RDC

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Final Signoff Package