(SOLVED!) How to read and write mainboard Flash (Spansion S29GL)

[oscarboiro]

Today I erase a FX unit, after erase (completed process) I disconnect the power, my purpose are write unit more later.

When I connect the power later, I don’t possible connect with jtag and show this message:

369CEF4E-BC1D-4955-AEA4-4F14DF873EA4.jpeg

I try to delete “Disable MMU”

149CB469-EBD0-4F9D-B44C-541832D25693.jpeg

And now after push connect don’t have problem, but the problem comes when push write:

70B62A32-B6F5-4207-90AD-13E6CF582648.jpeg

Now I have another killed unit!! Hahahaha

And my question, what is the method to write a blank OMAP?

[Stevebe]

I have the same problem I erased a NX and got the same messages and Con not connect any more

Has the project.fladh file been removed

74EFF858-F686-4CDC-BD45-FD90AF36808F.png

[DGAlexandru]

Read my post from this thread - viewtopic.php?f=3&t=2&start=70#p442 .
I had the same problem.
Download and use that jlink configuration file.

[Go4IT]

He used my JFlash-Init-File and this already disables WP by Software. Trying doing so by hardware would not harm, anyway.
And keep my warning in mind to have the JTAG wires as short as possible (5 to 10cm max).
In a very last thing beware that even Flash chips may fail in a way they can't be erased or changed anymore...
Also the image above shows some kind of RAM problem, and this is not the external one, it's the internal RAM of the OMAP! So maybe the OMAP fails. You could try to reflow it...

[Stevebe]

He used my JFlash-Init-File and this already disables WP by Software. Trying doing so by hardware would not harm, anyway.
And keep my warning in mind to have the JTAG wires as short as possible (5 to 10cm max).
In a very last thing beware that even Flash chips may fail in a way they can't be erased or changed anymore...
Also the image above shows some kind of RAM problem, and this is not the external one, it's the internal RAM of the OMAP! So maybe the OMAP fails. You could try to reflow it...

Ok I thought as much can you pop the project.flash file in my Dropbox. As I have lost the file due to a drive problem
This is Andy’s old board. Just waiting for your mem to arrive ,
K,

[oscarboiro]

Read my post from this thread - viewtopic.php?f=3&t=2&start=70#p442 .
I had the same problem.
Download and use that jlink configuration file.

hello!!! I read my Fx and all sectors have "FF", do you have a backup from FX? and another from NX?

thanks!!!

[oscarboiro]

Read my post from this thread - viewtopic.php?f=3&t=2&start=70#p442 .
I had the same problem.
Download and use that jlink configuration file.

hello!!! I read my Fx and all sectors have "FF", do you have a backup from FX? and another from NX?

thanks!!!

i have a backup of all units, thanks!!!

[Go4IT]

Ok I thought as much can you pop the project.flash file in my Dropbox. As I have lost the file due to a drive problem
This is Andy’s old board. Just waiting for your mem to arrive ,
K,

Oh, they are all available here: https://mk4-wiki.denkdose.de/artikel/na ... figurieren (will translate this page as soon as i have time for it...)

But i don't think it's related to external SDRAM. You can even JTAG to Flash without external SDRAM soldered in, I told in this thread a while ago. If you are going to change the RAMs anyway, try it out yourself.

Best bet for now is that there is a problem with the OMAP itself.

[Go4IT]

Hey oscarboiro, isn't this the same problem you got with your NX here: viewtopic.php?f=3&t=2&start=60#p308

One thing you may try: replace the eeprom with one from a working device.
Also check voltages (look view posts before).

[Go4IT]

Did you also check the voltages?

IMG_3595.JPG

The main 1.6 volts is for the HMI and 2.5 volts for the RAM. The Flash is driven by the input 3.3 voltage.