DFT / ATPG · All levels

Clocking for Test: Review Checklist

Review Checklist for Clocking for Test.

Review checklist

Review Checklist for Clocking for Test focuses on test clock reachability, pulse legality, scan shift/capture violations. The goal is to convert metric movement into mechanism, owner, and release decision.

  • Run tags and scenario context are explicit.

  • Constraints and legality assumptions are documented.

  • Quality, timing, and test-power checks are included.

  • Diagnosis evidence supports residual-risk decision.

  • Owners signed: DFT owner, CTS owner, STA owner.

Signoff ownership

diagram
OWNERSHIP MAP - Clocking for Test

artifact              owner
----------------      -----------------
architecture/report DFT owner
constraints/setup   CTS owner
physical/test       STA owner

Name an owner for each failing metric cluster.

DFT deep dive

Scan architecture quality determines whether ATPG can control and observe real silicon state.

Concept diagram

diagram
SCAN INSERTION FLOW

scan-ready RTL -> scan replacement -> stitch chains -> DRC -> ATPG handoff

Metric graph

diagram
CHAIN BALANCE

chain length spread
low spread   = better shift time
high spread  = routing + hold risk

Reports and artifacts

  • scan insertion summary

  • chain balance report

  • scan DRC log

  • clocking legality report

Mini case study

Coverage plateau traced to non-scan flops in reset islands; RTL + DFT lint policy fixed root cause.

Debug branches

  • Check scan replacement first

  • Audit chain legality by domain

  • Validate shift/capture clocks

Senior review question

Ask: what evidence proves this DFT decision is safe for production?

Key takeaways

  • State metric, lot/corner context, and pattern tag with every claim.

  • Treat timing, power, and quality as one signoff problem.

Common pitfalls

  • Chasing coverage without legality checks.

  • Ignoring test-power side effects of pattern changes.

  • Debugging silicon without reproducible tags.

Principal DFT review addendum

Test clocks must safely drive scan shift and at-speed capture modes without violating clock gating, pulse width, or domain assumptions.

Metric: test clock reachability, pulse legality, scan shift/capture violations