DenseChip

CDC / RDC · All levels

Reset Debug Playbook: Step-by-Step Walkthrough

Step-by-Step Walkthrough for Reset Debug Playbook.

Step-by-step analysis walkthrough

Use this sequence when owning Reset Debug Playbook 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

  • boot waveform bundle, reset event timeline, root-cause memo

  • crossing inventory

  • waiver board notes

  • regression report

Decision memo template

diagram
CDC/RDC DECISION MEMO — Reset Debug Playbook
risk class:
mechanism:
evidence:
fix/waiver:
owners: integration lead, verification lead, RDC owner

Reference visuals

Reset failure timeline

diagram
t0 reset assert
t1 clock ungated
t2 reset release domain A
t3 reset release domain B
t4 first traffic

Correlate failure to exact release ordering.

CDC/RDC deep dive

Reset release ordering is a first-order reliability contract.

Concept diagram

diagram
RESET RELEASE FLOW

assert global -> clocks stable -> sync release per domain -> first transaction

Metric graph

diagram
BOOT STABILITY

passes per 1k boots: 920 -> 980 -> 999

Reports and artifacts

  • reset dependency matrix

  • RDC warning classes

  • boot stress logs

  • waiver aging

Mini case study

Domain B released before producer A was valid, causing rare startup deadlock.

Debug branches

  • Correlate reset and clock timelines

  • verify async assert/sync release

  • exercise skewed release tests

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

Reset bugs are often timing-sequence interactions across power, clocks, and reset domains; debug must isolate order, polarity, and release windows.

Metric: reset-related failure reproduction time, first-pass root-cause hit rate

Practice this lesson