flashrom

flashrom@flashrom.org

5 participants
9161 discussions

Intel Lynx Point LP Premium: W25Q64.V chip not detected correctly
by Denis Turischev 25 Mar '14

25 Mar '14

Hi flashrom team, I'm trying to read BIOS on SPI flash on Intel Lynx Point LP Premium chipset. 16M SPI flash consists of two Winbond chips 8M (W25Q64.V). When I use ich_spi_mode=auto flash is not detected. When I use ich_spi_mode=swseq detected only one 8M chip. Can you help? Denis

2 3

Re: [flashrom] Intel S5000PAL: Flash Not Found
by Sean Everson 24 Mar '14

24 Mar '14

Corey, I am working on getting physical access to a motherboard. We are first trying to see if we have an out of service box around so we don't have to pull a server out of production. While poking around I came across superiotool. Here is the output for the same box as the flashrom -V from earlier in the thread: # ./superiotool64 -d superiotool r4.0-5676-g1547ef2 Found NSC PC87427 (sid=0xf2, srid=0x05) at 0x2e Register dump: idx 10 12 13 1d 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f val 00 00 00 00 f2 11 a0 5a 84 40 02 05 00 11 00 c0 34 01 00 00 def 00 00 00 00 f2 11 a0 MM MM MM 02 NA 00 MM 00 00 MM MM RR RR LDN 0x00 (Floppy) idx 30 60 61 70 71 74 75 f0 f1 val 00 00 00 00 03 04 04 24 00 def 00 03 f2 06 03 02 04 24 00 LDN 0x02 (COM2) idx 30 60 61 70 71 74 75 f0 val 01 03 f8 04 03 04 04 02 def 00 02 f8 03 03 04 04 02 LDN 0x03 (COM1) idx 30 60 61 70 71 74 75 f0 val 00 00 00 04 03 04 04 02 def 00 03 f8 04 03 04 04 02 LDN 0x04 (System wake-up control (SWC)) idx 30 60 61 62 63 64 65 66 67 70 71 74 75 val 01 08 40 0c a8 0c ac 08 78 00 03 04 04 def 00 00 00 00 00 00 00 00 00 00 03 04 04 LDN 0x05 (Mouse) idx 30 70 71 74 75 val 01 0c 02 04 04 def 00 0c 02 04 04 LDN 0x06 (Keyboard) idx 30 60 61 62 63 70 71 74 75 f0 val 01 00 60 00 64 01 02 04 04 40 def 00 00 60 00 64 01 02 04 04 40 LDN 0x07 (GPIO) idx 30 50 60 61 70 71 74 75 f0 f1 f2 f3 f4 f5 f6 f7 f8 val 01 00 08 00 00 03 04 04 77 00 00 00 61 70 08 80 00 def 00 00 00 00 00 03 04 04 00 MM 01 00 00 00 00 00 00 LDN 0x09 (Fan Monitor and Control (FMC)) idx 30 50 60 61 70 71 74 75 f0 f1 val 00 00 00 00 00 03 04 04 00 00 def 00 00 00 00 00 03 04 04 19 06 LDN 0x0a (Watchdog timer (WDT)) idx 30 50 60 61 70 71 74 75 f0 val 01 00 08 60 00 03 04 04 00 def 00 00 00 00 00 03 04 04 00 LDN 0x0f (X-Bus) idx 30 60 61 70 71 74 75 f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff val 01 08 20 00 00 04 04 00 00 00 00 00 00 00 0b 84 00 00 00 00 00 80 91 def 00 00 00 00 00 04 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 10 LDN 0x10 (Real-time clock (RTC)) idx 30 60 61 62 63 70 71 74 75 f0 f1 f2 f3 f6 f7 val 01 08 72 08 74 08 00 04 04 00 00 00 32 80 03 def 00 00 70 00 72 08 00 04 04 00 00 00 00 MM 00 LDN 0x14 (Health monitoring and control (HMC)) idx 30 50 60 61 62 63 70 71 74 75 f0 val 00 00 00 00 00 00 00 03 04 04 05 def 00 00 00 00 00 00 00 03 04 04 05 ]# Not sure if that helps or not. Still working on gaining access to the motherboard today. Thanks for your help! --Sean On Sun, Mar 23, 2014 at 4:39 PM, Sean Everson <sean.everson(a)gmail.com> wrote: > Corey, > > I do not have access to a box today. When I am back at the office on > Monday I will open a box up and see what I can find for you. > > Thanks for the response! > > --Sean > > > On Sun, Mar 23, 2014 at 4:59 AM, Corey Osgood <corey.osgood(a)gmail.com> wrote: >> It looks like either the Super I/O chip on that board is not actually >> a Winbond W836xx, the flash chip isn't connected to that super IO, or >> you have a flash chip that isn't yet supported by flashrom. The reason >> I say this is because the technical manual says it uses a National >> Semiconductor PC87427, and that would explain the odd errors from >> flashrom. Do you have physical access to one of these boards? If so, >> can you get the part numbers off the Super I/O and BIOS flash chips? >> >> -Corey

1 0

Re: [flashrom] Intel S5000PAL: Flash Not Found
by Sean Everson 23 Mar '14

23 Mar '14

Corey, I do not have access to a box today. When I am back at the office on Monday I will open a box up and see what I can find for you. Thanks for the response! --Sean On Sun, Mar 23, 2014 at 4:59 AM, Corey Osgood <corey.osgood(a)gmail.com> wrote: > It looks like either the Super I/O chip on that board is not actually > a Winbond W836xx, the flash chip isn't connected to that super IO, or > you have a flash chip that isn't yet supported by flashrom. The reason > I say this is because the technical manual says it uses a National > Semiconductor PC87427, and that would explain the odd errors from > flashrom. Do you have physical access to one of these boards? If so, > can you get the part numbers off the Super I/O and BIOS flash chips? > > -Corey

1 0

Re: [flashrom] Intel S5000PAL: Flash Not Found
by Corey Osgood 23 Mar '14

23 Mar '14

It looks like either the Super I/O chip on that board is not actually a Winbond W836xx, the flash chip isn't connected to that super IO, or you have a flash chip that isn't yet supported by flashrom. The reason I say this is because the technical manual says it uses a National Semiconductor PC87427, and that would explain the odd errors from flashrom. Do you have physical access to one of these boards? If so, can you get the part numbers off the Super I/O and BIOS flash chips? -Corey

1 0

Asus H81M-PLUS board / Intel H81 chipset - bug report
by H. Sieger 23 Mar '14

23 Mar '14

Below is the output of sudo ./flashrom -p internal -V > ~/flashrom_test.txt *************START************* flashrom v0.9.7-r1769 on Linux 3.11.0-12-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.8.1, little endian Command line (3 args): ./flashrom -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 3397M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1002 us, 10000 myus = 10008 us, 4 myus = 6 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "ASUS" DMI string system-product-name: "All Series" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK COMPUTER INC." DMI string baseboard-product-name: "H81M-PLUS" DMI string baseboard-version: "Rev X.0x" Found chipset "Intel H81" with PCI ID 8086:8c5c. 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 = 0x2a: BIOS Lock Enable: enabled, BIOS Write Enable: disabled SPIBAR = 0x00007fd4108b3000 + 0x3800 0x04: 0xf008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Reading OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x50: 0x00004a4b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x4a, BRRA 0x4b 0x54: 0x00000000 0x58: 0x07ff0180 FREG1: BIOS region (0x00180000-0x007fffff) is read-write. 0x5C: 0x017f0001 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: 0xc4 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xfc4240 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=2, SME=0, SCF=4 0x94: 0x0006 (PREOP) 0x96: 0x043b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9C: 0x0000019f (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x80802025 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002025 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x50444653 (FPB) PROBLEMS, continuing anyway The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25F512, 64 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F512A, 64 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25F1024(A), 128 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F2048, 256 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F4096, 512 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI) at physical address 0xff800000. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Block Protect 4 (BP4) is not set Chip status register: Block Protect 3 (BP3) 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 GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L2005(C), 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L4005(A/C), 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L8005/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L3206E, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L6405(D), 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L6445E, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25L12805(D), 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 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 0xc8, id2 0x4017 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 0xc8, id2 0x4017 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 0xc8, id2 0x4017 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 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LV512(A), 64 kB: Invalid OPCODE 0xab, will not execute. Probing for PMC Pm25LV010, 128 kB: Invalid OPCODE 0xab, will not execute. Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Sanyo LE25FW418A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for Sanyo LE25FW806, 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for Sanyo LE25FW808, 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25LF040A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25LF080(A), 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25VF512A, 64 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF010, 128 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF020, 256 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Unknown SFDP-capable chip, 0 kB: Invalid OPCODE 0x5a, will not execute. Receiving SFDP signature failed. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x4017 Probing for Generic unknown SPI chip (REMS), 0 kB: Invalid OPCODE 0x90, will not execute. 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 0xc0, id2 0x3b, 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 0xc0, id2 0x3b, 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 0xa9, id2 0x10, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xc0, id2 0x3b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xc0, id2 0x3b, 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 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xc0, id2 0x3b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xc0, id2 0x3b, 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 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xc0, id2 0x3b, 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 0xc0, id2 0x3b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xc0, id2 0x3b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xc0, id2 0x3b, 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 0xc0, id2 0x3b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI). This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). No operations were specified. Restoring MMIO space at 0x7fd4108b68a0 Restoring PCI config space for 00:1f:0 reg 0xdc *************END************* Here below the terminal output of sudo ./flashrom -p internal *************START************* flashrom v0.9.7-r1769 on Linux 3.11.0-12-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel H81". 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... Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0x2a to 0x09 failed. New value is 0x2a. Warning: SPI Configuration Lockdown activated. FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG2: Warning: Management Engine region (0x00001000-0x0017ffff) is locked. 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). PROBLEMS, continuing anyway Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI) at physical address 0xff800000. Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org Trying to unmap a nonexisting mapping! Please report a bug at flashrom(a)flashrom.org No operations were specified. *************END************* Hope it helps. Heiko

1 0

NVIDIA MCP73
by Koen Rousseau 22 Mar '14

22 Mar '14

Reading, writing an verifying the BIOS on my old Acer Aspire M5640 PC's motherboard worked like a charm. Many thanks!

1 0

SuperMicro H8QME2 motherboards work great with Flashrom
by Greg Tippitt 21 Mar '14

21 Mar '14

On the hardware section of the wiki the SuperMicro H8QME2 was not mentioned, but several others from SM were supported. I needed to upgrade the BIOS on my motherboard before I could upgrade from dual core to hex core Opteron CPUs. It worked dead simple. I tried to do the -z option to send in, but it said that option wasn't compiled for. Thanks for a great program Greg Tippitt

1 0

W836xx: Foxconn nT435/nT535: flashrom -V
by Matt Keys 20 Mar '14

20 Mar '14

Hello, I was looking into coreboot compatibility with my nettop and noticed within the flashrom output (full log attached) : " 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. " You'll find the requested output of flashrom -V below. Regards, Matt ------ root@nettop:~# flashrom -V flashrom v0.9.6.1-r1563 on Linux 3.11.0-18-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 (1 args): flashrom -V Please select a programmer with the --programmer parameter. Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, ft2232_spi, serprog, buspirate_spi, rayer_spi, pony_spi, nicintel, nicintel_spi, ogp_spi, satamv root@nettop:~#

1 0

Re: [flashrom] Intel S5000PAL: Flash Not Found
by Sean Everson 19 Mar '14

19 Mar '14

All, I have a number of Intel S5000PAL motherboards that I would like to use FLASHROM to manage if at all possible. According to the Intel Docs at: http://download.intel.com/support/motherboards/server/s5000pal/sb/s5000pal_… The motherboard has the 6321ESB chipset which is listed as supported on the flashrom.org wiki page. When I try to use FLASHROM to read the flash I get an error message that the flash is not found. Can someone provide me with some guidance on what additional information or steps I can take to investigate this further? I have pasted the flashrom -V output here: http://pastebin.com/Rr24eXa5 Thanks for your help! --Sean On Wed, Mar 19, 2014 at 12:18 PM, Sean Everson <sean.everson(a)gmail.com> wrote: > All, > > > I have a number of Intel S5000PAL motherboards that I would like to use > FLASHROM to manage if at all possible. According to the Intel Docs at: > > > http://download.intel.com/support/motherboards/server/s5000pal/sb/s5000pal_… > > > The box contains the 6321ESB chipset which is listed as supported on the > flashrom.org wiki page. > > > When I try to use FLASHROM to read the flash I get an error message that the > flash is not found. Can someone provide me with some guidance on what > additional information or steps I can take to investigate this further? > > > I am including the output from flashrom -V below. > > > Thanks for your help! > > > --Sean > > > > # ./flashrom -V -p internal -r /tmp/bios.bin > > flashrom v0.9.7-r1764 on Linux 2.6.32.24 (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.7.1, little endian > > Command line (5 args): ./flashrom -V -p internal -r /tmp/bios.bin > > Calibrating delay loop... OS timer resolution is 1 usecs, 2824M loops per > second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = > 10025 us, 4 myus = 4 us, OK. > > Initializing internal programmer > > No coreboot table found. > > Using Internal DMI decoder. > > DMI string chassis-type: "Rack Mount Chassis" > > DMI string system-manufacturer: "Intel" > > DMI string system-product-name: "T5000PAL" > > DMI string system-version: "Not Specified" > > DMI string baseboard-manufacturer: "Intel" > > DMI string baseboard-product-name: "T5000PAL0 " > > DMI string baseboard-version: "FRU Ver 0.05" > > 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: f2. > > 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 631xESB/632xESB/3100" with PCI ID 8086:2670. 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: 0x0 > > 0xffc00000/0xff800000 FWH IDSEL: 0x0 > > 0xff700000/0xff300000 FWH IDSEL: 0x4 > > 0xff600000/0xff200000 FWH IDSEL: 0x5 > > 0xff500000/0xff100000 FWH IDSEL: 0x6 > > 0xff400000/0xff000000 FWH IDSEL: 0x7 > > 0xfff80000/0xffb80000 FWH decode enabled > > 0xfff00000/0xffb00000 FWH decode enabled > > 0xffe80000/0xffa80000 FWH decode enabled > > 0xffe00000/0xffa00000 FWH decode enabled > > 0xffd80000/0xff980000 FWH decode enabled > > 0xffd00000/0xff900000 FWH decode enabled > > 0xffc80000/0xff880000 FWH decode enabled > > 0xffc00000/0xff800000 FWH decode enabled > > 0xff700000/0xff300000 FWH decode disabled > > 0xff600000/0xff200000 FWH decode disabled > > 0xff500000/0xff100000 FWH decode disabled > > 0xff400000/0xff000000 FWH decode disabled > > Maximum FWH chip size: 0x400000 bytesSPI Read Configuration: prefetching > disabled, caching enabled, > > BIOS_CNTL = 0x03: BIOS Lock Enable: enabled, BIOS Write Enable: enabled > > Warning: Setting Bios Control at 0xdc from 0x02 to 0x01 failed. > > New value is 0x03. > > OK. > > The following protocols are supported: FWH. > > Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 > is normal flash content, id2 is normal flash content > > Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xea, id2 0xd0, > id1 is normal flash content, id2 is normal flash content > > Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x9b, id2 0x0c, > id1 is normal flash content, id2 is normal flash content > > Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xea, id2 > 0xd0, 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 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 > is normal flash content, id2 is normal flash content > > Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xc9, id2 > 0x78, id1 parity violation, id1 is normal flash content, id2 is normal flash > content > > Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x9b, id2 0x0c, id1 is > normal flash content, id2 is normal flash content > > Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xc9, id2 0x78, id1 > parity violation, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x9b, id2 > 0x0c, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xea, id2 > 0xd0, id1 is normal flash content, id2 is normal flash content > > Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xc9, id2 > 0x78, 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 > 0x9b, id2 0x0c, id1 is normal flash content, id2 is normal flash content > > No EEPROM/flash device found. > > Note: flashrom can never write if the flash chip isn't found automatically. > > Restoring PCI config space for 00:1f:0 reg 0xdc > >

1 0

Re: [flashrom] GSoC-2014 Flashrom project "Locking and unlocking of access protections of flash chips"
by David Hendricks 19 Mar '14

19 Mar '14

On Wed, Mar 19, 2014 at 5:58 AM, Allen Yan <lexkde(a)gmail.com> wrote: > Hi, David, > I was reading flashrom code base following the internal programmer > way. I also read mail > "http://www.flashrom.org/pipermail/flashrom/2013-March/010704.html" > and checked the Ibex peak datasheet about ME firmware. Here are some > questions: > about "Locking and unlocking of access protections of flash chips" > 1 which mechanism locks the flash?a software way or a hardware way > by the programmer. As in the Atmel AT25DL161, the protection ways are > "hardware protection, using WP pin", "Sector lockdown with permanent > freeze option", "individual sector protection with global > protect/unprotect feature". > All of the above :-) You will need to determine: - Which write-protection scheme is in place? Is it intended to prevent erroneous software from writing to the flash, or is it intended to prevent any re-writing of the flash? - Can it be disabled / worked around so that content can be updated? - How to restore the settings when you are finished. > 2 Does this problem concerns the ME firmware issue. > Yes. > 3 How to do the test? Is the test at specific mainboard and flash chip > enough? > IIRC Flashrom already tests for motherboards which are known to require a workaround, for example if a GPIO must be inverted in order to de-assert /WP. board_enable.c has many of these tests. It also knows about block protect bits in SPI ROMs. I think the main issue with modern systems (Intel in particular) is the management engine. > 4 How to value the work at last as stefan mentioned in the suggestion? > > > Actually, a little frustrating after I saw stefanct's mail. > It's very valuable :-) I put some effort into this functionality for ChromeOS, since handling write-protection is a requirement for Chromebooks. Here are some examples: Skip regions locked via flash descriptor for Intel platforms: https://chromium.googlesource.com/chromiumos/third_party/flashrom/+/1ed1d35… writeprotect.c, which contains block protect mapping for several flash chips: https://chromium.googlesource.com/chromiumos/third_party/flashrom/+/master/… Unfortunately we never reached a consensus regarding how to port this code to upstream. It would be nice if somebody like you can help to re-factor this code so that it can be accepted upstream. > On 3/18/14, Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> wrote: > > On Mon, 17 Mar 2014 09:56:43 +0800 > > 严进一 <lexkde(a)gmail.com> wrote: > > > >> Hi, > >> I am Jinyi Yan , a second year PhD candidate from Shanghai Institute of > >> Micro-system and Information Technology, Chinese Academy of Sciences. I > >> used to be a mainboard BIOS engineer in ASUS Technology Suzhou Co., Ltd > >> for about two years (2007.7~2009.2). My major now is optoelectronics. > But > >> I have a lot of fun while programming, in my heart the working > experience > >> of being a BIOS engineer is still very exciting. > >> I think GsoC is a nice platform for me to participate the open source > >> community. When I search the GsoC projects and organizations, the > coreboot > >> and flashrom projects are definitely the right choices for me. I have a > >> spare ASUS P5KPL PC at my hand, but the chipset is not in the support > list > >> of coreboot project. So I consider the flashrom project is the better > >> choice. I also have a home-made flash programmer based on uspasp. > >> I'd like to choose “Locking and unlocking of access protections of flash > >> chips” for GSoC 2014. > >> Now I'm not very familiar with the program structure of flashrom, so I > >> expect your guidence and hope to contribute for flashrom and coreboot > even > >> if my application is not accpeted. > >> Thanks! Look forward to your kind advice! > > > > Hello Jinyi, > > > > thanks for your interest in flashrom. I have been the most active > > flashrom developer in the last years and would probably be responsible > > to integrate your work and answer questions if you get stuck. I agree > > that the coreboot-related projects are probably the best choice for you > > (there are not many low-level projects participating sadly... that's > > how I ended up here too ;). I also have to admit that the P5KPL is > > probably not very helpful AFAICT. But I don't think that this is a show > > stopper regarding coreboot (or seabios) projects and that your skills > > and insights obtained at ASUS regarding x86 might be more useful in a > > non-flashrom project. Also, the project you chose requires to > > understand two code bases ("ours" and that maintained by google/ > > chromiumos ppl) and interact with two communities and persuade at least > > one of them that your solution is sound and profitable. On the other > > hand, I am biased because I will apply for a flashrom GSoC project > > myself probably. ;) > > The code bases have a very similar core so that should not be a big > > issue at all. Producing something that will be praised by everyone on > > the other hand is really hard. The vanilla flashrom community is > > traditionally very (very) picky regarding changes, especially user > > interface changes. This is also the reason why there is a chromiumos > > fork of flashrom... > > > > I have talked to David (dhendrix) and he is willing to mentor you this > > year. If you want to pursue this project (and the patch you sent seems > > to indicate that ;) I suggest you talk to him directly about details > > of the assignment (here or on IRC). > > > > Adding new flash chips as you have done is a very good first step to > > get to know flashrom a bit better. The fun begins with the awkward > > models though :) > > I suggest you test flashrom on any hardware available to you (including > > network cards for example)... there is always room for improvement and > > learning a foreign code base is always easier when on has a specific > > goal to reach. > > -- > > Kind regards/Mit freundlichen Grüßen, Stefan Tauner > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > http://www.flashrom.org/mailman/listinfo/flashrom > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom