flashrom

flashrom@flashrom.org

3 participants
9188 discussions

Re: [flashrom] FAILED: NVIDIA MCP61
by Carl-Daniel Hailfinger 19 Jul '12

19 Jul '12

Hi Bill, glad to hear you could restore by writing the backup. Analysis follows. Am 18.07.2012 01:39 schrieb William Speirs: > $ flashrom -w M2N_0902.ROM > flashrom v0.9.5.2-r1517 on Linux > Calibrating delay loop... OK. > Found chipset "NVIDIA MCP61". Enabling flash write... OK. > Found Winbond flash chip "W39V040C" (512 kB, LPC) at physical address > 0xfff80000. A notoriously troublesome chip. It behaves in a weird way (IMHO not really JEDEC-compliant) with the JEDEC Toggle Bit algorithm (minimum 50 ms time between reads). You may be hitting that problem although we tried to add workarounds for it. > Reading old flash chip contents... done. > Erasing and writing flash chip... ERASE FAILED at 0x00000000! > Expected=0xff, Read=0x4f, failed byte count from 0x00000000-0x0000ffff: > 0x10000 > ERASE FAILED! This is actually not a failed erase, but a misdetected end-of-erase due to the JEDEC Toggle Bit weirdness. The erase succeeds eventually, roughly half a second after flashrom complains about erase failure. > Reading current flash chip contents... done. ERASE FAILED at 0x00010000! > Expected=0xff, Read=0xdf, failed byte count from 0x00000000-0x0007ffff: > 0x652aa > ERASE FAILED! This is actually a failed erase due to a flashrom bug in the chip definition. Whole-chip erase is not supported by this chip at all, and flashrom should not attempt to use that. The successful erase of the first 0x10000 bytes is the longterm (admittedly long-term means roughly one second here) effect of the first erase attempt. > FAILED! > Uh oh. Erase/write failed. Checking if anything changed. > Your flash chip is in an unknown state. > > > I tried a flashrom -r and compared it to the backup I made and it's > different. It is also different from the ROM I tried to install. > > Any thoughts? Yes. Please download latest flashrom from svn, edit file jedec.c function toggle_ready_jedec_slow() and replace toggle_ready_jedec_common(flash, dst, 8 * 1000); with toggle_ready_jedec_common(flash, dst, 100 * 1000); In theory, that change should work around the hardware bug you're hitting, but to be honest I expect more weirdness to show up instead. Still, it would be very helpful if you could test that. Do you have a way to recover (i.e. another board with a LPC flash chip in a socket)? I'm asking because I want to keep the risk low, and while the test above should be harmless in itself, more tests might be necessary later. Regards, Carl-Daniel -- http://www.hailfinger.org/

2 1

FT232H support (was: FAILED: MS-7302)
by Stefan Tauner 19 Jul '12

19 Jul '12

On Thu, 19 Jul 2012 04:19:32 +0200 Miloud Malagouen <miloud.malagouen(a)gmail.com> wrote: > I bricked a MSI MS-7302 motherboard with a bad coreboot image. I'm trying > to flash the bios with a C232HM-DDHSL-0 FTDI USB > cable<http://www.ftdichip.com/Products/Cables/USBMPSSE.htm>using the > MSI JSPI1 Header <http://www.coreboot.org/MSI_JSPI1> present on the board > for SPI connection. The FTDI cable uses a FT232H chip witch is capable of > providing a USB to SPI, I2C or JTAG interface. > > The FTDI D2XX Linux driver cited that the FT232H chip has type number 6 > (while the FT4232H has type 5), so i had to modify the file > */usr/include/ftdi.h* and change the ftdi_chip_type enumeration definition: > > /** FTDI chip type */ > enum ftdi_chip_type { TYPE_AM=0, TYPE_BM=1, TYPE_2232C=2, TYPE_R=3, > TYPE_2232H=4, TYPE_4232H=5,*TYPE_232H=6* }; there is probably a way around this, we will have to investigate that. > I had to add support to the FT232H chip (vid=0403 pid=6014) in the * > ft2232_spi* programmer of flashrom. I's very simple. Here is the patch of > file ft2232_spi.c: thanks for the patch, i'll review it in detail later. two things certainly need to be changed before this can enter our repository though: - man page needs to be updated - the patch has to be signed off, see http://www.coreboot.org/Development_Guidelines#Sign-off_Procedure > =======================BEGIN DIFF================================ > --- flashrom/ft2232_spi.c 2012-07-19 03:43:28.866724677 +0200 > +++ flashrom-0.9.5.2-r1547/ft2232_spi.c 2012-07-16 05:16:53.000000000 > +0200 > […] > =======================END DIFF================================== > > > The flash memory is probed correctly but erase an write operations failed. > Here is flashrom command (bold) and output: > ____________________________________________________________________________________ > > *flashrom -p ft2232_spi:type=232H,port=A -w A7302AMS.160* > flashrom v0.9.5.2-runknown on Linux 3.4.4-5.fc17.i686.PAE (i686) > flashrom is free software, get the source code at http://www.flashrom.org > > […] > > The chip is powered with an external PSU (3.3V orange cable of an ATX PSU). > I will try with a 1200F capacitor on the VCC link. I hope this is just > a magnetic noise issue. Are all pins connected correctly? especially the #WP pin could introduce the problem, but all others should be connected as specified in the datasheet too (e.g. hold pin if available). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] (no subject)
by Idwer Vollering 19 Jul '12

19 Jul '12

2012/7/19 Riccardo Berto <riccardobrt(a)gmail.com>: > > > ok lol > > thanks for the explanation > btw I think that with battery on it and connected to AC you can use a > laptop > safely (with battery you avoid instant shutdowns) No, the battery isn't there to prevent unexpected poweroffs. Read the following two wiki pages, there you'll find out more about why we strongly discourage running flashrom on laptops/mobile hardware. http://flashrom.org/Laptops http://flashrom.org/Laptop_enable

1 0

Re: [flashrom] (no subject)
by Stefan Tauner 19 Jul '12

19 Jul '12

On Thu, 19 Jul 2012 17:20:46 +0200 Riccardo Berto <riccardobrt(a)gmail.com> wrote: > ok lol > > thanks for the explanation > btw I think that with battery on it and connected to AC you can use a > laptop safely (with battery you avoid instant shutdowns) no that problem is not the supply of power (that is actually a plus for laptops compared to desktops without an UPS), but the internal workings of most laptops. they include a chip called embedded controller that runs its own software and controls things like the backlight of the display or charging the battery. the problem is that these chips are often near the flash chip logically and flashrom sometimes irritates them enough that they just shut down the whole machine. the main reason why this can happen is that they are not documented publicly at all, see also http://flashrom.org/Laptops -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] (no subject)
by Stefan Tauner 19 Jul '12

19 Jul '12

On Thu, 19 Jul 2012 16:52:43 +0200 Riccardo Berto <riccardobrt(a)gmail.com> wrote: > didn't understand to send only if it has succes. > > > sorry but i'm a noob in hardware questions, all the things i can tell you > is that I have this > pc<http://www.hackerscomputer.com/art/id15255/acer/acer-aspire-5740g-624g64mn-…> > (mb Mobile > Intel HM55 Express). thank you, that was what i was looking for. at first i presumed you were running flashrom on a desktop machine. flashrom tries to detect this (with dmidecode) but failed, hence my confusion. the reason it checks that at all is that running flashrom on laptops can be dangerous (e.g. instant shutdowns). it was not in your case but please refrain from running it on other laptops. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] (no subject)
by Stefan Tauner 19 Jul '12

19 Jul '12

On Thu, 19 Jul 2012 13:31:03 +0200 Riccardo Berto <riccardobrt(a)gmail.com> wrote: > in the output of the program, it says to send to this email the verbose > output if I have untested chip Hello and thanks for your report, actually the message requested you to send an email if one of READ, ERASE or WRITE worked, but that was apparently not the case, and probing was already marked as working on that chip. But there is something else in your log that is interesting to us: the locked ME region. Which mainboard model is that? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

(no subject)
by Riccardo Berto 19 Jul '12

19 Jul '12

> > in the output of the program, it says to send to this email the verbose > output if I have untested chip So here you are *flashrom v0.9.5.2-r1515 on Linux 3.4.5-1-ARCH (x86_64), built with libpci 3.1.9, GCC 4.6.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, 1555M loops per second, 10 myus = 9 us, 100 myus = 104 us, 1000 myus = 969 us, 10000 myus = 9748 us, 4 myus = 4 us, OK.* *Initializing internal programmer* *No coreboot table found.* *sh: dmidecode: command not found* *dmidecode execution unsuccessful - continuing without DMI info* *Found chipset "Intel HM55" with PCI ID 8086:3b09. * *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: 0x0* *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: 0x400000 bytes* *BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0* *Root Complex Register Block address = 0xfed1c000* *GCS = 0xc60: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x3 (SPI)* *Top Swap : not enabled* *SPIBAR = 0xfed1c000 + 0x3800* *0x04: 0x6008 (HSFS)* *HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 * *Programming OPCODES... * *program_opcodes: preop=5006 optype=463b opmenu=05d80302c79f0190* *done* *0x06: 0x3f04 (HSFC)* *HSFC: FGO=0, FCYCLE=2, FDBC=63, 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: 0x03ff0180 FREG1: BIOS region (0x00180000-0x003fffff) is read-write.* *0x5C: 0x017f0001 FREG2: WARNING: Management Engine region (0x00001000-0x0017ffff) is locked.* *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: 0x04 (SSFS)* *SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0* *0x91: 0xf84140 (SSFC)* *SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=1, SME=0, SCF=0* *0x94: 0x5006 (PREOP)* *0x96: 0x463b (OPTYPE)* *0x98: 0x05d80302 (OPMENU)* *0x9C: 0xc79f0190 (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 disabled, caching enabled, OK.* *The following protocols are supported: FWH, SPI.* *Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for SST SST25LF040A, 512 kB: * *program_opcodes: preop=5006 optype=462b opmenu=05ab0302c79f0190* *on-the-fly OPCODE (0xAB) re-programmed, op-pos=2* *probe_spi_res2: id1 0x15, id2 0x15* *Probing for SST SST25LF080A, 1024 kB: probe_spi_res2: id1 0x15, id2 0x15* *Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xef, id2 0x15* *Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xef, id2 0x15* *Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xef, id2 0x15* *Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID.* *Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID.* *Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016 * *Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016 * *Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID.* *Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Chip status register is 00* *Found Winbond flash chip "W25X32" (4096 kB, SPI) at physical address 0xffc00000.* *Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Unknown SFDP-capable chip, 0 kB: * *program_opcodes: preop=5006 optype=462b opmenu=055a0302c79f0190* *on-the-fly OPCODE (0x5A) re-programmed, op-pos=2* *No SFDP signature found.* *Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x3016* *Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x15* *Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x0f, id2 0xb6, id1 parity violation, id1 is normal flash content, id2 is normal flash content* *Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x0f, id2 0xb6, id1 parity violation, id1 is normal flash content, id2 is normal flash content* *Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x0f, id2 0xb6, 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 0x05, id1 parity violation, id1 is normal flash content, id2 is normal flash content* *Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x0f, id2 0xb6, id1 parity violation, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x0f, id2 0xb6, id1 parity violation, id1 is normal flash content, id2 is normal flash content* *Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xab, id2 0x3d, id1 is normal flash content, id2 is normal flash content* *Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x89, id2 0x6e, id1 is normal flash content, id2 is normal flash content* *Found Winbond flash chip "W25X32" (4096 kB, SPI).* *===* *This flash part has status UNTESTED for operations: READ ERASE 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!* *No operations were specified.* *Restoring MMIO space at 0x7f34ce9b58a0* *Restoring MMIO space at 0x7f34ce9b589c* *Restoring MMIO space at 0x7f34ce9b5898* *Restoring MMIO space at 0x7f34ce9b5896* *Restoring MMIO space at 0x7f34ce9b5894* *Restoring PCI config space for 00:1f:0 reg 0xdc*

1 0

FAILED: MS-7302
by Miloud Malagouen 18 Jul '12

18 Jul '12

Dear Sir, I bricked a MSI MS-7302 motherboard with a bad coreboot image. I'm trying to flash the bios with a C232HM-DDHSL-0 FTDI USB cable<http://www.ftdichip.com/Products/Cables/USBMPSSE.htm>using the MSI JSPI1 Header <http://www.coreboot.org/MSI_JSPI1> present on the board for SPI connection. The FTDI cable uses a FT232H chip witch is capable of providing a USB to SPI, I2C or JTAG interface. The FTDI D2XX Linux driver cited that the FT232H chip has type number 6 (while the FT4232H has type 5), so i had to modify the file */usr/include/ftdi.h* and change the ftdi_chip_type enumeration definition: /** FTDI chip type */ enum ftdi_chip_type { TYPE_AM=0, TYPE_BM=1, TYPE_2232C=2, TYPE_R=3, TYPE_2232H=4, TYPE_4232H=5,*TYPE_232H=6* }; I had to add support to the FT232H chip (vid=0403 pid=6014) in the * ft2232_spi* programmer of flashrom. I's very simple. Here is the patch of file ft2232_spi.c: =======================BEGIN DIFF================================ --- flashrom/ft2232_spi.c 2012-07-19 03:43:28.866724677 +0200 +++ flashrom-0.9.5.2-r1547/ft2232_spi.c 2012-07-16 05:16:53.000000000 +0200 @@ -34,6 +34,7 @@ #define FTDI_VID 0x0403 #define FTDI_FT2232H_PID 0x6010 #define FTDI_FT4232H_PID 0x6011 +#define FTDI_FT232H_PID 0x6014 #define TIAO_TUMPA_PID 0x8a98 #define AMONTEC_JTAGKEY_PID 0xCFF8 @@ -52,6 +53,7 @@ const struct usbdev_status devs_ft2232spi[] = { {FTDI_VID, FTDI_FT2232H_PID, OK, "FTDI", "FT2232H"}, {FTDI_VID, FTDI_FT4232H_PID, OK, "FTDI", "FT4232H"}, + {FTDI_VID, FTDI_FT232H_PID, NT, "FTDI", "FT232H"}, {FTDI_VID, TIAO_TUMPA_PID, OK, "TIAO", "USB Multi-Protocol Adapter"}, {FTDI_VID, AMONTEC_JTAGKEY_PID, OK, "Amontec", "JTAGkey"}, {GOEPEL_VID, GOEPEL_PICOTAP_PID, OK, "GOEPEL", "PicoTAP"}, @@ -185,6 +187,8 @@ int ft2232_spi_init(void) ft2232_type = FTDI_FT2232H_PID; else if (!strcasecmp(arg, "4232H")) ft2232_type = FTDI_FT4232H_PID; + else if (!strcasecmp(arg, "232H")) + ft2232_type = FTDI_FT232H_PID; else if (!strcasecmp(arg, "jtagkey")) { ft2232_type = AMONTEC_JTAGKEY_PID; ft2232_interface = INTERFACE_A; @@ -285,7 +289,7 @@ int ft2232_spi_init(void) return -4; } - if (ftdic->type != TYPE_2232H && ftdic->type != TYPE_4232H) { + if (ftdic->type != TYPE_2232H && ftdic->type != TYPE_4232H && ftdic->type != TYPE_232H) { msg_pdbg("FTDI chip type %d is not high-speed\n", ftdic->type); clock_5x = 0; =======================END DIFF================================== The flash memory is probed correctly but erase an write operations failed. Here is flashrom command (bold) and output: ____________________________________________________________________________________ *flashrom -p ft2232_spi:type=232H,port=A -w A7302AMS.160* flashrom v0.9.5.2-runknown on Linux 3.4.4-5.fc17.i686.PAE (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25X80" (1024 kB, SPI) on ft2232_spi. Reading old flash chip contents... done. Erasing and writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x00, failed byte count from 0x00000000-0x00000fff: 0x10 ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x00, failed byte count from 0x00000000-0x0000ffff: 0x100 ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x00, failed byte count from 0x00000000-0x000fffff: 0xffc ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! ____________________________________________________________________________________ The chip is powered with an external PSU (3.3V orange cable of an ATX PSU). I will try with a 1200F capacitor on the VCC link. I hope this is just a magnetic noise issue. Thank you.

1 0

Re: [flashrom] FAILED: NVIDIA MCP61
by Stefan Tauner 18 Jul '12

18 Jul '12

On Wed, 18 Jul 2012 17:12:14 -0400 William Speirs <wspeirs(a)apache.org> wrote: > So if restoring the backup ROM worked am I safe to power cycle my machine? yes > Any ideas on what would be wrong with that ROM? not yet. but it is not related to the image itself pretty sure (there is a theoretical chance that there is a bad bit, that is in the right state in the old image but not in the new image, but that is quite unlikely). more likely is that there is some (partial) copy protection in place... -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] FAILED: NVIDIA MCP61
by William Speirs 18 Jul '12

18 Jul '12

So if restoring the backup ROM worked am I safe to power cycle my machine? Any ideas on what would be wrong with that ROM? Thanks... Bill- On Jul 17, 2012 8:49 PM, "William Speirs" <wspeirs(a)apache.org> wrote: > I was able to write the backup and run verify and it worked. I still > haven't and won't restart my machine. > > After restoring the backup, I tried again with the new BIOS and got the > same error/issue. I was able to backup yet again without issue. > > So I'm guessing it's more of a problem with the ROM image than the program > writing the ROM. I've attached the ROM to see if that provides any insight. > > Thanks again for the help! > > Bill- > > On Tue, Jul 17, 2012 at 8:22 PM, William Speirs <wspeirs(a)apache.org>wrote: > >> I will try writing the backup and certainly leave the machine on. >> >> Thanks, and get some sleep ;-) >> >> Bill- >> On Jul 17, 2012 8:20 PM, "Stefan Tauner" < >> stefan.tauner(a)student.tuwien.ac.at> wrote: >> >>> On Tue, 17 Jul 2012 19:39:31 -0400 >>> William Speirs <wspeirs(a)apache.org> wrote: >>> >>> > I tried a flashrom -r and compared it to the backup I made and it's >>> > different. It is also different from the ROM I tried to install. >>> > >>> > Any thoughts? >>> >>> Most importantly: dont reboot or shutdown that computer. (we really >>> mean it... but some users do it anyway, and brick their boards that >>> way) >>> >>> i would try writing the backup image again to get to a safe state >>> again. the reason why it failed in the first place is not obvious to >>> me, but it is 2:00 AM here, so i might be overlooking something. >>> -- >>> Kind regards/Mit freundlichen Grüßen, Stefan Tauner >>> >> >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom