Using Tool 32 to Power Frm Module Again

How to repair BMW FRM module – easy transmission

FRM module (BMW E90) was out of society when I hooked the positive concluding on the battery.

How it was (client told me):

" I come in the morning, I need to go to piece of work, kickoff the car, as usual the reddish car on the lift is lit, I think, well, the battery is almost out of society, simply no, it says that this is due to lighting, and the truth in the compulsory includes rear dimensions, depression beam, and low-cal stops when the restriction pedal is depressed, and the remaining lights are turned off. The first idea in my caput is "Well, at to the lowest degree information technology starts and goes!"

I call my friend, he says that a block of light has died, I start to check that it does non work yet, I refused the mirror bulldoze, and the front windows, the residuum seems to exist normal. After that no one knew how to solve it. "

I but used inpa-adapter as diagnostic interface G + Dcan

The description of it tin can be read in the internet. Afterwards that, I started looking for programs to work with this shoestring, how many times I did not try, just through DIS I could not even connect to the motorcar, but basically I practise not demand it, having sorted through a agglomeration of programs and various assemblies, I stopped on a gear up of BMW Standart Tools two.12, Rheingold, Ista-P, NCSExpert, BMW Coding Tool, draw the installation and where I did non get it, if anyone is interested from where I downloaded the write in the comments , I'll throw in a personal.

How to determine if FRM destroyed:

1. Forcibly lights the about and rear dimensions.
2. More than anything from the lighting does not work (plough signals, far, fog lights, interior lighting).
3. The front end drinking glass lifts practise not work (at the rear, the rear doors can be opened and airtight).
4. Mirror drives do not work (folding and steering).
5. I besides found a number of problems in other forums, but I did not take them, information technology'due south a problem with the fundamental lock (with the closure or does not work at all), and the problems with the power windows.
6. Nosotros connect the diagnostic plan and see if FRM is available for advice, in my case, not i program information technology was not visible.

When diagnosed via Rheingold in the block tree, the FRM was ruby-red and the reckoner functions could not be chosen up. and in the error tree, standard errors were displayed with this problem 00A3B4, 00A3C1, 00CDAB

at the same time in the INPA of the FRM block at that place is no tree at all, and the existing errors are assigned to the KOMBI block (this is the speedometer / tachometer / odometer combination block).

If the unit of measurement does not communicate, then it can but be restored by the programmer (in that location are many mentions that even so it was restored with diagnostic cords and diagnostic programs, but in that location was no documentary confirmation of this, besides as the promises of people to do this in the end concluded in failure).

From words to deportment.

In order to start to restore FRM, you must first eliminate the problem due to which he died, and it was a faulty battery, in the final postal service I wrote on which one I inverse it. Naturally, any normal person chooses the lesser of ii evils, so I tried diagnostic programs, merely there was no sense at all, I found a programmer for the firmware of the processors from the manufacturers of Motorolla from the familiar electrician, came to him, merely as for the evil X-Prog he had been non, it was under repair, just it was UPA-Usb v1.3, before that, a whole bag of various memory dumps was downloaded, but very petty information is actually needed for the firmware, which dump is suitable, because practically anyone will fit, and in my example it was a dump that supposedly did not desire to exist flooded from my block, but it turned out to be poured from FRM from BMW X5 E70, but it most likely was the version of Basis.

And and then the lodge of programming through UPA:

1. Solder the wires and insert a bit into the UPA.
2. They gave extra nutrient to the UPA. (Actress nutrition is ever necessary, otherwise the consequences could be very deplorable or as in my case, it but can not run FRM)
3. Nosotros launched the programme from UPA, chose our chip in it, counted the contents and saw if in that location was anything in it, in my case EEPROM was empty, I had null to lose, and and so I pressed to delete the division and marking the new partitioning, it is marked as follows EEPROM — 4kb (4096b), DFlash — 0kb (0b), PFlash — XXXkb (XXXb), UPA does not know how to piece of work with PFlash, and so I did not touch it at all.
four. We opened the EEPROM retentiveness dump file with the extension *.bin and wrote information technology through our programmer. (Honestly, I managed to write a dump through UPA times from 15, I did not sympathize what specific actions, because oftentimes afterwards pouring it dumping information technology again showed that it was empty)

HOORAY! — were my first impressions, and I immediately went to check on the car, what did it plow out, eventually connecting the unit and inserting the key into the ignition and turning it on, I had a scarlet typewriter on the elevator on the dashboard, merely at the aforementioned fourth dimension mistakes began to accrue lamps, adaptive low-cal, information technology became immediately articulate that o came to life, the rest I thought was a affair of technique and you just need to clean upward the errors, program the unit and register it in the car, but I was wrong …

The result of programming FRM through UPA-USB v1.3.

When the machine is turned on, nada is forcibly activated, when the lite is turned on, the front end left lamp does non work in the right, the eyes are shining, the nearer beats with a strobe, the fog lights on the flooring, the turn signals piece of work quickly, equally if the lamp has burnt out merely everything is shining, the light in the cabin has appeared, adaptive lite does not work, the window lifters are reversed (the left button lowers the right, and the right ane is left), folding the mirrors works together with the control is normal — this is the result of the fact that the dump in the block is not stitched from my machine. Through Rheingold, just one-half of the errors were reset, the main ones were this short circuit (hereinafter referred to equally "curt circuit"), the transport mode is activated and the software version does not correspond to the equipment of the FRM unit. Information technology was necessary to erase the fault, for this I needed
program Tool32 from the set of programs BMW Standart Tools ii.12

How did I reset the error in my FRM block?

Earlier resetting the fault, I opened NCS Skillful, read the data from the CAS block, then wrote down the FA and encoded the FRM block with this data, after which it was possible to reset the mistake.
one. First I downloaded the latest file for editing FRM (I downloaded the latest version of ISTA-P in the plan files, in the binder with my body — it's E89, copied all the files for programming into a separate folder on the desktop, specifically I needed the file FRM_70 .prg).
2. Opened Tool32, connected the laptop with a lanyard to the auto and turned on the ignition, opened the file ( FRM_70.prg ) which was already in a divide folder.
iii. In the Jobs column, which opened to the left, I selected status_lampen_kurzschluss_counter_maxx and at the top I started the button, the video shows that it is denoted by 1x> and if you do non take all values for 0 and then yous have a brusk-circuit in the block and here you lot specify the maximum values for each lamp.
four. I so selected the line status_lampen_kurzschluss_counter and clicked execute, and then saw the amount of faults that are stock-still in the block for each lamp.
5. Later that I opened the minimized table, as shown in the video, I selected LAMPNRTEXTE from the pull-down list, in this tabular array the addresses of the lamps I reset the faults were written, for this I looked at the status_lampen_kurzschluss_counter outcome and wrote out the addresses of the lamps with non-zero value from the table.
half-dozen. Now nosotros know which lamps we had, and to reset it nosotros demand to select the line _reset_kurzschluss_sperre, in the Arguments' column enter the lamp accost in the format 0xFF, where FF is the variable value for each lamp, then printing the button to execute 1x> so if you did everything correctly, a new window volition appear in which should be written JOB_STATUS OK, an example of such a window is on the video.
7. After that, we perform this procedure described in particular half dozen for each lamp, when all faults are reset, opening the lines from clauses 3 and four all values volition be null.

Later the performed operations, I again went through Rheingold and INPA and reset errors, later which they all disappeared, just there were new ones, while the light sensor did non work, and the machine swore at the faulty plow signals when they were turned on, as if the lamps burned out, but they worked, only very rapidly, apparently a block of light thought that in the turn signals at that place should take been lamps and non LEDs like mine.

While checking all the blocks through Rheingold there were no errors at all, he showed that all the blocks are green, which was very strange to me, later that I began to trust Rheingold program less.
Non understanding where this problem comes from, as well every bit a strong drawdown of a new battery, tk. I decided to test the program ISTA-P through my lanyard, she found all the blocks even wanted to brand a programme of work, it all took most i hr, merely I did not exercise anything since. The car wrote that the battery is discharged, immediately had to leave, drove away and recharged the battery a picayune, but decided that this was not plenty.

Upon arrival, put the machine off the bombardment and put it on the day for charging, for accuracy, the bombardment was charged well, put it into the auto hooked up the terminals and was very unpleasantly surprised, tk. all my tortures with encryption by resetting CZ and all the rest were in vain, FRM began to work as if I had only filled it with the same memory dump.
I had to become home far away, so I had to restore the lighting, in addition at that place was a heavy downpour, without information technology I could not become, it was good that I took a laptop and a cord with me, and within 30 minutes I once again deleted all the faults, coded the block and reset all errors, again everything began to work, and returned to the state in which it was earlier the terminal removal of the battery.
The conclusion was obvious, you need to fill in some other dump through the developer, because this is definitely not from my block, contacting an electrician, he was only returned Xprog-Box 5.55 from repair, at the forum BMWTools many thanks to the participant Strellson was downloaded a new memory dump from some other block, absolutely the aforementioned as I only with a slightly different role number.

Program firmware FRM via X-Prog Box 5.55
1. Solder the wires in the same places as with the UPA.
2. Connect additional ability to the X-Prog.
3. Select the scrap by pressing the "Device" button, in my instance it's MC9S12XEQ384, and select EEPROM without security.
4. After that, we press the "Erase" push, this is necessary to erase everything that is now written in the retention chip, and select the markup, the markup must be 16, in this case the EPROM size is 4096kb, and the DFlash size is 0kb.
5. Side by side, open the dump file and press the "Write" push, once more we select our markup, after which the dump will exist written.
6. We return to the selection of the fleck and select PFlash, and then we also open up PFlash from the dump and press the "Write" push button, the markup is chosen the same, it was recorded very long, merely in the end the success was waiting.
Note:
If during the programming through X-Prog you have errors during verification after writing or while reading, then you cannot write a dump, in order to clear the error data yous need to detect 2 files in the program folder (source.xml, configuratin.xml) and change their attributes, make them "read-merely", this issue was discussed in several forums, after irresolute the attributes practice non forget to restart the program.

Then followed the installation of FRM in his staff place to check how he volition deport now, the place of his installation if anyone does not know lay below
Afterward the ignition was turned on, the turn signals started working ordinarily and there were no errors, only there were a lot of other errors, the next one that I did was gone to NCS Proficient to download the configuration from the CAS block, I chose to program NFRM (in NCS, for some reason it is called so, why not I know), I start recorded FA, selecting the command "FA_WRITE", and then I selected the command "SG_CODIEREN", then the encoding was successful, then I went into Tool32, and to my surprise there was non ane brusk-excursion in the block, later that I went in Rheingold, later the examination and cleaning errors all fell into identify, all the functions of the work Ali, gained the whole world, including the adaptive light and calorie-free sensor, but got out fault on foot, had a burned out bulb 1 of the left human foot, it'southward already been a trifle. And so followed the stress test for FRM
whether I did the correct thing all right and did, I threw off the terminal with AKB waited and threw dorsum, and eureka, FRM live! And and so I realized that everything was done correctly, after that I went to buy 2 light bulbs and replaced in the left foot, after that all the mistakes I had disappeared; at present again the machine is clean without any errors.

Important!
The cost of this procedure from 70usd up to 200usd (or more than) the options to make it a few.
1. Make everything cute, normal and correct, for case every bit described past me.
2. Brand people who are profitable for you to come again, tell tales that they themselves are dying, etc.
If everything is articulate with the starting time variant, and so nosotros volition sort it out a little, kickoff if the dump is not from your block, so when the battery is removed, information technology dies (or returns to that state equally if a dump had merely been poured into it), and secondly, if all visible errors are not removed disable their display in the machine, then errors volition exist copied until the limit is reached, later which the unit will once more dice this announcement to comrades who say that they have it every month past itself. Think THEME NOTHING BREAKS, EVERYTHING IS YOUR REASON AND MORE THAN Only — THIS CURVES Hands.
Cheque on site the piece of work of the wizard, with it, drop the negative concluding, if FRM does not die, then coin can be paid for the piece of work done.

PS. You need to drop start of all "-" the negative terminal, otherwise kill yourself some kind of blocks in the car.

Accept a nice day! And buy BMW key programmer in our store.

Carscanners TEAM.

grahamtaidew1967.blogspot.com

Source: https://carscanners.net/repair-bmw-frm-module/

Share this post