flashrom

flashrom@flashrom.org

9164 discussions

Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by sdbarnes＠rockwellcollins.com 10 Dec '12

10 Dec '12

Despite the verification failure, the motherboard appears to function properly with the new flash image that is written. Below is the flashrom verbose output: flashrom v0.9.3-r1250 on Linux 2.6.32.59 (i686), built with libpci 3.1.7, GCC 4.3.4, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 1344M loops per second, 10 myus = 12 us, 100 myus = 109 us, 1000 myus = 1088 us, 10000 myus = 9464 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: " " DMI string system-product-name: " " DMI string system-version: " " DMI string baseboard-manufacturer: " " DMI string baseboard-product-name: "945GM" DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found chipset "Intel ICH7M", enabling flash write... chipset PCI ID is 8086:27b9, 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled OK. This chipset supports the following protocols: FWH. 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 AMIC A25L05PT, 64 KB: skipped. Probing for AMIC A25L05PU, 64 KB: skipped. Probing for AMIC A25L10PT, 128 KB: skipped. Probing for AMIC A25L10PU, 128 KB: skipped. Probing for AMIC A25L20PT, 256 KB: skipped. Probing for AMIC A25L20PU, 256 KB: skipped. Probing for AMIC A25L40PT, 512 KB: skipped. Probing for AMIC A25L40PU, 512 KB: skipped. Probing for AMIC A25L80P, 1024 KB: skipped. Probing for AMIC A25L16PT, 2048 KB: skipped. Probing for AMIC A25L16PU, 2048 KB: skipped. Probing for AMIC A25L512, 64 KB: skipped. Probing for AMIC A25L010, 128 KB: skipped. Probing for AMIC A25L020, 256 KB: skipped. Probing for AMIC A25L040, 512 KB: skipped. Probing for AMIC A25L080, 1024 KB: skipped. Probing for AMIC A25L016, 2048 KB: skipped. Probing for AMIC A25L032, 4096 KB: skipped. Probing for AMIC A25LQ032, 4096 KB: skipped. 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: skipped. Probing for Atmel AT25DF021, 256 KB: skipped. Probing for Atmel AT25DF041A, 512 KB: skipped. Probing for Atmel AT25DF081, 1024 KB: skipped. Probing for Atmel AT25DF081A, 1024 KB: skipped. Probing for Atmel AT25DF161, 2048 KB: skipped. Probing for Atmel AT25DF321, 4096 KB: skipped. Probing for Atmel AT25DF321A, 4096 KB: skipped. Probing for Atmel AT25DF641, 8192 KB: skipped. Probing for Atmel AT25DQ161, 2048 KB: skipped. Probing for Atmel AT25F512B, 64 KB: skipped. Probing for Atmel AT25FS010, 128 KB: skipped. Probing for Atmel AT25FS040, 512 KB: skipped. Probing for Atmel AT26DF041, 512 KB: skipped. Probing for Atmel AT26DF081A, 1024 KB: skipped. Probing for Atmel AT26DF161, 2048 KB: skipped. Probing for Atmel AT26DF161A, 2048 KB: skipped. Probing for Atmel AT26F004, 512 KB: skipped. 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: skipped. Probing for Atmel AT45DB011D, 128 KB: skipped. Probing for Atmel AT45DB021D, 256 KB: skipped. Probing for Atmel AT45DB041D, 512 KB: skipped. Probing for Atmel AT45DB081D, 1024 KB: skipped. Probing for Atmel AT45DB161D, 2048 KB: skipped. Probing for Atmel AT45DB321C, 4224 KB: skipped. Probing for Atmel AT45DB321D, 4096 KB: skipped. Probing for Atmel AT45DB642D, 8192 KB: skipped. Probing for Atmel AT49BV512, 64 KB: skipped. Probing for Atmel AT49F020, 256 KB: skipped. Probing for Atmel AT49F002(N), 256 KB: skipped. Probing for Atmel AT49F002(N)T, 256 KB: skipped. Probing for Bright BM29F040, 512 KB: skipped. Probing for EMST F49B002UA, 256 KB: skipped. Probing for EMST F25L008A, 1024 KB: skipped. Probing for Eon EN25B05, 64 KB: skipped. Probing for Eon EN25B05T, 64 KB: skipped. Probing for Eon EN25B10, 128 KB: skipped. Probing for Eon EN25B10T, 128 KB: skipped. Probing for Eon EN25B20, 256 KB: skipped. Probing for Eon EN25B20T, 256 KB: skipped. Probing for Eon EN25B40, 512 KB: skipped. Probing for Eon EN25B40T, 512 KB: skipped. Probing for Eon EN25B80, 1024 KB: skipped. Probing for Eon EN25B80T, 1024 KB: skipped. Probing for Eon EN25B16, 2048 KB: skipped. Probing for Eon EN25B16T, 2048 KB: skipped. Probing for Eon EN25B32, 4096 KB: skipped. Probing for Eon EN25B32T, 4096 KB: skipped. Probing for Eon EN25B64, 8192 KB: skipped. Probing for Eon EN25B64T, 8192 KB: skipped. Probing for Eon EN25D16, 2048 KB: skipped. Probing for Eon EN25F05, 64 KB: skipped. Probing for Eon EN25F10, 128 KB: skipped. Probing for Eon EN25F20, 256 KB: skipped. Probing for Eon EN25F40, 512 KB: skipped. Probing for Eon EN25F80, 1024 KB: skipped. Probing for Eon EN25F16, 2048 KB: skipped. Probing for Eon EN25F32, 4096 KB: skipped. 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 Hyundai HY29F002T, 256 KB: skipped. Probing for Hyundai HY29F002B, 256 KB: skipped. Probing for Hyundai HY29F040A, 512 KB: skipped. Probing for Intel 28F001BN/BX-B, 128 KB: skipped. Probing for Intel 28F001BN/BX-T, 128 KB: skipped. Probing for Intel 28F002BC/BL/BV/BX-T, 256 KB: skipped. Probing for Intel 28F008S3/S5/SC, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-B, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-T, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-B, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-T, 512 KB: skipped. Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX25L512, 64 KB: skipped. Probing for Macronix MX25L1005, 128 KB: skipped. Probing for Macronix MX25L2005, 256 KB: skipped. Probing for Macronix MX25L4005, 512 KB: skipped. Probing for Macronix MX25L8005, 1024 KB: skipped. Probing for Macronix MX25L1605, 2048 KB: skipped. Probing for Macronix MX25L1635D, 2048 KB: skipped. Probing for Macronix MX25L1635E, 2048 KB: skipped. Probing for Macronix MX25L3205, 4096 KB: skipped. Probing for Macronix MX25L3235D, 4096 KB: skipped. Probing for Macronix MX25L6405, 8192 KB: skipped. Probing for Macronix MX25L12805, 16384 KB: skipped. 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 MX29F040, 512 KB: skipped. Probing for Macronix MX29LV040, 512 KB: skipped. Probing for MoselVitelic V29C51000B, 64 KB: skipped. Probing for MoselVitelic V29C51000T, 64 KB: skipped. Probing for MoselVitelic V29C51400B, 512 KB: skipped. Probing for MoselVitelic V29C51400T, 512 KB: skipped. Probing for MoselVitelic V29LC51000, 64 KB: skipped. Probing for MoselVitelic V29LC51001, 128 KB: skipped. Probing for MoselVitelic V29LC51002, 256 KB: skipped. Probing for Numonyx M25PE10, 128 KB: skipped. Probing for Numonyx M25PE20, 256 KB: skipped. Probing for Numonyx M25PE40, 512 KB: skipped. Probing for Numonyx M25PE80, 1024 KB: skipped. Probing for Numonyx M25PE16, 2048 KB: skipped. Probing for PMC Pm25LV010, 128 KB: skipped. Probing for PMC Pm25LV016B, 2048 KB: skipped. Probing for PMC Pm25LV020, 256 KB: skipped. Probing for PMC Pm25LV040, 512 KB: skipped. Probing for PMC Pm25LV080B, 1024 KB: skipped. Probing for PMC Pm25LV512, 64 KB: skipped. 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 0x9d, id2 0x6e Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000. Probing for Sanyo LF25FW203A, 2048 KB: skipped. Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Spansion S25FL004A, 512 KB: skipped. Probing for Spansion S25FL008A, 1024 KB: skipped. Probing for Spansion S25FL016A, 2048 KB: skipped. Probing for Spansion S25FL032A, 4096 KB: skipped. Probing for Spansion S25FL064A, 8192 KB: skipped. Probing for SST SST25VF010.REMS, 128 KB: skipped. Probing for SST SST25VF016B, 2048 KB: skipped. Probing for SST SST25VF032B, 4096 KB: skipped. Probing for SST SST25VF064C, 8192 KB: skipped. Probing for SST SST25VF040.REMS, 512 KB: skipped. Probing for SST SST25VF040B, 512 KB: skipped. Probing for SST SST25LF040A.RES, 512 KB: skipped. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Probing for SST SST25VF080B, 1024 KB: skipped. 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 0x9d, id2 0x6e Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. 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: skipped. Probing for SST SST49LF020A, 256 KB: skipped. Probing for SST SST49LF040, 512 KB: skipped. Probing for SST SST49LF040B, 512 KB: skipped. Probing for SST SST49LF080A, 1024 KB: skipped. Probing for SST SST49LF160C, 2048 KB: skipped. Probing for ST M25P05-A, 64 KB: skipped. Probing for ST M25P05.RES, 64 KB: skipped. Probing for ST M25P10-A, 128 KB: skipped. Probing for ST M25P10.RES, 128 KB: skipped. Probing for ST M25P20, 256 KB: skipped. Probing for ST M25P40, 512 KB: skipped. Probing for ST M25P40-old, 512 KB: skipped. Probing for ST M25P80, 1024 KB: skipped. Probing for ST M25P16, 2048 KB: skipped. Probing for ST M25P32, 4096 KB: skipped. Probing for ST M25P64, 8192 KB: skipped. Probing for ST M25P128, 16384 KB: skipped. Probing for ST M25PX32, 4096 KB: skipped. Probing for ST M25PX64, 8192 KB: skipped. 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 M29F400BB, 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 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0x09, id2 0xd5, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. 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 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 KB: skipped. Probing for TI TMS29F002RB, 256 KB: skipped. Probing for TI TMS29F002RT, 256 KB: skipped. Probing for Winbond W25Q80, 1024 KB: skipped. Probing for Winbond W25Q16, 2048 KB: skipped. Probing for Winbond W25Q32, 4096 KB: skipped. Probing for Winbond W25Q64, 8192 KB: skipped. Probing for Winbond W25x10, 128 KB: skipped. Probing for Winbond W25x20, 256 KB: skipped. Probing for Winbond W25x40, 512 KB: skipped. Probing for Winbond W25x80, 1024 KB: skipped. Probing for Winbond W25x16, 2048 KB: skipped. Probing for Winbond W25x32, 4096 KB: skipped. Probing for Winbond W25x64, 8192 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W29C020(C)/W29C022, 256 KB: skipped. Probing for Winbond W29C040/P, 512 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W39V040A, 512 KB: skipped. Probing for Winbond W39V040B, 512 KB: skipped. Probing for Winbond W39V040C, 512 KB: skipped. Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FB, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FC, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080A, 1024 KB: skipped. Probing for Winbond W49F002U/N, 256 KB: skipped. Probing for Winbond W49F020, 256 KB: skipped. Probing for Winbond W49V002A, 256 KB: skipped. Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA (dual mode), 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for AMIC unknown AMIC SPI chip, 0 KB: skipped. Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Probing for Eon unknown Eon SPI chip, 0 KB: skipped. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Probing for SST unknown SST SPI chip, 0 KB: skipped. Probing for ST unknown ST SPI chip, 0 KB: skipped. Probing for Sanyo unknown Sanyo SPI chip, 0 KB: skipped. Probing for Generic unknown SPI chip (RDID), 0 KB: skipped. Probing for Generic unknown SPI chip (REMS), 0 KB: skipped. === This flash part has status UNTESTED for operations: 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(a)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. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling checks. Reading old flash chip contents... Erasing and writing flash chip... Looking at blockwise erase function 0... trying... 0x000000-0x000fff:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S, 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:S, 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, 0x015000-0x015fff:S, 0x016000-0x016fff:S, 0x017000-0x017fff:S, 0x018000-0x018fff:S, 0x019000-0x019fff:S, 0x01a000-0x01afff:S, 0x01b000-0x01bfff:S, 0x01c000-0x01cfff:S, 0x01d000-0x01dfff:S, 0x01e000-0x01efff:S, 0x01f000-0x01ffff:S, 0x020000-0x020fff:S, 0x021000-0x021fff:S, 0x022000-0x022fff:S, 0x023000-0x023fff:S, 0x024000-0x024fff:S, 0x025000-0x025fff:S, 0x026000-0x026fff:S, 0x027000-0x027fff:S, 0x028000-0x028fff:S, 0x029000-0x029fff:S, 0x02a000-0x02afff:S, 0x02b000-0x02bfff:S, 0x02c000-0x02cfff:S, 0x02d000-0x02dfff:S, 0x02e000-0x02efff:S, 0x02f000-0x02ffff:S, 0x030000-0x030fff:S, 0x031000-0x031fff:S, 0x032000-0x032fff:S, 0x033000-0x033fff:S, 0x034000-0x034fff:S, 0x035000-0x035fff:S, 0x036000-0x036fff:S, 0x037000-0x037fff:S, 0x038000-0x038fff:S, 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, 0x03c000-0x03cfff:S, 0x03d000-0x03dfff:S, 0x03e000-0x03efff:S, 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, 0x06f000-0x06ffff:S, 0x070000-0x070fff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x00070fff: 0xf70 ERASE FAILED! Looking at blockwise erase function 1... trying... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x0007ffff: 0xfd35 ERASE FAILED! Looking at blockwise erase function 2... trying... 0x000000-0x07ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x53f0b ERASE FAILED! Looking at blockwise erase function 3... not defined. trying... Done. Verifying flash... VERIFY FAILED at 0x0007010b! Expected=0x7c, Read=0x70, failed byte count from 0x00000000-0x0007ffff: 0x9f2 Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by sdbarnes＠rockwellcollins.com 10 Dec '12

10 Dec '12

1 0

mail archives down?
by Bernd Blaauw 10 Dec '12

10 Dec '12

Are the Pipermail mail archives down for some reason? Seeing this at flashrom, seabios and coreboot, of which I'm only subscribed to the first one (thus reading the other 2 from web archive). Getting a 403/Forbidden when clicking the Archives link at: http://www.flashrom.org/mailman/listinfo/flashrom Bernd

2 1

GA-A75M-UD2H
by Stefan Tauner 09 Dec '12

09 Dec '12

re GA-A75M-UD2H and your log at http://paste.flashrom.org/view.php?id=1490 yes, it looks good. thanks for the log. if you chose the correct file it should have booted afterwards without a problem. is/was that the case? please give us a bit more than 2 minutes in the middle of our night to react next time on IRC or send a mail to the mailing list instead ;) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Failure on 7252 MSI K9NBPM2-FID motherboard
by gordy perkins 08 Dec '12

08 Dec '12

Hello - thanks for the great effort on flashrom. My particular board doesn't flash. Here are the particulars. Ubuntu 12.04, if that matters. 0.9.6.1 failed too... gordy@macoushla:~/Downloads/7252v58$ sudo flashromflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000.Multiple flash chips were detected: "W39V040B", "W39V040FB"Please specify which chip to use with the -c <chipname> option.gordy@macoushla:~/Downloads/7252v58$ sudo flashrom -w A7252NMS.580 -c W39V040Bflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.Reading old flash chip contents... done.Erasing and writing flash chip... ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0000ffff: 0x5200ERASE FAILED!Reading current flash chip contents... done. ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0007ffff: 0x657a4ERASE 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.This means we have to add special support for your board, programmer or flash chip.Please report this on IRC at irc.freenode.net (channel #flashrom) ormail flashrom@flashrom.org!-------------------------------------------------------------------------------You may now reboot or simply leave the machine running.gordy@macoushla:~/Downloads/7252v58$ sudo flashrom -w A7252NMS.580 -c W39V040FBflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000.Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.Reading old flash chip contents... done.Erasing and writing flash chip... ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0000ffff: 0x5200ERASE FAILED!Reading current flash chip contents... done. ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0007ffff: 0x657a4ERASE 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.This means we have to add special support for your board, programmer or flash chip.Please report this on IRC at irc.freenode.net (channel #flashrom) ormail flashrom@flashrom.org!-------------------------------------------------------------------------------You may now reboot or simply leave the machine running.gordy@macoushla:~/Downloads/7252v58$

2 2

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Andrew Goodbody 06 Dec '12

06 Dec '12

On 01/12/12 21:11, Daniel . wrote: > So at last I just need to know now how I can merge the needed > decompressed files back into a flashable ROM file. No, this is the wrong way. You do not need to decompress the .wph file. The .wph file in this case is 1.5MB long with some extra data and code stuck on the end. So the first thing to do is to cut the excess after 1.5MB off the end of that file. This 1.5MB is the top 1.5MB of the 2MB flash image**. Read the first 0.5MB from the flash device* and prefix it to the 1.5MB image to create the 2MB image. You can then program that 2MB image to the flash device. Andrew * If the failed update has corrupted this first 0.5MB on the flash device then you have big trouble. ** If you want to confirm that, disassemble the last 16 bytes of the 1.5MB image, there should be a real mode far jump.

1 0

Fwd: BPv3.6 w flashrom
by Idwer Vollering 05 Dec '12

05 Dec '12

Forwarding. Please "reply to all". ---------- Forwarded message ---------- From: Nabs <ch12011-7(a)yahoo.com.au> Date: 2012/12/5 Subject: Re: [flashrom] BPv3.6 w flashrom To: "vidwer(a)gmail.com" <vidwer(a)gmail.com> Just had a Eureka moment. I think what confused me was the fact that the cables were soldered onto the actual soic clip! So all I need to do is desolder and resolder them into their correct layouts, or desolder and use alligator clips instead? Is that right? Cheers, Nabs. ------------------------------ * From: * Idwer Vollering <vidwer(a)gmail.com>; * To: * Nabs <ch12011-7(a)yahoo.com.au>; * Cc: * flashrom(a)flashrom.org <flashrom(a)flashrom.org>; * Subject: * Re: [flashrom] BPv3.6 w flashrom * Sent: * Wed, Dec 5, 2012 12:05:04 PM 2012/12/5 Nabs <ch12011-7(a)yahoo.com.au>: > Hi, sorry for the trouble. I'm running bus piratev3.6, bootloaderv4.4, > firmwarev6.1 on flashrom-0.9.6.1, i plan to run the BP at 1M. > > When i run the command "flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -Vr > oldbios.bin" > I get: > " > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on > buspirate_spi. > Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, > id2 0x0 > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE > WRITE > " etc... > > > I think i have the wiring wrong which is why i get that error, i wonder if > you could help me as its my first time? > I'm trying to use In-circuit programming with a soldered bios chip using an > 'SOIC 8 clip' and it has 8 wires. But the bus pirate has 10 pins. > > From another thread, these are the connections i need: > Bus Pirate "MISO" (Pin 1) <----- SPI Device "DO" (Wire/Pin 2) > Bus Pirate "CS" (Pin 2) -----> SPI Device "CS" (Wire/Pin 1) > Bus Pirate "MOSI" (Pin 3) -----> SPI Device "DI" (Wire/Pin 5) > Bus Pirate "CLK" (Pin 4) -----> SPI Device "CLK" (Wire/Pin 6) > Bus Pirate "GND" (Pin 10) <----> SPI Device "GND" (Wire/Pin 4) > > It appears to me that GND is pin 10 and that the wires of the SOIC8 clip > only contact pins 1-8, so how can this work? > > Also, could i just check the layout of the pins on the bus pirate if i'm > reading it correctly on BPv3.6: > 10 9 > 8 7 > 6 5 > 4 3 > 2 1 > > Corresponding to: > GND 3V3 > +5V ADC > VPU AUX > CLK MOSI > CS MISO Forget the existence of +5V, VPU, ADC and AUX for now ( http://dangerousprototypes.com/docs/Bus_Pirate_I/O_Pin_Descriptions ), connect the clip to the buspirate so that the clip passes the buspirate pins like mentioned in this post: http://www.coreboot.org/pipermail/flashrom/2012-November/010178.html This works for me, with a MX25L1605A soic8 chip: CS# (CS) [1 chip 8] VCC (bridge with buspirate pin 3+7) SO (MISO) [2 chip 7] HOLD# (+3V3) WP# (bridge with buspirate pin 7+8) [3 chip 6] SCLK (CLK) GND (GND) [4 chip 5] SI (MOSI) > > Or are the pin numbers read in the opposite direction? > ie > 9 10 > 7 8 > 5 6 > 3 4 > 1 2 > > Here's an image of my bus pirate if it helps: > http://dangerousprototypes.com/wp-content/media/2012/11/Bus-Pirate-v3.6inte… > > Your help is much appreciated and i appreciate your patience, Nabs. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] BPv3.6 w flashrom
by Idwer Vollering 05 Dec '12

05 Dec '12

Please "reply to all". 2012/12/5 Nabil <nabil.gergis(a)yahoo.com.au>: > Sorry there's one thing I'm not sure I understand... > Is it possible to adjust the locations of the wires of the soic clip so they match up with the correct pinouts? > I just dont get how gnd (pin 10 of bus pirate) can be connected to the soic clip (only 8 cables which connect to pins 1-8) > there's something I'm missing here i think, could you explain to me how to use an soic clip in detail, sorry for the trouble, much obliged. Nabs Which soic8 clip do you have? I have a Pomona 5250; it is possible to adjust the wire locations (pinouts) if you have the probe cable (that fits on the open end of the wires - the other end is a box header that connects to the buspirate): http://dangerousprototypes.com/2011/08/03/new-bus-pirate-probe-cable/ > > Idwer Vollering <vidwer(a)gmail.com> wrote: > >>2012/12/5 Nabs <ch12011-7(a)yahoo.com.au>: >>> Hi, sorry for the trouble. I'm running bus piratev3.6, bootloaderv4.4, >>> firmwarev6.1 on flashrom-0.9.6.1, i plan to run the BP at 1M. >>> >>> When i run the command "flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -Vr >>> oldbios.bin" >>> I get: >>> " >>> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on >>> buspirate_spi. >>> Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, >>> id2 0x0 >>> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). >>> === >>> This flash part has status NOT WORKING for operations: PROBE READ ERASE >>> WRITE >>> " etc... >>> >>> >>> I think i have the wiring wrong which is why i get that error, i wonder if >>> you could help me as its my first time? >>> I'm trying to use In-circuit programming with a soldered bios chip using an >>> 'SOIC 8 clip' and it has 8 wires. But the bus pirate has 10 pins. >>> >>> From another thread, these are the connections i need: >>> Bus Pirate "MISO" (Pin 1) <----- SPI Device "DO" (Wire/Pin 2) >>> Bus Pirate "CS" (Pin 2) -----> SPI Device "CS" (Wire/Pin 1) >>> Bus Pirate "MOSI" (Pin 3) -----> SPI Device "DI" (Wire/Pin 5) >>> Bus Pirate "CLK" (Pin 4) -----> SPI Device "CLK" (Wire/Pin 6) >>> Bus Pirate "GND" (Pin 10) <----> SPI Device "GND" (Wire/Pin 4) >>> >>> It appears to me that GND is pin 10 and that the wires of the SOIC8 clip >>> only contact pins 1-8, so how can this work? >>> >>> Also, could i just check the layout of the pins on the bus pirate if i'm >>> reading it correctly on BPv3.6: >>> 10 9 >>> 8 7 >>> 6 5 >>> 4 3 >>> 2 1 >>> >>> Corresponding to: >>> GND 3V3 >>> +5V ADC >>> VPU AUX >>> CLK MOSI >>> CS MISO >> >>Forget the existence of +5V, VPU, ADC and AUX for now ( >>http://dangerousprototypes.com/docs/Bus_Pirate_I/O_Pin_Descriptions ), >>connect the clip to the buspirate so that the clip passes the >>buspirate pins like mentioned in this post: >>http://www.coreboot.org/pipermail/flashrom/2012-November/010178.html >> >>This works for me, with a MX25L1605A soic8 chip: >> >>CS# (CS) [1 chip 8] VCC >>(bridge with buspirate pin 3+7) >>SO (MISO) [2 chip 7] HOLD# (+3V3) >>WP# (bridge with buspirate pin 7+8) [3 chip 6] SCLK (CLK) >>GND (GND) [4 chip 5] SI (MOSI) >> >>> >>> Or are the pin numbers read in the opposite direction? >>> ie >>> 9 10 >>> 7 8 >>> 5 6 >>> 3 4 >>> 1 2 >>> >>> Here's an image of my bus pirate if it helps: >>> http://dangerousprototypes.com/wp-content/media/2012/11/Bus-Pirate-v3.6inte… >>> >>> Your help is much appreciated and i appreciate your patience, Nabs. >>> >>> _______________________________________________ >>> flashrom mailing list >>> flashrom(a)flashrom.org >>> http://www.flashrom.org/mailman/listinfo/flashrom

1 0

BPv3.6 w flashrom
by Nabs 05 Dec '12

05 Dec '12

Hi, sorry for the trouble. I'm running bus piratev3.6, bootloaderv4.4, firmwarev6.1 on flashrom-0.9.6.1, i plan to run the BP at 1M. When i run the command "flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -Vr oldbios.bin" I get: " Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on buspirate_spi. Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, id2 0x0 Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE " etc... I think i have the wiring wrong which is why i get that error, i wonder if you could help me as its my first time? I'm trying to use In-circuit programming with a soldered bios chip using an 'SOIC 8 clip' and it has 8 wires. But the bus pirate has 10 pins. From another thread, these are the connections i need: Bus Pirate "MISO" (Pin 1) <----- SPI Device "DO" (Wire/Pin 2) Bus Pirate "CS" (Pin 2) -----> SPI Device "CS" (Wire/Pin 1) Bus Pirate "MOSI" (Pin 3) -----> SPI Device "DI" (Wire/Pin 5) Bus Pirate "CLK" (Pin 4) -----> SPI Device "CLK" (Wire/Pin 6) Bus Pirate "GND" (Pin 10) <----> SPI Device "GND" (Wire/Pin 4) It appears to me that GND is pin 10 and that the wires of the SOIC8 clip only contact pins 1-8, so how can this work? Also, could i just check the layout of the pins on the bus pirate if i'm reading it correctly on BPv3.6: 10 9 8 7 6 5 4 3 2 1 Corresponding to: GND 3V3 +5V ADC VPU AUX CLK MOSI CS MISO Or are the pin numbers read in the opposite direction? ie 9 10 7 8 5 6 3 4 1 2 Here's an image of my bus pirate if it helps: http://dangerousprototypes.com/wp-content/media/2012/11/Bus-Pirate-v3.6inte… Your help is much appreciated and i appreciate your patience, Nabs.

2 1

Bus Pirate + Flashrom
by Nabs 05 Dec '12

05 Dec '12

Hi, i get the following error below when trying to read a bios chip, what options do i have for troubleshooting and what's causing the problem? Thanks Nabs "flashrom -f -Vr bios.img.bin -p buspirate_spi:dev=/dev/tty8,spispeed=1M" flashrom v0.9.5.2-r1517 on Linux 3.2.0-23-generic (x86_64), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 1372M loops per second, 10 myus = 10 us, 100 myus = 113 us, 1000 myus = 1036 us, 10000 myus = 10346 us, 4 myus = 6 us, OK. Initializing buspirate_spi programmer SPI speed is 1MHz ^[[BEntering raw bitbang mode failed! Got 1c9ce050e0 Error: Programmer initialization failed. ^[[AEntering raw bitbang mode failed!

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom