Redundancy in Multi-Die Systems is the design strategy of including spare circuits, interconnects, and functional units within multi-chiplet packages to tolerate manufacturing defects and improve effective yield — enabling defective elements to be replaced by redundant spares through post-manufacturing repair, which is especially critical in large multi-die packages where the probability of at least one defect increases with die count and the cost of scrapping an assembled package is extremely high.

What Is Redundancy in Multi-Die Systems?

• Definition: The intentional inclusion of extra (redundant) circuit elements — spare memory rows/columns, backup TSVs, redundant die-to-die interconnect lanes, or even spare chiplets — that can be activated to replace defective elements discovered during testing, improving the effective yield of multi-die packages without requiring physical rework.
• Yield Recovery: In a multi-die package with millions of interconnections, the probability of zero defects is low — redundancy converts packages that would otherwise be scrapped into functional products by routing around defects.
• Memory Precedent: DRAM has used row/column redundancy for decades — a 16 Gb DRAM die typically includes 5-10% spare rows and columns, and repair during wafer test recovers 20-40% of dies that would otherwise fail. Multi-die systems extend this concept to inter-die connections and functional units.
• Interconnect Redundancy: Die-to-die links (micro-bumps, TSVs, hybrid bonds) can include spare connections — if a bump or via is defective, traffic is rerouted to a spare, maintaining full bandwidth.

Why Redundancy Matters for Multi-Die

• Yield Multiplication Problem: A package with 8 chiplets, each at 95% yield, has only 66% package yield (0.95⁸) — redundancy at the package level can recover many of these failures, potentially improving effective yield to 85-90%.
• HBM Stack Yield: An 8-high HBM3 stack has ~50,000 TSVs — even at 99.99% per-TSV yield, ~5 TSVs will be defective. Redundant TSVs allow the stack to function despite these defects.
• Cost Justification: Adding 5-10% redundant area costs relatively little but can improve package yield by 10-30% — for packages costing $2000-10,000, the yield improvement easily justifies the redundancy overhead.
• Reliability: Redundancy also provides in-field reliability — if an interconnect or circuit degrades over the product lifetime, spare elements can be activated to maintain functionality.

Types of Redundancy in Multi-Die Systems

• TSV/Micro-Bump Redundancy: Extra TSVs and bumps included in the die-to-die interface — typically 5-10% spare connections that can replace defective ones through electrical rerouting.
• Memory Redundancy: Spare rows, columns, and banks in HBM and on-chip SRAM — repaired during KGD testing using fuse or anti-fuse programming.
• Lane Redundancy: Die-to-die interconnect protocols (UCIe, Infinity Fabric) support lane degradation — if one lane fails, the link operates at reduced bandwidth using remaining lanes rather than failing completely.
• Die-Level Redundancy: Some architectures include spare chiplets — AMD EPYC can disable defective cores within a CCD, and products with fewer active cores are sold as lower-tier SKUs.
• Functional Redundancy: Spare compute units, cache banks, or I/O ports that can replace defective ones — GPU architectures routinely disable 1-2 defective streaming multiprocessors (SMs) and sell the chip as a lower-tier product.

Redundancy in multi-die systems is the yield engineering strategy that makes large chiplet packages economically viable — providing spare circuits, interconnects, and functional units that recover packages with manufacturing defects, converting would-be scrap into working products and enabling the high-die-count packages needed for AI GPUs and server processors to achieve production-worthy yields.