DenseChip

CDC / RDC · All levels

RDC Methodology: Step-by-Step Walkthrough

Step-by-Step Walkthrough for RDC Methodology.

Step-by-step analysis walkthrough

Use this sequence when owning RDC Methodology in a signoff review.

  1. Inspect warning class and severity.

  2. Trace crossing endpoints and domains.

  3. Check protocol/reset assumptions against spec.

  4. Review synchronizer or FIFO implementation detail.

  5. Run focused assertion or formal check.

  6. Draft fix options with risk and schedule impact.

  7. Execute regression and publish closure memo.

Artifacts to collect

  • RDC methodology guide, rule-set config, hazard taxonomy

  • crossing inventory

  • waiver board notes

  • regression report

Decision memo template

diagram
CDC/RDC DECISION MEMO — RDC Methodology
risk class:
mechanism:
evidence:
fix/waiver:
owners: RDC lead, methodology owner, verification lead

Reference visuals

RDC methodology loop

diagram
intent capture -> structural run -> dynamic proof
        -> waiver board -> milestone gate -> archive

CDC/RDC deep dive

RDC closure must connect IP assumptions to SoC reality.

Concept diagram

diagram
RDC CLOSURE

IP reset intent + SoC sequencing -> structural checks -> dynamic stress -> signoff

Metric graph

diagram
MILESTONE READINESS

M-2 55%
M-1 82%
M0  100%

Reports and artifacts

  • top-level RDC opens

  • reset simulation coverage

  • chip integration blockers

  • waiver backlog

Mini case study

Each IP was locally clean, but top-level sequencing violation created cross-subsystem boot intermittency.

Debug branches

  • Audit subsystem assumptions

  • stress chip-level reset scenarios

  • close ownership gaps

Senior review question

Ask: what evidence proves this risk is closed for silicon, not just tool-clean?

Key takeaways

  • State crossing class, assumptions, and owner with every issue.

  • Run structural and dynamic regressions after each fix.

Common pitfalls

  • Treating all warnings as equivalent risk.

  • Waiving issues without containment evidence.

  • Skipping reset and reconvergence stress after CDC fixes.

Principal CDC/RDC review addendum

RDC methodology treats reset behavior as a first-class asynchronous interface requiring intent capture, structural checks, and targeted dynamic proof.

Metric: reset-domain hazard coverage, unresolved RDC severity count, closure quality

Practice this lesson