- flashrom - mail.coreboot.org

Re: [flashrom] Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by Stefan Tauner 10 Dec '12

10 Dec '12

On Mon, 10 Dec 2012 14:35:54 -0500 sdbarnes(a)rockwellcollins.com wrote: > I think I have verified that there is no issue with flashrom 0.9.3 and the > PMC Pm49FL004 chip. > > I had received some Pm49FL004 chips from a vendor with a WinMate I330 BIOS > load (an I330 message was being displayed briefly on BIOS POST). Am I > correct in assuming that some portion of the BIOS (e.g.,boot block) cannot > be updated with flashrom? that depends on how the boot block (or any other range) is protected, there are various schemes to do this. the most common one is to use a dedicated write protection pin for the whole device or the boot block (or both), which can be changed by a GPIO of the southbridge or super i/o chip (flashrom supports a huge number of mainboards that need this, but each had to be added manually). but there are also some flash chips that can be locked by software which is done by the BIOS before the OS even loads (and there are various other schemes involving the chipset). the log you provided indicated that *if at all* there were only bits changed from 0 to 1 (by erasing whole blocks). this may have been because you rerun flashrom to obtain the log and the actual changes were done in an earlier run. flashrom would then skip every block that is already equal... > I never saw a checksum error after rebooting my > motherboard and I know that my BIOS defaults had been updated from the > factory defaults. > > I have since received some more Pm49FL004 chips from the same vendor with > a WinMate I370 BIOS load and flashing these chips with a different I370 > image works with flashrom-0.9.3 without any issues. this would OTOH indicate that there is no (hardware) write protection in place... i so am a bit puzzled ATM about what's the real issue (if there is any) and what happened exactly. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by Stefan Tauner 10 Dec '12

10 Dec '12

On Mon, 10 Dec 2012 10:44:01 -0500 sdbarnes(a)rockwellcollins.com wrote: > Despite the verification failure, the motherboard appears to function > properly with the new flash image that is written. Below is the flashrom > verbose output: > > > > flashrom v0.9.3-r1250 on Linux 2.6.32.59 (i686), built with libpci 3.1.7, > … > Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address > 0xfff80000. > … > Erasing and writing flash chip... Looking at blockwise erase function 0... > trying... 0x000000-0x000fff:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S, > 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, > 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, > 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, > 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, > 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:S, > 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, > 0x015000-0x015fff:S, 0x016000-0x016fff:S, 0x017000-0x017fff:S, > 0x018000-0x018fff:S, 0x019000-0x019fff:S, 0x01a000-0x01afff:S, > 0x01b000-0x01bfff:S, 0x01c000-0x01cfff:S, 0x01d000-0x01dfff:S, > 0x01e000-0x01efff:S, 0x01f000-0x01ffff:S, 0x020000-0x020fff:S, > 0x021000-0x021fff:S, 0x022000-0x022fff:S, 0x023000-0x023fff:S, > 0x024000-0x024fff:S, 0x025000-0x025fff:S, 0x026000-0x026fff:S, > 0x027000-0x027fff:S, 0x028000-0x028fff:S, 0x029000-0x029fff:S, > 0x02a000-0x02afff:S, 0x02b000-0x02bfff:S, 0x02c000-0x02cfff:S, > 0x02d000-0x02dfff:S, 0x02e000-0x02efff:S, 0x02f000-0x02ffff:S, > 0x030000-0x030fff:S, 0x031000-0x031fff:S, 0x032000-0x032fff:S, > 0x033000-0x033fff:S, 0x034000-0x034fff:S, 0x035000-0x035fff:S, > 0x036000-0x036fff:S, 0x037000-0x037fff:S, 0x038000-0x038fff:S, > 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, > 0x03c000-0x03cfff:S, 0x03d000-0x03dfff:S, 0x03e000-0x03efff:S, > 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, > 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, > 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, > 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, > 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, > 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, > 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, > 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, > 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, > 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, > 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, > 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, > 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, > 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, > 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, > 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, > 0x06f000-0x06ffff:S, 0x070000-0x070fff:EERASE FAILED at 0x00070002! > Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x00070fff: > 0xf70 > ERASE FAILED! > > > Looking at blockwise erase function 1... trying... 0x000000-0x00ffff:S, > 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, > 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, > 0x070000-0x07ffff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, > failed byte count from 0x00070000-0x0007ffff: 0xfd35 > ERASE FAILED! > > > Looking at blockwise erase function 2... trying... > 0x000000-0x07ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, > failed byte count from 0x00000000-0x0007ffff: 0x53f0b > ERASE FAILED! > > > Looking at blockwise erase function 3... not defined. trying... > > Done. > Verifying flash... VERIFY FAILED at 0x0007010b! Expected=0x7c, Read=0x70, > failed byte count from 0x00000000-0x0007ffff: 0x9f2 > 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! > Restoring PCI config space for 00:1f:0 reg 0xdc i am not entirely sure, but i think 0.9.3 can not distinguish between an unknown state and the old, safe state the flash was before flashrom tried to erase. in your case it would be possible then that the whole flash chip is write protected and nothing changed/was deleted at all, which would explain the bootable condition of the system (i.e. you were lucky). if that is true we will need to add a small routine that disables the write protection on that mainboard (if there is no jumper oder bios option to do so). please send us the output of 'lspci -nn', 'lspci -nnvvvxxx', 'superiotool -deV' (run all commands as root), thanks. if not too much of a hassle you should also upgrade flashrom before further attempts. JFYI: your first message was stuck in the moderation queue because it was sent before you subscribed. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by sdbarnes＠rockwellcollins.com 10 Dec '12

10 Dec '12

Despite the verification failure, the motherboard appears to function properly with the new flash image that is written. Below is the flashrom verbose output: flashrom v0.9.3-r1250 on Linux 2.6.32.59 (i686), built with libpci 3.1.7, GCC 4.3.4, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 1344M loops per second, 10 myus = 12 us, 100 myus = 109 us, 1000 myus = 1088 us, 10000 myus = 9464 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: " " DMI string system-product-name: " " DMI string system-version: " " DMI string baseboard-manufacturer: " " DMI string baseboard-product-name: "945GM" DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found chipset "Intel ICH7M", enabling flash write... chipset PCI ID is 8086:27b9, 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled OK. This chipset supports the following protocols: FWH. 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: skipped. Probing for AMIC A25L05PU, 64 KB: skipped. Probing for AMIC A25L10PT, 128 KB: skipped. Probing for AMIC A25L10PU, 128 KB: skipped. Probing for AMIC A25L20PT, 256 KB: skipped. Probing for AMIC A25L20PU, 256 KB: skipped. Probing for AMIC A25L40PT, 512 KB: skipped. Probing for AMIC A25L40PU, 512 KB: skipped. Probing for AMIC A25L80P, 1024 KB: skipped. Probing for AMIC A25L16PT, 2048 KB: skipped. Probing for AMIC A25L16PU, 2048 KB: skipped. Probing for AMIC A25L512, 64 KB: skipped. Probing for AMIC A25L010, 128 KB: skipped. Probing for AMIC A25L020, 256 KB: skipped. Probing for AMIC A25L040, 512 KB: skipped. Probing for AMIC A25L080, 1024 KB: skipped. Probing for AMIC A25L016, 2048 KB: skipped. Probing for AMIC A25L032, 4096 KB: skipped. Probing for AMIC A25LQ032, 4096 KB: skipped. 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: skipped. Probing for Atmel AT25DF021, 256 KB: skipped. Probing for Atmel AT25DF041A, 512 KB: skipped. Probing for Atmel AT25DF081, 1024 KB: skipped. Probing for Atmel AT25DF081A, 1024 KB: skipped. Probing for Atmel AT25DF161, 2048 KB: skipped. Probing for Atmel AT25DF321, 4096 KB: skipped. Probing for Atmel AT25DF321A, 4096 KB: skipped. Probing for Atmel AT25DF641, 8192 KB: skipped. Probing for Atmel AT25DQ161, 2048 KB: skipped. Probing for Atmel AT25F512B, 64 KB: skipped. Probing for Atmel AT25FS010, 128 KB: skipped. Probing for Atmel AT25FS040, 512 KB: skipped. Probing for Atmel AT26DF041, 512 KB: skipped. Probing for Atmel AT26DF081A, 1024 KB: skipped. Probing for Atmel AT26DF161, 2048 KB: skipped. Probing for Atmel AT26DF161A, 2048 KB: skipped. Probing for Atmel AT26F004, 512 KB: skipped. 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: skipped. Probing for Atmel AT45DB011D, 128 KB: skipped. Probing for Atmel AT45DB021D, 256 KB: skipped. Probing for Atmel AT45DB041D, 512 KB: skipped. Probing for Atmel AT45DB081D, 1024 KB: skipped. Probing for Atmel AT45DB161D, 2048 KB: skipped. Probing for Atmel AT45DB321C, 4224 KB: skipped. Probing for Atmel AT45DB321D, 4096 KB: skipped. Probing for Atmel AT45DB642D, 8192 KB: skipped. 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 Bright BM29F040, 512 KB: skipped. Probing for EMST F49B002UA, 256 KB: skipped. Probing for EMST F25L008A, 1024 KB: skipped. Probing for Eon EN25B05, 64 KB: skipped. Probing for Eon EN25B05T, 64 KB: skipped. Probing for Eon EN25B10, 128 KB: skipped. Probing for Eon EN25B10T, 128 KB: skipped. Probing for Eon EN25B20, 256 KB: skipped. Probing for Eon EN25B20T, 256 KB: skipped. Probing for Eon EN25B40, 512 KB: skipped. Probing for Eon EN25B40T, 512 KB: skipped. Probing for Eon EN25B80, 1024 KB: skipped. Probing for Eon EN25B80T, 1024 KB: skipped. Probing for Eon EN25B16, 2048 KB: skipped. Probing for Eon EN25B16T, 2048 KB: skipped. Probing for Eon EN25B32, 4096 KB: skipped. Probing for Eon EN25B32T, 4096 KB: skipped. Probing for Eon EN25B64, 8192 KB: skipped. Probing for Eon EN25B64T, 8192 KB: skipped. Probing for Eon EN25D16, 2048 KB: skipped. Probing for Eon EN25F05, 64 KB: skipped. Probing for Eon EN25F10, 128 KB: skipped. Probing for Eon EN25F20, 256 KB: skipped. Probing for Eon EN25F40, 512 KB: skipped. Probing for Eon EN25F80, 1024 KB: skipped. Probing for Eon EN25F16, 2048 KB: skipped. Probing for Eon EN25F32, 4096 KB: skipped. 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 Hyundai HY29F040A, 512 KB: skipped. Probing for Intel 28F001BN/BX-B, 128 KB: skipped. Probing for Intel 28F001BN/BX-T, 128 KB: skipped. Probing for Intel 28F002BC/BL/BV/BX-T, 256 KB: skipped. Probing for Intel 28F008S3/S5/SC, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-B, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-T, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-B, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-T, 512 KB: skipped. Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX25L512, 64 KB: skipped. Probing for Macronix MX25L1005, 128 KB: skipped. Probing for Macronix MX25L2005, 256 KB: skipped. Probing for Macronix MX25L4005, 512 KB: skipped. Probing for Macronix MX25L8005, 1024 KB: skipped. Probing for Macronix MX25L1605, 2048 KB: skipped. Probing for Macronix MX25L1635D, 2048 KB: skipped. Probing for Macronix MX25L1635E, 2048 KB: skipped. Probing for Macronix MX25L3205, 4096 KB: skipped. Probing for Macronix MX25L3235D, 4096 KB: skipped. Probing for Macronix MX25L6405, 8192 KB: skipped. Probing for Macronix MX25L12805, 16384 KB: skipped. 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 MX29F040, 512 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: skipped. Probing for Numonyx M25PE20, 256 KB: skipped. Probing for Numonyx M25PE40, 512 KB: skipped. Probing for Numonyx M25PE80, 1024 KB: skipped. Probing for Numonyx M25PE16, 2048 KB: skipped. Probing for PMC Pm25LV010, 128 KB: skipped. Probing for PMC Pm25LV016B, 2048 KB: skipped. Probing for PMC Pm25LV020, 256 KB: skipped. Probing for PMC Pm25LV040, 512 KB: skipped. Probing for PMC Pm25LV080B, 1024 KB: skipped. Probing for PMC Pm25LV512, 64 KB: skipped. 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 0x9d, id2 0x6e Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000. Probing for Sanyo LF25FW203A, 2048 KB: skipped. Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Spansion S25FL004A, 512 KB: skipped. Probing for Spansion S25FL008A, 1024 KB: skipped. Probing for Spansion S25FL016A, 2048 KB: skipped. Probing for Spansion S25FL032A, 4096 KB: skipped. Probing for Spansion S25FL064A, 8192 KB: skipped. Probing for SST SST25VF010.REMS, 128 KB: skipped. Probing for SST SST25VF016B, 2048 KB: skipped. Probing for SST SST25VF032B, 4096 KB: skipped. Probing for SST SST25VF064C, 8192 KB: skipped. Probing for SST SST25VF040.REMS, 512 KB: skipped. Probing for SST SST25VF040B, 512 KB: skipped. Probing for SST SST25LF040A.RES, 512 KB: skipped. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Probing for SST SST25VF080B, 1024 KB: skipped. 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: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 KB: skipped. Probing for SST SST49LF020A, 256 KB: skipped. Probing for SST SST49LF040, 512 KB: skipped. Probing for SST SST49LF040B, 512 KB: skipped. Probing for SST SST49LF080A, 1024 KB: skipped. Probing for SST SST49LF160C, 2048 KB: skipped. Probing for ST M25P05-A, 64 KB: skipped. Probing for ST M25P05.RES, 64 KB: skipped. Probing for ST M25P10-A, 128 KB: skipped. Probing for ST M25P10.RES, 128 KB: skipped. Probing for ST M25P20, 256 KB: skipped. Probing for ST M25P40, 512 KB: skipped. Probing for ST M25P40-old, 512 KB: skipped. Probing for ST M25P80, 1024 KB: skipped. Probing for ST M25P16, 2048 KB: skipped. Probing for ST M25P32, 4096 KB: skipped. Probing for ST M25P64, 8192 KB: skipped. Probing for ST M25P128, 16384 KB: skipped. Probing for ST M25PX32, 4096 KB: skipped. Probing for ST M25PX64, 8192 KB: skipped. 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 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0x09, id2 0xd5, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 KB: skipped. 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: skipped. Probing for Winbond W25Q16, 2048 KB: skipped. Probing for Winbond W25Q32, 4096 KB: skipped. Probing for Winbond W25Q64, 8192 KB: skipped. Probing for Winbond W25x10, 128 KB: skipped. Probing for Winbond W25x20, 256 KB: skipped. Probing for Winbond W25x40, 512 KB: skipped. Probing for Winbond W25x80, 1024 KB: skipped. Probing for Winbond W25x16, 2048 KB: skipped. Probing for Winbond W25x32, 4096 KB: skipped. Probing for Winbond W25x64, 8192 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W29C020(C)/W29C022, 256 KB: skipped. Probing for Winbond W29C040/P, 512 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W39V040A, 512 KB: skipped. Probing for Winbond W39V040B, 512 KB: skipped. Probing for Winbond W39V040C, 512 KB: skipped. Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FB, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FC, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080A, 1024 KB: skipped. Probing for Winbond W49F002U/N, 256 KB: skipped. Probing for Winbond W49F020, 256 KB: skipped. Probing for Winbond W49V002A, 256 KB: skipped. Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA (dual mode), 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for AMIC unknown AMIC SPI chip, 0 KB: skipped. Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Probing for Eon unknown Eon SPI chip, 0 KB: skipped. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Probing for SST unknown SST SPI chip, 0 KB: skipped. Probing for ST unknown ST SPI chip, 0 KB: skipped. Probing for Sanyo unknown Sanyo SPI chip, 0 KB: skipped. Probing for Generic unknown SPI chip (RDID), 0 KB: skipped. Probing for Generic unknown SPI chip (REMS), 0 KB: skipped. === 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, -Vw, -VE), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling checks. Reading old flash chip contents... Erasing and writing flash chip... Looking at blockwise erase function 0... trying... 0x000000-0x000fff:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S, 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:S, 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, 0x015000-0x015fff:S, 0x016000-0x016fff:S, 0x017000-0x017fff:S, 0x018000-0x018fff:S, 0x019000-0x019fff:S, 0x01a000-0x01afff:S, 0x01b000-0x01bfff:S, 0x01c000-0x01cfff:S, 0x01d000-0x01dfff:S, 0x01e000-0x01efff:S, 0x01f000-0x01ffff:S, 0x020000-0x020fff:S, 0x021000-0x021fff:S, 0x022000-0x022fff:S, 0x023000-0x023fff:S, 0x024000-0x024fff:S, 0x025000-0x025fff:S, 0x026000-0x026fff:S, 0x027000-0x027fff:S, 0x028000-0x028fff:S, 0x029000-0x029fff:S, 0x02a000-0x02afff:S, 0x02b000-0x02bfff:S, 0x02c000-0x02cfff:S, 0x02d000-0x02dfff:S, 0x02e000-0x02efff:S, 0x02f000-0x02ffff:S, 0x030000-0x030fff:S, 0x031000-0x031fff:S, 0x032000-0x032fff:S, 0x033000-0x033fff:S, 0x034000-0x034fff:S, 0x035000-0x035fff:S, 0x036000-0x036fff:S, 0x037000-0x037fff:S, 0x038000-0x038fff:S, 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, 0x03c000-0x03cfff:S, 0x03d000-0x03dfff:S, 0x03e000-0x03efff:S, 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, 0x06f000-0x06ffff:S, 0x070000-0x070fff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x00070fff: 0xf70 ERASE FAILED! Looking at blockwise erase function 1... trying... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x0007ffff: 0xfd35 ERASE FAILED! Looking at blockwise erase function 2... trying... 0x000000-0x07ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x53f0b ERASE FAILED! Looking at blockwise erase function 3... not defined. trying... Done. Verifying flash... VERIFY FAILED at 0x0007010b! Expected=0x7c, Read=0x70, failed byte count from 0x00000000-0x0007ffff: 0x9f2 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! Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by sdbarnes＠rockwellcollins.com 10 Dec '12

10 Dec '12

Despite the verification failure, the motherboard appears to function properly with the new flash image that is written. Below is the flashrom verbose output: flashrom v0.9.3-r1250 on Linux 2.6.32.59 (i686), built with libpci 3.1.7, GCC 4.3.4, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 1344M loops per second, 10 myus = 12 us, 100 myus = 109 us, 1000 myus = 1088 us, 10000 myus = 9464 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: " " DMI string system-product-name: " " DMI string system-version: " " DMI string baseboard-manufacturer: " " DMI string baseboard-product-name: "945GM" DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found chipset "Intel ICH7M", enabling flash write... chipset PCI ID is 8086:27b9, 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled OK. This chipset supports the following protocols: FWH. 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: skipped. Probing for AMIC A25L05PU, 64 KB: skipped. Probing for AMIC A25L10PT, 128 KB: skipped. Probing for AMIC A25L10PU, 128 KB: skipped. Probing for AMIC A25L20PT, 256 KB: skipped. Probing for AMIC A25L20PU, 256 KB: skipped. Probing for AMIC A25L40PT, 512 KB: skipped. Probing for AMIC A25L40PU, 512 KB: skipped. Probing for AMIC A25L80P, 1024 KB: skipped. Probing for AMIC A25L16PT, 2048 KB: skipped. Probing for AMIC A25L16PU, 2048 KB: skipped. Probing for AMIC A25L512, 64 KB: skipped. Probing for AMIC A25L010, 128 KB: skipped. Probing for AMIC A25L020, 256 KB: skipped. Probing for AMIC A25L040, 512 KB: skipped. Probing for AMIC A25L080, 1024 KB: skipped. Probing for AMIC A25L016, 2048 KB: skipped. Probing for AMIC A25L032, 4096 KB: skipped. Probing for AMIC A25LQ032, 4096 KB: skipped. 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: skipped. Probing for Atmel AT25DF021, 256 KB: skipped. Probing for Atmel AT25DF041A, 512 KB: skipped. Probing for Atmel AT25DF081, 1024 KB: skipped. Probing for Atmel AT25DF081A, 1024 KB: skipped. Probing for Atmel AT25DF161, 2048 KB: skipped. Probing for Atmel AT25DF321, 4096 KB: skipped. Probing for Atmel AT25DF321A, 4096 KB: skipped. Probing for Atmel AT25DF641, 8192 KB: skipped. Probing for Atmel AT25DQ161, 2048 KB: skipped. Probing for Atmel AT25F512B, 64 KB: skipped. Probing for Atmel AT25FS010, 128 KB: skipped. Probing for Atmel AT25FS040, 512 KB: skipped. Probing for Atmel AT26DF041, 512 KB: skipped. Probing for Atmel AT26DF081A, 1024 KB: skipped. Probing for Atmel AT26DF161, 2048 KB: skipped. Probing for Atmel AT26DF161A, 2048 KB: skipped. Probing for Atmel AT26F004, 512 KB: skipped. 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: skipped. Probing for Atmel AT45DB011D, 128 KB: skipped. Probing for Atmel AT45DB021D, 256 KB: skipped. Probing for Atmel AT45DB041D, 512 KB: skipped. Probing for Atmel AT45DB081D, 1024 KB: skipped. Probing for Atmel AT45DB161D, 2048 KB: skipped. Probing for Atmel AT45DB321C, 4224 KB: skipped. Probing for Atmel AT45DB321D, 4096 KB: skipped. Probing for Atmel AT45DB642D, 8192 KB: skipped. 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 Bright BM29F040, 512 KB: skipped. Probing for EMST F49B002UA, 256 KB: skipped. Probing for EMST F25L008A, 1024 KB: skipped. Probing for Eon EN25B05, 64 KB: skipped. Probing for Eon EN25B05T, 64 KB: skipped. Probing for Eon EN25B10, 128 KB: skipped. Probing for Eon EN25B10T, 128 KB: skipped. Probing for Eon EN25B20, 256 KB: skipped. Probing for Eon EN25B20T, 256 KB: skipped. Probing for Eon EN25B40, 512 KB: skipped. Probing for Eon EN25B40T, 512 KB: skipped. Probing for Eon EN25B80, 1024 KB: skipped. Probing for Eon EN25B80T, 1024 KB: skipped. Probing for Eon EN25B16, 2048 KB: skipped. Probing for Eon EN25B16T, 2048 KB: skipped. Probing for Eon EN25B32, 4096 KB: skipped. Probing for Eon EN25B32T, 4096 KB: skipped. Probing for Eon EN25B64, 8192 KB: skipped. Probing for Eon EN25B64T, 8192 KB: skipped. Probing for Eon EN25D16, 2048 KB: skipped. Probing for Eon EN25F05, 64 KB: skipped. Probing for Eon EN25F10, 128 KB: skipped. Probing for Eon EN25F20, 256 KB: skipped. Probing for Eon EN25F40, 512 KB: skipped. Probing for Eon EN25F80, 1024 KB: skipped. Probing for Eon EN25F16, 2048 KB: skipped. Probing for Eon EN25F32, 4096 KB: skipped. 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 Hyundai HY29F040A, 512 KB: skipped. Probing for Intel 28F001BN/BX-B, 128 KB: skipped. Probing for Intel 28F001BN/BX-T, 128 KB: skipped. Probing for Intel 28F002BC/BL/BV/BX-T, 256 KB: skipped. Probing for Intel 28F008S3/S5/SC, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-B, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-T, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-B, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-T, 512 KB: skipped. Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX25L512, 64 KB: skipped. Probing for Macronix MX25L1005, 128 KB: skipped. Probing for Macronix MX25L2005, 256 KB: skipped. Probing for Macronix MX25L4005, 512 KB: skipped. Probing for Macronix MX25L8005, 1024 KB: skipped. Probing for Macronix MX25L1605, 2048 KB: skipped. Probing for Macronix MX25L1635D, 2048 KB: skipped. Probing for Macronix MX25L1635E, 2048 KB: skipped. Probing for Macronix MX25L3205, 4096 KB: skipped. Probing for Macronix MX25L3235D, 4096 KB: skipped. Probing for Macronix MX25L6405, 8192 KB: skipped. Probing for Macronix MX25L12805, 16384 KB: skipped. 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 MX29F040, 512 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: skipped. Probing for Numonyx M25PE20, 256 KB: skipped. Probing for Numonyx M25PE40, 512 KB: skipped. Probing for Numonyx M25PE80, 1024 KB: skipped. Probing for Numonyx M25PE16, 2048 KB: skipped. Probing for PMC Pm25LV010, 128 KB: skipped. Probing for PMC Pm25LV016B, 2048 KB: skipped. Probing for PMC Pm25LV020, 256 KB: skipped. Probing for PMC Pm25LV040, 512 KB: skipped. Probing for PMC Pm25LV080B, 1024 KB: skipped. Probing for PMC Pm25LV512, 64 KB: skipped. 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 0x9d, id2 0x6e Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000. Probing for Sanyo LF25FW203A, 2048 KB: skipped. Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Spansion S25FL004A, 512 KB: skipped. Probing for Spansion S25FL008A, 1024 KB: skipped. Probing for Spansion S25FL016A, 2048 KB: skipped. Probing for Spansion S25FL032A, 4096 KB: skipped. Probing for Spansion S25FL064A, 8192 KB: skipped. Probing for SST SST25VF010.REMS, 128 KB: skipped. Probing for SST SST25VF016B, 2048 KB: skipped. Probing for SST SST25VF032B, 4096 KB: skipped. Probing for SST SST25VF064C, 8192 KB: skipped. Probing for SST SST25VF040.REMS, 512 KB: skipped. Probing for SST SST25VF040B, 512 KB: skipped. Probing for SST SST25LF040A.RES, 512 KB: skipped. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Probing for SST SST25VF080B, 1024 KB: skipped. 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: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 KB: skipped. Probing for SST SST49LF020A, 256 KB: skipped. Probing for SST SST49LF040, 512 KB: skipped. Probing for SST SST49LF040B, 512 KB: skipped. Probing for SST SST49LF080A, 1024 KB: skipped. Probing for SST SST49LF160C, 2048 KB: skipped. Probing for ST M25P05-A, 64 KB: skipped. Probing for ST M25P05.RES, 64 KB: skipped. Probing for ST M25P10-A, 128 KB: skipped. Probing for ST M25P10.RES, 128 KB: skipped. Probing for ST M25P20, 256 KB: skipped. Probing for ST M25P40, 512 KB: skipped. Probing for ST M25P40-old, 512 KB: skipped. Probing for ST M25P80, 1024 KB: skipped. Probing for ST M25P16, 2048 KB: skipped. Probing for ST M25P32, 4096 KB: skipped. Probing for ST M25P64, 8192 KB: skipped. Probing for ST M25P128, 16384 KB: skipped. Probing for ST M25PX32, 4096 KB: skipped. Probing for ST M25PX64, 8192 KB: skipped. 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 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0x09, id2 0xd5, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 KB: skipped. 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: skipped. Probing for Winbond W25Q16, 2048 KB: skipped. Probing for Winbond W25Q32, 4096 KB: skipped. Probing for Winbond W25Q64, 8192 KB: skipped. Probing for Winbond W25x10, 128 KB: skipped. Probing for Winbond W25x20, 256 KB: skipped. Probing for Winbond W25x40, 512 KB: skipped. Probing for Winbond W25x80, 1024 KB: skipped. Probing for Winbond W25x16, 2048 KB: skipped. Probing for Winbond W25x32, 4096 KB: skipped. Probing for Winbond W25x64, 8192 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W29C020(C)/W29C022, 256 KB: skipped. Probing for Winbond W29C040/P, 512 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W39V040A, 512 KB: skipped. Probing for Winbond W39V040B, 512 KB: skipped. Probing for Winbond W39V040C, 512 KB: skipped. Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FB, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FC, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080A, 1024 KB: skipped. Probing for Winbond W49F002U/N, 256 KB: skipped. Probing for Winbond W49F020, 256 KB: skipped. Probing for Winbond W49V002A, 256 KB: skipped. Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA (dual mode), 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for AMIC unknown AMIC SPI chip, 0 KB: skipped. Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Probing for Eon unknown Eon SPI chip, 0 KB: skipped. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Probing for SST unknown SST SPI chip, 0 KB: skipped. Probing for ST unknown ST SPI chip, 0 KB: skipped. Probing for Sanyo unknown Sanyo SPI chip, 0 KB: skipped. Probing for Generic unknown SPI chip (RDID), 0 KB: skipped. Probing for Generic unknown SPI chip (REMS), 0 KB: skipped. === 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, -Vw, -VE), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling checks. Reading old flash chip contents... Erasing and writing flash chip... Looking at blockwise erase function 0... trying... 0x000000-0x000fff:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S, 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:S, 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, 0x015000-0x015fff:S, 0x016000-0x016fff:S, 0x017000-0x017fff:S, 0x018000-0x018fff:S, 0x019000-0x019fff:S, 0x01a000-0x01afff:S, 0x01b000-0x01bfff:S, 0x01c000-0x01cfff:S, 0x01d000-0x01dfff:S, 0x01e000-0x01efff:S, 0x01f000-0x01ffff:S, 0x020000-0x020fff:S, 0x021000-0x021fff:S, 0x022000-0x022fff:S, 0x023000-0x023fff:S, 0x024000-0x024fff:S, 0x025000-0x025fff:S, 0x026000-0x026fff:S, 0x027000-0x027fff:S, 0x028000-0x028fff:S, 0x029000-0x029fff:S, 0x02a000-0x02afff:S, 0x02b000-0x02bfff:S, 0x02c000-0x02cfff:S, 0x02d000-0x02dfff:S, 0x02e000-0x02efff:S, 0x02f000-0x02ffff:S, 0x030000-0x030fff:S, 0x031000-0x031fff:S, 0x032000-0x032fff:S, 0x033000-0x033fff:S, 0x034000-0x034fff:S, 0x035000-0x035fff:S, 0x036000-0x036fff:S, 0x037000-0x037fff:S, 0x038000-0x038fff:S, 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, 0x03c000-0x03cfff:S, 0x03d000-0x03dfff:S, 0x03e000-0x03efff:S, 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, 0x06f000-0x06ffff:S, 0x070000-0x070fff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x00070fff: 0xf70 ERASE FAILED! Looking at blockwise erase function 1... trying... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x0007ffff: 0xfd35 ERASE FAILED! Looking at blockwise erase function 2... trying... 0x000000-0x07ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x53f0b ERASE FAILED! Looking at blockwise erase function 3... not defined. trying... Done. Verifying flash... VERIFY FAILED at 0x0007010b! Expected=0x7c, Read=0x70, failed byte count from 0x00000000-0x0007ffff: 0x9f2 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! Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

mail archives down?
by Bernd Blaauw 10 Dec '12

10 Dec '12

Are the Pipermail mail archives down for some reason? Seeing this at flashrom, seabios and coreboot, of which I'm only subscribed to the first one (thus reading the other 2 from web archive). Getting a 403/Forbidden when clicking the Archives link at: http://www.flashrom.org/mailman/listinfo/flashrom Bernd

2 1

GA-A75M-UD2H
by Stefan Tauner 09 Dec '12

09 Dec '12

re GA-A75M-UD2H and your log at http://paste.flashrom.org/view.php?id=1490 yes, it looks good. thanks for the log. if you chose the correct file it should have booted afterwards without a problem. is/was that the case? please give us a bit more than 2 minutes in the middle of our night to react next time on IRC or send a mail to the mailing list instead ;) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Failure on 7252 MSI K9NBPM2-FID motherboard
by gordy perkins 08 Dec '12

08 Dec '12

Hello - thanks for the great effort on flashrom. My particular board doesn't flash. Here are the particulars. Ubuntu 12.04, if that matters. 0.9.6.1 failed too... gordy@macoushla:~/Downloads/7252v58$ sudo flashromflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000.Multiple flash chips were detected: "W39V040B", "W39V040FB"Please specify which chip to use with the -c <chipname> option.gordy@macoushla:~/Downloads/7252v58$ sudo flashrom -w A7252NMS.580 -c W39V040Bflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.Reading old flash chip contents... done.Erasing and writing flash chip... ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0000ffff: 0x5200ERASE FAILED!Reading current flash chip contents... done. ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0007ffff: 0x657a4ERASE FAILED!FAILED!Uh oh. Erase/write failed. Checking if anything changed.Good. It seems nothing was changed.Writing to the flash chip apparently didn't do anything.This means we have to add special support for your board, programmer or flash chip.Please report this on IRC at irc.freenode.net (channel #flashrom) ormail flashrom@flashrom.org!-------------------------------------------------------------------------------You may now reboot or simply leave the machine running.gordy@macoushla:~/Downloads/7252v58$ sudo flashrom -w A7252NMS.580 -c W39V040FBflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000.Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.Reading old flash chip contents... done.Erasing and writing flash chip... ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0000ffff: 0x5200ERASE FAILED!Reading current flash chip contents... done. ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0007ffff: 0x657a4ERASE FAILED!FAILED!Uh oh. Erase/write failed. Checking if anything changed.Good. It seems nothing was changed.Writing to the flash chip apparently didn't do anything.This means we have to add special support for your board, programmer or flash chip.Please report this on IRC at irc.freenode.net (channel #flashrom) ormail flashrom@flashrom.org!-------------------------------------------------------------------------------You may now reboot or simply leave the machine running.gordy@macoushla:~/Downloads/7252v58$

2 2

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Andrew Goodbody 06 Dec '12

06 Dec '12

On 01/12/12 21:11, Daniel . wrote: > So at last I just need to know now how I can merge the needed > decompressed files back into a flashable ROM file. No, this is the wrong way. You do not need to decompress the .wph file. The .wph file in this case is 1.5MB long with some extra data and code stuck on the end. So the first thing to do is to cut the excess after 1.5MB off the end of that file. This 1.5MB is the top 1.5MB of the 2MB flash image**. Read the first 0.5MB from the flash device* and prefix it to the 1.5MB image to create the 2MB image. You can then program that 2MB image to the flash device. Andrew * If the failed update has corrupted this first 0.5MB on the flash device then you have big trouble. ** If you want to confirm that, disassemble the last 16 bytes of the 1.5MB image, there should be a real mode far jump.

1 0

Fwd: BPv3.6 w flashrom
by Idwer Vollering 05 Dec '12

05 Dec '12

Forwarding. Please "reply to all". ---------- Forwarded message ---------- From: Nabs <ch12011-7(a)yahoo.com.au> Date: 2012/12/5 Subject: Re: [flashrom] BPv3.6 w flashrom To: "vidwer(a)gmail.com" <vidwer(a)gmail.com> Just had a Eureka moment. I think what confused me was the fact that the cables were soldered onto the actual soic clip! So all I need to do is desolder and resolder them into their correct layouts, or desolder and use alligator clips instead? Is that right? Cheers, Nabs. ------------------------------ * From: * Idwer Vollering <vidwer(a)gmail.com>; * To: * Nabs <ch12011-7(a)yahoo.com.au>; * Cc: * flashrom(a)flashrom.org <flashrom(a)flashrom.org>; * Subject: * Re: [flashrom] BPv3.6 w flashrom * Sent: * Wed, Dec 5, 2012 12:05:04 PM 2012/12/5 Nabs <ch12011-7(a)yahoo.com.au>: > Hi, sorry for the trouble. I'm running bus piratev3.6, bootloaderv4.4, > firmwarev6.1 on flashrom-0.9.6.1, i plan to run the BP at 1M. > > When i run the command "flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -Vr > oldbios.bin" > I get: > " > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on > buspirate_spi. > Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, > id2 0x0 > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE > WRITE > " etc... > > > I think i have the wiring wrong which is why i get that error, i wonder if > you could help me as its my first time? > I'm trying to use In-circuit programming with a soldered bios chip using an > 'SOIC 8 clip' and it has 8 wires. But the bus pirate has 10 pins. > > From another thread, these are the connections i need: > Bus Pirate "MISO" (Pin 1) <----- SPI Device "DO" (Wire/Pin 2) > Bus Pirate "CS" (Pin 2) -----> SPI Device "CS" (Wire/Pin 1) > Bus Pirate "MOSI" (Pin 3) -----> SPI Device "DI" (Wire/Pin 5) > Bus Pirate "CLK" (Pin 4) -----> SPI Device "CLK" (Wire/Pin 6) > Bus Pirate "GND" (Pin 10) <----> SPI Device "GND" (Wire/Pin 4) > > It appears to me that GND is pin 10 and that the wires of the SOIC8 clip > only contact pins 1-8, so how can this work? > > Also, could i just check the layout of the pins on the bus pirate if i'm > reading it correctly on BPv3.6: > 10 9 > 8 7 > 6 5 > 4 3 > 2 1 > > Corresponding to: > GND 3V3 > +5V ADC > VPU AUX > CLK MOSI > CS MISO Forget the existence of +5V, VPU, ADC and AUX for now ( http://dangerousprototypes.com/docs/Bus_Pirate_I/O_Pin_Descriptions ), connect the clip to the buspirate so that the clip passes the buspirate pins like mentioned in this post: http://www.coreboot.org/pipermail/flashrom/2012-November/010178.html This works for me, with a MX25L1605A soic8 chip: CS# (CS) [1 chip 8] VCC (bridge with buspirate pin 3+7) SO (MISO) [2 chip 7] HOLD# (+3V3) WP# (bridge with buspirate pin 7+8) [3 chip 6] SCLK (CLK) GND (GND) [4 chip 5] SI (MOSI) > > Or are the pin numbers read in the opposite direction? > ie > 9 10 > 7 8 > 5 6 > 3 4 > 1 2 > > Here's an image of my bus pirate if it helps: > http://dangerousprototypes.com/wp-content/media/2012/11/Bus-Pirate-v3.6inte… > > Your help is much appreciated and i appreciate your patience, Nabs. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] BPv3.6 w flashrom
by Idwer Vollering 05 Dec '12

05 Dec '12

Please "reply to all". 2012/12/5 Nabil <nabil.gergis(a)yahoo.com.au>: > Sorry there's one thing I'm not sure I understand... > Is it possible to adjust the locations of the wires of the soic clip so they match up with the correct pinouts? > I just dont get how gnd (pin 10 of bus pirate) can be connected to the soic clip (only 8 cables which connect to pins 1-8) > there's something I'm missing here i think, could you explain to me how to use an soic clip in detail, sorry for the trouble, much obliged. Nabs Which soic8 clip do you have? I have a Pomona 5250; it is possible to adjust the wire locations (pinouts) if you have the probe cable (that fits on the open end of the wires - the other end is a box header that connects to the buspirate): http://dangerousprototypes.com/2011/08/03/new-bus-pirate-probe-cable/ > > Idwer Vollering <vidwer(a)gmail.com> wrote: > >>2012/12/5 Nabs <ch12011-7(a)yahoo.com.au>: >>> Hi, sorry for the trouble. I'm running bus piratev3.6, bootloaderv4.4, >>> firmwarev6.1 on flashrom-0.9.6.1, i plan to run the BP at 1M. >>> >>> When i run the command "flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -Vr >>> oldbios.bin" >>> I get: >>> " >>> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on >>> buspirate_spi. >>> Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, >>> id2 0x0 >>> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). >>> === >>> This flash part has status NOT WORKING for operations: PROBE READ ERASE >>> WRITE >>> " etc... >>> >>> >>> I think i have the wiring wrong which is why i get that error, i wonder if >>> you could help me as its my first time? >>> I'm trying to use In-circuit programming with a soldered bios chip using an >>> 'SOIC 8 clip' and it has 8 wires. But the bus pirate has 10 pins. >>> >>> From another thread, these are the connections i need: >>> Bus Pirate "MISO" (Pin 1) <----- SPI Device "DO" (Wire/Pin 2) >>> Bus Pirate "CS" (Pin 2) -----> SPI Device "CS" (Wire/Pin 1) >>> Bus Pirate "MOSI" (Pin 3) -----> SPI Device "DI" (Wire/Pin 5) >>> Bus Pirate "CLK" (Pin 4) -----> SPI Device "CLK" (Wire/Pin 6) >>> Bus Pirate "GND" (Pin 10) <----> SPI Device "GND" (Wire/Pin 4) >>> >>> It appears to me that GND is pin 10 and that the wires of the SOIC8 clip >>> only contact pins 1-8, so how can this work? >>> >>> Also, could i just check the layout of the pins on the bus pirate if i'm >>> reading it correctly on BPv3.6: >>> 10 9 >>> 8 7 >>> 6 5 >>> 4 3 >>> 2 1 >>> >>> Corresponding to: >>> GND 3V3 >>> +5V ADC >>> VPU AUX >>> CLK MOSI >>> CS MISO >> >>Forget the existence of +5V, VPU, ADC and AUX for now ( >>http://dangerousprototypes.com/docs/Bus_Pirate_I/O_Pin_Descriptions ), >>connect the clip to the buspirate so that the clip passes the >>buspirate pins like mentioned in this post: >>http://www.coreboot.org/pipermail/flashrom/2012-November/010178.html >> >>This works for me, with a MX25L1605A soic8 chip: >> >>CS# (CS) [1 chip 8] VCC >>(bridge with buspirate pin 3+7) >>SO (MISO) [2 chip 7] HOLD# (+3V3) >>WP# (bridge with buspirate pin 7+8) [3 chip 6] SCLK (CLK) >>GND (GND) [4 chip 5] SI (MOSI) >> >>> >>> Or are the pin numbers read in the opposite direction? >>> ie >>> 9 10 >>> 7 8 >>> 5 6 >>> 3 4 >>> 1 2 >>> >>> Here's an image of my bus pirate if it helps: >>> http://dangerousprototypes.com/wp-content/media/2012/11/Bus-Pirate-v3.6inte… >>> >>> Your help is much appreciated and i appreciate your patience, Nabs. >>> >>> _______________________________________________ >>> flashrom mailing list >>> flashrom(a)flashrom.org >>> http://www.flashrom.org/mailman/listinfo/flashrom

1 0

BPv3.6 w flashrom
by Nabs 05 Dec '12

05 Dec '12

Hi, sorry for the trouble. I'm running bus piratev3.6, bootloaderv4.4, firmwarev6.1 on flashrom-0.9.6.1, i plan to run the BP at 1M. When i run the command "flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -Vr oldbios.bin" I get: " Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on buspirate_spi. Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, id2 0x0 Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE " etc... I think i have the wiring wrong which is why i get that error, i wonder if you could help me as its my first time? I'm trying to use In-circuit programming with a soldered bios chip using an 'SOIC 8 clip' and it has 8 wires. But the bus pirate has 10 pins. From another thread, these are the connections i need: Bus Pirate "MISO" (Pin 1) <----- SPI Device "DO" (Wire/Pin 2) Bus Pirate "CS" (Pin 2) -----> SPI Device "CS" (Wire/Pin 1) Bus Pirate "MOSI" (Pin 3) -----> SPI Device "DI" (Wire/Pin 5) Bus Pirate "CLK" (Pin 4) -----> SPI Device "CLK" (Wire/Pin 6) Bus Pirate "GND" (Pin 10) <----> SPI Device "GND" (Wire/Pin 4) It appears to me that GND is pin 10 and that the wires of the SOIC8 clip only contact pins 1-8, so how can this work? Also, could i just check the layout of the pins on the bus pirate if i'm reading it correctly on BPv3.6: 10 9 8 7 6 5 4 3 2 1 Corresponding to: GND 3V3 +5V ADC VPU AUX CLK MOSI CS MISO Or are the pin numbers read in the opposite direction? ie 9 10 7 8 5 6 3 4 1 2 Here's an image of my bus pirate if it helps: http://dangerousprototypes.com/wp-content/media/2012/11/Bus-Pirate-v3.6inte… Your help is much appreciated and i appreciate your patience, Nabs.

2 1

Bus Pirate + Flashrom
by Nabs 05 Dec '12

05 Dec '12

Hi, i get the following error below when trying to read a bios chip, what options do i have for troubleshooting and what's causing the problem? Thanks Nabs "flashrom -f -Vr bios.img.bin -p buspirate_spi:dev=/dev/tty8,spispeed=1M" flashrom v0.9.5.2-r1517 on Linux 3.2.0-23-generic (x86_64), built with libpci 3.1.8, 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, 1372M loops per second, 10 myus = 10 us, 100 myus = 113 us, 1000 myus = 1036 us, 10000 myus = 10346 us, 4 myus = 6 us, OK. Initializing buspirate_spi programmer SPI speed is 1MHz ^[[BEntering raw bitbang mode failed! Got 1c9ce050e0 Error: Programmer initialization failed. ^[[AEntering raw bitbang mode failed!

1 0

Dell Alienware Aurora R2
by Gilles Antonetti / Gmail 03 Dec '12

03 Dec '12

Apparently my machine has/had been hijacked somehow. The lshw was showing that it was running on 15 logicalcpu. Let me know if you need more. Thanks for help, Regards, Gilles

1 0

[PATCH 4/4] Enable serprog on Windows.
by Stefan Tauner 03 Dec '12

03 Dec '12

Sockets are not ported (yet). Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Signed-off-by: Idwer Vollering <vidwer(a)gmail.com> --- Makefile | 8 +------- serprog.c | 18 ++++++++++++------ 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/Makefile b/Makefile index f3cb07a..b8cb7b7 100644 --- a/Makefile +++ b/Makefile @@ -138,12 +138,6 @@ FLASHROM_CFLAGS += -Dffs=__builtin_ffs # libusb-win32/libftdi stuff is usually installed in /usr/local. CPPFLAGS += -I/usr/local/include LDFLAGS += -L/usr/local/lib -# Serprog is not supported under Windows/MinGW (missing sockets support). -ifeq ($(CONFIG_SERPROG), yes) -UNSUPPORTED_FEATURES += CONFIG_SERPROG=yes -else -override CONFIG_SERPROG = no -endif # For now we disable all PCI-based programmers on Windows/MinGW (no libpci). ifeq ($(CONFIG_INTERNAL), yes) UNSUPPORTED_FEATURES += CONFIG_INTERNAL=yes @@ -324,7 +318,7 @@ SVNDEF := -D'FLASHROM_VERSION="$(VERSION)"' # Always enable internal/onboard support for now. CONFIG_INTERNAL ?= yes -# Always enable serprog for now. Needs to be disabled on Windows. +# Always enable serprog for now. CONFIG_SERPROG ?= yes # RayeR SPIPGM hardware support diff --git a/serprog.c b/serprog.c index 7f432ee..630039c 100644 --- a/serprog.c +++ b/serprog.c @@ -20,21 +20,23 @@ */ #include <stdio.h> +#ifndef _WIN32 /* stuff (presumably) needed for sockets only */ #include <stdlib.h> #include <unistd.h> -#include <strings.h> -#include <string.h> -#include <ctype.h> #include <fcntl.h> #include <sys/socket.h> #include <arpa/inet.h> #include <netinet/in.h> #include <netinet/tcp.h> #include <netdb.h> -#include <sys/stat.h> -#include <errno.h> -#include <inttypes.h> +#endif +#ifdef _WIN32 +#include <conio.h> +#else #include <termios.h> +#endif +#include <string.h> +#include <errno.h> #include "flash.h" #include "programmer.h" #include "chipdrivers.h" @@ -81,6 +83,7 @@ static int sp_opbuf_usage = 0; whether the command is supported before doing it */ static int sp_check_avail_automatic = 0; +#ifndef WIN32 static int sp_opensocket(char *ip, unsigned int port) { int flag = 1; @@ -114,6 +117,7 @@ static int sp_opensocket(char *ip, unsigned int port) setsockopt(sock, IPPROTO_TCP, TCP_NODELAY, &flag, sizeof(int)); return sock; } +#endif /* Synchronize: a bit tricky algorithm that tries to (and in my tests has * * always succeeded in) bring the serial protocol to known waiting-for- * @@ -351,6 +355,7 @@ int serprog_init(void) } free(device); +#ifndef _WIN32 device = extract_programmer_param("ip"); if (have_device && device) { msg_perr("Error: Both host and device specified.\n" @@ -394,6 +399,7 @@ int serprog_init(void) "flashrom -p serprog:ip=ipaddr:port\n"); return 1; } +#endif if (register_shutdown(serprog_shutdown, NULL)) return 1; -- Kind regards, Stefan Tauner

1 0

[PATCH 3/4] Replace native calls in serprog with wrapper calls.
by Stefan Tauner 03 Dec '12

03 Dec '12

read(), write(), usleep() are replaced. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Signed-off-by: Idwer Vollering <vidwer(a)gmail.com> --- serprog.c | 43 +++++++++++++++---------------------------- 1 file changed, 15 insertions(+), 28 deletions(-) diff --git a/serprog.c b/serprog.c index cf329a3..7f432ee 100644 --- a/serprog.c +++ b/serprog.c @@ -133,7 +133,7 @@ static int sp_synchronize(void) goto err_out; } /* A second should be enough to get all the answers to the buffer */ - usleep(1000 * 1000); + internal_delay(1000 * 1000); sp_flush_incoming(); /* Then try up to 8 times to send syncnop and get the correct special * @@ -206,15 +206,15 @@ static int sp_docommand(uint8_t command, uint32_t parmlen, unsigned char c; if (sp_automatic_cmdcheck(command)) return 1; - if (write(sp_fd, &command, 1) != 1) { + if (serialport_write(&command, 1) != 0) { msg_perr("Error: cannot write op code: %s\n", strerror(errno)); return 1; } - if (write(sp_fd, params, parmlen) != (parmlen)) { + if (serialport_write(params, parmlen) != 0) { msg_perr("Error: cannot write parameters: %s\n", strerror(errno)); return 1; } - if (read(sp_fd, &c, 1) != 1) { + if (serialport_read(&c, 1) != 0) { msg_perr("Error: cannot read from device: %s\n", strerror(errno)); return 1; } @@ -225,17 +225,10 @@ static int sp_docommand(uint8_t command, uint32_t parmlen, return 1; } if (retlen) { - int rd_bytes = 0; - do { - int r; - r = read(sp_fd, retparms + rd_bytes, - retlen - rd_bytes); - if (r <= 0) { - msg_perr("Error: cannot read return parameters: %s\n", strerror(errno)); - return 1; - } - rd_bytes += r; - } while (rd_bytes != retlen); + if (serialport_read(retparms, retlen) != 0) { + msg_perr("Error: cannot read return parameters: %s\n", strerror(errno)); + return 1; + } } return 0; } @@ -245,7 +238,7 @@ static void sp_flush_stream(void) if (sp_streamed_transmit_ops) do { unsigned char c; - if (read(sp_fd, &c, 1) != 1) { + if (serialport_read(&c, 1) != 0) { sp_die("Error: cannot read from device (flushing stream)"); } if (c == S_NAK) { @@ -272,7 +265,7 @@ static int sp_stream_buffer_op(uint8_t cmd, uint32_t parmlen, uint8_t * parms) memcpy(&(sp[1]), parms, parmlen); if (sp_streamed_transmit_bytes >= (1 + parmlen + sp_device_serbuf_size)) sp_flush_stream(); - if (write(sp_fd, sp, 1 + parmlen) != (1 + parmlen)) + if (serialport_write(sp, 1 + parmlen) != 0) sp_die("Error: cannot write command"); free(sp); sp_streamed_transmit_ops += 1; @@ -684,10 +677,9 @@ static void sp_pass_writen(void) header[4] = (sp_write_n_addr >> 0) & 0xFF; header[5] = (sp_write_n_addr >> 8) & 0xFF; header[6] = (sp_write_n_addr >> 16) & 0xFF; - if (write(sp_fd, header, 7) != 7) + if (serialport_write(header, 7) != 0) sp_die("Error: cannot write write-n command\n"); - if (write(sp_fd, sp_write_n_buf, sp_write_n_bytes) != - sp_write_n_bytes) + if (serialport_write(sp_write_n_buf, sp_write_n_bytes) != 0) sp_die("Error: cannot write write-n data"); sp_streamed_transmit_bytes += 7 + sp_write_n_bytes; sp_streamed_transmit_ops += 1; @@ -788,7 +780,7 @@ static uint8_t serprog_chip_readb(const struct flashctx *flash, buf[2] = ((addr >> 16) & 0xFF); sp_stream_buffer_op(S_CMD_R_BYTE, 3, buf); sp_flush_stream(); - if (read(sp_fd, &c, 1) != 1) + if (serialport_read(&c, 1) != 0) sp_die("readb byteread"); msg_pspew("%s addr=0x%lx returning 0x%02X\n", __func__, addr, c); return c; @@ -797,7 +789,6 @@ static uint8_t serprog_chip_readb(const struct flashctx *flash, /* Local version that really does the job, doesn't care of max_read_n. */ static void sp_do_read_n(uint8_t * buf, const chipaddr addr, size_t len) { - int rd_bytes = 0; unsigned char sbuf[6]; msg_pspew("%s: addr=0x%lx len=%lu\n", __func__, addr, (unsigned long)len); /* Stream the read-n -- as above. */ @@ -811,12 +802,8 @@ static void sp_do_read_n(uint8_t * buf, const chipaddr addr, size_t len) sbuf[5] = ((len >> 16) & 0xFF); sp_stream_buffer_op(S_CMD_R_NBYTES, 6, sbuf); sp_flush_stream(); - do { - int r = read(sp_fd, buf + rd_bytes, len - rd_bytes); - if (r <= 0) - sp_die("Error: cannot read read-n data"); - rd_bytes += r; - } while (rd_bytes != len); + if (serialport_read(buf, len) != 0) + sp_die("Error: cannot read read-n data"); return; } -- Kind regards, Stefan Tauner

1 0

[PATCH 2/4] Introduce serialport_write_nonblock().
by Stefan Tauner 03 Dec '12

03 Dec '12

It seems useful to have a generic and platform-independent method to read and write to a serial port without blocking. This is the write part. This allows to get rid of the explicit temporary disabling of blocking I/O in serprog's sp_synchronize(). Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- programmer.h | 1 + serial.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ serprog.c | 19 ++++------------ 3 files changed, 78 insertions(+), 14 deletions(-) diff --git a/programmer.h b/programmer.h index e385314..722fa54 100644 --- a/programmer.h +++ b/programmer.h @@ -649,6 +649,7 @@ extern fdtype sp_fd; /* expose serialport_shutdown as it's currently used by buspirate */ int serialport_shutdown(void *data); int serialport_write(unsigned char *buf, unsigned int writecnt); +int serialport_write_nonblock(unsigned char *buf, unsigned int writecnt, unsigned int timeout, unsigned int *really_wrote); int serialport_read(unsigned char *buf, unsigned int readcnt); int serialport_read_nonblock(unsigned char *c, unsigned int readcnt, unsigned int timeout, unsigned int *really_read); diff --git a/serial.c b/serial.c index 15fafbb..7c136c9 100644 --- a/serial.c +++ b/serial.c @@ -387,3 +387,75 @@ int serialport_read_nonblock(unsigned char *c, unsigned int readcnt, unsigned in #endif return ret; } + +/* Tries up to timeout ms to write writecnt characters from the array starting at buf. Returns + * 0 on success, positive values on temporary errors (e.g. timeouts) and negative ones on permanent errors. + * If really_wrote is not NULL, this function sets its contents to the number of bytes written successfully. */ +int serialport_write_nonblock(unsigned char *buf, unsigned int writecnt, unsigned int timeout, unsigned int *really_wrote) +{ + int ret = 1; + /* disable blocked i/o and declare platform-specific variables */ +#ifdef _WIN32 + DWORD rv; + COMMTIMEOUTS oldTimeout; + COMMTIMEOUTS newTimeout = { + .ReadIntervalTimeout = MAXDWORD, + .ReadTotalTimeoutMultiplier = 0, + .ReadTotalTimeoutConstant = 0, + .WriteTotalTimeoutMultiplier = 0, + .WriteTotalTimeoutConstant = 0 + }; + if(GetCommTimeouts(sp_fd, &oldTimeout) != 0) { + msg_perr("Could not get serial port timeout settings!\n"); + return -1; + } + if(SetCommTimeouts(sp_fd, &newTimeout) != 0) { + msg_perr("Could not set serial port timeout settings!\n"); + return -1; + } +#else + ssize_t rv; + const int flags = fcntl(sp_fd, F_GETFL); + fcntl(sp_fd, F_SETFL, flags | O_NONBLOCK); +#endif + + int i; + int wr_bytes = 0; + for (i = 0; i < timeout; i++) { + msg_pspew("writecnt %d wr_bytes %d\n", writecnt, wr_bytes); +#ifdef _WIN32 + WriteFile(sp_fd, buf + wr_bytes, writecnt - wr_bytes, &rv, NULL); + msg_pspew("wrote %lu bytes\n", rv); +#else + rv = write(sp_fd, buf + wr_bytes, writecnt - wr_bytes); + msg_pspew("wrote %zd bytes\n", rv); +#endif + if ((rv == -1) && (errno != EAGAIN)) { + msg_perr("Serial port write error: %s\n", strerror(errno)); + ret = -1; + break; + } + if (rv > 0) { + wr_bytes += rv; + if (wr_bytes == writecnt) { + msg_pspew("write successful\n"); + ret = 0; + break; + } + } + internal_delay(1000); /* 1ms units */ + } + if (really_wrote != NULL) + *really_wrote = wr_bytes; + + /* restore original blocking behavior */ +#ifdef _WIN32 + if(SetCommTimeouts(sp_fd, &oldTimeout) != 0) { + msg_perr("Could not restore serial port timeout settings!\n"); + return -1; + } +#else + fcntl(sp_fd, F_SETFL, flags); +#endif + return ret; +} diff --git a/serprog.c b/serprog.c index cc06798..cf329a3 100644 --- a/serprog.c +++ b/serprog.c @@ -117,23 +117,19 @@ static int sp_opensocket(char *ip, unsigned int port) /* Synchronize: a bit tricky algorithm that tries to (and in my tests has * * always succeeded in) bring the serial protocol to known waiting-for- * - * command state - uses nonblocking read - rest of the driver uses * + * command state - uses nonblocking I/O - rest of the driver uses * * blocking read - TODO: add an alarm() timer for the rest of the app on * * serial operations, though not such a big issue as the first thing to * * do is synchronize (eg. check that device is alive). */ static int sp_synchronize(void) { int i; - int flags = fcntl(sp_fd, F_GETFL); unsigned char buf[8]; - flags |= O_NONBLOCK; - fcntl(sp_fd, F_SETFL, flags); /* First sends 8 NOPs, then flushes the return data - should cause * * the device serial parser to get to a sane state, unless if it * * is waiting for a real long write-n. */ memset(buf, S_CMD_NOP, 8); - if (write(sp_fd, buf, 8) != 8) { - msg_perr("flush write: %s\n", strerror(errno)); + if (serialport_write_nonblock(buf, 8, 1, NULL) != 0) { goto err_out; } /* A second should be enough to get all the answers to the buffer */ @@ -147,8 +143,7 @@ static int sp_synchronize(void) for (i = 0; i < 8; i++) { int n; unsigned char c = S_CMD_SYNCNOP; - if (write(sp_fd, &c, 1) != 1) { - msg_perr("sync write: %s\n", strerror(errno)); + if (serialport_write_nonblock(&c, 1, 1, NULL) != 0) { goto err_out; } msg_pdbg("."); @@ -165,9 +160,8 @@ static int sp_synchronize(void) if (ret > 0 || c != S_ACK) continue; c = S_CMD_SYNCNOP; - if (write(sp_fd, &c, 1) != 1) { - msg_perr("sync write: %s\n", strerror(errno)); - return 1; + if (serialport_write_nonblock(&c, 1, 1, NULL) != 0) { + goto err_out; } ret = serialport_read_nonblock(&c, 1, 500, NULL); if (ret < 0) @@ -179,9 +173,6 @@ static int sp_synchronize(void) goto err_out; if (c != S_ACK) break; /* fail */ - /* Ok, synchronized; back to blocking reads and return. */ - flags &= ~O_NONBLOCK; - fcntl(sp_fd, F_SETFL, flags); msg_pdbg("\n"); return 0; } -- Kind regards, Stefan Tauner

1 0

[PATCH 1/4] Replace sp_sync_read_timeout() with serialport_read_nonblock().
by Stefan Tauner 03 Dec '12

03 Dec '12

It seems useful to have a generic and platform-independent method to read and write to a serial port without blocking. This is the read part. It stores the current blocking properties before disabling blocking and restores them after reading. The timeout is implemented as previously by retrying every millisecond until the timeout is reached or enough characters are available. TODO: testing on windows and then removing the spew prints. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- programmer.h | 1 + serial.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ serprog.c | 28 ++++------------------- 3 files changed, 76 insertions(+), 24 deletions(-) diff --git a/programmer.h b/programmer.h index dedec67..e385314 100644 --- a/programmer.h +++ b/programmer.h @@ -650,6 +650,7 @@ extern fdtype sp_fd; int serialport_shutdown(void *data); int serialport_write(unsigned char *buf, unsigned int writecnt); int serialport_read(unsigned char *buf, unsigned int readcnt); +int serialport_read_nonblock(unsigned char *c, unsigned int readcnt, unsigned int timeout, unsigned int *really_read); /* Serial port/pin mapping: diff --git a/serial.c b/serial.c index 9446ce3..15fafbb 100644 --- a/serial.c +++ b/serial.c @@ -316,3 +316,74 @@ int serialport_read(unsigned char *buf, unsigned int readcnt) return 0; } + +/* Tries up to timeout ms to read readcnt characters and places them into the array starting at c. Returns + * 0 on success, positive values on temporary errors (e.g. timeouts) and negative ones on permanent errors. + * If really_read is not NULL, this function sets its contents to the number of bytes read successfully. */ +int serialport_read_nonblock(unsigned char *c, unsigned int readcnt, unsigned int timeout, unsigned int *really_read) +{ + int ret = 1; + /* disable blocked i/o and declare platform-specific variables */ +#ifdef _WIN32 + DWORD rv; + COMMTIMEOUTS oldTimeout; + COMMTIMEOUTS newTimeout = { + .ReadIntervalTimeout = MAXDWORD, + .ReadTotalTimeoutMultiplier = 0, + .ReadTotalTimeoutConstant = 0, + .WriteTotalTimeoutMultiplier = 0, + .WriteTotalTimeoutConstant = 0 + }; + if(GetCommTimeouts(sp_fd, &oldTimeout) != 0) { + msg_perr("Could not get serial port timeout settings!\n"); + return -1; + } + if(SetCommTimeouts(sp_fd, &newTimeout) != 0) { + msg_perr("Could not set serial port timeout settings!\n"); + return -1; + } +#else + ssize_t rv; + const int flags = fcntl(sp_fd, F_GETFL); + fcntl(sp_fd, F_SETFL, flags | O_NONBLOCK); +#endif + + int i; + int rd_bytes = 0; + for (i = 0; i < timeout; i++) { + msg_pspew("readcnt %d rd_bytes %d\n", readcnt, rd_bytes); +#ifdef _WIN32 + ReadFile(sp_fd, c + rd_bytes, readcnt - rd_bytes, &rv, NULL); + msg_pspew("read %lu bytes\n", rv); +#else + rv = read(sp_fd, c + rd_bytes, readcnt - rd_bytes); + msg_pspew("read %zd bytes\n", rv); +#endif + if ((rv == -1) && (errno != EAGAIN)) { + msg_perr("Serial port read error: %s\n", strerror(errno)); + ret = -1; + break; + } + if (rv > 0) + rd_bytes += rv; + if (rd_bytes == readcnt) { + msg_perr("read successful\n"); + ret = 0; + break; + } + internal_delay(1000); /* 1ms units */ + } + if (really_read != NULL) + *really_read = rd_bytes; + + /* restore original blocking behavior */ +#ifdef _WIN32 + if(SetCommTimeouts(sp_fd, &oldTimeout) != 0) { + msg_perr("Could not restore serial port timeout settings!\n"); + return -1; + } +#else + fcntl(sp_fd, F_SETFL, flags); +#endif + return ret; +} diff --git a/serprog.c b/serprog.c index 98c839e..cc06798 100644 --- a/serprog.c +++ b/serprog.c @@ -115,26 +115,6 @@ static int sp_opensocket(char *ip, unsigned int port) return sock; } -/* Returns 0 on success and places the character read into the location pointed to by c. - * Returns positive values on temporary errors and negative ones on permanent errors. - * An iteration of one loop takes up to 1ms. */ -static int sp_sync_read_timeout(unsigned int loops, unsigned char *c) -{ - int i; - for (i = 0; i < loops; i++) { - ssize_t rv; - rv = read(sp_fd, c, 1); - if (rv == 1) - return 0; - if ((rv == -1) && (errno != EAGAIN)) { - msg_perr("read: %s\n", strerror(errno)); - return -1; - } - usleep(1000); /* 1ms units */ - } - return 1; -} - /* Synchronize: a bit tricky algorithm that tries to (and in my tests has * * always succeeded in) bring the serial protocol to known waiting-for- * * command state - uses nonblocking read - rest of the driver uses * @@ -174,12 +154,12 @@ static int sp_synchronize(void) msg_pdbg("."); fflush(stdout); for (n = 0; n < 10; n++) { - int ret = sp_sync_read_timeout(50, &c); + int ret = serialport_read_nonblock(&c, 1, 50, NULL); if (ret < 0) goto err_out; if (ret > 0 || c != S_NAK) continue; - ret = sp_sync_read_timeout(20, &c); + ret = serialport_read_nonblock(&c, 1, 20, NULL); if (ret < 0) goto err_out; if (ret > 0 || c != S_ACK) @@ -189,12 +169,12 @@ static int sp_synchronize(void) msg_perr("sync write: %s\n", strerror(errno)); return 1; } - ret = sp_sync_read_timeout(500, &c); + ret = serialport_read_nonblock(&c, 1, 500, NULL); if (ret < 0) goto err_out; if (ret > 0 || c != S_NAK) break; /* fail */ - ret = sp_sync_read_timeout(100, &c); + ret = serialport_read_nonblock(&c, 1, 100, NULL); if (ret > 0 || ret < 0) goto err_out; if (c != S_ACK) -- Kind regards, Stefan Tauner

1 0

[PATCH 0/4] Port serprog to Windows
by Stefan Tauner 03 Dec '12

03 Dec '12

No idea why we did that... Idwer got me started and this came out. Tested with my AVR flasher on Ubuntu, compile tested with MinGW. Stefan Tauner (4): Replace sp_sync_read_timeout() with serialport_read_nonblock(). Introduce serialport_write_nonblock(). Replace native calls in serprog with wrapper calls. Enable serprog on Windows. Makefile | 8 +--- programmer.h | 2 + serial.c | 143 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ serprog.c | 108 +++++++++++++++----------------------------- 4 files changed, 182 insertions(+), 79 deletions(-) -- Kind regards, Stefan Tauner

1 0

Re: [flashrom] EC A928 failed flash. part 2.1
by Stefan Tauner 02 Dec '12

02 Dec '12

On Sun, 2 Dec 2012 00:33:10 +0100 Idwer Vollering <vidwer(a)gmail.com> wrote: > 2012/12/1 simon <simon.riget(a)gmail.com>: > > Den 01-12-2012 02:13, Stefan Tauner skrev: > > > > Hi Stefan > > > > Patch added and seems to work fine. > > Can you re-send the patch, which we'll happily integrate, this time > not as a .vcf? that was misread by Idwer, sorry. everything is fine and the change will be committed with my tested_stuff branch. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Need help with failed flash. part 2.1
by Simon Riget 02 Dec '12

02 Dec '12

Biso was flashed with backup and are hopefully restored. flashrom -p internal -V: http://paste.flashrom.org/view.php?id=1442 lspci -nnvvvxxx: http://paste.flashrom.org/view.php?id=1443 superiotool -deV : http://paste.flashrom.org/view.php?id=1444 flashrom -p internal -r readout.rom: http://paste.flashrom.org/view.php?id=1445 Best regards Simon Riget

4 10

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Daniel . 01 Dec '12

01 Dec '12

I'm sorry there went something wrong in my last answer. I wanted to send the following text: Ok I have tried to use bcpvpd but it was not working because of an incorrect input file format. So I have done the following steps now: 1. Extract the .wph file from Bios .exe file (result see my last answer) 2. Loading the .wph file into Phoenix WinPhlash v1.7.16.0 to get some more information about the Bios (see attached log file) 3. Decompressed the .wph file with PhoenixTool v2.11 into several single Bios module files. I guess it is the same what bcpvpd would have done. So it seems you are right that the Bios file is compressed because the folder of extracted wph has a size of 2.497 KB which nearly match the chip size. You can check the other 2 attached log files (one is the decompressing log and the other one the folder structure). So at last I just need to know now how I can merge the needed decompressed files back into a flashable ROM file. Can someone help me? I hope the log files give some more information. Thanks and regards, Daniel

1 0

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Stefan Tauner 01 Dec '12

01 Dec '12

On Fri, 30 Nov 2012 08:43:32 +0100 "Daniel ." <phl3ckz(a)googlemail.com> wrote: > > > > that is a bit odd (at least to me). you have not mentioned which board > > we are talking about all the time. please give us some details. > > > > Ok here are some more details about the Laptop: > > Model: Samsung NP-R719-FA01DE > Mainboard: CANNES-L,PGA,DDR2,1MB L2 Cache,N10M-LP,SATA,-,Intel PM45 > Part Code: BA92-05835A > > The BIOS is downloadable from Samsung Support site. Last version: 09CI > It comes as packed .exe file. I have it extracted it and get the following > structure: > > 09CIM060.wph 1.613.930 30.11.2012 08:35 -a-- > AddMem.sys 3.205 30.11.2012 08:35 -a-- > ConResChs.dll 65.536 30.11.2012 08:35 -a-- > ConResCht.dll 65.536 30.11.2012 08:35 -a-- > ConResEn.dll 69.632 30.11.2012 08:35 -a-- > ConResFr.dll 69.632 30.11.2012 08:35 -a-- > ConResGr.dll 69.632 30.11.2012 08:35 -a-- > ConResKr.dll 65.536 30.11.2012 08:35 -a-- > ConResPo.dll 69.632 30.11.2012 08:35 -a-- > ConResRu.dll 69.632 30.11.2012 08:35 -a-- > ConResSp.dll 69.632 30.11.2012 08:35 -a-- > devcon.exe 80.896 30.11.2012 08:35 -a-- > mfc42.dll 995.383 30.11.2012 08:35 -a-- > msvcp60.dll 401.462 30.11.2012 08:35 -a-- > msvcrt.dll 266.293 30.11.2012 08:35 -a-- > PHLASH_32.INI 235 30.11.2012 08:35 -a-- > PHLASH_64.INI 302 30.11.2012 08:35 -a-- > PhlashLc_32.dll 204.800 30.11.2012 08:35 -a-- > PhlashLc_64.dll 200.704 30.11.2012 08:35 -a-- > PhlashNT_32.sys 40.120 30.11.2012 08:35 -a-- > PhlashNT_64.sys 47.160 30.11.2012 08:35 -a-- > SABI2.dll 53.248 30.11.2012 08:35 -a-- > SWinFlash_32.exe 319.488 30.11.2012 08:35 -a-- > SWinFlash_64.exe 299.008 30.11.2012 08:35 -a-- > WinUp64_V01.exe 327.680 30.11.2012 08:35 -a-- > WinUpV01_10.exe 122.880 30.11.2012 08:35 -a-- > > As you can see the BIOS file 09CIM060.wph has just a size of 1.613.930. > The dump from chip is 2.097.152. ok in that case a colleague suggested that the file is probably compressed and can be decompressed with a tool contained in the bios_extract repository named bcpvpd you can find it here http://review.coreboot.org/gitweb?p=bios_extract.git;a=summary i have not tried it on that file, please try yourself. if it works and expands to the right size you can flash it. if not we would like to hear about it :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

ASUS Sabertooth 990FX R2.0 - EN25F64 - erase and write tested
by František Kučera 01 Dec '12

01 Dec '12

Hi, at first I want to thank everybody working on flashrom and coreboot. I really appreciate your work. I have ASUS Sabertooth 990FX R2.0 motherboard and I got message: "This flash part has status UNTESTED for operations: ERASE WRITE" Because I have also a spare chip, I tested this operations with the original one and it seems working - my computer is able to boot after erasing the chip and writing the ROM image :-) Original chip is Eon "EN25F64" (8192 kB, SPI). For more details please see attached files. Regards, František Kučera

2 1

GA-MA785GT-UD3H (rev. 1.0)
by Андрей Булаев 01 Dec '12

01 Dec '12

GA-MA785GT-UD3H (rev. 1.0) ? http://www.gigabyte.com/products/product-page.aspx?pid=3154#ov

3 2

Re: [flashrom] Flashrom v0.9.6.1-r1564 BIOS reading fail on HP EliteBook 8560p
by Stefan Tauner 01 Dec '12

01 Dec '12

On Fri, 30 Nov 2012 12:21:28 +0100 Marc-Alexandre Espiaut <lunavorax(a)gmail.com> wrote: > Here's the log you're asking for. > I haven't installed dmidecode since it prevents flashrom from running > on a laptop for security reasons. > > Replacing the current BIOS on this laptop would be a blast. HP/Compaq > BIOS prevents the user to change the hardware to what they want. For > exemple, replacing a Mini PCI-e Wifi card that requires proprietary > drivers with one that can use FOSS drivers. > > Hope that helps, feel free to contact me for further informations > about my laptop. Hello Marc-Alexandre, thanks for your report, but flashrom won't work on that machine anytime soon (or ever). I have added the board to our list of (un)supported boards (with an appropriate note) and will commit that later together with other small changes. You could get/build an external programmer, dismantle the laptop, find the flash chip and write it that way. see http://flashrom.org/Supported_programmers and http://flashrom.org/ISP That's all we can do for you, sorry. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] GA-M720-US3 (rev. 1.1) flashrom -V
by Stefan Tauner 01 Dec '12

01 Dec '12

On Wed, 28 Nov 2012 13:01:05 +0100 "UnbAs.Foro" <unbas.foro(a)gmail.com> wrote: > Hi! > > Thanks for your sotfware. I upload my results of -V and my -w > > Thanks!! it was already reported as working last year http://www.flashrom.org/pipermail/flashrom/2011-July/007104.html but i forgot to mark the chipset as tested (which does only get rid of one of the two warnings), i have done that now and will commit that later, thanks. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

problem with software
by goran metlic 01 Dec '12

01 Dec '12

Hi I have problems flashing mx25l4005 chip. I'm using raspberry pi for flashing. I have connected to is thru putty and i have compiled flashrom from latest stable release. There are flashrom log files that I have created. It looks like it doesn't recognize chip. I have connected chip using folowing rpi header name chip pin 1 3.3V 8 6 GND 4 19 DI 5 21 DO 2 23 SCK 6 24 CS 1 Any ideas on how to solve this? Kind regards Goran Metlic

2 1

Re: [flashrom] [PATCH 3/3] Fix sp_openserport users on Windows.
by Stefan Tauner 30 Nov '12

30 Nov '12

On Mon, 26 Nov 2012 16:52:17 +0100 Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> wrote: > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> acked by idwer on IRC and committed in r1627. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] [PATCH] Break endless loop in serialport_write().
by Stefan Tauner 30 Nov '12

30 Nov '12

On Thu, 29 Nov 2012 17:43:50 +0100 Idwer Vollering <vidwer(a)gmail.com> wrote: > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> > > Note that this introduces a minor execution slowdown when used with -o/--output. (in the case of a broken setup only) > Acked-by: Idwer Vollering <vidwer(a)gmail.com> thanks, committed in r1626. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

[commit] r1627 - trunk
by repository service 30 Nov '12

30 Nov '12

Author: stefanct Date: Fri Nov 30 17:46:45 2012 New Revision: 1627 URL: http://flashrom.org/trac/flashrom/changeset/1627 Log: Fix sp_openserport users on Windows. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Idwer Vollering <vidwer(a)gmail.com> Modified: trunk/buspirate_spi.c trunk/pony_spi.c trunk/serprog.c Modified: trunk/buspirate_spi.c ============================================================================== --- trunk/buspirate_spi.c Fri Nov 30 17:46:41 2012 (r1626) +++ trunk/buspirate_spi.c Fri Nov 30 17:46:45 2012 (r1627) @@ -40,7 +40,7 @@ { /* 115200bps, 8 databits, no parity, 1 stopbit */ sp_fd = sp_openserport(dev, 115200); - if (sp_fd < 0) + if (sp_fd == SER_INV_FD) return 1; return 0; } Modified: trunk/pony_spi.c ============================================================================== --- trunk/pony_spi.c Fri Nov 30 17:46:41 2012 (r1626) +++ trunk/pony_spi.c Fri Nov 30 17:46:45 2012 (r1627) @@ -116,7 +116,7 @@ arg = extract_programmer_param("dev"); if (arg && strlen(arg)) { sp_fd = sp_openserport(arg, 9600); - if (sp_fd < 0) { + if (sp_fd == SER_INV_FD) { free(arg); return 1; } Modified: trunk/serprog.c ============================================================================== --- trunk/serprog.c Fri Nov 30 17:46:41 2012 (r1626) +++ trunk/serprog.c Fri Nov 30 17:46:45 2012 (r1627) @@ -372,7 +372,7 @@ } if (strlen(device)) { sp_fd = sp_openserport(device, atoi(baudport)); - if (sp_fd < 0) { + if (sp_fd == SER_INV_FD) { free(device); return 1; }

1 0

[commit] r1626 - trunk
by repository service 30 Nov '12

30 Nov '12

Author: stefanct Date: Fri Nov 30 17:46:41 2012 New Revision: 1626 URL: http://flashrom.org/trac/flashrom/changeset/1626 Log: Break endless loop in serialport_write(). serialport_write could loop endlessly when used with a seemingly valid port that does always return 0 on writes instead of an error. Give up after about 125 ms i.e. 250 tries with a period of 500 us. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Idwer Vollering <vidwer(a)gmail.com> Modified: trunk/serial.c Modified: trunk/serial.c ============================================================================== --- trunk/serial.c Thu Nov 29 23:22:04 2012 (r1625) +++ trunk/serial.c Fri Nov 30 17:46:41 2012 (r1626) @@ -262,6 +262,7 @@ #else ssize_t tmp = 0; #endif + unsigned int empty_writes = 250; /* results in a ca. 125ms timeout */ while (writecnt > 0) { #ifdef _WIN32 @@ -273,9 +274,16 @@ msg_perr("Serial port write error!\n"); return 1; } - if (!tmp) - msg_pdbg("Empty write\n"); - writecnt -= tmp; + if (!tmp) { + msg_pdbg2("Empty write\n"); + empty_writes--; + programmer_delay(500); + if (empty_writes == 0) { + msg_perr("Serial port is unresponsive!\n"); + return 1; + } + } + writecnt -= tmp; buf += tmp; }

1 0

Flashrom v0.9.6.1-r1564 BIOS reading fail on HP EliteBook 8560p
by Marc-Alexandre Espiaut 30 Nov '12

30 Nov '12

Here's the log you're asking for. I haven't installed dmidecode since it prevents flashrom from running on a laptop for security reasons. Replacing the current BIOS on this laptop would be a blast. HP/Compaq BIOS prevents the user to change the hardware to what they want. For exemple, replacing a Mini PCI-e Wifi card that requires proprietary drivers with one that can use FOSS drivers. Hope that helps, feel free to contact me for further informations about my laptop. Regards, Marc-Alexandre Espiaut

1 0

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Stefan Tauner 30 Nov '12

30 Nov '12

On Thu, 29 Nov 2012 23:48:14 +0100 "Daniel ." <phl3ckz(a)googlemail.com> wrote: > In my case the BIOS file is smaller than the chip size. So I need to blow > it up. Are there some information about that somewhere? I couldnt find > anything? that is a bit odd (at least to me). you have not mentioned which board we are talking about all the time. please give us some details. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Stefan Tauner 30 Nov '12

30 Nov '12

On Thu, 29 Nov 2012 23:29:28 +0100 "Daniel ." <phl3ckz(a)googlemail.com> wrote: > Maybe just a last question. Is it possible to flash a .wph BIOS-file with > flashrom? Furthermore I have read something about that the BIOS-file has to > be the same size like the chip. This is not the case for me. Can someone > help? flashrom does not care about the contents of the files you fed it at all, hence they must be prepared first. usually this is done by cutting out headers or footers. in the case of wph it is likely that you can cut everything away that is larger than your flash chip AFAIK. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Daniel . 29 Nov '12

29 Nov '12

Ok thanks for the info. In my case the BIOS file is smaller than the chip size. So I need to blow it up. Are there some information about that somewhere? I couldnt find anything? Thanks and regards, Daniel Am 29.11.2012 23:29 schrieb "Daniel ." <phl3ckz(a)googlemail.com>: > Oh I'm sorry that was my fault. :-D > > At the end I can tell you everything works fine and I was able to read out > the flash content. > > I really appreciate your help you made my day. > > Maybe just a last question. Is it possible to flash a .wph BIOS-file with > flashrom? Furthermore I have read something about that the BIOS-file has to > be the same size like the chip. This is not the case for me. Can someone > help? > > Best regards, > Daniel > Am 29.11.2012 22:00 schrieb "Stefan Tauner" < > stefan.tauner(a)student.tuwien.ac.at>: > >> On Thu, 29 Nov 2012 21:40:44 +0100 >> "Daniel ." <phl3ckz(a)googlemail.com> wrote: >> >> > Could you please tell me the names of PIN 3, 7 and 8 in your >> > description. >> >> he was talking about the flash chip pin numbers, not the bus pirate pin >> numbers. ;) >> >> -- >> Kind regards/Mit freundlichen Grüßen, Stefan Tauner >> >

1 0

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Stefan Tauner 29 Nov '12

29 Nov '12

On Thu, 29 Nov 2012 21:40:44 +0100 "Daniel ." <phl3ckz(a)googlemail.com> wrote: > Could you please tell me the names of PIN 3, 7 and 8 in your > description. he was talking about the flash chip pin numbers, not the bus pirate pin numbers. ;) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

[commit] r1625 - trunk
by repository service 29 Nov '12

29 Nov '12

Author: hailfinger Date: Thu Nov 29 23:22:04 2012 New Revision: 1625 URL: http://flashrom.org/trac/flashrom/changeset/1625 Log: Fix linker flag bug introduced in r1623. Spotted by Idwer Vollering. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Modified: trunk/Makefile Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Sat Nov 24 19:59:39 2012 (r1624) +++ trunk/Makefile Thu Nov 29 23:22:04 2012 (r1625) @@ -710,10 +710,10 @@ echo "See README for more information."; echo; \ rm -f .test.c .test.o; exit 1) @printf "Checking if libpci is present and sufficient... " - @$(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(PCILIBS) >/dev/null && \ + @$(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(PCILIBS) >/dev/null && \ echo "yes." || ( echo "no."; \ printf "Checking if libz+libpci are present and sufficient..."; \ - $(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(PCILIBS) -lz >/dev/null && \ + $(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(PCILIBS) -lz >/dev/null && \ ( echo "yes."; echo "NEEDLIBZ := yes" > .libdeps ) || ( echo "no."; echo; \ echo "Please install libpci (package pciutils) and/or libz."; \ echo "See README for more information."; echo; \ @@ -729,7 +729,7 @@ echo "See README for more information."; echo; \ rm -f .test.c .test.o; exit 1) @printf "Checking if libusb-0.1 is usable... " - @$(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(USBLIBS) >/dev/null && \ + @$(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(USBLIBS) >/dev/null && \ echo "yes." || ( echo "no."; \ echo "Please install libusb-0.1 or libusb-compat."; \ echo "See README for more information."; echo; \

1 0

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Stefan Tauner 29 Nov '12

29 Nov '12

On Thu, 29 Nov 2012 05:25:38 +0100 "Daniel ." <phl3ckz(a)googlemail.com> wrote: > Hi everyone, > > I am absolute beginner but I need to read and write the above mentioned > serial Flash memory. > > This is a BIOS chip and had a bad flash. Now it is unsoldered from > mainboard. I want read it out and reflash a new BIOS file. > > Therefore I really need help how to connect the chip pins with the > buspirate pins in a correct way. Hello, we have fixed the flashrom website and i have added a table explaining the connections. please see http://flashrom.org/Bus_Pirate#Connections -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Dear team flashrom
by In Krikoon Hilton Enterprise 29 Nov '12

29 Nov '12

Dear team flashrom I wish know when you produce update for ASUS M2N-MX SE PLUS. When I install Linux always appeared string <kernel panic IO-APIC+timer doesn't work!> I wish replace proprietary code in my PC Sincerely Alexander

1 0

Re: [flashrom] [PATCH] Break endless loop in serialport_write().
by Idwer Vollering 29 Nov '12

29 Nov '12

2012/11/29 Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at>: > serialport_write could loop endlessly when used with a seemingly valid port > that does always return 0 on writes instead of an error. > Give up after about 125 ms i.e. 250 tries with a period of 500 us. > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Note that this introduces a minor execution slowdown when used with -o/--output. Acked-by: Idwer Vollering <vidwer(a)gmail.com> > --- > serial.c | 14 +++++++++++--- > 1 file changed, 11 insertions(+), 3 deletions(-) > > diff --git a/serial.c b/serial.c > index 7e47dcc..794763e 100644 > --- a/serial.c > +++ b/serial.c > @@ -262,6 +262,7 @@ int serialport_write(unsigned char *buf, unsigned int writecnt) > #else > ssize_t tmp = 0; > #endif > + unsigned int empty_writes = 250; /* results in a ca. 125ms timeout */ > > while (writecnt > 0) { > #ifdef _WIN32 > @@ -273,9 +274,16 @@ int serialport_write(unsigned char *buf, unsigned int writecnt) > msg_perr("Serial port write error!\n"); > return 1; > } > - if (!tmp) > - msg_pdbg("Empty write\n"); > - writecnt -= tmp; > + if (!tmp) { > + msg_pdbg2("Empty write\n"); > + empty_writes--; > + programmer_delay(500); > + if (empty_writes == 0) { > + msg_perr("Serial port seems dead!\n"); > + return 1; > + } > + } > + writecnt -= tmp; > buf += tmp; > } > > -- > Kind regards, Stefan Tauner > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

[PATCH] Break endless loop in serialport_write().
by Stefan Tauner 29 Nov '12

29 Nov '12

serialport_write could loop endlessly when used with a seemingly valid port that does always return 0 on writes instead of an error. Give up after about 125 ms i.e. 250 tries with a period of 500 us. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- serial.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/serial.c b/serial.c index 7e47dcc..794763e 100644 --- a/serial.c +++ b/serial.c @@ -262,6 +262,7 @@ int serialport_write(unsigned char *buf, unsigned int writecnt) #else ssize_t tmp = 0; #endif + unsigned int empty_writes = 250; /* results in a ca. 125ms timeout */ while (writecnt > 0) { #ifdef _WIN32 @@ -273,9 +274,16 @@ int serialport_write(unsigned char *buf, unsigned int writecnt) msg_perr("Serial port write error!\n"); return 1; } - if (!tmp) - msg_pdbg("Empty write\n"); - writecnt -= tmp; + if (!tmp) { + msg_pdbg2("Empty write\n"); + empty_writes--; + programmer_delay(500); + if (empty_writes == 0) { + msg_perr("Serial port seems dead!\n"); + return 1; + } + } + writecnt -= tmp; buf += tmp; } -- Kind regards, Stefan Tauner

1 0

dump of flashrom -V of a Clevo P170EMx
by EyEofHorus DiProDiGy 29 Nov '12

29 Nov '12

Hi everyone... Here is a dump of "flashrom -V" in a Clevo P170EMx laptop... http://paste.debian.net/213281/ Any further information you might need, please don't hesitate in replying to this email... Best regards... PsySc0rpi0n

1 0

Re: [flashrom] MX25L1605DM2I-12G with Buspirate
by Idwer Vollering 29 Nov '12

29 Nov '12

2012/11/29 Daniel . <phl3ckz(a)googlemail.com>: > Hi everyone, > > I am absolute beginner but I need to read and write the above mentioned > serial Flash memory. > > This is a BIOS chip and had a bad flash. Now it is unsoldered from > mainboard. How do you connect the buspirate to the chip and what is the chip's form factor (e.g. soic8)? The datasheet mentions SOP/WSON/PDIP. > I want read it out and reflash a new BIOS file. > > Therefore I really need help how to connect the chip pins with the buspirate > pins in a correct way. > > This is how pins are shown in the data sheet of Macronix MX25L1605DM2I-12G > > CS# 1 8 VCC > SO/SIO1 2 7 HOLD# > WP#ACC 3 6 SCLK > GND 4 5 SI/SIO0 http://dangerousprototypes.com/docs/Bus_Pirate_I/O_Pin_Descriptions This is how I connect my buspirate to a MX25L1605A soic8 chip: CS# (CS) [1 8] VCC (bridge with buspirate pin 3+7) SO (MISO) [2 7] HOLD # (+3V3) WP# (bridge with buspirate pin 7+8) [3 6] SCLK (CLK) GND (GND) [4 5] SI (MOSI) > > I am using Bus Pirate v3.5 with FW v6.2-beta1 r1981 BL v4.4 and flashrom > v0.9.6.1-r1624 on Windows. HiZ>i Bus Pirate v3.a Firmware v6.2-beta1 r1981 Bootloader v4.4 > > Would I have to setup the buspirate in a terminal before using flashrom? I > mean SPI mode and so on? If yes could someone help me with this settings > too? It's not necessary to change modes (no need to change from HiZ to SPI). > > Thanks! > > Best regards, > Daniel > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

MX25L1605DM2I-12G with Buspirate
by Daniel . 29 Nov '12

29 Nov '12

Hi everyone, I am absolute beginner but I need to read and write the above mentioned serial Flash memory. This is a BIOS chip and had a bad flash. Now it is unsoldered from mainboard. I want read it out and reflash a new BIOS file. Therefore I really need help how to connect the chip pins with the buspirate pins in a correct way. This is how pins are shown in the data sheet of Macronix MX25L1605DM2I-12G CS# 1 8 VCC SO/SIO1 2 7 HOLD# WP#ACC 3 6 SCLK GND 4 5 SI/SIO0 I am using Bus Pirate v3.5 with FW v6.2-beta1 r1981 BL v4.4 and flashrom v0.9.6.1-r1624 on Windows. Would I have to setup the buspirate in a terminal before using flashrom? I mean SPI mode and so on? If yes could someone help me with this settings too? Thanks! Best regards, Daniel

1 0

GA-M720-US3 (rev. 1.1) flashrom -V
by UnbAs.Foro 28 Nov '12

28 Nov '12

Hi! Thanks for your sotfware. I upload my results of -V and my -w Thanks!!

1 0

Supermicro X9DRW
by lesovsky 27 Nov '12

27 Nov '12

# flashrom -VV -p internal -r backup.bin flashrom v0.9.6-r1559 on Linux 3.4.9-gentoo-h64-tesla-a (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with unknown PCI library, GCC 4.5.4, big endian Command line (5 args): flashrom -VV -p internal -r backup.bin Calibrating delay loop... OS timer resolution is 1 usecs, 1997M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = 10004 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Supermicro" DMI string system-product-name: "X9DRW" DMI string system-version: "0123456789" DMI string baseboard-manufacturer: "Supermicro" DMI string baseboard-product-name: "X9DRW" DMI string baseboard-version: "0123456789" DMI string chassis-type: "Desktop" Found chipset "Intel X79" with PCI ID 8086:1d41. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x8 Root Complex Register Block address = 0xfed1c000 GCS = 0xc20: 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 OP Type Pre-OP op[0]: 0x02, write w/ addr, none op[1]: 0x03, read w/ addr, none op[2]: 0xd8, write w/ addr, none op[3]: 0x05, read w/o addr, none op[4]: 0x90, read w/ addr, none op[5]: 0x01, write w/o addr, none op[6]: 0x9f, read w/o addr, none op[7]: 0xc7, write w/o addr, none Pre-OP 0: 0x06, Pre-OP 1: 0x50 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x08: 0x00020000 (FADDR) 0x50: 0x00001a1b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x1a, BRRA 0x1b 0x54: 0x000f0000 FREG0: WARNING: Flash Descriptor region (0x00000000-0x0000ffff) is read-only. 0x58: 0x0fff0400 FREG1: BIOS region (0x00400000-0x00ffffff) is read-write. 0x5C: 0x03ff0020 FREG2: WARNING: Management Engine region (0x00020000-0x003fffff) is locked. 0x60: 0x00000fff FREG3: Gigabit Ethernet region is unused. 0x64: 0x001f0010 FREG4: Platform Data region (0x00010000-0x0001ffff) is read-write. 0x74: 0x00000000 (PR0 is unused) 0x78: 0x00000000 (PR1 is unused) 0x7C: 0x00000000 (PR2 is unused) 0x80: 0x00000000 (PR3 is unused) 0x84: 0x00000000 (PR4 is unused) 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: 0x84 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf80000 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00002005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x00000000 (FPB) Reading flash descriptors mapped by the chipset via FDOC/FDOD... done. === Content Section === FLVALSIG 0x0ff0a55a FLMAP0 0x03040003 FLMAP1 0x12100206 FLMAP2 0x00210020 --- Details --- NR (Number of Regions): 4 FRBA (Flash Region Base Address): 0x040 NC (Number of Components): 1 FCBA (Flash Component Base Address): 0x030 ISL (ICH/PCH Strap Length): 18 FISBA/FPSBA (Flash ICH/PCH Strap Base Address): 0x100 NM (Number of Masters): 3 FMBA (Flash Master Base Address): 0x060 MSL/PSL (MCH/PROC Strap Length): 0 FMSBA (Flash MCH/PROC Strap Base Address): 0x200 === Component Section === FLCOMP 0x24900025 FLILL 0x00000000 --- Details --- Component 1 density: 16 MB Component 2 is not used. Read Clock Frequency: 20 MHz Read ID and Status Clock Freq.: 50 MHz Write and Erase Clock Freq.: 50 MHz Fast Read is supported. Fast Read Clock Frequency: 50 MHz No forbidden opcodes. === Region Section === FLREG0 0x000f0000 FLREG1 0x0fff0400 FLREG2 0x03ff0020 FLREG3 0x00000fff FLREG4 0x001f0010 --- Details --- Region 0 (Descr.) 0x00000000 - 0x0000ffff Region 1 (BIOS ) 0x00400000 - 0x00ffffff Region 2 (ME ) 0x00020000 - 0x003fffff Region 3 (GbE ) is unused. Region 4 (Platf.) 0x00010000 - 0x0001ffff === Master Section === FLMSTR1 0x1a1b0000 FLMSTR2 0x04050000 FLMSTR3 0x08090118 --- Details --- Descr. BIOS ME GbE Platf. BIOS r rw rw rw ME r rw GbE r rw 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 0xba18 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for GigaDevice GD25Q20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for GigaDevice GD25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for GigaDevice GD25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for GigaDevice GD25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for GigaDevice GD25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for GigaDevice GD25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for GigaDevice GD25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Numonyx N25Q064, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 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 0xff, id2 0xff Probing for SST SST25LF080A, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 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 0xba18 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 0xba18 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 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 0xba18 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 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 SFDP revision = 1.0 SFDP number of parameter headers is 1 (NPH = 0). SFDP parameter table header 0/0: ID 0x00, version 1.0 Length 36 B, Parameter Table Pointer 0x000030 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 16384 kB. Block eraser 0: 4096 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 4096 x 4096 B with opcode 0x20. Block eraser 1: 256 x 65536 B with opcode 0xd8 done. === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter (if needed)]' Thanks for your help! === Found Unknown flash chip "SFDP-capable chip" (16384 kB, SPI) at physical address 0x0. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba18 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 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 Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 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 SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 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 W39V040FC, 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 W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Unknown flash chip "SFDP-capable chip" (16384 kB, SPI). Reading flash... Transaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=63, SME=0, SCF=0 Running OPCODE 0x03 failed at address 0x020000 (payload length was 64). Read operation failed! FAILED. Restoring MMIO space at 0x7f96b19158a0 Restoring MMIO space at 0x7f96b191589c Restoring MMIO space at 0x7f96b1915898 Restoring MMIO space at 0x7f96b1915896 Restoring MMIO space at 0x7f96b1915894 Restoring PCI config space for 00:1f:0 reg 0xdc -- С уважением Алексей В. Лесовский отдел разработки ПО, ИД Абак-Пресс

2 3

[PATCH 3/3] Fix sp_openserport users on Windows.
by Stefan Tauner 26 Nov '12

26 Nov '12

Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- buspirate_spi.c | 2 +- pony_spi.c | 2 +- serprog.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/buspirate_spi.c b/buspirate_spi.c index 92d7fb4..55d4133 100644 --- a/buspirate_spi.c +++ b/buspirate_spi.c @@ -40,7 +40,7 @@ static int buspirate_serialport_setup(char *dev) { /* 115200bps, 8 databits, no parity, 1 stopbit */ sp_fd = sp_openserport(dev, 115200); - if (sp_fd < 0) + if (sp_fd == SER_INV_FD) return 1; return 0; } diff --git a/pony_spi.c b/pony_spi.c index 7875200..101751f 100644 --- a/pony_spi.c +++ b/pony_spi.c @@ -116,7 +116,7 @@ int pony_spi_init(void) arg = extract_programmer_param("dev"); if (arg && strlen(arg)) { sp_fd = sp_openserport(arg, 9600); - if (sp_fd < 0) { + if (sp_fd == SER_INV_FD) { free(arg); return 1; } diff --git a/serprog.c b/serprog.c index edc5a7b..98c839e 100644 --- a/serprog.c +++ b/serprog.c @@ -372,7 +372,7 @@ int serprog_init(void) } if (strlen(device)) { sp_fd = sp_openserport(device, atoi(baudport)); - if (sp_fd < 0) { + if (sp_fd == SER_INV_FD) { free(device); return 1; } -- Kind regards, Stefan Tauner

1 0

[PATCH 2/3] Break endless loop in serialport_write().
by Stefan Tauner 26 Nov '12

26 Nov '12

serialport_write could loop endlessly when used with a seemingly valid port that does always return 0 on writes instead of an error. Give up after 10k tries. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- serial.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/serial.c b/serial.c index 11a749c..a3cdefb 100644 --- a/serial.c +++ b/serial.c @@ -264,6 +264,7 @@ int serialport_write(unsigned char *buf, unsigned int writecnt) #else ssize_t tmp = 0; #endif + uint empty_writes = 10000; while (writecnt > 0) { #ifdef _WIN32 @@ -275,9 +276,15 @@ int serialport_write(unsigned char *buf, unsigned int writecnt) msg_perr("Serial port write error!\n"); return 1; } - if (!tmp) + if (!tmp) { msg_pdbg("Empty write\n"); - writecnt -= tmp; + empty_writes--; + if (empty_writes == 0) { + msg_perr("Serial port seems dead!\n"); + return 1; + } + } + writecnt -= tmp; buf += tmp; } -- Kind regards, Stefan Tauner

1 0

[PATCH 1/3] Fix error message in sp_openserport().
by Stefan Tauner 26 Nov '12

26 Nov '12

free seems to touch errno on windows...? Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- serial.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/serial.c b/serial.c index 7e47dcc..11a749c 100644 --- a/serial.c +++ b/serial.c @@ -109,6 +109,7 @@ fdtype sp_openserport(char *dev, unsigned int baud) #ifdef _WIN32 HANDLE fd; char *dev2 = dev; + int err; if ((strlen(dev) > 3) && (tolower((unsigned char)dev[0]) == 'c') && (tolower((unsigned char)dev[1]) == 'o') && (tolower((unsigned char)dev[2]) == 'm')) { @@ -122,10 +123,11 @@ fdtype sp_openserport(char *dev, unsigned int baud) } fd = CreateFile(dev2, GENERIC_READ | GENERIC_WRITE, 0, NULL, OPEN_EXISTING, 0, NULL); + err = errno; // free may change errno if (dev2 != dev) free(dev2); if (fd == INVALID_HANDLE_VALUE) { - msg_perr("Error: cannot open serial port: %s\n", strerror(errno)); + msg_perr("Error: cannot open serial port: %s\n", strerror(err)); return SER_INV_FD; } DCB dcb; -- Kind regards, Stefan Tauner

1 0

[PATCH 0/3] serial woes
by Stefan Tauner 26 Nov '12

26 Nov '12

Idwer noticed a few problems... these patches try to fix them. Idwer please try one at the time and report if they work as intended: the first one should fix the "no error" message, the second one should stop the loop after 10k tries, the third one should fix the underlying problem for good. Stefan Tauner (3): Fix error message in sp_openserport(). Break endless loop in serialport_write(). Fix sp_openserport users on Windows. buspirate_spi.c | 2 +- pony_spi.c | 2 +- serial.c | 15 ++++++++++++--- serprog.c | 2 +- 4 files changed, 15 insertions(+), 6 deletions(-) -- Kind regards, Stefan Tauner

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom