[flashrom] M25P16, erase (ok) and write (not ok)

[Raven]

Hello Stefan,
ok then i try to write in English.
Hope you understand my bad English ;-)

I have tried to stabilize the Vcc with an additional Capacitor and cut 
the cables (to minimize the length), but with no luck.

I'm not sure if the Flash is really broken. Maybe the Programmer has a 
Problem (is unstable).
Sometimes the arduino "locks up" and i have to unplug and plug the USB 
again. :-\
Also tried with the parameter "spispeed=xx" but same (bad) results.

I have an AT45DB011B chip here, but unfortunately this chip is 
unsupported. :-(
Not sure what the difference between the "B" and the "D" is.
But if i have time i try it with a AT45DB161D, this chip should be 
supported.

I try to do some tests with other chips, let's see if it works.

Have a nice day!

Greetings Marc


Am 17.10.2013 18:02, schrieb Stefan Tauner:
> On Thu, 17 Oct 2013 14:13:31 +0200
> Raven <originalraven at hotmail.com> wrote:
>
>> Hallo Stefan,
>> anhand des "at" am Ende denke (oder hoffe) ich du sprichst deutsch.
> Sure, but not everybody else does. ;) If is it is not too much of a
> burden on you please try to reply in English, and I hope you understand
> my mails well enough. If not we can continue in German too of course
> (if need be at all... looks like that chip is dead anyway :/)
>
>> Der Chip ist ein 3.3V, ich Depp habe es aber mit dem 5V Adapter probiert.
>> Daher kann es sein das der Chip nun nicht mehr so toll ist... :-\
>> Jetzt verwende ich den 3.3V Adapter den ich mir vorhin schnell zusammen
>> gebaut habe.
>> Habe den Flash nun mehrmals Veryfied, manchmal geht es manchmal nicht.
>> Aber wenn der Chip nun einen Knacks hat sind jegliche weitere tests
>> zwecklos.
>> Der Fehler kommt übrigens immer an einem anderen Ort. Mal hier, mal da...
>> Läuft etwas unstabil.
>>
>> *Geht:*
>> /Reading old flash chip contents... done.//
>> //Verifying flash... VERIFIED./
>>
>> *Geht nicht:*
>> /Reading old flash chip contents... done.//
>> //Verifying flash... FAILED at 0x00096a02! Expected=0x0b, Found=0x47,
>> failed byte count from 0x00000000-0x001fffff: 0x39d/
>>
>> oder mit version 0.9.5.2-r1517
>> Reading old flash chip contents... done.
>> Verifying flash... VERIFY FAILED at 0x00148489! Expected=0x02,
>> Read=0x00, failed byte count from 0x00000000-0x001fffff: 0xe9
>> /
>> Reading old flash chip contents... done.//
>> //Verifying flash... VERIFY FAILED at 0x0002369b! Expected=0x5a,
>> Read=0xc6, failed byte count from 0x00000000-0x001fffff: 0x39//
>> /
> OK that all sounds like a dying chip to me, although I can't explain
> the symptoms in details. Fried electronics are even harder to
> understand than working ones ;)
>
>> Habe auch versucht den Speed runter zu stellen
>> (serprog:dev=/dev/ttyACM0:1500000).
>> Was aber nicht funktioniert hat. Wenn ich weiter runter gehe bekomme ich
>> einen Sync error:
>> /
>> //Calibrating delay loop... OK.//
>> //Error: cannot synchronize protocol - check communications and reset
>> device?//
>> //Error: Programmer initialization failed./
> The baud rate of the serprog module does change the communication rate
> between the micro controller and the host PC. That of course depends on
> the configuration of the Arduino and is usually fixed, and probably
> irrelevant in your case. What might be more interesting is the clock
> signal the micro controller applies to the flash chip. That can be
> changed by adding ",spispeed=..." to the programmer parameter, and only
> if the serprog implementation in the Arduino supports it. See manpage
> for details of the parameter.
>
>> An der Kabellänge kann es auch nicht liegen, denn die beträgt weniger
>> als 10cm.
> OK
>
>> Lange Rede kurzer Sinn:
>> Ich schaue das ich einen neuen Chip organisieren kann und teste damit.
>> Bez. es kann auch sein das es am Programmer und gar nicht an flashrom liegt!
> Yes, I would definitely try to get another chip if you want to get some
> device working (again) reliably. You can probably use many other flash
> chips because most of them are very similar (same pin layout, mostly
> equal protocol)...
>
>> Eine andere Frage:
>> Wiso werden die AT45DBxxx Chips nicht unterstützt? Gibt es da eine
>> möglichkeit diese
>> zu unterstützen?
> but there are exceptions. The AT45DB series is such an exception, but
> thanks to the work of Aidan Thornton and myself they are supported now.
> You need at least flashrom revision 1723 (which is included in 0.9.7).
> Be aware of the different pin layout!
>