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
  • DFT Physical Integration61
    • Scan Chain Physical Effects
    • Test Logic Floorplan
      • Test Logic Floorplan: Mechanism
      • Test Logic Floorplan: Inputs & Outputs
      • Test Logic Floorplan: Reports & Metrics
      • Test Logic Floorplan: Debug Playbook
      • Test Logic Floorplan: Worked Example
      • Test Logic Floorplan: Pitfalls & Red Flags
      • Test Logic Floorplan: Interview Drills
      • Test Logic Floorplan: Review Checklist
      • Test Logic Floorplan: Theory Deep Dive
      • Test Logic Floorplan: Design Space
      • Test Logic Floorplan: Expanded Case Study
      • Test Logic Floorplan: Step-by-Step Walkthrough
      • Test Logic Floorplan: Comparison Matrix
      • Test Logic Floorplan: Software / Programmer View
      • Test Logic Floorplan: Silicon PPA Impact
    • DFT-PD Handoff
    • Physical DFT Debug
    • DFT Physical Integration: Tricky Q&A
  • DFT Interview Prep61
  • DFT / ATPG Cheatsheet
Loading lesson

‹Test Logic Floorplan
  1. Topics
  2. Design for Test
  3. DFT Physical Integration
  4. Test Logic Floorplan
  5. Test Logic Floorplan: Inputs & Outputs

DFT / ATPG · All levels

Test Logic Floorplan: Inputs & Outputs

Inputs & Outputs for Test Logic Floorplan.

On this page

    Inputs and outputs contract

    Inputs & Outputs for Test Logic Floorplan focuses on compression logic placement quality, test route detours, floorplan DFT ECO count. 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 Logic Floorplan
    
    scan insertion -> chain stitch -> compression map -> ATPG -> tester apply -> diagnosis
          |                |                |            |             |
     controllability   shift balance    channel use   coverage     silicon correlation
    
    Primary metric: compression logic placement quality, test route detours, floorplan DFT ECO count

    Ownership map

    Diagram
    OWNERSHIP MAP - Test Logic Floorplan
    
    artifact              owner
    ----------------      -----------------
    architecture/report PD owner
    constraints/setup   DFT owner
    physical/test       CTS owner
    
    Name an owner for each failing metric cluster.

    DFT deep dive

    Physical integration quality decides whether DFT architecture survives implementation realities.

    Concept diagram

    Diagram
    PHYSICAL DFT FLOW
    
    chain planning -> floorplan placement -> route -> test timing/power validation

    Metric graph

    Diagram
    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

    Placement of decompressors, compactors, and BIST controllers impacts routing quality, clocking, and timing closure effort.

    Metric: compression logic placement quality, test route detours, floorplan DFT ECO count

    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

    387 / 493

    Next: Test Logic Floorplan: Reports & Metrics

    Up next

    Up nextTest Logic Floorplan: Reports & Metrics

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Test Logic Floorplan: Debug Playbook
    • Test Logic Floorplan: Worked Example
    • Test Logic Floorplan: Pitfalls & Red Flags