Arduino EEPROM Guide: Prevent Memory Wear & Save Data

Learn how to use Arduino's EEPROM for non-volatile storage without destroying your hardware. We cover the 100k write limit, the critical difference between write() and update(), and how to handle multi-byte data.

The Problem: The 100,000 Write Limit

When building an Arduino project, you often need to save settings—like a calibration offset, a user preference, or a device ID—that persist after the power is toggled. The built-in EEPROM (Electrically Erasable Programmable Read-Only Memory) is the standard tool for this, but it comes with a physical limitation: write endurance. Most AVR-based Arduinos, such as the Uno (ATmega328p), can only handle approximately 100,000 write/erase cycles per memory address before that cell fails.

If your code writes a sensor value to EEPROM every second inside a loop(), you will permanently damage that section of the chip in less than 28 hours. The goal is to treat EEPROM as a vault for configuration, not a scratchpad for telemetry.

How EEPROM Operates

EEPROM is separate from the Flash memory where your program resides. While reading a byte is nearly instantaneous (under 100 microseconds), writing is a blocking operation that takes roughly 3.4 milliseconds. During this write window, the processor is effectively paused.

Key Constraints

Byte-Addressable: You access data by a specific address (e.g., address 0 to 1023 on an Uno).
Blocking Writes: Frequent writes can jitter time-sensitive tasks like PWM signals or fast serial communication.
Limited Capacity: With only 1KB on common boards, it is unsuitable for logs or large datasets.

The "Update" Pattern: Reducing Wear

The most common mistake is using EEPROM.write() indiscriminately. This function forces a write cycle every time it is called, regardless of whether the value has actually changed. To solve this, use EEPROM.update().

The update() function reads the current value at the address first. If the new value matches the existing one, the function returns immediately without performing a write cycle. This simple check can extend the life of your hardware from hours to years if the stored configuration rarely changes.

Worked Example: Saving a User Threshold

In this example, we save a temperature threshold. We use EEPROM.update() to ensure we only consume a write cycle when the user actually changes the setting.

#include <EEPROM.h>\n\nconst int thresholdAddress = 0; // Memory location for our setting\nint currentThreshold = 25;     // Default value\n\nvoid setup() {\n  Serial.begin(9600);\n\n  // Read the saved threshold on startup\n  currentThreshold = EEPROM.read(thresholdAddress);\n  Serial.print("Loaded Threshold: ");\n  Serial.println(currentThreshold);\n}\n\nvoid saveNewThreshold(int newValue) {\n  // update() only writes if newValue != current value in EEPROM\n  EEPROM.update(thresholdAddress, newValue);\n  currentThreshold = newValue;\n  Serial.println("Threshold updated in non-volatile memory.");\n}\n\nvoid loop() {\n  // Example: simulate a user changing the threshold via Serial\n  if (Serial.available() > 0) {\n    int input = Serial.parseInt();\n    if (input > 0) {\n      saveNewThreshold(input);\n    }\n  }\n}\n

Implementation Details and Risks

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Action	Permission/Context	Expected Result	Risk
`EEPROM.read(addr)`	Any context	Returns byte (0-255)	None (non-destructive)
`EEPROM.update(addr, val)`	Main loop/Interrupts	Writes if value differs	Blocking (~3.4ms)
`EEPROM.write(addr, val)`	Main loop/Interrupts	Forces write cycle	Rapid wear of memory cell

Handling Larger Data Types

The read() and write() functions only handle single bytes (8 bits). If you need to store an integer (2 bytes) or a float (4 bytes), use EEPROM.put() and EEPROM.get(). These functions use the update() logic internally and automatically calculate how many bytes the data type requires.

Limitations and Verification

EEPROM is not a database. It is prone to corruption if power is lost exactly during a write operation. For mission-critical data, consider storing two copies of the configuration at different addresses and using a checksum to verify which one is valid.

How to Verify Persistence

Upload your sketch and send a new value via the Serial Monitor.
Unplug the USB cable or remove the battery to completely kill power.
Reconnect power and observe the Serial Monitor output. If the "Loaded Threshold" matches your last input, the non-volatile storage is functioning correctly.

Preventing EEPROM Wear: Managing Non-Volatile Storage in Arduino