[BimmerGT1]

HI all, I have a problem with this 525 2006, original PCM was water damage, bought used one, I need to know if it is possible to swap flash eeprom from damage to new used one, I like to know wich chips do I need to desolder.
Or what have to be done in order to fireup this engine. I have ICOM ISTAd 236 ISTA p 250.4, INPA with SPdaten 49.
I will submit a pic of DME.

Siemens VDO
7 559 178

DME MCV70

5WK98081

[Sir Pommes]

Originally Posted by BimmerGT1

I need to know if it is possible to swap flash eeprom from damage to new used one, I like to know wich chips do I need to desolder.

Hi,

there´s no need to swap the components and some components are not swappable with reasonable expense.
The best way to get your car running is to buy an xprog5 (china clone) and copy the data from mcu, flash and eeprom via BDM, provided that the ecu is not completly dead.

regards SP

[BimmerGT1]

Originally Posted by Sir Pommes

Hi,

there´s no need to swap the components and some components are not swappable with reasonable expense.
The best way to get your car running is to buy an xprog5 (china clone) and copy the data from mcu, flash and eeprom via BDM, provided that the ecu is not completly dead.

regards SP

Thank you for your response I do have xprog but dont know wich chip to read from.there is a AMD 29BDD160.

swap the flash and eprom will be best I think, dont know much on bmw, others are easy.

[Sir Pommes]

Hello,

- open Xprog software
- go to Device/MCU/Motorola MCU and select "Show connection diagram"
- connect the XPROG to your damaged ecu as shown in diagram and connect power supply to ecu
- read MCU, Config, Flash and EEprom and save each file
- connect the used ecu to Xprog
- write MCU, Config, Flash and EEprom
- now you have an 100% copy of your damaged ecu

Swapping the flash and eeprom may work on some ecus but sometimes you also need to copy the data from the mcu itself. A solder specialist can also swap the mcu, but its not easy. I always used the software solution.

regards Jan

[MR.BLUECOLLARMAN]

Sorry for bringing up an old thread, but I do micro soldering and I swapped my eeprom and flash and I get cranking but no spark on my e90 msv70. What's the MCU? Is that where the ISN is written in? What chip is that programmed into, I would like to swap it and then do a write up for anyone else looking for help.

[Sensible_]

Originally Posted by MR.BLUECOLLARMAN

Sorry for bringing up an old thread, but I do micro soldering and I swapped my eeprom and flash and I get cranking but no spark on my e90 msv70. What's the MCU? Is that where the ISN is written in? What chip is that programmed into, I would like to swap it and then do a write up for anyone else looking for help.

If you did a FULL backup over BDM and wrote this to new DME the ISN should be correct and car should fire.

Checkout this thread: http://www.e90post.com/forums/showthread.php?t=1035058

[rjahl]

Originally Posted by Sensible_

If you did a FULL backup over BDM and wrote this to new DME the ISN should be correct and car should fire.

Checkout this thread: http://www.e90post.com/forums/showthread.php?t=1035058

Ya, would have been easier to copy everything over to the new DME with a good BDM.

Try INPA to see what errors are stored.

[MR.BLUECOLLARMAN]

I'm having exhaust/intake camshaft synchronization errors. 2A9A & 2A9B

[rjahl]

Originally Posted by MR.BLUECOLLARMAN

I'm having exhaust/intake camshaft synchronization errors. 2A9A & 2A9B

Couple of thoughts for you;

The DME boots and reports errors, that's a good sign. I don't know enough about the program stored in the microprocessor/MCU to say all is ok. I would not assume the file versions are compatible. As an example your original DME could be running a 921 program and the doner could have been an 830, I don't know if the boot sectors are compatible between them. The good news is this part of the program is stored in the WinfKP, 0PA files and can be reflashed using the BMW tools. I would no do this until you have looked into other possible causes. I highly recommend using a BDM to backup any remaining data from the DME before taking any more action in that direction.

Other than "no spark", what made you think your original DME was faulty? Did you try to read the codes before pulling the DME?

These stored codes could have been brought over from your old DME and have nothing to do with your current situation. You could try clearing them, resetting the adaptions and checking the error codes again.

From this side of the keyboard, I think it's possible these codes are the original cause of your problems.

[MR.BLUECOLLARMAN]

Well my original DME is still functional and I put it back into the car and the only codes I get are the camshaft codes. I sent the car to a shop to check it out mechanically because I was thinking maybe it jumped out of time or maybe a tooth broke off and messed it up somehow but even then it would just run rough and not give me a no spark issue. Mechanic said it has to be a ECU issue because all my sensors are brand new. Crankshaft and camshaft sensors are good, changed solenoids, relays and fuses are good. One question he asked me though I couldn't figure out "Do the spark plugs have a fuse?"

[rjahl]

Originally Posted by MR.BLUECOLLARMAN

Well my original DME is still functional and I put it back into the car and the only codes I get are the camshaft codes. I sent the car to a shop to check it out mechanically because I was thinking maybe it jumped out of time or maybe a tooth broke off and messed it up somehow but even then it would just run rough and not give me a no spark issue. Mechanic said it has to be a ECU issue because all my sensors are brand new. Crankshaft and camshaft sensors are good, changed solenoids, relays and fuses are good. One question he asked me though I couldn't figure out "Do the spark plugs have a fuse?"

There are faults that cause the DME to prohibit the engine from running. I would think that bad signals from both camshafts might be one of those faults. I can't say if it's going to cut the ignition, fuel or both.

Are you reading the codes through INPA or some generic reader? Often INPA will report if the fault is still present and what type of action it's taking. Do you have a screen shot? Look at the fault history as well.

[MR.BLUECOLLARMAN]

I have ISTA as well as INPA. And I think you're correct. I'm working on it right now (just got off night shift and won't go to sleep till its fixed) It's cranking up to 113 rpms and then the ECU shuts it off. It's stopping the spark for some odd reason, it'll give a shudder as if it's about to start and then cranks

[MR.BLUECOLLARMAN]

By the way, how do I insert photos? Do I have to link it? No way to upload?

[MR.BLUECOLLARMAN]

The FRM codes are because my headlights aren't attached.

[stevethresh]

Did you find an answer?

[LBC28704]

I'm glad someone else revived this thread recently, because I was about to.

I am also getting persistent 2A9A & 2A9B.

I tested both CPS and I'm getting constant battery voltage @ X6224/1 or X6214/1 (Both Crank position sensors) with ignition on, where there should only be 5v, and should drop to zero when the sensor is activated.

The DME in the vehicle is MSV70, 7 553 166

I had another untested DME that I was pretty sure was bad but I put it in just to see what would happen.

This one is a MSV70, 7 567 178

My thoughts were that if this seemed promising, I would then take the time to try and clone/repair

With the untested DME installed I got the same battery voltage at X6224/1 or X6214/1, which lead me to assume this DME is bad, as well.

Crank/no start, no spark.

No other engine related codes from ISTA.

I am considering picking up a MSV70 7 561 684 DME today, to see if I can do anything with it.

I've found conflicting information that states the 7 xxx xxx number is the programming only, and that the hardware across MSV70 is the same, so that software programming/coding should be the only change?

[LBC28704]

Originally Posted by stevethresh

Did you find an answer?

Steve, I may be further along in the troubleshooting than you at this point. Are you just getting the CPS codes?

Let me know, I'd be glad to help if I can.

Originally Posted by MR.BLUECOLLARMAN

The FRM codes are because my headlights aren't attached.

I see more issues than just 2A9A & 2A9B, here..?