BMW E81 FRM3 Dump

**LosG** · 30th August, 2018, 11:40 AM

Hello Guys,

I need a good eeprom image for my FRM3R E81 Basis 6135 9224588.
Only got a corrupted Dflash Image

**daniersms** · 30th August, 2018, 11:55 AM

Hi look here http://tlvps.tomvanleeuwen.nl/frm/

**LosG** · 30th August, 2018, 12:10 PM

I already tried this site, but it says "Corrupt D-Flash file detected! Results probably incorrect!"

**daniersms** · 30th August, 2018, 03:38 PM

Originally Posted by LosG

I already tried this site, but it says "Corrupt D-Flash file detected! Results probably incorrect!"

Yes mine said the same but I have used that EEE file and it worked perfect--Maybe you must just give it a go

**tomvleeuwen** · 30th August, 2018, 08:49 PM

I would not try this file, your HW-NR and VIN are both incorrect so there are probably many more problems with the file.

I never had any of those problems with Xprog. I have often seen people uploaded multiple files with the same VIN, where the first ones have these problems with unexpected commands and block types, while later they manage to read the D-flash correctly and have no issues anymore. My suspicion is that some of the eeprom readers are just not reliable. Or maybe you use some "BDM frame" and needle probes instead of proper soldering connections? Did you verify the D-flash after you read it?

I think you have 2 options:
1) Try reading the D-Flash again with Xprog with the cables soldered directly to the probe points until you can verify your read. Upload and test that file.
2) If you can reliably read and verify the D-flash and it still contains these errors, your only option is to burn a image from another car. I have one attached.

**lupu_sandu** · 30th August, 2018, 09:51 PM

tomvleeuwen itself is here,

. Dude to be honest i never see you nick so far.
Good job for dflash to eep project, and a big thumbs up for give this free to everyone.

**LosG** · 31st August, 2018, 01:59 PM

Originally Posted by tomvleeuwen

I would not try this file, your HW-NR and VIN are both incorrect so there are probably many more problems with the file.

I never had any of those problems with Xprog. I have often seen people uploaded multiple files with the same VIN, where the first ones have these problems with unexpected commands and block types, while later they manage to read the D-flash correctly and have no issues anymore. My suspicion is that some of the eeprom readers are just not reliable. Or maybe you use some "BDM frame" and needle probes instead of proper soldering connections? Did you verify the D-flash after you read it?

I think you have 2 options:
1) Try reading the D-Flash again with Xprog with the cables soldered directly to the probe points until you can verify your read. Upload and test that file.
2) If you can reliably read and verify the D-flash and it still contains these errors, your only option is to burn a image from another car. I have one attached.

Thank you very much for uploading this file. So this is the eepromfile from exactly the same frm3? I have the possibility to code the FRM over DCAN, but with the flashfile i uploaded, i got many errors: windows are not working properly, i get a light error in cockpit and so on...

Yesterday i broke up my xprog (5.55), it says device is silent and i tried everyhing, even reflashed the atmega with an USBasp... Seems like i have to buy a new xprog, because this FRM version is not even shown up in the bmw parts catalogue...

**tomvleeuwen** · 1st September, 2018, 07:29 PM

The file I uploaded is for the same FRM part number, but coded differently off coarse.

You should actually be able to fix most or all problems even with the corrupt image by just coding the unit via DCAN using WinKFP (read Vehicle Order from CAS since the FRM's Vehicle Order is corrupt) and then initialize the power windows, but you won't ever be able to upgrade using ISTA/P anymore since the part number is not recovered from your D-flash.

**LosG** · 1st September, 2018, 08:11 PM

Thats exactly the problem, I cannot reconstruct the FRM with NCS/WinKFP, because my Dflash image has too many mistakes...
Ordered a new Xprog today and properly connected the cables to the FRM contacts to flash your image. It should arrive until Friday.
I wont use ISTA ever again, because this Software killed my FRM...

**LosG** · 14th September, 2018, 08:33 PM

The Xprog arrived today. I installed the Software but when it says Configuring Hardware, i get an "communication error"... I tried several usb cables and my soldering is fine. what should i do?

**tomvleeuwen** · 15th September, 2018, 07:55 PM

Check if your USB to serial drivers are installed correctly?
I suppose it is a communication error between your PC and the X-PROG. I think I normally get a different error when I connect the wires wrong.

I still think that you should be able to make your car work again by just coding it using NCS Expert (WinKFP won't work indeed) and then use INPA or any other diagnostic tool to initialize the power windows.

**LosG** · 5th October, 2018, 07:07 PM

Still cant use my XPROG due to software problems... When the communication error happens, i hear the "USB disconnected" sound, so i think you are right with the drivers... can you send me your driver/software for 5.7.4?
coding is not possible, because my actual dump got too many errors.

**tomvleeuwen** · 5th October, 2018, 07:44 PM

You can try this one: http://www.digital-kaos.co.uk/forums...=1#post2955196
But if the USB to serial converter actually disconnects, it sounds like a power supply issue (broken cable or hardware). Keep device manager open to see if the serial port disappears.