- flashrom - mail.coreboot.org

Flashing fails with Jetway Board
by Hans-Martin Roßmann 17 Feb '14

17 Feb '14

Hi again, I'd test again with other chips, but it is still not possible to flash with flashrom on my Jetway NC96FL Board. Could somebody help me? Outputs of flashrom -V and so on are attached. Thanks, Hans-Martin

1 0

Re: [flashrom] Flashing fails with SF100
by Idwer Vollering 13 Feb '14

13 Feb '14

2014-02-12 13:34 GMT+01:00 Arun Chandran <achandran(a)mvista.com>: > Hi, > > I am using the latest flashrom. I am unable to flashBIOS using dediprog sf > 100 programmer. > > The log is pasted below. Please help. > ################################################################### > > arun@arun-OptiPlex-9010:~/work/vview/flashrom$ sudo flashrom -p internal -w > BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin -V When you run flashrom like that, you will tell it to write 'BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin' to your optiplex' mainboard flash chip, not to the flash chip connected to your dediprog. (hint: change the target programmer after reading the comment below) Most, if not all, distributions package without compiling in dediprog support. If this is the case, this means that you must compile flashrom with dediprog support yourself. Instructions are found here: http://flashrom.org/Downloads#Installation_from_source

1 0

Flashing fails with SF100
by Arun Chandran 12 Feb '14

12 Feb '14

Hi, I am using the latest flashrom. I am unable to flashBIOS using dediprog sf 100 programmer. The log is pasted below. Please help. ################################################################### arun@arun-OptiPlex-9010:~/work/vview/flashrom$ sudo flashrom -p internal -w BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin -V flashrom v0.9.7-r1764 on Linux 3.5.0-45-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.8, GCC 4.6.3, little endian Command line (5 args): flashrom -p internal -w BYTI_072_011_ReleasePackage/BYTICRB__X64_R_0072_11_SeC_Enable.bin -V Calibrating delay loop... OS timer resolution is 1 usecs, 3881M loops per second, 10 myus = 10 us, 100 myus = 99 us, 1000 myus = 999 us, 10000 myus = 10006 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Mini Tower" DMI string system-manufacturer: "Dell Inc." DMI string system-product-name: "OptiPlex 9010" DMI string system-version: "01" DMI string baseboard-manufacturer: "Dell Inc." DMI string baseboard-product-name: "0M9KCM" DMI string baseboard-version: "A02" Found chipset "Intel Q77" with PCI ID 8086:1e47. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Root Complex Register Block address = 0xfed1c000 GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled 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 enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytesSPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x0a: BIOS Lock Enable: enabled, BIOS Write Enable: disabled Warning: Setting Bios Control at 0xdc from 0x0a to 0x09 failed. New value is 0x0a. SPIBAR = 0x00007f669c2d9000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Warning: SPI Configuration Lockdown activated. Reading OPCODES... done 0x06: 0x3f00 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=63, SME=0 0x50: 0x00000a0b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b 0x54: 0x00000000 FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x0bff0600 FREG1: BIOS region (0x00600000-0x00bfffff) is read-write. 0x5C: 0x05ff0005 FREG2: Warning: Management Engine region (0x00005000-0x005fffff) is locked. 0x60: 0x00040001 FREG3: Gigabit Ethernet region (0x00001000-0x00004fff) is read-write. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see http://flashrom.org/ME for details. Writes have been disabled for safety reasons. You can enforce write support with the ich_spi_force programmer option, but you will most likely harm your hardware! If you force flashrom you will get no support if something breaks. On a few mainboards it is possible to enable write access by setting a jumper (see its documentation or the board itself). 0x90: 0xc0 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0x91: 0xf84030 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=3, DBC=0, SME=0, SCF=0 0x94: 0x0006 (PREOP) 0x96: 0x043b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9C: 0x0000019f (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00802005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x00000800 (FPB) Enabling hardware sequencing due to multiple flash chips detected. PROBLEMS, continuing anyway The following protocols are supported: FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Found 2 attached SPI flash chips with a combined density of 12288 kB. The flash address space (0x000000 - 0xbfffff) is divided at address 0x800000 in two partitions. The first partition ranges from 0x000000 to 0x7fffff. In that range are 2048 erase blocks with 4096 B each. The second partition ranges from 0x800000 to 0xbfffff. In that range are 1024 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific) at physical address 0x0. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content 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 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content 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 Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content 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 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, 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 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 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, 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: 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 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 0xea, id2 0xd0, 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 W39V040FB, 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 W39V040FC, 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 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: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific). Write/erase is not working yet on your programmer in its current configuration. Aborting. Restoring MMIO space at 0x7f669c2dc8a0 Restoring PCI config space for 00:1f:0 reg 0xdc ############################################################## Regards, Arun C

1 0

Re: [flashrom] Motherboard Support Inquiry
by Idwer Vollering 11 Feb '14

11 Feb '14

2014-02-11 9:00 GMT+01:00 Anthony Ross <anthonyross230(a)gmail.com>: > Hello One and all > Well Im new to this mailing list & would like to confirm if flashrom > supports my motherboard. Here is the output of Flashrom & lspci > > user#flashrom -V -p internal > flashrom v0.9.7-r1711 on Linux 3.5.0-23-generic (i686) > flashrom is free software, get the source code at http://www.flashrom.org > > flashrom was built with libpci 3.1.8, GCC 4.4.7, little endian > Command line (3 args): flashrom -V -p internal > Calibrating delay loop... OS timer resolution is 1 usecs, 1725M loops > per second, delay more than 10% too short (got 89% of expected delay), > recalculating... 1702M loops per second, delay more than 10% too short > (got 87% of expected delay), recalculating... 1827M loops per second, 10 > myus = 9 us, 100 myus = 93 us, 1000 myus = 930 us, 10000 myus = 9310 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: "Intel Corporation" > DMI string baseboard-product-name: "D945GCCR" > DMI string baseboard-version: "AAD78647-304" > DMI string chassis-type: "Desktop" > Found ITE Super I/O, ID 0x8603 on port 0x2e > Found chipset "Intel ICH7/ICH7R" with PCI ID 8086:27b8. Enabling flash > write... > 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 disabled > 0xffe00000/0xffa00000 FWH decode disabled > 0xffd80000/0xff980000 FWH decode disabled > 0xffd00000/0xff900000 FWH decode disabled > 0xffc80000/0xff880000 FWH decode disabled > 0xffc00000/0xff800000 FWH decode disabled > 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_CNTL = 0x02: BIOS Lock Enable: enabled, BIOS Write Enable: disabled > Warning: Setting Bios Control at 0xdc from 0x02 to 0x03 on ICH7/ICH7R > failed. This is/could be blocking. > New value is 0x02. > Root Complex Register Block address = 0xfed1c000 > GCS = 0x50444: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x1 > (SPI) > Top Swap : not enabled > SPIBAR = 0xfed1c000 + 0x3020 > 0x00: 0x0004 (SPIS) > 0x02: 0x4004 (SPIC) > 0x04: 0x00000000 (SPIA) > 0x08: 0x00000000 (SPID0) > 0x0c: 0x00000000 (SPID0+4) > 0x10: 0x00000000 (SPID1) > 0x14: 0x00000000 (SPID1+4) > 0x18: 0x00000000 (SPID2) > 0x1c: 0x00000000 (SPID2+4) > 0x20: 0x00000000 (SPID3) > 0x24: 0x00000000 (SPID3+4) > 0x28: 0x00000000 (SPID4) > 0x2c: 0x00000000 (SPID4+4) > 0x30: 0x00000000 (SPID5) > 0x34: 0x00000000 (SPID5+4) > 0x38: 0x00000000 (SPID6) > 0x3c: 0x00000000 (SPID6+4) > 0x40: 0x00000000 (SPID7) > 0x44: 0x00000000 (SPID7+4) > 0x50: 0x00f80000 (BBAR) > 0x54: 0x0004 (PREOP) > 0x56: 0x0000 (OPTYPE) > 0x58: 0x00000005 (OPMENU) > 0x5c: 0x00000000 (OPMENU+4) > 0x60: 0x00000000 (PBR0) > 0x64: 0x00000000 (PBR1) > 0x68: 0x00000000 (PBR2) > Programming OPCODES... done > SPI Read Configuration: prefetching disabled, caching enabled, PROBLEMS, > continuing anyway This too. > Super I/O ID 0x8603 is not on the list of flash capable controllers. > The following protocols are supported: SPI. > Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff > Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Macronix MX25L2005(C), 256 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L4005(A/C), 512 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L8005/MX25V8005, 1024 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Macronix MX25L3206E, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L6405(D), 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Macronix MX25L6445E, 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25L12805(D), 16384 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. > Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of > RDID. > Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour > of RDID. > Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour > of RDID. > Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res3: id1 0x1212, id2 0x12 > Probing for PMC Pm25LV010, 128 kB: probe_spi_res3: id1 0x1212, id2 0x12 > Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x12, id2 0x12 > Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x12, id2 0x12 > Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x12, id2 0x12 > Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Spansion S25FL116K/S25FL216K, 2048 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x12, id2 0x12 > Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x12, id2 0x12 > Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xef, id2 0x12 > Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xef, id2 0x12 > Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xef, id2 0x12 > Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 > 0x3013 > Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Found Winbond flash chip "W25X40" (512 kB, SPI) at physical address > 0xfff80000. This is good. While fully erasing/writing the chip might not work, you can use an external SPI programmer and test clips like Pomona 5250 to erase/write to the flash chip when the board is powered off. You need a second machine/laptop to do this. > Chip status register is 0x00. > Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xef, > id2 0x3013 > Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. > Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Macronix unknown Macronix SPI chip, 0 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 > 0xef, id2 0x3013 > Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: > id1 0xef, id2 0x3013 > Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Generic unknown SPI chip (RDID), 0 kB: > probe_spi_rdid_generic: id1 0xef, id2 0x3013 > Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 > 0xef, id2 0x12 > Found Winbond flash chip "W25X40" (512 kB, SPI). > No operations were specified. > Restoring MMIO space at 0xb76fd070 > Restoring MMIO space at 0xb76fd07c > Restoring MMIO space at 0xb76fd078 > Restoring MMIO space at 0xb76fd076 > Restoring MMIO space at 0xb76fd074 > Restoring PCI config space for 00:1f:0 reg 0xdc > > user#lspci -vnn > 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory > Controller Hub [8086:2770] (rev 02) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, fast devsel, latency 0 > Capabilities: [e0] Vendor Specific Information: Len=09 <?> > Kernel driver in use: agpgart-intel > > 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ > Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA > controller]) > Subsystem: Intel Corporation Intel Desktop Board D945GCCR [8086:d605] > Flags: bus master, fast devsel, latency 0, IRQ 16 > Memory at 90100000 (32-bit, non-prefetchable) [size=512K] > I/O ports at 20e0 [size=8] > Memory at 80000000 (32-bit, prefetchable) [size=256M] > Memory at 90180000 (32-bit, non-prefetchable) [size=256K] > Expansion ROM at <unassigned> [disabled] > Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- > Capabilities: [d0] Power Management version 2 > Kernel driver in use: i915 > Kernel modules: intelfb, i915 > > 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High > Definition Audio Controller [8086:27d8] (rev 01) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, fast devsel, latency 0, IRQ 43 > Memory at 901c0000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [50] Power Management version 2 > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 > Capabilities: [100] Virtual Channel > Capabilities: [130] Root Complex Link > Kernel driver in use: snd_hda_intel > Kernel modules: snd-hda-intel > > 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI > Express Port 1 [8086:27d0] (rev 01) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > I/O behind bridge: 00003000-00003fff > Memory behind bridge: f8000000-f81fffff > Prefetchable memory behind bridge: 00000000f8200000-00000000f83fffff > Capabilities: [40] Express Root Port (Slot+), MSI 00 > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [90] Subsystem: Intel Corporation NM10/ICH7 Family PCI > Express Port 1 [8086:27d0] > Capabilities: [a0] Power Management version 2 > Capabilities: [100] Virtual Channel > Capabilities: [180] Root Complex Link > Kernel driver in use: pcieport > Kernel modules: shpchp > > 00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI > Express Port 3 [8086:27d4] (rev 01) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 > I/O behind bridge: 00004000-00004fff > Memory behind bridge: f8400000-f85fffff > Prefetchable memory behind bridge: 00000000f8600000-00000000f87fffff > Capabilities: [40] Express Root Port (Slot+), MSI 00 > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [90] Subsystem: Intel Corporation NM10/ICH7 Family PCI > Express Port 3 [8086:27d4] > Capabilities: [a0] Power Management version 2 > Capabilities: [100] Virtual Channel > Capabilities: [180] Root Complex Link > Kernel driver in use: pcieport > Kernel modules: shpchp > > 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI > Express Port 4 [8086:27d6] (rev 01) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 > I/O behind bridge: 00005000-00005fff > Memory behind bridge: f8800000-f89fffff > Prefetchable memory behind bridge: 00000000f8a00000-00000000f8bfffff > Capabilities: [40] Express Root Port (Slot+), MSI 00 > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [90] Subsystem: Intel Corporation NM10/ICH7 Family PCI > Express Port 4 [8086:27d6] > Capabilities: [a0] Power Management version 2 > Capabilities: [100] Virtual Channel > Capabilities: [180] Root Complex Link > Kernel driver in use: pcieport > Kernel modules: shpchp > > 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB > UHCI Controller #1 [8086:27c8] (rev 01) (prog-if 00 [UHCI]) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 0, IRQ 23 > I/O ports at 2080 [size=32] > Kernel driver in use: uhci_hcd > > 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB > UHCI Controller #2 [8086:27c9] (rev 01) (prog-if 00 [UHCI]) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 0, IRQ 19 > I/O ports at 2060 [size=32] > Kernel driver in use: uhci_hcd > > 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB > UHCI Controller #3 [8086:27ca] (rev 01) (prog-if 00 [UHCI]) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 0, IRQ 18 > I/O ports at 2040 [size=32] > Kernel driver in use: uhci_hcd > > 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB > UHCI Controller #4 [8086:27cb] (rev 01) (prog-if 00 [UHCI]) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 0, IRQ 16 > I/O ports at 2020 [size=32] > Kernel driver in use: uhci_hcd > > 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 > EHCI Controller [8086:27cc] (rev 01) (prog-if 20 [EHCI]) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 0, IRQ 23 > Memory at 901c4000 (32-bit, non-prefetchable) [size=1K] > Capabilities: [50] Power Management version 2 > Capabilities: [58] Debug port: BAR=1 offset=00a0 > Kernel driver in use: ehci_hcd > > 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge > [8086:244e] (rev e1) (prog-if 01 [Subtractive decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=04, subordinate=04, sec-latency=32 > I/O behind bridge: 00001000-00001fff > Memory behind bridge: 90000000-900fffff > Capabilities: [50] Subsystem: Intel Corporation Device [8086:d605] > > 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) > LPC Interface Bridge [8086:27b8] (rev 01) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 0 > Capabilities: [e0] Vendor Specific Information: Len=0c <?> > Kernel driver in use: lpc_ich > Kernel modules: leds-ss4200, lpc_ich, intel-rng > > 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE > Controller [8086:27df] (rev 01) (prog-if 8a [Master SecP PriP]) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 0, IRQ 18 > I/O ports at 01f0 [size=8] > I/O ports at 03f4 [size=1] > I/O ports at 0170 [size=8] > I/O ports at 0374 [size=1] > I/O ports at 20b0 [size=16] > Kernel driver in use: ata_piix > > 00:1f.2 IDE interface [0101]: Intel Corporation NM10/ICH7 Family SATA > Controller [IDE mode] [8086:27c0] (rev 01) (prog-if 8f [Master SecP SecO > PriP PriO]) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19 > I/O ports at 20c8 [size=8] > I/O ports at 20ec [size=4] > I/O ports at 20c0 [size=8] > I/O ports at 20e8 [size=4] > I/O ports at 20a0 [size=16] > Capabilities: [70] Power Management version 2 > Kernel driver in use: ata_piix > > 00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus > Controller [8086:27da] (rev 01) > Subsystem: Intel Corporation Device [8086:d605] > Flags: medium devsel, IRQ 11 > I/O ports at 2000 [size=32] > Kernel modules: i2c-i801 > > 04:08.0 Ethernet controller [0200]: Intel Corporation PRO/100 VE Network > Connection [8086:1094] (rev 01) > Subsystem: Intel Corporation Device [8086:d605] > Flags: bus master, medium devsel, latency 32, IRQ 20 > Memory at 90000000 (32-bit, non-prefetchable) [size=4K] > I/O ports at 1000 [size=64] > Capabilities: [dc] Power Management version 2 > Kernel driver in use: e100 > Kernel modules: e100 > > Well since my EEPROM chip is quite small and is permanently fixed > (non-dettachable) could there be a setup of a Virtual EEPROM? I dont > know if this would be right but if so I would be eager to know if there > could be any workarounds on that > > Best Regards > > Fred > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Motherboard Support Inquiry
by Anthony Ross 11 Feb '14

11 Feb '14

Hello One and all Well Im new to this mailing list & would like to confirm if flashrom supports my motherboard. Here is the output of Flashrom & lspci user#flashrom -V -p internal flashrom v0.9.7-r1711 on Linux 3.5.0-23-generic (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.8, GCC 4.4.7, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 1725M loops per second, delay more than 10% too short (got 89% of expected delay), recalculating... 1702M loops per second, delay more than 10% too short (got 87% of expected delay), recalculating... 1827M loops per second, 10 myus = 9 us, 100 myus = 93 us, 1000 myus = 930 us, 10000 myus = 9310 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: "Intel Corporation" DMI string baseboard-product-name: "D945GCCR" DMI string baseboard-version: "AAD78647-304" DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8603 on port 0x2e Found chipset "Intel ICH7/ICH7R" with PCI ID 8086:27b8. Enabling flash write... 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 disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 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_CNTL = 0x02: BIOS Lock Enable: enabled, BIOS Write Enable: disabled Warning: Setting Bios Control at 0xdc from 0x02 to 0x03 on ICH7/ICH7R failed. New value is 0x02. Root Complex Register Block address = 0xfed1c000 GCS = 0x50444: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3020 0x00: 0x0004 (SPIS) 0x02: 0x4004 (SPIC) 0x04: 0x00000000 (SPIA) 0x08: 0x00000000 (SPID0) 0x0c: 0x00000000 (SPID0+4) 0x10: 0x00000000 (SPID1) 0x14: 0x00000000 (SPID1+4) 0x18: 0x00000000 (SPID2) 0x1c: 0x00000000 (SPID2+4) 0x20: 0x00000000 (SPID3) 0x24: 0x00000000 (SPID3+4) 0x28: 0x00000000 (SPID4) 0x2c: 0x00000000 (SPID4+4) 0x30: 0x00000000 (SPID5) 0x34: 0x00000000 (SPID5+4) 0x38: 0x00000000 (SPID6) 0x3c: 0x00000000 (SPID6+4) 0x40: 0x00000000 (SPID7) 0x44: 0x00000000 (SPID7+4) 0x50: 0x00f80000 (BBAR) 0x54: 0x0004 (PREOP) 0x56: 0x0000 (OPTYPE) 0x58: 0x00000005 (OPMENU) 0x5c: 0x00000000 (OPMENU+4) 0x60: 0x00000000 (PBR0) 0x64: 0x00000000 (PBR1) 0x68: 0x00000000 (PBR2) Programming OPCODES... done SPI Read Configuration: prefetching disabled, caching enabled, PROBLEMS, continuing anyway Super I/O ID 0x8603 is not on the list of flash capable controllers. The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L2005(C), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L4005(A/C), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L8005/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L3206E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L6405(D), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L6445E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25L12805(D), 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res3: id1 0x1212, id2 0x12 Probing for PMC Pm25LV010, 128 kB: probe_spi_res3: id1 0x1212, id2 0x12 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x12, id2 0x12 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x12, id2 0x12 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x12, id2 0x12 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x12, id2 0x12 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x12, id2 0x12 Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xef, id2 0x12 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xef, id2 0x12 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xef, id2 0x12 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Found Winbond flash chip "W25X40" (512 kB, SPI) at physical address 0xfff80000. Chip status register is 0x00. Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3013 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x12 Found Winbond flash chip "W25X40" (512 kB, SPI). No operations were specified. Restoring MMIO space at 0xb76fd070 Restoring MMIO space at 0xb76fd07c Restoring MMIO space at 0xb76fd078 Restoring MMIO space at 0xb76fd076 Restoring MMIO space at 0xb76fd074 Restoring PCI config space for 00:1f:0 reg 0xdc user#lspci -vnn 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=09 <?> Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Intel Desktop Board D945GCCR [8086:d605] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 90100000 (32-bit, non-prefetchable) [size=512K] I/O ports at 20e0 [size=8] Memory at 80000000 (32-bit, prefetchable) [size=256M] Memory at 90180000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Kernel driver in use: i915 Kernel modules: intelfb, i915 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at 901c0000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: f8000000-f81fffff Prefetchable memory behind bridge: 00000000f8200000-00000000f83fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 3 [8086:27d4] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00004000-00004fff Memory behind bridge: f8400000-f85fffff Prefetchable memory behind bridge: 00000000f8600000-00000000f87fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Intel Corporation NM10/ICH7 Family PCI Express Port 3 [8086:27d4] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 4 [8086:27d6] (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 00005000-00005fff Memory behind bridge: f8800000-f89fffff Prefetchable memory behind bridge: 00000000f8a00000-00000000f8bfffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Intel Corporation NM10/ICH7 Family PCI Express Port 4 [8086:27d6] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Root Complex Link Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 01) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 0, IRQ 23 I/O ports at 2080 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 01) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 0, IRQ 19 I/O ports at 2060 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 01) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 2040 [size=32] Kernel driver in use: uhci_hcd 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 01) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at 2020 [size=32] Kernel driver in use: uhci_hcd 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 01) (prog-if 20 [EHCI]) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at 901c4000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1) (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=32 I/O behind bridge: 00001000-00001fff Memory behind bridge: 90000000-900fffff Capabilities: [50] Subsystem: Intel Corporation Device [8086:d605] 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> Kernel driver in use: lpc_ich Kernel modules: leds-ss4200, lpc_ich, intel-rng 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 01f0 [size=8] I/O ports at 03f4 [size=1] I/O ports at 0170 [size=8] I/O ports at 0374 [size=1] I/O ports at 20b0 [size=16] Kernel driver in use: ata_piix 00:1f.2 IDE interface [0101]: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] [8086:27c0] (rev 01) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19 I/O ports at 20c8 [size=8] I/O ports at 20ec [size=4] I/O ports at 20c0 [size=8] I/O ports at 20e8 [size=4] I/O ports at 20a0 [size=16] Capabilities: [70] Power Management version 2 Kernel driver in use: ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller [8086:27da] (rev 01) Subsystem: Intel Corporation Device [8086:d605] Flags: medium devsel, IRQ 11 I/O ports at 2000 [size=32] Kernel modules: i2c-i801 04:08.0 Ethernet controller [0200]: Intel Corporation PRO/100 VE Network Connection [8086:1094] (rev 01) Subsystem: Intel Corporation Device [8086:d605] Flags: bus master, medium devsel, latency 32, IRQ 20 Memory at 90000000 (32-bit, non-prefetchable) [size=4K] I/O ports at 1000 [size=64] Capabilities: [dc] Power Management version 2 Kernel driver in use: e100 Kernel modules: e100 Well since my EEPROM chip is quite small and is permanently fixed (non-dettachable) could there be a setup of a Virtual EEPROM? I dont know if this would be right but if so I would be eager to know if there could be any workarounds on that Best Regards Fred

1 0

ZOTAC IONITX-A-E: flashrom -V
by Maciej Wroniecki 09 Feb '14

09 Feb '14

Read and write works great on this motherboard - THANKS! flashrom v0.9.7-r1711 on Linux 3.2.0-23-generic (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.8, GCC 4.6.3, little endian Command line (3 args): flashrom -V --programmer internal Calibrating delay loop... OS timer resolution is 1 usecs, 647M loops per second, 10 myus = 10 us, 100 myus = 98 us, 1000 myus = 971 us, 10000 myus = 9881 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "To Be Filled By O.E.M." DMI string system-product-name: "To Be Filled By O.E.M." DMI string system-version: "To Be Filled By O.E.M." DMI string baseboard-manufacturer: "To be filled by O.E.M." DMI string baseboard-product-name: "To be filled by O.E.M." DMI string baseboard-version: "To be filled by O.E.M." DMI string chassis-type: "Desktop" Found chipset "NVIDIA MCP79" with PCI ID 10de:0aad. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... This chipset is not really supported yet. Guesswork... ISA/LPC bridge reg 0x8a contents: 0x40, bit 6 is 1, bit 5 is 0 Flash bus type is SPI SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! Found SMBus device 10de:0aa2 at 00:03:2 MCP SPI BAR is at 0xfae80000 SPI control is 0xc052, req=0, gnt=0 Please send the output of "flashrom -V" to flashrom(a)flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L2005(C), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L4005(A/C), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L8005/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L3206E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L6405(D), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L6445E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L12805(D), 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res3: id1 0x1313, id2 0x13 Probing for PMC Pm25LV010, 128 kB: probe_spi_res3: id1 0x1313, id2 0x13 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xef, id2 0x13 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xef, id2 0x13 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xef, id2 0x13 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Found Winbond flash chip "W25X80" (1024 kB, SPI) at physical address 0xfff00000. Chip status register is 0x00. Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x13 Found Winbond flash chip "W25X80" (1024 kB, SPI). No operations were specified.

1 0

Re: [flashrom] [PATCH] Bus Pirate UART speedup.
by Idwer Vollering 08 Feb '14

08 Feb '14

2013-04-01 18:49 GMT+02:00 Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at>: > Increase PIC/FT232 UART speed to 2 Mbaud (instead of 115200 baud) in > firmware 5.5 and newer. Given that UART speed is the biggest bottleneck > for Bus Pirate communication (right now 90% of the read time is caused > by slow BP<->host communication), this patch is absolutely needed to get > any decent speed out of the Bus Pirate. > > WARNING: This patch may hang flashrom or corrupt data for any non-v3 Bus > Pirate model. I haven't tested such models, and it might work without > problems. Who knows. We would have to find someone with a v2 (or > earlier) Bus Pirate and a firmware version >=v5.5 to test this. For Bus > Pirate model v4 this patch may be completely superfluous. Anyway, > activating fast UART only for some models is probably the way to go. We > already have code to determine the hardware model in the init function, > this just needs to be stored in some variable. I've applied this patch but it doesn't use 2Mbaud on my buspirate v3.a with firmware v6.3-beta1 r2088 or v6.3-beta1 r2151, nor will it proceed to probing. Platforms used are linux and windows. flashrom v0.9.7-r1764 on Linux 3.10-3-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian Command line (5 args): ./flashrom -VVV -p buspirate_spi:dev=/dev/ttyUSB0 -r buspirate_read.bin Calibrating delay loop... OS timer resolution is 1 usecs, 945M loops per second, 10 myus = 12 us, 100 myus = 119 us, 1000 myus = 1187 us, 10000 myus = 11863 us, 4 myus = 5 us, OK. Initializing buspirate_spi programmer Baud rate is 115200 now. buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 1, read 0 Sending 0x00 buspirate_sendrecv: write 0, read 4 , receiving 0x42 0x42 0x49 0x4f buspirate_sendrecv: write 1, read 0 Sending 0x0f buspirate_sendrecv: write 0, read 6 , receiving 0x31 0x01 0x0d 0x0a 0x42 0x75 buspirate_sendrecv: write 0, read 1 , receiving 0x73 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x50 buspirate_sendrecv: write 0, read 1 , receiving 0x69 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x76 buspirate_sendrecv: write 0, read 1 , receiving 0x33 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x0d Detected Bus Pirate hardware v3.a buspirate_sendrecv: write 0, read 8 , receiving 0x0a 0x46 0x69 0x72 0x6d 0x77 0x61 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x76 buspirate_sendrecv: write 0, read 1 , receiving 0x36 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x33 buspirate_sendrecv: write 0, read 1 , receiving 0x2d buspirate_sendrecv: write 0, read 1 , receiving 0x62 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x20 Detected Bus Pirate firmware 6.3 ("v6.3-beta1") buspirate_sendrecv: write 0, read 4 , receiving 0x72 0x32 0x30 0x38 buspirate_sendrecv: write 0, read 1 , receiving 0x38 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x42 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x6c buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x64 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x76 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x44 buspirate_sendrecv: write 0, read 1 , receiving 0x45 buspirate_sendrecv: write 0, read 1 , receiving 0x56 buspirate_sendrecv: write 0, read 1 , receiving 0x49 buspirate_sendrecv: write 0, read 1 , receiving 0x44 buspirate_sendrecv: write 0, read 1 , receiving 0x3a buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x78 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x37 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x52 buspirate_sendrecv: write 0, read 1 , receiving 0x45 buspirate_sendrecv: write 0, read 1 , receiving 0x56 buspirate_sendrecv: write 0, read 1 , receiving 0x49 buspirate_sendrecv: write 0, read 1 , receiving 0x44 buspirate_sendrecv: write 0, read 1 , receiving 0x3a buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x78 buspirate_sendrecv: write 0, read 1 , receiving 0x33 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x36 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x28 buspirate_sendrecv: write 0, read 1 , receiving 0x32 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x46 buspirate_sendrecv: write 0, read 1 , receiving 0x4a buspirate_sendrecv: write 0, read 1 , receiving 0x36 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x47 buspirate_sendrecv: write 0, read 1 , receiving 0x41 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x32 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x42 buspirate_sendrecv: write 0, read 1 , receiving 0x38 buspirate_sendrecv: write 0, read 1 , receiving 0x29 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x68 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x70 buspirate_sendrecv: write 0, read 1 , receiving 0x3a buspirate_sendrecv: write 0, read 1 , receiving 0x2f buspirate_sendrecv: write 0, read 1 , receiving 0x2f buspirate_sendrecv: write 0, read 1 , receiving 0x64 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x6e buspirate_sendrecv: write 0, read 1 , receiving 0x67 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x75 buspirate_sendrecv: write 0, read 1 , receiving 0x73 buspirate_sendrecv: write 0, read 1 , receiving 0x70 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x79 buspirate_sendrecv: write 0, read 1 , receiving 0x70 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x73 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x63 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x6d buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x48 buspirate_sendrecv: write 0, read 1 , receiving 0x69 buspirate_sendrecv: write 0, read 1 , receiving 0x5a buspirate_sendrecv: write 0, read 1 , receiving 0x3e Using SPI command set v2. buspirate_sendrecv: write 2, read 0 Sending 0x62 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x62 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x53 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x73 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x69 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x6c buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x70 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x73 buspirate_sendrecv: write 0, read 1 , receiving 0x70 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x64 buspirate_sendrecv: write 0, read 1 , receiving 0x3a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x28 buspirate_sendrecv: write 0, read 1 , receiving 0x62 buspirate_sendrecv: write 0, read 1 , receiving 0x70 buspirate_sendrecv: write 0, read 1 , receiving 0x73 buspirate_sendrecv: write 0, read 1 , receiving 0x29 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x33 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x32 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x32 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x33 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x32 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x38 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x35 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x39 buspirate_sendrecv: write 0, read 1 , receiving 0x36 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x36 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x39 buspirate_sendrecv: write 0, read 1 , receiving 0x32 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x37 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x33 buspirate_sendrecv: write 0, read 1 , receiving 0x38 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x38 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x35 buspirate_sendrecv: write 0, read 1 , receiving 0x37 buspirate_sendrecv: write 0, read 1 , receiving 0x36 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x39 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x35 buspirate_sendrecv: write 0, read 1 , receiving 0x32 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x2e buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x42 buspirate_sendrecv: write 0, read 1 , receiving 0x52 buspirate_sendrecv: write 0, read 1 , receiving 0x47 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x77 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x76 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x6c buspirate_sendrecv: write 0, read 1 , receiving 0x75 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x28 buspirate_sendrecv: write 0, read 1 , receiving 0x39 buspirate_sendrecv: write 0, read 1 , receiving 0x29 buspirate_sendrecv: write 0, read 1 , receiving 0x3e buspirate_sendrecv: write 3, read 0 Sending 0x31 0x30 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x31 buspirate_sendrecv: write 0, read 1 , receiving 0x30 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x45 buspirate_sendrecv: write 0, read 1 , receiving 0x6e buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x77 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x76 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x6c buspirate_sendrecv: write 0, read 1 , receiving 0x75 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x66 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x42 buspirate_sendrecv: write 0, read 1 , receiving 0x52 buspirate_sendrecv: write 0, read 1 , receiving 0x47 buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x28 buspirate_sendrecv: write 0, read 1 , receiving 0x33 buspirate_sendrecv: write 0, read 1 , receiving 0x34 buspirate_sendrecv: write 0, read 1 , receiving 0x29 buspirate_sendrecv: write 0, read 1 , receiving 0x3e buspirate_sendrecv: write 2, read 0 Sending 0x31 0x0a Baud rate is 115200 now. buspirate_sendrecv: write 1, read 0 Sending 0x20 buspirate_sendrecv: write 0, read 4 , receiving 0x31 0x0d 0x0a 0x41 buspirate_sendrecv: write 0, read 1 , receiving 0x64 buspirate_sendrecv: write 0, read 1 , receiving 0x6a buspirate_sendrecv: write 0, read 1 , receiving 0x75 buspirate_sendrecv: write 0, read 1 , receiving 0x73 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x79 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x75 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x72 buspirate_sendrecv: write 0, read 1 , receiving 0x6d buspirate_sendrecv: write 0, read 1 , receiving 0x69 buspirate_sendrecv: write 0, read 1 , receiving 0x6e buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x6c buspirate_sendrecv: write 0, read 1 , receiving 0x0d buspirate_sendrecv: write 0, read 1 , receiving 0x0a buspirate_sendrecv: write 0, read 1 , receiving 0x53 buspirate_sendrecv: write 0, read 1 , receiving 0x70 buspirate_sendrecv: write 0, read 1 , receiving 0x61 buspirate_sendrecv: write 0, read 1 , receiving 0x63 buspirate_sendrecv: write 0, read 1 , receiving 0x65 buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x20 buspirate_sendrecv: write 0, read 1 , receiving 0x63 buspirate_sendrecv: write 0, read 1 , receiving 0x6f buspirate_sendrecv: write 0, read 1 , receiving 0x6e buspirate_sendrecv: write 0, read 1 , receiving 0x74 buspirate_sendrecv: write 0, read 1 , receiving 0x69 buspirate_sendrecv: write 0, read 1 > > Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> > --- > buspirate_spi.c | 44 +++++++++++++++++++++++++++++++++++++++++++- > 1 file changed, 43 insertions(+), 1 deletion(-) > > diff --git a/buspirate_spi.c b/buspirate_spi.c > index d2ebc75..57da63a 100644 > --- a/buspirate_spi.c > +++ b/buspirate_spi.c > @@ -178,7 +178,10 @@ static int buspirate_spi_shutdown(void *data) > } > /* Reset Bus Pirate (return to user terminal) */ > bp_commbuf[0] = 0x0f; > - ret = buspirate_sendrecv(bp_commbuf, 1, 0); > + if ((ret = buspirate_sendrecv(bp_commbuf, 1, 0))) > + goto out_shutdown; > + if ((ret = serialport_config(sp_fd, 115200))) > + goto out_shutdown; > > out_shutdown: > /* Shut down serial port communication */ > @@ -365,6 +368,45 @@ int buspirate_spi_init(void) > spi_programmer_buspirate.command = buspirate_spi_send_command_v1; > } > > + /* Increase PIC/FT232 UART speed to 2 Mbaud (instead of 115200 baud) in firmware 5.5 and newer. Where is the firmware able to increase UART speed when/while 115200 is the highest speed documented? See https://code.google.com/p/dangerous-prototypes-open-hardware/source/browse/… > + * Although this is already possible in firmware 5.2, fast UART in combination with the old SPI > + * command set causes hangs for bigger transactions. This is caused by a UART buffer overrun > + * in the PIC, and all firmware versions up to (hopefully not including) 6.2 are affected. > + */ > + if (BP_FWVERSION(fw_version_major, fw_version_minor) >= BP_FWVERSION(5, 5)) { > + // FIXME: Do this only for USB-based Bus Pirates... unless you're sure the UART can handle more. > + int cmdlen; > + /* Request setting the UART baud rate. */ > + cmdlen = snprintf((char *)bp_commbuf, DEFAULT_BUFSIZE, "b\n"); > + if ((ret = buspirate_sendrecv(bp_commbuf, cmdlen, 0))) > + return ret; > + if ((ret = buspirate_wait_for_string(bp_commbuf, ">"))) > + return ret; > + /* Request setting the UART clock divisor manually. */ > + cmdlen = snprintf((char *)bp_commbuf, DEFAULT_BUFSIZE, "10\n"); > + if ((ret = buspirate_sendrecv(bp_commbuf, cmdlen, 0))) > + return ret; > + if ((ret = buspirate_wait_for_string(bp_commbuf, ">"))) > + return ret; > + /* Set the UART clock divisor. New clock is 4000000/(divisor+1). */ > + cmdlen = snprintf((char *)bp_commbuf, DEFAULT_BUFSIZE, "%i\n", 1); > + if ((ret = buspirate_sendrecv(bp_commbuf, cmdlen, 0))) > + return ret; > + sleep(1); > + if (serialport_config(sp_fd, 115200) != 0) > + return 1; > + bp_commbuf[0] = ' '; > + if ((ret = buspirate_sendrecv(bp_commbuf, 1, 0))) > + return ret; > + if ((ret = buspirate_wait_for_string(bp_commbuf, "HiZ>"))) > + return ret; > + msg_pdbg("Using fast 2 Mbaud for Bus Pirate <-> host communication.\n"); > + } else { > + msg_pinfo("Bus Pirate firmware 5.4 and older does not support fast Bus Pirate <-> host " > + "communication. Limiting UART speed to 115200 Baud.\n"); > + msg_pinfo("It is recommended to upgrade to firmware 6.2 or newer.\n"); > + } > + > /* Workaround for broken speed settings in firmware 6.1 and older. */ > if (BP_FWVERSION(fw_version_major, fw_version_minor) < BP_FWVERSION(6, 2)) > if (spispeed > 0x4) { > -- > Kind regards, Stefan Tauner > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] [PATCH] nicintel_eeprom: New programmer for Intel Nics eeproms
by Ricardo Ribalda Delgado 06 Feb '14

06 Feb '14

ping? On Mon, Dec 2, 2013 at 4:45 PM, Ricardo Ribalda Delgado < ricardo.ribalda(a)gmail.com> wrote: > Hello > > Is there any status change here? There are other people using this patch. > > http://www.projectosx.com/forum/index.php?showtopic=2485&st=20&start=20 > > Thanks! > > > On Thu, Sep 12, 2013 at 1:26 PM, Ricardo Ribalda Delgado > <ricardo.ribalda(a)gmail.com> wrote: > > Hello Stefan > > > > On Thu, Sep 12, 2013 at 12:08 PM, Stefan Tauner > > <stefan.tauner(a)student.tuwien.ac.at> wrote: > >> On Thu, 12 Sep 2013 11:25:39 +0200 > >> Ricardo Ribalda Delgado <ricardo.ribalda(a)gmail.com> wrote: > >> > >>> ping? > >> > >> Hi Ricardo, > >> > >> I would have hoped for a more generic patch that adds some > >> eeprom-specific infrastructure, but your approach seems to be legit > >> when implementing this with the current infrastructure in flashrom. > >> Sorry for not mentioning the opaque API before, that is of course the > >> easiest way to get such things to work. > > > > I thought about it, but I soon realized that it was probably not the > > best option. > > > > The intel cards supports a limited ammount of chips, and the > > read/write is not very standard. They are read by the card firmware, > > but written with something spi_alike, but no jedec or anything to find > > out the model of the eeprom. > > > >> > >> Would it be even possible to probe for IDs of the EEPROMs with the > >> interface on the Intel NICs? What EEPROM model(s) do see on your boards? > > > > You can ask the network card for the size of the eeprom. That is done > > in nicintel_ee_probe > > > > According to the doc this eeproms can be used: > > > > 128 AT25128AN-10SI-2.7 M95128WMN6T CAT25CS128-TE13 > > 256 AT25256AN-10SI-2.7 M95256WMN6T > > > > All of them have the same instruction set. And unfortunately there is > > no id instruction > > > > So, if the board is an intel card and it says that the size is 128 > > kbits, then it is a chip from the first row, otherwise it is from the > > second > > > >> > >> I have not reviewed your patch in detail yet. There are probably a few > >> coding style issues etc., but we can fix that ourselves if we have to. > > > > I could not find a coding style, so I tried to stick to the kernel one. > > > >> The bigger question is if we want to add something like it at all. I > >> don't see good reason why we should not, but I need to discuss this > >> with my colleague(s) (and that usually takes more time than one would > >> expect). In any case your code is out there and can be used even if it > >> does not get merged into vanilla flashrom eventually and your work is > >> much appreciated, thank you. > > > > That was the whole point, that this could be reused by somebody else. > > And the program more standard up to date is yours :) > > > > Thaks! > > > > > >> -- > >> Kind regards/Mit freundlichen Grüßen, Stefan Tauner > > > > > > > > -- > > Ricardo Ribalda > > > > -- > Ricardo Ribalda > -- Ricardo Ribalda

1 0

Re: [flashrom] Foxconn NT-510: flashrom doesn't find anything
by Daniel Lenski 06 Feb '14

06 Feb '14

On Wed, Feb 5, 2014 at 10:59 PM, Daniel Lenski <dlenski(a)gmail.com> wrote: > Hello, > I have a Flashrom NT-510 nettop (Intel Atom D510, ICH7/NM10 chipset). > Flashrom doesn't find any chip while probing. Complete output of > sensors-detect and flashrom -V here: > http://paste.flashrom.org/view.php?id=1966 A little more info... According to the BIOS docs I found on Foxconn's site, it's an AMI BIOS with an 8 MB SPI flash chip. The part on the motherboard is a square surface-mount IC labeled "AMI BIOS" etc but with no part information labeled that I can see.

1 0

Foxconn NT-510: flashrom doesn't find anything
by Daniel Lenski 06 Feb '14

06 Feb '14

Hello, I have a Flashrom NT-510 nettop (Intel Atom D510, ICH7/NM10 chipset). Flashrom doesn't find any chip while probing. Complete output of sensors-detect and flashrom -V here: http://paste.flashrom.org/view.php?id=1966 When running sensors-detect to find thermal/fan/etc., it appears to find an EEPROM chip while probing I2C/SMBus adapters, however I think this is just an EEPROM that gives information about the RAM module, rather than a BIOS/firmware Flash chip: SMBus I801 adapter at 0400 (i2c-6) Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Does anyone else have experience with this system and might know how to probe and read the BIOS EEPROM? Thanks, Dan

1 0

question
by Magnus Johansson E 05 Feb '14

05 Feb '14

Im working with a HW unit (similar to the ICH10), that has two SPI devices connected. enum ich_spi_mode { ich_auto, ich_hwseq, ich_swseq } ich_spi_mode = ich_auto; And I cannot use the ich_hwseq (which is propsed) because the Intel Chipset is only capable of erasing: 00: 256 byte 01: 4 KB 10: 8 KB 11: 64 KB And my flash chip, only support Sector erase/ or Bulk (but I don't like that one) and each sector is 256kB. So how can I proceed here? As I understand I cannot use the hw_seq and have to go for the sw_seq. But then how to handle the chip-select? When Im running the sw_seq I can only use one flash device, .. Thanks for support Magnus Johansson

3 3

Re: [flashrom] New motherboard for supported HW list
by Stefan Tauner 04 Feb '14

04 Feb '14

On Mon, 3 Feb 2014 14:19:52 -0800 "Jeff O'Neil" <jeffreydoneil(a)gmail.com> wrote: > Reporting a successful bios flash for motherboard GIGABYTE GA-X79-UD3 > > Flashrom reports as multiple different chips, visual inspection shows mine > to be "MX25L6406E" > > All went smooth, excellent work guys! Much respect! Thank you > Put outputs into pastebin so I don't have too much clutter. Please dont do that. pastebins get lost, mails dont (at least they are mirrored a few dozen times). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Issues recognizing Macronics 25L3205D using UM232H-B-WE
by Jay Khan 04 Feb '14

04 Feb '14

Hi Idwer, The flash is on Macbook motherboard and I am using Pomona test clip (next time I think I would buy 3M clip), the same that ISP page on this site shows. The cable length is about 8 inches, so I think it should be pretty safe. I haven't tried to powered on the laptop in order to read the flash. I keep the battery removed. I could desolder the flash but I want to avoid it. Thanks! > Date: Tue, 4 Feb 2014 02:10:59 +0100 > From: vidwer(a)gmail.com > To: flashrom(a)flashrom.org > Subject: Re: [flashrom] Issues recognizing Macronics 25L3205D using UM232H-B-WE > > 2014-02-03 Jay Khan <greekhero(a)hotmail.com>: > > Thanks Idwer for your quick response. > > > > I changed the HOLD and WP to VCC still no luck; I am attaching the output > > with -V option; but it now does seem to detect the ID1 and ID2: > > > > Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: > > id1 0x7f7f, id2 0x7f > > This is where you have to tell us where the chip is connected to, or > if it is desoldered :) > The wiki page http://flashrom.org/ISP describes "the procedure of > writing a flash chip while it is (already/still) attached to the > circuit it is to be used with". > > > > > Still gives the error as before: > > > > > > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on > > ft2232_spi. > > Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x7f, > > id2 0x7f > > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). > > === > > From the attached log file: > ....

1 0

Re: [flashrom] Issues recognizing Macronics 25L3205D using UM232H-B-WE
by Jay Khan 04 Feb '14

04 Feb '14

Thanks Idwer for your quick response. I changed the HOLD and WP to VCC still no luck; I am attaching the output with -V option; but it now does seem to detect the ID1 and ID2: Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x7f7f, id2 0x7f Still gives the error as before: Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ft2232_spi. Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x7f, id2 0x7f Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). === 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(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, -VE, -Vw), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! No operations were specified. > Date: Mon, 3 Feb 2014 20:53:17 +0100 > From: vidwer(a)gmail.com > To: flashrom(a)flashrom.org > Subject: Re: [flashrom] Issues recognizing Macronics 25L3205D using UM232H-B-WE > > 2014-02-03 Jay Khan <greekhero(a)hotmail.com>: > > Hello, > > > > I am trying to get the Macronics Flash MX25L3205D using FTDI UM232H-B-WE > > with Flashrom 0.9.7-r1764 on lunux. > > > > The programmer UM232H seems to be supported based on > > http://flashrom.org/Supported_programmers > > The flash MX25L3205D seems to be supported based on: > > http://flashrom.org/Supported_hardware (MX datasheet: > > http://www.macronix.com/Lists/DataSheet/Attachments/1534/MX25L6405D,%203V,%…) > > > > I have the following pins connected using the following mapping and > > connected the MX flash using test clip: > > > > UM232H Mapping Macronics (25L3205D) > > D0->SPI_SK 6 > > D1->SPI_DO 2 > > D2->SPI_DI 5 > > D3->SPI_CS 1 > > D4->SPI_WP 3 > > D5->SPI_HOLD 7 > > GND 4 > > VCC 8 (3.13v) > > That mapping looks good, and when you apply VCC power to HOLD and WP > this flash chip should be detected. > Although this wiki page is about the buspirate, the connection section > applies to a great amount of flash chips: > http://flashrom.org/Bus_Pirate#Connections > > > > > When I use flashrom with command line: flashrom -p ft2232_spi:type232H, > > flashrom replies with "Found Generic flash chip "unknown SPI chip (RDID)" (0 > > kB, SPI) on ft2232_spi. Unsupported etc...... > > > > It is my understanding that the 25L3205D is supported and I am not sure why > > I would get this message. Any pointers would be very helpful. > > > > Thanks! > > > > > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > http://www.flashrom.org/mailman/listinfo/flashrom > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

2 1

New motherboard for supported HW list
by Jeff O'Neil 03 Feb '14

03 Feb '14

Reporting a successful bios flash for motherboard GIGABYTE GA-X79-UD3 Flashrom reports as multiple different chips, visual inspection shows mine to be "MX25L6406E" All went smooth, excellent work guys! Much respect! Put outputs into pastebin so I don't have too much clutter. Outputs: flashrom -p internal -V http://pastebin.com/csEisq2j lspci *-nnvvxxx* http://pastebin.com/HXuKAw6t superiotool -deV http://pastebin.com/M0rUrhXZ

1 0

Issues recognizing Macronics 25L3205D using UM232H-B-WE
by Jay Khan 03 Feb '14

03 Feb '14

Hello, I am trying to get the Macronics Flash MX25L3205D using FTDI UM232H-B-WE with Flashrom 0.9.7-r1764 on lunux. The programmer UM232H seems to be supported based on http://flashrom.org/Supported_programmers The flash MX25L3205D seems to be supported based on: http://flashrom.org/Supported_hardware (MX datasheet: http://www.macronix.com/Lists/DataSheet/Attachments/1534/MX25L6405D,%203V,%…) I have the following pins connected using the following mapping and connected the MX flash using test clip: UM232H Mapping Macronics (25L3205D) D0->SPI_SK 6 D1->SPI_DO 2 D2->SPI_DI 5 D3->SPI_CS 1 D4->SPI_WP 3 D5->SPI_HOLD 7 GND 4 VCC 8 (3.13v) When I use flashrom with command line: flashrom -p ft2232_spi:type232H, flashrom replies with "Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ft2232_spi. Unsupported etc...... It is my understanding that the 25L3205D is supported and I am not sure why I would get this message. Any pointers would be very helpful. Thanks!

2 1

Re: [flashrom] Trouble disabling write-protection on Chromebook
by BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq＠bitmessage.ch 01 Feb '14

01 Feb '14

The issue here turned out to be that I was not scrubbing the write-protect screw hole enough. I had to take the board out and scrub the screw hole with rubbing alcohol in order to get enough traction to clean the gunk I wasn't seeing. I had been scrubbing the board while leaving it in the case; apparently that wasn't enough. I finally got a success on flashrom --wp-disable after the fifth or sixth time cleaning. Thanks for the help!

1 0

idea: make flashrom a "driver" in linux kernel
by The Gluglug 31 Jan '14

31 Jan '14

Basically, /dev/spi This would be your flash chip, enumerated using flashrom. flashrom -r equivalent: dd if=/dev/spi of=dump.rom flashrom -w eqivalent: dd if=coreboot.rom of=/dev/spi Where SPI is the internal SPI chip on your motherboard. If (using flashrom as the backend) the linux kernel supports your flash chip, you could just use dd. What does the community think of this idea?

7 9

Re: [flashrom] MX25L25635F support?
by Brian Rak 27 Jan '14

27 Jan '14

Ah, I was using the windows builds (0.7.6.1-r1705). I'll have to give this another shot from a linux machine with a more recent build. I didn't see it in the wiki, so I didn't look for one. Thanks! On 1/24/2014 8:05 AM, Idwer Vollering wrote: > 2014/1/24 Brian Rak <brak(a)gameservers.com>: >> How would I go about getting an additional chip supported? I've got one of >> these: >> http://datasheet.octopart.com/MX25L25635FZNI-12G-Macronix-datasheet-1253711… >> connected to a buspirate. I'm able to detect it: >> >> Found Macronix flash chip "unknown Macronix SPI chip" (0 kB, SPI). >> >> but that's about it. This isn't part of a BIOS (it's actually used by an >> IPMI controller), so I don't have any ability to attempt to use an internal >> programmer. > Which version or build of flashrom were you using? Chip support for > this MX25L25635F was committed a while ago: > http://flashrom.org/trac/flashrom/changeset/1702 > > See http://flashrom.org/Downloads#Installation_from_source for > instructions to download and compile flashrom's source code manually. > > HTH, > > Idwer > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 1

Re: [flashrom] Setting up and getting to run
by Omar Aitcheson 27 Jan '14

27 Jan '14

One more these are commands I am trying On Jan 26, 2014 11:09 PM, "Omar Aitcheson" <purposedriven2012(a)gmail.com> wrote: > Hello these are the screenshots of my issue the first is when I drag > flashrom.exe into CMD window. Folder flashrom new is on desktop . Buspirate > is on COM 3 . Need read commands and write commands thanks > Thought I had it after irc window. > Thanks >

1 0

Setting up and getting to run
by Omar Aitcheson 27 Jan '14

27 Jan '14

Hello these are the screenshots of my issue the first is when I drag flashrom.exe into CMD window. Folder flashrom new is on desktop . Buspirate is on COM 3 . Need read commands and write commands thanks Thought I had it after irc window. Thanks

1 0

RE Flashrom
by Omar Aitcheson 27 Jan '14

27 Jan '14

hello i was in the room earlier to get info in the set up of flashrom and usage well i connect to chip drag flashrom to the dos cmd it comes up asking for programmer choice programmer is on com3 what are the correct commands i have folder on desktop folder name flashrom new thanks

1 0

Flash special target
by Michael Matz 26 Jan '14

26 Jan '14

Dear team, may you can help me for to fix some problem. I'm working in a company and we repair and produce for a well known costumer. Normally we upload the test firmware (Linux) to the device by Ethernet, with an encrypted Windows machine controlled from the customer. The tester show only not useful error, like DUT load stub. I work in the department for recover and repair ( Customer return ). Unfortunately the company is not willing to pay for professional tools. So may colleges (asian) they scrap the units, but my boss (Asian) complain. Now too the situation, I have a few units with firmware (Linux) and fortunately the have had a problem with the Ethernet so the tester is not able to delete the flash. I can use it for to debug the unit with the Bus pirate at UART mode. So I want to read this flash rom's and reprogramme the others to debug them. It is not clear the MCU is complete working or not, may some pins have a micro crack. How ever I have no SPI port on it, I have an JTAG an a Serial port. The flash it is a 1 to 4 MB TQFP with 48 pin. Exchanging the chip was already working for me, but as you know it is difficult and dangerous to solder on a 6 layer PCB. Of course I have all information about the chips, schematic and layout. I believe, I can use the serial port with bit-bang. But I have had no success (I read it one time on a other schematic). I'm the only one in the company use and have experience with Linux. So, if you have some time and willing to help, it will be great. As pay back I can give you the information with what parallel flash it is working (ICP). The only things, are not allowed for me is: to tell the customer name, share schematics, his product or firmware or CPU they use. But I can say it is a MIPS based MCU. Thank you in advance for any answer or help you can give to me. Sincerely Mike

2 2

MX25L25635F support?
by Brian Rak 24 Jan '14

24 Jan '14

How would I go about getting an additional chip supported? I've got one of these: http://datasheet.octopart.com/MX25L25635FZNI-12G-Macronix-datasheet-1253711… connected to a buspirate. I'm able to detect it: Found Macronix flash chip "unknown Macronix SPI chip" (0 kB, SPI). but that's about it. This isn't part of a BIOS (it's actually used by an IPMI controller), so I don't have any ability to attempt to use an internal programmer.

2 1

Fwd: Intel (R) Developer Zone - Case #: 00091086 [ ref:_00DU0JBUY._500U0AExiQ:ref ]
by Elmar Stellnberger 24 Jan '14

24 Jan '14

Dear FlashRom mailing list, I have a pb dot se 2 netbook with a CG82NM10 Bios chip. The good news is that Intel was ready to give us all necessary tech docs for supporting it by flashrom. Not so good news are: - the chip is not removable so trying to write it would likely only work once - I currently don`t have time to join your programming effort Nonetheless I believe that we should at least try to offer read support for the given chip. Being able to verify the installed Bios can already be of great value when it comes to system security. If that has worked well I am also ready to venture testing a write support though I would have to ask whether and how the chip could be repaired on a failed write attempt. Elmar Anfang der weitergeleiteten E-Mail: > Von: Intel Customer Support <supportreplies(a)intel.com> > Betreff: RE: Intel (R) Developer Zone - Case #: 00091086 [ ref:_00DU0JBUY._500U0AExiQ:ref ] > Datum: 22. Jänner 2014 20:43:16 MEZ > An: "estellnb(a)elstel.org" <estellnb(a)elstel.org> > > Hello Elmar, > > Thank you for your interest in Intel and for your inquiry regarding documentation for the CG82NM10 Bios Chip. > > We truly appreciate every opportunity to provide assistance. Information available to the public that will be helpful with your research is located on our Web sites listed below: > > Product specification for Intel® NM10 Express Chipset-Intel® CG82NM10 PCH is located in ark.intel.com: http://ark.intel.com/products/47610/Intel-CG82NM10-PCH > Datasheet for the product can be found: > http://www.intel.com/Assets/PDF/datasheet/322896.pdf > Specification update for the chipset can be found: > https://www-ssl.intel.com/content/www/us/en/intelligent-systems/cedar-trail… > > Best regards with your research, > > Aida s. > Intel® Developer Center > www.intel.com/content/www/us/en/hardware-developers/hardware-development.ht… >

2 1

Supermicro X9SCL+-F BIOS (via buspirate)
by Brian Rak 22 Jan '14

22 Jan '14

The Supermicro X9SCL+-F has an SPI programming header which lets you access the BIOS without soldering. The pinout looks something like this: (orient board so PCI slots are on the top) DI - | | - GND CS * * VCC CLK - | BIOS | - WP DO * * HOLD HOLD - | CHIP | - DO WP * * CLK VCC - | *| - CS GND * * DI (edge of board) There is also a SPI jumper (J29). I'm unsure of what this does, but I had it open while doing this (though, it seemed to work closed as well) Once connected properly, the BIOS is detected: Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on buspirate_spi. I'm assuming everything else will work, though I'm still waiting for the initial read to complete.

1 0

HP AAHD3-H8 Motherboard flashing with Uno
by Elvis Kit 21 Jan '14

21 Jan '14

Hello, I am getting this error message when i attempt to re-flash the bricked bios of this motherboard. Any help would be greatly appreciated! e6410 Test # flashrom -p serprog:dev=/dev/ttyACM0:2000000 -w HIB_716.ROM flashrom v0.9.7-r1764 on Linux 3.2.0-4-486 (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. serprog: Programmer name is "serprog-duino" Found Winbond flash chip "W25Q16.V" (2048 kB, SPI) on serprog. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Reading current flash chip contents... done. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x8000 ERASE FAILED! Reading current flash chip contents... Error: invalid response 0x00 from device Can't read anymore! Aborting. FAILED! Uh oh. Erase/write failed. Checking if anything changed. Error: invalid response 0x00 from device Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! Thanks in advance! Rob Stewart

1 0

Re: [flashrom] F2A85-M with flashrom
by HacKurx 20 Jan '14

20 Jan '14

Hi, Thank you for the informations. I just tested with succes flashrom on the versions 6002, 6004, 6102, 6402. Only the 6404 version does not work with flashrom and it is the only version that has the printable character sequence "SecureBootSetup"... I still have a few things to do with coreboot. Thank you very much. Best regards, 2014/1/18 Idwer Vollering <vidwer(a)gmail.com>: > Please include the mailinglist on the To: field hereafter, thanks :) > > 2014/1/18 HacKurx <hackurx(a)gmail.com>: >> Hello, >> >> I have a error with flashrom on f2a85_m : >> ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. >> >> flashrom --programmer internal -r sauvegarde-bios.rom >> flashrom v0.9.7-r1720 on Linux 3.12.7 (x86_64) >> flashrom is free software, get the source code at http://www.flashrom.org >> >> Calibrating delay loop... OK. >> Found chipset "AMD FCH". Enabling flash write... ERROR: State of >> SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. >> PROBLEMS, continuing anyway >> No EEPROM/flash device found. >> Note: flashrom can never write if the flash chip isn't found automatically. >> >> How to solve this problem? > > I ran into this too, and found out that F2A85M's BIOS v6404 prohibits > access where v5018 (the version that was preloaded on my board) does > not. > > I haven't tried whether any other build (5103 or 5104 or 51047 or 5202 > or 6002 or 6004 or 6102 or 6402) blocks full access. > > To solve this problem: either downgrade or read the chip using (a > breadboard and) an external programmer. > >> >> Thanks, Best regards, >> >> Loic >> http://hackurx.wordpress.com > > HTH, > > Idwer -- Best regards, HacKurx www.hackurx.info

1 0

Re: [flashrom] F2A85-M with flashrom
by Idwer Vollering 18 Jan '14

18 Jan '14

Please include the mailinglist on the To: field hereafter, thanks :) 2014/1/18 HacKurx <hackurx(a)gmail.com>: > Hello, > > I have a error with flashrom on f2a85_m : > ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. > > flashrom --programmer internal -r sauvegarde-bios.rom > flashrom v0.9.7-r1720 on Linux 3.12.7 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > Found chipset "AMD FCH". Enabling flash write... ERROR: State of > SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. > PROBLEMS, continuing anyway > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > > How to solve this problem? I ran into this too, and found out that F2A85M's BIOS v6404 prohibits access where v5018 (the version that was preloaded on my board) does not. I haven't tried whether any other build (5103 or 5104 or 51047 or 5202 or 6002 or 6004 or 6102 or 6402) blocks full access. To solve this problem: either downgrade or read the chip using (a breadboard and) an external programmer. > > Thanks, Best regards, > > Loic > http://hackurx.wordpress.com HTH, Idwer

1 0

Please support my laptop!
by Max Stevens 17 Jan '14

17 Jan '14

Here's the output of flashrom -V -p internal

1 0

W836xx: Latitude E4300: flashrom -V
by Spudnik＠sbcglobal.net 15 Jan '14

15 Jan '14

flashrom v0.9.6.1-r1564 on Linux 3.2.0-52-generic (x86_64) flashrom is free software,get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.7.3 little endian Command line ( args): flashrom -V

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by David Hendricks 14 Jan '14

14 Jan '14

On Tue, Jan 14, 2014 at 8:23 AM, Cory Henderson <dcoryh192(a)gmail.com> wrote: > With the chromebook powered on (be careful), and your multimeter in DC > volt mode, touch one probe to any metallic part of the computer chassis or > any known ground (could even use the ground pin of the flash), then touch > the other probe to the /WP pin (there was a datasheet sent out before with > pictures of all of the different packages and their pinouts). If your meter > reads 0V then the pin is being pulled down and the hardware /WP is being > enforced. If it reads 1.8V or something around there then it might be a bad > chip or something off in flashrom. > Yep, that's exactly right. For reference, here is the datasheet link posted earlier: http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… . The chip layout is on page 6--We're using the SOIC 208-mil package. The black dot which indicates pin 1 corresponds with a small dimple on the chip itself (and perhaps a white dot silkscreened on the mainboard PCB). IIRC this system is using the 1.8V chip, but it could be 3.3V. The procedure Cory outlined is correct, in either case. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq＠bitmessage.ch 14 Jan '14

14 Jan '14

> Darn, still no luck then... > > Well, I guess all that's left is to try finding a multimeter and seeing > if > /WP is being held low somehow. Also, do you have an external programmer > such as a Bus Pirate? > I now have a Bus Pirate. I also have a multimeter. What is the best way to check if /WP is being held low?

2 1

Re: [flashrom] Failed flash
by Stefan Tauner 14 Jan '14

14 Jan '14

On Mon, 13 Jan 2014 17:02:02 -0500 Paul <langpenguin(a)gmail.com> wrote: > Is it safe to > reboot? no. Try writing the backup you made with flashrom -r/--read before you wrote the new image. If that is successful you can reboot/shut down etc. Which device are you using? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Failed flash
by Paul 13 Jan '14

13 Jan '14

It failed. I might not have the write protector connected. Is it safe to reboot? Penagwin flashrom v0.9.4 : d02ee0f : Nov 02 2013 00:09:09 UTC on Linux 3.4.0 (x86_64), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian Block protection could not be disabled! Erasing and writing flash chip... spi_block_erase_20 failed during command execution at address 0x0 ERASE FAILED at 0x00400000! Expected=0xff, Read=0x00, failed byte count from 0x00400000-0x00400fff: 0x1000 ERASE FAILED! Reading current flash chip contents... spi_block_erase_52 failed during command execution at address 0x0 ERASE FAILED at 0x00400000! Expected=0xff, Read=0x00, failed byte count from 0x00400000-0x00407fff: 0x8000 ERASE FAILED! Reading current flash chip contents... spi_block_erase_d8 failed during command execution at address 0x0 ERASE FAILED at 0x00400000! Expected=0xff, Read=0x00, failed byte count from 0x00400000-0x0040ffff: 0x10000 ERASE FAILED! Reading current flash chip contents... spi_chip_erase_60 failed during command execution ERASE FAILED! Reading current flash chip contents... spi_chip_erase_c7 failed during command execution ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. 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! FAILED

1 0

Problems with Jetway Board and Winbond chip
by HaMa 09 Jan '14

09 Jan '14

Hey there… first of all: Thank you for that incredible flashrom tool. But sadly: I can not write my BIOS chip on my Jetway Board. I got a Jetway NC96FL Mainboard with a Winbond W25Q80BV BIOS Chip, Intel NM10 Chipset and running Ubuntu 10.10. Flashrom detects the chip and the chipset well, but can not disable block protection. So it is not possible to write. I also tried to flash the chip with the Serprog/Arduino-Flasher on an Arduino Uno and it works. (But I want to burn it with my Jetway Board.) Then I tried to write it in my Jetway Board with manual raising the /WP-Pin of the Winbond Chip to VCC and it works too. So is it something (GPIO) to raise the /WP-Pin in the chipset? Can somebody help me? I attached the logs from: $ flashrom -p internal -V (flash.log) $ lspci -nnvvxxx (lspci.log) $ superiotool -deV (superio.log) Thanks a lot, Hans-Martin

1 0

Re: [flashrom] Failed flash programming
by roxfan 08 Jan '14

08 Jan '14

Hello David, Wednesday, January 8, 2014, 8:33:33 PM, you wrote: DB> Did not work on my board. Did you actually read the error message? DB> # ./flashrom-guppy -w Guppy-I-unlocked-bios.bin -p internal <skipped> DB> Found SST flash chip "SST25VF064C" (8192 kB, SPI) at physical address 0xff800000. DB> Error: Image size doesn't match This is not a board issue (so far). Your file is wrong size. It must be exactly 8 megabytes (8388608 bytes). -- WBR, roxfan mailto:roxfan@skynet.be

1 0

Failed flash programming
by David Bashaw 08 Jan '14

08 Jan '14

Did not work on my board. # ./flashrom-guppy -w Guppy-I-unlocked-bios.bin -p internal flashrom v0.9.6.1-r1564 on Linux 2.6.32 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel DH89xxCC". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... OK. Found SST flash chip "SST25VF064C" (8192 kB, SPI) at physical address 0xff800000. Error: Image size doesn't match # ./flashrom-guppy -V flashrom v0.9.6.1-r1564 on Linux 2.6.32 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.4, GCC 4.4.6 20110731 (Red Hat 4.4.6-3), little endian Command line (1 args): ./flashrom-guppy -V Please select a programmer with the --programmer parameter. Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, serprog, buspirate_spi, rayer_spi, pony_spi, nicintel, nicintel_spi, ogp_spi, satamv, linux_spi #

1 0

flashrom -V
by Антон Основной 01 Jan '14

01 Jan '14

flashrom v0.9.6.1-r1705 on Linux 3.12.5-302.fc20.x86_64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.8.1 20130717 (Red Hat 4.8.1-5), little endian Command line (1 args): flashrom -V Using default programmer "internal". Calibrating delay loop... OS timer resolution is 1 usecs, 767M loops per second, delay more than 10% too short (got 55% of expected delay), recalculating... 1437M loops per second, 10 myus = 11 us, 100 myus = 101 us, 1000 myus = 1001 us, 10000 myus = 10008 us, 4 myus = 6 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Gigabyte Technology Co., Ltd." DMI string system-product-name: "M85M-US2H" DMI string system-version: " " DMI string baseboard-manufacturer: "Gigabyte Technology Co., Ltd." DMI string baseboard-product-name: "M85M-US2H" DMI string baseboard-version: "x.x" DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8718 on port 0x2e Found chipset "NVIDIA MCP78S" with PCI ID 10de:075c. Enabling flash write... This chipset is not really supported yet. Guesswork... ISA/LPC bridge reg 0x8a contents: 0x00, bit 6 is 0, bit 5 is 0 Flash bus type is LPC Found SMBus device 10de:0752 at 00:01:1 MCP SPI BAR is at 0x00000000 MCP SPI is not used. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Serial flash segment 0xfffe0000-0xffffffff enabled Serial flash segment 0x000e0000-0x000fffff enabled Serial flash segment 0xffee0000-0xffefffff disabled Serial flash segment 0xfff80000-0xfffeffff enabled LPC write to serial flash enabled Serial flash pin 29 Serial flash port 0x0820 The following protocols are supported: LPC, SPI. Probing for AMIC A25L05PT, 64 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L05PU, 64 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L10PT, 128 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L10PU, 128 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L20PT, 256 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L20PU, 256 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L40PT, 512 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L40PU, 512 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L80P, 1024 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L16PT, 2048 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L16PU, 2048 kB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L2005(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L4005(A/C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L8005/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Found Macronix flash chip "MX25L8005/MX25V8005" (1024 kB, SPI) at physical address 0xfff00000. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L3206E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L6405(D), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L6445E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L12805(D), 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res3: id1 0x1313, id2 0x13 Probing for PMC Pm25LV010, 128 kB: probe_spi_res3: id1 0x1313, id2 0x13 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xc2, id2 0x13 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xc2, id2 0x13 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xc2, id2 0x13 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: 4 byte RDID not supported on this SPI controller Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xc2, id2 0x13 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 Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content 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 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 0x25, id2 0x7b, 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 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 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, 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 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: 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 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content 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 Found Macronix flash chip "MX25L8005/MX25V8005" (1024 kB, SPI). No operations were specified. Restoring PCI config space for 00:01:0 reg 0x6d Restoring PCI config space for 00:01:0 reg 0x90 Restoring PCI config space for 00:01:0 reg 0x8c Restoring PCI config space for 00:01:0 reg 0x88

1 0

how to flashrom on alix 2d3 boards?
by d l f 31 Dec '13

31 Dec '13

Hello , I am interesting flashrom tool , and saw the site mentioned the tool is compatible with pc engines alix 2d3. http://www.flashrom.org/Supported_hardware but this boards without vga output ,and only has a serial port to check the board status. could you tell me how to step by step flash bios ? Thanks, deng 2013-12-31

1 0

Supermicro X6DVL-EG2 results
by Jared Mauch 31 Dec '13

31 Dec '13

[root@nat flashrom]# ./flashrom -p internal -Vw ~jared/6eg21257.rom flashrom v0.9.7-r1764 on Linux 2.6.32-358.18.1.el6.x86_64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.10, GCC 4.4.7 20120313 (Red Hat 4.4.7-3), little endian Command line (4 args): ./flashrom -p internal -Vw /home/jared/6eg21257.rom Calibrating delay loop... OS timer resolution is 1 usecs, 1635M loops per second, 10 myus = 18 us, 100 myus = 98 us, 1000 myus = 983 us, 10000 myus = 9438 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "Supermicro" DMI string system-product-name: "X6DVL-EG2" DMI string system-version: "1234567890" DMI string baseboard-manufacturer: "Supermicro" DMI string baseboard-product-name: "X6DVL-EG2" DMI string baseboard-version: "1234567890" Found Winbond Super I/O, id 0x52 W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 00. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found chipset "Intel 6300ESB" with PCI ID 8086:25a1. Enabling flash write... 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 disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 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_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled OK. The following protocols are supported: FWH. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x89, id2 0xac Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x89, id2 0xac Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Found Intel flash chip "82802AC" (1024 kB, FWH) at physical address 0xfff00000. Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x89, id2 0xac Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x89, id2 0xac 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 ST M50FLW040A, 512 kB: probe_82802ab: id1 0x89, id2 0xac Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x89, id2 0xac Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x89, id2 0xac 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 0x89, id2 0xac Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x89, id2 0xac Found Intel flash chip "82802AC" (1024 kB, FWH). === This flash part has status UNTESTED for operations: 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(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, -VE, -Vw), 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 coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:S, 0x080000-0x08ffff:S, 0x090000-0x09ffff:S, 0x0a0000-0x0affff:S, 0x0b0000-0x0bffff:S, 0x0c0000-0x0cffff:S, 0x0d0000-0x0dffff:S, 0x0e0000-0x0effff:EReady:BE RUN/FINISH:BE ERROR:PROG OK:VPP OK:PROG RUN/FINISH:WP|TBL#|WP#,ABORT:FAILED at 0x000ec000! Expected=0xff, Found=0x07, failed byte count from 0x000e0000-0x000effff: 0x11ef ERASE FAILED! Looking for another erase function. No usable erase functions left. 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 chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. Restoring PCI config space for 00:1f:0 reg 0x4e

1 0

Flashrom report/DELL Optiplex 980
by William Voccia 30 Dec '13

30 Dec '13

Hello, I've attached a verbose Flashrom report for a Dell Optiplex 980 I'm trying to flash. thank you. flashrom v0.9.6.1-r1563 on Linux 3.8.0-19-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (5 args): flashrom -V -w O980-A09.hdr --programmer internal Calibrating delay loop... OS timer resolution is 1 usecs, 1679M loops per second, 10 myus = 10 us, 100 myus = 104 us, 1000 myus = 976 us, 10000 myus = 10145 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Dell Inc." DMI string system-product-name: "OptiPlex 980 " DMI string system-version: "Not Specified" DMI string baseboard-manufacturer: "Dell Inc." DMI string baseboard-product-name: "0D441T" DMI string baseboard-version: "A01" DMI string chassis-type: "Mini Tower" Found chipset "Intel Q57" with PCI ID 8086:3b0a. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x0 0xffe00000/0xffa00000 FWH IDSEL: 0x0 0xffd80000/0xff980000 FWH IDSEL: 0x0 0xffd00000/0xff900000 FWH IDSEL: 0x0 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 disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x300000 bytes BIOS Lock Enable: enabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x2 WARNING: Setting 0xdc from 0x2 to 0x3 on Q57 failed. New value is 0x2. Root Complex Register Block address = 0xfeda8000 GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfeda8000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 WARNING: SPI Configuration Lockdown activated. Reading OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x08: 0x00000000 (FADDR) 0x50: 0x00000a0b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b 0x54: 0x00000000 FREG0: WARNING: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x09ff0700 FREG1: BIOS region (0x00700000-0x009fffff) is read-write. 0x5C: 0x06ff0023 FREG2: WARNING: Management Engine region (0x00023000-0x006fffff) is locked. 0x60: 0x00220021 FREG3: Gigabit Ethernet region (0x00021000-0x00022fff) is read-write. 0x64: 0x00200001 FREG4: WARNING: Platform Data region (0x00001000-0x00020fff) is locked. Please send a verbose log to flashrom(a)flashrom.org if this board is not listed on http://flashrom.org/Supported_hardware#Supported_mainboards yet. Writes have been disabled. You can enforce write support with the ich_spi_force programmer option, but it will most likely harm your hardware! If you force flashrom you will get no support if something breaks. 0x90: 0x04 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf84054 (SSFC) SSFC: SCGO=0, ACS=1, SPOP=0, COP=5, DBC=0, SME=0, SCF=0 0x94: 0x0606 (PREOP) 0x96: 0x4fc8 (OPTYPE) 0x98: 0x029fabab (OPMENU) 0x9C: 0x01050220 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00802005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x00000000 (FPB) Enabling hardware sequencing due to multiple flash chips detected. SPI Read Configuration: prefetching disabled, caching enabled, PROBLEMS, continuing anyway The following protocols are supported: FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Found 2 attached SPI flash chips with a combined density of 10240 kB. There is only one partition containing the whole address space (0x000000 - 0x9fffff). There are 2560 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (10240 kB, Programmer-specific) at physical address 0x0. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content 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 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 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 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 0xdc, id2 0x7a, id1 is normal flash content, id2 is normal flash content 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 0xdc, id2 0x7a, 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 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 W39V040FB, 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 W39V040FC, 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 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: 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: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (10240 kB, Programmer-specific). Write/erase is not working yet on your programmer in its current configuration. Aborting. Restoring MMIO space at 0x7f27650948a0 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq＠bitmessage.ch 27 Dec '13

27 Dec '13

> Can you try running "flashrom -p host --wp-disable -V" and pasting the > output on paste.flashrom.org? > Here it is: http://paste.flashrom.org/view.php?id=1851 > > If you have a voltmeter handy, you can also try measuring the voltage > on > > > the /WP pin (pin 3). More details on pin configuration can be found in >> the >> > datasheet: >> > >> http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… >> > >> >> I don't have voltmeter; I'm sure I could locate one given enough time >> though. Do you have any other suggestions as to steps I might be >> overlooking here? Otherwise, what should I be looking for specifically >> in >> the Winbond data sheet? >> > > Unfortunately I don't have many ideas here... I've only seen this once and > it seemed to be a defective chip since I couldn't change the write-protect > status by removing the chip and using an external programmer. (This was on > a different machine, and not in a retail unit) > > The only reason for failure should be if there is anything bridging the > gap > between the copper pads around the write-protect screw hole, thereby > connecting /WP on the chip to ground. If you have a magnifying glass, can > you inspect just to make sure there is nothing connecting those pads? I took the Chromebook apart and cleaned the area around the write-protect screw hole using alcohol-dabbed q-tips a second time. Visual inspection did not reveal anything that appeared to be joining the two "halves" of the gold screw hole ring. Running "flashrom --wp-disable" as root gave me the same failure message as before, details in the paste. I executed "flashrom -p host --wp-range 0 0" and got this result: flashrom v0.9.4 : 4169bc8 : Sep 21 2013 02:17:24 UTC on Linux 3.4.0 (armv7l), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian expected=0xe0, but actual=0xb8. FAILED Then, executing "flashrom -p host --wp-status" gave this result: flashrom v0.9.4 : 4169bc8 : Sep 21 2013 02:17:24 UTC on Linux 3.4.0 (armv7l), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian WP: status: 0x00b8 WP: status.srp0: 1 WP: status.srp1: 0 WP: write protect is enabled. WP: write protect range: start=0x00000000, len=0x00200000

2 1

Re: [flashrom] How to program PIIX4 GPO26 for output to make
by Gelip 26 Dec '13

26 Dec '13

Thx for replay :-). I was not sure wher to improve the code, in flashrom, coreboot or maybe seabios. Now I know :-) P.S. I test command 'setpci -s 00:07.0 b2.w=8000' and this also make flashrom working but byte=e0 is from PCI config space table from vendor BIOS. Thanks again, I will seek help on coreboot list.

1 0

Re: [flashrom] How to program PIIX4 GPO26 for output to make
by Gelip 26 Dec '13

26 Dec '13

Also enable program chip like this: (PCI word register b2) setpci -s 00:07.0 b2.w=e000 or (PCI byte register b3) setpci -s 00:07.0 b3.b=e0 e0h = 224DEC = 11100000 binary (bits 5, 6, 7) Please help add or fix code to make flashrom program.

2 1

Re: [flashrom] How to program PIIX4 GPO26 for output to make flashrom
by Gelip 23 Dec '13

23 Dec '13

I think I found how to enable BIOS chip programming. I make dump PCI config space registers device: 00:07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] while vendor BIOS and while coreboot bios and compare them. I tried to change the DWORD at offset b0 and flashrom no longer displays an error GPO26 :-) This is log after boot debian on coreboot: ======================================================================================== root@debian:~# flashrom -p internal flashrom v0.9.7-r1763 on Linux 2.6.32-5-486 (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. coreboot table found at 0x9fe1c00. Found chipset "Intel PIIX4/4E/4M". Enabling flash write... OK. Enabling full flash access for board "abit BF6"... ERROR: PIIX4 GPO26 not programmed for output. FAILED! Aborting to be safe. Error: Programmer initialization failed. ======================================================================================== No try set PCI register at offset b0: setpci -s 00:07.0 b0.l=e0000105 and now flashrom working :-): ======================================================================================== root@debian:~# flashrom -p internal flashrom v0.9.7-r1763 on Linux 2.6.32-5-486 (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. coreboot table found at 0x9fe1c00. Found chipset "Intel PIIX4/4E/4M". Enabling flash write... OK. Enabling full flash access for board "abit BF6"... OK. Found Winbond flash chip "W49F002U/N" (256 kB, Parallel) at physical address 0xfffc0000. No operations were specified.

1 0

Re: [flashrom] Flashrom fails on write. P4 motherboard
by Gelip 23 Dec '13

23 Dec '13

Cześć. Udało ci się odblokować płytę dla flashrom bo mam podobny problem?

1 0

Checked Pm25LV010 Chip for PEWR
by Matthias Larisch 19 Dec '13

19 Dec '13

Dear all, I successfully flashed a notebooks GPU BIOS SPI Flash Pm25LV010 using flashrom. I don't know why but I used Flashrom 0.9.4 and not the latest one and therefore had to add the WREN feature flag that is already present in 0.9.7. I used the bus pirate with 120kHz SPI mode. Notebook is fine again and a friend of mine happy :) (He flashed some non-mobile gpu bios from within windows using another tool... Don't ask) Regards, Matthias

2 1

Re: [flashrom] Trouble disabling write-protection on Chromebook
by David Hendricks 19 Dec '13

19 Dec '13

On Wed, Dec 18, 2013 at 2:56 PM, David Hendricks <dhendrix(a)google.com>wrote: > On Mon, Dec 16, 2013 at 9:09 PM, < > BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq(a)bitmessage.ch> wrote: > >> >> As root in >> >> developer mode, the output of flashrom -v is "flashrom v0.9.4 : >> 4169bc8 >> >> ...". The first time I ran flashrom --wp-disable, I got a message >> saying >> >> the operation FAILED with error=1. At that point I took the board apart >> >> again and cleaned the write-protect screw hole with q-tips dipped in >> >> rubbing alcohol. When I reassembled the Chromebook and tried again with >> >> flashrom -V --wp-disable, the last few lines I receive are: >> >> >> >> w25_set_srp0: old status: 0xb8 >> >> w25_set_srp0: new status: 0xb8 >> >> w25q_disable_writeprotect(): error=1. >> >> No -i argument is specified, set ignore_fmap. >> >> FAILED >> >> restore_power_management(): Power management enabled >> >> >> >> As you can see, I can't seem to disable write protection on this chip. >> >> I'm >> >> running stock ChromeOS. Any idea what I might be doing wrong? Thanks in >> >> advance. >> > >> > >> > That's weird... Since you have the system taken apart already, can you >> try >> > disconnecting the battery while the machine is unplugged? I'd recommend >> > leaving it disconnected for a minute or so, the idea being to give the >> SPI >> > ROM enough time to fully discharge and reset. >> > >> >> Thanks for responding. I took your advice and disconnected the battery for >> several minutes. After reassembling the board and running flashrom >> --wp-disable again I am receiving the same message (FAILED). flashrom >> --wp-status says: >> >> WP: status: 0x00b8 >> WP: status.srp0: 1 >> WP: status.srp1: 0 >> WP: write protect is enabled. >> WP: write protect range: start=0x00000000, len=0x00200000 > > > Hmmm, that looks correct for normal circumstances (with write-protection > enabled). Flashrom *should* be able to clear bit 7 of SRP0, so the status > should show up be 0x38 after running with --wp-disable. > > Can you try running "flashrom -p host --wp-disable -V" and pasting the > output on paste.flashrom.org? > You can also try "flashrom -p host --wp-range 0 0" and then "flashrom -p host --wp-status" to see if that changes anything. I'm curious if it's just that SRP0 bit that seems stuck. If the /WP pin is not grounded, then hardware write-protection should not be in effect and you should be able to effectively disable write-protection by clearing the range of protected blocks even if SRP0 is set to 1. > > If you have a voltmeter handy, you can also try measuring the voltage >> on > > > the /WP pin (pin 3). More details on pin configuration can be found in >> the >> > datasheet: >> > >> http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… >> > >> >> I don't have voltmeter; I'm sure I could locate one given enough time >> though. Do you have any other suggestions as to steps I might be >> overlooking here? Otherwise, what should I be looking for specifically in >> the Winbond data sheet? >> > > Unfortunately I don't have many ideas here... I've only seen this once and > it seemed to be a defective chip since I couldn't change the write-protect > status by removing the chip and using an external programmer. (This was on > a different machine, and not in a retail unit) > > The only reason for failure should be if there is anything bridging the > gap between the copper pads around the write-protect screw hole, thereby > connecting /WP on the chip to ground. If you have a magnifying glass, can > you inspect just to make sure there is nothing connecting those pads? I > assume that since you cleaned the area with rubbing alcohol that there is > no residue from the sticker. I'm wondering if there is a tiny bit of copper > (perhaps from a manufacturing defect) bridging the gap. If so, I'll ask one > of our hardware engineers if it's safe to attempt severing it or if they > have any better ideas. > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq＠bitmessage.ch 18 Dec '13

18 Dec '13

> On Mon, Dec 16, 2013 at 9:14 AM, < > BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq(a)bitmessage.ch> wrote: > >> Hello flashrom developers, >> >> I'm having trouble disabling write-protection on my Samsung Arm >> Chromebook. So far I've removed the metallic sticker covering the >> "write-protect screw hole" according to the pictures on the Chromium >> wiki >> < >> http://www.chromium.org/chromium-os/developer-information-for-chrome-os-dev… >> >. >> On the Snow board, this hole ships with no screw in it. > > > Are you sure about that? There should be a screw there... > > I guess I should not have spoken for all Snow boards, but mine certainly did not have a screw in the write-protect screw hole--only the metallic sticker. I did notice this the first time I opened it up, but I wasn't sure what to make of it. >> As root in >> developer mode, the output of flashrom -v is "flashrom v0.9.4 : 4169bc8 >> ...". The first time I ran flashrom --wp-disable, I got a message saying >> the operation FAILED with error=1. At that point I took the board apart >> again and cleaned the write-protect screw hole with q-tips dipped in >> rubbing alcohol. When I reassembled the Chromebook and tried again with >> flashrom -V --wp-disable, the last few lines I receive are: >> >> w25_set_srp0: old status: 0xb8 >> w25_set_srp0: new status: 0xb8 >> w25q_disable_writeprotect(): error=1. >> No -i argument is specified, set ignore_fmap. >> FAILED >> restore_power_management(): Power management enabled >> >> As you can see, I can't seem to disable write protection on this chip. >> I'm >> running stock ChromeOS. Any idea what I might be doing wrong? Thanks in >> advance. > > > That's weird... Since you have the system taken apart already, can you try > disconnecting the battery while the machine is unplugged? I'd recommend > leaving it disconnected for a minute or so, the idea being to give the SPI > ROM enough time to fully discharge and reset. > Thanks for responding. I took your advice and disconnected the battery for several minutes. After reassembling the board and running flashrom --wp-disable again I am receiving the same message (FAILED). flashrom --wp-status says: WP: status: 0x00b8 WP: status.srp0: 1 WP: status.srp1: 0 WP: write protect is enabled. WP: write protect range: start=0x00000000, len=0x00200000 > If you have a voltmeter handy, you can also try measuring the voltage on > the /WP pin (pin 3). More details on pin configuration can be found in the > datasheet: > http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… > I don't have voltmeter; I'm sure I could locate one given enough time though. Do you have any other suggestions as to steps I might be overlooking here? Otherwise, what should I be looking for specifically in the Winbond data sheet?

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom