4.1.2 · D5Memory Technologies

Question bank — SRAM read - write operations

1,693 words8 min readBack to topic

Before we start, three words we lean on constantly — pinned here so no reveal uses an undefined term:


True or false — justify

True or false: An SRAM read is destructive, so the cell must be rewritten afterward like DRAM.
False. The cross-coupled latch is actively powered and continuously restores its own state, so nothing decays and no rewrite is needed — provided so the read disturbance never trips it.
True or false: During a correctly designed read, the internal node storing "0" stays exactly at 0 V.
False. Current flowing in from the pre-charged bit-line through the access transistor lifts that node to a small ; the design only guarantees stays below the inverter trip point, not zero.
True or false: Both bit-lines are pre-charged high before a read regardless of what bit is stored.
True. Pre-charge doesn't know the data; both go to , then float, and the cell pulls one down. Downward sensing is robust because the NMOS pull-down sinks current well.
True or false: A stronger (wider) access transistor always improves the cell.
False. It helps writes but hurts reads — a strong access transistor injects more current into the "0" node, raising toward the trip point and risking read upset. It's a squeeze, not a free win.
True or false: To write a 0 you only need to drive to 0 and leave alone.
False. You drive both lines complementarily (); forcing both sides lets the cross-coupling regenerate the new state instead of leaving a marginal, possibly-not-flipped cell.
True or false: Read stability and write-ability push the access transistor in opposite directions.
True. Read wants access weak vs pull-down (); write wants access strong vs pull-up (). The single access transistor must satisfy both simultaneously — that trade-off is SRAM sizing.
True or false: Making the PMOS pull-up very strong makes the cell better because it holds "1" firmly.
False. A strong pull-up firmly resists being overwritten — it holds up during a write and can cause write failure. Pull-ups are deliberately kept the weakest device.
True or false: The word-line being high is what selects a row for both reading and writing.
True. WL gates the access transistors M5/M6; asserting it connects to the bit-lines. The bit-line drive/sensing then decides whether it's a read or a write.
True or false: If exactly, the read is guaranteed safe.
False. means access and pull-down are equally strong, so rises to roughly half — right at the danger zone. You need (typically 1.2–2) with margin, or noise pushes it over the trip point.

Spot the error

"During a read, the cell sources current onto the bit-line to charge it high." — what's wrong?
Reading works the other way: bit-lines are already pre-charged high, and the cell only needs to sink current to pull one down. We rely on strong NMOS sinking, not weak PMOS sourcing.
"Cell ratio and we want it large." — fix it.
It's inverted. , and we want it >1 so the pull-down out-muscles the access transistor and keeps low.
"Write succeeds when the pull-up PMOS pulls the node below the trip point." — what's wrong?
The PMOS pulls toward ; it's the enemy of the write. The access transistor (via ) must pull the node below the trip point against the PMOS.
"Read upset happens when the stored-1 node gets pulled too low." — correct the mechanism.
Upset happens on the stored-0 node: current from the high bit-line lifts up above the trip point. It's an unwanted rise on the low node, not a fall on the high node.
"Because writes drive the bit-lines hard, the access transistor's size doesn't matter for writing." — spot the error.
It matters critically. The access transistor is the device that must conduct the bit-line's 0 into the node and overpower the pull-up (). A weak access transistor can't win even with .
"A larger on the bit-lines during read means the cell is being disturbed more." — what's confused here?
is the useful signal the sense amplifier needs; it develops on the bit-line being pulled down. Disturbance is measured by the internal node rise, a separate quantity — a healthy read has good and small .

Why questions

Why do we pre-charge bit-lines high rather than low before a read?
Because the pull-down NMOS sinks current strongly and reliably, so letting the cell drag a high line down is robust; asking a weak PMOS to source a low line up would be slower and noisier.
Why can't one access transistor size be perfect for both read and write?
Read needs it weak (vs pull-down, ) to avoid disturbing; write needs it strong (vs pull-up, ) to force a flip. One device can't be both simultaneously — hence a compromise "sweet spot" governed by W/L sizing.
Why is the pull-up (PMOS) usually the smallest/weakest of the three device types?
It must not hold the node up so stubbornly that a write fails, and reads never rely on it to source current. Weak pull-up eases writes while the actively-latched pair still holds data fine.
Why does the write flip "regenerate" once the node crosses the trip point?
Crossing the trip point flips the other inverter's output, which is cross-coupled back to reinforce the new value on the first node — a positive-feedback loop (bistability of the inverter pair) that snaps the cell fully into the new state.
Why do we sense the difference instead of one line's absolute voltage?
Differential sensing cancels common-mode noise and needs only a tiny , letting the sense amplifier decide fast and correctly even before either line swings to a full logic level.
Why does read upset relate to Static Noise Margin?
SNM is the largest noise voltage the latch can tolerate before flipping; the read-time rise eats into that margin. Sizing for keeps the disturbance well inside the SNM.
Why does SRAM need no refresh while DRAM does?
SRAM stores the bit as a stable powered state of the latch, not as charge on a capacitor. Nothing leaks away, so the value persists as long as power is on.

Edge cases

Edge case: What happens if you assert WL but never pre-charge the bit-lines?
The bit-lines sit at whatever leftover/leakage voltage they had, so the sense amp gets an undefined or wrong — the read result is unreliable even in a perfectly sized cell.
Edge case: Both and are accidentally driven to 0 during a "write."
You pull both internal nodes down; the complementary-restoring feedback has nothing to latch onto, leaving the cell in an undefined/contended state — it's why writes must drive complementary values.
Edge case: WL is left high after a read (never de-asserted).
The cell stays connected to the floating bit-lines, prolonging the read disturbance and blocking a clean pre-charge for the next access — can drift toward the trip point, risking a delayed upset.
Edge case: A cell with (access stronger than pull-down) — what fails and when?
Reads fail: rises above the trip point and the cell flips (read upset). Writes may work fine, but you've traded away data integrity — unacceptable for a memory.
Edge case: A cell with a very weak access transistor and weak pull-up.
Reads are safe (low disturbance) but writes may still be marginal if the access transistor is too weak to swing the node — you must check both ratios, not just one.
Edge case: Supply is lowered aggressively (low-power cache).
The trip point and SNM shrink, so the same disturbance becomes a larger fraction of the margin — read upset and write failure both worsen, which is why low-voltage SRAM needs careful re-sizing or assist circuits.

Parent: SRAM read - write operations · Hinglish: 4.1.02 SRAM read - write operations (Hinglish)