flashrom April 2012

flashrom@flashrom.org

44 participants
141 discussions

LGPL
by Rolette, James (Jay) 25 Apr '12

25 Apr '12

Howdy, I started asking my question on IRC and it was suggested that it might be better to have the discussion on the mailing list. Here's the discussion from IRC so far: [16:02] <rolette> Howdy. Is there any possibility of releasing flashrom under LGPL rather than GPL? I've searched through the docs, wiki, archives, etc. but haven't seen any discussions around this issue. [16:07] <stefanct> i'd guess that the problem did not arise yet because libflashrom is not really ready for use [16:08] <stefanct> feel free to start a thread on the ml :) [17:06] <PaulePanter> rolette: Why do you need LGPL? [17:44] <carldani> rolette: We had discussions about GPLv2 vs GPLv3, but I've never seen a request for LGPL. LGPL would only make sense if parts of flashrom should be linked against GPLv2-incompatible (e.g. GPLv3/proprietary) code. [17:47] <carldani> rolette: To make sure we can always incorporate flashrom code changes back into our codebase, we decided to stick to GPLv2. [17:49] <carldani> rolette: AFAIK Google modified flashrom to have a different command line interface and additional features for better integration into their update software. That update software just executes flashrom in a separate process and has a clean licensing barrier that way. [17:50] <carldani> rolette: That approach may work for you as well. [17:56] <carldani> rolette: And if you need support for some odd hardware where the vendor only offers a binary-only driver (e.g. some external programmers), there's always the option of reverse engineering it. We've done that in the past, and it works fine and is legally sound thanks to EU legislation which allows reverse engineering for interoperability regardless of what the vendor/manufacturer says. [17:59] <carldani> rolette: Most flashrom developers live in the EU, and quite a few of us are pretty good at reverse engineering. [18:02] <carldani> rolette: I would be very interested in hearing about a use case which requires flashrom to be LGPL. Please tell us about the background of your question. [07:31] <rolette> Thanks to PaulePanter and carldani for the responses. The reason I'm asking about LGPL is that I'm interested in porting flashrom to VxWorks and using it in an embedded system. [07:32] <rolette> Historically we've written our own custom code for programming the various programmable parts we use and it makes more sense to work with something like flashrom if possible [07:33] <rolette> More than happy to contribute back our changes, but need the license to be something we can use in a system with flat memory space, etc. [07:34] <rolette> libflashrom is really what we'd be more interested in, but looks too early for that. Might be something we could help build if we can work out the licensing issues [07:35] <idwer> libflashrom would be derived work, therefor still be GPL2 licensed (afaik, ianal) [07:36] <rolette> Yep, understood. That's why I started by asking if there was any way to license flashrom as LGPL :) [07:39] <rolette> Given how common programmable parts are in embedded systems, seems like LGPL would end up netting more contributions from companies as they add support for the parts they are using on their designs [07:40] <rolette> Although I'm sure I'm not bringing up anything you guys haven't discussed [07:41] <rolette> Let me know if this is something that I should be discussing on the mailing list instead. I started here mainly in case there was going to be an immediate "hell no!" reaction [07:46] <stefanct> all active developers are here, but since i doubt that there will be an immediate conclusion it is probably a good idea to have something more persistent... i.e. a thread on the ml. Thanks, Jay

1 0

Re: [flashrom] Fedora 8 cross compile flashrom failed
by Idwer Vollering 25 Apr '12

25 Apr '12

Op 25 april 2012 13:11 heeft 陳力綸 <chychen.chen(a)msa.hinet.net> het volgende geschreven: > Dear Sir: > > > > Because I am also a DOS fans not much like using OS(like Windows, Linux) > to flash BIOS. > > > > And cross compiler is much interesting to me, because I not touch it > before. Perhaps you can ask a colleague for assistance? > > > > So, I am eager want to know how can I learn to set up a cross compiler > environment for me to play with funny. Start with installing DJGPP [1] and follow the steps documented at the DOS wiki page [2]. [1] http://www.delorie.com/djgpp/ [2] http://www.flashrom.org/DOS > > > > So, I do need your help to do so, I am stupid a little but I am a work > hard man. If you want I can build a DOS .exe for you; send a proper patch with your Foxconn/WynMax as the sign-off: http://flashrom.org/Development_Guidelines > > > > Best Regards, > > Loren Chen > > From: Idwer Vollering [mailto:vidwer@gmail.com] > Sent: Wednesday, April 25, 2012 6:42 PM > To: 陳力綸 > Cc: flashrom > Subject: Re: Fedora 8 cross compile flashrom failed > > > > > CC'ing flashrom(a)flashrom.org, please use reply-to-all. > > Op 25 april 2012 06:53 schreef 陳力綸 <chychen.chen(a)msa.hinet.net> het > volgende: > > Dear Sir: > > > Hello, > > > > > I am s senior BIOS engineer, > > > > I try cross compile the flashrom for DOS but it say can’t not fount > pciutil header and can’t build. > > > May I ask why you are using DOS, as a target operating system, instead of > Linux? > > > See this page: http://www.flashrom.org/Downloads > You have to install, quote: "pciutils development package > (pciutils-dev/libpci-dev/pciutils-devel, depending on OS/distribution)" > > > > > Can you give me some hinet about how to correct dot it? > > > Yes: you have to adjust/include the path(s) to i586-pc-msdosdjgpp-gcc and > the cross-compiled versions of libgetopt ( http://assembler.cz/flashrom/ ) > and libpci. > I suggest that you study flashrom's Makefile, all the hints should be there. > > > > > Thank you. > > > > Best Regards, > > Loren Chen > > > Idwer

1 0

Re: [flashrom] Fedora 8 cross compile flashrom failed
by 陳力綸 25 Apr '12

25 Apr '12

Dear Sir: Loren Chen born: 13. 02. 1964 address:ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ, Taiwan Republic email: chychen.chen(a)msa.hinet.net BR, Loren From: 陳力綸 [mailto:chychen.chen@msa.hinet.net] Sent: Wednesday, April 25, 2012 7:11 PM To: 'Idwer Vollering' Cc: 'flashrom' Subject: RE: Fedora 8 cross compile flashrom failed Dear Sir: Because I am also a DOS fans not much like using OS(like Windows, Linux) to flash BIOS. And cross compiler is much interesting to me, because I not touch it before. So, I am eager want to know how can I learn to set up a cross compiler environment for me to play with funny. So, I do need your help to do so, I am stupid a little but I am a work hard man. Best Regards, Loren Chen From: Idwer Vollering [mailto:vidwer@gmail.com] Sent: Wednesday, April 25, 2012 6:42 PM To: 陳力綸 Cc: flashrom Subject: Re: Fedora 8 cross compile flashrom failed CC'ing flashrom(a)flashrom.org, please use reply-to-all. Op 25 april 2012 06:53 schreef 陳力綸 <chychen.chen(a)msa.hinet.net> het volgende: Dear Sir: Hello, I am s senior BIOS engineer, I try cross compile the flashrom for DOS but it say can’t not fount pciutil header and can’t build. May I ask why you are using DOS, as a target operating system, instead of Linux? See this page: http://www.flashrom.org/Downloads You have to install, quote: "pciutils development package (pciutils-dev/libpci-dev/pciutils-devel, depending on OS/distribution)" Can you give me some hinet about how to correct dot it? Yes: you have to adjust/include the path(s) to i586-pc-msdosdjgpp-gcc and the cross-compiled versions of libgetopt ( http://assembler.cz/flashrom/ ) and libpci. I suggest that you study flashrom's Makefile, all the hints should be there. Thank you. Best Regards, Loren Chen Idwer

1 0

Re: [flashrom] Fedora 8 cross compile flashrom failed
by 陳力綸 25 Apr '12

25 Apr '12

Dear Sir: Because I am also a DOS fans not much like using OS(like Windows, Linux) to flash BIOS. And cross compiler is much interesting to me, because I not touch it before. So, I am eager want to know how can I learn to set up a cross compiler environment for me to play with funny. So, I do need your help to do so, I am stupid a little but I am a work hard man. Best Regards, Loren Chen From: Idwer Vollering [mailto:vidwer@gmail.com] Sent: Wednesday, April 25, 2012 6:42 PM To: 陳力綸 Cc: flashrom Subject: Re: Fedora 8 cross compile flashrom failed CC'ing flashrom(a)flashrom.org, please use reply-to-all. Op 25 april 2012 06:53 schreef 陳力綸 <chychen.chen(a)msa.hinet.net> het volgende: Dear Sir: Hello, I am s senior BIOS engineer, I try cross compile the flashrom for DOS but it say can’t not fount pciutil header and can’t build. May I ask why you are using DOS, as a target operating system, instead of Linux? See this page: http://www.flashrom.org/Downloads You have to install, quote: "pciutils development package (pciutils-dev/libpci-dev/pciutils-devel, depending on OS/distribution)" Can you give me some hinet about how to correct dot it? Yes: you have to adjust/include the path(s) to i586-pc-msdosdjgpp-gcc and the cross-compiled versions of libgetopt ( http://assembler.cz/flashrom/ ) and libpci. I suggest that you study flashrom's Makefile, all the hints should be there. Thank you. Best Regards, Loren Chen Idwer

1 0

Re: [flashrom] Fedora 8 cross compile flashrom failed
by Idwer Vollering 25 Apr '12

25 Apr '12

CC'ing flashrom(a)flashrom.org, please use reply-to-all. Op 25 april 2012 06:53 schreef 陳力綸 <chychen.chen(a)msa.hinet.net> het volgende: > Dear Sir: > Hello, > **** > > ** ** > > I am s senior BIOS engineer,**** > > ** ** > > I try cross compile the flashrom for DOS but it say can’t not fount > pciutil header and can’t build. > May I ask why you are using DOS, as a target operating system, instead of Linux? See this page: http://www.flashrom.org/Downloads You have to install, quote: "pciutils development package (pciutils-dev/libpci-dev/pciutils-devel, depending on OS/distribution)" > **** > > ** ** > > Can you give me some hinet about how to correct dot it? > Yes: you have to adjust/include the path(s) to i586-pc-msdosdjgpp-gcc and the cross-compiled versions of libgetopt ( http://assembler.cz/flashrom/ ) and libpci. I suggest that you study flashrom's Makefile, all the hints should be there. > **** > > ** ** > > Thank you.**** > > ** ** > > Best Regards,**** > > Loren Chen**** > Idwer

1 0

Re: [flashrom] Unable to update the bios
by David Hendricks 25 Apr '12

25 Apr '12

On Tue, Apr 24, 2012 at 3:42 PM, David Hendricks <dhendrix(a)google.com>wrote: > Also, your chipset might be configured to target the LPC bus instead of > the SPI bus. > More specifically, check the value of the boot BIOS straps (BBS) register. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Unable to update the bios
by David Hendricks 25 Apr '12

25 Apr '12

Hi Raghu, I've seen similar symptoms when on laptops when embedded controller (EC) interactions interfere. Delay loop calibration can be interfered if the EC is spamming the host chipset with SCIs (check dmesg output and see if the kernel complains about interrupt storms or some such). Also, if the EC and chipset BIOS share a SPI chip, then the EC might attempting to accessing the SPI chip at the same time and interfering. You may need to consult your mainboard vendor and ask them if there is an "update mode" command you can use to prevent it from interfering with your SPI chip. Also, your chipset might be configured to target the LPC bus instead of the SPI bus. Please post the verbose output using the -V flag. You can paste it at http://paste.flashrom.org.

1 0

FAILED: MX25L1605 on Thinkpad X60s
by Motiejus Jakštys 24 Apr '12

24 Apr '12

Hi, I carefully followed the instructions by Peter Stuge: http://comments.gmane.org/gmane.linux.bios/69354 Used latest git flashrom and coreboot with Thinkpad X60s 1702WNQ. Got this error: pierce# ../flashrom/flashrom -p internal:laptop=force_I_want_a_brick -w build/coreboot.rom flashrom v0.9.5.2-r1523 on Linux 2.6.32-5-686 (i686), built with libpci 3.1.7, GCC 4.4.5, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. ======================================================================== WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH7M". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. Found Macronix flash chip "MX25L1605" (2048 kB, SPI) at physical address 0xffe00000. Note: If the following flash access fails, try -p internal:mainboard=<vendor>:<mainboard>. Reading old flash chip contents... done. Erasing and writing flash chip... spi_block_erase_20 failed during command execution at address 0x0 Reading current flash chip contents... done. spi_block_erase_52 failed during command execution at address 0x0 Reading current flash chip contents... done. Transaction error! spi_block_erase_d8 failed during command execution at address 0x1f0000 Reading current flash chip contents... done. spi_chip_erase_60 failed during command execution Reading current flash chip contents... done. spi_chip_erase_c7 failed during command execution FAILED! Uh oh. Erase/write failed. Checking if anything changed. Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Where should I start fixing the problem? The computer is running. Thanks a lot :) Motiejus

2 6

Flashrom report
by Paweł Drewniak 24 Apr '12

24 Apr '12

Hi, as requested by the program, a report for the read below: woody-laptop flashrom # ./flashrom -p internal:laptop=force_I_want_a_brick -V -r ../x1.bios flashrom v0.9.5.2-r1523 on Linux 3.2.12-gentoo-woody (x86_64), built with libpci 3.1.9, GCC 4.5.3, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 3094M loops per second, 10 myus = 9 us, 100 myus = 116 us, 1000 myus = 990 us, 10000 myus = 9803 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "1291CTO" DMI string system-version: "ThinkPad X1" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "1291CTO" DMI string baseboard-version: "Not Available" DMI string chassis-type: "Notebook" Laptop detected via DMI. ======================================================================== WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel QM67" with PCI ID 8086:1c4f. This chipset is marked as untested. If you are using an up-to-date version of flashrom please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x0 0xffe00000/0xffa00000 FWH IDSEL: 0x0 0xffd80000/0xff980000 FWH IDSEL: 0x0 0xffd00000/0xff900000 FWH IDSEL: 0x0 0xffc80000/0xff880000 FWH IDSEL: 0x0 0xffc00000/0xff800000 FWH IDSEL: 0xf 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 disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x380000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x8 Root Complex Register Block address = 0xfed1c000 GCS = 0xc21: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 WARNING: SPI Configuration Lockdown activated. Reading OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x08: 0x00000000 (FADDR) 0x50: 0x00000a0b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b 0x54: 0x00000000 FREG0: WARNING: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x07ff0500 FREG1: BIOS region (0x00500000-0x007fffff) is read-write. 0x5C: 0x04ff0003 FREG2: WARNING: Management Engine region (0x00003000-0x004fffff) is locked. 0x60: 0x00020001 FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. 0x74: 0x9fff0780 PR0: WARNING: 0x00780000-0x01ffffff is read-only. Please send a verbose log to flashrom(a)flashrom.org if this board is not listed on http://flashrom.org/Supported_hardware#Supported_mainboards yet. Writes have been disabled. You can enforce write support with the ich_spi_force programmer option, but it will most likely harm your hardware! If you force flashrom you will get no support if something breaks. 0x90: 0xc4 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf84200 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=2, SME=0, SCF=0 0x94: 0x0406 (PREOP) 0x96: 0x0f90 (OPTYPE) 0x98: 0x0301059f (OPMENU) 0x9C: 0x00000220 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00802005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x00000000 (FPB) SPI Read Configuration: prefetching enabled, caching enabled, OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for GigaDevice GD25Q20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for GigaDevice GD25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for GigaDevice GD25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for GigaDevice GD25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for GigaDevice GD25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for GigaDevice GD25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for GigaDevice GD25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Numonyx N25Q064, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 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 0x20, id2 0x7117 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Chip status register is 00 Found ST flash chip "M25PX64" (8192 kB, SPI) at physical address 0xff800000. Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 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 0x20, id2 0x7117 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7117 Probing for Generic unknown SPI chip (REMS), 0 kB: Invalid OPCODE 0x90, will not execute. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0x75, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x04, id2 0x9e, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x04, id2 0x9e, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xda, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Found ST flash chip "M25PX64" (8192 kB, SPI). === This flash part has status UNTESTED for operations: WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -VE, -Vw), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Reading flash... Transaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=0, SPOP=0, COP=3, DBC=63, SME=0, SCF=0 Running OPCODE 0x03 failed at address 0x003000 (payload length was 64). Read operation failed! FAILED. Restoring MMIO space at 0x7f15ba76c8a0 Restoring PCI config space for 00:1f:0 reg 0xdc --- Cheers, Paweł

1 0

ASUS RS120-E5/PA2 & Debug Info
by Geoffrey McRae 24 Apr '12

24 Apr '12

flashrom -V : http://paste.flashrom.org/view.php?id=1171 superio -deV: http://paste.flashrom.org/view.php?id=1172 flashrom -r : http://paste.flashrom.org/view.php?id=1173 Thanks in advance, - Geoff

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom April 2012