Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • DFT Metrics Reference
  • DFT Glossary
  • Reading Path
  • Scan Fundamentals61
  • Compression & Diagnosis61
  • ATPG & Pattern Generation61
  • MBIST & LBIST61
  • Boundary Scan & JTAG61
  • Test Timing & Power61
    • Test-Mode SDC
    • Shift vs Capture Timing
    • Test Power & IR
      • Test Power & IR: Mechanism
      • Test Power & IR: Inputs & Outputs
      • Test Power & IR: Reports & Metrics
      • Test Power & IR: Debug Playbook
      • Test Power & IR: Worked Example
      • Test Power & IR: Pitfalls & Red Flags
      • Test Power & IR: Interview Drills
      • Test Power & IR: Review Checklist
      • Test Power & IR: Theory Deep Dive
      • Test Power & IR: Design Space
      • Test Power & IR: Expanded Case Study
      • Test Power & IR: Step-by-Step Walkthrough
      • Test Power & IR: Comparison Matrix
      • Test Power & IR: Software / Programmer View
      • Test Power & IR: Silicon PPA Impact
    • Test Signoff Reports
    • Test Timing & Power: Tricky Q&A
  • DFT Physical Integration61
  • DFT Interview Prep61
  • DFT / ATPG Cheatsheet
Loading lesson

‹Test Power & IR
  1. Topics
  2. Design for Test
  3. Test Timing & Power
  4. Test Power & IR
  5. Test Power & IR: Inputs & Outputs

DFT / ATPG · All levels

Test Power & IR: Inputs & Outputs

Inputs & Outputs for Test Power & IR.

On this page

    Inputs and outputs contract

    Inputs & Outputs for Test Power & IR focuses on peak test-mode current, IR drop hotspots, scan-induced thermal spikes. The goal is to convert metric movement into mechanism, owner, and release decision.

    Treat these as a release contract. Ambiguity here creates expensive debug loops because teams optimize against different assumptions.

    Diagram
    INPUTS
      - scan/ATPG architecture and constraints
      - fault model and quality target policy
      - pattern generation config + tester limits
      - timing/power/physical assumptions
    
    OUTPUTS
      - quality metrics and closure status
      - signed artifacts and owner approvals
      - diagnosis evidence for residual risk
      - release, waiver, or escalation decision

    Flow sequence

    Diagram
    DFT FLOW - Test Power & IR
    
    scan insertion -> chain stitch -> compression map -> ATPG -> tester apply -> diagnosis
          |                |                |            |             |
     controllability   shift balance    channel use   coverage     silicon correlation
    
    Primary metric: peak test-mode current, IR drop hotspots, scan-induced thermal spikes

    Ownership map

    Diagram
    OWNERSHIP MAP - Test Power & IR
    
    artifact              owner
    ----------------      -----------------
    architecture/report power signoff owner
    constraints/setup   ATPG owner
    physical/test       DFT lead
    
    Name an owner for each failing metric cluster.

    DFT deep dive

    Test signoff fails when shift/capture timing and test power are treated independently.

    Concept diagram

    Diagram
    TEST SIGNOFF LOOP
    
    test SDC -> shift/capture timing -> power-aware ATPG -> IR validation -> release

    Metric graph

    Diagram
    TEST CURRENT
    
    functional current  baseline
    scan shift current  peak-risk zone

    Reports and artifacts

    • test-mode STA report

    • shift/capture split

    • test power IR map

    • waiver tracker

    Mini case study

    At-speed patterns passed timing but failed in production due to peak shift IR; staggered capture and power-aware fill resolved.

    Debug branches

    • Tag test and functional corners separately

    • Check hold in shift mode

    • Correlate fail bins with power hotspots

    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

    Scan activity can exceed functional switching, so pattern scheduling and power-aware ATPG are needed to avoid IR and thermal escapes.

    Metric: peak test-mode current, IR drop hotspots, scan-induced thermal spikes

    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

    Previous

    341 / 493

    Next: Test Power & IR: Reports & Metrics

    Up next

    Up nextTest Power & IR: Reports & Metrics

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Test Power & IR: Debug Playbook
    • Test Power & IR: Worked Example
    • Test Power & IR: Pitfalls & Red Flags