[f00dstamps]

Originally Posted by Sensible_

You are correct. Just select a close match dump from my archive and write it to your bricked frm3. Once you have your dcan cable you can find a correct flash file in winkfp and flash the module with your own vin again. Then recode to default with ncsexpert.

Thank you for the response. I just discovered that I'm lacking in a different area while getting started on coding. I thought I had an old laptop that had Windows XP installed but it is Vista. Do you have recommendations on which OS is better for coding? XP vs 7? Xprog is compatible with both and I have seen the software needed for coding has different versions compatible with XP and 7.

Also, Can I program the FRM outside of the car by just having the Xprog power the microcontroller?

[808AWD325xi]

There is a SIB that has something to do with FRM_70 crashing during diagnoses and/or clearing fault memory. Perhaps someone with access to the SIB can share details?

[weehe126]

I believe I also bricked my FRM. I disconnected the battery to disconnect the DME connectors to remove the intake manifold, and once all back together I have the same problem as f00dstamps. My friend who does coding tried to connect to it to reset it, but was not able connect to it with any program he had. What would be your suggestion as next steps to take before buying a new FRM?

[Sensible_]

Originally Posted by weehe126

I believe I also bricked my FRM. I disconnected the battery to disconnect the DME connectors to remove the intake manifold, and once all back together I have the same problem as f00dstamps. My friend who does coding tried to connect to it to reset it, but was not able connect to it with any program he had. What would be your suggestion as next steps to take before buying a new FRM?

It's simple. Just write good eeprom to your FRM3. Communication via odb2 will then be restored 99.9% of time...

[weehe126]

Originally Posted by Sensible_

It's simple. Just write good eeprom to your FRM3. Communication via odb2 will then be restored 99.9% of time...

I'm not sure what that means, as my friend does all my coding. Which program would we use and how would I get a good eeprom. Following the first post?

[f00dstamps]

This thread has been so helpful. I was able to get XPROG installed and working. It took only a short time for me to get comfortable with the program because of my experience as a computer engineer. I flashed only the EEPROM from the FRM E90 XE LED dump and left my program memory alone. It returned functionality of some very important items I did not have before such as blinkers, high beams (I live in a rural area), gauge cluster lights, and window operation (although the window switches control the wrong window). I also got my gauge cluster lights, courtesy lights, and puddle lights working again.

I cannot wait for my DCAN cable to arrive so I can code the FRM to the specific features of my car.

Thank you Sensible.

Weehe126 - yes, read through this thread and you can get your eeprom going. you need to be comfortable with soldering. Order the XPROG 5.55 which comes with software. You'll also need a DCAN cable to code the specific features of your car after you've written an EEPROM dump from the FRM of another car. It sounds like your friend can help with the coding part.

[weehe126]

Ok this is all greek to me, but I am going to try to learn. So to write a good eeprom can I do it through the OBD2 port or do I have to take out the FRM and solder something? Do I need to remove it from the FRM board? Reading the first post and Sensible's comment I am not sure if I need to reset the eeprom first or just write over with one from the first post.

[weehe126]

So I need to buy this http://www.obd2tuning.com/xprog-box-...cu-p-2348.html to be able to do the steps in the first post?

[yuyuyuyu]

Originally Posted by weehe126

Ok this is all greek to me, but I am going to try to learn. So to write a good eeprom can I do it through the OBD2 port or do I have to take out the FRM and solder something? Do I need to remove it from the FRM board? Reading the first post and Sensible's comment I am not sure if I need to reset the eeprom first or just write over with one from the first post.

Need to remove the FRM, open it and solder your test points to the programmer. Clear the EEPROM since its most likely corrupted, rewrite it with one of the dumps provided in the OP.

Originally Posted by weehe126

So I need to buy this http://www.obd2tuning.com/xprog-box-...cu-p-2348.html to be able to do the steps in the first post?

Yes

[weehe126]

Ok thanks a lot for the clarification. Unless my buddy has one already I'll be buying a new FRM. Cant drive the car with the window stuck down so need a fix by this weekend. Maybe il see if i can fix it and sell it later on. thanks again

[f00dstamps]

weehee - PM me if you're interested in selling me your bricked FRM.

[Friendship]

Hi!

I have light problems after a change of the battery. I had the charger connected to the car during the change and this caused my FRM3 module to flip-out. I have been to a car-mechanic that looked with Autologic and the FRM module did not respond.

Therefor, I am looking for a solution instead of replacing this with a new or used FRM3 module and found this thread.

Right now I was wondering if I order a Eeprom programmer but do not know the MCU-type, What can I do if I don't know the type of MCU? Can I still program the unit?

I have opened the FRM3 unit but no information on the MCU. (attached picture)

I have a E91 -2010

Regards
Daniel

[Sensible_]

Originally Posted by Friendship

Hi!

I have light problems after a change of the battery. I had the charger connected to the car during the change and this caused my FRM3 module to flip-out. I have been to a car-mechanic that looked with Autologic and the FRM module did not respond.

Therefor, I am looking for a solution instead of replacing this with a new or used FRM3 module and found this thread.

Right now I was wondering if I order a Eeprom programmer but do not know the MCU-type, What can I do if I don't know the type of MCU? Can I still program the unit?

I have opened the FRM3 unit but no information on the MCU. (attached picture)

I have a E91 -2010

Regards
Daniel

The MCU will be a variant of the 9S12X finally...

It will be fine to erase eeprom then write a new one to the MCU. It's very simple. Just need XPROG or similar...

[Alex_WLY]

can anyone repair my frm3 maxbrose?I am from Romania, but I can send it anywhere.Thank you

[gimmethemuumuu]

My FRM3 module became nonfunctional and nonresponsive. I have since replaced it with a new one. I do have the original unit for sale if someone wants to try this repair.

PM me if you're interested

[Alex@Alpine]

Hello, I offer FRM3 repair/recovery, $150 includes priority 2 day shipping (in US) back to you. Usually 1-2 day turn around time. No soldering or removing of chip. You can checkout through our site or email if you have any questions. Alex@alpinemss.com. Forum vendor for the last 6 years.

http://alpinemss.com/product_p/FR.htm

[pepperwhiteknight]

I disconnected the battery and the DME to change the thermostat and when I put it back together the FRM was dead.
Thanks for all the information. It fixed my 2011 r56 mcs frm3. Before this whole ordeal of the junk BMW/MINI FRM dying the only software I used was playing with was Carly for iOS and Dashcommand.

While shopping for xprog boxes I was like where is the BKGD? BKGD is on the HC(S)12 BDM adapter in the attached photo.

Vdd(+5V) = Vcc
RESET = B5
BKGD = B3
GND = GND (do not use the GND that is B0)

I think since we are not using the XCLKS and EXTAL flashing works with or without the BDM adapter.

This video helped me install the xprog software and see how it works.
http://www.dailymotion.com/video/x27...-software_auto
I was not able to get this software to work with windows 7 64-bit. I was lucky enough to have an old HDD with windows 7 32-bit.
Before plugging in the xprog hardware go to system properties and change the device installation settings to never install driver software from windows update.

Once the software was setup I hooked up the frm to the xprog and tried to make a backup of the existing EPROM via the MCU/MPU -> Freescale 9S12XE -> MC9s12XEQ384_EEE profile. Error partition corrupted. Set the sector to 16. I also made a backup of the existing P-FLASH via the MCU/MPU -> Freescale 9S12XE -> MC9s12XEQ384_P-FLASH profile. I think I got errors the first few times I tried to do this but restarting the program resolved the error.
In the MCU/MPU -> Freescale 9S12XE -> MC9s12XEQ384_EEE profile: erase, blank, open good EEE dump, write, verify, close, new, read.
This took several tries because the read back was still showing as blank.
I removed the BDM adapter and went direct into the xprog box. I also closed the program and reopened it when it kept giving me errors. After I was able to get a good write to the FRM I installed it back into the car and it was working again with a couple of errors (xenon high beam failure and fog light failure).

In NCS expert I backed up the FRM, changed the VO and VIN, reset the FRM to factory and still had the high beam and fog errors. I proceeded to WINKFP to update the FRM and none of the ZB-numbers for my ECU worked. I updated WINKFP with BMW coding tool and the list of available ZB-numbers changed. After WINKFP was able to update the FRM I went back to NCS Expert and copied the VO from the CAS to the FRM and then set the FRM back to defaults. Everything was fixed. Fired up ISTA+ and cleared fault memory.
Afterwards I hooked the frm back to the xprog and made a backup of the EEE and pflash.



My FRM:
R56 HIGH EKS 35 frm3r pl3 6135 3456395 01 23994322 sw141030 hw07 5324828c5
mc9s12xeq384mag
3m25j
Internet file:
R56 HIGH EKS 35 frm3r pl3 6135 3456987 01 23994322 sw156033 hw11 5324828r5

According to realoem parts 61353456395 and 61353456987 are Bilaterally exchangeable.
http://www.realoem.com/bmw/enUS/part...&q=61353456395

[Sensible_]

Great! Glad this helped you! Hopefully this demonstrates to people it's possible to repair these modules with minimum cost.

[dumitru.o]

after erasing the PFlash i am getting the error the that chip is secured and i can not write back any of the 3 dumps. i tried with the secured profile but keeps saying that is bypassing the MCU security and does nothing. can anyone help with an idea on what to do?

thanks

[Sensible_]

Originally Posted by dumitru.o

after erasing the PFlash i am getting the error the that chip is secured and i can not write back any of the 3 dumps. i tried with the secured profile but keeps saying that is bypassing the MCU security and does nothing. can anyone help with an idea on what to do?

thanks

What programmer are you using?

[m5james]

Originally Posted by Alex@Alpine

Hello, I offer FRM3 repair/recovery, $150 includes priority 2 day shipping (in US) back to you. Usually 1-2 day turn around time. No soldering or removing of chip. You can checkout through our site or email if you have any questions. Alex@alpinemss.com. Forum vendor for the last 6 years.

http://alpinemss.com/product_p/FR.htm

Do you buy these for resale? I've got two spares given to me by a buddy who works at the dealership after having mine replaced under warranty. I was going to repair them thinking I can flip them to make a little money, but between the cost of repair and what they can be sold for, it's likely not worth my time but is moreso for someone like you who does this as a side business.

[dumitru.o]

Originally Posted by Sensible_

What programmer are you using?

xprog 5.55 china

thanks