[Virtual Factoid]

Originally Posted by egaille

Hi,
I am new to the forum. I'm french. My car is a 2011 BMW 335d E92 with Xenon, adaptative headlights.

Fisrt of all, thank you very much for all the information posted here. It has been of great help to understand the BMW architecture. And thank you for the help you could bring to me...

I hope this is the right place to post my problem :

Since a few weeks,
- my windows started to malfunction : When i close my windows (driver or passenger) up to middle, i can't get them down. I need to go all way up to be able to open them again.
- Same behavior if i open the windows to the middle : i can't get them up until they are all way down...
BUT all other functions seem to work fine...
I tried every reset method i could find for my windows, but none worked or even happened to do something (press button and wait 20s, or 2x up / 2x down, etc).

I'm guessing the FRM3 module is the problem. Do you confirm?

Would a WinKFP reprogramming (with VIN) + FA writing to the FRM3 module, be sufficient to fix the problem?
Or do these symptoms mean the EEprom is corrupted and must be re-flashed ?

I downloaded the Gimmergeek standard tools suite, and the SP-Daten (E89) v66. I installed it following tutorials. I updated all tool's databases with the SP-Daten files. All seems ok.
I have a D-Can K USB Cable coming home soon.

Thank you all very much for your advices.

Step #1 would be to verify if you are able to communicate with your FRM3 module using the tools suite. Try the read functions and see if you are able to read anything from it. If this does not work (you will not be able to communicate at all if it is "bricked") then it is time for the surgery mentioned in this thread i.e. remove it from your car, solder the wires read from DFlash and all the good stuff.

Your situation sounds bad in the sense that it is an annoying limitation but it is still nowhere near as bad as a completely busted module with headlights permanently on high-beams, windows not working at all etc. Remember that it is possible to make your current situation far worse by doing something wrong with WinKfp. Not trying to discourage you - just doing a risk/benefit analysis.

[Mike Atkisson]

Has anyone run into an issue where the Xprog software will not run? I have tried the version on the CD as well as downloading from 2 different Mega sites. Everything else seems fine until I try to start the Xprog software. I get a small spinning circle for a few seconds then nothing happens.

[Ratnik]

Is it possible to recover this frm module?

[Virtual Factoid]

Originally Posted by Ratnik

Is it possible to recover this frm module?

The 14 pin IC in the photo on the left appears to be burnt. I couldn't find a schematic for the board online - that would have been helpful since this is all proprietary stuff with no visible markers/labels plus the entire thing is doused in a layer of conformal coating.

You could try desoldering the same one off of another sacrificial busted board and replace the burnt one with that but I am not sure it is worth all that effort. There could be further damage beyond that component.

[rkstar9]

has anyone ever figured out how to prevent the frm from burning out from over under voltage /short circuit or what ever?

Like placing a fuse in line or replacing oem fuse with a smaller fuse or some kind of voltage stabilizer?

Im troubleshooting a short in the car and would hate to go trough a dozen frms before i find where the short is

[Makoa6]

where can I buy xprog box and what version to use on my 2010 bmw 328i? FRM3R module faulty and I would like purchase one. searched online but couldnt really find one

[Monty2010]

This is from a 2010 328i (built in 11/2009 according to realOEM).
I made a cardinal sin last weekend when I replaced the valve cover gasket. I caused a tiniest spark and I think that might be caused the eprom corruption. Needlessly to say, I have no power window, no internal light, turning blinkers. It is also possible it's due to the battery that I replace many years ago started dying especially with the less frequent driving nowadays.

Anyhow, I have removed the FRM and it's attached. I want to try to repair it rather than replace. Can this particular one be repaired? I see a bunch of eBayer listed the latest part number, 61359390491. This one is an original piece and I don't want to ship it around the country and only to find it's not repairable.

Any comment would be appreciated.

[Monty2010]

I had a mobile mechanic fixed my FRM problem and now I have signals, windows, lights.

[cyangqd]

This is what I am experiencing.
Mine is 2010 BMW X5. My battery died first. We replaced the battery but found the turn left/right, window stopped working. I found this thread and it talks the same issue I am facing. Unfortunately, my BMW was 2010 and warranty was expired in 2020. Dealer said it was about $1000 to replace the FRM. I decided to try it myself.

I got the footwell from the car, purchased the xprog 6.1.2, installed the software on a Windows, soldered the wires to the FRM board.
I am trying to read MCU/MC9S12XEQ384_Dflash, EEE etc. But I got the error msg 'Can't get access to BDM'. I tried to read the FRM with/without 12v power, with/without BDM adaptor. But still getting the same msg 'Can't get access to BDM'.

Anyone had the same problem before? Any suggestion?

Thanks a lot!!

[cyangqd]

I think I figured out what was wrong. I didn't wire it correctly. I am not sure if the xprog version matters. I followed the wire instruction on youtube, but it turned out it is different than the xprog I use.
Xprog I use is 6.1.2 and the xprog on youtube is something like 5.5.

After rewiring, I was able to read the dflash and write back to EEE. Will try it in my car today.

[cyangqd]

It works.

[eku1s]

Hi Folks,

Sorry to hijack an old thread, but I wanted to make sure the right people got visibility of this.

I stupidly coded a new VO to my car (CAS and NFRM modules) yesterday with a low battery (yes.. I know!), however I did not modify any of the parameters on the FRM3, so it hasn't reset.

So far, the FRM3 is still working with no issues.

However, what I'm concerned about is when I change my battery, it'll brick the FRM3 as the module hasn't rebooted yet and might try to boot from corrupt firmware.

Is there anything I can do to try and prevent this from happening, before I disconnect the battery? Perhaps write a new VO to the module or do an SG_CODERIEN with the engine running to maintain power and ensure no corrupt data gets written?

Unfortunately, I don't have a power supply.

Is this something that's possible or am I out of luck?

Really don't want to have to get anyone to re-flash it during this pandemic situation as the company in the UK which does it is about 100 miles away from me, and travelling is something we're not allowed to do right now...

Any advice would be appreciated.

Thanks,

Luke

[sdbmwcoding]

Originally Posted by eku1s

Hi Folks,

Sorry to hijack an old thread, but I wanted to make sure the right people got visibility of this.

I stupidly coded a new VO to my car (CAS and NFRM modules) yesterday with a low battery (yes.. I know!), however I did not modify any of the parameters on the FRM3, so it hasn't reset.

So far, the FRM3 is still working with no issues.

However, what I'm concerned about is when I change my battery, it'll brick the FRM3 as the module hasn't rebooted yet and might try to boot from corrupt firmware.

Is there anything I can do to try and prevent this from happening, before I disconnect the battery? Perhaps write a new VO to the module or do an SG_CODERIEN with the engine running to maintain power and ensure no corrupt data gets written?

Unfortunately, I don't have a power supply.

Is this something that's possible or am I out of luck?

Really don't want to have to get anyone to re-flash it during this pandemic situation as the company in the UK which does it is about 100 miles away from me, and travelling is something we're not allowed to do right now...

Any advice would be appreciated.

Thanks,

Luke

Coding the frm reboots it, so if the eeprom data is corrupt then it'll brick itself. You can have power supply connected to car but that won't help you if the frm3 is faulty. Remember, not all frm3 modules are corrupt, yours could be completely fine. There's nothing preventatively you can do from the obd port as far as I know.

[Monty2010]

Where did you purchased xprog? Pls pm me as I may need to do this in the future as well. Thx.

Originally Posted by cyangqd

I think I figured out what was wrong. I didn't wire it correctly. I am not sure if the xprog version matters. I followed the wire instruction on youtube, but it turned out it is different than the xprog I use.
Xprog I use is 6.1.2 and the xprog on youtube is something like 5.5.

After rewiring, I was able to read the dflash and write back to EEE. Will try it in my car today.

[littlecreatures]

Anyone in Sydney recommended for repairing one of these?

[cawwt]

This is a GREAT thread. Thanks for all the information.

I wished I had found this earlier though.

TL;DR Try it with the China clone XProg 5.55 if you want to shorten your life by a few years!

If anyone in the San Francisco bay area have a good programmer, please contact me. I am willing to pay you to fix my FRM3. Getting a XProg 5.60 may work, but that will mean waiting for another few weeks to ship from China.

XProg 5.55 box, as others have said, fails on read verification very often. If I kept reading, in some cases I can get a successful read/verification. After collecting a few successful reads, I converted them into eee. Diff shows that they are all the same. The dflash_to_eee also reported correct VIN number, production date and serial number. So the EEE file may be valid.

The problem is that Xprog 5.55 is so unstable that I am not sure if the write is good or not. I was trying to be smart to do a write, then read it back until I get no verification error, then I diff the read file against the one I flashed. I found no diff. But unfortunately no success. So, at this point, I am not sure if my dflash read was a success or not.

[cawwt]

Originally Posted by cawwt

This is a GREAT thread. Thanks for all the information.

I wished I had found this earlier though.

TL;DR Try it with the China clone XProg 5.55 if you want to shorten your life by a few years!

If anyone in the San Francisco bay area have a good programmer, please contact me. I am willing to pay you to fix my FRM3. Getting a XProg 5.60 may work, but that will mean waiting for another few weeks to ship from China.

XProg 5.55 box, as others have said, fails on read verification very often. If I kept reading, in some cases I can get a successful read/verification. After collecting a few successful reads, I converted them into eee. Diff shows that they are all the same. The dflash_to_eee also reported correct VIN number, production date and serial number. So the EEE file may be valid.

The problem is that Xprog 5.55 is so unstable that I am not sure if the write is good or not. I was trying to be smart to do a write, then read it back until I get no verification error, then I diff the read file against the one I flashed. I found no diff. But unfortunately no success. So, at this point, I am not sure if my dflash read was a success or not.

Follow up on the story in case it will help someone else. I have almost given up and convined that this Xprog 5.55 box I had could not write correctly either.

I randomly downloaded 9230433 eee and flashed it. Holyshit!! The lights, windows, turning signals are all working!! However, the "Lighting System, Stop" error message came back though. Not sure if this is a coding issue. I am waiting for a coding cable to come and will code it and see if I can get rid of that error message. I am not going to risk flashing eee again as I am not sure if I was extremely lucky or that the Xprog 5.55 has no problem writing.

[cawwt]

Originally Posted by cawwt

Follow up on the story in case it will help someone else. I have almost given up and convined that this Xprog 5.55 box I had could not write correctly either.

I randomly downloaded 9230433 eee and flashed it. Holyshit!! The lights, windows, turning signals are all working!! However, the "Lighting System, Stop" error message came back though. Not sure if this is a coding issue. I am waiting for a coding cable to come and will code it and see if I can get rid of that error message. I am not going to risk flashing eee again as I am not sure if I was extremely lucky or that the Xprog 5.55 has no problem writing.

Another update: I bought a cable. Using NCS Expert I was able to write the VO back into the FRM. There is no more error now and the everything is working perfectly!

Before writing the VO there was an error message of $318 not compatible with this FA. So probably that was the reason of the error message on the car screen.

Interestedly there was no option to enter VIN in WinKFP. So I couldn't my FRM still has wrong VIN number.

[sdbmwcoding]

Originally Posted by cawwt

Another update: I bought a cable. Using NCS Expert I was able to write the VO back into the FRM. There is no more error now and the everything is working perfectly!

Before writing the VO there was an error message of $318 not compatible with this FA. So probably that was the reason of the error message on the car screen.

Interestedly there was no option to enter VIN in WinKFP. So I couldn't my FRM still has wrong VIN number.

Winkfp > configuration > check box to write vin in comfort mode

[cawwt]

Originally Posted by sd*********

Winkfp > configuration > check box to write vin in comfort mode

Thank you very much, Sir!!!

The check box doesn't say VIN. It says ULF (Not sure if I remember correctly). That's the trick to show the "Enter VIN" button.

I was able to update the FRM3 module with the right VIN. Apparently the update reset the VO on the FRM3. So I had to do the NCS trick again to copy it from CAS to FRM.

All good now!! Thanks a lot for all the forum/youtube friends for helping.

[ghost.87]

Hello!
Could anyone help me with a FRM PL2 FRM3R E89 E9x LED XE dump flash
S: 6135 9230447 - 01
AW: 9230440
SW: 122000
HW: 06

Thank you!

[Hotter]

Hi, anyone had an issue with XProg? I had error "unable to open C:/XPROG-BOX 5.60 English/HC11RD.BOO", so I have tried different software and one of the software recommended update XProg firmware.



After update, now I get "Device is silent"... Any ideas how to fix this error?



Or my XProg is done?..