This could be a really early engineering prototype ECU. Alternately, it could be a normal ECU which has had a tune applied which has modified the ROM to protect the tuner's calibrations - this is pretty common in the industry. They may have based their ROM on something they found elsewhere, which is why the part number doesn't match the ones you've seen.
This is what I am trying to figure out. I purchased this so that I could practice re-writing the ECU firmware via k-line without risk to the ECU in my car, but finding a non-standard ROM on it complicates things.
I currently suspect that the part is a development ECU based on both the ROM contents and the sealed PCB. If it is a dev. ecu, I want to figure out how to read the protected memory via BDM before I start reflashing it so that I don't lose out on potentially interesting information. I was originally hoping that I would not have to figure out how to build a BDM interface.
On the other hand, if the part has a different aftermarket ROM on it that re-writes itself to protect a tuner's calibration, then I am in a sticky situation. I do not want to undermine their effort by exposing sensitive information and have been trying to stay away from ECUs with aftermarket tunes. If this is an aftermarket tune, I hope someone familiar with such information can tell me so that I can figure out how to proceed without breaching their confidence.
could help identify this ECU.
Croft was the codename for the Federal Elise. ...
Do the Croft strings appear in the 2005 ROMs you have?
The two other T4 ROMs which I have looked through both have Croft in their software upload information strings. However neither of them return "DEVELOPMENT ONLY" when OBD PIDs request the CAL ID or vehicle make, model and year (they return something like "Lotus Elise MY05").
Similarly, the two other ROMs have ECU part numbers which look like:
and Cal IDs like:
Seeing an ECU part number which looks like it belongs with a K-series motor is strange to me. Perhaps the ECU was not a dev part, but rather was used in a different vehicle application?
In any case, when I power it in my car, it properly commands the gauge cluster. I did not try starting the engine, though.