Use when you own Scan Chain Physical Effects in a DFT closure review.
Open release criteria and failing metric dashboard.
Partition failures by pattern family and operating context.
Inspect constraints, clocks, masks, and unknown handling.
Check architecture assumptions against implementation reality.
Review diagnosis evidence for repeatability.
Assign owner and propose smallest high-confidence change.
Run timing, power, and quality regressions.
Capture final signoff or waiver decision.
scan physical report, wirelength histogram, congestion heatmap
pattern tag manifest
tester program revision
signoff checklist
owner tracker
DFT DECISION MEMO - Scan Chain Physical Effects
scenario:
metric:
hypothesis:
fix:
regression:
owners: PD owner, DFT owner, implementation ownerchain order -> wirelength -> congestion -> hold buffers -> shift timing riskPhysical integration quality decides whether DFT architecture survives implementation realities.
PHYSICAL DFT FLOW
chain planning -> floorplan placement -> route -> test timing/power validationROUTING BURDEN
poor chain order -> longer routes -> more hold buffersscan physical wirelength
congestion heatmap
test clock skew
handoff issue tracker
Late scan reorder reduced route detours and eliminated a major shift hold cluster before signoff.
Correlate chain order with congestion
Place compression logic near chain clusters
Keep DFT-PD handoff versioned
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.
Logical chain order interacts with placement and routing; poor ordering inflates wirelength, congestion, and shift hold fixes.
Metric: scan wirelength, congestion from chain ordering, hold buffer overhead
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