Hi Shane,
thanks for your report.
Auf 12.01.2011 21:58, sdbarnes@rockwellcollins.com schrieb:
I can read succcessfully read the flash ROM contents: [...] I can also successfully write the same flash ROM contents: [...] However, when I try to write a new flash ROM (provided by the motherboard manufacturer), the erase function fails:
[root]#./flashrom -w i3700n1t.bin
flashrom v0.9.3-r1250 on Linux 2.6.24.7 (i686), built with libpci 2.2.9, GCC 4.1.2 20070925 (Red Hat 4.1.2-33), little endian Calibrating delay loop... OK. No coreboot table found. Invalid string keyword: chassis-type
That is very odd. Maybe your dmidecode is too old. Could you upgrade it so we have a chance to get a better log?
dmidecode execution unsucessfull - continuing without DMI info Found chipset "Intel ICH7M", enabling flash write... OK. This chipset supports the following protocols: FWH. Found chip "Winbond W39V040FC" (512 KB, FWH) at physical address 0xfff80000. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
Hm OK, so at least PROBE works.
Erasing and writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0000ffff: 0x3ec ERASE FAILED! ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x5437e ERASE FAILED! Done. Verifying flash... VERIFY FAILED at 0x00000000! Expected=0xed, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x13ea Your flash chip is in an unknown state.
This part of the log is very strange. Can you run "make distclean", rebuild flashrom, and retry the write in verbose mode? AFAICS the messages above can not be triggered in that combination if you try to write, but they may happen if you try to erase.
To rule out a bug in flashrom, the verbose write log would be very appreciated.
Oh, and please try to write the old image again to make sure the machine still comes up after a reboot.
Regards, Carl-Daniel