DenseChip

CDC / RDC · All levels

Chip-level RDC Closure: Step-by-Step Walkthrough

Step-by-Step Walkthrough for Chip-level RDC Closure.

Step-by-step analysis walkthrough

Use this sequence when owning Chip-level RDC Closure 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

  • SoC reset map, subsystem waiver list, integration closure report

  • crossing inventory

  • waiver board notes

  • regression report

Decision memo template

diagram
CDC/RDC DECISION MEMO — Chip-level RDC Closure
risk class:
mechanism:
evidence:
fix/waiver:
owners: SoC lead, RDC lead, IP owners

Reference visuals

SoC reset map

diagram
IP A reset tree ---IP B reset tree ----+--> SoC dependency graph
IP C reset tree ---/

Top-level closure fails when IP assumptions conflict.

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

Chip-level RDC closure depends on clean reset intent handoff from IPs and alignment between subsystem sequencing assumptions.

Metric: top-level RDC open count, subsystem handoff completeness, integration churn

Practice this lesson