6.5.2 · D3 · HinglishAdvanced & Emerging Architectures

Worked examples2.5D packaging and interposers

2,487 words11 min read↑ Read in English

6.5.2 · D3 · Hardware › Advanced & Emerging Architectures › 2.5D packaging and interposers

Yeh page 2.5D packaging and interposers ka drill floor hai. Parent note ne tumhe tools diye; yahan hum unhe har possible case mein run karte hain — bade dies aur chote dies, zero aur infinity defect densities, energy comparisons, bandwidth budgets, ek real-world word problem, aur ek exam-style trap.

Numbers se pehle, ek promise: neeche use kiya gaya har symbol ya toh parent note define karta hai ya yahan re-define kiya gaya hai. Agar tum , , , , , , , pehli baar dekh rahe ho, toh is line ke neeche wali table batati hai ki har ek ka kya matlab hai.

Do master formulas jo hum har jagah reuse karte hain (parent se):


The scenario matrix

Neeche har worked example is matrix ke cell ke saath tagged hai jise wo cover karta hai. Saath milke yeh sab cells ko touch karte hain.

Cell Kya vary karta hai "Edge" jo hum test karte hain
C1 Small area small Yield near 1 — chiplet regime
C2 Large area large Yield collapse — monolithic regime
C3 Zero defects Degenerate: , chiplets se koi yield benefit nahi
C4 Huge defects Limiting: , kuch nahi bachta
C5 Split-vs-whole fixed total , zyada cuts Kitne chiplets "enough" hain?
C6 Energy ratio change Interposer vs PCB energy per bit
C7 Bandwidth budget Kya bus fit hoti hai? (word problem)
C8 Exam twist mixed Overhead costs / jab 2.5D haare

C1 + C2 — Yield dono extremes par

  1. Chota area plug karo. . Yeh step kyun? die par zero defects hone ki probability hai; chota ⇒ chota exponent ⇒ near 1.
  2. Evaluate karo: ≈ 81.9% good.
  3. Bada area plug karo. . Yeh step kyun? Same formula; bada ⇒ bada exponent ⇒ 0 ki taraf crush ho jaata hai.
  4. Evaluate karo: ≈ 4.1% good.
Recall Area itni violently kyun hurt karta hai?

Kyunki area exponent mein hota hai. Area double karne se yield half nahi hoti — yeh survival penalty ko square kar deta hai. Yahi exponential chiplets ke exist karne ki poori economic reason hai.

Verify: exponents aur ka sign sahi hai (negative → ). Tiny die (81.9%) giant (4.1%) ko ~20× se beat karta hai, jo "chote dies defects se bachte hain" intuition se match karta hai.

Figure — 2.5D packaging and interposers

C3 + C4 — Degenerate limits

  1. Zero-defect case. kisi bhi ke liye. Yeh step kyun? Agar koi defects kabhi nahi girte, toh har die — badi ya choti — perfect hai. Exponent vanish ho jaata hai.
  2. Consequence: jab , chiplets zero yield advantage dete hain. 2.5D ke liye yield argument sirf isliye exist karta hai kyunki hota hai. (2.5D phir bhi reticle limit aur node-mixing par win kar sakta hai, lekin yahan yield par nahi.)
  3. Huge-defect case. . Yeh step kyun? Defects ki large mean number ⇒ near-certain ki kam se kam ek toh girega ⇒ almost kuch nahi bachta.
  4. Limit check: jaise , . Koi bhi packaging trick ek broken fab ko nahi bachaa sakti.

Verify: ( se independent, correct degenerate behaviour). ek tiny positive number hai — kabhi exactly zero nahi, toh even ek bad fab kuch silicon yield karta hai, jaise physics demand karta hai.


C5 — Kitne chiplets "enough" hain?

  1. Per-chiplet area hai . Per-chiplet yield . Yeh step kyun? System ko pieces mein cut karne se har piece ki area shrink hoti hai, jo har piece ki individual survival probability badhata hai.
  2. Monolith : → 13.5% whole chips good.
  3. 4 chiplets : → har chiplet 60.7% good.
  4. 16 chiplets : → har chiplet 88.2% good. Yeh step kyun? Jaise badhta hai, exponent , toh — har tiny die near-perfect ho jaata hai.
  5. The catch (infinite chiplets kyun nahi?): har extra cut microbumps, interposer wiring, aur assembly cost add karta hai. Individual dies ki yield diminishing return ke saath badhti rehti hai, jabki packaging overhead linearly badhta hai. Woh trade-off — sirf yield nahi — sweet spot set karta hai (practice mein usually 2–8 chiplets, dekho Chiplets and Heterogeneous Integration).
Recall

kya approach karta hai jaise ? . Individual yield 1 par saturate ho jaati hai — pure diminishing returns.

Verify: sequence strictly increase karta hai 1 ki taraf jaise badhta hai, aur har ek ke equal hai. Gaps shrink hoti hain ( vs ) — diminishing returns confirm karta hai.


C6 — Energy per bit: interposer vs PCB

  1. Energy formula. . Yeh step kyun? Ek bit bhejna matlab wire ki capacitance ko tak charge karna; ek capacitor ki charging energy hoti hai jisme .
  2. ek baar compute karo. . Yeh step kyun? Dono cases same voltage share karte hain, toh re-work se bachne ke liye ise factor out karo.
  3. PCB: = 1.28 pJ/bit.
  4. Interposer: = 0.0128 pJ/bit.
  5. Ratio. 100× kam energy. Yeh step kyun? Jab aur identical hain, energy purely length ke proportional hai, toh ratio length ratio hai. (Reality mein interposer ki finer geometry bhi lower karti hai, jisse win aur bada ho jaata hai.)

Verify: units — ✓. Numbers: vs , ratio exactly . ✓


C7 — Bandwidth budget (real-world word problem)

  1. Raw bandwidth in bits/s. . Yeh step kyun? Bandwidth lanes × per-lane rate hai; 1024 wires mein se har ek per second transfers carry karta hai, har ek 1 bit ka.
  2. Bytes/s mein convert karo. 8 se divide karo: 409.6 GB/s. Yeh step kyun? Storage/bandwidth targets bytes mein quote kiye jaate hain (8 bits = 1 byte).
  3. Target meet kiya? haan, comfortably.
  4. Kya PCB 1024 wires route kar sakta hai? PCB pitch ~100 µm par, 1024 wires ko data ke liye ~ edge chahiye — ~5 mm die edge ke saath impossible. Interposer pitch ~1 µm par, inhe sirf ~1 mm edge chahiye. Yeh step kyun? Parallelism se bandwidth useless hai agar tum physically wires place nahi kar sakte; yahi exact reason hai ki HBM ek interposer par ship hoti hai. Dekho High Bandwidth Memory (HBM).
Recall PCB HBM ki bus kyun carry nahi kar sakta?

1024 wires at 100 µm pitch ⇒ ~102 mm routing edge; die edge sirf kuch mm hoti hai. Sirf ~1 µm interposer pitch inhe fit karta hai.

Verify: bits/s; ÷8 = B/s = 409.6 GB/s ≥ 300 ✓. PCB edge needed ✓.


C8 — Exam twist: 2.5D kab haarta hai?

  1. Monolith yield. . Yeh step kyun? Single die ka baseline good-fraction.
  2. Cost per good monolith ("area units" mein) . Yeh step kyun? Agar sirf 81.9% bachte hain, toh ek acha paane ke liye tumhe dies-worth area fabricate karni padegi.
  3. Chiplet yield. har chiplet ; ek system ko dono achha chahiye: . Yeh step kyun? Do independent dies ko dono pass karna hoga; probabilities multiply karo. Notice karo — monolith ke identical total silicon-yield, kyunki total area unchanged hai!
  4. Chiplet cost overhead ke saath. Good silicon per system , phir 40% packaging tax apply karo: . Yeh step kyun? Interposer aur assembly real costs hain jo monolith nahi pay karta.
  5. Compare karo. Monolith 1.2215 vs chiplet 1.710 → monolith yahan sasta hai. Yeh trap kyun kaam karta hai: chote area par, split karne se yield gain tiny hota hai (dono dete hain), toh 40% overhead dominate karta hai. Chiplets sirf tab jeetate hain jab large ho (C2) aur yield gain overhead ko outweigh kare.

Verify: monolith cost ; chiplet total yield (monolith ke equal), cost ; toh monolith jeet jaata hai ✓.


Recap: kis cell ne kya sikhaya

Recall Matrix fill karo

C1/C2 — yield near 1 vs collapsed, sab exponent se ::: Chota ; bada . Area exponent mein rehta hai. C3 — implication ::: kisi bhi area ke liye; chiplets zero yield benefit dete hain. C4 — limit ::: ; koi bhi packaging broken fab ko nahi bachata. C6 — energy ratio equal hai ::: length ratio ke (jab match karte hain): 100× shorter wire ⇒ 100× kam energy. C7 — HBM ko interposer kyun chahiye ::: 1024 wires PCB pitch par fit nahi hoti; sirf ~1 µm interposer pitch inhe route karta hai. C8 — chiplets kab haarte hain ::: Jab area chota ho, yield gain tiny hota hai aur packaging overhead dominate karta hai.

Related builds: Wafer Yield and Defect Density, Reticle Limit and Lithography, 3D Stacking and TSVs, Moore's Law and its Slowdown, Package Substrate and Ball Grid Array.