An EPROM is a read-only memory whose pattern is written with a programming supply and then held without power. The ultraviolet parts have a quartz window in a ceramic package and can be erased and written again. The one-time-programmable parts use the same cell and the same pinout in a plastic package, with no window. Engine and transmission controllers of the 1980s and 1990s used both, usually as the program and calibration store beside an 8-bit or 16-bit processor. Later controllers moved that store into electrically erasable flash, which has its own section, and then into the microcontroller. Serial EEPROM, the small 93C, 24C and 95-series devices used for immobiliser data and learnt values, is a different memory and is not catalogued here.
A ceramic window, or a plastic chip whose marking follows the JEDEC 27C numbering, is what this section describes. A house marking with no density code can be a mask ROM or a custom one-time part. Those devices do not join this catalogue just because the controller is old. The densities, packages and manufacturer codes are on the JEDEC EPROM densities and packages page. Controllers whose socket or emulator support is published against a particular device are on EPROMs named on engine controllers.
What the marking is saying
STMicroelectronics' February 2002 EPROM cross-reference, order code CREPROM/0202, is the clearest public key to the M27 numbering. The supply letter C is a 5 V part. The letter W, on the M27W family, is 2.7 V to 3.6 V. The temperature digit 1 is 0 °C to 70 °C, 6 is −40 °C to 85 °C, and 3 is −40 °C to 125 °C. The last of those is the range an under-bonnet controller needs. Package letters in the same guide include B for plastic DIP, F for windowed ceramic DIP, C for PLCC at 5 V, and N for TSOP. The density field is the part that decides the file size: 256 is 256 Kbit organised as bytes, 512 is 512 Kbit as bytes, 1001 is 1 Mbit as bytes, 1024 is 1 Mbit as 16-bit words, 4001 is 4 Mbit as bytes, 400 is 4 Mbit selectable as bytes or words, and 160 is 16 Mbit selectable as bytes or words. The full table is on the densities page.
The same devices were second-sourced. The ST guide maps Macronix MX27C1000 and MX27C1000A onto M27C1001, MX27C2000 onto M27C2001, MX27C4000 onto M27C4001, and the word-wide MX27C1024, MX27C2048, MX27C4096 and MX27C4100 onto the matching ST word-wide parts. An SST cross-reference lists AM27C256, M27256 and AT27C256 against its 256 Kbit pin-compatible flash, and AM27C512, M27512, AT27C512 and the Winbond W27E512 against the 512 Kbit part. A prefix from AMD, Atmel, Hitachi, Intel, Macronix, National, ST, Texas Instruments or Winbond does not by itself prove the pins match. The datasheet of the marked device does.
Read voltage and programming voltage
The CMOS generation reads from a single 5 V supply. ST's datasheets for the M27C256B, the M27C512, the M27C1001 and the M27C4001 each specify a programming voltage of 12.75 V ± 0.25 V. That is the voltage on the programming pin while the part is being written in a programmer. It is not the voltage the controller puts on the board in normal running.
Earlier NMOS EPROMs used higher programming voltages. Performance Vehicle Engineering's programmer coverage list still carries separate algorithms named 2716 at 12.7 V, 21 V and 25 V, and the same three voltages for the 2732, with 21 V algorithms for the 2764 and 27128. Those names are a programmer vendor's list of algorithms, not a statement of which controller was built with which voltage. The datasheet of the chip in the socket is the source for the programming supply. A 25 V algorithm applied to a 12.75 V CMOS part, or the other way round, is how these devices are destroyed.
Where this sits beside the processor
On these controllers the EPROM is an external memory. The processor fetches instructions and calibration from it over a parallel address and data bus. A socket is what an emulator sits in. The OLS300 page describes EVC's emulator, including the DIP and PLCC adapters for these outlines. Moates' Ostrich 2.0 page and CobraRTP's MotronicRT page are the two published lists of which JEDEC outlines those emulators present. Both are vendor support lists. They are cited on the controller page as such.
The processor families that replaced this arrangement, with flash inside the microcontroller, are on the ECU microcontrollers page. The external flash that sits between the EPROM era and that internal flash is on automotive external flash.
Real-time ROM emulation
A ROM emulator presents a substitute memory image to a compatible controller, so supported software can change calibration data while the engine runs. It is different from a programmer, which writes an image into a memory device. Live changes still need an appropriate definition for the exact software and measured feedback; the emulator itself does not identify maps or prove that a change is safe.
Match the emulator and adapter to the actual device's organisation, pinout, supply and access timing, as well as the ECU and software. For example, Moates specifies its Ostrich 2.0 for certain 8-bit devices and configurations, not all ROMs. Bank selection and address placement also matter. A matching package alone is not proof of compatibility.
Keep a verified original image, follow the specific hardware instructions with power removed for installation, and verify the uploaded image before testing. After calibration, save the final image and use the supported programmer and verification procedure if a permanent device is required. Some ECU software checks its stored image and may react to changes made while running; identify the particular system's behaviour before testing. An emulator need not remain fitted as the final storage device. Moates' emulator test guidance gives one example of upload and read-back verification.
Ford J3 port example
Not every real-time emulator connects in place of a socketed EPROM. Moates describes its QuarterHorse as a module for a compatible Ford EEC controller’s J3 port, providing emulation and datalogging when the required software support is available. Its product documentation explicitly distinguishes hardware compatibility from controller-specific software support; the port alone does not establish that a particular strategy has a usable definition or logger.
Identify the ECU, strategy and supported software before selecting hardware, and follow the device instructions for installation and recovery. The vendor’s Ford tuning overview describes different devices for emulation and module programming; a programmer that writes a module is not automatically a real-time logger. Historical pricing, availability and compatibility claims need current confirmation. For diagnostic self-test on one specific Ford system, see Ford EEC-IV.
GM MEMCAL example
Some GM controllers use a removable MEMCAL assembly rather than a bare, interchangeable calibration chip. Moates describes its G1 adapter as retaining the original assembly's resistor networks while providing a separate programmable memory device; it also notes that some MEMCALs include knock-related circuitry. Replacing only the code does not make the other hardware or its calibration universally interchangeable. Confirm the correct MEMCAL for the engine and controller using the applicable service information.
As a specific historical example, Moates identifies the 1986–89 TPI 1227165 family as a MEMCAL application with a 27C128 EPROM, and says the diagnostic data rate and software definition depend on the code mask. Identify the ECM number, installed calibration and software definition before choosing an adapter, reader or emulator. The diagnostic connector alone does not establish whether the memory can be reflashed through it. Keep and verify the original image and hardware, and follow the relevant tool's installation and read-back procedure.