Scan-Ready RTL turns DFT intent into measurable release confidence. RTL coding style controls scanability through reset style, clock gating discipline, and avoiding structures that block controllability/observability. The senior challenge is proving whether a metric move came from real quality gain, setup drift, or hidden regression.
When DFT lint pass rate, uncontrollable register count, black-box scan escapes moves, can you identify mechanism, evidence quality, owner, and the minimum safe next action?
DFT CLOSURE FLOW - Scan-Ready RTL
scan/test architecture
|
v
ATPG constraints + fault models
|
v
pattern generation + compression
|
v
timing/power/physical validation
|
v
silicon diagnosis and release signoff
Debug rule: always state metric, run tags, and owning team with any claim.Draw the causal flow before opening tools. Use these diagrams to anchor architecture, constraints, and silicon behavior discussions.
scan-ready RTL -> scan insertion -> stitch -> DRC -> ATPG handoffDFT FLOW - Scan-Ready RTL
scan insertion -> chain stitch -> compression map -> ATPG -> tester apply -> diagnosis
| | | | |
controllability shift balance channel use coverage silicon correlation
Primary metric: DFT lint pass rate, uncontrollable register count, black-box scan escapesDFT OWNERSHIP LAYERS - Scan-Ready RTL
layer owns failure mode
---------------- -------------------------- -------------------------
rtl/architecture scanability hooks uncontrollable logic
atpg/constraints legal pattern intent aborts, low coverage
physical/clocking chain route + test clocks shift hold/timing escapes
tester/program pattern apply integrity false binning / bad fails
quality signoff release criteria escapes or schedule slipPrimary metric: DFT lint pass rate, uncontrollable register count, black-box scan escapes.
Primary artifact: DFT lint report, non-scan element list, waiver manifest.
Owners to bring into review: RTL owner, DFT owner, verification owner.
One failing signature and one reduced reproduction path.
Exact run tags for constraints, patterns, and tester program.
OWNERSHIP MAP - Scan-Ready RTL
artifact owner
---------------- -----------------
architecture/report RTL owner
constraints/setup DFT owner
physical/test verification owner
Name an owner for each failing metric cluster.Each topic includes mechanism, inputs/outputs, reports, debug, worked example, pitfalls, interview, checklist, theory, design space, expanded case study, walkthrough, comparison matrix, software view, and silicon impact.
State metric and run tags with every claim.
Connect every fix to a regression matrix.
Treat quality, timing, and power as coupled.
Coverage-centric decisions without legality checks.
Pattern changes without tester correlation.
Release calls without owner signoff.
Scan architecture quality determines whether ATPG can control and observe real silicon state.
SCAN INSERTION FLOW
scan-ready RTL -> scan replacement -> stitch chains -> DRC -> ATPG handoffCHAIN BALANCE
chain length spread
low spread = better shift time
high spread = routing + hold riskscan insertion summary
chain balance report
scan DRC log
clocking legality report
Coverage plateau traced to non-scan flops in reset islands; RTL + DFT lint policy fixed root cause.
Check scan replacement first
Audit chain legality by domain
Validate shift/capture clocks
Ask: what evidence proves this DFT decision is safe for production?
State metric, lot/corner context, and pattern tag with every claim.
Treat timing, power, and quality as one signoff problem.
Chasing coverage without legality checks.
Ignoring test-power side effects of pattern changes.
Debugging silicon without reproducible tags.