RomRaider

Hi,

After a bricked ECU (when writing with MSS5x flasher), I need to ask you:

If an MSS52 ECU got another version than my file, can I just overwrite with the fullread, like I've always done on MS41, MS42 and MS43?

Anyone done it?

Last time it didn't work out very well, but I suspect that that was another problem..

Thanks!

Could works. Some works another dont.
So test. 99% sucess i got.
But iam not sure if i would write your file if you brick your last one... so better upload here so we can check the file.

I used ba114's file from the definitions thread. "Siemens_mss52_FullRead_7837965_WBSDE9349YBZ97143.bin"

And I modiefied the partial. I can pm the partial if interested, it is chipped/tuned from ecufiles.com

lol standard chiptuing files ... and you are not allowed to share them here.
So please dont do it. Also you can do better by your own .
Do not use such standard file service files.

Use ba114s Fullread and after you can read partial and tune by your own for real tuning.

What I can suggest you to recover your bricked mss52 is to reflash it to oem with an oem software such as winKFP. (it is included in the INPA EDIABAS suite)

It's also the software to use to update your DME version. I had a 0601 version and I did update it to 1701 with this software.

If you need the oem e39 datten files then do let me know.

If ecu is real bricked winkfp wouldn't do anything for you :/.

It’s true, but if he still able to connect with inpa, then he should be able to reflash to OE with WinKFP

Yes but that isn't what I would call bricked

True!

when your mss52 seems fully bricked... its possible to recover this by grounding two pins on the eproms. I documented this in the e39 m5 owners group fb page.

what you'll need to do is ground these pins and then turn on ignition. release the pins after a moment. it should stop the dme from booting bad software and getting stuck. it should allow you to flash again with winkfp or mssflasher

How to solve " trouble idling ecu " when MSSflasher cannot identiy DME after a 'bad flash' either from winkfp or otherwise.

This is for those who:
Cannot recover your dme via winkfp / mssflasher / or communicate through OBD / see temp gauge maxed out after flash even after ignition cycling

Cause:
It usually means one of the CPUs is stuck with
bad flash and doesn't respond after booting up
(most of the time voltage / bad file / cable latency setting)

How to fix:
You'll need to put it into bootmode -
both EEPROMS need pin 37 shorted to GND during powerup.

What pins are 37 ?
the eprom should be an AMD AM29F200B
Grounding both eproms at the same time to chassis ground is KEY.
See picture for pin 37. Using programming probes and clips is most ideal and can be done in car.

You'll want to short these pins to ground on start up which means you'll likely need a second hand to turn on ignition.

Hold these pins to ground for about 3-4 seconds.