|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
FRM3 Resurrection Thread
|
|
08-06-2017, 05:15 PM | #244 |
BimECU
191
Rep 760
Posts |
|
Appreciate
0
|
08-07-2017, 09:31 AM | #246 |
Private
15
Rep 60
Posts |
Thx, now that I noticed you supply them I realize my question was rude.
But I live in Quebec and am a amazon prime member, I was looking at this https://www.amazon.ca/Joykit-OBDII-D...ct_top?ie=UTF8. I might schedule remote coding with you tho, could you inform me on the cost to erase all errors and check for a short circuit? |
Appreciate
0
|
08-07-2017, 09:45 AM | #247 |
Private
15
Rep 60
Posts |
I have changed the FRM3 with an FRM2, the windows and lights were working again. But when I started the car 1 month later it was not working anymore, the right side mirror was off, but taped up, and some water did get in the door. My car was beside a house fire and the mirror melted as well as the right window regulator. A friend of mine changed the regulator and re-taped the wires. So I don't know if it's the wires or water that caused the FRM's to fail or something else completly, I did plug and unplug the battery many times so maybe that was it. Now I am scared to pop another FRM in.
Bimmergeek can you check that remotely? Thx The right headlight and fog light were also unplugged for may start-ups, could that have caused the FRM's to fail? |
Appreciate
0
|
08-07-2017, 07:45 PM | #248 | |
Private First Class
159
Rep 138
Posts |
Quote:
__________________
2016 435i xdrive Gran Coupé
2011 E82 1M Custom Frozen Brilliant White 2006 E60 M5 Alpine white SMG DELETE 6MT swap. Gone : 135i 2008 | Gone : 2008 535i Touring| |
|
Appreciate
0
|
08-15-2017, 06:57 PM | #250 |
Colonel
532
Rep 2,503
Posts |
|
Appreciate
0
|
08-15-2017, 07:47 PM | #251 |
Second Lieutenant
27
Rep 270
Posts |
|
Appreciate
0
|
08-21-2017, 07:02 AM | #252 |
First Lieutenant
342
Rep 388
Posts |
I connected ISTA+ to my X5d yesterday and fried the FRM module, now the windows are stuck down and all the other side effects of that module being offline are being seen. I found this thread about refreshing and recoding the module and am going to try to do that myself. I am in the process of buying an XPROG but noticed that there are some newer versions than 5.55. They have all the way up to 5.70 right now. Does anyone know what the best version is? Should I just get 5.55 because it's known to work? Towards the end of the thread there are a few people talking about downgrading to 5.10 to make it work. Should I try to find a later version?
I am also very interested in the Levanime has to recover without coding. If I could somehow repair the flash that would be ideal.. Any more information on that? Thanks for the help, Alex.
__________________
Current: 2023 G20 LCI M340i xDrive
History: 2005 E90 325i > 2008 E90 328xi > 2011 E90 LCI 335i xDrive > 2013 F30 328i xDrive > 2016 F30 LCI 340i xDrive > 2020 G20 M340i xDrive WE ARE! Last edited by azwillnj; 08-21-2017 at 07:18 AM.. |
Appreciate
0
|
08-21-2017, 01:19 PM | #253 |
Colonel
532
Rep 2,503
Posts |
This is fine:
http://m.obdexpress.co.uk/wholesale/...-x-prog-m.html In Dflash there is a virtual eeprom which you can extract and use to flash actual eeprom. Meaning everything will be just like before it was corrupted. I'm sure I saw a program around to that extracted it. If not it's not so difficult to do. I'll do a guide at some point, but very busy recently. |
Appreciate
0
|
08-28-2017, 03:30 AM | #254 |
New Member
6
Rep 7
Posts |
D-flash to eee
Hi all,
I could not find any software to convert the D-flash to eee, apart from one that requires a USB dongle from Russia. Therefore, I decided to dive into it myself. I created the following conversion tool: http://tlvps.tomvanleeuwen.nl/frm/ I have not tested it with an actual broken FRM yet, but the format seems quite straight-forward. If anything is wrong with it, I guess it will just return an old version of the eeprom image. At least the VIN and the "DEADBEEF" code is at the correct positions... I have tested it with a few images that I found online, one of which included the eee as reference and it was bitwise identical to my output. So feel free to test it and if you use it, please report back if it works. Remember that I store all uploaded images, if you don't like that just download the source and run the Python script yourself. Regards, Tom |
08-28-2017, 05:37 PM | #255 | |
Colonel
532
Rep 2,503
Posts |
Quote:
You clearly have some skill with this. I'll take a look asap. Unfortunately my time is now very limited playing with BMW ecu's |
|
Appreciate
0
|
08-29-2017, 03:21 PM | #257 |
BimECU
191
Rep 760
Posts |
|
Appreciate
0
|
09-02-2017, 02:01 AM | #258 |
New Member
6
Rep 7
Posts |
A small update on my dflash-to-eeprom converter. I got some converted files to compare with my program output. The results are all slightly different, but I can't figure out how the other conversion program comes to this result.
I used "R56 HIGH EKS 35 frm3r pl3 6135 3456987 01 23994322 sw156033 hw11 5324828r5.rar" as a reference, which includes both the EEE and the D-Flash dump. (Apparently, Orange5 can read the D-flash of a non-bricked FRM). As the Orange5 screenshot in that RAR files shows, there is a counter which indicates which parts of the D-flash are more recent (ECOUNT), so that the chip can find a starting point when emulating the EEPROM. Finding the starting point is the trickiest part of the conversion. The corrupt images don't have a valid ECOUNT, but I found 3 other methods to find the valid starting point, which all 3 indicate the same point on all images I tested. On the reference D-flash dump, my output image is hence identical to the included eee dump. However, as said the "other" conversion tools results in files that are slightly different. I can't really explain it. For some files, none of the starting points result in the same output, while for others a different starting point results in the image that is provided by the other conversion tool. Since even the reference that I used is different from the output of the other conversion tool, I don't think they are updating any checksums after the conversion either. They might be clearing some DTC's, but I suspect that they just don't really care about the starting point, resulting in an image where the quickly changing data is invalid (or old), but as it is quickly changing data, it will be updated anyway. So while I still haven't tested my output on an actual FRM, I am quite confident that the output is correct, even more correct than the other conversion tool. Last edited by tomvleeuwen; 09-02-2017 at 03:23 PM.. |
Appreciate
0
|
09-02-2017, 04:14 AM | #259 | |
Colonel
532
Rep 2,503
Posts |
Quote:
Last edited by Sensible_; 09-03-2017 at 01:19 PM.. |
|
Appreciate
0
|
09-06-2017, 06:58 AM | #260 |
New Member
0
Rep 5
Posts |
Have tested on a couple of e92 frms I have and both seem to have come back ok, a mini one I have however seems to still have issues, will look more into mini frm and report back, top job Tom.
|
Appreciate
0
|
11-09-2017, 01:26 AM | #262 | |
Registered
0
Rep 3
Posts |
Quote:
Your tool is very usefull! What does this warning message mean: "Found more than one set of new blocks" ?? Thanks is advance! Bala Hungary |
|
Appreciate
0
|
11-29-2017, 12:24 PM | #263 | |
New Member
6
Rep 7
Posts |
Quote:
The dflash consists of different blocks of data that "update" each other. Hence, the order of these blocks is important. Since I have to be able to handle corrupt images, I have 3 different ways of determining the first block, one of which is to check which blocks are already prepared but do not yet contain information ("new blocks"). If that method fails, my program switches to a different method. If that is the only warning you get, I'd say go ahead and try the resulting eeprom. Note that I deduced this all from looking at different dumps and corresponding eee images, so I might have made an incorrect assumption somewhere. However, most of the data is only present in once block so I guess even if I made a mistake somewhere it will still work in most of the cases. Regards, Tom |
|
Appreciate
0
|
01-03-2018, 07:39 AM | #264 |
Registered
1
Rep 2
Posts |
I don't understand the underlying memory concept of this chip.
So there are 3 different logical memory components: - The D-Flash - The EEPROM - The P-Flash As far as I understand, the EEPROM is simply emulated by a part of the d-flash? This means physically, that the d-flash and the eeprom are somewhat the same? However if we interpret this chunk of memory as d-flash (which for some reason is not faulty at all), we then can transform this data into eeprom-format, write it back to memory and everything is fixed. I don't understand the logic behind this at all. What is exactly faulty in a bricked frm? Last edited by denzelx; 01-03-2018 at 07:47 AM.. |
Appreciate
0
|
Bookmarks |
|
|