Am Dienstag, den 15.03.2011, 02:05 +0100 schrieb Stefan Tauner:
even more puzzling (at least for me atm) are these erase verify failures... ./flashrom -V -p nic3com -c "W29C010(M)/W29C011A/W29EE011/W29EE012" -w ../testimages/128kB.rand.img ... Reading old flash chip contents... Erasing and writing flash chip... Looking at blockwise erase function 0... trying... 0x000000-0x01ffff:EWVERIFY FAILED at 0x00008400! Expected=0xa6, Read=0x00, failed byte count from 0x00008400-0x0000847f: 0x80 retrying. VERIFY FAILED at 0x0000f180! Expected=0xb9, Read=0x00, failed byte count from 0x0000f180-0x0000f1ff: 0x7d retrying.
The key is "retrying". We really need to suppress the frightening "VERIFY FAILED" messages for these chips. It retries a page up to ten times, and only bails out then.
BTW: These failures don't look like the typical "we didn't manage to get the whole page without timeout" problem. Maybe the need for retrying on these chips is normal, or our toggle-bit code terminates early...
Regards, Michael Karcher