Interview Drills for Shift vs Capture Timing focuses on shift hold violations, capture setup failures, at-speed pattern pass rate. The goal is to convert metric movement into mechanism, owner, and release decision.
PROMPT
You observe shift hold violations, capture setup failures, at-speed pattern pass rate on Shift vs Capture Timing. Walk through diagnosis and release decision.
STRONG ANSWER
1. States context and run tags.
2. Explains mechanism: Shift mode is hold-sensitive while capture mode is setup-sensitive; closure must preserve both under test clocking assumptions.
3. Requests shift/capture timing report, at-speed validation logs, path-group summary.
4. Proposes minimal fix and regression.
WEAK ANSWER
Jumps to tool switches without evidence quality, ownership, or regression plan.shift mode: hold-dominant
capture mode: setup-dominant
Do not sign off one without the other.ROOT-CAUSE TREE - Shift vs Capture Timing
shift hold violations, capture setup failures, at-speed pattern pass 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 signatureTest signoff fails when shift/capture timing and test power are treated independently.
TEST SIGNOFF LOOP
test SDC -> shift/capture timing -> power-aware ATPG -> IR validation -> releaseTEST CURRENT
functional current baseline
scan shift current peak-risk zonetest-mode STA report
shift/capture split
test power IR map
waiver tracker
At-speed patterns passed timing but failed in production due to peak shift IR; staggered capture and power-aware fill resolved.
Tag test and functional corners separately
Check hold in shift mode
Correlate fail bins with power hotspots
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.
Shift mode is hold-sensitive while capture mode is setup-sensitive; closure must preserve both under test clocking assumptions.
Metric: shift hold violations, capture setup failures, at-speed pattern pass rate
This content block can't be displayed here.
Block type: unknown
This content block can't be displayed here.
Block type: unknown
This content block can't be displayed here.
Block type: unknown