[Bl@nquito]

Originally Posted by Levanime

post picture of the unit itself where numbers are written,
you need to chose by part number

This is it!

I guess that the correct one is: FRM3 AHL 9249082 e87 e92 e93.zip

[Levanime]

here you go

https://dl.dropboxusercontent.com/u/...0e92%20e93.zip

[Bl@nquito]

Originally Posted by Levanime

here you go

https://dl.dropboxusercontent.com/u/...0e92%20e93.zip

Many thanks!! Guess was that, and it was.
It's better to use the file named "NEW" right?

I've been talking with the dealer and they told me that the eee that they used was from a X5...

So I guess that the problem came from there...

I will keep you updated!


They need to:
- Write eee on the EPROM
- Update VIN number
- Let the ISTA update the module? Or better to update it manually and then use the ISTA to reupdate it?

[Levanime]

Just get proper eeprom so frm is responsive

You will change win number with WinKFP flash (or ista/p but its more complicated way)

And then copy VO from Cas and then code it

5 minute job

[y3k10]

Can you please tell me which eee dump to use for FRM3R PL2 E87 E92 E93 XE SW: 132001 / HW: 07? Thank you

[Levanime]

without part number you can not get the right one

[Levanime]

Sensible_

cant send PM to you (your inbox is full)
I've got some more dumps and wanted to add to your collection

[y3k10]

Partno. is 6135 9240528 - 01

[Sensible_]

Originally Posted by Levanime

Sensible_

cant send PM to you (your inbox is full)
I've got some more dumps and wanted to add to your collection

Hi,

Sorry I've been away. Yes. I'll add them. Send me PM.

[Bl@nquito]

Originally Posted by Levanime

Just get proper eeprom so frm is responsive

You will change win number with WinKFP flash (or ista/p but its more complicated way)

And then copy VO from Cas and then code it

5 minute job

Guess what? After FRM came back, while updating the whole VO on the car, the CAS bricked...

Do you how to get it back with the ISTA?

[Levanime]

CAS Bricked?

what did you do exactly?
did you have charger connected? did you maintain at least 13v?

what you needed to do is:
1) Flash FRM with WinKFP
2) copy VO from CAS to FRM (just get in CAS and FA_WRITE on NFRM)
3) SG_CODIEREN only NFRM module

[Bl@nquito]

Originally Posted by Levanime

CAS Bricked?

what did you do exactly?
did you have charger connected? did you maintain at least 13v?

what you needed to do is:
1) Flash FRM with WinKFP
2) copy VO from CAS to FRM (just get in CAS and FA_WRITE on NFRM)
3) SG_CODIEREN only NFRM module

The dealer connected the FRM and with ISTA they were going to code
Ista started asking for some numbers and to do the basic coding and the programmed one, they put the number from the unit tree and then it bricked

I forwarded them your instructions but they ignore them completely...

Now it's connected with BMW Germany to fix it

[chris11]

hello

Anyone try with r270 ? i thinks the pinout is not the same

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

[alexstatie]

Could i please get the firmware for part number 9240530?

Thank you!

[Levanime]

Originally Posted by alexstatie

Could i please get the firmware for part number 9240530?

Thank you!

try this one

https://dl.dropboxusercontent.com/u/...40528_HW07.rar

[khanjar]

Hi guys,
i am trying to reed and eee from a good working FRM module of a Clubman R55 2010 and i am getting this error while reading.
anyone can help what should be the error?

[djollie]

hi

i need flash eeprom for this E90 FRM3

any help much appreciated

br.

DJ

[Yasser]

Originally Posted by Mik325tds

It also turned out that the Secure mode of Xprog is not needed. I later selected the normal MC9S12XE mode and it wrote to EEprom and Program Flash just fine. However, my Xprog did give me a lot of problems reading either one without mismatches in the verify stage. Don't know why. But restarting Laptop every now and then helped.

By the way, my FRM is using a MC9S12XEQ384 (Mask 3M25J).

I have exactly same MCU and having same problems... when i read it fails on verification... and if i read 2 or 3 times its reads different...

I tried to read at all ways...

How did you solve that?
Just restarting or did anything else?

Thanks!

[Mik325tds]

Originally Posted by Yasser

I have exactly same MCU and having same problems... when i read it fails on verification... and if i read 2 or 3 times its reads different...

I tried to read at all ways...

How did you solve that?
Just restarting or did anything else?

Thanks!

The trick is to always save the file you read and then compare to the file you wrote. Once you got a match you're good.
First just try to restart the xprog then Laptop.

[minim]

I was helping a friend out with replacing his high pressure pump on a E84 and he also replaced the battery at the same time. When applying power again the FRM module was not responsive inside ISTA-D and there is a light error and lots of errors in ista-d. When doing diagnostic somehow the port setting changed latency from 1 to 16ms (16 does not work and give a lot of interuptions on readings) but I got it changed back to 1ms once I noticed it. This helped for some other modules but the FRM module was not possible to connect to again. I started reading up on this and caught this thread quickly. Do you think that a NFS Emergency flash could solve this problem? If so how do I know what address the module has and what the ZB number is? I think the ZB number is 9230450 (see attachments) but the address I don't know how to find.

If there is no point in doing this we have to order either a new part or a Xprog to continue I guess so I would love some feedback on that. I got a 45min drive there so if it's no point trying emergency flashing I'd rather get that xprog ordered and try it next weekend. Bad thing tho is that it rains bad here and the window is down and not to be controlled when the FRM is not responsive so the car can't be used.

[Yasser]

Originally Posted by minim

I was helping a friend out with replacing his high pressure pump on a E84 and he also replaced the battery at the same time. When applying power again the FRM module was not responsive inside ISTA-D and there is a light error and lots of errors in ista-d. When doing diagnostic somehow the port setting changed latency from 1 to 16ms (16 does not work and give a lot of interuptions on readings) but I got it changed back to 1ms once I noticed it. This helped for some other modules but the FRM module was not possible to connect to again. I started reading up on this and caught this thread quickly. Do you think that a NFS Emergency flash could solve this problem? If so how do I know what address the module has and what the ZB number is? I think the ZB number is 9230450 (see attachments) but the address I don't know how to find.

If there is no point in doing this we have to order either a new part or a Xprog to continue I guess so I would love some feedback on that. I got a 45min drive there so if it's no point trying emergency flashing I'd rather get that xprog ordered and try it next weekend. Bad thing tho is that it rains bad here and the window is down and not to be controlled when the FRM is not responsive so the car can't be used.

I think you only have chance with xprog...

[Yasser]

Originally Posted by Mik325tds

The trick is to always save the file you read and then compare to the file you wrote. Once you got a match you're good.
First just try to restart the xprog then Laptop.

Ok.

I will try again...

But that day, all the times i tried to read, it reads always different... so don't know which ones is the "original"...

But i will try again...