flashrom

flashrom@flashrom.org

3 participants
9188 discussions

Re: [flashrom] Erase error with hardware sequencing
by Stefan Tauner 26 Mar '12

26 Mar '12

On Tue, 27 Mar 2012 01:40:30 +0530 narayanan best <narayananbest(a)gmail.com> wrote: > > > I believe the cause is due to hardware sequencing write does not disable > > > SRPL (sector protection register lock). I used -p > > > internal:ich_spi_force=yes option which didn't help. > > > > > > This was confirmed when i gave ich_spi_mode=swseq (read or write) as > > > parameter, it disables the SRPL and next write of 16MB with hardware > > > sequencing succeeded. you are right with your diagnosis afaics. when i implemented hwseq i was not thinking about setups like yours. hwseq abstracts away so many aspects of the write process that it did not make a lot of sense to think about chip-specific write protections. but in the case hwseq is only used to be able to access two flash chips, it is (apparently) a viable use case for some. are you involved in the design of that specific machine and are you able to change the firmware? in that case i wonder why you made the design choice to use chip-specific write protections instead of the ones provided by the chipset. if you bought it completely i would like to know which board that is. in any case, changing flashrom to unlock the first flash chip with sw sequencing and then doing the rest of the process with hwseq would be a major effort. a possible workaround is to use swseq to access the first chip and hwseq for the other half. this could be done with layout files, see manpage for details please (layout files do only work for writing at the moment. patches exist for the other operation modes too, but they are not committed yet. this does not really affect you, because you only need a workaround for writing anyway). i also spotted a bug in ich_descriptors.c that showed up in your log. line 822 should be " if (nr > 5) {" instead of " if (nr >= 5) {" would be nice if you could recompile with that change and post another log. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Erase error with hardware sequencing
by Stefan Tauner 26 Mar '12

26 Mar '12

On Mon, 26 Mar 2012 23:54:15 +0530 narayanan best <narayananbest(a)gmail.com> wrote: > Hi, > > I have Intel ICH9 with 2 SPI flash chips each with 8MB. I am able to read > 16MB of flash chip with hardware sequencing. > But while writing the image i get > ERASE FAILED at 0x00100000! Expected=0xff , Read=0x44, failed byte count > from 0x00100000-0x0010ffff:0xfef4 > ERASE FAILED > > I believe the cause is due to hardware sequencing write does not disable > SRPL (sector protection register lock). I used -p > internal:ich_spi_force=yes option which didn't help. > > This was confirmed when i gave ich_spi_mode=swseq (read or write) as > parameter, it disables the SRPL and next write of 16MB with hardware > sequencing succeeded. > > Let me know if i am missing anything here. > > Thanks in advance. hi and thanks for your report! i dont have time right now to look at it, but it would be great if you could send a log of flashrom's output with the verbose flags "-VV" added to your write command line (especially the one with hwseq forced, both would be best). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Erase error with hardware sequencing
by narayanan best 26 Mar '12

26 Mar '12

Hi, I have Intel ICH9 with 2 SPI flash chips each with 8MB. I am able to read 16MB of flash chip with hardware sequencing. But while writing the image i get ERASE FAILED at 0x00100000! Expected=0xff , Read=0x44, failed byte count from 0x00100000-0x0010ffff:0xfef4 ERASE FAILED I believe the cause is due to hardware sequencing write does not disable SRPL (sector protection register lock). I used -p internal:ich_spi_force=yes option which didn't help. This was confirmed when i gave ich_spi_mode=swseq (read or write) as parameter, it disables the SRPL and next write of 16MB with hardware sequencing succeeded. Let me know if i am missing anything here. Thanks in advance.

1 0

Latest version in console
by Cole Byre 26 Mar '12

26 Mar '12

Hello. I used the Linux command sudo apt-get install flashrom to get flashrom on Linux mint..but when I run sudo flashrom, it tells me its version 0.9.4..which is outdated. What is the command to download the latest version of flashrom?

1 0

Re: [flashrom] [PATCH] spi25.c: Refactor spi_write_status_register helpers.
by Carl-Daniel Hailfinger 25 Mar '12

25 Mar '12

Am 31.01.2012 06:50 schrieb Stefan Tauner: > In r1115 "Write protection handling for Atmel AT25*" the old spi_write_status_register > function was duplicated to send WREN and EWSR commands respectively controlled > by a new common wrapper function spi_write_status_register without a reason. > Both functions' resulting code is equal apart from the opcode used. The code > itself does also differ in the macros used, but their value (apart from the opcode) > is equal. This patch adds a new parameter for the opcode to the helper function > which allows removal of the other one. This relies on the fact that EWSR and WREN > have the same INSIZE and OUTSIZE though. If that is really seen as an issue, the > sizes could be made parameters too. > > This patch also changes the wrapper so that it no longer sets the feature bits > of the struct flash(ctx) argument. This may result in changed output, because it > no longer implicitly disables the debug message in following executions. Ahem. Once we do the per-region unlock dance, this will be extremely painful. We have three choices: - Keep that part of the code as is. Not good. - Spit out that message for every status register write. Not good. - Fix all flash chip definitions. Good, but separate patch. How do we proceed? I'd like to keep the feature bit setting until the flash chip definitions have been fixed, but this is not a veto-style decision. > Also, spi_write_status_enable has been dead code since r658 or so. Remove it. > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Once the feature bit setting is decided upon, this is Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> with one small comment below. > --- > spi25.c | 90 ++++++++++----------------------------------------------------- > 1 files changed, 14 insertions(+), 76 deletions(-) > > diff --git a/spi25.c b/spi25.c > index 3ce7f08..d81616c 100644 > --- a/spi25.c > +++ b/spi25.c > @@ -720,81 +720,19 @@ int spi_block_erase_c7(struct flashctx *flash, unsigned int addr, > return spi_chip_erase_c7(flash); > } > > -int spi_write_status_enable(struct flashctx *flash) > -{ > - static const unsigned char cmd[JEDEC_EWSR_OUTSIZE] = { JEDEC_EWSR }; > - int result; > - > - /* Send EWSR (Enable Write Status Register). */ > - result = spi_send_command(flash, sizeof(cmd), JEDEC_EWSR_INSIZE, cmd, NULL); > - > - if (result) > - msg_cerr("%s failed\n", __func__); > - > - return result; > -} > - > -/* > - * This is according the SST25VF016 datasheet, who knows it is more > - * generic that this... > - */ > -static int spi_write_status_register_ewsr(struct flashctx *flash, int status) > +static int spi_write_status_register_flag(struct flashctx *flash, int status, const unsigned char opcode) enable_opcode instead of opcode. > { > int result; > int i = 0; > - struct spi_command cmds[] = { > - { > - /* WRSR requires either EWSR or WREN depending on chip type. */ > - .writecnt = JEDEC_EWSR_OUTSIZE, > - .writearr = (const unsigned char[]){ JEDEC_EWSR }, > - .readcnt = 0, > - .readarr = NULL, > - }, { > - .writecnt = JEDEC_WRSR_OUTSIZE, > - .writearr = (const unsigned char[]){ JEDEC_WRSR, (unsigned char) status }, > - .readcnt = 0, > - .readarr = NULL, > - }, { > - .writecnt = 0, > - .writearr = NULL, > - .readcnt = 0, > - .readarr = NULL, > - }}; > - > - result = spi_send_multicommand(flash, cmds); > - if (result) { > - msg_cerr("%s failed during command execution\n", > - __func__); > - /* No point in waiting for the command to complete if execution > - * failed. > - */ > - return result; > - } > - /* WRSR performs a self-timed erase before the changes take effect. > - * This may take 50-85 ms in most cases, and some chips apparently > - * allow running RDSR only once. Therefore pick an initial delay of > - * 100 ms, then wait in 10 ms steps until a total of 5 s have elapsed. > + /* > + * WRSR requires either EWSR or WREN depending on chip type. > + * The code below relies on the fact hat EWSR and WREN have the same > + * INSIZE and OUTSIZE. > */ > - programmer_delay(100 * 1000); > - while (spi_read_status_register(flash) & JEDEC_RDSR_BIT_WIP) { > - if (++i > 490) { > - msg_cerr("Error: WIP bit after WRSR never cleared\n"); > - return TIMEOUT_ERROR; > - } > - programmer_delay(10 * 1000); > - } > - return 0; > -} > - > -static int spi_write_status_register_wren(struct flashctx *flash, int status) > -{ > - int result; > - int i = 0; > struct spi_command cmds[] = { > { > - /* WRSR requires either EWSR or WREN depending on chip type. */ > .writecnt = JEDEC_WREN_OUTSIZE, > - .writearr = (const unsigned char[]){ JEDEC_WREN }, > + .writearr = (const unsigned char[]){ opcode }, > .readcnt = 0, > .readarr = NULL, > }, { > @@ -811,8 +749,7 @@ static int spi_write_status_register_wren(struct flashctx *flash, int status) > > result = spi_send_multicommand(flash, cmds); > if (result) { > - msg_cerr("%s failed during command execution\n", > - __func__); > + msg_cerr("%s failed during command execution\n", __func__); > /* No point in waiting for the command to complete if execution > * failed. > */ > @@ -836,17 +773,18 @@ static int spi_write_status_register_wren(struct flashctx *flash, int status) > > int spi_write_status_register(struct flashctx *flash, int status) > { > + int feature_bits = flash->feature_bits; > int ret = 1; > > - if (!(flash->feature_bits & (FEATURE_WRSR_WREN | FEATURE_WRSR_EWSR))) { > + if (!(feature_bits & (FEATURE_WRSR_WREN | FEATURE_WRSR_EWSR))) { > msg_cdbg("Missing status register write definition, assuming " > "EWSR is needed\n"); > - flash->feature_bits |= FEATURE_WRSR_EWSR; > + feature_bits |= FEATURE_WRSR_EWSR; > } > - if (flash->feature_bits & FEATURE_WRSR_WREN) > - ret = spi_write_status_register_wren(flash, status); > - if (ret && (flash->feature_bits & FEATURE_WRSR_EWSR)) > - ret = spi_write_status_register_ewsr(flash, status); > + if (feature_bits & FEATURE_WRSR_WREN) > + ret = spi_write_status_register_flag(flash, status, JEDEC_WREN); > + if (ret && (feature_bits & FEATURE_WRSR_EWSR)) > + ret = spi_write_status_register_flag(flash, status, JEDEC_EWSR); > return ret; > } > Regards, Carl-Daniel -- http://www.hailfinger.org/

3 2

About mcp73 support on flashrom
by Olcay Korkmaz 22 Mar '12

22 Mar '12

Hello all I have Zotac 630i-itx board (old pcb rev model..very old i guess) flashrom -V log details on mail attachment is it safe to erase/write process extra info bios dump is ok via flashrom -r command -- Olcay K.

1 0

ASUS P5VD2-MX (works, but onboard lan mac is lost)
by Marcos Felipe Rasia de Mello 21 Mar '12

21 Mar '12

flashrom -w works, but the onboard lan mac address is reseted to 00 00 00 00 00 10. Same problem http://www.flashrom.org/pipermail/flashrom/2012-March/009004.html but I didn't find any string that could be the mac address in the P5VD2-MX 1017 BIOS image. I've read AwardBIOS can have the lan's mac stored inside a compressed module. Any tips is welcome. Marcos

1 0

output of flashrom -V on a asrock-K10N78FullHD-hSLI
by Michael.Burkhard＠gmx.net 20 Mar '12

20 Mar '12

wie gewünscht / as requested Michael

1 0

Bios Information
by rayfward 19 Mar '12

19 Mar '12

flashrom v0.9.2-r1141 on Linux 2.6.38-8-generic (x86_64), built with libpci 3.1.7, GCC 4.5.1, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 669M loops per second, 10 myus = 11 us, 100 myus = 101 us, 1000 myus = 1000 us, 10000 myus = 9997 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Gigabyte Technology Co., Ltd." DMI string system-product-name: "M52L-S3P" DMI string system-version: " " DMI string baseboard-manufacturer: "Gigabyte Technology Co., Ltd." DMI string baseboard-product-name: "M52L-S3P" DMI string baseboard-version: "x.x" DMI string chassis-type: "Desktop" Found ITE Super I/O, id 8718 Found chipset "NVIDIA MCP61", enabling flash write... chipset PCI ID is 10de:03e0, This chipset is not really supported yet. Guesswork... ISA/LPC bridge reg 0x8a contents: 0x00, bit 6 is 0, bit 5 is 0 Flash bus type is LPC Found SMBus device 10de:03eb at 00:01:1 MCP SPI BAR is at 0xfec80000 Strange. MCP SPI BAR is valid, but chipset apparently doesn't have SPI enabled. Please send the output of "flashrom -V" to flashrom(a)flashrom.org to help us finish support for your chipset. Thanks. OK. This chipset supports the following protocols: LPC. Serial flash segment 0xfffe0000-0xffffffff enabled Serial flash segment 0x000e0000-0x000fffff enabled Serial flash segment 0xffee0000-0xffefffff disabled Serial flash segment 0xfff80000-0xfffeffff enabled LPC write to serial flash enabled Serial flash pin 29 Serial flash port 0x0820 Probing for AMD Am29F010A/B, 128 KB: skipped. Probing for AMD Am29F002(N)BB, 256 KB: skipped. Probing for AMD Am29F002(N)BT, 256 KB: skipped. Probing for AMD Am29F016D, 2048 KB: skipped. Probing for AMD Am29F040B, 512 KB: skipped. Probing for AMD Am29F080B, 1024 KB: skipped. Probing for AMD Am29LV040B, 512 KB: skipped. Probing for AMD Am29LV081B, 1024 KB: skipped. Probing for AMIC A25L05PT, 64 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L05PU, 64 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L10PT, 128 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L10PU, 128 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L20PT, 256 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L20PU, 256 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L40PT, 512 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L40PU, 512 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L80P, 1024 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L16PT, 2048 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L16PU, 2048 KB: 4 byte RDID not supported on this SPI controller Probing for AMIC A25L512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A25L010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A25L020, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A25L040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A25L080, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A25L016, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A25L032, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A25LQ032, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for AMIC A29002B, 256 KB: skipped. Probing for AMIC A29002T, 256 KB: skipped. Probing for AMIC A29040B, 512 KB: skipped. Probing for AMIC A49LF040A, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ASD AE49F2008, 256 KB: skipped. Probing for Atmel AT25DF021, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DF041A, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DF081, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DF081A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DF321, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DF321A, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DF641, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25DQ161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25F512B, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25FS010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT25FS040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT26DF041, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT26DF081A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT26DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT26DF161A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT26F004, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT29C512, 64 KB: skipped. Probing for Atmel AT29C010A, 128 KB: skipped. Probing for Atmel AT29C020, 256 KB: skipped. Probing for Atmel AT29C040A, 512 KB: skipped. Probing for Atmel AT45CS1282, 16896 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB011D, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB021D, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB041D, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB081D, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB161D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB321C, 4224 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB321D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT45DB642D, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Atmel AT49BV512, 64 KB: skipped. Probing for Atmel AT49F020, 256 KB: skipped. Probing for Atmel AT49F002(N), 256 KB: skipped. Probing for Atmel AT49F002(N)T, 256 KB: skipped. Probing for EMST F49B002UA, 256 KB: skipped. Probing for EMST F25L008A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B05T, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B10T, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B20T, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B40T, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B80T, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B16T, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B32T, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25B64T, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25D16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25F05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25F10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25F20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25F40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25F80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25F16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN25F32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon EN29F010, 128 KB: skipped. Probing for Eon EN29F002(A)(N)B, 256 KB: skipped. Probing for Eon EN29F002(A)(N)T, 256 KB: skipped. Probing for Fujitsu MBM29F004BC, 512 KB: skipped. Probing for Fujitsu MBM29F004TC, 512 KB: skipped. Probing for Fujitsu MBM29F400BC, 512 KB: skipped. Probing for Fujitsu MBM29F400TC, 512 KB: skipped. Probing for Hyundai HY29F002T, 256 KB: skipped. Probing for Hyundai HY29F002B, 256 KB: skipped. Probing for Intel 28F001BX-B, 128 KB: skipped. Probing for Intel 28F001BX-T, 128 KB: skipped. Probing for Intel 28F002BC-T, 256 KB: skipped. Probing for Intel 28F004S5, 512 KB: skipped. Probing for Intel 28F004BV/BE-B, 512 KB: skipped. Probing for Intel 28F004BV/BE-T, 512 KB: skipped. Probing for Intel 28F400BV/CV/CE-B, 512 KB: skipped. Probing for Intel 28F400BV/CV/CE-T, 512 KB: skipped. Probing for Intel 82802AB, 512 KB: skipped. Probing for Intel 82802AC, 1024 KB: skipped. Probing for Macronix MX25L512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L1005, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L2005, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L4005, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L8005, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L1605, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L1635D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L3205, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L3235D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L6405, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX25L12805, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix MX29F001B, 128 KB: skipped. Probing for Macronix MX29F001T, 128 KB: skipped. Probing for Macronix MX29F002B, 256 KB: skipped. Probing for Macronix MX29F002T, 256 KB: skipped. Probing for Macronix MX29LV040, 512 KB: skipped. Probing for MoselVitelic V29C51000B, 64 KB: skipped. Probing for MoselVitelic V29C51000T, 64 KB: skipped. Probing for MoselVitelic V29C51400B, 512 KB: skipped. Probing for MoselVitelic V29C51400T, 512 KB: skipped. Probing for MoselVitelic V29LC51000, 64 KB: skipped. Probing for MoselVitelic V29LC51001, 128 KB: skipped. Probing for MoselVitelic V29LC51002, 256 KB: skipped. Probing for Numonyx M25PE10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Numonyx M25PE20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Numonyx M25PE40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Numonyx M25PE80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Numonyx M25PE16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC Pm25LV010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC Pm25LV016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC Pm25LV020, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC Pm25LV040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC Pm25LV080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC Pm25LV512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC Pm29F002T, 256 KB: skipped. Probing for PMC Pm29F002B, 256 KB: skipped. Probing for PMC Pm39LV010, 128 KB: skipped. Probing for PMC Pm39LV020, 256 KB: skipped. Probing for PMC Pm39LV040, 512 KB: skipped. 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sanyo LF25FW203A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Sharp LHF00L04, 1024 KB: skipped. Probing for Spansion S25FL008A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Spansion S25FL016A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for SST SST25VF016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for SST SST25VF032B, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for SST SST25VF064C, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for SST SST25VF040.REMS, 512 KB: probe_spi_rems: id1 0xbf, id2 0x8e Probing for SST SST25VF040B, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for SST SST25LF040A.RES, 512 KB: probe_spi_res2: id1 0xbf, id2 0x8e Probing for SST SST25VF040B.REMS, 512 KB: probe_spi_rems: id1 0xbf, id2 0x8e Probing for SST SST25VF080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Chip status register is 00 Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Bit 5 / Block Protect 3 (BP3) is not set Chip status register: Bit 4 / Block Protect 2 (BP2) is not set Chip status register: Bit 3 / Block Protect 1 (BP1) is not set Chip status register: Bit 2 / Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Found chip "SST SST25VF080B" (1024 KB, SPI) at physical address 0xfff00000. Probing for SST SST28SF040A, 512 KB: skipped. Probing for SST SST29EE010, 128 KB: skipped. Probing for SST SST29LE010, 128 KB: skipped. Probing for SST SST29EE020A, 256 KB: skipped. Probing for SST SST29LE020, 256 KB: skipped. Probing for SST SST39SF512, 64 KB: skipped. Probing for SST SST39SF010A, 128 KB: skipped. Probing for SST SST39SF020A, 256 KB: skipped. Probing for SST SST39SF040, 512 KB: skipped. Probing for SST SST39VF512, 64 KB: skipped. Probing for SST SST39VF010, 128 KB: skipped. Probing for SST SST39VF020, 256 KB: skipped. Probing for SST SST39VF040, 512 KB: skipped. Probing for SST SST39VF080, 1024 KB: skipped. Probing for SST SST49LF002A/B, 256 KB: skipped. Probing for SST SST49LF003A/B, 384 KB: skipped. Probing for SST SST49LF004A/B, 512 KB: skipped. Probing for SST SST49LF004C, 512 KB: skipped. Probing for SST SST49LF008A, 1024 KB: skipped. Probing for SST SST49LF008C, 1024 KB: skipped. Probing for SST SST49LF016C, 2048 KB: skipped. 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, 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 0x24, id2 0x46, 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, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M25P05-A, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P05.RES, 64 KB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P10.RES, 128 KB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P40-old, 512 KB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M25P128, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST M29F002B, 256 KB: skipped. Probing for ST M29F002T/NT, 256 KB: skipped. Probing for ST M29F040B, 512 KB: skipped. Probing for ST M29F400BB, 512 KB: skipped. Probing for ST M29F400BT, 512 KB: skipped. Probing for ST M29W010B, 128 KB: skipped. Probing for ST M29W040B, 512 KB: skipped. Probing for ST M29W512B, 64 KB: skipped. Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0x24, id2 0x46, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0x24, id2 0x46, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 KB: skipped. Probing for ST M50FW016, 2048 KB: skipped. Probing for ST M50FW040, 512 KB: skipped. Probing for ST M50FW080, 1024 KB: skipped. Probing for ST M50LPW116, 2048 KB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 KB: skipped. Probing for TI TMS29F002RB, 256 KB: skipped. Probing for TI TMS29F002RT, 256 KB: skipped. Probing for Winbond W25Q80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25Q16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25Q32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25Q64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25x10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25x20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25x40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25x80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25x16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25x32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W25x64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Winbond W29C011, 128 KB: skipped. Probing for Winbond W29C020C, 256 KB: skipped. Probing for Winbond W29C040P, 512 KB: skipped. Probing for Winbond W29EE011, 128 KB: skipped. Probing for Winbond W39V040A, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 KB: probe_jedec_common: id1 0xff, id2 0xff, 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 KB: skipped. Probing for Winbond W39V080A, 1024 KB: probe_jedec_common: id1 0x24, id2 0x46, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U, 256 KB: skipped. Probing for Winbond W49F020, 256 KB: skipped. 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: skipped. Probing for Winbond W39V080FA, 1024 KB: skipped. Probing for Winbond W39V080FA (dual mode), 512 KB: skipped. Probing for AMIC unknown AMIC SPI chip, 0 KB: 4 byte RDID not supported on this SPI controller Probing for Atmel unknown Atmel SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Eon unknown Eon SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Macronix unknown Macronix SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for PMC unknown PMC SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for SST unknown SST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for ST unknown ST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Sanyo unknown Sanyo SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Generic unknown SPI chip (RDID), 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x258e Probing for Generic unknown SPI chip (REMS), 0 KB: probe_spi_rems: id1 0xbf, id2 0x8e No operations were specified.

1 0

Optiplex 380 BIOS read
by sai＠rawthrills.com 19 Mar '12

19 Mar '12

Hello All, I am trying to use flashrom to read/write my bios settings. This is the error that I get when I try to read the BIOS: Found chipset "Intel ICH7/ICH7R". Enabling flash write... WARNING: Setting 0xdc from 0x2 to 0x3 on ICH7/ICH7R failed. New value is 0x2. WARNING: SPI Configuration Lockdown activated. Setting BBAR to 0x00000000 failed! New value: 0x00e00000. PROBLEMS, continuing anyway Found Macronix flash chip "MX25L1605" (2048 kB, SPI) at physical address 0xffe00000. ich_spi_send_command: Internal command size error for opcode 0xab, got writecnt=4, want =1 ich_spi_send_command: Internal command size error for opcode 0xab, got writecnt=4, want =1 Reading flash... Read operation failed! FAILED. When I read through this mail archives, I learned that SPI locked down configuration is not possible. I read through the list of supported hardware and I could see that MX25L1605 is among the list of supported hardware. But I still not able to read my BIOS settings. Any suggestions would be appreciated Sai

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom