flashrom

flashrom@flashrom.org

1 participants
9182 discussions

Success: HP Mini 5101 netbook
by David Hendricks 20 Nov '09

20 Nov '09

I'm kicking myself for not getting more verbose output logged when I had the thing in my hands. I did a successful read, and it appears that they hook the firmware EEPROM straight to the southbridge instead of going thru an EC for the Mini :-) Here is a the read output I captured: flashrom v0.9.0-r631 No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. Calibrating delay loop... OK. Found chip "Macronix MX25L8005" (1024 KB) at physical address 0xfff00000. Reading flash... done. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Verbose output of lspci, superiotool and flashrom - PC Chips M863 (unsupported)
by Adrian Glaubitz 20 Nov '09

20 Nov '09

Hi, Hi, tested an PC Chips M863, however the chipset was not detected and therefore flashing was not possible. Please see the attached logs of lspci -nnvvvxxx, superiotool -dV and flashrom -V. Product Website: <http://www.pcchips.com.tw/PCCWebSite/Products/ProductsDetail.aspx?CategoryI…> Adrian

1 0

SUCCESS: Asus K8VXSE
by Adrian Glaubitz 20 Nov '09

20 Nov '09

Hello, I successfully flashed a new BIOS version onto an AsRock K8V8XSE. Used flashrom r767. Did not yet reboot the machine because someone is still logged in but since the board verified I suspect it's working fine. Please see the attached logs and mark the board as *supported*. Thanks, Adrian

1 0

FAIL: Gigabyte GA-8IPE1000Pro2, board still intact, couldn't erase
by Adrian Glaubitz 20 Nov '09

20 Nov '09

Hi, I tried flashing an Gigabyte GA-8IPE1000Pro2. Erasing the flash failed, however, the flash is still intact. Please see the attached logs of lspci -nnvvvxxx, superiotool -dV and flashrom -V plus the output for the failed flash attempt. Adrian

1 0

[PATCH] Totally generic SPI chip match
by Carl-Daniel Hailfinger 19 Nov '09

19 Nov '09

If a chip is not on the RDID generic vendor list nor on the REMS specific ID list, flashrom will claim that no chip is there. Handle these cases gracefully. flashrom will ignore generic matches if a specific chip was found, so this will have no impact on supported chips, but help a lot for a first quick analysis by the user or developer. The only drawback is that unknown chips may be recognized multiple times until they are added to flashchips.[ch]. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-spi_totally_generic_probe/flashchips.c =================================================================== --- flashrom-spi_totally_generic_probe/flashchips.c (Revision 664) +++ flashrom-spi_totally_generic_probe/flashchips.c (Arbeitskopie) @@ -3167,5 +3167,32 @@ .read = NULL, }, + { + .vendor = "Generic", + .name = "unknown SPI chip (RDID)", + .bustype = CHIP_BUSTYPE_SPI, + .manufacture_id = GENERIC_MANUF_ID, + .model_id = GENERIC_DEVICE_ID, + .total_size = 0, + .page_size = 256, + .tested = TEST_BAD_PREW, + .probe = probe_spi_rdid, + .erase = NULL, + .write = NULL, + }, + { + .vendor = "Generic", + .name = "unknown SPI chip (REMS)", + .bustype = CHIP_BUSTYPE_SPI, + .manufacture_id = GENERIC_MANUF_ID, + .model_id = GENERIC_DEVICE_ID, + .total_size = 0, + .page_size = 256, + .tested = TEST_BAD_PREW, + .probe = probe_spi_rems, + .erase = NULL, + .write = NULL, + }, + { NULL } }; Index: flashrom-spi_totally_generic_probe/flashchips.h =================================================================== --- flashrom-spi_totally_generic_probe/flashchips.h (Revision 664) +++ flashrom-spi_totally_generic_probe/flashchips.h (Arbeitskopie) @@ -34,6 +34,7 @@ * SPI parts have 16-bit device IDs if they support RDID. */ +#define GENERIC_MANUF_ID 0xffff /* Check if there is a vendor ID */ #define GENERIC_DEVICE_ID 0xffff /* Only match the vendor ID */ #define ALLIANCE_ID 0x52 /* Alliance Semiconductor */ Index: flashrom-spi_totally_generic_probe/spi.c =================================================================== --- flashrom-spi_totally_generic_probe/spi.c (Revision 664) +++ flashrom-spi_totally_generic_probe/spi.c (Arbeitskopie) @@ -274,6 +274,11 @@ GENERIC_DEVICE_ID == flash->model_id) return 1; + /* Test if there is any vendor ID. */ + if (GENERIC_MANUF_ID == flash->manufacture_id && + id1 != 0xff) + return 1; + return 0; } @@ -329,6 +334,11 @@ GENERIC_DEVICE_ID == flash->model_id) return 1; + /* Test if there is any vendor ID. */ + if (GENERIC_MANUF_ID == flash->manufacture_id && + id1 != 0xff) + return 1; + return 0; } -- http://www.hailfinger.org/

2 4

[commit] r767 - trunk
by svn＠flashrom.org 19 Nov '09

19 Nov '09

Author: hailfinger Date: 2009-11-20 02:12:45 +0100 (Fri, 20 Nov 2009) New Revision: 767 Modified: trunk/flashchips.c trunk/flashchips.h trunk/spi.c Log: If a chip is not on the RDID generic vendor list nor on the REMS specific ID list, flashrom will claim that no chip is there. Handle these cases gracefully. flashrom will ignore generic matches if a specific chip was found, so this will have no impact on supported chips, but help a lot for a first quick analysis by the user or developer. The only drawback is that unknown chips may be recognized multiple times until they are added to flashchips.[ch]. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Marc Jones <marcj303(a)gmail.com> Modified: trunk/flashchips.c =================================================================== --- trunk/flashchips.c 2009-11-17 09:57:34 UTC (rev 766) +++ trunk/flashchips.c 2009-11-20 01:12:45 UTC (rev 767) @@ -3340,5 +3340,32 @@ .read = NULL, }, + { + .vendor = "Generic", + .name = "unknown SPI chip (RDID)", + .bustype = CHIP_BUSTYPE_SPI, + .manufacture_id = GENERIC_MANUF_ID, + .model_id = GENERIC_DEVICE_ID, + .total_size = 0, + .page_size = 256, + .tested = TEST_BAD_PREW, + .probe = probe_spi_rdid, + .erase = NULL, + .write = NULL, + }, + { + .vendor = "Generic", + .name = "unknown SPI chip (REMS)", + .bustype = CHIP_BUSTYPE_SPI, + .manufacture_id = GENERIC_MANUF_ID, + .model_id = GENERIC_DEVICE_ID, + .total_size = 0, + .page_size = 256, + .tested = TEST_BAD_PREW, + .probe = probe_spi_rems, + .erase = NULL, + .write = NULL, + }, + { NULL } }; Modified: trunk/flashchips.h =================================================================== --- trunk/flashchips.h 2009-11-17 09:57:34 UTC (rev 766) +++ trunk/flashchips.h 2009-11-20 01:12:45 UTC (rev 767) @@ -34,6 +34,7 @@ * SPI parts have 16-bit device IDs if they support RDID. */ +#define GENERIC_MANUF_ID 0xffff /* Check if there is a vendor ID */ #define GENERIC_DEVICE_ID 0xffff /* Only match the vendor ID */ #define ALLIANCE_ID 0x52 /* Alliance Semiconductor */ Modified: trunk/spi.c =================================================================== --- trunk/spi.c 2009-11-17 09:57:34 UTC (rev 766) +++ trunk/spi.c 2009-11-20 01:12:45 UTC (rev 767) @@ -281,6 +281,11 @@ GENERIC_DEVICE_ID == flash->model_id) return 1; + /* Test if there is any vendor ID. */ + if (GENERIC_MANUF_ID == flash->manufacture_id && + id1 != 0xff) + return 1; + return 0; } @@ -340,6 +345,11 @@ GENERIC_DEVICE_ID == flash->model_id) return 1; + /* Test if there is any vendor ID. */ + if (GENERIC_MANUF_ID == flash->manufacture_id && + id1 != 0xff) + return 1; + return 0; }

1 0

flashrom Windows port
by Carl-Daniel Hailfinger 19 Nov '09

19 Nov '09

Hi, what's the current state of the Windows port of flashrom (and DirectIO, for that matter)? I'm willing to review/merge/update anything which brings us closer, as long as functionality on supported platforms is not affected. Patches I'm talking about are: http://patchwork.coreboot.org/patch/97/ (but one of the patches in that mail is missing) http://patchwork.coreboot.org/patch/98/ Subject was: [flashrom] [PATCH] new windows port Regards, Carl-Daniel -- Developer quote of the month: "We are juggling too many chainsaws and flaming arrows and tigers."

1 0

FAIL: AsRock K8Upgrade, weird write behavior, board still intact
by Adrian Glaubitz 18 Nov '09

18 Nov '09

Hi, I tried flashing an AsRock K8Upgrade board (yes, the model name is really "K8Upgrade"). flashrom didn't detect the chipset but it detected the flash chip. I attempted to write the flash which initially seemed to work: flashrom indicated that it was writing some pages however progress was *very* slow (as opposed to the Elitegroup K7S5A which I successfully flashed for example). Thus while the flash was written I already suspected something going wrong. Eventually flashrom gave up. However, when I reread the flash and compared it with the flash before write the images matched. So I suspect the bios is still intact. Please see the attached logs of lspci -nnvvvxxx, superiotool -dV and flashrom -V plus the output for the failed flash attempt. Adrian

1 0

FAIL: Asus P4PE-X, board still intact, couldn't erase
by Adrian Glaubitz 18 Nov '09

18 Nov '09

Hi, I tried flashing an P4PE-X. Erasing the flash failed, however, the flash is still intact. Please see the attached logs of lspci -nnvvvxxx, superiotool -dV and flashrom -V plus the output for the failed flash attempt. Adrian

1 0

FAIL: Asus P5B, board still intact, couldn't erase
by Adrian Glaubitz 18 Nov '09

18 Nov '09

Hi, I tried flashing an P5B today. However, opposed to the previously reported working "Asus P5B Deluxe" in the Wiki, the P5B doesn't seem to be supported. Please see the attached logs of lspci -nnvvvxxx, superiotool -dV and flashrom -V plus the output for the failed flash attempt. Adrian

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom