|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
FRM3 Resurrection Thread
|
|
08-02-2019, 06:23 PM | #353 | |
Private
23
Rep 56
Posts |
Quote:
|
|
Appreciate
0
|
08-21-2019, 03:46 PM | #354 |
New Member
0
Rep 15
Posts |
frm3 update
|
Appreciate
0
|
09-02-2019, 07:24 PM | #355 |
New Member
0
Rep 6
Posts |
Thanks
My xprog is on it’s way, I should have it within the next days and a friend of mine has a Workshop with many dead FRMs in stock he gave me some to try. When repaired (if working) I’ll try to fit them into a car. As FRM vin change is easy (if I’ve a good memory) I’ll won’t try to restore it to virgin. |
Appreciate
0
|
09-16-2019, 03:55 PM | #356 | |
New Member
0
Rep 6
Posts |
Quote:
|
|
Appreciate
0
|
09-17-2019, 07:54 AM | #357 |
coding BMW.....
478
Rep 853
Posts |
I have a strange problem with one frm3. Someone sent it back because he had errors on the door lock. When i ve got the frm back and test it, the module it was actually dead. I tried to read the d flash but gave error that the chip is secured. I erased the chip and wrote only EEE as i had a backup of it. Everything went fine and the EEE was written correctly but the FRM is still dead, no communication to CAN!
Does anyone have any ideas? |
Appreciate
0
|
09-22-2019, 05:02 AM | #358 |
New Member
6
Rep 7
Posts |
You need a way to program the AVR in-system, for example using a AVR ASP. These programmers are available for a few bucks. Another Xprog will work as well.
Search for "xprog isp" on Google and you will find a tutorial. Find a file called x-prog551.rar for the correct firmware. |
Appreciate
0
|
10-05-2019, 02:27 AM | #359 | |
New Member
0
Rep 6
Posts |
Quote:
I've soldered the wires to the dead Xprog and i'm stuck here, i've an other working xprog but don't know how to process then.. |
|
Appreciate
0
|
10-06-2019, 01:32 AM | #360 |
New Member
0
Rep 6
Posts |
Hiii;
Finally (i think) managed to restore FRM3. here is my story and maybe help if i can : Bought a Xprog clone (bad one) and read Dflash. convert to EEE but always corrupted. Vin was showing WMWXXMyy0102Y7yy93 for example. I didn't notices this immediatly so i've flashed with this EEE. Too late to read DFLASH again as it was now only 0x0. So, i bought New Xprog clone, was not working for an hour then suddenly it started working and it always works now (chinese clones pleasures) I didn't have Dflash, it was 0x0 as i flushed it with the first Xprog.. So I found a EEE file online for my FRM part number. BUT, writting file i always had many verrify errors. >> I disabled verrify check and it worked. At the end, i Have : DFLASH : 0x0 which i think it the expected value EEPROM : made a new read and compared it with the donwloaded file : They are exactly the same. If you see anything i made wrong do not hesitate, i didn't test the FRM for the moment. EDIT : I tested 4 and they're fully working Last edited by Vincentnini2011; 10-24-2019 at 05:54 AM.. |
Appreciate
0
|
10-24-2019, 02:24 PM | #361 |
Major
263
Rep 1,173
Posts |
Has anyone outside of the US market got their FRM replaced due these issues? If so, did they (BMW) send out a different bulletin to each region?
I’m currently working with someone in Peru where the FRM failed. And, their dealer claims they’ve never heard of the extended warranty for the FRM. Not that their car isn’t eligible (which it meets all criteria), but they physically have not heard of that extended warranty. Thanks. |
Appreciate
0
|
11-03-2019, 03:47 PM | #362 |
New Member
3
Rep 20
Posts |
Seeking expert opinion on something I am planning to do:
So, I got the dreaded Death Warning from Carly a couple months ago about impending FRM3 malfunction which stopped me in my tracks and I left it at that. My FRM3 module works perfectly at the moment. I have disconnected the battery multiple times for other work and that did not affect my FRM3. I guess it would have gotten bricked by now if I had overridden the Carly warning and gone ahead with coding back then. Here's my plan: 1) Remove the module 2) Read D-Flash using Orange5. Note that my Orange5 is a clone but suffers from none of the instability issues that xprog clones have (yes I tried xprog 5.55 from China and gave up in frustration after endless "verify errors" while reading D-Flash. In fact, I couldn't get a single clean read). Another bonus is that EEE does not need to be completely busted for Orange5 to be able to read, unlike xprog. 3) Use tomvleeuwen's converter to create EEE binary from D-Flash 4) Write that back to EEE using Orange5 Note: I tried my Orange5 experiments on a known busted module that was not from my car. Do you think doing the above would let me start from a clean slate as far as Carly's Death Warning is concerned? Will restoring EEE from D-Flash re-start the counter for the firmware death-bug? Or would I just be back to square one with no improvement in my situation at all? I need to code/change a few minor settings but will not take the risk if bricking was a serious possibility. ------------------------------------ *Edit: I have come to realize upon further reading on this topic in other forums that there is no D-Flash partition in a good FRM3 module. So all I can do is save the current EEPROM content and write it back when it goes bad. My question then is can I do that preemptively? Would that achieve anything at all? Will that reset the "brick" counter from "imminent" to some later date in future? Last edited by Virtual Factoid; 11-03-2019 at 07:30 PM.. Reason: Update on assumptions made |
Appreciate
0
|
01-25-2020, 12:57 PM | #364 | |
Registered
0
Rep 1
Posts |
Unknown MC9S12 device
Quote:
Hello, I have the same problem with the error message "Unknown MC9S12 device" as described in #365. In very few cases, data was read, but then the error message came when verifying. I also use XProg Clone V5.55. By chance I found a solution to avoid this error: I wrongly selected the processor "9S12XD" (Subtype: Freescale 9S12XD / Device: MC9S12XD256_FLASH) and tried to read the Flash. Here I get also the error message "Unknown MC9S12X device". (It's ok because this is actually the wrong processor). If I now choose the right processor (Subtype: Freescale 9S12XE / Device: MC9S12XEQ384_D-FLASH) and then read the D-Flash, there is no error message and the data is reliably read out. Repeated reading also reliably produces the same results (some files compared with WinMerge). If someone also succeeds with this method, I would appreciate a short message here. Kind regards BMW_Detlef |
|
Appreciate
0
|
01-31-2020, 04:49 AM | #365 | |
Registered
0
Rep 1
Posts |
Unknown MC9S12 device
Quote:
It worked for me. Thank you, it helped me a lot. Robikson |
|
Appreciate
0
|
03-02-2020, 10:48 PM | #366 |
New Member
0
Rep 6
Posts |
Just reading through the pages of this thread and I see a lot of different programmers mentioned and there are some hit and misses. What is a reliable source and programmer to pick up. Lots of mention of the Xprog clones and UPA USB Programmer clones but is there a reliable vendor. Looks like my FRM3 just took a dump last night after my wife left the lights on and her coworker jump the car. She called me and said the head lights stay on but no turn signals and the windows don't work. So it looks like I need to pull it. Thanks in advanced.
Last edited by Malibu_rod; 03-03-2020 at 12:56 AM.. |
Appreciate
0
|
03-03-2020, 06:23 PM | #367 | |
Private
23
Rep 56
Posts |
Quote:
https://www.elrasoft.com/uusps.htm |
|
Appreciate
0
|
03-04-2020, 05:06 PM | #368 | |
New Member
0
Rep 6
Posts |
Quote:
Last edited by Malibu_rod; 03-04-2020 at 08:59 PM.. |
|
Appreciate
0
|
03-05-2020, 11:34 AM | #369 | |
Private
23
Rep 56
Posts |
Quote:
|
|
Appreciate
0
|
03-05-2020, 12:45 PM | #370 | |
New Member
0
Rep 6
Posts |
Quote:
|
|
Appreciate
0
|
05-08-2020, 04:51 PM | #371 |
Lieutenant Colonel
1190
Rep 1,544
Posts
Drives: '22 Tesla MY + '23 Tesla MY
Join Date: Jul 2010
Location: Land of high taxes and crappy healthcare
|
Anyone in thy GTA (Greater Toronto Area) do this? I just had a buddy's FRM3 crash on coding. If you can flash an eeprom, PM me
__________________
| '22 Tesla Model Y P - My daily | '23 Tesla Model Y LR - Wife's daily | '17 F15 35D - missed daily |
|
Appreciate
0
|
06-19-2020, 01:36 PM | #372 |
New Member
2
Rep 6
Posts |
Hi, I am hoping this is the right thread to post my issue here.
I recently tried to code out the headlight error on dash using bimmercode for my 2011 328i after installing new headlights and LEDs. But I got this error message: FRM3_89 errors memory contains critical error. I thought My footwell module was bad so I went to the BMW dealer for replacement given the extended warranty on footwell module. Dealer checked it and did not find anything wrong with the footwell module. Now bimmercode is unusable and I definitely dont know anything about coding. Any recommendations would be greatly appreciated. Thank you so much. Last edited by jimmyliupa; 06-19-2020 at 02:03 PM.. |
Appreciate
0
|
06-19-2020, 02:43 PM | #373 | |
Captain
182
Rep 780
Posts |
Quote:
|
|
Appreciate
0
|
06-24-2020, 01:02 PM | #374 |
Registered
0
Rep 1
Posts |
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. Last edited by egaille; 06-24-2020 at 01:16 PM.. |
Appreciate
0
|
Bookmarks |
|
|