semiAIfoundry

Memory / HBM fabrication and assembly · Atlas v1.3.0

HBM stack assembly, repair and staged test

Combines screened memory dies into a delivered stack using a specified joining route.

Explore in AtlasDRAM cell to vertical stack; routes and logical mapping are separate

Learning objectiveTrace a named HBM assembly route and place screening at valid population boundaries.

The mechanism

An HBM stack is assembled from memory dies that have already passed substantial wafer processing and screening. Thin dies are aligned and joined so vertical connections continue through the stack. SK hynix’s public MR-MUF description combines mass reflow joining with molded underfill; thermocompression-based flows use a different joining sequence and material arrangement. The atlas labels these alternatives instead of mixing their steps into one recipe. Testing can occur at die, partial-stack, completed-stack and final-package boundaries, with coverage shaped by available access. Qualification releases a product/process configuration; it is distinct from screening every stack produced on that route.

  1. Select compatible screened dies and retain their identity and repair/bin status.
  2. Align supported thin dies and establish vertical joint continuity using the named assembly route.
  3. For the MR-MUF example, distinguish collective reflow from the subsequent protective molding/underfill role.
  4. For a thermocompression alternative, preserve its actual joining and material sequence instead of borrowing MR-MUF order.
  5. Perform the defined intermediate/final tests and count released stacks separately from qualification samples.

Science and assumptions

Assembly-stage yield

Nout=Nready∏iyiN_{\mathrm{out}}=N_{\mathrm{ready}}\prod_i y_i

Expected output equals complete screened input sets times each successive stage’s conditional survival fraction.

The yiy_{i} values are conditional on reaching each stage. The chain product does not itself require unconditional stage independence, but double-counted losses or unmodeled rework invalidate this simple path.

Symbols and units
N_out
Expected surviving assembled outputs

stacks

N_ready
Complete screened compatible input sets

sets

yᵢ
Conditional survival of the incoming population at new stage i

fraction

i
Ordered assembly/test stage index

integer index

NreadyN_{\mathrm{ready}} counts complete compatible input sets after screening; each yiy_{i} is conditional survival through a new stage.

Assumptions Stage factors require defined populations and nonoverlapping losses. Rework, repair and shared-cause failures need explicit branches.

Engineering example

Synthetic inventory: 100 complete sets of screened dies encounter two new stages with 0.98 and 0.97 conditional survival. Expected output is 95.06 stacks before other losses, without reapplying original wafer yield.

Distinctions and tradeoffs

Multiplying raw die yield through a stack of already screened dies double-counts losses and misstates incoming quality.

Earlier test can avoid consuming good parts in a bad assembly but needs test access and adds handling/time; later test observes more completed interfaces.

A logic die cannot become a memory-equipped accelerator until compatible good stacks are available in the required quantity.

Specifications and interfaces

Incoming quality
Conditional quality after defined screening

Raw DRAM wafer yield has already affected available die count.

Test boundaries
Die, stack and final package

Each boundary adds or observes different failure opportunities.

Interfaces

Screened thin dies and base Input
Known genealogy, compatible interfaces and assembly materials
Tested HBM stack Output
Defined capacity, interface behavior and release status

Check your understanding

What yield term belongs after an inventory of known-good dies has already been counted?

  1. An assumed perfect finished-stack yield
  2. New assembly losses and residual conditional incoming defects
  3. The same raw wafer yield applied again to every die
Answer and reasoning

New assembly losses and residual conditional incoming defects

The population at the input boundary determines which losses remain to be modeled.

Evidence and scope

No vendor stack-yield, repair coverage or process recipe is asserted. Stack qualification and current volume status must be supported separately.

Propagate conditional assembly and final-test survival from already screened inputs; test coverage and common-cause failures require separate evidence.

Sources

Published lesson data · Atlas releases and licensing

Continue exploring

Foundations

Related lessons