Reset Sequencing: Review Checklist

Review checklist

Review Checklist for Reset Sequencing focuses on domain bring-up order violations, dependency deadlocks, reset latency. The goal is to convert issue observations into mechanism-backed closure decisions.

• Crossing and reset intent are explicitly classified.

• Protocol assumptions are documented and checked.

• Critical issues have owners and dates.

• Waivers include mechanism, containment, and expiry.

• Regression matrix includes stress and milestone modes.

• Owners signed: SoC integration owner, firmware owner, RTL lead.

Signoff ownership

OWNERSHIP MAP — Reset Sequencing

artifact                  owner
----------------------    -------------------------
design intent           SoC integration owner
verification evidence   firmware owner
signoff decision        RTL lead

Every open CDC/RDC issue needs one accountable owner before waiver or fix.

CDC/RDC deep dive

Reset release ordering is a first-order reliability contract.

Concept diagram

RESET RELEASE FLOW

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

Metric graph

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 ordering enforces dependency contracts so control domains and memories become valid before downstream consumers execute.

Metric: domain bring-up order violations, dependency deadlocks, reset latency