4.1.2 · D3Memory Technologies

Worked examples — SRAM read - write operations

3,350 words15 min readBack to topic

This page hunts down every case an SRAM read/write problem can throw at you. Before we start, remember the two numbers that decide everything (built in the parent note):

  • Cell ratio — governs whether a read stays safe.
  • Pull-up ratio — governs whether a write succeeds.

Everything below is just plugging real numbers into these two ideas. If a symbol here feels new, it was earned in the parent note — glance back, then continue.

where is the transistor pulling toward ground (0 V) and is the transistor pulling toward . We will use this single formula in every example. Read it as: "the node sits closer to whichever resistor is smaller." The figure below is the picture to keep in your head for all eleven examples.

Figure — SRAM read - write operations

Look at the figure: the yellow NODE dot is the internal storage node ( or ). The pink (pulls to ) and blue (pulls to ground) are the two "on" transistors fighting over it. Every example just swaps which transistor plays top and bottom, and what voltage each end pulls toward.


The scenario matrix

Every SRAM read/write question is one (or a mix) of these cells:

# Case class What's being tested Example
A Read, safe () node stays below trip, no upset Ex 1
B Read, upset () node rises above trip, data lost Ex 2
C Read, boundary () the exact tipping point Ex 3
D Write, success (access beats pull-up) node forced below trip Ex 4
E Write, failure (pull-up too strong) node stuck above trip Ex 5
F Degenerate: WL off access transistors open → hold mode Ex 6
G Which bit-line droops (sign/direction) reading the correct bit Ex 7
H Real-world sizing (word problem) pick to satisfy both constraints Ex 8
I Exam twist: both must hold find the access-width window Ex 9
J Limiting case ( or ) what happens at the extremes Ex 10
K Write boundary () the exact write tipping point Ex 11

Because "strength" of a MOSFET rises with and its on-resistance falls with , we freely translate between "stronger transistor" ⇄ "smaller resistance". See MOSFET sizing (W/L) for why .

Fixed constants for all numeric examples unless stated otherwise: , inverter trip point .


Case A — Read, safe


Case B — Read, upset


Case C — Read, exact boundary


Case D — Write, success


Case E — Write, failure


Case F — Degenerate: word-line off


Case G — Which bit-line droops (sign/direction)


Case H — Real-world sizing (word problem)


Case I — Exam twist: both constraints at once


Case J — Limiting case


Case K — Write, exact boundary


Recall Recall check

In a read, is the node dragged toward the smaller or larger of its two resistances? ::: Toward the smaller resistance (that transistor wins the tug-of-war). What single comparison decides upset vs. safe read? ::: Whether the disturbed node voltage is below (safe) or above (upset) the trip point . Where is the read cliff and where is the write cliff? ::: Read cliff at (Ex 3), write cliff at (Ex 11); both put the node exactly at half rail. Why does Ex 9 produce a window rather than a single value? ::: Read imposes an upper bound on access strength, write imposes a lower bound; only their overlap is legal.