Clock/Reset + DFT Interactions: Review Checklist

Review checklist

Review Checklist for Clock/Reset + DFT Interactions focuses on scan mode timing escapes, test-mode bring-up issues. The goal is to map symptoms to boundary contracts, owner actions, and regression-proof closure.

• Baseline manifest and revision are explicit.

• Boundary contracts for this topic are current and approved.

• Ownership map covers all open issues.

• Focused and full regression evidence both exist.

• Residual risks are either closed or bounded via waiver policy.

• Owners signed: DFT lead, STA lead, clock/reset owners.

Signoff ownership

OWNERSHIP MAP — Clock/Reset + DFT Interactions

artifact             owner
-----------------    -----------------
primary owner     DFT lead
co-owner          STA lead
review owner      clock/reset owners

No top-level issue should remain ownerless beyond one review cycle.

SoC deep dive

Clock/reset assumptions must be globally consistent across functional and test modes.

Concept diagram

CLOCK/RESET FLOW
pll lock -> clock enable -> reset release -> domain ready

Metric graph

BOOT STABILITY
stable boots ████████
reset hangs  ███

Reports and artifacts

• clock architecture report

• reset release timing

• mode matrix

• boot trace summary

Mini case study

Intermittent boot hang traced to one domain releasing reset before dependent clock was stable.

Debug branches

• Check mode-specific constraints

• Trace reset dependencies

• Correlate firmware sequencing

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

• State baseline manifest and owner with every closure metric.

• Run cross-domain regression after every top-level fix.

Common pitfalls

• Comparing results across different manifests.

• Unowned issues slipping through review cycles.

• Waiving risks without expiry and validation plan.

Principal SoC review addendum

Functional and test clocks/resets share infrastructure; missing mode-specific constraints and mux assumptions often break ATPG or silicon bring-up.

Metric: scan mode timing escapes, test-mode bring-up issues