Complete Guide to EEPROM Interface Commands: Comparison and Implementation of I2C, SPI, and Microwire

This guide compares the communication methods and command sets of I²C, SPI, and Microwire EEPROM interfaces, while explaining key design considerations and best practices to assist in selecting the optimal EEPROM.

Introduction

EEPROM (Electrically Erasable Programmable Read-Only Memory) is a type of non-volatile memory that allows data to be electrically erased and rewritten; it is widely used in embedded systems and various electronic devices. Its ability to retain data even when power is removed makes it ideal for storing configuration settings and historical data. EEPROM communication primarily utilizes interfaces such as I²C, SPI, and Microwire, each with its own defined command set. This article provides a detailed explanation of the typical commands, implementation methods, and differences associated with these interfaces, offering guidelines to help design engineers select the optimal EEPROM and implement their designs effectively.

EEPROM Overview and Applications

EEPROM is a type of ROM that can be electrically erased and reprogrammed. While similar to flash memory, it performs write operations at the byte level, making it well-suited for applications requiring frequent updates of small amounts of data. Common applications include storing microcontroller initialization settings, sensor calibration data, and communication device logs. Additionally, EEPROMs typically offer relatively small capacities (ranging from a few kilobits to several megabits) and feature low power consumption and long operational lifespans.

Major Interface Types (I²C, SPI, Microwire)

The following is a comparison of representative interfaces.

Interface	Signal line	Communication speed	Main uses
I2C	2 lines (SCL/SDA)	up to 400 kbps	Low-capacity memory, sensor interfaces
SPI	4 lines (SCK, etc.)	10 Mbps+	High-speed communication, data logger
Microwire	3–4 lines (SK, etc.)	up to 1 Mbps	Legacy control equipment

I²C Interface

I²C is a simple synchronous communication method that enables the connection of multiple devices with minimal wiring. When interfacing with EEPROM, the processes of addressing and data read/write operations are distinct, making it particularly suitable for small-scale systems.

Communication Protocol Overview

Start bit
Slave address transmission + R/W bit
ACK/NACK response check
Memory address specification
Data transmission/reception
Stop bit
A single communication cycle is completed through this sequence.

Key Commands and Their Functions

Command type	Overview
Random read	Read one byte from an arbitrary address.
Sequential read	Read multiple bytes from consecutive addresses
Page write	Write multiple bytes per page

Implementation Examples and Considerations

Always account for the internal write time (tWR) after a write operation.
There are restrictions on write operations that cross page boundaries.
Initialization is required, as the device may not respond immediately after startup.

SPI Interface

SPI supports high-speed full-duplex communication and enables advanced operations such as status checking and write control. It is suitable for applications requiring high capacity or high-speed access.

Communication Protocol Overview

Communication begins when the CS signal goes LOW.
Command (8-bit)
Address (16–24 bits, depending on the device)
Data transmission/reception

Key Commands and Their Functions

Command name	Opcode	Description
WREN	0x06	Write enable
WRDI	0x04	Write disable
READ	0x03	Data read
WRITE	0x02	Data write
RDSR	0x05	Status register readout (WIP check, etc.)
WRSR	0x01	Write to status register

Implementation Examples and Considerations

Always execute WREN before writing.
After writing, confirm completion using RDSR (check the WIP bit).
Pay attention to page size limitations and CS signal control.

Microwire Interface

Microwire is a simple half-duplex communication protocol widely used in older control equipment. It allows for direct control of EEPROMs.

Communication Protocol Overview

Start bit
Opcode (2 bits) + Address
Data (target for read/write)
Communication starts/ends via the CS signal

Key Commands and Their Functions

Command name	Function overview
READ	Read 1 byte by specifying address
WRITE	Write 1 byte to a specified address (effective after WEN)
WEN	Enabling write operations
WDS	Disabling write operations
WRAL	Write the same data to all addresses
ERAL	Erase data from all addresses

Implementation Examples and Considerations

Software-based control via GPIO (bit-banging) is the common configuration.
Proper control of the SK toggle and management of the CS signal are critical.
Care must be taken regarding interrupts or power loss during write operations.

Command Comparison Table by Interface

Functional Items	I2C	SPI	Microwire
Reading	Random/sequential	READ	READ
Write	Page/byte write	WRITE (after WREN)	WRITE (after WEN)
Check status	none	RDSR	none
Write protection	none	WREN / WRDI	WEN / WDS
All write/erase	Not supported	Not supported	WRAL / ERAL

Implementation Best Practices

Key Points for Device Selection

When selecting an EEPROM, it is important to comprehensively evaluate multiple parameters, such as capacity, endurance, supply voltage, package type, and operating temperature range. Capacity, in particular, must be chosen appropriately based on the volume of data the system needs to retain and the types of data to be stored (e.g., configuration settings, logs, user information). For applications involving frequent data rewriting, the EEPROM’s write endurance (typically around 100,000 to 1 million cycles) may become a limiting factor; For applications that require significantly higher write endurance, alternative non-volatile memory technologies such as FeRAM may be worth considering. Furthermore, verifying that the supply voltage range and interface voltage levels are compatible with the microcontroller is essential. Regarding packaging, options such as SOP, TSSOP, and DFN should be selected based on the specific application and mounting environment. Industrial and automotive applications may require products capable of operating within a -40°C to 125°C range, so the selection process must also include a reliability assessment.

Handling Communication Errors

Communication with EEPROM can result in errors specific to interfaces like I²C or SPI; thus, designing robust error-handling logic in the software is critical. Stability can be improved by monitoring ACK/NACK responses for I²C or polling the WIP (Write In Progress) bit for SPI to determine the communication status, and by implementing retry logic as needed. In particular, failing to properly implement a wait process for write completion can lead to data corruption or system malfunctions. Additionally, to handle anomalies during communication, techniques such as bus reset for I²C and re-asserting the CS signal for SPI are effective. To ensure data integrity, implementing error-checking mechanisms using verification codes—such as checksums or CRC—is also recommended. These measures enable the early detection of communication errors or data-integrity issues caused by EEPROM aging, thereby ensuring robust system operation.

Considerations for Power Management and Data Retention

Safe EEPROM operation requires careful consideration of power management and data integrity. Power loss during a write operation, in particular, can lead to data corruption or inconsistencies in the EEPROM’s contents. To mitigate this risk, effective strategies include employing a power monitoring IC to detect voltage drops during writes or designing a power hold-up circuit using large-capacity capacitors. Managing write endurance is another critical design factor. For applications involving frequent rewrites, lifespan can be extended by implementing techniques such as ring buffer structures or address rotation to avoid concentrating writes on a single address. Additionally, implementing control logic in software to limit the frequency of data rewrites—such as restricting the number of write operations within a specific timeframe—helps ensure EEPROM reliability and the long-term stable operation of the entire product.

Summary

Each EEPROM interface offers distinct characteristics and advantages: I²C excels in wiring efficiency and scalability; SPI offers high speed and flexibility; and Microwire is well-suited for legacy equipment. By selecting the appropriate interface and EEPROM product for your design goals and implementing robust control measures, you can build embedded systems that deliver improved reliability and durability.