DFT / ATPG · All levels
Debug Access Port: Comparison Matrix
Comparison Matrix for Debug Access Port.
Comparison matrix
Instruction sets and access modes trade debug speed and attack surface.
+------------------+----------------+----------------+----------------+
| Approach | Strength | Weakness | Best when |
+------------------+----------------+----------------+----------------+
| Conservative | safe | higher cost | ramp-sensitive |
| Balanced | practical | needs rigor | production |
| Aggressive | fast | escape risk | schedule pressure |
| Architecture | durable | slow | repeated pain |
+------------------+----------------+----------------+----------------+When to choose each approach
Tie approach to product risk and tester constraints
Interview traps
Optimizing one metric only
No regression ownership
Evidence comparison
DFT EVIDENCE MATRIX - Debug Access Port
+-------------------+------------------------+--------------------------+-------------------------+
| Evidence | Tells you | Does not prove | Next action |
+-------------------+------------------------+--------------------------+-------------------------+
| coverage report | fault detect trends | silicon root cause | inspect bucket details |
| pattern diff | generation changes | architecture quality | replay suspect patterns |
| timing/power report| test closure margin | diagnosis confidence | correlate fail logs |
| diagnosis summary | likely defect classes | ownership decision | assign action owner |
| signoff checklist | process completeness | correctness of evidence | peer review artifacts |
+-------------------+------------------------+--------------------------+-------------------------+DFT deep dive
Boundary scan and JTAG are board-level contracts, not just RTL features.
Concept diagram
JTAG ACCESS
TAP controller -> instruction register -> boundary/data register -> board test/debugMetric graph
BOARD TEST READINESS
instruction coverage vs pin controllabilityReports and artifacts
TAP compliance report
boundary cell coverage matrix
EXTEST/INTEST results
debug lock policy log
Mini case study
Board bring-up blocked by pinmux override in one mode; TAP instruction decode and package table alignment fixed path.
Debug branches
Verify TAP state transitions
Audit package pin ownership
Check security lifecycle lock behavior
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
Debug access over JTAG must balance bring-up visibility with production security and lifecycle lock policy.
Metric: debug access latency, security lock compliance, bring-up access reliability