4.1.8 · D2Memory Technologies

Visual walkthrough — Flash memory (NOR vs NAND)

1,893 words9 min readBack to topic

This is the picture-derivation behind the parent topic. If any word below feels unfamiliar, it gets defined the moment it appears.


Step 1 — What is ? The smallest thing the factory can draw

WHAT we did: named the fundamental unit of length on a chip.

WHY this and not nanometres directly: if we count everything in "pencil strokes" , the shape of a memory cell has a size that does not depend on which factory built it. A cell is whether or . It makes cells comparable across generations.

PICTURE: below, one stroke of width , and the smallest possible gap (also ) beside it. You literally cannot squeeze two lines closer than apart, or the light bleeds and they merge.

Figure — Flash memory (NOR vs NAND)

Step 2 — One cell needs a line AND a gap, in both directions

WHAT we did: set the ideal packing rule — active region , isolation gap .

WHY a gap at all: two transistors touching would leak current into each other (the switches would interfere). The gap is the minimum insulation, and the minimum printable gap is exactly .

PICTURE: the pitch (repeat distance) of a row of cells is . Same going up. So the smallest a cell footprint can ever be is across by tall.

Figure — Flash memory (NOR vs NAND)

Every term: the first is one horizontal pitch (a wire plus its gap); the second is one vertical pitch; multiplied, they give the area of the single smallest possible cell — the ideal.


Step 3 — Why NOR can't reach : the contact tax

WHAT we did: added the thing NOR cannot avoid — a private contact per cell.

WHY it costs area: a contact needs its own stroke of width, its own surrounding gap so it doesn't short to neighbours, plus extra isolation. Counting strokes, a NOR cell spreads to roughly strokes one way and the other:

The first factor is inflated by the contact and its isolation; the second is still one pitch. Result: , about the ideal.

PICTURE: two NOR cells, each with its own fat contact plug eating space between them.

Figure — Flash memory (NOR vs NAND)

Step 4 — Why NAND reaches : share one contact across many cells

WHAT we did: amortised the contact tax over a long chain.

WHY it works: inside the string, neighbouring cells simply touch source-to-drain — no gap, no contact between them. Only the two ends of the string touch the outside world. So per cell you're back to just line + gap = .

PICTURE: a NAND string of beads sharing end-contacts; the per-cell box shrinks back to the ideal .

Figure — Flash memory (NOR vs NAND)

The ratio says: on identical silicon, 2.5 NAND cells fit in the space of one NOR cell. Each symbol: numerator = NOR area, denominator = NAND area, both in so the cancels — a pure count.


Step 5 — The second multiplier: bits per cell from voltage levels

WHAT we did: turned "how full is the bucket" into a number of distinct symbols .

WHY and not just : bits count yes/no questions. With equally-likely levels, the number of binary questions needed to pin one down is . Two levels 1 question 1 bit; four levels 2 questions 2 bits. That is exactly the definition of : "2 to what power gives ?"

Here is bits stored, is the count of usable voltage windows, and converts a symbol count into a bit count.

PICTURE: the axis sliced into 2, 4, 8, 16 windows (SLC→QLC). More slices = more bits, but the gaps between windows shrink — the source of QLC's fragility.

Figure — Flash memory (NOR vs NAND)
Name
SLC 2 1
MLC 4 2
TLC 8 3
QLC 16 4

Step 6 — Multiply the two effects: total density advantage

WHAT we did: combined the geometric win with the level win.

WHY multiply (not add): "2.5× as many cells" and "3× as many bits in each cell" compound — like doubling the number of shelves and tripling the books per shelf.

So TLC NAND stores about more bits per unit area than SLC NOR — exactly the parent's claim, now derived from strokes and slices.

PICTURE: a bar showing the two multipliers stacking into the total.

Figure — Flash memory (NOR vs NAND)

Step 7 — The degenerate cases (never leave a gap)

  • (one level): bits. A cell that can only ever be in one state stores nothing — you can't distinguish anything. The formula correctly returns 0.
  • Zero-length string (NAND with 1 cell): if a "string" holds only one cell, both end-contacts belong to it — it degenerates back into the NOR case, no sharing, area balloons to . The ideal needs a long string to amortise contacts.
  • Ideal vs real : is a floor, never quite reached — real cells add margin. So published numbers () sit slightly above the ideal; the derivation gives the limit, not the exact fab number.
  • Reading a NAND cell: to sense one cell you must turn all other cells in its string fully on (pass-through). If even one neighbour is stuck, the whole string reads wrong — the price of sharing wires. This is why NAND reads a whole page, never a lone byte.

PICTURE: the collapse (zero bits) and the single-cell string collapse (back to NOR area) side by side.

Figure — Flash memory (NOR vs NAND)

The one-picture summary

Figure — Flash memory (NOR vs NAND)

Everything on one canvas: a pencil-stroke of width → the ideal cell → NOR's contact tax pushing it to → NAND's shared string pulling it to → the axis sliced into levels giving bits → the two multipliers compounding to .

Recall Feynman retelling — the whole walkthrough in plain words

The factory can only draw lines a certain thinness — call one stroke . The tiniest possible memory cell is one stroke of stuff plus one stroke of empty gap, in both directions: by , which is . But NOR wiring insists every cell get its own little metal plug (a contact) with insulation around it, and that plug fattens the cell to about . NAND's clever trick is to string a hundred-plus cells in a row and let the whole row share just two end-plugs — so per cell you're back down to the ideal , about 2.5 times denser than NOR. Then a second trick: instead of "bucket full or empty" (1 bit), you fill the bucket to several precise levels; levels store bits, so TLC's 8 levels give 3 bits. Both tricks multiply: 2.5× smaller cells times 3× the bits each is about 7.5× more storage in the same chip. Edge checks: one level stores zero bits (nothing to tell apart); a "string" of one cell loses the sharing and bloats back to NOR size; and is a floor real chips only approach, never beat.

Recall Quick self-test

Why is NAND denser than NOR at the cell level? ::: NOR needs a private contact + isolation per cell (~10F²); NAND shares end-contacts across a long series string, hitting the ideal ~4F². Why do bits per cell use and not ? ::: Bits count binary yes/no questions; is how many such questions distinguish one of equally-likely levels. What does the ideal require to actually hold? ::: A long series string so the two end-contacts are amortised to near-zero per cell; a 1-cell string collapses back to NOR area.