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
    • Scan Cell Architecture
      • Scan Cell Architecture: Mechanism
      • Scan Cell Architecture: Inputs & Outputs
      • Scan Cell Architecture: Reports & Metrics
      • Scan Cell Architecture: Debug Playbook
      • Scan Cell Architecture: Worked Example
      • Scan Cell Architecture: Pitfalls & Red Flags
      • Scan Cell Architecture: Interview Drills
      • Scan Cell Architecture: Review Checklist
      • Scan Cell Architecture: Theory Deep Dive
      • Scan Cell Architecture: Design Space
      • Scan Cell Architecture: Expanded Case Study
      • Scan Cell Architecture: Step-by-Step Walkthrough
      • Scan Cell Architecture: Comparison Matrix
      • Scan Cell Architecture: Software / Programmer View
      • Scan Cell Architecture: Silicon PPA Impact
    • Chain Stitching Rules
    • Clocking for Test
    • Scan-Ready RTL
    • Scan Fundamentals: Tricky Q&A
  • Compression & Diagnosis61
  • ATPG & Pattern Generation61
  • MBIST & LBIST61
  • Boundary Scan & JTAG61
  • Test Timing & Power61
  • DFT Physical Integration61
  • DFT Interview Prep61
  • DFT / ATPG Cheatsheet
Loading lesson

‹Scan Cell Architecture
  1. Topics
  2. Design for Test
  3. Scan Fundamentals
  4. Scan Cell Architecture
  5. Scan Cell Architecture: Design Space

DFT / ATPG · All levels

Scan Cell Architecture: Design Space

Design Space for Scan Cell Architecture.

On this page

    Design space exploration

    For Scan Cell Architecture, release options trade quality, tester cost, and schedule risk.

    Option A - conservative

    • Conservative quality: helps debug confidence

    • Risk: higher test cost

    • Validate with: first production ramps

    Option B - balanced

    • Balanced release: helps quality and cost

    • Risk: needs discipline

    • Validate with: mainstream products

    Option C - aggressive

    • Aggressive schedule: helps faster closure

    • Risk: escape risk

    • Validate with: late tapeout pressure

    Option D - architecture change

    • Architecture change: helps long-term quality

    • Risk: schedule hit

    • Validate with: chronic recurring failures

    Diagram
    DESIGN SPACE - Scan Cell Architecture
    quality <-> tester cost <-> schedule

    Design pitfalls

    • No ownership for quality gap

    • Fixing one metric while regressing another

    Tradeoff curve

    Diagram
    BEFORE / AFTER - Scan Cell Architecture
    
    metric quality
      ^
      |                    --- release target
      |      o regressed
      |           o baseline
      |                o after fix
      +-------------------------------> closure iteration
    
    Prove quality, timing, and test-power all moved safely.

    DFT deep dive

    Scan architecture quality determines whether ATPG can control and observe real silicon state.

    Concept diagram

    Diagram
    SCAN INSERTION FLOW
    
    scan-ready RTL -> scan replacement -> stitch chains -> DRC -> ATPG handoff

    Metric graph

    Diagram
    CHAIN BALANCE
    
    chain length spread
    low spread   = better shift time
    high spread  = routing + hold risk

    Reports and artifacts

    • scan insertion summary

    • chain balance report

    • scan DRC log

    • clocking legality report

    Mini case study

    Coverage plateau traced to non-scan flops in reset islands; RTL + DFT lint policy fixed root cause.

    Debug branches

    • Check scan replacement first

    • Audit chain legality by domain

    • Validate shift/capture clocks

    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 insertion replaces functional flops with scan-capable cells so internal state becomes controllable and observable in test mode.

    Metric: scan cell legality rate, scan replacement ratio, scan DRC 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

    14 / 493

    Next: Scan Cell Architecture: Expanded Case Study

    Up next

    Up nextScan Cell Architecture: Expanded Case Study

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Scan Cell Architecture: Mechanism
    • Scan Cell Architecture: Inputs & Outputs
    • Scan Cell Architecture: Reports & Metrics