Write Error Rate

Write error rate is the uncomfortable flip side of the same thermal randomness that makes MRAM retention possible in the first place: the identical stochastic process that occasionally flips a bit by accident when it should stay put also means a deliberate write pulse does not switch the cell with one hundred percent certainty every single time — switching an MRAM cell on purpose is itself a probabilistic event, not a guaranteed one.

A Write Pulse Lowers the Barrier — It Does Not Erase It switching still depends on thermal assistance crossing whatever barrier remains during the pulse No write current — full barrier tall E_barrier During a write pulse — current tilts and lowers the barrier lowered E_barrier — easier, but still finite thermal assist still required to finish the crossing A short or weak pulse can end before thermal assistance completes the crossing That incomplete crossing is a write failure — the cell is read back still holding its old value.

The mechanism is the mirror image of the retention process described by thermal stability factor, run with the barrier deliberately weakened rather than left at full height. A spin-transfer-torque or spin-orbit-torque write current does not instantaneously force the free layer's magnetization to the opposite state the way flipping a mechanical switch would; it tilts the energy landscape, lowering the barrier between the two states and biasing the system toward the target state, but the actual crossing still requires the same kind of thermally-assisted fluctuation that causes accidental retention failures — just made far more likely to succeed within the pulse duration because the barrier is now much lower. If the write pulse is too short, too weak, or an unlucky thermal fluctuation simply does not arrive in time, the crossing does not complete before the current is removed and the barrier returns to its full height, leaving the cell exactly where it started.

Write error rate is quantified as the probability that a single write pulse fails to switch the cell, and because the underlying process is genuinely stochastic, that probability can never be reduced to exactly zero through write pulse design alone. Longer or stronger write pulses increase the probability of a successful crossing within the available time, pushing the write error rate down toward acceptably low levels — commercial MRAM designs typically target a write error rate low enough that errors occur in roughly one in a million write attempts or better — but driving it to a mathematical zero would require either an infinitely long pulse or infinite write current, neither of which is practical. This genuinely probabilistic character is why MRAM write operations, unlike a DRAM write or a simple logic gate transition, are specified with an error rate at all rather than treated as deterministic.

Longer Pulses Buy Lower Error Rate — At a Direct Cost the same curve this series keeps finding: more margin, paid for in time or energy pulse duration / current write error rate (log) short/weak pulse — high failure rate long/strong pulse — approaches but never reaches zero Error-correcting code and write-verify-and-retry are standard system-level answers to a floor that writing harder cannot fully close.

This is precisely the same shape of tradeoff thermal stability factor already described for retention, now applied to the opposite side of the same physics. A higher thermal stability factor buys longer retention at the cost of needing more write energy and time to overcome that same barrier on purpose; a lower write error rate at fixed pulse parameters is bought the same way, by spending more write current or more pulse duration to push the probability of a successful crossing higher within the available window. Both quantities trace back to the identical underlying stochastic barrier-crossing process — retention failure is an unwanted crossing with no applied assistance, write failure is a wanted crossing that assistance still does not guarantee — which is why MRAM designers cannot independently optimize retention, write speed, write energy, and write error rate; all four are different measurements of the same thermally-activated switching physics, pulling against each other through the shared energy barrier.

System-level mitigation exists specifically because write pulse design alone cannot close this gap, mirroring the same philosophy this series has already seen in NAND's incremental step pulse programming. A write-verify-and-retry scheme reads back the cell immediately after a write pulse and reissues the pulse if the intended state was not reached, directly analogous to ISPP's pulse-then-verify loop for NAND, though here the retry exists to overcome stochastic failure rather than analog undershoot. Error-correcting code adds redundant bits so that an occasional failed write, caught later at read time rather than immediately, can still be corrected rather than silently corrupting data — a system-level safety net for a physical write error rate floor that pulse design can push arbitrarily low but never fully eliminate.

QuantityWhat raises itWhat it costs to improve
Thermal stability factor (Δ)Taller energy barrierMore write current/time per bit
Write error rateWeaker/shorter write pulseLonger or stronger pulses, more write energy
Retention timeHigher ΔHarder, slower writes (shared tradeoff)
System-level fixWrite-verify-retry, ECCExtra read-back cycles or redundant bits

Write error rate is the admission that MRAM's write operation inherits the same probabilistic character as its retention mechanism, because both are the same thermally-activated barrier-crossing physics viewed from opposite directions. Pulse design can push the error rate arbitrarily low but never to true zero, which is exactly why MRAM systems — like the NAND systems this series has already covered — layer write-verify-retry and error correction on top of the physical write operation rather than trusting a single pulse to always succeed.

Take write error rate further

Ask the copilot about this term, or have our engineers assess it against your process.