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
    • CDC Constraints and STA
    • CDC Waiver Policy
    • CDC Review Gate
    • CDC Signoff Dashboard
      • What to Track
      • Reading Progress
      • Honest Metrics
      • Trend and Regression
    • 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 Signoff Dashboard
  1. Topics
  2. CDC & RDC
  3. CDC Signoff Methodology
  4. CDC Signoff Dashboard
  5. Reading Progress

Part 7 · CDC Signoff Methodology · Advanced

Reading Progress

Trend and burn-down reading: the expected shape of convergence, and why a flat zero can be a setup problem.

On this page

    Progress is read from trends, never from a single run. A healthy project shows a recognisable shape: early noise as setup settles, a steady burn-down as defects are fixed, and a long tail of waiver reviews. Learning that shape — and its impostors — is what makes the dashboard a management tool instead of wallpaper.

    The expected shape

    1. Early runs are noisy: counts swing as clocks are added, relationships corrected, and hierarchy included. Judge setup here, not design.

    2. Middle runs burn down: open defects fall run over run as fixes land, with occasional bumps when new blocks integrate. The bumps are healthy.

    3. Late runs flatten on waivers: defects near zero, and the remaining work is evidence and joint approvals. The tail is slow because review is slow.

    Impostor shapes

    Shape

    What it might mean

    Check

    Flat zero from the start

    The analysis is blind: missing clocks or excluded hierarchy

    Seed a known crossing and confirm it is reported; review setup

    Cliff drop in one run

    Setup changed, scope shrank, or findings were bulk-waived

    Diff setup, scope, and waiver list across the cliff before celebrating

    Sawtooth that never falls

    Fixes landing alongside new defects at the same rate

    Separate new-findings rate from fix rate; the design may be churning faster than signoff

    Zero defects, growing waivers

    Risk converted to permissions, possibly without evidence

    Audit the new waivers against the template before the milestone

    The flat zero deserves its reputation as the most dangerous shape: it is exactly what a missing clock definition produces. Every project should know the location of at least one real crossing and confirm the dashboard sees it — a living canary for setup blindness.

    Common pitfall

    Celebrating the cliff drop in a status meeting locks the team into defending it. Read every sharp move as suspect first, in private, before anyone presents it as progress.

    Check yourself Open defects fall from 200 to 0 in a single run with no RTL change. List three innocent-or-guilty causes to check.

    A setup change that narrowed the analysis, a scope change that excluded hierarchy, or bulk waiving. The setup and scope diffs plus the waiver list distinguish them — and all three must be checked before the run counts.

    Check yourself What is the “canary” practice, and which failure does it guard against?

    Keeping a known real crossing visible on the dashboard to confirm the analysis still sees it. It guards against setup blindness producing a false flat zero.

    Related topics

    • What to Track

    • Trend and Regression

    • Setup: Clocks, Resets and Intent

    Previous

    112 / 179

    Next: Honest Metrics

    Up next

    Up nextHonest Metrics

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Trend and Regression