Keeping frequently updated data through a power cut
FRAM is non-volatile memory that stores bits using the electrical polarization of a ferroelectric material. You may also see it called FeRAM or F-RAM. It offers addressed reads and writes associated with random-access memory, while retaining stored information without continuous power or a backup battery. That makes it a member of the NVRAM family.
Its strongest use case is small records that change repeatedly: a machine counter, accumulated operating hours, or the latest event in a log. Compared with EEPROM and Flash, FRAM can reduce the delay and endurance constraints involved in making these updates persistent.
What makes the information stay?
An applied electric field sets the material to one of two polarization states. The circuit interprets these states as binary 0 and 1. A remaining polarization persists after the field is removed. Traditional commercial FRAM commonly uses a thin film of lead zirconate titanate, or PZT.
The name can be misleading: FRAM does not store bits by magnetizing the material. MRAM uses magnetic properties; FRAM relies on electric polarization. Ordinary DRAM and SRAM lose their working data when their supply disappears.
In conventional capacitor-based FRAM, reading can disturb the cell's state. The memory circuitry senses the bit and automatically restores the original state. Software does not need to issue a separate write after every read. This restoration is distinct from the periodic refresh required by DRAM.
How the options behave in a controller
| Memory | After power loss | Updating data |
|---|---|---|
| FRAM | Stored data remains. | No prior block erase; suited to frequent updates. |
| SRAM / DRAM | Data is lost without backup. | Fast access for working memory. |
| EEPROM | Stored data remains. | Allow for internal programming time and finite rewrite endurance. |
| NOR / NAND Flash | Stored data remains. | Typically organized around block/sector erases and programming operations. |
Fast storage cells do not mean unlimited transfer speed. With an external device, the I²C, SPI or QSPI interface, command overhead and host processor determine how quickly a complete record reaches memory. Consider that distinction when comparing capacity and access speed.
A counter illustrates the workload
Suppose a PLC saves a production counter ten times per second. Continuous operation produces 315,360,000 updates per year. This calculation explains the attraction of high endurance; it does not predict the service life of the controller.
A concrete example is Infineon's FM25640B, whose datasheet specifies 1014 read/write cycles. Treat this as a specification for that device, not a universal FRAM rating. The memory's internal row organization and read-restoration behavior matter when assessing endurance and reliability; counting only software write commands can miss part of the workload.
Calibration values, accumulated totals and fault histories are other useful memory applications. An industrial IoT node can also keep a local record before forwarding it. Whether a particular PLC uses FRAM, and which variables survive a restart, depends on its hardware and configured retention behavior.
Read the specifications that match the job
Check density, supply voltage, interface, operating temperature, access endurance and data retention. Endurance describes repeated accesses; retention describes how long information remains stored under stated conditions. A high cycle rating does not establish the same retention period at every temperature. For power consumption, compare the energy needed to save a record as well as active and standby currents.
Large file storage calls for a different capacity and cost assessment. FRAM also serves a different purpose from read-mostly technologies such as ROM and EPROM. Select the exact part number and review its datasheet: a familiar package or similar pinout alone does not establish that an FRAM device can replace an EEPROM without hardware or software changes.
Technical references: TI — FRAM FAQs · Infineon — F-RAM · FM25640B datasheet · RAMXEED — Memory FAQ
