[dumitru.o]

Originally Posted by Mik325tds

Thanks levanime, the issue I have with the converter is that I can't get a good read of the D-Flash section with my xprog. It will always throw a verify error so I don't know when I get a good read. No two files that I read match. Writes are slower and seem to work though. Anyway, I got it working by updating my xprog to 5.55 which supports the 1M12S mask.

can you help me upgrade my xprog 5.5.1 to 5.5.5 ? i am having the same issue on 5.5.1

thanks

Originally Posted by charles.soori

possible to get eeprom file for this dump.

frm3r pl2
e81 e82 e88ahl
9251489

thanks

have you fixed this? can you post the EEE or D-flash of this module? thanks

[Mik325tds]

Originally Posted by dumitru.o

can you help me upgrade my xprog 5.5.1 to 5.5.5 ? i am having the same issue on 5.5.1

thanks

I used a TL866 programmer to reflash the xprog to 5.55. Do you have a second programmer? If so I can send you the necessary files. Shoot me a PM with your email address.

[dumitru.o]

I have a tl866

[Hotter]

Hi, I have an "Number of dead EEE sectors too high" error in information memory.
Also my seat belt extenders do not work, no sound, no movement, nothing. Could this be because of dying FRM? Everything else seems to be working.

I have "read_dead_eee_sections_lear" done in Tool32:

apiJob("FRM_70","read_dead_eee_sections_lear","","stat_dead_eee_sections")

Satz : 0
  OBJECT                          = frm_70
  SAETZE                          = 1
  JOBNAME                         = read_dead_eee_sections_lear
  VARIANTE                        = FRM_70
  JOBSTATUS                       = 
  UBATTCURRENT                    = -1
  UBATTHISTORY                    = -1
  IGNITIONCURRENT                 = -1
  IGNITIONHISTORY                 = -1
Satz : 1
  JOB_STATUS                      = OKAY
  STAT_DEAD_EEE_SECTIONS          = 25                00 19  ..

So it seems that I have 25dead sections and it should be between 0-19 so its above limit. Anyone had such or similar case?

[brettcp]

I updated my FRM on my 2012 E93 to ZB 9390487 (this is the latest ZB# according to the latest version of ISTA/P). Was the root cause of the FRM failure resolved in this version, or is my FRM still at risk of dying if I change the battery or attempt to code/reboot the FRM? I ask because the Carly app is giving me a warning that my FRM is at risk for failure and asks if I'm 100% sure I want to proceed with coding as there's a high chance it will fail. Thoughts?

[Hotter]

Originally Posted by brettcp

I updated my FRM on my 2012 E93 to ZB 9390487 (this is the latest ZB# according to the latest version of ISTA/P). Was the root cause of the FRM failure resolved in this version, or is my FRM still at risk of dying if I change the battery or attempt to code/reboot the FRM? I ask because the Carly app is giving me a warning that my FRM is at risk for failure and asks if I'm 100% sure I want to proceed with coding as there's a high chance it will fail. Thoughts?

Do you have a cable? could you open Tool32 then Open FRM70 and select read_dead_eee_sections_lear to see how many dead sectors you have?

[brettcp]

Originally Posted by Hotter

Do you have a cable? could you open Tool32 then Open FRM70 and select read_dead_eee_sections_lear to see how many dead sectors you have?

Here is the output:

apiJob("FRM_70","read_dead_eee_sections_lear","","")

Satz : 0
  OBJECT                          = frm_70
  SAETZE                          = 1
  JOBNAME                         = read_dead_eee_sections_lear
  VARIANTE                        = FRM_70
  JOBSTATUS                       = 
  UBATTCURRENT                    = -1
  UBATTHISTORY                    = -1
  IGNITIONCURRENT                 = -1
  IGNITIONHISTORY                 = -1
Satz : 1
  JOB_STATUS                      = OKAY
  STAT_DEAD_EEE_SECTIONS          = 25                00 19  ..                    
  _TEL_ANTWORT                    = 8 Bytes
    0000 : 84 F1 72 70 43 01 19 B4                            ?ñrpC..´

What do you think?

[Hotter]

Originally Posted by brettcp

Here is the output:

apiJob("FRM_70","read_dead_eee_sections_lear","","")

Satz : 0
  OBJECT                          = frm_70
  SAETZE                          = 1
  JOBNAME                         = read_dead_eee_sections_lear
  VARIANTE                        = FRM_70
  JOBSTATUS                       = 
  UBATTCURRENT                    = -1
  UBATTHISTORY                    = -1
  IGNITIONCURRENT                 = -1
  IGNITIONHISTORY                 = -1
Satz : 1
  JOB_STATUS                      = OKAY
  STAT_DEAD_EEE_SECTIONS          = 25                00 19  ..                    
  _TEL_ANTWORT                    = 8 Bytes
    0000 : 84 F1 72 70 43 01 19 B4                            ?ñrpC..´

What do you think?

Interesting, I have exactly the same - 25dead sections like you. I think value should be between 0-19. I dont know what number is critical and when our FRM will die, but 25 is already over the safe limit. So I think Carly is correct there is a risk that FRM wont boot. It would be good that someone else would read this value who has good FRM to confirm this.
My seat belt extenders also do not work on E92, I am thinking that this might be the cause, but not sure. Maybe someone else has more knowladge about these EEE sectors?

[Sensible_]

Read the data sheet. Everything regarding 'dropped' (dead) sectors is explained.

https://www.nxp.com/docs/en/application-note/AN3490.pdf

[Hotter]

Originally Posted by Sensible_

Read the data sheet. Everything regarding 'dropped' (dead) sectors is explained.

https://www.nxp.com/docs/en/application-note/AN3490.pdf

Well its still not clear what number is maximum before death of FRM it writes 24 or 28. Since I have 25 dead sectors does this mean FRM will die once I reach 28?
So this cant be the reason my both seat belt extenders do not work, correct?

[Sensible_]

Originally Posted by Hotter

Well its still not clear what number is maximum before death of FRM it writes 24 or 28. Since I have 25 dead sectors does this mean FRM will die once I reach 28?
So this cant be the reason my both seat belt extenders do not work, correct?

It's likely to be 24 but I don't know the partition configuration.

Anyway. Is that reading of '25' not the hexadecimal of 19?

I'd imagine you have 19 dropped sectors.

This will likely be your problem. Why not try writing your dflash eeprom and see what happens?

[Hotter]

Originally Posted by Sensible_

It's likely to be 24 but I don't know the partition configuration.

Anyway. Is that reading of '25' not the hexadecimal of 19?

I'd imagine you have 19 dropped sectors.

This will likely be your problem. Why not try writing your dflash eeprom and see what happens?

Reading of 25 is marked as integer so it should be decimal, range 0-19 should be also decimal.

result    : STAT_DEAD_EEE_SECTIONS
  type    : int
  comment : Anzahl von DEAD_EEE_SECTIONS

It writes in documentation that it generates error message once dead sector reaches 13 is it hex? it would make sense because 13h=19d which is in my range 0-19. So if 24h=36d is hex in documentation then FRM is still good to go?

I do not have xprog unit, but thinking to get one if its the reason my seat belt extenders do not work... I was doing quite some researching in this thread https://www.e90post.com/forums/showthread.php?t=1509109 not yet discovered the cause...

[Sensible_]

Having read your other thread I very much doubt the problem is related to the dropped sectors. But I guess the only way you'll know is if you either replace the FRM or fix the dying eeprom with xprog.

Have you 100% rules out mechanical problems?

[Levanime]

dead sectors would not cause that.
dead sectors are more of a storage units that are no more used when dead.

I would check coding, fuse, mechanical side.

[Hotter]

Originally Posted by Sensible_

Having read your other thread I very much doubt the problem is related to the dropped sectors. But I guess the only way you'll know is if you either replace the FRM or fix the dying eeprom with xprog.

Have you 100% rules out mechanical problems?

No, I did not rule out all mechanical problems completely. I did not want to take side panels apart until I will rule out software or FRM issues. Position sensors work and fuse sends power to belt extender controllers. So either both motors are dead or FRM cable is broken and does not sent a signal. Its strange that both motors would be dead...

[RaptoR228]

Hello,
i have an error when i try to write / read / erase or something else.

"Unknown MC9S12 device. Part ID: 0x0204C486"

I use the X-Prog V5.5.5
My port connection the xprog seems to be fine: Com7 (Xprog-Box)

You have some idea to fix it?

Thank you.

[tomvleeuwen]

Originally Posted by RaptoR228

Hello,
i have an error when i try to write / read / erase or something else.

"Unknown MC9S12 device. Part ID: 0x0204C486"

I use the X-Prog V5.5.5
My port connection the xprog seems to be fine: Com7 (Xprog-Box)

You have some idea to fix it?

Thank you.

X-Prog clone v5.5.5 can't read or write FRM3 reliably.
Downgrade to X-Prog v5.5.1 and use a dump from the Internet (v5.5.1 can't read D-flash) or buy a new Xprog v5.6 or newer. It's best to buy genuine off coarse. Genuine UPA-USB works flawlessly as well if you think X-Prog is too expensive.

[Najt]

hi. Friend of mine got FRM dead after reading errors with ISTA. Which dump file shall i use for him , if he has 2011 e92 LCI with adaptive lights (xenons)?

[dumitru.o]

Post a picture with the label

[Sensible_]

Originally Posted by Najt

hi. Friend of mine got FRM dead after reading errors with ISTA. Which dump file shall i use for him , if he has 2011 e92 LCI with adaptive lights (xenons)?

You don't need a dump. Just read the dflash and extract the eeprom.

[SLF80]

Such an amazing thread. Thank you all!

[Vincentnini2011]

Hi guys,
Just ordered a XProg 5.55 to restore FRM.
Have seen all your posts about how to do that and I should achieve that easily now.

1 questions remains : is it possible to restore frm to virgin ? No vin, no VO/fa nothing as if it was new ?

Thanks for your answers