External flash is the program and calibration memory soldered beside the processor once controllers stopped using an EPROM. It is electrically erased, so a calibration can be written in place, and it is NOR flash, so the processor can execute directly from it. The section splits by the device the board was designed around.
The five-volt boot-block parts, AMD's Am29F200, Am29F400, Am29F800 and Am29F160 and the Micron and ST M29F parts that follow them, are the memories on the C167 generation, including a large part of Bosch ME7 and EDC15. That catalogue is Five-volt NOR flash: Am29F and M29F. The burst-mode parts on the Motorola MPC555 to MPC565 boards, ST's M58BW, AMD's Am29BL802 and Am29BDD160, and Spansion's S29CD, are Burst flash on PowerPC controllers. The later three-volt page-mode families, the small flash devices that drop into an EPROM socket, and the serial NOR used in clusters and newer modules are on Three-volt and serial NOR flash and EPROM-pinout flash.
Earlier Intel 28F boot-block parts, including the 28F200 found in an MS41 example and the 28F800F3 listed for a BMW ME9, have their own Intel 28F flash reference. Check the exact suffix and programming requirements before choosing a device.
Further ECU examples and device details are in Am29BL162C ECU burst flash and 32 Mbit burst flash in engine controllers, including S29CD032G and M58BW32F.
For older byte-wide pairs, see Saab Trionic 5 28F512 and 28F010 flash. The Rover MEMS 2J conversion reference describes aftermarket 16-bit Atmel replacements.
The Intel Smart 5 B5 reference covers a 28F400B5 reported in a GM PCM and its programming-voltage distinction from the older 28F400BX.
The S29CL016J reference compares reported Marelli diesel ECU flash variants and their device identification.
How a part number is read
Density is the number after the family, in megabits, not megabytes. An Am29F400 is 4 Mbit, which is 512 Kbytes. An Am29F800 is 8 Mbit, which is 1 Mbyte. The file taken from the chip is that byte count when the device is the only program store. A board with two devices, which EVC records for the BMW ME9, is twice one device.
Boot location is the letter that follows. On the Am29F400B, AMD's datasheet uses T for a top boot block and B for a bottom boot block. The small sectors sit at the top of the address map or at the bottom. A top-boot image written into a bottom-boot device, or the reverse, is the same capacity and the wrong sector map. The NefMoto project notes for ME7 name the bottom-boot devices specifically: 29F800BB and 29F400BB.
The supply is the other hard boundary. The Am29F400B datasheet is a 5.0 V-only part. The Am29BL802C datasheet is 3.0 V to 3.6 V. The Am29BDD160 and the S29CD016J are 2.5 V to 2.75 V burst devices. They are not substitutes for each other because the command set looks similar. Micron's 2013 migration note TN-13-22 is the document that says the M29F can replace selected Am29F devices, and it lists the exceptions, including a write-protect pin the M29F does not have.
What this section does not cover
Flash inside the microcontroller is on the ECU microcontrollers page, with the MPC5xx and TriCore families. EVC's BDM100 description says the MPC555 to MPC565 already contain 448 Kbytes to 1 Mbyte of flash that an EPROM programmer cannot reach, which is why those controllers are read through the background-debug port even when an external burst flash is also fitted. The external device and the internal array are both present on that generation. A later TriCore controller is a different memory map again.
Serial EEPROM remains a separate small device for immobiliser and adaptation data. EVC's BDM table often names an ST95xxx EEPROM in the column beside the flash. That column is not repeated here as a flash part. NAND flash and eMMC, used in navigation and some later displays, are not the execute-in-place program store this section is describing.