Hi all,
I have a SuperMicro H8QG6/i-F motherboard, which I recently attempted to flash with flashrom. As per the man page, I probed the rom first, then made a backup of the current state, which I have. Initially, the probe reported my chip as a "SST SST25VF016B", with the probe, read, and write operations supported. I attempted to flash another copy of the current rom (obtained from super micro's website), and it complained about not being able to erase, then said "SUCCESS" and "done", and "COMPLETE". Then it started verifying, and the verify failed. I then tried to restore the backup I had made, and it now reports the chip as a "SST unknown SST SPI chip", with all four operations not working. Attached are the output of the failed flash attempt, and a probe from after that attempt.
Thanks, --Colin
Am Mittwoch, den 21.07.2010, 22:19 -0400 schrieb Colin Williams:
complained about not being able to erase, then said "SUCCESS" and "done", and "COMPLETE".
The output of flashrom is a bit confusing, cleaning that up is one of the many pending tasks. Your flash chip has different erase methods, and if one fails, we try the next one. In your case, flashrom tried erasing in blocks of 4K each, but the second 4K block was not erased. It then tried to erase 32K each block, and failed in the first block. On erasing in blocks of 64K, erasing 4 blocks went OK while it hit a problem in the 5th block. Finally it tried a "chip erase" instruction which worked. (this is the "SUCCESS" in your output). Then it sent write instructions to the flash chip for all data bytes, after that it said "COMPLETE". Finally on checking that the write was successfull, it finds out that many write instructions in fact did not work.
For the erase instructions, I am surprised to find that every failed erase instruction has "0xe9" as its first non-erased byte. Flashrom checks the success of the erase by reading the to-be-erased region and comparing it to the expect result of 0xff. What's also interesting is that the failures are always on an address with the last five bits being 0x08. I suspect that something goes wrong with the communication between the chipset and the flash chip (maybe some other flash accesses, for example from System Management Mode?).
and it now reports the chip as a "SST unknown SST SPI chip", with all four operations not working. Attached are the output of the failed flash attempt, and a probe from after that attempt.
can you please send the output of "flashrom -VV" and "lspci -vvvnnxxx" to the list, and send me privately the old backup image, the image you tried to write and the file "contentsnow.bin" created by 'flashrom -r contentsnow.bin -f -c SST49LF160C', and also check whether different runs of flashrom create the same contentsnow.bin? It looks like flashrom managed to mess up your chipset configuration that much that most flash accesses do not do what they really should do anymore.
Regards, Michael Karcher
On 22.07.2010 09:33, Michael Karcher wrote:
[...] I suspect that something goes wrong with the communication between the chipset and the flash chip (maybe some other flash accesses, for example from System Management Mode?).
The board has an IPMI controller which may cause all sorts of screwups.
Greg, Colin, can you get a sharp high-res photo of the region of the board where the flash chip is located and upload that to imageshack or some other service? I want to be 100% sure that we're not dealing with a situation where two flash chips are present, and the IPMI controller switches between chips to confuse flashrom to no end.
Am Mittwoch, den 21.07.2010, 22:19 -0400 schrieb Colin Williams
and it now reports the chip as a "SST unknown SST SPI chip", with all four operations not working. Attached are the output of the failed flash attempt, and a probe from after that attempt.
can you please send the output of "flashrom -VV" and "lspci -vvvnnxxx" to the list, and send me privately the old backup image, the image you tried to write and the file "contentsnow.bin" created by 'flashrom -r contentsnow.bin -f -c SST49LF160C', and also check whether different runs of flashrom create the same contentsnow.bin? It looks like flashrom managed to mess up your chipset configuration that much that most flash accesses do not do what they really should do anymore.
Yes, the flash chip seems to be totally confused. Once we have the output of the commands above, we have a good chance to find a way to whack the chip on the head so that it will respond normally again.
Regards, Carl-Daniel
On 22.07.2010 13:05, Carl-Daniel Hailfinger wrote:
On 22.07.2010 09:33, Michael Karcher wrote:
[...] I suspect that something goes wrong with the communication between the chipset and the flash chip (maybe some other flash accesses, for example from System Management Mode?).
The board has an IPMI controller which may cause all sorts of screwups.
Greg, Colin, can you get a sharp high-res photo of the region of the board where the flash chip is located and upload that to imageshack or some other service? I want to be 100% sure that we're not dealing with a situation where two flash chips are present, and the IPMI controller switches between chips to confuse flashrom to no end.
Ummm... the photo you sent showed the IPMI controller, but I wanted a photo of the SST25VF016B flash chip and the region around it. Please upload your photo to imageshack.us (my mailbox is overflowing already and further huge mails may be discarded silently) and paste only the link to that photo in your mail.
On 22.07.2010 09:33, Michael Karcher wrote
Am Mittwoch, den 21.07.2010, 22:19 -0400 schrieb Colin Williams
and it now reports the chip as a "SST unknown SST SPI chip", with all four operations not working. Attached are the output of the failed flash attempt, and a probe from after that attempt.
can you please send the output of "flashrom -VV" and "lspci -vvvnnxxx" to the list, and send me privately the old backup image, the image you tried to write and the file "contentsnow.bin" created by 'flashrom -r contentsnow.bin -f -c SST49LF160C', and also check whether different runs of flashrom create the same contentsnow.bin? It looks like flashrom managed to mess up your chipset configuration that much that most flash accesses do not do what they really should do anymore.
Yes, the flash chip seems to be totally confused. Once we have the output of the commands above, we have a good chance to find a way to whack the chip on the head so that it will respond normally again.
From the readbacks you sent I got the following information:
carldani@p35:~> hexdump -C contentsnow.bin 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 001f0a70 ff fb ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| 001f0a80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00200000 carldani@p35:~> hexdump -C contentsnow2.bin 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 001f0a70 ff fb ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| 001f0a80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00200000 carldani@p35:~> hexdump -C contentsnow3.bin 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00200000
contentsnow.bin and contentsnow2.bin are SST49LF160C readbacks (i.e. memory dumps) and contentsnow3.bin is a SST25VF016B readback (SPI dump).
Your "flashrom -VV" output was truncated, but I think a few essential pieces of information were usable. It seems that the FIFO for reading is dysfunctional right now and returns a repeat of the first response byte, but apparently it worked well for the original read. The IPMI controller and/or the 8051 core in the southbridge may be interfering as well.
Can you reply-to-all with the output from "flashrom -V" to allow us to cross-check my assumptions?
Regards, Carl-Daniel
*Your "flashrom -VV" output was truncated, but I think a few essential pieces of information were usable. It seems that the FIFO for reading is dysfunctional right now and returns a repeat of the first response byte, but apparently it worked well for the original read. The IPMI controller and/or the 8051 core in the southbridge may be interfering as well.
Can you reply-to-all with the output from "flashrom -V" to allow us to cross-check my assumptions?*
[root@slinux ~]# [root@slinux ~]# flashrom -V flashrom v0.9.2-r1001 on Linux 2.6.18-194.8.1.el5 (x86_64), built with libpci 2.2.3, GCC 4.1.2 20080704 (Red Hat 4.1.2-48) flashrom is free software, get the source code at http://www.flashrom.org
Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Supermicro" DMI string system-product-name: "H8QG6" DMI string system-version: "1234567890" DMI string baseboard-manufacturer: "Supermicro" DMI string baseboard-product-name: "H8QG6" DMI string baseboard-version: "1234567890" DMI string chassis-type: "Desktop" Found chipset "AMD SB700/SB710/SB750", enabling flash write... SPI base address is at 0xfec10000 AltSpiCSEnable=0, SpiRomEnable=1, AbortEnable=0 PrefetchEnSPIFromIMC=0, PrefetchEnSPIFromHost=1, SpiOpEnInLpcMode=1 SpiArbEnable=1, SpiAccessMacRomEn=1, SpiHostAccessRomEn=1, ArbWaitCount=7, SpiBridgeDisable=1, DropOneClkOnRd=0 GPIO11 used for SPI_DO GPIO12 used for SPI_DI GPIO31 used for SPI_HOLD GPIO32 used for SPI_CS GPIO47 used for SPI_CLK ROM strap override is not active OK. This chipset supports the following protocols: LPC,FWH,SPI. Calibrating delay loop... 995M loops per second, 10 myus = 10 us, 100 myus = 101 us, 1000 myus = 1001 us, 10000 myus = 10004 us, OK. Probing for AMD Am29F010A/B, 128 KB: skipped. Probing for AMD Am29F002(N)BB, 256 KB: skipped. Probing for AMD Am29F002(N)BT, 256 KB: skipped. Probing for AMD Am29F016D, 2048 KB: skipped. Probing for AMD Am29F040B, 512 KB: skipped. Probing for AMD Am29F080B, 1024 KB: skipped. Probing for AMD Am29LV040B, 512 KB: skipped. Probing for AMD Am29LV081B, 1024 KB: skipped. Probing for ASD AE49F2008, 256 KB: skipped. Probing for Atmel AT25DF021, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25DF041A, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25DF081, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25DF321, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25DF321A, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25DF641, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25F512B, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25FS010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT25FS040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT26DF041, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT26DF081A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT26DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT26DF161A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT26F004, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT29C512, 64 KB: skipped. Probing for Atmel AT29C010A, 128 KB: skipped. Probing for Atmel AT29C020, 256 KB: skipped. Probing for Atmel AT29C040A, 512 KB: skipped. Probing for Atmel AT45CS1282, 16896 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB011D, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB021D, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB041D, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB081D, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB161D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB321C, 4224 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB321D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT45DB642D, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Atmel AT49BV512, 64 KB: skipped. Probing for Atmel AT49F002(N), 256 KB: skipped. Probing for Atmel AT49F002(N)T, 256 KB: skipped. Probing for AMIC A25L40PT, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for AMIC A25L40PU, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for AMIC A29002B, 256 KB: skipped. Probing for AMIC A29002T, 256 KB: skipped. Probing for AMIC A29040B, 512 KB: skipped. Probing for AMIC A49LF040A, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for EMST F49B002UA, 256 KB: skipped. Probing for Eon EN25B05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B05T, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B10T, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B20T, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B40T, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B80T, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B16T, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B32T, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25B64T, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25D16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25F05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25F10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25F20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25F40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25F80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25F16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN25F32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Eon EN29F010, 128 KB: skipped. Probing for EON EN29F002(A)(N)B, 256 KB: skipped. Probing for EON EN29F002(A)(N)T, 256 KB: skipped. Probing for Fujitsu MBM29F004BC, 512 KB: skipped. Probing for Fujitsu MBM29F004TC, 512 KB: skipped. Probing for Fujitsu MBM29F400BC, 512 KB: skipped. Probing for Fujitsu MBM29F400TC, 512 KB: skipped. Probing for Intel 28F001BX-B, 128 KB: skipped. Probing for Intel 28F001BX-T, 128 KB: skipped. Probing for Intel 28F004S5, 512 KB: skipped. Probing for Intel 28F004BV/BE-B, 512 KB: skipped. Probing for Intel 28F004BV/BE-T, 512 KB: skipped. Probing for Intel 28F400BV/CV/CE-B, 512 KB: skipped. Probing for Intel 28F400BV/CV/CE-T, 512 KB: skipped. Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX25L512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L1005, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L2005, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L4005, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L8005, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L1605, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L1635D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L3205, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L3235D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L6405, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX25L12805, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix MX29F001B, 128 KB: skipped. Probing for Macronix MX29F001T, 128 KB: skipped. Probing for Macronix MX29F002B, 256 KB: skipped. Probing for Macronix MX29F002T, 256 KB: skipped. Probing for Macronix MX29LV040, 512 KB: skipped. Probing for Numonyx M25PE10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Numonyx M25PE20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Numonyx M25PE40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Numonyx M25PE80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Numonyx M25PE16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC Pm25LV010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC Pm25LV016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC Pm25LV020, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC Pm25LV040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC Pm25LV080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC Pm25LV512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC Pm29F002T, 256 KB: skipped. Probing for PMC Pm29F002B, 256 KB: skipped. Probing for PMC Pm39LV010, 128 KB: skipped. Probing for PMC Pm39LV020, 256 KB: skipped. Probing for PMC Pm39LV040, 512 KB: skipped. Probing for PMC Pm49FL002, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sanyo LF25FW203A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Spansion S25FL008A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Spansion S25FL016A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for SST SST25VF016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for SST SST25VF032B, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for SST SST25VF040.REMS, 512 KB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF040B, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for SST SST25VF040B.REMS, 512 KB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for SST SST28SF040A, 512 KB: skipped. Probing for SST SST29EE010, 128 KB: skipped. Probing for SST SST29LE010, 128 KB: skipped. Probing for SST SST29EE020A, 256 KB: skipped. Probing for SST SST29LE020, 256 KB: skipped. Probing for SST SST39SF512, 64 KB: skipped. Probing for SST SST39SF010A, 128 KB: skipped. Probing for SST SST39SF020A, 256 KB: skipped. Probing for SST SST39SF040, 512 KB: skipped. Probing for SST SST39VF512, 64 KB: skipped. Probing for SST SST39VF010, 128 KB: skipped. Probing for SST SST39VF020, 256 KB: skipped. Probing for SST SST39VF040, 512 KB: skipped. Probing for SST SST39VF080, 1024 KB: skipped. Probing for SST SST49LF002A/B, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M25P05-A, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P05.RES, 64 KB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P10.RES, 128 KB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P40-old, 512 KB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M25P128, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for ST M29F002B, 256 KB: skipped. Probing for ST M29F002T/NT, 256 KB: skipped. Probing for ST M29F040B, 512 KB: skipped. Probing for ST M29F400BT, 512 KB: skipped. Probing for ST M29W010B, 128 KB: skipped. Probing for ST M29W040B, 512 KB: skipped. Probing for ST M29W512B, 64 KB: skipped. Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS S29C31004T, 512 KB: skipped. Probing for SyncMOS S29C51001T, 128 KB: skipped. Probing for SyncMOS S29C51002T, 256 KB: skipped. Probing for SyncMOS S29C51004T, 512 KB: skipped. Probing for TI TMS29F002RB, 256 KB: skipped. Probing for TI TMS29F002RT, 256 KB: skipped. Probing for Winbond W25Q80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25Q16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25Q32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25x10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25x20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25x40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25x80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25x16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25x32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W25x64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Winbond W29C011, 128 KB: skipped. Probing for Winbond W29C020C, 256 KB: skipped. Probing for Winbond W29C040P, 512 KB: skipped. Probing for Winbond W29EE011, 128 KB: skipped. Probing for Winbond W39V040A, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U, 256 KB: skipped. Probing for Winbond W49V002A, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel unknown Atmel SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for EON unknown EON SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Macronix unknown Macronix SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for PMC unknown PMC SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for SST unknown SST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Found chip "SST unknown SST SPI chip" (0 KB, SPI) at physical address 0x0. Probing for ST unknown ST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Sanyo unknown Sanyo SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Generic unknown SPI chip (RDID), 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0xbfbf Probing for Generic unknown SPI chip (REMS), 0 KB: probe_spi_rems: id1 0x0, id2 0x0 === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom@flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -Vw, -VE), and mention which mainboard or programmer you tested. Thanks for your help! === No operations were specified. [root@slinux ~]#
On Thu, Jul 22, 2010 at 9:46 PM, Carl-Daniel Hailfinger < c-d.hailfinger.devel.2006@gmx.net> wrote:
On 22.07.2010 13:05, Carl-Daniel Hailfinger wrote:
On 22.07.2010 09:33, Michael Karcher wrote:
[...] I suspect that something goes wrong with the communication between the chipset and the flash chip (maybe some other flash accesses, for example from System Management Mode?).
The board has an IPMI controller which may cause all sorts of screwups.
Greg, Colin, can you get a sharp high-res photo of the region of the board where the flash chip is located and upload that to imageshack or some other service? I want to be 100% sure that we're not dealing with a situation where two flash chips are present, and the IPMI controller switches between chips to confuse flashrom to no end.
Ummm... the photo you sent showed the IPMI controller, but I wanted a photo of the SST25VF016B flash chip and the region around it. Please upload your photo to imageshack.us (my mailbox is overflowing already and further huge mails may be discarded silently) and paste only the link to that photo in your mail.
On 22.07.2010 09:33, Michael Karcher wrote
Am Mittwoch, den 21.07.2010, 22:19 -0400 schrieb Colin Williams
and it now reports the chip as a "SST unknown SST SPI chip", with all four operations not working. Attached are the output of the failed flash attempt, and a probe from after that attempt.
can you please send the output of "flashrom -VV" and "lspci -vvvnnxxx" to the list, and send me privately the old backup image, the image you tried to write and the file "contentsnow.bin" created by 'flashrom -r contentsnow.bin -f -c SST49LF160C', and also check whether different runs of flashrom create the same contentsnow.bin? It looks like flashrom managed to mess up your chipset configuration that much that most flash accesses do not do what they really should do anymore.
Yes, the flash chip seems to be totally confused. Once we have the output of the commands above, we have a good chance to find a way to whack the chip on the head so that it will respond normally again.
From the readbacks you sent I got the following information:
carldani@p35:~> hexdump -C contentsnow.bin 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
001f0a70 ff fb ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| 001f0a80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
00200000 carldani@p35:~> hexdump -C contentsnow2.bin 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
001f0a70 ff fb ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| 001f0a80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
00200000 carldani@p35:~> hexdump -C contentsnow3.bin 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
00200000
contentsnow.bin and contentsnow2.bin are SST49LF160C readbacks (i.e. memory dumps) and contentsnow3.bin is a SST25VF016B readback (SPI dump).
Your "flashrom -VV" output was truncated, but I think a few essential pieces of information were usable. It seems that the FIFO for reading is dysfunctional right now and returns a repeat of the first response byte, but apparently it worked well for the original read. The IPMI controller and/or the 8051 core in the southbridge may be interfering as well.
Can you reply-to-all with the output from "flashrom -V" to allow us to cross-check my assumptions?
Regards, Carl-Daniel
Hi Greg, hi Colin,
what's the current state of this? I'm dealing with ~10 different flashrom related projects/problems at the same time and want to make sure nobody is left behind.
Regards, Carl-Daniel
-
Carl-Daniel Hailfinger -
Colin Williams -
Greg Scantlen -
Michael Karcher