Physical DFT Debug: Silicon PPA Impact

Silicon impact

Physical DFT issues are frequent late-stage schedule risks.

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 - Physical DFT Debug
area/power/timing/yield tradeoff

Takeaways

• Signoff needs silicon evidence

• Ownership clarity accelerates closure

Design option snapshot

CHAIN BALANCE - Physical DFT Debug

chain length
  ^
  |      o        o
  |   o    o  o
  | o
  +-----------------------------> chain index

Tight spread reduces shift time and hold-fix burden.

DFT deep dive

Physical integration quality decides whether DFT architecture survives implementation realities.

Concept diagram

PHYSICAL DFT FLOW

chain planning -> floorplan placement -> route -> test timing/power validation

Metric graph

ROUTING BURDEN

poor chain order -> longer routes -> more hold buffers

Reports and artifacts

• scan physical wirelength

• congestion heatmap

• test clock skew

• handoff issue tracker

Mini case study

Late scan reorder reduced route detours and eliminated a major shift hold cluster before signoff.

Debug branches

• Correlate chain order with congestion

• Place compression logic near chain clusters

• Keep DFT-PD handoff versioned

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

Physical DFT debug traces violations to chain ordering, buffering strategy, clock topology, or extraction/view mismatches.

Metric: physical root-cause turnaround, repeat DFT route violations, signoff escape risk