Small memory packages can look almost identical while requiring different handling. A short marking, damaged label or an online photograph is not a reliable substitute for the full device specification. Identification should precede a read attempt.
Start with the device family
ST’s automotive EEPROM documentation distinguishes M24 devices using I²C, M95 devices using SPI and M93 devices using Microwire. Its guidance also discusses endurance and data retention. These names illustrate distinct interfaces; they do not establish the pinout, voltage or capacity of an unidentified chip. ST automotive EEPROM reference.
Questions worth asking the repair provider
- Has the exact device variant been identified?
- Does the proposed tool support its voltage and memory organisation?
- Can the read be repeated consistently and checked against the expected capacity?
- Is the original data preserved before any write operation?
- Could other circuitry interfere with an in-circuit read?
These questions help define the work; they are not instructions to attach a programmer to an installed vehicle module. Do not power a board simultaneously from a vehicle and an external programmer unless an explicit supported procedure requires it.
An apparently valid file may still be wrong
A file full of repeated values deserves investigation, but it is not by itself proof that the memory is blank or corrupt. Likewise, two matching reads only show that the same result was obtained; interpretation and module-specific validation still matter. Preserve the tool settings and history so a later assessment is possible.
There is no generic EEPROM edit that safely repairs every BCM, BSI or immobiliser fault. Retain the original module and explain all earlier work. Send AXION the module label and symptoms before arranging data-recovery assessment.
Reviewed September 2026. Use the complete manufacturer-specific fault description and vehicle repair information.