- flashrom - mail.coreboot.org

[PATCH] Add support for Intel 82599 10G NICs
by Ed Swierk 05 Dec '14

05 Dec '14

The Intel 82599 series of 10G Ethernet controllers has a bit-banged SPI interface that's register-compatible with the one in the 1G controllers, except the register addresses are shifted up by 0x10000. See http://www.intel.com/content/www/us/en/ethernet-controllers/82599-10-gbe-co…. I tested this with a board that has the 0x10fc device and a Micron M25P40 SPI flash chip. I filled in device IDs for other 82599 devices per https://www-ssl.intel.com/content/www/us/en/ethernet-controllers/82599-10-g… and lifted the name strings from the PCI SIG device ID registry. Signed-off-by: Ed Swierk <eswierk(a)skyportsystems.com> =================================================================== diff --git a/trunk/nicintel_spi.c b/trunk/nicintel_spi.c --- a/trunk/nicintel_spi.c (revision 1855) +++ b/trunk/nicintel_spi.c (working copy) @@ -80,6 +80,13 @@ {PCI_VENDOR_ID_INTEL, 0x10b9, OK, "Intel", "82572EI Gigabit Ethernet Controller"}, {PCI_VENDOR_ID_INTEL, 0x10d3, OK, "Intel", "82574L Gigabit Ethernet Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10f7, NT, "Intel", "10 Gigabit BR KX4 Dual Port Network Connection"}, + {PCI_VENDOR_ID_INTEL, 0x10f8, NT, "Intel", "82599 10 Gigabit Dual Port Backplane Connection"}, + {PCI_VENDOR_ID_INTEL, 0x10f9, NT, "Intel", "82599 10 Gigabit Dual Port Network Connection"}, + {PCI_VENDOR_ID_INTEL, 0x10fb, NT, "Intel", "82599ES 10-Gigabit SFI/SFP+ Network Connection"}, + {PCI_VENDOR_ID_INTEL, 0x10fc, OK, "Intel", "82599 10 Gigabit Dual Port Network Connection"}, + {PCI_VENDOR_ID_INTEL, 0x1557, NT, "Intel", "82599 10 Gigabit Network Connection"}, + {0}, }; @@ -183,7 +190,13 @@ if (!io_base_addr) return 1; - nicintel_spibar = rphysmap("Intel Gigabit NIC w/ SPI flash", io_base_addr, MEMMAP_SIZE); + if (dev->device_id < 0x10f0) { + nicintel_spibar = rphysmap("Intel Gigabit NIC w/ SPI flash", io_base_addr, + MEMMAP_SIZE); + } else { + nicintel_spibar = rphysmap("Intel 10 Gigabit NIC w/ SPI flash", io_base_addr + 0x10000, + MEMMAP_SIZE); + } if (nicintel_spibar == ERROR_PTR) return 1;

2 1

[commit] r1856 - trunk
by repository service 05 Dec '14

05 Dec '14

Author: stefanct Date: Fri Dec 5 23:56:13 2014 New Revision: 1856 URL: http://flashrom.org/trac/flashrom/changeset/1856 Log: Add support for Intel 82599 10 GbE NICs. The Intel 82599 series of 10 GbE controllers has a bit-banged SPI interface that's register-compatible with the one in the 1 GbE controllers, except the register addresses are shifted up by 0x10000, cf. Intel document 331520: http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/8259… This patch was tested with a board that has the 0x10fc device and a Micron M25P40 SPI flash chip. The PCI IDs and names for the devices are per Intel document 331521 https://www-ssl.intel.com/content/dam/www/public/us/en/documents/specificat… and the PCI SIG device ID registry with small refinements. Signed-off-by: Ed Swierk <eswierk(a)skyportsystems.com> Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/nicintel_spi.c Modified: trunk/nicintel_spi.c ============================================================================== --- trunk/nicintel_spi.c Sun Nov 30 23:31:12 2014 (r1855) +++ trunk/nicintel_spi.c Fri Dec 5 23:56:13 2014 (r1856) @@ -29,6 +29,9 @@ * * Intel 82574 Gigabit Ethernet Controller Family Datasheet * http://www.intel.com/content/www/us/en/ethernet-controllers/82574l-gbe-cont… + * + * Intel 82599 10 GbE Controller Datasheet (331520) + * http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/8259… */ #include <stdlib.h> @@ -50,7 +53,7 @@ * Table 13-6 * * Bit 04, 05: FWE (Flash Write Enable Control) - * 00b = not allowed + * 00b = not allowed (on some cards this sends an erase command if bit 31 (FL_ER) of FLA is set) * 01b = flash writes disabled * 10b = flash writes enabled * 11b = not allowed @@ -80,6 +83,18 @@ {PCI_VENDOR_ID_INTEL, 0x10b9, OK, "Intel", "82572EI Gigabit Ethernet Controller"}, {PCI_VENDOR_ID_INTEL, 0x10d3, OK, "Intel", "82574L Gigabit Ethernet Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10d8, NT, "Intel", "82599 10 Gigabit Unprogrammed Network Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10f7, NT, "Intel", "82599 10 Gigabit KX4 Dual Port Network Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10f8, NT, "Intel", "82599 10 Gigabit Dual Port Backplane Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10f9, NT, "Intel", "82599 10 Gigabit CX4 Dual Port Network Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10fb, NT, "Intel", "82599 10-Gigabit SFI/SFP+ Network Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10fc, OK, "Intel", "82599 10 Gigabit XAUI/BX4 Dual Port Network Controller"}, + {PCI_VENDOR_ID_INTEL, 0x1517, NT, "Intel", "82599 10 Gigabit KR Network Controller"}, + {PCI_VENDOR_ID_INTEL, 0x151c, NT, "Intel", "82599 10 Gigabit TN Network Controller"}, + {PCI_VENDOR_ID_INTEL, 0x1529, NT, "Intel", "82599 10 Gigabit Dual Port Network Controller with FCoE"}, + {PCI_VENDOR_ID_INTEL, 0x152a, NT, "Intel", "82599 10 Gigabit Dual Port Backplane Controller with FCoE"}, + {PCI_VENDOR_ID_INTEL, 0x1557, NT, "Intel", "82599 10 Gigabit SFI Network Controller"}, + {0}, }; @@ -183,7 +198,13 @@ if (!io_base_addr) return 1; - nicintel_spibar = rphysmap("Intel Gigabit NIC w/ SPI flash", io_base_addr, MEMMAP_SIZE); + if (dev->device_id < 0x10d8) { + nicintel_spibar = rphysmap("Intel Gigabit NIC w/ SPI flash", io_base_addr, + MEMMAP_SIZE); + } else { + nicintel_spibar = rphysmap("Intel 10 Gigabit NIC w/ SPI flash", io_base_addr + 0x10000, + MEMMAP_SIZE); + } if (nicintel_spibar == ERROR_PTR) return 1;

1 0

updating Coreboot
by Mathilde 05 Dec '14

05 Dec '14

Hello, Being not an informatician, I need help for updating my BIOS Coreboot (on a Thinkpad X60), because of heat issues. I dowloaded the last release here http://libreboot.org/docs/release.html, and installed the build dependencies. Could you explain me step by step what to do now? I did'nt understand whether I am to compile flashrom or not. In advance thank you very much! Math

1 0

Winbond 25Q256 support
by Francisco Javier Lasa Gutierrez 02 Dec '14

02 Dec '14

I need to program a 25Q256 chip, do you plan to add support to this EEPROM? if not, can you please guide me how to add it to the code?

2 1

Regression in r1833
by Roman Lebedev 01 Dec '14

01 Dec '14

Hello. I had a segfault with current version of flashrom, and with some help from stefanct at IRC i was able to bisect it down to r1833. I attach backtraces. Roman.

1 0

W836xx: ASUS PCH-DR: flashrom -V
by Roman Lebedev 01 Dec '14

01 Dec '14

flashrom v0.9.7-r1855 on Linux 3.16.0-4-686-pae (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.9.2, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 902M loops per second, 10 myus = 9 us, 100 myus = 90 us, 1000 myus = 900 us, 10000 myus = 9009 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: "ASUSTeK COMPUTER INC." DMI string system-product-name: "PCH-DR" DMI string system-version: "1.XX " DMI string baseboard-manufacturer: "ASUSTek Computer INC." DMI string baseboard-product-name: "PCH-DR" DMI string baseboard-version: "1.XX " Found Winbond Super I/O, id 0x82 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 -p internal" 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 0x08, id2 0x14, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) mapped at physical address 0xfff80000. Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: 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 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x08, id2 0x14, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x9d, id2 0x6e Found PMC flash chip "Pm49FL004" (512 kB, LPC, 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 chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! No operations were specified. Restoring PCI config space for 00:1f:0 reg 0x4e

1 0

[commit] r1855 - trunk
by repository service 30 Nov '14

30 Nov '14

Author: stefanct Date: Sun Nov 30 23:31:12 2014 New Revision: 1855 URL: http://flashrom.org/trac/flashrom/changeset/1855 Log: Add board enable for GIGABYTE GA-8SIMLFS 2.0. This board was used/sold by Fujitsu. The board enabled was tested (sadly with the wrong image, i.e. one of the GA-8SIMLH images directly from GIGABYTE instead of one from Fujitsu). Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/board_enable.c trunk/print.c Modified: trunk/board_enable.c ============================================================================== --- trunk/board_enable.c Sun Nov 2 00:12:33 2014 (r1854) +++ trunk/board_enable.c Sun Nov 30 23:31:12 2014 (r1855) @@ -1963,6 +1963,7 @@ * * Suited for: * - MSI 651M-L: SiS651 / SiS962 + * - GIGABYTE GA-8SIMLFS 2.0 * - GIGABYTE GA-8SIMLH */ static int sis_gpio0_raise_and_w836xx_memw(void) @@ -2403,6 +2404,7 @@ {0x8086, 0x2570, 0x1458, 0x2570, 0x8086, 0x24d0, 0, 0, "^8IP775/-G$",NULL, NULL, P3, "GIGABYTE", "GA-8IP775", 0, OK, intel_ich_gpio32_raise}, {0x8086, 0x244b, 0x8086, 0x2442, 0x8086, 0x2445, 0x1458, 0xa002, NULL, NULL, NULL, P3, "GIGABYTE", "GA-8IRML", 0, OK, intel_ich_gpio25_raise}, {0x8086, 0x24c3, 0x1458, 0x24c2, 0x8086, 0x24cd, 0x1458, 0x5004, NULL, NULL, NULL, P3, "GIGABYTE", "GA-8PE667 Ultra 2", 0, OK, intel_ich_gpio32_raise}, + {0x1039, 0x0650, 0x1039, 0x0650, 0x1039, 0x7012, 0x1458, 0xA002, "^GA-8SIMLFS20$", NULL, NULL, P3, "GIGABYTE", "GA-8SIMLFS 2.0", 0, OK, sis_gpio0_raise_and_w836xx_memw}, {0x1039, 0x0651, 0x1039, 0x0651, 0x1039, 0x7002, 0x1458, 0x5004, "^GA-8SIMLH$",NULL, NULL, P3, "GIGABYTE", "GA-8SIMLH", 0, OK, sis_gpio0_raise_and_w836xx_memw}, {0x10DE, 0x02F1, 0x1458, 0x5000, 0x10DE, 0x0261, 0x1458, 0x5001, NULL, NULL, NULL, P3, "GIGABYTE", "GA-K8N51GMF", 0, OK, nvidia_mcp_gpio3b_raise}, {0x10DE, 0x026C, 0x1458, 0xA102, 0x10DE, 0x0260, 0x1458, 0x5001, NULL, NULL, NULL, P3, "GIGABYTE", "GA-K8N51GMF-9", 0, OK, nvidia_mcp_gpio3b_raise}, Modified: trunk/print.c ============================================================================== --- trunk/print.c Sun Nov 2 00:12:33 2014 (r1854) +++ trunk/print.c Sun Nov 30 23:31:12 2014 (r1855) @@ -818,6 +818,7 @@ B("GIGABYTE", "GA-8IRML", OK, "http://www.gigabyte.com/products/product-page.aspx?pid=1343", NULL), B("GIGABYTE", "GA-8PE667 Ultra 2", OK, "http://www.gigabyte.com/products/product-page.aspx?pid=1607", NULL), B("GIGABYTE", "GA-8S648", OK, "http://www.gigabyte.com/products/product-page.aspx?pid=1674", NULL), + B("GIGABYTE", "GA-8SIMLFS 2.0", OK, NULL, "This is an OEM board used by Fujitsu."), B("GIGABYTE", "GA-8SIMLH", OK, "http://www.gigabyte.com/products/product-page.aspx?pid=1399", NULL), B("GIGABYTE", "GA-945PL-S3P (rev. 6.6)", OK, "http://www.gigabyte.com/products/product-page.aspx?pid=2541", NULL), B("GIGABYTE", "GA-965GM-S2 (rev. 2.0)", OK, "http://www.gigabyte.com/products/product-page.aspx?pid=2617", NULL),

1 0

[PATCH] Fix board enables in a hacky way
by Stefan Tauner 30 Nov '14

30 Nov '14

I broke the board enable matching. This is just a hack to get it working on non-coreboot boards. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> --- board_enable.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/board_enable.c b/board_enable.c index 1235bb8..38a966d 100644 --- a/board_enable.c +++ b/board_enable.c @@ -2532,10 +2532,10 @@ static const struct board_match *board_match_name(const char *vendor, const char const struct board_match *partmatch = NULL; for (; board->vendor_name; board++) { - if (!board->lb_vendor || strcasecmp(board->lb_vendor, vendor)) + if (!board->vendor_name || strcasecmp(board->vendor_name, vendor)) continue; - if (!board->lb_part || strcasecmp(board->lb_part, model)) + if (!board->board_name || strcasecmp(board->board_name, model)) continue; if (!pci_dev_find(board->first_vendor, board->first_device)) { -- Kind regards, Stefan Tauner

1 0

W836xx: lenovo ideapad y500 laptop: flashrom -V
by Максим Мосейчук 28 Nov '14

28 Nov '14

flashrom v0.9.7-r1711 on Linux 3.17.4-1-ARCH (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.2, little endian Command line (3 args): flashrom --programmer internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 3360M loops per second, 10 myus = 10 us, 100 myus = 198 us, 1000 myus = 1030 us, 10000 myus = 9994 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "20193" DMI string system-version: "Lenovo IdeaPad Y500" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "INVALID" DMI string baseboard-version: "31900004WIN8 STD SGL" DMI string chassis-type: "Notebook" Laptop detected via DMI. 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: 85. 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 ITE EC, ID 0x8580, Rev 0x00 on port 0x4e.

1 0

Success with flashing AOPEN UK79G-1394 (EZ18) -Vw
by Lawrence Gough 23 Nov '14

23 Nov '14

flashrom v0.9.7-r1782 on Linux 3.16.0-24-generic (i686) flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian Command line (7 args): flashrom -p internal -V -o logfile.txt -w EZ18112C.BIN Calibrating delay loop... OS timer resolution is 14 usecs, 525M loops per second, 10 myus = 11 us, 100 myus = 101 us, 1000 myus = 1011 us, 10000 myus = 16421 us, 56 myus = 57 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: " " DMI string system-product-name: " " DMI string system-version: " " DMI string baseboard-manufacturer: "AOpen" DMI string baseboard-product-name: "EZ18" DMI string baseboard-version: "9172410001" Found Winbond Super I/O, id 0x52 Found chipset "NVIDIA NForce2" with PCI ID 10de:0060. Enabling flash write... OK. The following protocols are supported: Non-SPI. Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT49(H)F010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F080T, 1024 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 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0xffff, id2 0x00ff Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_m29f400bt: id1 0x49, id2 0x44 Probing for Fujitsu MBM29F400TC, 512 kB: probe_m29f400bt: id1 0x49, id2 0x44 Probing for Fujitsu MBM29LV160BE, 2048 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Fujitsu MBM29LV160TE, 2048 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0x49, id2 0x44, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0x49, id2 0x44, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0xfa, id2 0xfc, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: 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 SST28SF040A, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST39VF080, 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 SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Found SST flash chip "SST49LF040" (512 kB, LPC) at physical address 0xfff80000. Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_m29f400bt: id1 0x49, id2 0x44 Probing for ST M29F400BT, 512 kB: probe_m29f400bt: id1 0x49, id2 0x44 Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0xfa, id2 0xfc, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 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 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0xf4, id2 0x4f, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39F010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39L010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39L020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xbf, id2 0x51 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 0xbf, id2 0x51 Found SST flash chip "SST49LF040" (512 kB, LPC). === This flash part has status UNTESTED for operations: WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -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-0x000fff:EW, 0x001000-0x001fff:S, 0x002000-0x002fff:S, 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, 0x00f000-0x00ffff:S, 0x010000-0x010fff:EW, 0x011000-0x011fff:EW, 0x012000-0x012fff:EW, 0x013000-0x013fff:EW, 0x014000-0x014fff:EW, 0x015000-0x015fff:EW, 0x016000-0x016fff:EW, 0x017000-0x017fff:EW, 0x018000-0x018fff:EW, 0x019000-0x019fff:EW, 0x01a000-0x01afff:EW, 0x01b000-0x01bfff:EW, 0x01c000-0x01cfff:EW, 0x01d000-0x01dfff:EW, 0x01e000-0x01efff:EW, 0x01f000-0x01ffff:EW, 0x020000-0x020fff:EW, 0x021000-0x021fff:EW, 0x022000-0x022fff:EW, 0x023000-0x023fff:EW, 0x024000-0x024fff:EW, 0x025000-0x025fff:EW, 0x026000-0x026fff:EW, 0x027000-0x027fff:EW, 0x028000-0x028fff:EW, 0x029000-0x029fff:EW, 0x02a000-0x02afff:EW, 0x02b000-0x02bfff:EW, 0x02c000-0x02cfff:EW, 0x02d000-0x02dfff:EW, 0x02e000-0x02efff:EW, 0x02f000-0x02ffff:EW, 0x030000-0x030fff:EW, 0x031000-0x031fff:EW, 0x032000-0x032fff:EW, 0x033000-0x033fff:EW, 0x034000-0x034fff:EW, 0x035000-0x035fff:EW, 0x036000-0x036fff:EW, 0x037000-0x037fff:EW, 0x038000-0x038fff:EW, 0x039000-0x039fff:EW, 0x03a000-0x03afff:EW, 0x03b000-0x03bfff:EW, 0x03c000-0x03cfff:EW, 0x03d000-0x03dfff:EW, 0x03e000-0x03efff:EW, 0x03f000-0x03ffff:EW, 0x040000-0x040fff:EW, 0x041000-0x041fff:EW, 0x042000-0x042fff:EW, 0x043000-0x043fff:EW, 0x044000-0x044fff:EW, 0x045000-0x045fff:EW, 0x046000-0x046fff:EW, 0x047000-0x047fff:EW, 0x048000-0x048fff:EW, 0x049000-0x049fff:EW, 0x04a000-0x04afff:EW, 0x04b000-0x04bfff:EW, 0x04c000-0x04cfff:EW, 0x04d000-0x04dfff:EW, 0x04e000-0x04efff:EW, 0x04f000-0x04ffff:EW, 0x050000-0x050fff:EW, 0x051000-0x051fff:EW, 0x052000-0x052fff:EW, 0x053000-0x053fff:EW, 0x054000-0x054fff:EW, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:EW, 0x06e000-0x06efff:EW, 0x06f000-0x06ffff:EW, 0x070000-0x070fff:EW, 0x071000-0x071fff:EW, 0x072000-0x072fff:EW, 0x073000-0x073fff:EW, 0x074000-0x074fff:EW, 0x075000-0x075fff:EW, 0x076000-0x076fff:EW, 0x077000-0x077fff:S, 0x078000-0x078fff:S, 0x079000-0x079fff:S, 0x07a000-0x07afff:S, 0x07b000-0x07bfff:S, 0x07c000-0x07cfff:S, 0x07d000-0x07dfff:S, 0x07e000-0x07efff:EW, 0x07f000-0x07ffff:EW Erase/write done. Verifying flash... VERIFIED. Restoring PCI config space for 00:01:0 reg 0x6d Restoring PCI config space for 00:01:0 reg 0x92

1 0

Re: [flashrom] additional support
by Thomas ... 23 Nov '14

23 Nov '14

hi can you please add support for the W25Q128FV chip, it says you already support but i cannot communicate via the buspirate. i can however talk to the chip via the bus pirate interface. i will give $50 donation. regards

2 2

Log
by Anouar Zoui 23 Nov '14

23 Nov '14

Calibrating delay loop... OK. Found SST flash chip "SST25VF032B" (4096 kB, SPI) on buspirate_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00009180! Expected=0x45, Found=0x43, failed byte count from 0x00000000-0x003fffff: 0x4db Your flash chip is in an unknown state.

2 1

Re: [flashrom] Unable to flash Kabini with NetBSD
by Stefan Tauner 18 Nov '14

18 Nov '14

On Fri, 14 Nov 2014 16:45:39 -0800 Justin Hibbits <jrh29(a)alumni.cwru.edu> wrote: > Hi, > > I just checked out the trunk from svn, since it supports the Kabini > SPI bus, but I'm unable to flash the BIOS. I see the following > message when I run it as: > > 'flashrom -p internal:laptop=force_I_want_a_brick -w myimage.bin' > > "Warning: Chip content is identical to the requested image." Well... above is pretty much everything to say unless you know your image differs from the chip contents. Why do you think there is anything wrong? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 6

Unable to update BIOS for my MainBoard MS7816 =Z87-G43
by nabil massaoudi 17 Nov '14

17 Nov '14

Hello I would update bios for my mainboard msi Z87-G43, and flashrom seems unable to do-it Hereafter the "flashrom" report and "flashrom" verbose report Thank you in advance for your help Regards Nabil MASSAOUDI [root@-----]# uname -a Linux ----- 3.17.2-200.fc20.x86_64 #1 SMP Tue Nov 4 18:04:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@-----]# ./flashrom --programmer internal flashrom v0.9.7-r1711 on Linux 3.17.2-200.fc20.x86_64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel Z87". 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: SPI Configuration Lockdown activated. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific) at physical address 0x0. No operations were specified. ===================flashrom verbose [root@kerfedora sbin]# ./flashrom --programmer internal -V flashrom v0.9.7-r1711 on Linux 3.17.2-200.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.1, GCC 4.8.3 20140911 (Red Hat 4.8.3-7), little endian Command line (3 args): ./flashrom --programmer internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 3296M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1000 us, 10000 myus = 10002 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "MSI" DMI string system-product-name: "MS-7816" DMI string system-version: "1.0" DMI string baseboard-manufacturer: "MSI" DMI string baseboard-product-name: "Z87-G43 (MS-7816)" DMI string baseboard-version: "1.0" DMI string chassis-type: "Desktop" Found chipset "Intel Z87" with PCI ID 8086:8c44. 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: 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 bytes BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled Root Complex Register Block address = 0xfed1c000 GCS = 0xc65: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0xf008 (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 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. 0x58: 0x07ff0200 FREG1: BIOS region (0x00200000-0x007fffff) is read-write. 0x5C: 0x01ff0001 FREG2: Management Engine region (0x00001000-0x001fffff) is read-write. 0x90: 0xc0 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0x91: 0xfc4010 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=0, SME=0, SCF=4 0x94: 0x0006 (PREOP) 0x96: 0x043b (OPTYPE) 0x98: 0x05203b02 (OPMENU) 0x9C: 0x0000019f (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x80802045 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002045 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x50444653 (FPB) Enabling hardware sequencing because some important opcode is locked. SPI Read Configuration: prefetching enabled, caching enabled, OK. The following protocols are supported: FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Found 1 attached SPI flash chip with a density of 8192 kB. The flash address space (0x000000 - 0x7fffff) is divided at address 0x653000 in two partitions. The first partition ranges from 0x000000 to 0x652fff. In that range are 1619 erase blocks with 4096 B each. The second partition ranges from 0x653000 to 0x7fffff. In that range are 429 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (8192 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 0xed, id2 0x88, 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 0xed, id2 0x88, 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 0x00, id2 0x03, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xed, id2 0x88, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xed, id2 0x88, 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: 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 0x7b, id2 0xbf, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xed, id2 0x88, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xed, id2 0x88, 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: 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 0x7b, id2 0xbf, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xed, id2 0x88, 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 0xed, id2 0x88, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xed, id2 0x88, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xed, id2 0x88, 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 0xed, id2 0x88, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific). No operations were specified. Restoring MMIO space at 0x7f81ef8018a0 Restoring PCI config space for 00:1f:0 reg 0xdc [root@----]#

3 2

Try add support for SST45LF010
by The Raven 16 Nov '14

16 Nov '14

Hello, i have an SST45LF010 chip here (from a nvidia graphic card) and try to add support for it. The log show me this: Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x5f, id2 0xdf Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25VF512A, 64 kB: probe_spi_rems: id1 0x5f, id2 0xdf Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0x5f, id2 0xdf Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x5f, id2 0xdf Probing for SST SST25VF020B, 256 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x5f, id2 0xdf Probing for SST SST25VF040B, 512 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x5f, id2 0xdf Probing for SST SST25VF080B, 1024 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25VF016B, 2048 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25VF032B, 4096 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25VF064C, 8192 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25WF512, 64 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25WF010, 128 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25WF020, 256 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25WF040, 512 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff Probing for SST SST25WF080, 1024 kB: RDID byte 1 parity violation. probe_spi_rdid_generic: id1 0x7fff, id2 0xff So it looks that it works similar to the "SST25VF010". But it has (always) an ID of 0x5F! Normally SST chips have 0xBF. In the datasheet i can also see that this chip should have 0xBF. Looks strange to me. Why i get this strange ID? Is this possible? Thx

2 4

Unable to flash Kabini with NetBSD
by Justin Hibbits 14 Nov '14

14 Nov '14

Hi, I just checked out the trunk from svn, since it supports the Kabini SPI bus, but I'm unable to flash the BIOS. I see the following message when I run it as: 'flashrom -p internal:laptop=force_I_want_a_brick -w myimage.bin' "Warning: Chip content is identical to the requested image." I've attached the full log of 'flashrom -p internal -V' and 'lspci -nnvvvxxxx'. I can provide even more verbose logs from flashrom if needed as well. Thanks, Justin

1 0

Re: [flashrom] Add new Macronix MX25L6495F support
by David Hendricks 13 Nov '14

13 Nov '14

Hi Alex, Thanks for the patch. I uploaded a modified version to chromium.org's code review server here: https://chromium-review.googlesource.com/229697 On Wed, Oct 15, 2014 at 3:13 AM, <alexlu6(a)mxic.com.tw> wrote: > Dear sirs, > > This mail comes from Macronix to add the new MX25L6495F flash chip > support > in the flashrom project in order to help the adoption of the chip for > Google Chromium OS. > Please help to review it. Thanks a lot! > > Alex Lu > FAE SW manager > > > > CONFIDENTIALITY NOTE: > > This e-mail and any attachments may contain confidential information > and/or personal data, which is protected by applicable laws. Please be > reminded that duplication, disclosure, distribution, or use of this e-mail > (and/or its attachments) or any part thereof is prohibited. If you receive > this e-mail in error, please notify us immediately and delete this mail as > well as its attachment(s) from your system. In addition, please be informed > that collection, processing, and/or use of personal data is prohibited > unless expressly permitted by personal data protection laws. Thank you for > your attention and cooperation. > > Macronix International Co., Ltd. > > ===================================================================== > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] flashrom error ioctl
by Idwer Vollering 11 Nov '14

11 Nov '14

2014-11-11 21:26 GMT+01:00 Jorge Mesquita <jorge(a)jmtech.com.py>: > > Hi, im trying to program a flash on hardkernel's odroid u3, > > my paste is here any help would be appreciated, thanks. Quote from paste: root@odroid:/home/odroid/flashrom-0.9.7# ./flashrom -p linux_spi:dev=/dev/spidev1.0 -E flashrom v0.9.7-r1711 on Linux 3.8.13.28 (armv7l) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on linux_spi. Erasing and writing flash chip... linux_spi_send_command: ioctl: Input/output error Verification impossible because read failed at 0x0 (len 0x1000) ERASE FAILED! Reading current flash chip contents... linux_spi_send_command: ioctl: Input/output error Can't read anymore! Aborting. FAILED! 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! Can you re-run the same command, but this time add one -V parameter? Are you familiar with strace and/or gdb? Idwer

1 0

flashrom error ioctl
by Jorge Mesquita 11 Nov '14

11 Nov '14

Hi, im trying to program a flash on hardkernel's odroid u3 <http://www.hardkernel.com/main/products/prdt_info.php?g_code=G138745696275> , my paste is here <http://paste.flashrom.org/view.php?id=2687> any help would be appreciated, thanks. --

1 0

Unsupported MB
by Alexandr . 10 Nov '14

10 Nov '14

Flashrom for dos не работает на плате Acer M1610 LGA775 (SIS672 + SIS968) ROM W25X40 DIP Описание: http://acersupport.com/acerpanam/manuals/acer/0000/servicemanuals/S.G_AS_M1… Данные по: Flashrom -v -p internal lspci -nnvvvxxx предоставлять?

1 0

Re: [flashrom] flashrom support for read\write word\byte actions
by Carl-Daniel Hailfinger 09 Nov '14

09 Nov '14

Hi Chanan, On 09.11.2014 12:27, Peri, Chanan wrote: > Do you know what does this "core" of flashrom include in terms of dediprog API for more specific operations (sector erase, read\write byte\word)? Right now we use a common (to all programmers and all flash chips) abstraction in flashrom which allows you to read/write/erase down to arbitrary small sizes, but internally larger operations (usually sector-based) happen. Think of it like the 512 Byte sector emulation of 4 kB hard drives. This is the abstraction we plan to make publicly available as part of libflashrom. There is also an internal common command submission engine which can send arbitrary raw commands to a flash chip, one engine per flash bus (SPI, FWH/LPC/Parallel). This engine is also common to all programmers of the same flash bus type. > Would it be reasonably possible for me (using the source code of flashrom) to add what I need, even if it's specific to dediprog or to some specific flash type? I think it should be reasonably easy to do this generically (see spi25.c for code which does SPI command submission), and there is no reason to make this dediprog specific. The suggested course of action also depends on whether you want a simple "read some bytes, write some bytes, erase manually/automatically" interface, or whether you want explicit SPI command submission and want to handle all the nasty details (verifying write/erase, handling programmer errors) yourself. > Chanan. Regards, Carl-Daniel > -----Original Message----- > From: Stefan Tauner [mailto:stefan.tauner@alumni.tuwien.ac.at] > Sent: Sunday, November 09, 2014 11:48 > To: Peri, Chanan > Cc: flashrom(a)flashrom.org > Subject: Re: [flashrom] flashrom support for read\write word\byte actions > > currently there exist already some patches that allow to read and write single sectors with some preparation and the user interface is probably not what you want (I am talking about layout files that allow to define and operate on regions of flash space). > > The midterm plan is to make the core of flashrom more library-like, which would ease the creation of a special purpose tool like the one you probably require. Note that midterm in flashrom terms can mean some years since developer time has been rather scarce lately... > > All of that is pretty much programmer-agnostic because most of the time we specify exactly what is sent to the SPI (or other) bus. >

1 0

Re: [flashrom] GA-H77-DS3H (rev. 1.1) Trying to unmap a nonexisting mapping!
by Stefan Tauner 09 Nov '14

09 Nov '14

On Sun, 9 Nov 2014 14:04:55 +0600 Evgeniy Edigarev <edigarev(a)gmail.com> wrote: > Hello. > It's just a program output, but new BIOS was installed with no problems. Hello Evgeniy, thanks for your report! I have added your board to our list of supported hardware and will commit that later together with other small changes. If possible, please always include a (verbose) log with such reports so that we can verify them and also look for oddities that might be interesting for our future work, thanks. > # flashrom --programmer internal -r F7.bin > flashrom v0.9.7-r1782 on Linux 3.16-3-amd64 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > Found chipset "Intel H77". Enabling flash write... Warning: SPI > Configuration Lockdown activated. > OK. > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) at physical address > 0xff800000. > Trying to unmap a nonexisting mapping! > Please report a bug at flashrom(a)flashrom.org > […] That one is known and fixed already, thanks. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] flashrom support for read\write word\byte actions
by Stefan Tauner 09 Nov '14

09 Nov '14

On Sun, 9 Nov 2014 08:29:21 +0000 "Peri, Chanan" <chanan.peri(a)intel.com> wrote: > Hi, > From what I see, flashrom only support full erase\read\write actions for the entire flash chip. > Is there any support for more specific actions - like erase sector? Read\write word\byte? > If not, is there any plan to support such a thing. > > I'm asking specifically about the DediProg programmer, but I'll be interested to know if this can be done with other programmers. Hello, currently there exist already some patches that allow to read and write single sectors with some preparation and the user interface is probably not what you want (I am talking about layout files that allow to define and operate on regions of flash space). The midterm plan is to make the core of flashrom more library-like, which would ease the creation of a special purpose tool like the one you probably require. Note that midterm in flashrom terms can mean some years since developer time has been rather scarce lately... All of that is pretty much programmer-agnostic because most of the time we specify exactly what is sent to the SPI (or other) bus. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

flashrom support for read\write word\byte actions
by Peri, Chanan 09 Nov '14

09 Nov '14

Hi, >From what I see, flashrom only support full erase\read\write actions for the entire flash chip. Is there any support for more specific actions - like erase sector? Read\write word\byte? If not, is there any plan to support such a thing. I'm asking specifically about the DediProg programmer, but I'll be interested to know if this can be done with other programmers. Thanks, Chanan Peri Intel Corporation |DCG, CSIG, CSE Controllers , SV MNG --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

GA-H77-DS3H (rev. 1.1) Trying to unmap a nonexisting mapping!
by Evgeniy Edigarev 09 Nov '14

09 Nov '14

Hello. It's just a program output, but new BIOS was installed with no problems. # flashrom --programmer internal -r F7.bin flashrom v0.9.7-r1782 on Linux 3.16-3-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel H77". Enabling flash write... Warning: SPI Configuration Lockdown activated. OK. Found Winbond flash chip "W25Q64.V" (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 Reading flash... done. # flashrom -w /home/sysop/Downloads/H77DS3H.F10 --programmer internal flashrom v0.9.7-r1782 on Linux 3.16-3-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel H77". Enabling flash write... Warning: SPI Configuration Lockdown activated. OK. Found Winbond flash chip "W25Q64.V" (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 Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom