How Chiplet Test Strategies Are Forcing a Rethink of Known-Good-Die Economics
P. NakamuraNobody writes headlines about test engineers. That's a mistake.
Photo by Maksim Goncharenok on Pexels.
When a chiplet-based design fails at final package assembly, you don't just lose the bad die, you lose every good die stacked or bonded alongside it. A single untested defect inside a 3D package can brick $800 worth of silicon. That math is why known-good-die (KGD) qualification has quietly become one of the most expensive unsolved problems in advanced packaging.
The Yield Multiplication Problem
Monolithic SoC yield follows a simple curve: bigger die, more defects, lower yield. Chiplets were supposed to fix that by shrinking individual die sizes and multiplying yield across the package. In principle, it works. A 5nm compute chiplet at 50mm² has far better yield than a 300mm² monolithic equivalent.
But here's the catch: package-level yield is the product of all individual chiplet yields. Bond five chiplets with 98% individual yield each, and your assembled package yield drops to roughly 90%. Add thermal interface failures, bump opens during reflow, and substrate-level escapes, you're looking at 85% or lower before you've tested a single functional path end-to-end.
The only way to defend package yield is to ensure every die entering assembly is genuinely known-good. Not "passed wafer probe." Known good, stress-screened, validated at speed and voltage, with enough margin confidence that the test result actually predicts field behavior.
Where Wafer Probe Falls Short
Traditional wafer-level probe tests electrical continuity and basic logic. It was designed for monolithic dies that would sit in a single-chip package with accessible I/Os. Chiplet interconnects break several of its assumptions.
Die-to-die interfaces running at 32 GT/s through UCIe or MDIO links require controlled impedance, tight skew alignment, and specific equalization tuning, none of which wafer probe can replicate at scale. You can't stress a high-speed serial link properly when your probe card parasitic capacitance is adding 0.5 pF per bump. The test itself corrupts the signal you're trying to validate.
Worse, vertical integration formats like hybrid bonding present bumps at sub-10µm pitch. Standard probe needles physically cannot land on them without risking bond pad damage. The test access problem becomes geometric.
graph TD
A[Wafer Probe] --> B{Passes Basic Electrical?}
B -- No --> C[/Scrap Die/]
B -- Yes --> D(KGD Stress Screen)
D --> E{Passes at Speed + Voltage?}
E -- No --> C
E -- Yes --> F[Known-Good Die]
F --> G((Package Assembly))
The Reconstituted Wafer Workaround
One approach gaining real traction: test dies in reconstituted wafer format before bonding. You singulate dies from the source wafer, embed them in a temporary carrier that mimics final package geometry, then run full-speed electrical test through the carrier's redistribution layer. This gives you controlled impedance and proper signal return paths, the things wafer probe can't provide.
TSMC's CoWoS flow and Intel's Foveros process both incorporate variants of this. The tradeoff is cost and throughput; reconstitution adds two to three days of processing per wafer lot. For high-margin AI accelerators, that's acceptable. For cost-sensitive edge chiplets? Less obvious.
Burn-In at the Die Level: Finally Practical?
Burn-in, running devices under elevated temperature and voltage to precipitate infant mortality failures, has historically happened at package level. Moving it upstream to bare die is appealing: catch the defects before they contaminate a $400 HBM stack.
The problem has always been handling. Bare dies are fragile; contacting them repeatedly at temperature without introducing new damage is hard. Several startups are now offering temporary bonding solutions specifically for KGD burn-in, using compliant micro-spring contacts that can hit sub-100µm pitch pads without the force spikes that crack thin backend-of-line stacks.
Early data from contract test houses suggests die-level burn-in can reduce post-assembly early-life failures by 60–70% in stacked DRAM configurations. That's not a marginal improvement. That changes the warranty cost model for a chiplet product.
The Economics Haven't Settled Yet
Here's what the industry hasn't fully worked out: who pays for KGD testing, and how does that cost flow through the supply chain? A fabless chiplet vendor selling compute dies to an OSATor a systems integrator needs to certify KGD status, but the test costs real money, typically $5–$15 per die depending on complexity. Pass that cost upstream and you erode the price advantage of disaggregation. Absorb it and your margin model breaks.
The answer probably looks like standardized test interfaces baked into chiplet specifications, something UCIe's physical layer spec gestures toward but doesn't yet fully mandate. Until test access is a first-class design requirement rather than an afterthought handled post-tapeout, KGD economics will remain a friction point that dampens the yield math chiplets are supposed to deliver.
The silicon is getting smaller. The test problem isn't.
Get Chiplet Ecosystem in your inbox
New posts delivered directly. No spam.
No spam. Unsubscribe anytime.