February 2013 - flashrom - mail.coreboot.org

Re: [flashrom] Fwd: BIOS Write Enable bit problem.
by Andrew Goodbody Feb. 10, 2013

Feb. 10, 2013

On 08/02/13 23:47, Rich Futyma wrote: > Does anyone know why bit 0 in the BIOS Control register cannot be set using > Intel® X79 Express Chipset. This is what I get when running: > flashrom -r /tmp/bios.rom -p internal or flashrom -w xx.rom -p internal > > *Warning: Setting Bios Control at 0xdc from 0x2a to 0x0b on X79 failed.* > *New value is 0x2a.* You can see that bit 1 is already set. This will generate an SMI when you attempt to set bit 0. There will be SMM code that will reset bit 0 if you have not performed the correct handshake beforehand. This is a protection mechanism to prevent unauthorised modification of the BIOS. Andrew

2 1

chipset "NVIDIA MCP78S"
by Алексей Кардапольцев Feb. 9, 2013

Feb. 9, 2013

You're asking for email a report to flashrom(a)flashrom.org including a verbose (-V) log. Here it is: ┌─[~] └─[alexey@home]: sudo flashrom -V -w 1402.BIN flashrom v0.9.5.2-r1546 on Linux 3.2.0-4-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.7, GCC 4.6.2, little endian Command line (3 args): flashrom -V -w 1402.BIN Calibrating delay loop... OS timer resolution is 1 usecs, 402M loops per second, delay more than 10% too short (got 37% of expected delay), recalculating... 324M loops per second, delay more than 10% too short (got 29% of expected delay), recalculating... 327M loops per second, delay more than 10% too short (got 30% of expected delay), recalculating... 327M loops per second, delay more than 10% too short (got 30% of expected delay), recalculating... 328M loops per second, delay loop is unreliable, trying to continue 10 myus = 3 us, 100 myus = 30 us, 1000 myus = 298 us, 10000 myus = 9494 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "M3N78 PRO" DMI string baseboard-version: "1.XX" DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8716 on port 0x2e Found chipset "NVIDIA MCP78S" with PCI ID 10de:075c. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... This chipset is not really supported yet. Guesswork... ISA/LPC bridge reg 0x8a contents: 0x40, bit 6 is 1, bit 5 is 0 Flash bus type is SPI SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! Found SMBus device 10de:0752 at 00:01:1 MCP SPI BAR is at 0xfdf80000 Mapping NVIDIA MCP6x SPI at 0xfdf80000, unaligned size 0x544. SPI control is 0xc012, req=0, gnt=0 Please send the output of "flashrom -V" to flashrom(a)flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. No IT87* serial flash segment enabled. The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Chip status register is 00 Found Eon flash chip "EN25F80" (1024 kB, SPI) at physical address 0xfff00000. Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for GigaDevice GD25Q20, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for GigaDevice GD25Q40, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for GigaDevice GD25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for GigaDevice GD25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for GigaDevice GD25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for GigaDevice GD25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for GigaDevice GD25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Numonyx N25Q064, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25LF080A, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0x1c, id2 0x13 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x1c, id2 0x13 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x1c, id2 0x13 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x1c, id2 0x3114 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x1c, id2 0x13 Found Eon flash chip "EN25F80" (1024 kB, SPI). 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:E, 0x002000-0x002fff:S, 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:E, 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, 0x015000-0x015fff:S, 0x016000-0x016fff:S, 0x017000-0x017fff:S, 0x018000-0x018fff:S, 0x019000-0x019fff:S, 0x01a000-0x01afff:S, 0x01b000-0x01bfff:S, 0x01c000-0x01cfff:S, 0x01d000-0x01dfff:S, 0x01e000-0x01efff:S, 0x01f000-0x01ffff:S, 0x020000-0x020fff: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:EW, 0x056000-0x056fff:EW, 0x057000-0x057fff:EW, 0x058000-0x058fff:EW, 0x059000-0x059fff:EW, 0x05a000-0x05afff:EW, 0x05b000-0x05bfff:EW, 0x05c000-0x05cfff:EW, 0x05d000-0x05dfff:EW, 0x05e000-0x05efff:EW, 0x05f000-0x05ffff:EW, 0x060000-0x060fff:EW, 0x061000-0x061fff:EW, 0x062000-0x062fff:EW, 0x063000-0x063fff:EW, 0x064000-0x064fff:EW, 0x065000-0x065fff:EW, 0x066000-0x066fff:EW, 0x067000-0x067fff:EW, 0x068000-0x068fff:EW, 0x069000-0x069fff:EW, 0x06a000-0x06afff:EW, 0x06b000-0x06bfff:EW, 0x06c000-0x06cfff:EW, 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:EW, 0x078000-0x078fff:EW, 0x079000-0x079fff:EW, 0x07a000-0x07afff:EW, 0x07b000-0x07bfff:EW, 0x07c000-0x07cfff:EW, 0x07d000-0x07dfff:EW, 0x07e000-0x07efff:EW, 0x07f000-0x07ffff:EW, 0x080000-0x080fff:EW, 0x081000-0x081fff:EW, 0x082000-0x082fff:EW, 0x083000-0x083fff:EW, 0x084000-0x084fff:EW, 0x085000-0x085fff:EW, 0x086000-0x086fff:EW, 0x087000-0x087fff:EW, 0x088000-0x088fff:EW, 0x089000-0x089fff:EW, 0x08a000-0x08afff:EW, 0x08b000-0x08bfff:EW, 0x08c000-0x08cfff:EW, 0x08d000-0x08dfff:EW, 0x08e000-0x08efff:EW, 0x08f000-0x08ffff:EW, 0x090000-0x090fff:EW, 0x091000-0x091fff:EW, 0x092000-0x092fff:EW, 0x093000-0x093fff:EW, 0x094000-0x094fff:EW, 0x095000-0x095fff:EW, 0x096000-0x096fff:EW, 0x097000-0x097fff:EW, 0x098000-0x098fff:EW, 0x099000-0x099fff:EW, 0x09a000-0x09afff:EW, 0x09b000-0x09bfff:EW, 0x09c000-0x09cfff:EW, 0x09d000-0x09dfff:EW, 0x09e000-0x09efff:EW, 0x09f000-0x09ffff:EW, 0x0a0000-0x0a0fff:EW, 0x0a1000-0x0a1fff:EW, 0x0a2000-0x0a2fff:E, 0x0a3000-0x0a3fff:E, 0x0a4000-0x0a4fff:E, 0x0a5000-0x0a5fff:E, 0x0a6000-0x0a6fff:E, 0x0a7000-0x0a7fff:S, 0x0a8000-0x0a8fff:S, 0x0a9000-0x0a9fff:S, 0x0aa000-0x0aafff:S, 0x0ab000-0x0abfff:S, 0x0ac000-0x0acfff:S, 0x0ad000-0x0adfff:S, 0x0ae000-0x0aefff:S, 0x0af000-0x0affff:S, 0x0b0000-0x0b0fff:S, 0x0b1000-0x0b1fff:S, 0x0b2000-0x0b2fff:S, 0x0b3000-0x0b3fff:S, 0x0b4000-0x0b4fff:S, 0x0b5000-0x0b5fff:S, 0x0b6000-0x0b6fff:S, 0x0b7000-0x0b7fff:S, 0x0b8000-0x0b8fff:S, 0x0b9000-0x0b9fff:S, 0x0ba000-0x0bafff:S, 0x0bb000-0x0bbfff:S, 0x0bc000-0x0bcfff:S, 0x0bd000-0x0bdfff:S, 0x0be000-0x0befff:S, 0x0bf000-0x0bffff:S, 0x0c0000-0x0c0fff:S, 0x0c1000-0x0c1fff:S, 0x0c2000-0x0c2fff:S, 0x0c3000-0x0c3fff:S, 0x0c4000-0x0c4fff:S, 0x0c5000-0x0c5fff:S, 0x0c6000-0x0c6fff:S, 0x0c7000-0x0c7fff:S, 0x0c8000-0x0c8fff:S, 0x0c9000-0x0c9fff:S, 0x0ca000-0x0cafff:S, 0x0cb000-0x0cbfff:S, 0x0cc000-0x0ccfff:S, 0x0cd000-0x0cdfff:S, 0x0ce000-0x0cefff:S, 0x0cf000-0x0cffff:S, 0x0d0000-0x0d0fff:S, 0x0d1000-0x0d1fff:S, 0x0d2000-0x0d2fff:S, 0x0d3000-0x0d3fff:S, 0x0d4000-0x0d4fff:S, 0x0d5000-0x0d5fff:S, 0x0d6000-0x0d6fff:S, 0x0d7000-0x0d7fff:S, 0x0d8000-0x0d8fff:S, 0x0d9000-0x0d9fff:S, 0x0da000-0x0dafff:W, 0x0db000-0x0dbfff:W, 0x0dc000-0x0dcfff:W, 0x0dd000-0x0ddfff:W, 0x0de000-0x0defff:W, 0x0df000-0x0dffff:W, 0x0e0000-0x0e0fff:EW, 0x0e1000-0x0e1fff:EW, 0x0e2000-0x0e2fff:EW, 0x0e3000-0x0e3fff:EW, 0x0e4000-0x0e4fff:EW, 0x0e5000-0x0e5fff:EW, 0x0e6000-0x0e6fff:EW, 0x0e7000-0x0e7fff:EW, 0x0e8000-0x0e8fff:EW, 0x0e9000-0x0e9fff:EW, 0x0ea000-0x0eafff:EW, 0x0eb000-0x0ebfff:EW, 0x0ec000-0x0ecfff:EW, 0x0ed000-0x0edfff:EW, 0x0ee000-0x0eefff:EW, 0x0ef000-0x0effff:EW, 0x0f0000-0x0f0fff:EW, 0x0f1000-0x0f1fff:EW, 0x0f2000-0x0f2fff:EW, 0x0f3000-0x0f3fff:EW, 0x0f4000-0x0f4fff:EW, 0x0f5000-0x0f5fff:EW, 0x0f6000-0x0f6fff:EW, 0x0f7000-0x0f7fff:EW, 0x0f8000-0x0f8fff:EW, 0x0f9000-0x0f9fff:EW, 0x0fa000-0x0fafff:EW, 0x0fb000-0x0fbfff:EW, 0x0fc000-0x0fcfff:S, 0x0fd000-0x0fdfff:S, 0x0fe000-0x0fefff:EW, 0x0ff000-0x0fffff:EW Erase/write done. Verifying flash... VERIFIED. -- Sincerely yours, Alexey Kardapoltsev. +7 (917) 777-10-60

1 0

Fwd: BIOS Write Enable bit problem.
by Rich Futyma Feb. 8, 2013

Feb. 8, 2013

Guys, Does anyone know why bit 0 in the BIOS Control register cannot be set using Intel® X79 Express Chipset. This is what I get when running: flashrom -r /tmp/bios.rom -p internal or flashrom -w xx.rom -p internal *Warning: Setting Bios Control at 0xdc from 0x2a to 0x0b on X79 failed.* *New value is 0x2a.* The read command completes and I get the correct data, but subsequently when I try to erase and program my flash (./flashrom -w xx.rom -p internal:ich_spi_force=yes) I get FCERR (on the first sector erase) which implies that the BIOS is write protected. Thank you in advance for any advice. ---- Rich Futyma ** [image: Inline image 1] CONFIDENTIALITY This e-mail message and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail message, you are hereby notified that any dissemination, distribution or copying of this e-mail message, and any attachments thereto, is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender and permanently delete the original and any copies of this email and any prints thereof. ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the Uniform Electronic Transactions Act or the applicability of any other law of similar substance and effect, absent an express statement to the contrary hereinabove, this e-mail message its contents, and any attachments hereto are not intended to represent an offer or acceptance to enter into a contract and are not otherwise intended to bind the sender, Sanmina Corporation (or any of its subsidiaries), or any other person or entity.

1 0

Re: [flashrom] ASUS P5GC: BIOS erased after after `flashrom -r`f (was: a serious problem to solve)
by Paul Menzel Feb. 8, 2013

Feb. 8, 2013

Dear Henry, Am Freitag, den 08.02.2013, 21:41 +0100 schrieb Henry Blanco Lores: > Hello guys, I have subscribed to this mailing list looking for some help > about the use of the flashrom tool. > The problem is this: > > A friend of mine who has just started using Linux, was testing some tools > and not reading carefully their corresponding manuals, he executed this > command: flashrom -r normally that should not cause any problems as it just tries to read the flash chip content. flashrom is very careful to not break anything, so it is very unlikely that the problem was caused by this command. > and this seems to have erased the BIOS of his PC. This is my guess because > he just told me by phone that not even the video signal was working. You have to be very specific. 1. What Linux distribution did your friend use? What version of flashrom? The packaged one? 2. What did your friend exactly do? Did he see any error messages from flashrom. I guess he just shut the system down? > His motherboard is an ASUS P5GC. A similar board seems to be supported [1]. So the problem is even stranger. > Is it possible to recover the BIOS back to the previous state?? If it was really deleted/erased or a bad image was flashed, then you have to reprogram the chip either with a flash chip programmer. One way is to find a motherboard where the chip fits and reprogram it there by hot swapping it. If that is not possible ask around in your local hacker community or find a shop which does it. > Please, I will be looking forward for your comments. I wish you good luck with recovery! You should also join the #flashrom IRC channel on irc.freenode.net. Thanks, Paul [1] http://flashrom.org/Supported_hardware

1 0

Re: [flashrom] a serious problem to solve
by Idwer Vollering Feb. 8, 2013

Feb. 8, 2013

2013/2/8 Henry Blanco Lores <hblanco2009(a)gmail.com>: > Hello guys, I have subscribed to this mailing list looking for some help > about the use of the flashrom tool. > The problem is this: > > A friend of mine who has just started using Linux, was testing some tools > and not reading carefully their corresponding manuals, he executed this > command: flashrom -r > > and this seems to have erased the BIOS of his PC. This is my guess because > he just told me by phone that not even the video signal was working. His > motherboard is an ASUS P5GC. Is it possible to recover the BIOS back to the > previous state?? The above command, 'flashrom -r', will not erase a flash chip. Have your friend either power cycle his machine or remove the mainboard battery (CMOS reset) with mains disconnected. Given the fact that the parameter '-p internal' was not used, he was using an old version of flashrom, version 0.9.3 or older. > > Please, I will be looking forward for your comments. > Thanks in advance. > > H. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

a serious problem to solve
by Henry Blanco Lores Feb. 8, 2013

Feb. 8, 2013

Hello guys, I have subscribed to this mailing list looking for some help about the use of the flashrom tool. The problem is this: A friend of mine who has just started using Linux, was testing some tools and not reading carefully their corresponding manuals, he executed this command: flashrom -r and this seems to have erased the BIOS of his PC. This is my guess because he just told me by phone that not even the video signal was working. His motherboard is an ASUS P5GC. Is it possible to recover the BIOS back to the previous state?? Please, I will be looking forward for your comments. Thanks in advance. H.

1 0

Re: [flashrom] flashrom ignoring ROM layout region
by Stefan Tauner Feb. 8, 2013

Feb. 8, 2013

On Thu, 7 Feb 2013 16:09:45 -0800 John Gainsborough <jgindc1(a)gmail.com> wrote: > Hi Stefan. > > I am now attempting to write to a flashrom using the layout/region > approach. I need to write a region from a 4MB ROM to the beginning of an > 8MB ROM. > The region image from the 4MB ROM is 4,128,768 bytes == 0x3f0000 long and > this file is called image1. > I have defined the 8MB ROM layout in file called romlayout_8MB to be: > > 000000:3effff main > 3f0000:7fffff remainder > > i.e I want to place the contents of file image1 in to the 8MB ROM region > defined as main. > > I invoked flashrom as follows: > > flashrom -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=250k -l romlayout_8MB > -i main -w image1 > > The flash ROM is detected correctly, delay calculated, but then flashrom > immediately returns the error: > "image size doesn't match". > > As always, guidance/suggestions gratefully received. That's one of the other things my patches fix :) The image you supply with -v/-r/-w is always used to present a mapping of the whole chip. The layout information is only used to select the address range inside that mapping. So for vanilla flashrom you have to create an 8MB file and fill the first 4MB with the content you want and continue as you have done. With my patches one can add an image name to any -i parameter (e.g. -i main:main.img) which is then mapped to the corresponding offset. IIRC one has still to supply a whole image with the correct size, but if the needed ranges are also present as "-i images" then it would not be used at all. Similar for the read operations: it would create a whole image with a lot of 0xFFs outside the selected regions and smaller/exact files for the "-i images". Maybe I have some time at the weekend to integrate the patches. I think there is consensus that we want them in and they have been tested by a number of people, so i think it should not break too much :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

3 2

operation details and future changes (was: flashrom ignoring ROM layout region)
by Stefan Tauner Feb. 8, 2013

Feb. 8, 2013

On Fri, 8 Feb 2013 11:08:21 +0100 Mark Marshall <markmarshall14(a)gmail.com> wrote: Hi Mark, > I too would love for these changes to go in. I'm currently working with a > 64MB flash, and > I've got a number of problems, one of which is that flashrom tries to read > the entire flash > before doing anything (which will never be what I want...). It does so to be able to skip blocks that have the wanted content already and to be able to tell you if anything has changed in the case of an error (not so important on external programmes, but very interesting for people writing their live BIOSes and seeing errors). Usually reading does take way less time than erasing/writing or might even speed up the whole process. ATM there is no way to disable this behavior but we plan to do so and IIRC a part of the mentioned patch set is a first step into that direction. > The other problems are: > - That most of flashrom seems to be limited to 2^24 address bits. > (this is relatively easy to fix) We will see about that :) We are of course aware that this is needed quite soon. Do you want to help us with this (mostly testing, but if you like you can also try to create the needed patch)? > - That flashrom thinks a page is always 256 byes (I think I've found > most cases of this, but I'm not sure. What's the granularity flag > for? The flag is there to fix exactly this :) See also http://patchwork.coreboot.org/patch/3757/ Not many chips need this and so we never moved into this direction... do you really need it? > I've also found that flashrom doesn't always do what I expect, and I'm not > sure if this is > by design or not. for instance, if I want to erase my entire flash chip, > it ends up calling > the sector erase on each sector, not by doing a chip-erase? Are these > types of things > written down anywhere? We try to erase the smallest possible blocks first (in order of the eraser array of the chip definition(s) in flashchips.c. This potentially allows to skip writing of block as explained above. It is of course rather useless for the -E/--erase operation, but the code is shared and no one complained yet IIRC (or sent a patch). Most of these details are not documented I think, but some are (in the manpage). Patches for the manpage are welcomed. Everyone is invited to edit the wiki too :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Added chipsets
by Николай Николаев Feb. 8, 2013

Feb. 8, 2013

Added chipsets: AMIC A25LQ16 Eon EN25S64 Eon EN25S10 Eon EN25S20 Eon EN25S40 Eon EN25S80 Eon EN25QH256 Eon EN25QH128 Eon EN25S32 Eon EN25S16 GigaDevice GD25Q10 GigaDevice GD25Q512 GigaDevice GD25Q128B Numonyx (Micron) N25Q128A13 Numonyx (Micron) N25Q128A11 Numonyx (Micron) N25Q256A11 Numonyx (Micron) N25Q256A13 Numonyx (Micron) N25Q512A11 Numonyx (Micron) N25Q512A13 Numonyx (Micron) N25Q00AA13 Numonyx (Micron) M25PX80 Numonyx (Micron) M45PE16 Numonyx (Micron) M45PE80 Numonyx (Micron) M45PE40 Numonyx (Micron) M45PE10 Numonyx (Micron) M45PE20 Sanyo LE25FW403A Sanyo LE25FW418A Sanyo LE25FW806 Sanyo LE25FW808 Spansion S25FL204K Spansion S25FL128S Spansion S25FL256S Spansion S25FL512S Spansion S25FL208K Spansion S25FL116K Fixed wrong description for Sanyo LE25FW203A -- With best regards Nikolay Nikolaev С Уважением Николаев Николай

1 0

Re: [flashrom] flashrom OPCODES for SPI
by Николай Николаев Feb. 8, 2013

Feb. 8, 2013

The SST25VF040B was added before the new naming scheme was implemented. We > did not want to break any existing software which depends on certain > strings. > Ok i support your fears. it is old chip and has a small capacity. { .vendor = "SST", .name = "SST25VF032B", .bustype = BUS_SPI, .manufacture_id = SST_ID, .model_id = SST_SST25VF032B, .total_size = 4096, .page_size = 256, .feature_bits = FEATURE_WRSR_EWSR, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, .probe_timing = TIMING_ZERO, .block_erasers = { { .eraseblocks = { {4 * 1024, 1024} }, .block_erase = spi_block_erase_20, }, { .eraseblocks = { {32 * 1024, 128} }, .block_erase = spi_block_erase_52, }, { .eraseblocks = { {64 * 1024, 64} }, .block_erase = spi_block_erase_d8, }, { .eraseblocks = { {4 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_60, }, { .eraseblocks = { {4 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_c7, }, }, .printlock = spi_prettyprint_status_register_sst25, /* TODO: check */ .unlock = spi_disable_blockprotect, .write = spi_aai_write, /* what do i see? - this is a fetch */ .read = spi_chip_read, .voltage = {2700, 3600}, }, for example: if i used chip MX25L3205 and i want to change it on SST25VF032B, that i can't reprogram chip because this chip didn't have a AAI OPcodes 0xAD (i can't change opcodes in SPI controller). But i know my controller has a standard codes for reading and page programming. Voltage can be important for external programmer usage. It's not much > effort to add it, anyway. > How will you choose voltage for external program if you want to program MX25L6439E and MX25U6435F? What value we will write to field voltage? > Some SST25VF040B chips identify using the REMS opcode, others use RDID. > Complain to the manufacturer :-) > Sorry but i can't found REMS code in documentation on this chip. Mayby you give me link on pdf and i will be study on my free time. 8) Support for this chip came before the new naming scheme. In the future, > part names like this will be written as "EN25Q80...P" where the dot '.' is > a wildcard for each letter which does not affect programming capabilities. > Ok how will you mark next chips MX25L6439E and MX25U6435F? That chips has a identical chip ID = 0x2537. if if will be MX25.64...(F) that i think it's don't readable. -- With best regards Nikolay Nikolaev С Уважением Николаев Николай

1 0