[daniersms]

You need to read the d-flash then create new eeeprom with the tomvanleeuwen method and write the eeeprom back but you need to partition the d-flash.Just have a look on youtube there are some vids there

[Tombo]

As I said if is possible to read eprom the frm is in normal working order and is not possible to read d flash.
If frm broke then is not possible to read eprom but possible to read dflash. That's because eprom partition is moved in to d-flash.
Frm from this thread is working as normal

[Aldi]

As I said if is possible to read eprom the frm is in normal working order and is not possible to read d flash.
If frm broke then is not possible to read eprom but possible to read dflash. That's because eprom partition is moved in to d-flash.
Frm from this thread is working as normal

It is an old thread but my xprog 5.51 behave exactly the same.
I can read P-Flash and eeeprom but can't read D-Flash.
The results when reading D-Flash return to 0x0.
I'm just trying to test my xprog on a defective FRM.
I don't know exactly what is wrong with FRM.

Is that normal that in an non corrupted FRM you can't read D-Flash?

Thank you in the advance.

[sixcode]

As I said if is possible to read eprom the frm is in normal working order and is not possible to read d flash.
If frm broke then is not possible to read eprom but possible to read dflash. That's because eprom partition is moved in to d-flash.
Frm from this thread is working as normal

It is an old thread but my xprog 5.51 behave exactly the same.
I can read P-Flash and eeeprom but can't read  D-Flash.
The results when reading D-Flash return to 0x0.
I'm just trying to test my xprog on a defective FRM.
I don't know exactly what is wrong with FRM.

Is that normal that in an non corrupted FRM you can't read D-Flash?

Thank you in the advance.

if dflash is 0x0 then your frm is not corrupt