Serial EEPROM stores non-volatile information that a controller can update electrically. Depending on the design it may hold configuration, learned values, vehicle identity or instrument data; its contents and purpose must be established for the specific module. A separate EEPROM is not the same region as an ECU's external program flash or its processor's internal memory.
Common families
| Marking family | Interface | Examples |
|---|---|---|
| 24Cxx / M24 | I²C | 24C04: 4 Kbit (512 bytes); 24C32: 32 Kbit (4 KiB). See I²C EEPROMs in automotive modules. |
| 93Cxx / 93LCxx | Microwire | 93C56: 2 Kbit (256 bytes); 93C86: 16 Kbit (2 KiB). Read organisation can be fixed or selectable. See Microwire EEPROMs in instrument clusters. |
| 95xxx / M95 | SPI | 95080: 8 Kbit (1 KiB); 95320: 32 Kbit (4 KiB). See SPI EEPROMs in engine ECUs. |
| M35080 | SPI-compatible, special registers | 8 Kbit (1 KiB) with incremental registers in the original ST device; see M35080 in BMW instrument clusters. |
Capacities above describe the named families; exact suffixes, pinouts, operating voltages, write protection, and read organisation vary. Eight pins or a similar numerical marking alone do not establish the bus. Some controllers emulate EEPROM in processor or external flash; do not infer a discrete EEPROM from an ECU family name.
Before repair, document the complete module and chip markings and the read method; preserve and compare repeat reads. In-circuit reads can be affected by other powered components. File size alone cannot prove a complete or correct read, and a copied image can carry vehicle-specific data or calibration.
Device sources: ST M24C04, ST M24C32-A125, Microchip 93LC56, Microchip 93C86, ST M95080, ST M95320-A125, and ST M35080 preliminary datasheet.