flashrom November 2016

flashrom@flashrom.org

9 participants
19 discussions

Re: [flashrom] [PATCH] RFC: enable flashrom to write images of arbitrary size
by Peter Mamonov 09 Nov '16

09 Nov '16

Hi David, On Tue, Nov 08, 2016 at 11:22:56AM -0800, David Hendricks wrote: > Hi Peter, > Thanks for the patch! However, I suspect this will not be accepted > since the size check is an important safety measure for the general > use case. > > In general layout files should be used for this sort of thing. The way > we've gone about this in the chromium.org branch is to augment the -i > syntax to allow the user to specify a region and corresponding file, > and we also added a "--fast-verify" mode to only verify regions which > were targeted. So for example you could do "flashrom -p <programmer> > -l <layout_file> -i region:filename.bin --fast-verify --ignore-fmap > -w" which will write filename.bin to the targeted region and verify > only that region. > > Details here: https://www.chromium.org/chromium-os/packages/cros-flashrom#TOC-Partial-Rea… > . LMK if this is any help. Thanks for the tip! Looks like an ultimate solution. I'll try it and report the results later. Regards, Peter > > > > On Mon, Nov 7, 2016 at 1:00 PM, Peter Mamonov <pmamonov(a)gmail.com> wrote: > > Flashrom restricts an image size to be equal to a ROM capacity. This is > > inconvenient in case of large and slow ROM chips, when only part of the ROM > > should be updated. This patch removes this restriction in a quick-and-dirty > > manner. > > > > Signed-off-by: Peter Mamonov <pmamonov(a)gmail.com> > > --- > > flashrom.c | 26 +++++++++++++++----------- > > 1 file changed, 15 insertions(+), 11 deletions(-) > > > > diff --git a/flashrom.c b/flashrom.c > > index d51a44c..f805e00 100644 > > --- a/flashrom.c > > +++ b/flashrom.c > > @@ -1255,30 +1255,30 @@ int read_buf_from_file(unsigned char *buf, unsigned long size, > > > > if ((image = fopen(filename, "rb")) == NULL) { > > msg_gerr("Error: opening file \"%s\" failed: %s\n", filename, strerror(errno)); > > - return 1; > > + return -1; > > } > > if (fstat(fileno(image), &image_stat) != 0) { > > msg_gerr("Error: getting metadata of file \"%s\" failed: %s\n", filename, strerror(errno)); > > fclose(image); > > - return 1; > > + return -1; > > } > > - if (image_stat.st_size != size) { > > + if (image_stat.st_size > size) { > > msg_gerr("Error: Image size (%jd B) doesn't match the flash chip's size (%lu B)!\n", > > (intmax_t)image_stat.st_size, size); > > - fclose(image); > > - return 1; > > + return -1; > > } > > + size = image_stat.st_size; > > numbytes = fread(buf, 1, size, image); > > if (fclose(image)) { > > msg_gerr("Error: closing file \"%s\" failed: %s\n", filename, strerror(errno)); > > - return 1; > > + return -1; > > } > > if (numbytes != size) { > > msg_gerr("Error: Failed to read complete file. Got %ld bytes, " > > "wanted %ld!\n", numbytes, size); > > - return 1; > > + return -1; > > } > > - return 0; > > + return size; > > #endif > > } > > > > @@ -1481,7 +1481,10 @@ static int walk_eraseregions(struct flashctx *flash, int erasefunction, > > * members so the loop below won't be executed for them. > > */ > > len = eraser.eraseblocks[i].size; > > - for (j = 0; j < eraser.eraseblocks[i].count; j++) { > > + for (j = 0; > > + j < eraser.eraseblocks[i].count && > > + start + len <= flash->chip->total_size * 1024; > > + j++) { > > /* Print this for every block except the first one. */ > > if (i || j) > > msg_cdbg(", "); > > @@ -1988,11 +1991,12 @@ int doit(struct flashctx *flash, int force, const char *filename, int read_it, > > } > > > > if (write_it || verify_it) { > > - if (read_buf_from_file(newcontents, size, filename)) { > > + size = read_buf_from_file(newcontents, size, filename); > > + if (size < 0) { > > ret = 1; > > goto out; > > } > > - > > + flash->chip->total_size = size / 1024; /* FIXME */ > > #if CONFIG_INTERNAL == 1 > > if (programmer == PROGRAMMER_INTERNAL && cb_check_image(newcontents, size) < 0) { > > if (force_boardmismatch) { > > -- > > 2.1.4 > > > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > https://www.flashrom.org/mailman/listinfo/flashrom > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc.

1 0

Apollo Lake
by Tim Lewis 09 Nov '16

09 Nov '16

On the most recent version of the Chromium flashrom effort, there was a patch for Apollo Lake. I have applied it to the latest, fixed up one issue in the get_target_bus_from_chipset() to return the right BBS strapping. It finds the Winbond chip and starts to read, and gets an error when reading the ROM using the HWSEQ style. I have tracked it down to the function that waits for complete, where it fails. Any thoughts? Thanks, Tim Lewis P.S. I have this working with other flash utilities, so I know that the hardware is working and the flash part is present and responds. FAILED.p@p-desktop:~/Desktop/Blinkflash-Linux64-100.00.00.03$ sudo ./flashrom -p internal -r 123.bin -VV flashrom v0.9.7-unknown on Linux 4.4.0-21-generic (x86_64), built with libpci 3.2.1, GCC 4.8.4, little endian flashrom is free software, get the source code at http://www.flashrom.org Initializing internal programmer No coreboot table found. get_target_bus_from_chipset() returns 0x10. Found chipset "Intel Apollolake" with PCI ID 8086:5af0. Enabling flash write... Vendor ID: 8086, Device ID: 5a96, BAR: fed01000 BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x89 SPI BAR is = 0xfed01000 GCS = 0x89: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x0 (SPI) SPIBAR = 0xfed01000 + 0x0000 0x04: 0x3f00e000 (HSFSC) WARNING: SPI Configuration Lockdown activated. 0x08: 0x00000000 (FADDR) 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 (FREG0: Flash Descriptor) 0x00000000-0x00000fff is read-write 0x58: 0x06fe0001 (FREG1: BIOS) 0x00001000-0x006fefff is read-write 0x5C: 0x00007fff (FREG2: Management Engine) Management Engine region is unused. 0x60: 0x00007fff (FREG3: Gigabit Ethernet) Gigabit Ethernet region is unused. 0x64: 0x00007fff (FREG4: Platform Data) Platform Data region is unused. 0x84: 0x00000000 (PR0, unused) 0x88: 0x00000000 (PR1, unused) 0x8C: 0x00000000 (PR2, unused) 0x90: 0x00000000 (PR3, unused) 0x94: 0x00000000 (PR4, unused) Reading flash descriptors mapped by the chipset via FDOC/FDOD... done. === Content Section === FLVALSIG 0x0ff0a55a FLMAP0 0x00040003 FLMAP1 0x13100208 FLMAP2 0x00000000 --- Details --- NR (Number of Regions): 1 FRBA (Flash Region Base Address): 0x040 NC (Number of Components): 1 FCBA (Flash Component Base Address): 0x030 ISL (ICH/PCH Strap Length): 19 FISBA/FPSBA (Flash ICH/PCH Strap Base Address): 0x100 NM (Number of Masters): 3 FMBA (Flash Master Base Address): 0x080 MSL/PSL (MCH/PROC Strap Length): 0 FMSBA (Flash MCH/PROC Strap Base Address): 0x000 === Component Section === FLCOMP 0x649c02f4 FLILL 0xad604221 --- Details --- Component 1 density: 8 MB Component 2 is not used. Read Clock Frequency: reserved Read ID and Status Clock Freq.: 50 MHz Write and Erase Clock Freq.: 50 MHz Fast Read is supported. Fast Read Clock Frequency: 50 MHz Invalid instruction 0: 0x21 Invalid instruction 1: 0x42 Invalid instruction 2: 0x60 Invalid instruction 3: 0xad === Region Section === FLREG0 0x00000000 FLREG1 0x06fe0001 --- Details --- Region 0 (Descr.) 0x00000000 - 0x00000fff Region 1 (BIOS ) 0x00001000 - 0x006fefff === Master Section === FLMSTR1 0xffffff00 FLMSTR2 0xffffff00 FLMSTR3 0x7ff7ff00 --- Details --- Descr. BIOS ME GbE Platf. BIOS rw rw rw rw rw ME rw rw rw rw rw GbE rw rw rw w rw SPI Read Configuration: prefetching enabled, caching enabled, OK. This programmer supports the following protocols: FWH, Programmer-specific. Probing for Winbond W25Q128.V, 0 kB: Found 1 attached SPI flash chip with a density of 8192 kB. There are 2048 erase blocks with 4096 B each. Found Winbond flash chip "W25Q128.V" (8192 kB, Programmer-specific) at physical address 0x0. Found Winbond flash chip "W25Q128.V" (8192 kB, Programmer-specific). === 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, -Vw, -VE), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Reading flash... Reading 8388608 bytes starting at 0x000000. Transaction error between offset 0x00000000 and 0x0000003f (= 0x00000000 + 63) failed to read 0x0-0x7fffff Read operation failed! FAILED.p@p-desktop:~/Desktop/Blinkflash-Linux64-100.00.00.03$

2 1

Re: [flashrom] [PATCH] RFC: enable flashrom to write images of arbitrary size
by Nico Huber 09 Nov '16

09 Nov '16

Hi all, On 09.11.2016 00:20, Charlotte Plusplus wrote: > Hello > > That is very interesting. Do you have a way to automate that? > > I am testing ram stuff with coreboot, I don't need to flash a full 8MB > image. I could just pass a -i of the cbfs content to only change the > ramstage, and do a manual md5 of the various parts contained to only target > the difference, but it seems a bit tedious. > > It would be nice to do have a way to do kind of diff between the currenttly > flashed image and the desired image, and only flash the required changes. that is exactly what stock flashrom already does. The only thing that's not optimized is the reading. It currently always reads the whole flash twice, once before the flashing to create the diff, once for verifica- tion (no matter what the layout says). I did something to improve that for stock flashrom, see https://www.flashrom.org/pipermail/flashrom/2016-May/014629.html and the fourteen patches surrounding it. The magic there would be the -A option (don't read All). Nico > > Charlotte > > On Tue, Nov 8, 2016 at 2:22 PM, David Hendricks via flashrom < > flashrom(a)flashrom.org> wrote: > >> Hi Peter, >> Thanks for the patch! However, I suspect this will not be accepted >> since the size check is an important safety measure for the general >> use case. >> >> In general layout files should be used for this sort of thing. The way >> we've gone about this in the chromium.org branch is to augment the -i >> syntax to allow the user to specify a region and corresponding file, >> and we also added a "--fast-verify" mode to only verify regions which >> were targeted. So for example you could do "flashrom -p <programmer> >> -l <layout_file> -i region:filename.bin --fast-verify --ignore-fmap >> -w" which will write filename.bin to the targeted region and verify >> only that region. >> >> Details here: https://www.chromium.org/chromium-os/packages/cros- >> flashrom#TOC-Partial-Reads-and-Writes >> . LMK if this is any help. >> >> >> >> On Mon, Nov 7, 2016 at 1:00 PM, Peter Mamonov <pmamonov(a)gmail.com> wrote: >>> Flashrom restricts an image size to be equal to a ROM capacity. This is >>> inconvenient in case of large and slow ROM chips, when only part of the >> ROM >>> should be updated. This patch removes this restriction in a >> quick-and-dirty >>> manner. >>> >>> Signed-off-by: Peter Mamonov <pmamonov(a)gmail.com> >>> --- >>> flashrom.c | 26 +++++++++++++++----------- >>> 1 file changed, 15 insertions(+), 11 deletions(-) >>> >>> diff --git a/flashrom.c b/flashrom.c >>> index d51a44c..f805e00 100644 >>> --- a/flashrom.c >>> +++ b/flashrom.c >>> @@ -1255,30 +1255,30 @@ int read_buf_from_file(unsigned char *buf, >> unsigned long size, >>> >>> if ((image = fopen(filename, "rb")) == NULL) { >>> msg_gerr("Error: opening file \"%s\" failed: %s\n", >> filename, strerror(errno)); >>> - return 1; >>> + return -1; >>> } >>> if (fstat(fileno(image), &image_stat) != 0) { >>> msg_gerr("Error: getting metadata of file \"%s\" failed: >> %s\n", filename, strerror(errno)); >>> fclose(image); >>> - return 1; >>> + return -1; >>> } >>> - if (image_stat.st_size != size) { >>> + if (image_stat.st_size > size) { >>> msg_gerr("Error: Image size (%jd B) doesn't match the >> flash chip's size (%lu B)!\n", >>> (intmax_t)image_stat.st_size, size); >>> - fclose(image); >>> - return 1; >>> + return -1; >>> } >>> + size = image_stat.st_size; >>> numbytes = fread(buf, 1, size, image); >>> if (fclose(image)) { >>> msg_gerr("Error: closing file \"%s\" failed: %s\n", >> filename, strerror(errno)); >>> - return 1; >>> + return -1; >>> } >>> if (numbytes != size) { >>> msg_gerr("Error: Failed to read complete file. Got %ld >> bytes, " >>> "wanted %ld!\n", numbytes, size); >>> - return 1; >>> + return -1; >>> } >>> - return 0; >>> + return size; >>> #endif >>> } >>> >>> @@ -1481,7 +1481,10 @@ static int walk_eraseregions(struct flashctx >> *flash, int erasefunction, >>> * members so the loop below won't be executed for them. >>> */ >>> len = eraser.eraseblocks[i].size; >>> - for (j = 0; j < eraser.eraseblocks[i].count; j++) { >>> + for (j = 0; >>> + j < eraser.eraseblocks[i].count && >>> + start + len <= flash->chip->total_size * 1024; >>> + j++) { >>> /* Print this for every block except the first >> one. */ >>> if (i || j) >>> msg_cdbg(", "); >>> @@ -1988,11 +1991,12 @@ int doit(struct flashctx *flash, int force, >> const char *filename, int read_it, >>> } >>> >>> if (write_it || verify_it) { >>> - if (read_buf_from_file(newcontents, size, filename)) { >>> + size = read_buf_from_file(newcontents, size, filename); >>> + if (size < 0) { >>> ret = 1; >>> goto out; >>> } >>> - >>> + flash->chip->total_size = size / 1024; /* FIXME */ >>> #if CONFIG_INTERNAL == 1 >>> if (programmer == PROGRAMMER_INTERNAL && >> cb_check_image(newcontents, size) < 0) { >>> if (force_boardmismatch) { >>> -- >>> 2.1.4 >>> >>> >>> _______________________________________________ >>> flashrom mailing list >>> flashrom(a)flashrom.org >>> https://www.flashrom.org/mailman/listinfo/flashrom >> >> >> >> -- >> David Hendricks (dhendrix) >> Systems Software Engineer, Google Inc. >> >> _______________________________________________ >> flashrom mailing list >> flashrom(a)flashrom.org >> https://www.flashrom.org/mailman/listinfo/flashrom >> > > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://www.flashrom.org/mailman/listinfo/flashrom >

1 0

Re: [flashrom] [PATCH] RFC: enable flashrom to write images of arbitrary size
by Charlotte Plusplus 09 Nov '16

09 Nov '16

Hello That is very interesting. Do you have a way to automate that? I am testing ram stuff with coreboot, I don't need to flash a full 8MB image. I could just pass a -i of the cbfs content to only change the ramstage, and do a manual md5 of the various parts contained to only target the difference, but it seems a bit tedious. It would be nice to do have a way to do kind of diff between the currenttly flashed image and the desired image, and only flash the required changes. Charlotte On Tue, Nov 8, 2016 at 2:22 PM, David Hendricks via flashrom < flashrom(a)flashrom.org> wrote: > Hi Peter, > Thanks for the patch! However, I suspect this will not be accepted > since the size check is an important safety measure for the general > use case. > > In general layout files should be used for this sort of thing. The way > we've gone about this in the chromium.org branch is to augment the -i > syntax to allow the user to specify a region and corresponding file, > and we also added a "--fast-verify" mode to only verify regions which > were targeted. So for example you could do "flashrom -p <programmer> > -l <layout_file> -i region:filename.bin --fast-verify --ignore-fmap > -w" which will write filename.bin to the targeted region and verify > only that region. > > Details here: https://www.chromium.org/chromium-os/packages/cros- > flashrom#TOC-Partial-Reads-and-Writes > . LMK if this is any help. > > > > On Mon, Nov 7, 2016 at 1:00 PM, Peter Mamonov <pmamonov(a)gmail.com> wrote: > > Flashrom restricts an image size to be equal to a ROM capacity. This is > > inconvenient in case of large and slow ROM chips, when only part of the > ROM > > should be updated. This patch removes this restriction in a > quick-and-dirty > > manner. > > > > Signed-off-by: Peter Mamonov <pmamonov(a)gmail.com> > > --- > > flashrom.c | 26 +++++++++++++++----------- > > 1 file changed, 15 insertions(+), 11 deletions(-) > > > > diff --git a/flashrom.c b/flashrom.c > > index d51a44c..f805e00 100644 > > --- a/flashrom.c > > +++ b/flashrom.c > > @@ -1255,30 +1255,30 @@ int read_buf_from_file(unsigned char *buf, > unsigned long size, > > > > if ((image = fopen(filename, "rb")) == NULL) { > > msg_gerr("Error: opening file \"%s\" failed: %s\n", > filename, strerror(errno)); > > - return 1; > > + return -1; > > } > > if (fstat(fileno(image), &image_stat) != 0) { > > msg_gerr("Error: getting metadata of file \"%s\" failed: > %s\n", filename, strerror(errno)); > > fclose(image); > > - return 1; > > + return -1; > > } > > - if (image_stat.st_size != size) { > > + if (image_stat.st_size > size) { > > msg_gerr("Error: Image size (%jd B) doesn't match the > flash chip's size (%lu B)!\n", > > (intmax_t)image_stat.st_size, size); > > - fclose(image); > > - return 1; > > + return -1; > > } > > + size = image_stat.st_size; > > numbytes = fread(buf, 1, size, image); > > if (fclose(image)) { > > msg_gerr("Error: closing file \"%s\" failed: %s\n", > filename, strerror(errno)); > > - return 1; > > + return -1; > > } > > if (numbytes != size) { > > msg_gerr("Error: Failed to read complete file. Got %ld > bytes, " > > "wanted %ld!\n", numbytes, size); > > - return 1; > > + return -1; > > } > > - return 0; > > + return size; > > #endif > > } > > > > @@ -1481,7 +1481,10 @@ static int walk_eraseregions(struct flashctx > *flash, int erasefunction, > > * members so the loop below won't be executed for them. > > */ > > len = eraser.eraseblocks[i].size; > > - for (j = 0; j < eraser.eraseblocks[i].count; j++) { > > + for (j = 0; > > + j < eraser.eraseblocks[i].count && > > + start + len <= flash->chip->total_size * 1024; > > + j++) { > > /* Print this for every block except the first > one. */ > > if (i || j) > > msg_cdbg(", "); > > @@ -1988,11 +1991,12 @@ int doit(struct flashctx *flash, int force, > const char *filename, int read_it, > > } > > > > if (write_it || verify_it) { > > - if (read_buf_from_file(newcontents, size, filename)) { > > + size = read_buf_from_file(newcontents, size, filename); > > + if (size < 0) { > > ret = 1; > > goto out; > > } > > - > > + flash->chip->total_size = size / 1024; /* FIXME */ > > #if CONFIG_INTERNAL == 1 > > if (programmer == PROGRAMMER_INTERNAL && > cb_check_image(newcontents, size) < 0) { > > if (force_boardmismatch) { > > -- > > 2.1.4 > > > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > https://www.flashrom.org/mailman/listinfo/flashrom > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://www.flashrom.org/mailman/listinfo/flashrom >

1 0

[PATCH] RFC: enable flashrom to write images of arbitrary size
by Peter Mamonov 08 Nov '16

08 Nov '16

Flashrom restricts an image size to be equal to a ROM capacity. This is inconvenient in case of large and slow ROM chips, when only part of the ROM should be updated. This patch removes this restriction in a quick-and-dirty manner. Signed-off-by: Peter Mamonov <pmamonov(a)gmail.com> --- flashrom.c | 26 +++++++++++++++----------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/flashrom.c b/flashrom.c index d51a44c..f805e00 100644 --- a/flashrom.c +++ b/flashrom.c @@ -1255,30 +1255,30 @@ int read_buf_from_file(unsigned char *buf, unsigned long size, if ((image = fopen(filename, "rb")) == NULL) { msg_gerr("Error: opening file \"%s\" failed: %s\n", filename, strerror(errno)); - return 1; + return -1; } if (fstat(fileno(image), &image_stat) != 0) { msg_gerr("Error: getting metadata of file \"%s\" failed: %s\n", filename, strerror(errno)); fclose(image); - return 1; + return -1; } - if (image_stat.st_size != size) { + if (image_stat.st_size > size) { msg_gerr("Error: Image size (%jd B) doesn't match the flash chip's size (%lu B)!\n", (intmax_t)image_stat.st_size, size); - fclose(image); - return 1; + return -1; } + size = image_stat.st_size; numbytes = fread(buf, 1, size, image); if (fclose(image)) { msg_gerr("Error: closing file \"%s\" failed: %s\n", filename, strerror(errno)); - return 1; + return -1; } if (numbytes != size) { msg_gerr("Error: Failed to read complete file. Got %ld bytes, " "wanted %ld!\n", numbytes, size); - return 1; + return -1; } - return 0; + return size; #endif } @@ -1481,7 +1481,10 @@ static int walk_eraseregions(struct flashctx *flash, int erasefunction, * members so the loop below won't be executed for them. */ len = eraser.eraseblocks[i].size; - for (j = 0; j < eraser.eraseblocks[i].count; j++) { + for (j = 0; + j < eraser.eraseblocks[i].count && + start + len <= flash->chip->total_size * 1024; + j++) { /* Print this for every block except the first one. */ if (i || j) msg_cdbg(", "); @@ -1988,11 +1991,12 @@ int doit(struct flashctx *flash, int force, const char *filename, int read_it, } if (write_it || verify_it) { - if (read_buf_from_file(newcontents, size, filename)) { + size = read_buf_from_file(newcontents, size, filename); + if (size < 0) { ret = 1; goto out; } - + flash->chip->total_size = size / 1024; /* FIXME */ #if CONFIG_INTERNAL == 1 if (programmer == PROGRAMMER_INTERNAL && cb_check_image(newcontents, size) < 0) { if (force_boardmismatch) { -- 2.1.4

2 1

Invalid size. Asus P8Z77-V LX. W25Q64.V
by Лейба Бронштейн 08 Nov '16

08 Nov '16

[ 0.000000] DMI: System manufacturer System Product Name/P8Z77-V LX, BIOS 1502 11/09/2012 /usr/local/sbin/flashrom -p internal -w P8Z77-V-LX-ASUS-2501.CAP flashrom v0.9.9-r1954 on Linux 4.4.19-1-pve (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel Z77". Enabling flash write... Warning: SPI Configuration Lockdown activated. OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Error: Image size (8390656 B) doesn't match the flash chip's size (8388608 B)!

1 0

Re: [flashrom] FAILED: W25Q64.V bios flash on a ThinkPad
by Charlotte Plusplus 06 Nov '16

06 Nov '16

In case someone else has the same problem, I found a solution. It is weird but works reliably for me: the pins must not be connected one by one to the J100 header, but all at once. If you use floating wires, use duct tape to shape them into a plug. Insert it swiftly. Then it works fine 100% of the time. I got the idea after reading about timing issues on: http://dangerousprototypes.com/forum/viewtopic.php?f=40&t=4157 https://www.raspberrypi.org/forums/viewtopic.php?f=41&t=123825 I have no idea why it works, but it works. On 11/4/16, Charlotte Plusplus <pluspluscharlotte(a)gmail.com> wrote: > Hello > > I am trying to flash a W25Q64.V in a Thinkpad W520 using a Raspberry Pi > To make it easier, I soldered an ISP connector on the motherboard J100 > connector (https://www.coreboot.org/Board:lenovo/t520#Flashing) to > make sure I would have a good electrical connection. > WP and HOLD were left floating, and I used the 3.3V from the Raspberry Pi > pin 1. > The electrical connection was good: I could read the flash. I did it 4 > times to make sure the MD5 matched. They did. The strings inside the > flash matched the bios version, and ifdtool did recognize the image. > > When I tried to flash however, something weird happened: > > flashrom -w coreboot.pre apt-ge-p linux_spi:dev=/dev/spidev0.0 > Calibrating delay loop... delay loop is unreliable, trying to continue OK. > Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on linux_spi. > Reading old flash chip contents... done. > Erasing and writing flash chip... Erase/write done. > Verifying flash... FAILED at 0x007bbe00! Expected=0x24, Found=0x98, > failed byte count from 0x00000000-0x007fffff: 0x8e4 > Your flash chip is in an unknown state. > Please report this on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom(a)flashrom.org, thanks! > > Ever since, I can't access the chip. The laptop can't boot. The > original image can't be restored. > > Whenever I try to read the flash using the exact same command line as > before, I get: > > flashrom -r w520-bios-backup.bin -V -p linux_spi:dev=/dev/spidev0.0 > (...) > Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. > probe_spi_rdid_generic: id1 0x00, id2 0x00 > (...) > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). > > Funny enough, if I don't connect any cable to the raspberry, I get the > exact same error message. > > I tried various configuration: with the raspberry pi power, with WP > and HOLD set to high, with external power and WP and HOLD set to high > - nothing works. > I checked the W25Q64 specsheet > (ttps://cdn.sparkfun.com/datasheets/Dev/Teensy/w25q64fv.pdf), the > system board schematics > (http://kythuatphancung.vn/uploads/download/5165b_Wistron_Kendo-3_WS_-_10222…) > but I just don't understand what is happening. > > Any suggestion?? I have flashed with this raspberry before, and it > never when bad to the point that I could no longer even read the chip. > > I am afraid something really wrong happened. Any help is appreciated. >

1 0

FAILED: W25Q64.V bios flash on a ThinkPad
by Charlotte Plusplus 04 Nov '16

04 Nov '16

Hello I am trying to flash a W25Q64.V in a Thinkpad W520 using a Raspberry Pi To make it easier, I soldered an ISP connector on the motherboard J100 connector (https://www.coreboot.org/Board:lenovo/t520#Flashing) to make sure I would have a good electrical connection. WP and HOLD were left floating, and I used the 3.3V from the Raspberry Pi pin 1. The electrical connection was good: I could read the flash. I did it 4 times to make sure the MD5 matched. They did. The strings inside the flash matched the bios version, and ifdtool did recognize the image. When I tried to flash however, something weird happened: flashrom -w coreboot.pre apt-ge-p linux_spi:dev=/dev/spidev0.0 Calibrating delay loop... delay loop is unreliable, trying to continue OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x007bbe00! Expected=0x24, Found=0x98, failed byte count from 0x00000000-0x007fffff: 0x8e4 Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! Ever since, I can't access the chip. The laptop can't boot. The original image can't be restored. Whenever I try to read the flash using the exact same command line as before, I get: flashrom -r w520-bios-backup.bin -V -p linux_spi:dev=/dev/spidev0.0 (...) Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 (...) Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). Funny enough, if I don't connect any cable to the raspberry, I get the exact same error message. I tried various configuration: with the raspberry pi power, with WP and HOLD set to high, with external power and WP and HOLD set to high - nothing works. I checked the W25Q64 specsheet (ttps://cdn.sparkfun.com/datasheets/Dev/Teensy/w25q64fv.pdf), the system board schematics (http://kythuatphancung.vn/uploads/download/5165b_Wistron_Kendo-3_WS_-_10222…) but I just don't understand what is happening. Any suggestion?? I have flashed with this raspberry before, and it never when bad to the point that I could no longer even read the chip. I am afraid something really wrong happened. Any help is appreciated.

1 0

Success Report for Found chipset "Intel Lynx Point" with PCI ID 8086:8c5c
by Steve Kenton 01 Nov '16

01 Nov '16

The ECS H81H3-I Rev 1.0 motherboard BIOS has an option to disable the Management Engine, which I had to select before flashrom would work. There is also an ME_UNLOCK jumper on the motherboard which I left as shipped. In this configuration I have successfully run: flashrom -p internal -V flashrom -p internal -r oembios.rom flashrom -p internal -v oembios.rom flashrom -p internal -w oembios.rom I need to patch a BIOS and while this test just reflashed the existing contents as a baseline, flashrom seems to work on this hardware I recently cloned flashrom and built from source: $ svn co svn://flashrom.org/flashrom/trunk flashrom Below is the requested -V output flashrom v0.9.6.1-r1563 on Linux 3.19.0-69-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (3 args): flashrom -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 3685M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = 10016 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "ECS" DMI string system-product-name: "H81H3-I" DMI string system-version: "1.0" DMI string baseboard-manufacturer: "ECS" DMI string baseboard-product-name: "H81H3-I" DMI string baseboard-version: "1.0" DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8772 on port 0x2e Found chipset "Intel Lynx Point" with PCI ID 8086:8c5c. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... enable_flash_ich_dc_spi: unknown ICH generation. Please report! 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x8 Root Complex Register Block address = 0xfed1c000 GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (unknown) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0xd008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=0, FDV=1, FLOCKDN=1 WARNING: SPI Configuration Lockdown activated. The Flash Descriptor Security Override Strap-Pin is set. Restrictions implied by the FRAP and FREG registers are NOT in effect. Please note that Protected Range (PR) restrictions still apply. Reading OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x08: 0x00000000 (FADDR) 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. 0x58: 0x07ff0400 FREG1: BIOS region (0x00400000-0x007fffff) is read-write. 0x5C: 0x03ff0001 FREG2: Management Engine region (0x00001000-0x003fffff) is read-write. 0x90: 0x84 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xfc4240 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=2, SME=0, SCF=4 0x94: 0x0006 (PREOP) 0x96: 0x043b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9C: 0x0000019f (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x80802045 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002045 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x50444653 (FPB) SPI Read Configuration: prefetching enabled, caching enabled, OK. Super I/O ID 0x8772 is not on the list of flash capable controllers. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for GigaDevice GD25Q20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for GigaDevice GD25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for GigaDevice GD25Q80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for GigaDevice GD25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for GigaDevice GD25Q32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for GigaDevice GD25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for GigaDevice GD25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Chip status register is 00 Chip status register: Status Register Write Disable (SRWD) is not set Chip status register: Bit 6 is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Found Macronix flash chip "MX25L6405" (8192 kB, SPI) at physical address 0xff800000. Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Numonyx N25Q064, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for SST SST25LF040A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25LF080A, 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25VF010, 128 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Unknown SFDP-capable chip, 0 kB: Invalid OPCODE 0x5a, will not execute. Receiving SFDP signature failed. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Probing for Generic unknown SPI chip (REMS), 0 kB: Invalid OPCODE 0x90, will not execute. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xc9, id2 0x66, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x26, id2 0xf6, 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 0xc9, id2 0x66, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x26, id2 0xf6, id1 is normal flash content, id2 is normal flash content 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 0xc9, id2 0x66, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x74, id2 0x10, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x26, id2 0xf6, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x26, id2 0xf6, 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: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xb8, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x26, id2 0xf6, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x26, id2 0xf6, 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 0xc9, id2 0x66, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xb8, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x26, id2 0xf6, 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 0x26, id2 0xf6, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x26, id2 0xf6, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x26, id2 0xf6, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xc9, id2 0x66, id1 parity violation, id1 is normal flash content, id2 is normal flash content 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 0x26, id2 0xf6, id1 is normal flash content, id2 is normal flash content Found Macronix flash chip "MX25L6405" (8192 kB, SPI). No operations were specified. Restoring MMIO space at 0x7f4261fd38a0 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom November 2016