flashrom

flashrom@flashrom.org

6 participants
9186 discussions

Pegatron IPP7A-CP: flashrom -V
by Илья Шипко 02 Nov '13

02 Nov '13

root@qgear:/home/psihiatr# flashrom -V flashrom v0.9.5.2-r1517 on Linux 3.2.0-51-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 2 usecs, 767M loops per second, 10 myus = 10 us, 100 myus = 147 us, 1000 myus = 1023 us, 10000 myus = 10018 us, 8 myus = 15 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "nVidia" DMI string system-product-name: "MCP79" DMI string system-version: "To Be Filled By O.E.M." DMI string baseboard-manufacturer: "To be filled by O.E.M." DMI string baseboard-product-name: "To be filled by O.E.M." DMI string baseboard-version: "1.00" DMI string chassis-type: "Desktop" Found chipset "NVIDIA MCP79" with PCI ID 10de:0aad. This chipset is marked as untested. If you are using an up-to-date version of flashrom please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... This chipset is not really supported yet. Guesswork... ISA/LPC bridge reg 0x8a contents: 0x40, bit 6 is 1, bit 5 is 0 Flash bus type is SPI SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! Found SMBus device 10de:0aa2 at 00:03:2 MCP SPI BAR is at 0xfae80000 Mapping NVIDIA MCP6x SPI at 0xfae80000, 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. The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Chip status register is 00 Chip status register: Status Register Write Disable (SRWD) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 / Block Protect 3 (BP3) is not set Chip status register: Bit 4 / Block Protect 2 (BP2) is not set Chip status register: Bit 3 / Block Protect 1 (BP1) is not set Chip status register: Bit 2 / Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Found Macronix flash chip "MX25L8005" (1024 kB, SPI) at physical address 0xfff00000. Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25LF080A, 1024 kB: probe_spi_res2: id1 0x13, id2 0x13 Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xc2, id2 0x13 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xc2, id2 0x13 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xc2, id2 0x13 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2014 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xc2, id2 0x13 Found Macronix flash chip "MX25L8005" (1024 kB, SPI). No operations were specified. root@qgear:/home/psihiatr# flashrom -w IPP7A-CP-0505.rom flashrom v0.9.5.2-r1517 on Linux 3.2.0-51-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA MCP79". This chipset is marked as untested. If you are using an up-to-date version of flashrom 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... SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! Mapping NVIDIA MCP6x SPI at 0xfae80000, unaligned size 0x544. 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. Found Macronix flash chip "MX25L8005" (1024 kB, SPI) at physical address 0xfff00000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.

1 0

Bricked an Asus Pundit P1-AH1 barebones desktop system
by Jason M. 01 Nov '13

01 Nov '13

Dear flashrom, I just managed to brick my nice little Asus Pundit P1-AH1 barebones desktop system. While researching for this e-mail, I figured out what happened: I grabbed the updated BIOS from Asus' web site for P1-PH1, rather than P1-AH1. Apparently, I believed Google's search results when they sent me to Asus' web site for AH1, but this time I noted the model discrepancy and did not get back the same BIOSes when I changed to the correct model. Knowing Asus, the PH1 model is likely an Intel CPU, where the AH1 model uses an AMD CPU. I had BIOS 0301, and used flashrom to flash to 0801. There is no 0801 for the AH1 model, but there is for the PH1 model. Flashrom read my 0301 BIOS to a file, that matched the exact byte count of the 0801 BIOS I had downloaded and extracted as a BIN file. I ran the flashrom -w with the 0801 BIN file, it wrote and verified and exited success. I ran the -v and it re-verified success. (I'm using instructions found at https://wiki.archlinux.org/index.php/Flashing_BIOS_from_Linux, including their reference to http://www.flashrom.org/Flashrom). There was no indication of any kind of mismatch. Since all those things were a success, I rebooted. Got a black screen, with power LED on. I shut down using front power button for a minute, turned on, got black screen, power LED on (no HDD activity). System was willing to turn off using ten second "shutdown override." I pulled the power cord for ten minutes: Now, system fan comes on full power, power button did not do anything (no power LED). Eventually I discovered that the ten second override would shut the fan off (never heard it go full blast before). There is a red recessed small-object-only reset button at the top of the Pundit's front panel. I could not change the basic No POST symptom with this, but I have not tracked down documentation on how to use it correctly (there's usually something about holding your mouth this way or that while pressing it). Now I get a single flash from the HDD LED when I press the front power button, no power LED, and full power fan. Shutdown override still works. Identifying info: Make: Asus Marketing model: Pundit P1-AH1 Back sticker model: AS P1-AH1 A8N8L Serial number: 64P0AL018820 MB model: A8N8L Chipset: Nvidia MCP 51/Crush 51PV (AH1 manual page 54, MB block diagram) Flash BIOS chip (I think): PMC Flash BIOS BIN file sizes: All files are 524,288 bytes (512 KB) Relevant links I used: Discussion of MB model number versus system model name: http://vip.asus.com/forum/view.aspx?board_id=8&model=P1-AH1&id=200612010005… Page I accidentally got BIOS from: http://support.asus.com/download.aspx?SLanguage=en&p=8&s=7&m=P1-PH1 Page I should have gotten BIOS from: http://support.asus.com/download.aspx?SLanguage=en&m=P1-AH1 (latest BIOS for AH1 is 0402, not 0801) I'm surprised I made this mistake, I've several decades experience maintaining personal computers. You may share this e-mail with the public mailing list, but I prefer to be known as Jason-without-an-email-address. If you have any suggestion what I can try next let me know. The point of the exercise was to get support for the latest of the Socket 939 AMD CPUs. This is a nice little living room system, very quiet. I could not find the motherboard for sale on Google or eBay, nor the system for that matter; it dates to about 2006. Thanks, Jason M.

1 0

Re: [flashrom] Issues updating MX25L3206E
by Marc Pascual 31 Oct '13

31 Oct '13

On Thu, Oct 31, 2013 at 7:05 AM, David Hendricks <dhendrix(a)google.com>wrote: > On Wed, Oct 30, 2013 at 12:08 AM, marc pascual <marcmpascual(a)gmail.com>wrote: > >> Hello, >> >> I have an HP DL165 G7 and I applied the latest BIOS image from HP. >> >> root# flashrom -p internal:amd_imc_force=yes -w >> /var/tmp/2012.07.27.A-O37_0727.ROM -c MX25L3206E >> >> flashrom v0.9.7-r1711 on Linux 2.6.32-358.2.1.el6.x86_64 (x86_64) >> flashrom is free software, get the source code at http://www.flashrom.org >> >> Calibrating delay loop... OK. >> Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... Writes >> have been disabled for safety reasons because the presence of the IMC >> was detected and it could interfere with accessing flash memory. Flashrom >> will >> try to disable it temporarily but even then this might not be safe: >> when it is reenabled and after a reboot it expects to find working code >> in the flash and it is unpredictable what happens if there is none. >> >> To be safe make sure that there is a working IMC firmware at the right >> location in the image you intend to write and do not attempt to erase. >> >> You can enforce write support with the amd_imc_force programmer option. >> Continuing with write support because the user forced us to! >> OK. >> Found Macronix flash chip "MX25L3206E" (4096 kB, SPI) at physical address >> 0xffc00000. >> Reading old flash chip contents... done. >> Erasing and writing flash chip... Erase/write done. >> Verifying flash... VERIFIED. >> >> However after rebooting the machine once, I'm getting this message: >> >> Detect a Unsame SDRR/Configuration Image in Current BIOS >> BMC SDRR Version : 2.37.0.98 --> 2.33.1.226 >> Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF >> Erasing Sectors Done! >> Uploading SDRR: 100% >> Uploading Configuration: 100% >> Update SDRR/Configuration Image successfully >> Resetting BMC.... >> >> The machine reboots itself again, and I see the same message the second >> time around. It reboots itself again. >> >> This time, it can't find my local disk: >> >> Reboot and Select proper Boot device >> or Insert Boot Media in selected Boot device and press a key >> >> I issue a reset, then everything seems to be fine from here. >> >> /./-> reset /system1/console1 >> System1 reset. >> >> /./-> start /system1/console1 >> ... >> (boots to the OS) >> >> >> Is this normal, or is this related to the warning about IMC being >> detected? >> > > This seems normal for the HP DL165 G7. In general, Flashrom does not know > about vendor-specific BMCs. I guess that the BMC configuration is stored on > the same ROM as the BIOS, so flashing the .ROM file provided by HP wipes it > out and the BMC must be re-configured. > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. > Thanks for your response. It does seem normal. I was able to replicate this consistently -- only happens when downgrading from a higher ROM version. I don't know what's exactly going on, but what happens is that after a reboot, it downgrades the "BMC SDRR", resets the BMC, updates it again to the previous version (what it was before), and finally resets the BMC for the second time. root# dmidecode -t bios # dmidecode 2.11 SMBIOS 2.7 present. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: HP Version: O37 Release Date: 10/17/2012 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 4096 kB root# flashrom -p internal:amd_imc_force=yes -w /var/tmp/2012.07.27.A-O37_0727.ROM -c MX25L3206E (reboot) Detect a Unsame SDRR/Configuration Image in Current BIOS BMC SDRR Version : 2.37.0.98 --> 2.33.1.226 Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF Erasing Sectors Done! Uploading SDRR: 100% Uploading Configuration: 100% Update SDRR/Configuration Image successfully Resetting BMC. Detect a Unsame SDRR/Configuration Image in Current BIOS BMC SDRR Version : 2.33.1.226 --> 2.37.0.98 Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF Erasing Sectors Done! Uploading SDRR: 100% Uploading Configuration: 100% Update SDRR/Configuration Image successfully Resetting BMC. (... normal boot up follows) I don't know why it does this, but I think I should be asking HP. Regards, Marc

1 0

Re: [flashrom] Issues updating MX25L3206E
by David Hendricks 31 Oct '13

31 Oct '13

On Wed, Oct 30, 2013 at 12:08 AM, marc pascual <marcmpascual(a)gmail.com>wrote: > Hello, > > I have an HP DL165 G7 and I applied the latest BIOS image from HP. > > root# flashrom -p internal:amd_imc_force=yes -w > /var/tmp/2012.07.27.A-O37_0727.ROM -c MX25L3206E > > flashrom v0.9.7-r1711 on Linux 2.6.32-358.2.1.el6.x86_64 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... Writes have > been disabled for safety reasons because the presence of the IMC > was detected and it could interfere with accessing flash memory. Flashrom > will > try to disable it temporarily but even then this might not be safe: > when it is reenabled and after a reboot it expects to find working code > in the flash and it is unpredictable what happens if there is none. > > To be safe make sure that there is a working IMC firmware at the right > location in the image you intend to write and do not attempt to erase. > > You can enforce write support with the amd_imc_force programmer option. > Continuing with write support because the user forced us to! > OK. > Found Macronix flash chip "MX25L3206E" (4096 kB, SPI) at physical address > 0xffc00000. > Reading old flash chip contents... done. > Erasing and writing flash chip... Erase/write done. > Verifying flash... VERIFIED. > > However after rebooting the machine once, I'm getting this message: > > Detect a Unsame SDRR/Configuration Image in Current BIOS > BMC SDRR Version : 2.37.0.98 --> 2.33.1.226 > Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF > Erasing Sectors Done! > Uploading SDRR: 100% > Uploading Configuration: 100% > Update SDRR/Configuration Image successfully > Resetting BMC.... > > The machine reboots itself again, and I see the same message the second > time around. It reboots itself again. > > This time, it can't find my local disk: > > Reboot and Select proper Boot device > or Insert Boot Media in selected Boot device and press a key > > I issue a reset, then everything seems to be fine from here. > > /./-> reset /system1/console1 > System1 reset. > > /./-> start /system1/console1 > ... > (boots to the OS) > > > Is this normal, or is this related to the warning about IMC being detected? > This seems normal for the HP DL165 G7. In general, Flashrom does not know about vendor-specific BMCs. I guess that the BMC configuration is stored on the same ROM as the BIOS, so flashing the .ROM file provided by HP wipes it out and the BMC must be re-configured. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Issues updating MX25L3206E
by marc pascual 30 Oct '13

30 Oct '13

Hello, I have an HP DL165 G7 and I applied the latest BIOS image from HP. root# flashrom -p internal:amd_imc_force=yes -w /var/tmp/2012.07.27.A-O37_0727.ROM -c MX25L3206E flashrom v0.9.7-r1711 on Linux 2.6.32-358.2.1.el6.x86_64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... Writes have been disabled for safety reasons because the presence of the IMC was detected and it could interfere with accessing flash memory. Flashrom will try to disable it temporarily but even then this might not be safe: when it is reenabled and after a reboot it expects to find working code in the flash and it is unpredictable what happens if there is none. To be safe make sure that there is a working IMC firmware at the right location in the image you intend to write and do not attempt to erase. You can enforce write support with the amd_imc_force programmer option. Continuing with write support because the user forced us to! OK. Found Macronix flash chip "MX25L3206E" (4096 kB, SPI) at physical address 0xffc00000. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. However after rebooting the machine once, I'm getting this message: Detect a Unsame SDRR/Configuration Image in Current BIOS BMC SDRR Version : 2.37.0.98 --> 2.33.1.226 Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF Erasing Sectors Done! Uploading SDRR: 100% Uploading Configuration: 100% Update SDRR/Configuration Image successfully Resetting BMC.... The machine reboots itself again, and I see the same message the second time around. It reboots itself again. This time, it can't find my local disk: Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key I issue a reset, then everything seems to be fine from here. /./-> reset /system1/console1 System1 reset. /./-> start /system1/console1 ... (boots to the OS) Is this normal, or is this related to the warning about IMC being detected?

1 0

Re: [flashrom] [PATCH] Ensure DMI strings used in dmi_compare() are not NULL.
by Stefan Tauner 29 Oct '13

29 Oct '13

On Tue, 29 Oct 2013 00:12:50 +0100 Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> wrote: > Previously the external DMI decoder did not allow this to happen because > all possible pointers were initialized at startup by the output of > 'dmidecode -s ...' which has default values for all supported types. > > The now active internal DMI decoder does work differently: it scans the > complete DMI table once and copies the available strings. Therefore, strings > that are not set by the firmware are left at their default value of NULL. > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Idwer reproduced the problem and was able to verify the correctness of this patch (see new, extended commit log), hence Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> and committed in r1763. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

[commit] r1763 - trunk
by repository service 29 Oct '13

29 Oct '13

Author: stefanct Date: Tue Oct 29 02:38:45 2013 New Revision: 1763 URL: http://flashrom.org/trac/flashrom/changeset/1763 Log: Ensure DMI strings used in dmi_compare() are not NULL. Previously the external DMI decoder did not allow this to happen because all possible pointers were initialized at startup by the output of 'dmidecode -s ...' which has default values for all supported types. The now active internal DMI decoder does work differently: it scans the complete DMI table once and copies the available strings. Therefore, strings that are not set by the firmware are left at their default value of NULL. A segfault would arise if the following conditions are all true: - the firmware sets up a DMI/SMBIOS table which has at least a correct checksum, and - that table does *not* define at least one of the DMI strings we use for matching (as defined by dmi_strings[] in dmi.c), and - there exists a board enable whose PCI IDs are matched by the board, and which has a DMI string set that ends with a $ anchor, and - the user calls the internal programmer of flashrom without the optional mainboard parameter. This was first observed by Gelip on an abit BF6 using the coreboot port for the abit BE6-II V2.0. The segfault was reproduced by Idwer Vollering on an ASUS F2A85-M with the default DMI values of CONFIG_MAINBOARD_SMBIOS_MANUFACTURER etc. overwritten and a forged board enable matching his board. Idwer also verified that this patch fixes the problem, thanks a lot! Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Modified: trunk/dmi.c Modified: trunk/dmi.c ============================================================================== --- trunk/dmi.c Sat Oct 26 19:02:03 2013 (r1762) +++ trunk/dmi.c Tue Oct 29 02:38:45 2013 (r1763) @@ -406,8 +406,8 @@ * at the beginning and '$' at the end. So you can look for "^prefix", * "suffix$", "substring" or "^complete string$". * - * @param value The string to check. - * @param pattern The pattern. + * @param value The non-NULL string to check. + * @param pattern The non-NULL pattern. * @return Nonzero if pattern matches. */ static int dmi_compare(const char *value, const char *pattern) @@ -454,9 +454,13 @@ if (!has_dmi_support) return 0; - for (i = 0; i < ARRAY_SIZE(dmi_strings); i++) + for (i = 0; i < ARRAY_SIZE(dmi_strings); i++) { + if (dmi_strings[i].value == NULL) + continue; + if (dmi_compare(dmi_strings[i].value, pattern)) return 1; + } return 0; }

1 0

[PATCH] Ensure DMI strings used in dmi_compare() are not NULL.
by Stefan Tauner 29 Oct '13

29 Oct '13

Previously the external DMI decoder did not allow this to happen because all possible pointers were initialized at startup by the output of 'dmidecode -s ...' which has default values for all supported types. The now active internal DMI decoder does work differently: it scans the complete DMI table once and copies the available strings. Therefore, strings that are not set by the firmware are left at their default value of NULL. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- dmi.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/dmi.c b/dmi.c index 14f3871..ef7ae2c 100644 --- a/dmi.c +++ b/dmi.c @@ -406,8 +406,8 @@ void dmi_init(void) * at the beginning and '$' at the end. So you can look for "^prefix", * "suffix$", "substring" or "^complete string$". * - * @param value The string to check. - * @param pattern The pattern. + * @param value The non-NULL string to check. + * @param pattern The non-NULL pattern. * @return Nonzero if pattern matches. */ static int dmi_compare(const char *value, const char *pattern) @@ -454,9 +454,13 @@ int dmi_match(const char *pattern) if (!has_dmi_support) return 0; - for (i = 0; i < ARRAY_SIZE(dmi_strings); i++) + for (i = 0; i < ARRAY_SIZE(dmi_strings); i++) { + if (dmi_strings[i].value == NULL) + continue; + if (dmi_compare(dmi_strings[i].value, pattern)) return 1; + } return 0; } -- Kind regards, Stefan Tauner

1 0

[PATCH] Add util/pad_image.sh.
by Stefan Tauner 28 Oct '13

28 Oct '13

A convenient POSIX shell script to pad images by prepending or appending constant data to prepare them for flashrom digestion. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- Preparing images for iPXE was a pain without this (I had to build it many times for debugging), and it is probably useful for other use cases too. The only thing missing is a mode that repeats the file every 2^N bytes where 2^N is the nearest larger power of two to the length of the image to be padded, e.g. if you want to write a 256 kB chip in a 3Com NIC that does only support up to 128 kB/is one address line short. And maybe a SI-prefix parser... but first flashrom should get one ;) util/pad_image.sh | 222 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 222 insertions(+) create mode 100755 util/pad_image.sh diff --git a/util/pad_image.sh b/util/pad_image.sh new file mode 100755 index 0000000..30813f4 --- /dev/null +++ b/util/pad_image.sh @@ -0,0 +1,222 @@ +#!/bin/sh +# +# This file is part of the flashrom project. +# +# Copyright (C) 2013 Stefan Tauner +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +# + +assert_cmds_avail () { + while [ $# -gt 0 ]; + do + command -v $1 >/dev/null 2>&1 || { + echo "$1 is required." + exit 1 + } + shift + done +} + +assert_cmds_avail "cat" "cp" "dd" "mv" "printf" "tr" "wc" + +show_help() { + echo "Usage: + $0 [-a|-p] [-h] [-f] -i <infile> [-o <outfile>] -s <size> [-v <val>] + + Copies infile into outfile and fills up the remaining space to size with val. +Options + -h or --help + this message + -a or --append + append the padding (default) + -p or --prepend + prepend the padding + -f or --force + force to overwrite existing output file + -i or --infile <infile> + the input file + -o or --outfile <outfile> + the output file (\"<infile>-padded\" on default) + -s or --size <size> + the wanted size of the output file in bytes + -v or --value <value> + the value in common hexadecimal format to be used for padding (0xFF on default) +" +} + +check_action() { + if [ -n "$action" ]; then + echo "Error: Multiple actions given.">&2 + exit 1 + fi +} + +check_arg() { + if [ -z "$2" ]; then + echo "Error: $1 requires an argument.">&2 + exit 1 + fi +} + + +prepend () { + { tr '\0' $(printf "\\\\%o" "$val") < /dev/zero | dd bs=1 count=$padsize of="$outfile".tmp && \ + cat "$infile" >> "$outfile".tmp && \ + mv -f "$outfile".tmp "$outfile" ; } >/dev/null 2>&1 || \ + return 1 +} + +append () { + { cp "$infile" "$outfile".tmp && tr '\0' $(printf "\\\\%o" "$val") < /dev/zero | \ + dd bs=1 count=$padsize of="$outfile".tmp conv=notrunc seek=$filesize && \ + mv -f "$outfile".tmp "$outfile" ; } >/dev/null 2>&1 || \ + return 1; +} + +main () { + local action= + local outfile= + local infile= + local size= + local val= + local force= + + # The is the main loop + while [ $# -gt 0 ]; + do + case ${1} in + -h|--help) + action=show_help; + shift;; + -a|--append) + check_action $1 + action=append + shift;; + -p|--prepend) + check_action $1 + action=prepend + shift;; + -f|--force) + force=1 + shift;; + -i|--infile) + if [ -z "$infile" ] ; then + check_arg $1 $2 + infile=$2 + else + echo "Error: More than one input file given.">&2; + exit 1 + fi + shift 2;; + -o|--outfile) + if [ -z "$outfile" ] ; then + check_arg $1 $2 + outfile=$2 + else + echo "Error: More than one output file given.">&2; + exit 1 + fi + shift 2;; + -v|--value) + if [ -z "$val" ] ; then + check_arg $1 $2 + val=$2 + else + echo "Error: More than one value given.">&2; + exit 1 + fi + shift 2;; + -s|--size) + if [ -z "$size" ] ; then + check_arg $1 $2 + size=$2 + case $size in + ''|[!0-9]*) echo "Error: Could not parse size $size.">&2; exit 1;; + *) ;; + esac + else + echo "Error: More than one size given.">&2; + exit 1 + fi + shift 2;; + -*) + show_help; + echo "Error: Invalid option: ${1}">&2 + exit 1;; + *) + echo "Error: Overabundant parameter: \"${1}\"">&2 + shift;; + esac; + done + + if [ -z "$infile" ] ; then + show_help + echo "Error: No input file specified">&2 + exit 1 + fi + + if [ ! -e "$infile" -o ! -r "$infile" -o ! -w "$infile" ]; then + echo "Error: ${infile} is not accessible">&2 + exit 1 + fi + + if [ -z "$outfile" ] ; then + outfile="${infile}-padded" + fi + + if [ -z "$force" -a -e "$outfile" ]; then + echo "Error: ${outfile} exists already.">&2 + exit 1 + fi + + if [ -z "$size" ] ; then + show_help + echo "Error: No target size specified.">&2 + exit 1 + fi + + filesize=$(wc -c < "$infile") || exit 1 + if [ $size -le $filesize ]; then + echo "File is already as large as or even larger than requested.">&2 + exit 1 + fi + + # default action is to append + if [ -z "$action" ] ; then + action=append + fi + + # default value is all ones + if [ -z "$val" ] ; then + val="0xff" + fi + case $val in + ''|[!a-fA-F0-9]*) echo "Could not parse value $val.">&2; exit 1;; + *) ;; + esac + + padsize=$(($size-$filesize)) + printf "Copy data from file \"%s\" to \"%s\" and pad it from %d B to %d B by %sing 0x%x %d times... " \ + $infile $outfile $filesize $size $action $val $padsize + if $action ; then + echo "done." + else + echo "failed." + return 1 + fi +} + +main $@ -- Kind regards, Stefan Tauner

1 0

Add confirmed board to wiki
by Kyle Bentley 27 Oct '13

27 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can confirm that the Suprmicro X7SPA-H board can be safely flashed using flashrom. A similar board is listed in the wiki, but for the sake of completeness add this one as well. The full verbose flash and verify can be found here if interested: http://kbentley.dyndns.org/data/flashrom-output The flash chip MX25L3205, the chipset is an Intel ICH9. Kyle Bentley - ---------------------- Kyle Bentley kwbent(a)uab.edu UAB Dept of Physics 1300 University Blvd Birmingham, AL - ---------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJSbYEoAAoJEKZ75usGhR84MhYH/0owEQorV8thQXP76iBlBmI1 bsfGQ6PjEukHgVImDaItmSm1Tq18RcAo7G9/1bPeIl0VcFAPYglVkpECmuukKZNz zyu7PjT/jsTd76NDRRmDyut5YXaSujKo6YSxWhjWMZGroo4CZaZmQUqUxcz1JKQS caAhpMbxjR2PWW8zeQfJ6KKtVvcV6a7L2NRZiBUIxa4vY9Mu7Yu+7vjJq/QAvJ8j KJ7ZsvG9nkwzPo8iOeUzWRokNyCeVZJc4sevSaVyiImhvPOcoz6cmX2ObJNC6xdX 7RjBf6sC2BFlzrQL4b3w9c3LJPPbnv3Up6vGBVvt+7b0NQHL7CBdtzIxUoA9M9U= =P+W6 -----END PGP SIGNATURE-----

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom