EDC16CP35 Clone

[amar28]

Hi

I have a water damaged ecu from BMW X5 EDC16CP35, cannot BDM read it, has ext eep 95320

Just wanted to know if moving the eeprom data onto a new ecu would allow the car to start, does the ext eeprom contain the VIN, ISN etc or is the data in the micro MPC564

New ecu data attached if anyone can identify the location of the isn data, this will give me an idea as to if the micro needs moving over or just the ext eeprom or maybe just write cas isn and cks for the data

Thanks

[figani]

move EE...
maybe, but I forget it...
you need dme/cas syncro...
but even a cloned launch x431 can do this synchro under ecu options you will find it...

and no, vin is also in flash...
but you can also solder from ori to donor, no big thing...

[Stelaras26]

move EE...
maybe, but I forget it...
you need dme/cas syncro...
but even a cloned launch x431 can do this synchro under ecu options you will find it...

and no, vin is also in flash...
but you can also solder from ori to donor, no big thing...

But mpc564 is not possible to desolder and resolder ,is not like the others,right?

[amar28]

But mpc564 is not possible to desolder and resolder ,is not like the others,right?

need special tool to desolder MPC because you cant see the pins

the ISN for this ecu in in the eeprom or the flash? I seem to see short vin in the EE

[figani]

But mpc564 is not possible to desolder and resolder ,is not like the others,right?

Yes, it's possible but if donor ecu same...
Not necessary...

[Stelaras26]

is should be 9E DF

[amar28]

For anyone reading in future, ISN is EDC16CP35 is stored in Ext EEP, Repeated 3 times throughout the dump, Lines 40, Line 80, Line 0C0 - Bytes 02 and 03, 4 Digit ISN as is old ECU and doesnt use the new style 32 bytes, Solved and thread can be closed. Thanks to all who responded