[maninblack]

Hi,

i had some trouble with E9x FRM3.

First i read dflash several times and got several results (some bits differed).
then i could not write partition table...
After some tries it worked... strange...

But now the dflash to eee tools says that the dflash is corrupt. 

With upa i can not write dflash - is this correct? Isn't dflash writeable?

Now, if i execute frm70.prg job "read_dead_eee_sections_lear" i get 3 dead section.

anyone has a idea on that?

thanks

[duckdonald]

once you read the D-Flash, you must get the EEprom.
then you don't have to write the D-Flash, .. but only the EEprom

[Alex_Tushino]

it's not difficult at all , online is possible.

[benzprod]

normmaly, when you make verification of you read, verification its ok.I make this with upa last week and dflash several time its same file in my FRM3

[user0086]

If you read a different file every time, it's no surprise that the tool also sees it as corrupt. You just don't have the equipment to reliably read and write the FRM3.

I experienced the same problems with clone Xprog 5.55 and clone UPA-USB. Also with clone Xprog 5.6 after a few years of usage. Xprog 5.51 works fine but can't read D-Flash. Genuine tools work perfectly off coarse, but you can't write to D-Flash if the partition table is set to EEE.

But, it seems that you have managed to fixed the partition table (otherwise you can't read dead sectors) and you have access to Tool32. I assume you also have NCS Expert installed. All you need to do is code FRM3, write the VO and FA using NCS Expert and copy the I-level from CAS using Tool32.

[maninblack]

hi,

no i have an original upa. its reliable. I did tens of frm, i know how to extract eee from dflash.

i think it is an hardware issue (frm hardware, not my programmer)

I could identify the corrupt dflash bytes and could repair them. but there is no option to write the dflash to frm. Is this correct? Is dflash not writeable with programmer?

[Enabled]

You need to research more...

The FRM doesn't use dflash at all.
It uses a virtual eeprom that takes up the whole space of dflash. Zero dflash.

When the partition table corrupts, you lose the correct partitioning and you get a false dflash.

There are programs made that you can use to rebuild yourself an eeprom from the false dflash.
You will still have to erase the mcu and fix the partition first, then write in pflash and eeprom. I would make sure to backup all you can.

[autombr]

Need help I have d-flash corrupted

[Cowboy]

Here you go, it's in the attachment