EEPROM, NOR Flash, or FRAM: Matching Nonvolatile Memory to the Job

Every product stores something it must not forget: calibration constants, user settings, a tamper log, an odometer. The three candidate technologies - serial EEPROM, SPI NOR flash, and FRAM - look interchangeable in a parametric table and behave very differently in a product that writes data every few seconds for ten years. The match is made by write pattern, not by capacity.

EEPROM: the byte-granularity workhorse

EEPROM erases and writes at byte or page granularity without a block-erase step, which makes its firmware model trivial: read, modify, write, done. Densities run from a few hundred bytes to 1 Mbit and beyond, with 1 to 4 million write cycles per cell. For configuration and calibration data - tens of bytes, updated occasionally - it remains the correct answer. Domestic supply is broad and dependable here; Puya (普冉) and BoyaMicro (博雅) both ship EEPROM families alongside their NOR lines, which simplifies qualifying one vendor across both memory types.

NOR flash: density with housekeeping

NOR wins from roughly 512 Kbit upward, where EEPROM pricing turns vertical. The cost of that density is the erase-before-write rule: sectors of 4 KB must be erased as a block, writes may only clear bits, and the controller (or your firmware) must manage wear. Modern serial NOR parts integrate on-die ECC and page buffers that hide much of this, and parts like the P25Q and BY25FQ series add erase-suspend features so a logging write does not stall code execution on the same bus. The firmware pattern that makes NOR durable is journaling: append records across the sector, mark them invalid in place, erase only when the sector fills. That single pattern turns a 100,000-cycle endurance limit into effectively unlimited product life for most logging workloads.

FRAM: writes without wear anxiety

Ferroelectric memory writes at byte granularity like EEPROM but with 10^10 to 10^14 cycle endurance and symmetric, fast writes at near-zero write energy. For high-frequency data capture - energy meters logging every second, industrial counters, medical dosimeters - FRAM removes the endurance math entirely. The trade is price per bit and an upper density limit; it competes for the job EEPROM cannot survive, not for bulk storage.

Doing the endurance math honestly

Take the real write rate, not the average: a smart meter writing 64 bytes every 10 seconds to a 4 KB NOR sector, journaling until full, erases the sector once per (4096/64) x 10 seconds - about 7 days - giving roughly 52 erases per year against a 100,000-cycle rating: two thousand years of margin. The same write pattern aimed at a single EEPROM page with in-place updates instead burns 3.2 million cycles per year against a 1 million rating: failure inside year one. Same data, same product, opposite outcomes - the difference is purely the journaling pattern and the technology match.

A selection shortcut

Configuration and calibration under weekly updates: EEPROM, smallest package that fits. Logging above a few writes per minute or above 512 Kbit total: SPI NOR with journaling. Writes faster than once per second sustained over product life, or write-energy-constrained harvesting designs: FRAM. And whatever the choice, verify the datasheet write-cycle rating at the maximum operating temperature of your product, not at room - endurance specifications, like most semiconductor promises, assume a cooler world than the one the product ships into.