On Mon, Apr 28, 2014 at 08:45:14AM +0200, Carl-Daniel Hailfinger wrote:
Amit confirmed that probe works: "Found Winbond flash chip "W25X40" (512 kB, SPI) on satamv." However, reading failed due to incorrect limits in max_data_read and max_data_write.
New version, read should work fine. Write might work, but I'd rather wait a bit for that unless we know the image is correct and the flash chip can be accessed easily with another external programmer.
Signed-off-by: Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Thanks for the latest patch! Read works as expected, the file I read looks good.
Write does not work as of yet. Here is the output:
$ sudo ./flashrom -p satamv -w 9445_rev5.bin flashrom v0.9.7-r1769 on Linux 3.2.48-logicube-ng.16-bfq (x86_64) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Winbond flash chip "W25X40" (512 kB, SPI) on satamv. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x55, failed byte count from 0x00000000-0x00000fff: 0xf37 ERASE FAILED! Reading current flash chip contents... done. FAILED at 0x00000000! Expected=0xff, Found=0x55, failed byte count from 0x00000000-0x0000ffff: 0xfcd0 ERASE FAILED! Reading current flash chip contents... done. FAILED at 0x00000000! Expected=0xff, Found=0x55, failed byte count from 0x00000000-0x0007ffff: 0x25de9 ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. Good. It seems nothing was changed. Writing to the flash chip apparently didn't do anything. Please check the connections (especially those to write protection pins) between the programmer and the flash chip. If you think the error is caused by flashrom please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom@flashrom.org, thanks!