DenseChip

Silicon Bring-up · All levels

ATE Correlation & Test

Methodical correlation between automatic test equipment and bench data, disciplined test-program bring-up, practical yield and binning foundations, and the release process that turns engineering tests into stable production screening.

Section goal

Methodical correlation between automatic test equipment and bench data, disciplined test-program bring-up, practical yield and binning foundations, and the release process that turns engineering tests into stable production screening.

How to study this section

  1. Start with each topic hub and restate first-failure boundaries in your own words.

  2. Use reports and debug pages to separate symptoms from root-cause classes.

  3. Practice worked examples and interview drills under fixed metadata.

  4. Close with checklist and silicon impact before signoff claims.

Topics

  1. ate-vs-bench-correlation/ - ATE vs Bench Correlation: Measurement Integrity Before Debug

  2. test-program-bringup/ - Test Program Bring-up: From Characterization Script to Screening Flow

  3. yield-and-binning-basics/ - Yield and Binning Basics: Turning Parametrics Into Business Decisions

  4. production-test-handoff/ - Production Test Handoff: Release Discipline, Controls, and Sustaining Loop

Related topics

Silicon bring-up deep dive

Correlation succeeds when tester and bench experiments share identical conditions and evidence expectations.

Concept diagram

diagram
CORRELATION LADDER

ATE fail bin -> extract pattern -> reproduce on bench -> reconcile deltas

Metric graph

diagram
CORRELATION CONFIDENCE

unmatched signatures     █████
partial matches          ████
full context matches     ███████

Metrics and artifacts to collect

  • ATE-to-bench signature match ratio

  • pattern replay fidelity score

  • environment mismatch incident rate

  • yield-impact closure tracker

Mini case study

Correlation speed improved dramatically after enforcing shared metadata headers and one replay protocol across tester and lab.

Debug branches

  • Normalize V/F/T and pattern-window metadata first.

  • Audit fixture and probing assumptions before silicon blame.

  • Require repeatable signature in both environments before closure.

Senior review question

Ask: what is the first failing boundary, which artifact proves it, and who owns bounded closure?

Practice this lesson