ATPG Constraints: Interview Drills

Interview drills

Interview Drills for ATPG Constraints focuses on constraint consistency errors, illegal state count, pattern abort rate. The goal is to convert metric movement into mechanism, owner, and release decision.

PROMPT
You observe constraint consistency errors, illegal state count, pattern abort rate on ATPG Constraints. Walk through diagnosis and release decision.

STRONG ANSWER
1. States context and run tags.
2. Explains mechanism: ATPG constraints encode legal test-mode behavior, clocks, resets, and masks so generated patterns are both executable and meaningful.
3. Requests ATPG constraint file, legality checker log, constraint diff report.
4. Proposes minimal fix and regression.

WEAK ANSWER
Jumps to tool switches without evidence quality, ownership, or regression plan.

Diagram to draw on the whiteboard

ATPG legality envelope

constraints define legal test states:
clocks + resets + masks + test enables + safe unknown handling

invalid envelope -> great-looking but unusable patterns.

Root-cause narrative

ROOT-CAUSE TREE - ATPG Constraints

constraint consistency errors, illegal state count, pattern abort rate regresses
        |
  setup changed?
    /        \
  yes         no
  |            |
constraint    silicon or
or ATPG       physical/test path
 /    \          |
SDC   model    chain/clock/power/diagnosis
diff  diff     isolate first failing signature

DFT deep dive

ATPG quality comes from fault model choice plus legal constraints, not raw pattern volume alone.

Concept diagram

ATPG FLOW

fault model -> constraints -> generation -> simulation -> coverage closure -> signoff

Metric graph

COVERAGE GAP

target coverage
  ^
  |      o before closure
  |          o after fixes
  +---------------------> iteration

Reports and artifacts

• fault model coverage

• untestable class report

• constraint legality errors

• pattern signoff memo

Mini case study

Transition coverage stalled due to clock constraints mismatch; updated at-speed capture definitions recovered target.

Debug branches

• Classify untestable faults

• Diff ATPG constraints each run

• Pair coverage with pattern budget

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

ATPG constraints encode legal test-mode behavior, clocks, resets, and masks so generated patterns are both executable and meaningful.

Metric: constraint consistency errors, illegal state count, pattern abort rate