DFT / ATPG · All levels
Clocking for Test: Silicon PPA Impact
Silicon PPA Impact for Clocking for Test.
Silicon impact
Chain balance and test clocks directly affect tester throughput and escape risk.
Area drivers
compression logic footprint
hold buffers from scan paths
Power drivers
shift toggling peaks
capture burst stress
Timing impact
test-clock skew
shift/capture path sensitivity
PD consequences
chain route detours
placement hotspots near test logic
Verification burden
pattern replay correlation
diagnosis reproducibility
SILICON IMPACT - Clocking for Test
area/power/timing/yield tradeoffTakeaways
Signoff needs silicon evidence
Ownership clarity accelerates closure
Design option snapshot
CHAIN BALANCE - Clocking for Test
chain length
^
| o o
| o o o
| o
+-----------------------------> chain index
Tight spread reduces shift time and hold-fix burden.DFT deep dive
Scan architecture quality determines whether ATPG can control and observe real silicon state.
Concept diagram
SCAN INSERTION FLOW
scan-ready RTL -> scan replacement -> stitch chains -> DRC -> ATPG handoffMetric graph
CHAIN BALANCE
chain length spread
low spread = better shift time
high spread = routing + hold riskReports 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