SSD, HBM and DRAM Atlas

Take an SSD, an HBM stack and a DDR5 memory stick apart in one window, from the board down to a single memory cell.

One drive, ten systems

An SSD is a coordinated collection of memory, firmware, power delivery, and high-speed signaling. Each card points to its part on the drive; open it and the Atlas takes you down through it, one named stop at a time.

The reference M.2 SSD seen from straight above: connector, controller, DRAM and two NAND packages

One package, many layers

HBM is wide, stacked DRAM sitting beside compute on a 2.5D package. Here the package is pulled apart; each layer card points to where that layer sits, top to bottom.

The accelerator package pulled apart: compute dies and an HBM stack lifted above the interposer, frame and substrate
  1. DRAM core die with banks
    Core die · DRAM banks
    01

    Core die

    One of the 12 DRAM dies, with bank arrays on both sides of a central stripe of vias and control strips between them.

    Open in the Atlas
  2. Microbumps between dies
    Microbumps · Die to die
    02

    Microbumps

    The tiny connections between stacked dies.

    Open in the Atlas
  3. HBM stack: core dies on a base die
    Stack · 12-high pile
    03

    Stack

    One HBM stack on its own: a base die under a 12-high pile of DRAM core dies. Twelve is the height drawn, a representative option rather than a measured count.

    Open in the Atlas
  4. Base logic die
    Base die · Logic layer
    04

    Base die

    The logic die at the bottom of the stack. Its face shows the interface (PHY) band, the through-silicon via area and a test port, as published floorplans describe.

    Open in the Atlas
  5. Accelerator package: compute dies and HBM stacks
    Package · 2.5D layout
    05

    Package

    A reference accelerator layout: compute dies, eight HBM stacks, an LSI bridge, and the substrate beneath them.

    Open in the Atlas

Inside the stack

  • Through-silicon vias
    TSVs · Vertical vias

    Through-silicon vias

    Vertical copper connections that carry signals and power through each die.

    Open in the Atlas
  • One-transistor, one-capacitor DRAM cell
    DRAM cell · One bit

    DRAM cell

    Keep going from the die down to a bank and the one-transistor, one-capacitor cell that stores a single bit.

    Open in the Atlas
  • Tours, glossary and sources
    Read · Controller to cell

    Follow a read

    The same read in DRAM: controller, PHY, channel, then the commands that open a row, read it and close it again at the cell.

    Open in the Atlas

One stick, two paths down

The DRAM specimen is a DDR5 server memory stick, an RDIMM with ECC. Its packages share the board with the parts that buffer, power and identify it; open one package and the Atlas goes down through the die to a single cell.

The reference DDR5 RDIMM in the Atlas: DRAM packages either side of the registering clock driver, gold edge pins along the bottom

On the stick

  • Registering clock driver

    Buffers the command, address and clock lines, so the memory controller drives one load instead of every package.

    Open in the Atlas
  • Power management IC

    DDR5 moved regulation onto the stick: the PMIC turns the board supply into the core, I/O and pump rails.

    Open in the Atlas
  • SPD hub

    Holds the stick’s identity and timings for the system to read at start, and reaches the temperature sensors.

    Open in the Atlas
  • Edge connector

    Pins front and back carry two independent subchannels, clock, command and power. The key notch fits a DDR5 slot only.

    Open in the Atlas

Down one package

  1. 01

    DRAM package

    The die lies face down on a substrate under the mold, wired through a slot to the solder balls.

    Open in the Atlas
  2. 02

    DRAM die

    Banks gathered into bank groups around a central stripe of control logic and pads.

    Open in the Atlas
  3. 03

    Bank

    Opens one row at a time: ACTIVATE opens it, READ follows, PRECHARGE closes it again.

    Open in the Atlas
  4. 04

    Subarray

    Rows of mats, each a field of cells with row drivers on one side and sense amplifiers on the other.

    Open in the Atlas
  5. 05

    Sense amplifiers

    The row buffer: when a row opens they read every cell on it at once.

    Open in the Atlas
  6. 06

    DRAM cell

    One transistor and one capacitor. The charge leaks, so every cell is refreshed again and again.

    Open in the Atlas

Five depths, three memories

Each row is one depth in the Atlas, with the SSD, HBM and the DDR5 stick side by side, so you can watch a NAND die and two DRAM dies shrink to one cell together. Every render opens at that exact stop.

The whole thing

measured in cm
The reference M.2 2280 SSD on a black board: the controller, DRAM and a row of NAND packages on its top face

SSDReference NVMe SSD

A generic M.2 2280 drive: controller, DRAM and NAND packages on both faces, and the parts that power them.

Open here in the Atlas
The reference accelerator package under its lid, on a dark substrate

HBMPackage

A reference SI accelerator package, lid on: compute and HBM stacks sit underneath.

Open here in the Atlas
The reference DDR5 RDIMM: a row of DRAM packages either side of the registering clock driver, gold edge pins along the bottom

DRAMDDR5 RDIMM

A DDR5 server memory stick with ECC: DRAM packages, the registering clock driver, its power and the edge pins.

133.35 × 31.25 mm sticksource

Open here in the Atlas

Package

measured in mm
A NAND package on the board, opened to show what is inside

SSDNAND package

One NAND package, opened up on the board.

14 × 18 mm bodysource

Open here in the Atlas
Compute dies and HBM stacks on the interposer with the lid lifted

HBMHBM stack

Lid off: an HBM stack beside the compute dies.

14.175 × 10.975 mm HBM4 bodysource

Open here in the Atlas
One DRAM package on the stick, the registering clock driver and the next package beside it

DRAMDRAM package

One DRAM package on the stick: the die sits inside, face down on its substrate.

10.0 × 11.0 mm bodysource

Open here in the Atlas

Die

measured in mm
The NAND die inside its package, its planes showing

SSDNAND die

The die inside, with its planes and the periphery that drives them.

128.5 mm² for a 64-layer diesource

Open here in the Atlas
An HBM stack beside the compute die, its top core DRAM die marked

HBMCore DRAM die

One core DRAM die in the stack, above the base die.

12.8 × 11 mm Samsung HBM4 diesource

Open here in the Atlas
The DRAM die drawn face up in its package: blocks of banks either side of a central stripe of pads

DRAMDRAM die

The die, drawn face up: its banks sit either side of a central stripe of control logic and pads.

66.26 mm² for a Micron 16 Gb DDR5 diesource

Open here in the Atlas

Array

measured in µm
A memory plane on the NAND die face, a row of word lines marked across it

SSDMemory plane

A memory plane: blocks of vertical strings, read a page at a time.

9.4 µm tall stringssource

Open here in the Atlas
A 16 by 16 patch of DRAM cell capacitors standing in rows

HBMCell array

A 16 by 16 patch of cells, capacitors standing over their transistors.

0.80 × 0.53 µm patchsource

Open here in the Atlas
A subarray: rows of mats, each a field of cells with a strip of sense amplifiers along one edge

DRAMSubarray

A bank built from rows of mats, row drivers on one side and sense amplifiers on the other.

Half a million to a million cells per matsource

Open here in the Atlas

One cell

measured in nm
One charge-trap cell cut open around its vertical channel

SSDCharge-trap cell

One charge-trap cell, cut open around its channel.

152 nm hole pitchsource

Open here in the Atlas
One DRAM cell: a capacitor above an access transistor

HBM1T1C cell

One bit: a capacitor and the transistor that opens it.

1,672 nm² cellsource

Open here in the Atlas
One DRAM cell: a capacitor standing on its access transistor between word and bit lines

DRAMDRAM cell

One transistor and one capacitor, rewritten again and again before its charge leaks away.

Open here in the Atlas

Follow one read through all three

The same read, traced three times: from the controller to a NAND cell, from the memory controller through the PHY to an HBM row that opens, reads and closes, and from the memory controller down a DDR5 stick to a bank and back out on the pins.

Now watch the parts work

The Atlas shows where everything sits. These simulators run in your browser and open up the parts that carry most of the behavior: the flash cell, the firmware that manages it, and the capacitors that decide what survives a power cut. They are teaching models, not vendor data.

Runs in your browserSimulator

NAND Cell Lab

An interactive threshold-voltage simulator that shows how P/E cycling, retention, temperature and read disturb push NAND cells toward bit errors.

Try this: Choose Wear in the walkthrough, then drag a read reference on the bench chart and watch the error-correction ladder change.

Open NAND Cell Lab

Runs in your browserSimulator

FTL & GC Sandbox

A flash translation layer and garbage-collection simulator that shows how overprovisioning, workload, TRIM and data placement change write amplification.

Try this: The card opens the 80-20 hot-cold drive from setup 4, Hot and cold data. Choose Separated and give it about 30 seconds: write amplification settles near 2.2 instead of about 2.4.

Open FTL & GC Sandbox

Runs in your browserSimulator

Power Loss Lab

Cut power to a simulated SSD mid-write and see which writes come back, with and without capacitor-backed power loss protection, old capacitors and flushes.

Try this: Scroll the five sections to see what capacitors, fsync and age change, then drag any setting in the sandbox and watch the cells.

Open Power Loss Lab

Pick a part and keep going down

Orbit the model, pick a part, and swap between the SSD, HBM and DRAM without losing your place in any of them.