flashrom

flashrom@flashrom.org

3 participants
9188 discussions

[commit] r1516 - trunk
by repository service 10 Mar '12

10 Mar '12

Author: stefanct Date: Sat Mar 10 20:22:13 2012 New Revision: 1516 URL: http://flashrom.org/trac/flashrom/changeset/1516 Log: Add (untested) board enable for ASUS TUSL2-C Primary IDs SMBus controller, secondary IDs MCH. The reverse engineering was done by Michael Karcher. Андрей Тимираев <dark_prof(a)mail.ru> reported the problem, but did not reply (yet) to our propsed fix. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Michael Karcher <flashrom(a)mkarcher.dialup.fu-berlin.de> Modified: trunk/board_enable.c trunk/print.c Modified: trunk/board_enable.c ============================================================================== --- trunk/board_enable.c Thu Mar 8 23:01:25 2012 (r1515) +++ trunk/board_enable.c Sat Mar 10 20:22:13 2012 (r1516) @@ -1529,6 +1529,7 @@ * - ASUS P5GD2 Premium: Intel LGA775 + 915G + ICH6R * - ASUS P5GDC Deluxe: Intel socket775 + 915P + ICH6R * - ASUS P5PE-VM: Intel LGA775 + 865G + ICH5 + * - ASUS TUSL2-C: Intel socket370 + 815 + ICH2 * - Samsung Polaris 32: socket478 + 865P + ICH5 */ static int intel_ich_gpio21_raise(void) @@ -2173,6 +2174,7 @@ {0x10DE, 0x0260, 0x1043, 0x81BC, 0x10DE, 0x026C, 0x1043, 0x829E, "^P5N-D$", NULL, NULL, P3, "ASUS", "P5N-D", 0, OK, it8718f_gpio63_raise}, {0x10DE, 0x0260, 0x1043, 0x81BC, 0x10DE, 0x026C, 0x1043, 0x8249, "^P5N-E SLI$",NULL, NULL, P3, "ASUS", "P5N-E SLI", 0, NT, it8718f_gpio63_raise}, {0x8086, 0x24dd, 0x1043, 0x80a6, 0x8086, 0x2570, 0x1043, 0x8157, NULL, NULL, NULL, P3, "ASUS", "P5PE-VM", 0, OK, intel_ich_gpio21_raise}, + {0x8086, 0x2443, 0x1043, 0x8027, 0x8086, 0x1130, 0x1043, 0x8027, NULL, NULL, NULL, P3, "ASUS", "TUSL2-C", 0, NT, intel_ich_gpio21_raise}, {0x10b7, 0x9055, 0x1028, 0x0082, 0x8086, 0x7190, 0, 0, NULL, NULL, NULL, P3, "Dell", "OptiPlex GX1", 0, OK, intel_piix4_gpo30_lower}, {0x8086, 0x3590, 0x1028, 0x016c, 0x1000, 0x0030, 0x1028, 0x016c, NULL, NULL, NULL, P3, "Dell", "PowerEdge 1850", 0, OK, intel_ich_gpio23_raise}, {0x10de, 0x03ea, 0x1019, 0x2602, 0x10de, 0x03e0, 0x1019, 0x2602, NULL, NULL, NULL, P3, "Elitegroup", "GeForce6100SM-M", 0, OK, board_ecs_geforce6100sm_m}, Modified: trunk/print.c ============================================================================== --- trunk/print.c Thu Mar 8 23:01:25 2012 (r1515) +++ trunk/print.c Sat Mar 10 20:22:13 2012 (r1516) @@ -706,6 +706,7 @@ B("ASUS", "P8H67-M PRO", 0, NULL, "Probing works (Macronix MX25L3205, 4096 kB, SPI), but parts of the flash are problematic: descriptor is r/o (conforming to ICH reqs), ME region is locked."), B("ASUS", "P8P67 (rev. 3.1)", 0, NULL, "Probing works (Macronix MX25L3205, 4096 kB, SPI), but parts of the flash are problematic: descriptor is r/o (conforming to ICH reqs), ME region is locked."), B("ASUS", "P8Z68-V PRO", 0, NULL, "Probing works (Winbond W25Q64, 8192 kB, SPI), but parts of the flash are problematic: descriptor is r/o (conforming to ICH reqs), ME region is locked."), + B("ASUS", "TUSL2-C", 0, "http://support.asus.com/download.aspx?SLanguage=en&p=1&s=4&m=TUSL2-C&os=&ha…", "Untested board enable."), B("ASUS", "Z8NA-D6C", 1, "http://www.asus.com/Server_Workstation/Server_Motherboards/Z8NAD6C/", NULL), B("ASUS", "Z8PE-D12", 1, "http://www.asus.com/Server_Workstation/Server_Motherboards/Z8PED12/", NULL), B("BCOM", "WinNET100", 1, "http://www.coreboot.org/BCOM_WINNET100", "Used in the IGEL-316 thin client."),

1 0

bug
by Андрей Тимираев 10 Mar '12

10 Mar '12

[darkprof@SUT tusl-2c]$ sudo flashrom -w 1014tc.001 Пароль: flashrom v0.9.5.1-r1509 on Linux 3.0-ARCH (i686), built with libpci 3.1.9, GCC 4.6.2 20120120 (prerelease), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. sh: dmidecode: команда не найдена dmidecode execution unsuccessful - continuing without DMI info Found chipset "Intel ICH2". Enabling flash write... OK. Found Winbond flash chip "W49V002FA" (256 kB, FWH) at physical address 0xfffc0000. === This flash part has status UNTESTED for operations: ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -VE, -Vw), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0000ffff: 0xfee7 ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0003ffff: 0x36050 ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. Good. It seems nothing was changed. Writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. [darkprof@SUT tusl-2c]$ sudo flashrom -Vw 1014tc.001 Пароль: flashrom v0.9.5.1-r1509 on Linux 3.0-ARCH (i686), built with libpci 3.1.9, GCC 4.6.2 20120120 (prerelease), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 476M loops per second, delay more than 10% too short (got 84% of expected delay), recalculating... 380M loops per second, delay more than 10% too short (got 69% of expected delay), recalculating... 364M loops per second, delay more than 10% too short (got 65% of expected delay), recalculating... 525M loops per second, 10 myus = 10 us, 100 myus = 93 us, 1000 myus = 1022 us, 10000 myus = 15445 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. sh: dmidecode: команда не найдена dmidecode execution unsuccessful - continuing without DMI info Found chipset "Intel ICH2" with PCI ID 8086:2440. Enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 OK. The following protocols are supported: FWH. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, 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 0xda, id2 0x32 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x32 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 0xda, id2 0x32 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0x32 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0x32 Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, 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 ST M50FLW040A, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, 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 0x25, id2 0xdc, 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 0x25, id2 0xdc, 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 0xda, id2 0x32 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0x32 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0x32 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0x32 Found Winbond flash chip "W49V002FA" (256 kB, FWH) at physical address 0xfffc0000. 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 0xda, id2 0x32 Found Winbond flash chip "W49V002FA" (256 kB, FWH). === This flash part has status UNTESTED for operations: ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -VE, -Vw), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x00ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0000ffff: 0xfee7 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0x03ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0003ffff: 0x36050 ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything changed. Good. It seems nothing was changed. Writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. Restoring PCI config space for 00:1f:0 reg 0x4e [darkprof@SUT tusl-2c]$

3 3

Re: [flashrom] Dediprog programming is slow
by Carl-Daniel Hailfinger 10 Mar '12

10 Mar '12

Hi Jeff, Am 10.03.2012 05:52 schrieb jeff(a)linuxwest.com: > Thank you for the impressive work in this app! Glad to hear it works for you. > This is only my first time using Flashrom to write the bios file so I don't know > what is considered normal. The software provided by Dediprog writes the same > file in much less time it takes Flashrom to do it. I wonder if that's because > Flashrom will first erase the chip and then "In the process the chip is also > read several times"? No, it's because your flashrom version does not have the dediprog write speedup. You need at least 0.9.4-r1477 for a reasonable write speed (it won't help for all flash chips, but a majority of them). > Is it possible to bypass the erasing and in-memory backup operations to save > time? The slowness is with the "--noverify" option enabled. --noverify will save maybe 10 seconds if you're lucky. The slow write speed is caused by an incomplete dediprog driver in v0.9.4-r1395. > If I flash with the same image, it is really fast. Perhaps that is expected. But > notice in my attachment, it's taking 20 mins to flash 8M. You should get almost native speed (like the Windows tool from Dediprog) with latest flashrom unless your flash chip uses the AAI or write_1 methods. We're working to provide native speed for all SPI flash chips, but it depends on testers. > Also, something important I really want to know is if it is possible to run more > than one instance of flashrom at the same time (two dediprogs)? Do you own multiple Dediprogs? If yes, it would be very interesting to know how the Windows Dediprog tool differentiates between the two, and what flashrom does if it sees two Dediprogs (it will probably just ignore the second one). I'm willing to add support for concurrent flashrom instances (one per programmer) to the Dediprog driver if you're willing to test. Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

Dediprog programming is slow
by jeff＠linuxwest.com 09 Mar '12

09 Mar '12

1 0

Report for HP ProBook 4510s NX693EA for READ operation.
by user 09 Mar '12

09 Mar '12

Report for HP ProBook 4510s NX693EA for READ operation.

1 0

Re: [flashrom] FlashRom and Intel C204 chipset.
by Stefan Tauner 09 Mar '12

09 Mar '12

On Wed, 12 Oct 2011 22:01:01 +0400 "Andrey V. Bondarenko" <avbondarenko(a)gmail.com> wrote: > Hello, > > Verbose output is in the attachment file for chipset Intel C204. I sent this > e-mail because it was suggested to send report. > > # ./flashrom --read ./P8B-E-4L-ASUS-0602.ROM > flashrom v0.9.4-r1395 on Linux 2.6.18-274.3.1.el5.028stab094.3 (x86_64), > built with libpci 3.1.7, GCC 4.1.2 20080704 (Red Hat 4.1.2-51), little > endian > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > Found chipset "Intel C204". > 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... OK. > This chipset supports the following protocols: FWH, SPI. > Found Winbond flash chip "W25Q64" (8192 kB, SPI) at physical address > 0xff800000. > Reading flash... Transaction error! > Read operation failed! > FAILED. hello and thanks for your report. this is another case of a locked Management Engine (ME) region, which we can't unlock yet. i have added the P8B-E/4L to our list of boards with a note about the problem for now and will commit that later. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Report for chipset "Intel Q67" on a GA-Q67M-D2H-B3 motheboard.
by user 09 Mar '12

09 Mar '12

Sorry for my previous report. Report for chipset "Intel Q67" on a GA-Q67M-D2H-B3 motheboard for READ operation.

1 0

working card
by RiCH ＠ gmail 09 Mar '12

09 Mar '12

rfm6@amd64:~/ipxe/src$ sudo flashrom -p nicintel flashrom v0.9.4-r1394 on Linux 3.0.0-12-generic (i686), built with libpci 3.1.7, GCC 4.6.1, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found "Intel 82557/8/9/0/1 Ethernet Pro 100" (8086:1229, BDF 04:08.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Found "Intel 82557/8/9/0/1 Ethernet Pro 100" (8086:1229, BDF 04:08.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Mapping Intel NIC control/status reg at 0xfdaff000, unaligned size 0x10. Found Atmel flash chip "AT49BV512" (64 kB, Parallel) on nicintel. No operations were specified. rfm6@amd64:~/ipxe/src$ sudo flashrom -p nicintel -w test.rom [sudo] password for rfm6: flashrom v0.9.4-r1394 on Linux 3.0.0-12-generic (i686), built with libpci 3.1.7, GCC 4.6.1, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found "Intel 82557/8/9/0/1 Ethernet Pro 100" (8086:1229, BDF 04:08.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Found "Intel 82557/8/9/0/1 Ethernet Pro 100" (8086:1229, BDF 04:08.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === Mapping Intel NIC control/status reg at 0xfdaff000, unaligned size 0x10. Found Atmel flash chip "AT49BV512" (64 kB, Parallel) on nicintel. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.

1 0

[PATCH] flashrom 0.9.5.1
by Carl-Daniel Hailfinger 08 Mar '12

08 Mar '12

Increase flashrom release number to 0.9.5.2 Informal ack by Stefan Tauner on IRC. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Index: flashrom-0.9.5.2-release/Makefile =================================================================== --- flashrom-0.9.5.2-release/Makefile (Revision 1513) +++ flashrom-0.9.5.2-release/Makefile (Arbeitskopie) @@ -277,7 +277,7 @@ # will not require subversion. The downloadable snapshots are already exported. SVNVERSION := $(shell LC_ALL=C svnversion -cn . 2>/dev/null | sed -e "s/.*://" -e "s/$[0-9]*$.*/\1/" | grep "[0-9]" || LC_ALL=C svn info . 2>/dev/null | awk '/^Revision:/ {print $$2 }' | grep "[0-9]" || LC_ALL=C git svn info . 2>/dev/null | awk '/^Revision:/ {print $$2 }' | grep "[0-9]" || echo unknown) -RELEASE := 0.9.5.1 +RELEASE := 0.9.5.2 VERSION := $(RELEASE)-r$(SVNVERSION) RELEASENAME ?= $(VERSION) -- http://www.hailfinger.org/

1 2

[commit] r1515 - tags/flashrom-0.9.5.2
by repository service 08 Mar '12

08 Mar '12

Author: hailfinger Date: Thu Mar 8 23:01:25 2012 New Revision: 1515 URL: http://flashrom.org/trac/flashrom/changeset/1515 Log: Tag flashrom 0.9.5.2 Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Added: tags/flashrom-0.9.5.2/ - copied from r1514, trunk/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom