- flashrom - mail.coreboot.org

Help with Flashing a new Bios for a Asus C90P and Asus C90S
by d3izzymail-asus＠yahoo.com 23 Aug '10

23 Aug '10

Hi I can use any help you guys can offer me with my 2 kinds of Laptops The Asus C90S and the Asus C90P I will Start with the Easy one First the C90S For it alI want to do is simply add more CPUID's to the Bios as I know that you can not just add the raw ID or it will not load or boot at all But I know the CPU I want Will or rather should work it will be arriving tomorrow so I am going to try it. it is the Intel Xeon X3230 CPU SLACS Kentsfield LGA775 and the reason why I think it will work is not the 775 socket but rather that the Intel® Core™2 Extreme Processor QX6700 (8M Cache, 2.66 GHz, 1066 MHz FSB) is almost an exact match for my intel C90S Motherboard with the Intel® i975G Express Chipset with 82801GB I/O Controller Hub 7 (ICH7/R) at least I think based on info obtained from the program CPUID Version 1.55 Also I solved both the Power heat and overall thermal issues buy buying a spare C90P case and heatsink and 150W power Adapter but if that is sill not enough I can get a 230W power Adapter Plus add more copper and extra copper fins to the heat sinks. Also Below is the List of its 975X Chipset Computability List for the QX6700 Chipset its the Intel® 975X Express Chipset (3 Configurations) Intel® 975X Express Chipset with 82801GB I/O Controller Hub 7 (ICH7) # of CPUs: 1 Embedded: No System Price: N/A System TDP: 146.8W Intel® 975X Express Chipset with 82801GDH I/O Controller Hub 7 (ICH7DH) # of CPUs: 1 Embedded: No System Price: N/A System TDP: 146.8W Intel® 975X Express Chipset with 82801GR I/O Controller Hub 7 (ICH7R) # of CPUs: 1 Embedded: No System Price: N/A System TDP: 146.8W So that is what makes me think that if I can just add the Xeon X3230 CPUID and Flash it with all the required Values it will work out ok as my new X3230 is due to arrive here on 08/23/2010 and I know that the Specs are almost Identical vs the QZ6700 as they are these Intel® Xeon® Processor X3230 (8M Cache, 2.66 GHz, 1066 MHz FSB) However I have Absolutely no idea how to make the Program work. As I can Not Do any of the Following things as I don't know how because as odd as this will sound I can make most things work in windows but not dos or the command prompt Let me explain I have difficulty making things work if I have to manually input them in code with ether a keyboard or with out a GUI due to a Physical Impairment Disability and a slight Learning impairment. but despite that I manged to get by as a free lance only PC Technician I even successfully got my Comp Tia A+ From Stevens Henager college but are there any premade and ready to go on both CD and Flash Drive 1. the first step 1 compile it properly as the manual values and both the compilers how do you do this as I do not reality know at this point whit a compile is in this context let aloe how to do it. 2. I also tried Flash rom and Unifash but with them I still dont understood how to set them up or if ether of them can do the things I need 3. I considered buying a chip but after I looked inside none are removable 4. than I though how about one of these here http://cgi.ebay.com/EasyPro-90B-Universal-Chips-Program-Device-Programmer-/… and I thought this was great but than no because I have no idea what my EEPROM PLCC or my SOIC is or any others and google doesn't know ether and no one else seams to know So I was wondering if any one over their could ether help me be ether taking my C90S and C90P .Rom bios files and adding the CPUID's for me add naturally make it bookable and also give me a copy of the .rom file as well for back up just in case and if possible see if that EasyPro 90B universal USB programmer 6000+ EEPROM would help ether my C90P or my C90S ether now or later and is this the same units or a generic equivalent or does the first one do more or work better can you guys tell http://cgi.ebay.com/2010-high-speed-USB-SPI-Programmer-/320557016512?pt=LH_… As for my C90P the Problem is more complicated but the reason is more simple I used the wrong version of asus Aflash2 it was just too old I guess as I made the mistake of not downloading the latest version I used a the normal one not the top one but the one based on date not by version number. so can any one over there help me with any of these things I would be eternally grateful thank you

1 0

output of flashrom -v
by Richard Hanson 23 Aug '10

23 Aug '10

2 1

Re: [flashrom] Trying to flash Bios on MS-6728
by David Borg 21 Aug '10

21 Aug '10

Hi Manuel, Thanks for your logs. Flashrom version 0.9.1-r946 is pretty outdated though, could you try again with latest sources? Instructions here: http://flashrom.org/Downloads In the latest flashrom directory, do the following: 1) Make a new backup of the partly over-written bios ./flashrom -Vr newBiosDump.bin 2) Try writing new BIOS flashrom -Vw /path/to/bios/update/file If it still doesn't work (which it probably won't), could you please post the output of step 2 and the _ORIGINAL_ BIOS image you read using the old flashrom to http://paste.flashrom.org/ In the "Board name" field fill in the exact and _full_ name as printed with white letters on the motherboard. Note: Also ensure that the BIOS update file is valid, as i couldn't find a valid file from the MSI site. Thanks! Regards, David On 19 August 2010 23:07, Manuel Luitz <stupor_mundi(a)gmx.net> wrote: > > Hi guys, > > I just tried to flash the bios on my MSI board 865PE Neo2-PLS v1 (MS-6728) via > flashrom. The chip recognition and reading works flawlessly and produced valid > output. Writing to the ROM chip produces an error, listed in the attachment. I > also attached the output of lspci, superiotool and flashrom -V. Hope you can > play around with this data. > > Hope I will hear from you, > Greets, > > Manuel > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Anyone else encountered segfault with latest flashrom?
by Peter Lemenkov 20 Aug '10

20 Aug '10

Hello! Just FYI - I fetched latest r1145 and got segfault while running: omega1 ~/flashrom: sudo ./flashrom flashrom v0.9.2-r1145 on Linux 2.6.18-194.11.1.el5 (x86_64), built with libpci 2.2.3, GCC 4.1.2 20080704 (Red Hat 4.1.2-48), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. No coreboot table found. sh: dmidecode: command not found dmidecode execution unsucessfull - continuing without DMI info Found chipset "Intel 6300ESB", enabling flash write... OK. This chipset supports the following protocols: FWH. Segmentation fault omega1 ~/flashrom: I'm trying to find the cause of this issue. -- With best regards, Peter Lemenkov.

2 2

Trying to flash Bios on MS-6728
by Manuel Luitz 19 Aug '10

19 Aug '10

Hi guys, I just tried to flash the bios on my MSI board 865PE Neo2-PLS v1 (MS-6728) via flashrom. The chip recognition and reading works flawlessly and produced valid output. Writing to the ROM chip produces an error, listed in the attachment. I also attached the output of lspci, superiotool and flashrom -V. Hope you can play around with this data. Hope I will hear from you, Greets, Manuel

1 0

SB700 IMC disabling
by Carl-Daniel Hailfinger 19 Aug '10

19 Aug '10

Hi Zheng, running flashrom on certain systems with SB700 family chipsets will result in read and write corruption. I have added a corruption check to latest flashrom, and it seems that the IMC will access flash even if flashrom holds the BiosSemaphore (LPC bridge config space register 0x40, bit 5). Matthias Kretz owns a Supermicro H8DGT with this problem, but other boards (including a MITAC development board) exhibit the same issue. If we use flashrom to write, the SPI registers (especially FIFO counter and FIFO) will lock up after some time, and we have not been successful in getting the stuck board working again. Is there a way to stop the IMC from the host or to stop all IMC flash accesses (including read and instruction fetch)? Regards, Carl-Daniel -- http://www.hailfinger.org/

2 2

flashrom -V for GA-E7AUM-DS2H
by Beelzebubbie 19 Aug '10

19 Aug '10

Здравствуйте, Flashrom. -- С уважением, Beelzebubbie mailto:Beelzebubbie@mail.ru

1 0

Re: [flashrom] Urgent: Flash part would be destroied by flashrom 0.9.2 once manager application is running.
by Hony.Chiang＠mic.com.tw 19 Aug '10

19 Aug '10

Hi Daniel, I follow your suggestion capture error messages from flashrom v0.9.2-runknown. We have probed SPI bus while that application is running, and have found that ROM shadow address 0xFFC00000 seems to be accessed. It may be the cause. Whatever, I have submitted the request of application modification to 3rd party, and expect that flashrom will be also improved in the future. Could you not post our messages from mail to Patchwork Flashrom web site for commerce? I appreciate for your immediate assistance here. Best Regards, Hony -----Original Message----- From: Carl-Daniel Hailfinger [mailto:c-d.hailfinger.devel.2006@gmx.net] Sent: Wednesday, August 18, 2010 11:42 PM To: hony.chiang (江昆仲 - MIC) Cc: victor.chen (陳文貴 - MIC); jerry.c (陳亭岳 - MIC); flashrom(a)flashrom.org Subject: Re: [flashrom] Urgent: Flash part would be destroied by flashrom 0.9.2 once manager application is running. Hi Hony, can you please update flashrom to the latest version from svn and then run flashrom -V -r test.rom while the 3rd party application is running? This should detect the corruption you were seeing. The corruption is no fixed yet, but detecting it is a good first step. Thanks! Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

Recall: Urgent: Flash part would be destroied by flashrom 0.9.2 once manager application is running.
by Hony.Chiang＠mic.com.tw 19 Aug '10

19 Aug '10

hony.chiang (江昆仲 - MIC) would like to recall the message, "[flashrom] Urgent: Flash part would be destroied by flashrom 0.9.2 once manager application is running.".

1 0

Re: [flashrom] Urgent: Flash part would be destroied by flashrom 0.9.2 once manager application is running.
by Hony.Chiang＠mic.com.tw 19 Aug '10

19 Aug '10

Hi Daniel, I follow your suggestion capture error messages from flashrom v0.9.2-runknown. We have probed SPI bus while that application is running, and have found that ROM shadow address 0xFFEC0000 seems to be accessed. It may be the cause. Whatever, I have submitted the request of application modification to 3rd party, and expect that flashrom will be also improved in the future. Could you not post our messages from mail to Patchwork Flashrom web site for commerce? I appreciate for your immediate assistance here. Best Regards, Hony -----Original Message----- From: Carl-Daniel Hailfinger [mailto:c-d.hailfinger.devel.2006@gmx.net] Sent: Wednesday, August 18, 2010 11:42 PM To: hony.chiang (江昆仲 - MIC) Cc: victor.chen (陳文貴 - MIC); jerry.c (陳亭岳 - MIC); flashrom(a)flashrom.org Subject: Re: [flashrom] Urgent: Flash part would be destroied by flashrom 0.9.2 once manager application is running. Hi Hony, can you please update flashrom to the latest version from svn and then run flashrom -V -r test.rom while the 3rd party application is running? This should detect the corruption you were seeing. The corruption is no fixed yet, but detecting it is a good first step. Thanks! Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

Re: [flashrom] [PATCH] Board enable for ASUS P5LP-LE
by Leon Zhang 18 Aug '10

18 Aug '10

lspci/superiotool: http://www.coreboot.org/pipermail/flashrom/2010-August/004495.html Signed-off-by: Michael Karcher <flashrom at mkarcher.dialup.fu-berlin.de <http://www.flashrom.org/mailman/listinfo/flashrom>> Tested-by: Leon Zhang <leoncamel(a)gmail.com> --- board_enable.c | 2 ++ print.c | 1 + 2 files changed, 3 insertions(+), 0 deletions(-) diff --git a/board_enable.c b/board_enable.c index ae0fbfa..dd56477 100644 --- a/board_enable.c +++ b/board_enable.c @@ -1309,6 +1309,7 @@ static int intel_ich_gpio18_raise(void) /* * Suited for: * - ASUS A8Jm (laptop): Intel 945 + ICH7 + * - ASUS P5LP-LE (Epson/HP OEM) */ static int intel_ich_gpio34_raise(void) { @@ -1788,6 +1789,7 @@ const struct board_pciid_enable board_pciid_enables[] = { {0x1039, 0x0661, 0x1043, 0x8113, 0x1039, 0x5513, 0x1043, 0x8087, NULL, NULL, NULL, "ASUS", "P4S800-MX", 512, OK, w836xx_memw_enable_2e}, {0x10B9, 0x1541, 0, 0, 0x10B9, 0x1533, 0, 0, "^P5A$", "asus", "p5a", "ASUS", "P5A", 0, OK, board_asus_p5a}, {0x10DE, 0x0030, 0x1043, 0x818a, 0x8086, 0x100E, 0x1043, 0x80EE, NULL, NULL, NULL, "ASUS", "P5ND2-SLI Deluxe", 0, OK, nvidia_mcp_gpio10_raise}, + {0x8086, 0x27b8, 0x1043, 0x2a22, 0x8086, 0x2770, 0x1043, 0x2a22, NULL, NULL, NULL, "ASUS", "P5LP-LE", 0, OK, intel_ich_gpio34_raise}, {0x8086, 0x24dd, 0x1043, 0x80a6, 0x8086, 0x2570, 0x1043, 0x8157, NULL, NULL, NULL, "ASUS", "P5PE-VM", 0, OK, intel_ich_gpio21_raise}, {0x8086, 0x3590, 0x1028, 0x016c, 0x1000, 0x0030, 0x1028, 0x016c, NULL, NULL, NULL, "Dell", "PowerEdge 1850", 0, OK, intel_ich_gpio23_raise}, {0x1106, 0x3038, 0x1019, 0x0996, 0x1106, 0x3177, 0x1019, 0x0996, NULL, NULL, NULL, "Elitegroup", "K7VTA3", 256, OK, NULL}, diff --git a/print.c b/print.c index 4871cc8..933ac2c 100644 --- a/print.c +++ b/print.c @@ -366,6 +366,7 @@ const struct board_info boards_known[] = { B("ASUS", "P5KC", 1, "http://www.asus.com/product.aspx?P_ID=fFZ8oUIGmLpwNMjj", NULL), B("ASUS", "P5L-MX", 1, "http://www.asus.com/product.aspx?P_ID=X70d3NCzH2DE9vWH", NULL), B("ASUS", "P5ND2-SLI Deluxe", 1, "http://www.asus.com/product.aspx?P_ID=WY7XroDuUImVbgp5", NULL), + B("ASUS", "P5LP-LE", 1, NULL, NULL), /* OEM board, no ASUS URL */ B("ASUS", "P5PE-VM", 1, "http://www.asus.com/product.aspx?P_ID=k3h0ZFVu9Lo1dUvk", NULL), B("ASUS", "P6T SE", 1, "http://www.asus.com/product.aspx?P_ID=t4yhK6y9W9o7iQ9E", NULL), B("ASUS", "P6T Deluxe", 1, "http://www.asus.com/product.aspx?P_ID=vXixf82co6Q5v0BZ", NULL),

1 0

ASUS P5LP-LE
by Leon Zhang 18 Aug '10

18 Aug '10

http://faq.epsondirect.co.jp/faq/dl/app/servlet/relatedqa?QID=010372 Model: MT7700

2 1

[PATCH] SB700 IMC arbitration
by Carl-Daniel Hailfinger 18 Aug '10

18 Aug '10

Try to request the BIOS semaphore on SB700 family southbridges. This is a really gross hack and should _not_ enter the tree as is. It is also potentially dangerous on SB600, and will slow down all flash accesses a lot. It is a really simple patch designed to test my assumptions about locking. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-sb700_spi_imc_flash_arbitration/sb600spi.c =================================================================== --- flashrom-sb700_spi_imc_flash_arbitration/sb600spi.c (Revision 1145) +++ flashrom-sb700_spi_imc_flash_arbitration/sb600spi.c (Arbeitskopie) @@ -42,6 +42,7 @@ */ static uint8_t *sb600_spibar = NULL; +static struct pci_dev *lpc_bridge = NULL; int sb600_spi_read(struct flashchip *flash, uint8_t *buf, int start, int len) { @@ -100,6 +101,71 @@ ; } +static int request_flash_access(void) +{ + uint8_t tmp; + int i = 0; + + tmp = pci_read_byte(lpc_bridge, 0x40); + if (tmp & (1 << 6)) { + msg_pspew("Waiting for SB600 IMC to release flash access.\n"); + while (pci_read_byte(lpc_bridge, 0x40) & (1 << 6)) { + if (++i > 1024) { + msg_perr("SB600 IMC did not release flash.\n"); + return 1; + } + } + msg_pspew("SB600 IMC released flash access after %i cycles.\n", + i); + i = 0; + } + + if (tmp & (1 << 5)) { + /* Is this an error? */ + msg_pdbg("Strange. SB600 flash access requested although it " + "was already granted.\n"); + return 0; + } + + /* Request BiosSemaphore. */ + tmp = pci_read_byte(lpc_bridge, 0x40); + tmp |= 1 << 5; + pci_write_byte(lpc_bridge, 0x40, tmp); + while (!(pci_read_byte(lpc_bridge, 0x40) & (1 << 5))) { + if (++i > 1024) { + msg_perr("SB600 flash access was not granted.\n"); + return 1; + } + } + tmp = pci_read_byte(lpc_bridge, 0x40); + if (tmp & (1 << 6)) { + msg_perr("Very strange. SB600 IMC has flash access although " + "we requested SB600 flash access.\n"); + return 1; + } + msg_pspew("SB600 flash access granted after %i cycles.\n", i); + return 0; +} + +static int release_flash_access(void) +{ + uint8_t tmp; + + tmp = pci_read_byte(lpc_bridge, 0x40); + if (tmp & (1 << 6)) { + /* Is this an error? */ + msg_pdbg("Strange. SB600 IMC already has flash access.\n"); + } + if (!(tmp & (1 << 5))) { + /* Is this an error? */ + msg_pdbg("Strange. SB600 already released flash access.\n"); + } + tmp &= ~(1 << 5); + pci_write_byte(lpc_bridge, 0x40, tmp); + + return 0; +} + int sb600_spi_send_command(unsigned int writecnt, unsigned int readcnt, const unsigned char *writearr, unsigned char *readarr) { @@ -126,6 +192,13 @@ return SPI_INVALID_LENGTH; } + /* FIXME: Waiting for arbitration here is stupid. We need arbitration + * either at the start of a multicommand, or even at SB600 init. + * FIXME: Check if arbitration also is needed on SB600. + */ + if (request_flash_access()) + return SPI_PROGRAMMER_ERROR; + /* This is a workaround for a bug in SB600 and SB700. If we only send * an opcode and no additional data/address, the SPI controller will * read one byte too few from the chip. Basically, the last byte of @@ -199,6 +272,7 @@ "flash chip.\n"); return SPI_PROGRAMMER_ERROR; } + release_flash_access(); return 0; } @@ -212,6 +286,8 @@ "Reserved", "33", "22", "16.5" }; + lpc_bridge = dev; + /* Read SPI_BaseAddr */ tmp = pci_read_long(dev, 0xa0); tmp &= 0xffffffe0; /* remove bits 4-0 (reserved) */ -- http://www.hailfinger.org/

1 0

Urgent: Flash part would be destroied by flashrom 0.9.2 once manager application is running.
by Hony.Chiang＠mic.com.tw 18 Aug '10

18 Aug '10

Hi Sirs, Nice to have your support. I get the serious problem on flashrom 0.9.2 on our server systems. We always have to run 3rd party manager application to call up flashrom for BIOS upgrade. However, flashrom would be failed on “Verifying flash” step because some of programmed data in flash part is different with ones in golden ROM image file on random offset addresses. This defect occurs on Red Hat 5 x64, SLES 10 x64 and SLES 11 x64. If I run flashrom tool manually without this 3rd application, it would always flash SPI part successfully. Due to the 3rd party application is confidential, it can not be provided to you for defect reproduction. Q1: May I suspect that expected data that is written to mapped virtual memory space by flashrom is overwritten or interfered by other process from 3rd application before SPI host controller operates these data to SPI ROM? Q2: May I suspect that expected data that is written to mapped virtual memory space by flashrom is not sync to physical memory space immediately when SPI host controller operates these data to SPI ROM? Q3: In order to prevent other process to interfere /dev/mem, mapped virtual memory space or physical memory space that flashrom uses, would you have any idea or some slice codes to lock them during flashrom operation? Q4: Would you have any idea to trace the root cause interfered flashrom? Please advise me your professional comments. Thanks!! Verbose message: Programming flash done. COMPLETE. Verifying flash... VERIFY FAILED at 0x00017ca4! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x003fffff: 0x3a Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Syntax: ./flashrom –w 24a.rom Hardware configuration: MB: AMD platform solution South Bridge: AMD SP5100 Flash part: ST M25P32 NOS: Reg Hat 5 X86_X64 SLES 10 X86_X64 SLES 11 X86_X64 Best Regards, Hony Chiang

3 16

[commit] r1145 - trunk
by repository service 18 Aug '10

18 Aug '10

Author: hailfinger Date: Wed Aug 18 17:12:43 2010 New Revision: 1145 URL: http://flashrom.org/trac/coreboot/changeset/1145 Log: Add paranoid checks for correct values in essential registers in the SB600/SB700/... SPI driver. If something else changes the values we wrote, we will see severe read/write corruption. sb600spi will now abort the access and return an error if it detects this sort of corruption. Note: This corruption can be caused by a few different events: - IPMI/BMC/IMC accesses flash - Other software accesses flash The nature of flash access (read/write/ID/...) is irrelevant. Each such access will cause corruption for all other accesses happening at the same time. Thanks to Matthias Kretz for testing this patch. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Matthias Kretz <kretz(a)kde.org> Modified: trunk/sb600spi.c trunk/spi.h Modified: trunk/sb600spi.c ============================================================================== --- trunk/sb600spi.c Tue Aug 17 00:12:39 2010 (r1144) +++ trunk/sb600spi.c Wed Aug 18 17:12:43 2010 (r1145) @@ -58,10 +58,40 @@ { mmio_writeb(mmio_readb(sb600_spibar + 2) | 0x10, sb600_spibar + 2); + /* FIXME: This loop makes no sense at all. */ while (mmio_readb(sb600_spibar + 0xD) & 0x7) msg_pspew("reset\n"); } +static int compare_internal_fifo_pointer(uint8_t want) +{ + uint8_t tmp; + + tmp = mmio_readb(sb600_spibar + 0xd) & 0x07; + want &= 0x7; + if (want != tmp) { + msg_perr("SB600 FIFO pointer corruption! Pointer is %d, wanted " + "%d\n", tmp, want); + msg_perr("Something else is accessing the flash chip and " + "causes random corruption.\nPlease stop all " + "applications and drivers and IPMI which access the " + "flash chip.\n"); + return 1; + } else { + msg_pspew("SB600 FIFO pointer is %d, wanted %d\n", tmp, want); + return 0; + } +} + +static int reset_compare_internal_fifo_pointer(uint8_t want) +{ + int ret; + + ret = compare_internal_fifo_pointer(want); + reset_internal_fifo_pointer(); + return ret; +} + static void execute_command(void) { mmio_writeb(mmio_readb(sb600_spibar + 2) | 1, sb600_spibar + 2); @@ -77,6 +107,7 @@ /* First byte is cmd which can not being sent through FIFO. */ unsigned char cmd = *writearr++; unsigned int readoffby1; + unsigned char readwrite; writecnt--; @@ -102,15 +133,17 @@ * It is unclear if the CS# line is set high too early as well. */ readoffby1 = (writecnt) ? 0 : 1; - mmio_writeb((readcnt + readoffby1) << 4 | (writecnt), sb600_spibar + 1); + readwrite = (readcnt + readoffby1) << 4 | (writecnt); + mmio_writeb(readwrite, sb600_spibar + 1); mmio_writeb(cmd, sb600_spibar + 0); /* Before we use the FIFO, reset it first. */ reset_internal_fifo_pointer(); /* Send the write byte to FIFO. */ + msg_pspew("Writing: "); for (count = 0; count < writecnt; count++, writearr++) { - msg_pspew(" [%x]", *writearr); + msg_pspew("[%02x]", *writearr); mmio_writeb(*writearr, sb600_spibar + 0xC); } msg_pspew("\n"); @@ -119,8 +152,10 @@ * We should send the data by sequence, which means we need to reset * the FIFO pointer to the first byte we want to send. */ - reset_internal_fifo_pointer(); + if (reset_compare_internal_fifo_pointer(writecnt)) + return SPI_PROGRAMMER_ERROR; + msg_pspew("Executing: \n"); execute_command(); /* @@ -134,21 +169,36 @@ * the opcode, the FIFO already stores the response from the chip. * Usually, the chip will respond with 0x00 or 0xff. */ - reset_internal_fifo_pointer(); + if (reset_compare_internal_fifo_pointer(writecnt + readcnt)) + return SPI_PROGRAMMER_ERROR; /* Skip the bytes we sent. */ + msg_pspew("Skipping: "); for (count = 0; count < writecnt; count++) { cmd = mmio_readb(sb600_spibar + 0xC); - msg_pspew("[ %2x]", cmd); + msg_pspew("[%02x]", cmd); } + msg_pspew("\n"); + if (compare_internal_fifo_pointer(writecnt)) + return SPI_PROGRAMMER_ERROR; - msg_pspew("The FIFO pointer after skipping is %d.\n", - mmio_readb(sb600_spibar + 0xd) & 0x07); + msg_pspew("Reading: "); for (count = 0; count < readcnt; count++, readarr++) { *readarr = mmio_readb(sb600_spibar + 0xC); msg_pspew("[%02x]", *readarr); } msg_pspew("\n"); + if (reset_compare_internal_fifo_pointer(readcnt + writecnt)) + return SPI_PROGRAMMER_ERROR; + + if (mmio_readb(sb600_spibar + 1) != readwrite) { + msg_perr("Unexpected change in SB600 read/write count!\n"); + msg_perr("Something else is accessing the flash chip and " + "causes random corruption.\nPlease stop all " + "applications and drivers and IPMI which access the " + "flash chip.\n"); + return SPI_PROGRAMMER_ERROR; + } return 0; } @@ -158,6 +208,10 @@ struct pci_dev *smbus_dev; uint32_t tmp; uint8_t reg; + const char *speed_names[4] = { + "Reserved", "33", "22", "16.5" + }; + /* Read SPI_BaseAddr */ tmp = pci_read_long(dev, 0xa0); tmp &= 0xffffffe0; /* remove bits 4-0 (reserved) */ @@ -183,15 +237,25 @@ msg_pdbg("PrefetchEnSPIFromIMC=%i, ", tmp); tmp = pci_read_byte(dev, 0xbb); + /* FIXME: Set bit 3,6,7 if not already set. + * Set bit 5, otherwise SPI accesses are pointless in LPC mode. + * See doc 42413 AMD SB700/710/750 RPR. + */ msg_pdbg("PrefetchEnSPIFromHost=%i, SpiOpEnInLpcMode=%i\n", tmp & 0x1, (tmp & 0x20) >> 5); tmp = mmio_readl(sb600_spibar); + /* FIXME: If SpiAccessMacRomEn or SpiHostAccessRomEn are zero on + * SB700 or later, reads and writes will be corrupted. Abort in this + * case. Make sure to avoid this check on SB600. + */ msg_pdbg("SpiArbEnable=%i, SpiAccessMacRomEn=%i, " "SpiHostAccessRomEn=%i, ArbWaitCount=%i, " "SpiBridgeDisable=%i, DropOneClkOnRd=%i\n", (tmp >> 19) & 0x1, (tmp >> 22) & 0x1, (tmp >> 23) & 0x1, (tmp >> 24) & 0x7, (tmp >> 27) & 0x1, (tmp >> 28) & 0x1); + tmp = (mmio_readb(sb600_spibar + 0xd) >> 4) & 0x3; + msg_pdbg("NormSpeed is %s MHz\n", speed_names[tmp]); /* Look for the SMBus device. */ smbus_dev = pci_dev_find(0x1002, 0x4385); @@ -230,6 +294,9 @@ return 0; } + /* Bring the FIFO to a clean state. */ + reset_internal_fifo_pointer(); + buses_supported |= CHIP_BUSTYPE_SPI; spi_controller = SPI_CONTROLLER_SB600; return 0; Modified: trunk/spi.h ============================================================================== --- trunk/spi.h Tue Aug 17 00:12:39 2010 (r1144) +++ trunk/spi.h Wed Aug 18 17:12:43 2010 (r1145) @@ -124,5 +124,6 @@ #define SPI_INVALID_ADDRESS -3 #define SPI_INVALID_LENGTH -4 #define SPI_FLASHROM_BUG -5 +#define SPI_PROGRAMMER_ERROR -6 #endif /* !__SPI_H__ */

1 0

(no subject)
by Матыскин Алексей 18 Aug '10

18 Aug '10

root@matiskin-desktop:~# flashrom -vV /tmp/A74M0315.ROM flashrom v0.9.1-r946 No coreboot table found. DMI string system-manufacturer: "ECS" DMI string system-product-name: "A740GM-M" DMI string system-version: "1.0 " DMI string baseboard-manufacturer: "ECS" DMI string baseboard-product-name: "A740GM-M" DMI string baseboard-version: "1.0 " DMI string chassis-type: "Desktop" Found ITE Super I/O, id 8726 Found chipset "AMD SB700/SB710/SB750", enabling flash write... SPI base address is at 0xfec10000 AltSpiCSEnable=0, SpiRomEnable=1, AbortEnable=0 PrefetchEnSPIFromIMC=0, PrefetchEnSPIFromHost=1, SpiOpEnInLpcMode=1 SpiArbEnable=1, SpiAccessMacRomEn=1, SpiHostAccessRomEn=1, ArbWaitCount=4, SpiBridgeDisable=0, DropOneClkOnRd=0 GPIO11 used for SPI_DO GPIO12 used for SPI_DI GPIO31 used for SPI_HOLD GPIO32 used for SPI_CS GPIO47 used for SPI_CLK ROM strap override is not active OK. This chipset supports the following protocols: LPC,FWH,SPI. Calibrating delay loop... 635M loops per second, 100 myus = 188 us. OK. Probing for AMD Am29F010A/B, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMD Am29F002(N)BB, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMD Am29F002(N)BT, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMD Am29F016D, 2048 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMD Am29F040B, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMD Am29F080B, 1024 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMD Am29LV040B, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMD Am29LV081B, 1024 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ASD AE49F2008, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Atmel AT25DF021, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF041A, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF081, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF161, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF321, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF321A, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF641, 8192 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25F512B, 64 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25FS010, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25FS040, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF041, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF081A, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF161, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF161A, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26F004, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT29C512, 64 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Atmel AT29C010A, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Atmel AT29C020, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Atmel AT29C040A, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Atmel AT45CS1282, 16896 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB011D, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB021D, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB041D, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB081D, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB161D, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB321C, 4224 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB321D, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB642D, 8192 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT49BV512, 64 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Atmel AT49F002(N), 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Atmel AT49F002(N)T, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMIC A25L40PT, 512 KB: RDID returned 0xef 0x30 0x14 0x00. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A25L40PU, 512 KB: RDID returned 0xef 0x30 0x14 0x00. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A29002B, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMIC A29002T, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMIC A29040B, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for AMIC A49LF040A, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for EMST F49B002UA, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Eon EN25B05, 64 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B05T, 64 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B10, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B10T, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B20, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B20T, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B40, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B40T, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B80, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B80T, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B16, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B16T, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B32, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B32T, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B64, 8192 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25B64T, 8192 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25D16, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F05, 64 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F10, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F20, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F40, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F80, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F16, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN25F32, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Eon EN29F010, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for EON EN29F002(A)(N)B, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for EON EN29F002(A)(N)T, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Fujitsu MBM29F004BC, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Fujitsu MBM29F004TC, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Fujitsu MBM29F400BC, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Fujitsu MBM29F400TC, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Intel 28F001BX-B, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Intel 28F001BX-T, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Intel 28F004S5, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x18, id2 0x9f Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Macronix MX25L512, 64 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1005, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L2005, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L4005, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L8005, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1605, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1635D, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L3205, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L3235D, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L6405, 8192 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L12805, 16384 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX29F001B, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Macronix MX29F001T, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Macronix MX29F002B, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Macronix MX29F002T, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Macronix MX29LV040, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Numonyx M25PE10, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE20, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE40, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE80, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE16, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV010, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV016B, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV020, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV040, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV080B, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV512, 64 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm29F002T, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for PMC Pm29F002B, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for PMC Pm39LV010, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for PMC Pm49FL002, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sanyo LF25FW203A, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Spansion S25FL008A, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Spansion S25FL016A, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF016B, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF032B, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF040.REMS, 512 KB: REMS returned ef 13. probe_spi_rems: id1 0xef, id2 0x13 Probing for SST SST25VF040B, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF040B.REMS, 512 KB: REMS returned ef 13. probe_spi_rems: id1 0xef, id2 0x13 Probing for SST SST25VF080B, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST28SF040A, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST29EE010, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST29LE010, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST29EE020A, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST29LE020, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39SF512, 64 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39SF010A, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39SF020A, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39SF040, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39VF512, 64 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39VF010, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39VF020, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39VF040, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST39VF080, 1024 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SST SST49LF002A/B, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0x53, id2 0x0b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x18, id2 0x9f 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 Probing for SST SST49LF016C, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for SST SST49LF020, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P05.RES, 64 KB: RDID returned 0xef 0x30 0x14. Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P10.RES, 128 KB: RDID returned 0xef 0x30 0x14. Ignoring RES in favour of RDID. Probing for ST M25P20, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P40, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P40-old, 512 KB: RDID returned 0xef 0x30 0x14. Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P16, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P32, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P64, 8192 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P128, 16384 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M29F002B, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ST M29F002T/NT, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ST M29F040B, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ST M29F400BT, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ST M29W010B, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ST M29W040B, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ST M29W512B, 64 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0x18, id2 0x9f Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x18, id2 0x9f Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x18, id2 0x9f Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50LPW116, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for SyncMOS S29C31004T, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SyncMOS S29C51001T, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SyncMOS S29C51002T, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for SyncMOS S29C51004T, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for TI TMS29F002RB, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for TI TMS29F002RT, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Winbond W25x10, 128 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x20, 256 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x40, 512 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x80, 1024 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Chip status register is 00 Found chip "Winbond W25x80" (1024 KB, SPI) at physical address 0xfff00000. Probing for Winbond W25x16, 2048 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x32, 4096 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x64, 8192 KB: RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W29C011, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Winbond W29C020C, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Winbond W29C040P, 512 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Winbond W29EE011, 128 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Winbond W39V040A, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U, 256 KB: skipped. Host bus type LPC,FWH,SPI and chip bus type Parallel are incompatible. Probing for Winbond W49V002A, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x18, id2 0x9f, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel unknown Atmel SPI chip, 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for EON unknown EON SPI chip, 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for Macronix unknown Macronix SPI chip, 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for PMC unknown PMC SPI chip, 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for SST unknown SST SPI chip, 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for ST unknown ST SPI chip, 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for Sanyo unknown Sanyo SPI chip, 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for Generic unknown SPI chip (RDID), 0 KB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0xef 0x30 0x14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Not unmapping zero size at (nil) Probing for Generic unknown SPI chip (REMS), 0 KB: Not mapping flash chip, zero size at 0x00000000. REMS returned ef 13. probe_spi_rems: id1 0xef, id2 0x13 Not unmapping zero size at (nil) === This flash part has status UNTESTED for operations: ERASE 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, -rV, -wV, -EV), and mention which mainboard or programmer you tested. Thanks for your help! === Flash image seems to be a legacy BIOS. Disabling checks. Verifying flash... VERIFY FAILED at 0x0000000c! Expected=0x68, Read=0xe0, failed byte count from 0x00000000-0x000fffff: 0xb25d2

1 0

Re: [flashrom] SST25VF016B verbose output
by Wagner, Helge (GE Intelligent Platforms) 17 Aug '10

17 Aug '10

Ups, the flash devices i have set a different write algorithm was the SST 25VF032B and 25VF064C, and not the 25VF016B, and i have NOT tested the 25VF016B before. Sorry for that wrong message! So you will not see any speed-up for the 25VF016B, but the error messages will be gone after applying my patch. What you could do to speed-up this chip is to change the write algorithm from "spi_chip_write_1" to "spi_aai_write" after applying my SST 25VF032B and 25VF064C patch. Regards, Helge -----Original Message----- From: flashrom-bounces(a)flashrom.org [mailto:flashrom-bounces@flashrom.org] On Behalf Of Wagner, Helge (GE Intelligent Platforms) Sent: Dienstag, 17. August 2010 09:29 To: Veres, Greg; Michael Karcher Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] SST25VF016B verbose output Hi, i have marked the erase of that chip already as working, and i have also supplied a patch which will prevent the error messages (i have added on-the-fly reprogramming of the list of predefine commands). Please see http://www.flashrom.org/pipermail/flashrom/2010-August/004331.html And with my patch you will see a significant programming speed-up (from 228 to 113 seconds in my case) as it now uses a different programming algorithm. Unfortunally, my patch has not been acked yet. Hopefully it will happen soon. Regards, Helge -----Original Message----- From: flashrom-bounces+helge.wagner=ge.com(a)flashrom.org [mailto:flashrom-bounces+helge.wagner=ge.com@flashrom.org] On Behalf Of Veres, Greg Sent: Dienstag, 17. August 2010 00:50 To: Michael Karcher Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] SST25VF016B verbose output Great. It did seem to work. When I read the section of the memory that I wrote, it contained what I wrote. So I was happy. :) Does this allow you guys to mark erasing on that chip as a yes? It is currently marked as '?'. Greg -----Original Message----- From: Michael Karcher [mailto:flashrom@mkarcher.dialup.fu-berlin.de] Sent: August-16-10 6:33 PM To: Veres, Greg Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] SST25VF016B verbose output Am Montag, den 16.08.2010, 11:43 -0700 schrieb Veres, Greg: > I noticed that the erase fails on the SST25VF016B. Attached is the log > file for burning a portion of the bios file. Thanks for your mail. While the output of flashrom is quite unclear, what you are observing is not an erase failure, but normal operation on Intel chipsets. Intel Chipsets allow only to send 8 predefined commands to the flash chip and flashrom does not yet support changing the predefinitions on the fly. Your flash chip supports different erase commands (mostly eraseing different block sizes), and both 0x20 and 0x52, the first two erase commands listed for your chip, are not in the default list-of-eight that is sent to the chipset, so these erase methods fail. The third one OTOH worked flawlessly, allowing flashrom to continue. Regards, Michael Karcher _______________________________________________ flashrom mailing list flashrom(a)flashrom.org http://www.flashrom.org/mailman/listinfo/flashrom _______________________________________________ flashrom mailing list flashrom(a)flashrom.org http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] SST25VF016B verbose output
by Wagner, Helge (GE Intelligent Platforms) 17 Aug '10

17 Aug '10

Hi, i have marked the erase of that chip already as working, and i have also supplied a patch which will prevent the error messages (i have added on-the-fly reprogramming of the list of predefine commands). Please see http://www.flashrom.org/pipermail/flashrom/2010-August/004331.html And with my patch you will see a significant programming speed-up (from 228 to 113 seconds in my case) as it now uses a different programming algorithm. Unfortunally, my patch has not been acked yet. Hopefully it will happen soon. Regards, Helge -----Original Message----- From: flashrom-bounces+helge.wagner=ge.com(a)flashrom.org [mailto:flashrom-bounces+helge.wagner=ge.com@flashrom.org] On Behalf Of Veres, Greg Sent: Dienstag, 17. August 2010 00:50 To: Michael Karcher Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] SST25VF016B verbose output Great. It did seem to work. When I read the section of the memory that I wrote, it contained what I wrote. So I was happy. :) Does this allow you guys to mark erasing on that chip as a yes? It is currently marked as '?'. Greg -----Original Message----- From: Michael Karcher [mailto:flashrom@mkarcher.dialup.fu-berlin.de] Sent: August-16-10 6:33 PM To: Veres, Greg Cc: flashrom(a)flashrom.org Subject: Re: [flashrom] SST25VF016B verbose output Am Montag, den 16.08.2010, 11:43 -0700 schrieb Veres, Greg: > I noticed that the erase fails on the SST25VF016B. Attached is the log > file for burning a portion of the bios file. Thanks for your mail. While the output of flashrom is quite unclear, what you are observing is not an erase failure, but normal operation on Intel chipsets. Intel Chipsets allow only to send 8 predefined commands to the flash chip and flashrom does not yet support changing the predefinitions on the fly. Your flash chip supports different erase commands (mostly eraseing different block sizes), and both 0x20 and 0x52, the first two erase commands listed for your chip, are not in the default list-of-eight that is sent to the chipset, so these erase methods fail. The third one OTOH worked flawlessly, allowing flashrom to continue. Regards, Michael Karcher _______________________________________________ flashrom mailing list flashrom(a)flashrom.org http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] SST25VF016B verbose output
by Michael Karcher 17 Aug '10

17 Aug '10

Am Montag, den 16.08.2010, 11:43 -0700 schrieb Veres, Greg: > I noticed that the erase fails on the SST25VF016B. Attached is the log > file for burning a portion of the bios file. Thanks for your mail. While the output of flashrom is quite unclear, what you are observing is not an erase failure, but normal operation on Intel chipsets. Intel Chipsets allow only to send 8 predefined commands to the flash chip and flashrom does not yet support changing the predefinitions on the fly. Your flash chip supports different erase commands (mostly eraseing different block sizes), and both 0x20 and 0x52, the first two erase commands listed for your chip, are not in the default list-of-eight that is sent to the chipset, so these erase methods fail. The third one OTOH worked flawlessly, allowing flashrom to continue. Regards, Michael Karcher

2 1

[PATCH] Neuter probe for ITE SuperIO
by Ed Swierk 17 Aug '10

17 Aug '10

If the system has an SMSC LPC47N217N SuperIO, enter_conf_mode_ite() enters configuration mode, and then exit_conf_mode_ite() kills power to the serial UART. I don't know if there is a proper way to detect what kind of SuperIO the system has, but probe_superio_ite() is unsafe in its current form. Signed-off-by: Ed Swierk <eswierk(a)aristanetworks.com> --- Index: flashrom-0.9.2-r1057/internal.c =================================================================== --- flashrom-0.9.2-r1057.orig/internal.c +++ flashrom-0.9.2-r1057/internal.c @@ -104,7 +104,10 @@ struct superio superio = {}; void probe_superio(void) { +#if 0 + /* ITE probe causes SMSC LPC47N217 to power off the serial UART! */ superio = probe_superio_ite(); +#endif #if 0 /* Winbond Super I/O code is not yet available. */ if (superio.vendor == SUPERIO_VENDOR_NONE)

4 5

[PATCH] SST49FL040B: add unlocking
by Joshua Roys 17 Aug '10

17 Aug '10

Hello all, A bit of poking around revealed the possible reason this chip wasn't getting written to... both the datasheet and linux mtd twiddle some registers in the 4Mbit area before the flash chip in a manner identical to the 82802ab unlock function. Attached is a patch to hook it up. Thanks, Josh

2 2

[commit] r1144 - trunk
by repository service 17 Aug '10

17 Aug '10

Author: mkarcher Date: Tue Aug 17 00:12:39 2010 New Revision: 1144 URL: http://flashrom.org/trac/coreboot/changeset/1144 Log: SST49FL040B: add unlocking The datasheet says there's a set of registers in the 4Mbit before the flash memory. The block locking registers are aligned on 64K boundaries, plus 2. Write/erase sucessful on a system it failed before: http://www.flashrom.org/pipermail/flashrom/2010-August/004432.html Signed-off-by: Joshua Roys <roysjosh(a)gmail.com> Acked-by: Michael Karcher <flashrom(a)mkarcher.dialup.fu-berlin.de> Modified: trunk/flashchips.c Modified: trunk/flashchips.c ============================================================================== --- trunk/flashchips.c Mon Aug 16 00:43:23 2010 (r1143) +++ trunk/flashchips.c Tue Aug 17 00:12:39 2010 (r1144) @@ -5651,8 +5651,8 @@ .model_id = SST_49LF040B, .total_size = 512, .page_size = 64 * 1024, - .feature_bits = FEATURE_EITHER_RESET, - .tested = TEST_OK_PR, + .feature_bits = FEATURE_EITHER_RESET | FEATURE_REGISTERMAP, + .tested = TEST_OK_PREW, .probe = probe_jedec, .probe_timing = 1, /* 150ns */ .block_erasers = @@ -5668,6 +5668,7 @@ .block_erase = NULL, } }, + .unlock = unlock_82802ab, .write = write_jedec_1, .read = read_memmapped, },

1 0

SST25VF016B verbose output
by Veres, Greg 16 Aug '10

16 Aug '10

I noticed that the erase fails on the SST25VF016B. Attached is the log file for burning a portion of the bios file. Greg

1 0

[PATCH] Test patch for patchwork experiments
by Carl-Daniel Hailfinger 16 Aug '10

16 Aug '10

This patch is here to allow testing state changes, user permissions and have fun with. No signoff because the patch is not for flashrom. --- 1 2010-08-16 20:30:44.000000000 +0200 +++ 2 2010-08-16 20:30:47.000000000 +0200 @@ -1 +1 @@ -foo +bar -- http://www.hailfinger.org/

1 0

ERROR
by Jason Cochrane 16 Aug '10

16 Aug '10

ran this command: sudo flashrom -w ~/Downloads/P4P81019.rom and got this output: flashrom v0.9.1-r706 No coreboot table found. Found chipset "Intel ICH5/ICH5R", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... Programming page: ERASE FAILED at 0x00004ec0! Expected=0xff, Read=0x24, failed byte count from 0x00000000-0x0000ffff: 0xb06d ERASE FAILED! ERASE FAILED! FAILED! Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net channel #flashrom or mail flashrom(a)flashrom.org ------------------------------------------------------------ DO NOT REBOOT OR POWEROFF!

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom