Am Freitag, den 04.03.2011, 22:45 +0100 schrieb Michał Janke:
Well, it IS strange - sometimes the chip gets flashed ok in spite of an error during erease and sometimes there is either no such error or the error causes writing to fail. I attach a console script log showing how it looks like (a series ofnon-verbose flashing attempts) and one verbose log.
It looks like sometimes the erase command doesn't get through to the chip. We try two different erase methods, first erasing 4K blocks and then we try erasing 64K blocks. The whole process only fails of both erase methods fail (i.e. you get "ERASE FAILED at 0x...." twice). Thanks for the logs, we have to check what we can find in flashrom. Some thing you could try is: Do you get the random failures also in single user mode? There might be something performing concurrent access to the flash chip (like some ACPI stuff) or interrupts causing too high delays between flash access cycles make write commands not recognize. Having no background tasks mitigates the latency problem.
Regards, Michael Karcher