The devices on this page are the ones a tool maker or an adapter author has named against a controller. A support list is evidence that the vendor's hardware presents that memory outline, and that the vendor believes the listed controllers use it. It is not a Bosch, Marelli or Delphi bill of materials, and it does not mean every hardware revision of a family is the same. Where a controller of this era has a mask ROM or a house-marked one-time part, it will not appear here. The densities and pinouts themselves are on JEDEC EPROM densities and packages.
Outlines the emulators present
Moates' Ostrich 2.0 page lists the 8-bit targets the emulator can stand in for. The 28-pin cable covers the 27C128, 27C256 and 27C512, and, with the SocketBooster, the 27C32 and 27C64. Moates names the 27C32 against throttle-body-injection General Motors controllers and older Bosch Motronic. The 32-pin cable is the 27C010 and the 29F040. The 29F040 is flash in an EPROM outline, covered under EPROM-pinout flash. The same page is explicit that the Ostrich does not emulate 16-bit memories such as the 28F series.
CobraRTP's MotronicRT page states support for 27C128, 27C256, 27C512 and 28F512, and for the 87C257 through an adapter, in DIP-28 and DIP-32. The controllers it then names are the cars it says use those outlines, from about 1984 to 1997. The families in that list are Audi and Volkswagen Bosch Motronic including M2.3.2 and Digifant, BMW Bosch DME and Siemens MS40.0 and MS40.1, Fiat, General Motors, Ford controllers with a 28-pin memory, Mitsubishi DSM and Lancer Evolution I to III, Porsche Motronic and LH-Jetronic, Nissan and Infiniti, and Magneti Marelli. Two of those Marelli lines are specific: IAW P8 is given as 27C128 to 27C256, and IAW 1AP as a 28F512 in a DIP package. CobraRTP also says a 16-bit Nissan controller that uses two chips needs two emulators. That is a statement about boards with a pair of byte-wide devices, which matches the word-wide alternative on the densities page.
EVC's own EPROM table is organised by density and pin count rather than by car. It is the source for the 87C257 at 256 Kbit in 28 pins, the 87C510 at 512 Kbit in 28 pins, and the 87C110 and 87C210 at 1 Mbit and 2 Mbit in 32 pins. Those 87C numbers are one-time or custom parts that share a density with a JEDEC device and do not always share its pinout.
The 87C510 on BMW Motronic motorcycles
One of those custom parts is documented beyond the density table. The adapter project published as y23tanaka/87c510to27C512 says Motronic 2.4 from 1997 to 2001 uses a Texas Instruments 87C510, that blank devices are not sold as a normal catalogue part, and that the author's R1100S and the earlier R1150 years are in that group. The adapter maps that chip to a 27C512. EVC's table agrees on the density and the 28-pin outline: 87C510 is the 512 Kbit, 28-pin entry beside the 27C512. The adapter is evidence for those motorcycles. It is not evidence that every Motronic 2.4 car uses an 87C510.
What a socket does and does not prove
A socket, or a footprint for one, means the board was built to take a removable memory of that outline. The label on the chip is the next check. A 27C256, a 27C512 and an 87C257 can all be 28-pin plastic packages, and the first two already differ on pin 1, as the densities page records from the ST datasheets. An emulator that presents 64 Kbytes into a board wired for 32 Kbytes will run only if the unused address line is held the way that board expects. Moates describes that failure as a controller that behaves as if the chip were missing or bad.
The programmer index for reading these devices out of circuit is EPROM and flash programmers. The generation that replaced the socket with a soldered 29F400 or 29F800 is five-volt NOR flash.