- flashrom - mail.coreboot.org

Support for MX29F001T/B
by Marko Kraljevic 21 Aug '09

21 Aug '09

Hi, I've added support for MX29F001T/B. I'm not sure the proper way to submit a patch, I've just joined the mailing list recently. I've only got the -T type, but I just tested it and it works with them. The attached files are the patch, the additional .c file (based on mx29f002.c, modified based on datasheet for mx29f001. The trial.txt is output of probe, read, erase, write on the MX29F001T. I compiled and tested this all on an old Soyo SY-6BB [440BX, PIIX4]; It still boots after a read, erase, blank check, write... So it must have worked ;) Hopefully I'm doing this the right way! Let me know if I'm not. Mark ** Probe flashrom v0.9.0-r694 No coreboot table found. Found chipset "Intel PIIX4/4E/4M", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... 299M loops per second, 100 myus = 349 us. OK. Probing for AMD Am29F010A/B, 128 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F080B, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ASD AE49F2008, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT25DF021, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF041A, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF081, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321A, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF641, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25F512B, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF041, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF081A, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26F004, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT29C512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT45CS1282, 16896 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB011D, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB021D, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB041D, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB081D, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB161D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321C, 4224 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB642D, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT49BV512, 64 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N), 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMIC A25L40P, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMIC A49LF040A, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EMST F49B002UA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Eon EN25B05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25D16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON EN29F002(A)(N)B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EON EN29F002(A)(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004BC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004TC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Intel 28F001BX-B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 28F001BX-T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for Macronix MX25L512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1005, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L2005, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L4005, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L8005, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1605, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1635D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3205, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3235D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L6405, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L12805, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX29F001T, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Found chip "Macronix MX29F001T" (128 KB, Parallel) at physical address 0xfffe0000. Probing for Macronix MX29F001B, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29LV040, 512 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Numonyx M25PE10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE40, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV020, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm29F0002T, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm29F0002B, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm39LV010, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL002, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL004, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0x25, id2 0x9a Probing for Spansion S25FL016A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF032B, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x25, id2 0x9a Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29EE020A, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF002A/B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF003A/B, 384 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004A/B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for SST SST49LF008A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P05.RES, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10-A, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10.RES, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40-old, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P128, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M29F002B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F002T/NT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for ST M29W010B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29W040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for ST M50LPW116, 2048 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS S29C31004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51001T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51002T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W25x10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W29C011, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29EE011, 128 KB: Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xc2, id2 0x18 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49F002U, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002FA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON unknown EON SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST unknown SST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST unknown ST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE 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, -rV, -wV, -EV), and mention which mainboard you tested. Thanks for your help! === No operations were specified. ** Read flashrom v0.9.0-r694 No coreboot table found. Found chipset "Intel PIIX4/4E/4M", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... 298M loops per second, 100 myus = 348 us. OK. Probing for AMD Am29F010A/B, 128 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F080B, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ASD AE49F2008, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT25DF021, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF041A, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF081, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321A, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF641, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25F512B, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF041, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF081A, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26F004, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT29C512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT45CS1282, 16896 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB011D, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB021D, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB041D, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB081D, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB161D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321C, 4224 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB642D, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT49BV512, 64 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N), 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMIC A25L40P, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMIC A49LF040A, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EMST F49B002UA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Eon EN25B05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25D16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON EN29F002(A)(N)B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EON EN29F002(A)(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004BC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004TC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Intel 28F001BX-B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 28F001BX-T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for Macronix MX25L512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1005, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L2005, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L4005, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L8005, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1605, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1635D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3205, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3235D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L6405, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L12805, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX29F001T, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Found chip "Macronix MX29F001T" (128 KB, Parallel) at physical address 0xfffe0000. Probing for Macronix MX29F001B, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29LV040, 512 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Numonyx M25PE10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE40, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV020, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm29F0002T, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm29F0002B, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm39LV010, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL002, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL004, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0x25, id2 0x9a Probing for Spansion S25FL016A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF032B, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x25, id2 0x9a Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29EE020A, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF002A/B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF003A/B, 384 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004A/B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for SST SST49LF008A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P05.RES, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10-A, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10.RES, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40-old, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P128, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M29F002B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F002T/NT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for ST M29W010B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29W040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for ST M50LPW116, 2048 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS S29C31004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51001T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51002T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W25x10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W29C011, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29EE011, 128 KB: Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xc2, id2 0x18 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49F002U, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002FA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON unknown EON SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST unknown SST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST unknown ST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE 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, -rV, -wV, -EV), and mention which mainboard you tested. Thanks for your help! === Reading flash... done. ** Erase flashrom v0.9.0-r694 No coreboot table found. Found chipset "Intel PIIX4/4E/4M", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... 299M loops per second, 100 myus = 349 us. OK. Probing for AMD Am29F010A/B, 128 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F080B, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ASD AE49F2008, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT25DF021, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF041A, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF081, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321A, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF641, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25F512B, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF041, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF081A, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26F004, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT29C512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT45CS1282, 16896 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB011D, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB021D, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB041D, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB081D, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB161D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321C, 4224 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB642D, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT49BV512, 64 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N), 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMIC A25L40P, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMIC A49LF040A, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EMST F49B002UA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Eon EN25B05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25D16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON EN29F002(A)(N)B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EON EN29F002(A)(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004BC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004TC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Intel 28F001BX-B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 28F001BX-T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Macronix MX25L512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1005, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L2005, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L4005, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L8005, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1605, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1635D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3205, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3235D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L6405, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L12805, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX29F001T, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Found chip "Macronix MX29F001T" (128 KB, Parallel) at physical address 0xfffe0000. Probing for Macronix MX29F001B, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29LV040, 512 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Numonyx M25PE10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE40, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV020, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm29F0002T, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm29F0002B, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm39LV010, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL002, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL004, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff Probing for Spansion S25FL016A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF032B, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xff, id2 0xff Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29EE020A, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF002A/B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF003A/B, 384 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004A/B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF008A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P05.RES, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10-A, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10.RES, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40-old, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P128, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M29F002B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F002T/NT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for ST M29W010B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29W040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50LPW116, 2048 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS S29C31004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51001T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51002T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W25x10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W29C011, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29EE011, 128 KB: Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xc2, id2 0x18 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49F002U, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002FA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON unknown EON SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST unknown SST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST unknown ST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE 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, -rV, -wV, -EV), and mention which mainboard you tested. Thanks for your help! === Erasing flash chip... SUCCESS. **write flashrom v0.9.0-r694 No coreboot table found. Found chipset "Intel PIIX4/4E/4M", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... 299M loops per second, 100 myus = 349 us. OK. Probing for AMD Am29F010A/B, 128 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F002(N)BT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29F080B, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ASD AE49F2008, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT25DF021, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF041A, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF081, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF321A, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25DF641, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25F512B, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT25FS040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF041, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF081A, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26DF161A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT26F004, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT29C512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT45CS1282, 16896 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB011D, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB021D, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB041D, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB081D, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB161D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321C, 4224 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB321D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT45DB642D, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Atmel AT49BV512, 64 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N), 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Atmel AT49F002(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for AMIC A25L40P, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for AMIC A49LF040A, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EMST F49B002UA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Eon EN25B05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25B64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25D16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F05, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Eon EN25F32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON EN29F002(A)(N)B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for EON EN29F002(A)(N)T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004BC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F004TC, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Intel 28F001BX-B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 28F001BX-T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for Macronix MX25L512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1005, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L2005, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L4005, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L8005, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1605, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L1635D, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3205, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L3235D, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L6405, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX25L12805, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix MX29F001T, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Found chip "Macronix MX29F001T" (128 KB, Parallel) at physical address 0xfffe0000. Probing for Macronix MX29F001B, 128 KB: probe_29f001: id1 0xc2, id2 0x18 Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Macronix MX29LV040, 512 KB: probe_29f002: id1 0xc2, id2 0x18 Probing for Numonyx M25PE10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE40, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Numonyx M25PE16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV010, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV020, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV040, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm25LV512, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC Pm29F0002T, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm29F0002B, 256 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for PMC Pm39LV010, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL002, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for PMC Pm49FL004, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0x25, id2 0x9a Probing for Spansion S25FL016A, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF016B, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF032B, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST25VF080B, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x25, id2 0x9a Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29EE020A, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF002A/B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF003A/B, 384 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004A/B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for SST SST49LF008A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF080A, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P05.RES, 64 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10-A, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P10.RES, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P40-old, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P32, 4096 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P64, 8192 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M25P128, 16384 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST M29F002B, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F002T/NT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xc2, id2 0x18 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for ST M29W010B, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M29W040B, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xc2, id2 0x18 Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x25, id2 0x9a Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x25, id2 0x9a Probing for ST M50LPW116, 2048 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS S29C31004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51001T, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51002T, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for SyncMOS S29C51004T, 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RB, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for TI TMS29F002RT, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W25x10, 128 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x20, 256 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x40, 512 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x80, 1024 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W25x16, 2048 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Winbond W29C011, 128 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W29EE011, 128 KB: Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xc2, id2 0x18 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49F002U, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W49V002FA, 256 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: id1 0xc2, id2 0x18 Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for EON unknown EON SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for SST unknown SST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. Probing for ST unknown ST SPI chip, 0 KB: skipped. Host bus type Non-SPI and chip bus type SPI are incompatible. === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE 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, -rV, -wV, -EV), and mention which mainboard you tested. Thanks for your help! === Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... Programming page: address: 0x00000000address: 0x00001000address: 0x00002000address: 0x00003000address: 0x00004000address: 0x00005000address: 0x00006000address: 0x00007000address: 0x00008000address: 0x00009000address: 0x0000a000address: 0x0000b000address: 0x0000c000address: 0x0000d000address: 0x0000e000address: 0x0000f000address: 0x00010000address: 0x00011000address: 0x00012000address: 0x00013000address: 0x00014000address: 0x00015000address: 0x00016000address: 0x00017000address: 0x00018000address: 0x00019000address: 0x0001a000address: 0x0001b000address: 0x0001c000address: 0x0001d000address: 0x0001e000address: 0x0001f000 COMPLETE. Verifying flash... VERIFIED.

2 4

Re: [flashrom] [commit] r695 - trunk
by Stefan Reinauer 20 Aug '09

20 Aug '09

Uwe, do you have some mechanism to check these URLs if they still make sense? It's very likely that the URLs change, while we're not having a new, fixed version out, or that we don't notice when a vendor renames or removes URLs. I think we should refrain from using URLs to vendor sites in our software like this. For actuality, and for legal reasons. just my 2ct Stefan > { "Abit", "IS-10", "http://www.abit.com.tw/page/en/motherboard/motherboard_detail.php?pMODEL_NA…" }, > + { "ASRock", "K7VT4A+", "http://www.asrock.com/mb/overview.asp?Model=K7VT4A%%2b&s=" }, > + { "ASUS", "A7V600-X", "http://www.asus.com/product.aspx?P_ID=L2XYS0rmtCjeOr4k" }, > + { "ASUS", "M2N68", "http://www.asus.com/product.aspx?P_ID=iDZQ9yNK2CbKW6Zv"}, > { "ASUS", "M3N78 Pro", "http://www.asus.com/product.aspx?P_ID=DVvm9CU0G1bCC4gp" }, > { "ASUS", "MEW-AM", "ftp://ftp.asus.com.tw/pub/ASUS/mb/sock370/810/mew-am/" }, > { "ASUS", "MEW-VM", "http://www.elhvb.com/mboards/OEM/HP/manual/ASUS%20MEW-VM.htm" }, > > -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866

2 1

successful_crossflashing_S2466
by Oliver 20 Aug '09

20 Aug '09

Hi! After i had problems flashing a SST 49LF004B on an asus m2npv-vm my last chance was a Tyan Tiger S2466 board which i haven't tried so far. Because this board is not listed here: > http://www.coreboot.org/Flashrom#Supported_mainboards I want you to know that this board works fine out of the box with the latest flashrom release (r669). Feel free to add this board now to the supported_mainboard list The original chip used in this board is a Winbond W49V002AP. > root@security:~/flashrom# ./flashrom -w 1805.BIN > flashrom v0.9.0-r669 > No coreboot table found. > Found chipset "AMD AMD-768", enabling flash write... OK. > This chipset supports the following protocols: Non-SPI. > Calibrating delay loop... OK. > Found chip "SST SST49LF004A/B" (512 KB, FWH) at physical address 0xfff80000. > Flash image seems to be a legacy BIOS. Disabling checks. > Writing flash chip... Programming page: 0007 at address: 0x00070000 > COMPLETE. > Verifying flash... VERIFIED. > root@security:~/flashrom# Oliver -- The choice of an -----==- open Oliver Niesner ----==-- _ generation devil.homelinux.org ---==---(_)__ __ ____ __ oli[at]rhce[dot]servebbs[dot]net --==---/ / _ \/ // /\ \/ / -=====/_/_//_/\_,_/ /_/\_\

2 1

Re: [flashrom] [commit] r695 - trunk
by Carl-Daniel Hailfinger 20 Aug '09

20 Aug '09

On 20.08.2009 20:45, svn(a)flashrom.org wrote: > Author: uwe > New Revision: 695 > > Mark the following boards as non-working for now: > > - ASRock K7VT4A+ (reported by Udu Ogah <putlinuxonit(a)gmail.com>) > Chipset detect, but no chip. > Needs board enable. It's so old that it has parallel flash which sometimes needs the write line enabled to respond to ID commands. > - ASUS M2N68 (reported by Udu Ogah <putlinuxonit(a)gmail.com>) > Chipset detect, but no chip. > Needs nForce SPI support, so it's not a board problem. Please remove again. Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

[commit] r695 - trunk
by svn＠flashrom.org 20 Aug '09

20 Aug '09

Author: uwe Date: 2009-08-20 20:45:18 +0200 (Thu, 20 Aug 2009) New Revision: 695 Modified: trunk/board_enable.c trunk/print.c Log: Various board status updates (trivial). Mark the following boards as OK (no board-enable needed): - Tyan S2466 (reported by Oliver Niesner <oli(a)servebbs.net>) http://www.flashrom.org/pipermail/flashrom/2009-August/000211.html Mark the following boards as non-working for now: - ASRock K7VT4A+ (reported by Udu Ogah <putlinuxonit(a)gmail.com>) Chipset detect, but no chip. - ASUS M2N68 (reported by Udu Ogah <putlinuxonit(a)gmail.com>) Chipset detect, but no chip. - ASUS A7V600-X (reported by Udu Ogah <putlinuxonit(a)gmail.com>) Chipset and chip detected, writes don't work. Board-enable required. Also, add some missing board URLs and fix incorrect board names. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/board_enable.c =================================================================== --- trunk/board_enable.c 2009-08-19 15:19:18 UTC (rev 694) +++ trunk/board_enable.c 2009-08-20 18:45:18 UTC (rev 695) @@ -637,7 +637,7 @@ } /** - * Suited for A-Open vKM400 AM-S: VIA KM400 + VT8237 + IT8705F. + * Suited for AOpen vKM400Am-S: VIA KM400 + VT8237 + IT8705F. */ static int board_aopen_vkm400(const char *name) { @@ -866,7 +866,7 @@ } /** - * Suited for Asus P4P800-E: Intel Intel 865PE + ICH5R. + * Suited for Asus P4P800-E Deluxe: Intel Intel 865PE + ICH5R. */ static int board_asus_p4p800(const char *name) { @@ -918,7 +918,7 @@ {0x8086, 0x1130, 0, 0, 0x105a, 0x0d30, 0x105a, 0x4d33, "acorp", "6a815epd", "Acorp", "6A815EPD", board_acorp_6a815epd}, {0x1022, 0x746B, 0x1022, 0x36C0, 0, 0, 0, 0, "AGAMI", "ARUMA", "agami", "Aruma", w83627hf_gpio24_raise_2e}, {0x1106, 0x3177, 0x17F2, 0x3177, 0x1106, 0x3148, 0x17F2, 0x3148, NULL, NULL, "Albatron", "PM266A*", board_epox_ep_8k5a2}, - {0x1106, 0x3205, 0x1106, 0x3205, 0x10EC, 0x8139, 0xA0A0, 0x0477, NULL, NULL, "AOpen", "vKM400 AM-s", board_aopen_vkm400}, + {0x1106, 0x3205, 0x1106, 0x3205, 0x10EC, 0x8139, 0xA0A0, 0x0477, NULL, NULL, "AOpen", "vKM400Am-S", board_aopen_vkm400}, {0x1022, 0x2090, 0, 0, 0x1022, 0x2080, 0, 0, "artecgroup", "dbe61", "Artec Group", "DBE61", board_artecgroup_dbe6x}, {0x1022, 0x2090, 0, 0, 0x1022, 0x2080, 0, 0, "artecgroup", "dbe62", "Artec Group", "DBE62", board_artecgroup_dbe6x}, {0x1106, 0x3189, 0x1043, 0x807F, 0x1106, 0x3177, 0x1043, 0x808C, NULL, NULL, "ASUS", "A7V8X", board_asus_a7v8x}, @@ -1022,6 +1022,7 @@ { "T-Online", "S-100", }, { "Tyan", "iS5375-1U", }, { "Tyan", "S1846", }, + { "Tyan", "S2466", }, { "Tyan", "S2881", }, { "Tyan", "S2882", }, { "Tyan", "S2882-D", }, @@ -1054,6 +1055,9 @@ const struct board_info boards_bad[] = { /* Verified non-working boards (for now). */ { "Abit", "IS-10", }, + { "ASRock", "K7VT4A+", }, + { "ASUS", "A7V600-X", }, + { "ASUS", "M2N68", }, { "ASUS", "M3N78 Pro", }, { "ASUS", "MEW-AM", }, { "ASUS", "MEW-VM", }, Modified: trunk/print.c =================================================================== --- trunk/print.c 2009-08-19 15:19:18 UTC (rev 694) +++ trunk/print.c 2009-08-20 18:45:18 UTC (rev 695) @@ -351,6 +351,7 @@ { "T-Online", "S-100", "http://wiki.freifunk-hannover.de/T-Online_S_100" }, { "Tyan", "iS5375-1U", "http://www.tyan.com/product_board_detail.aspx?pid=610" }, { "Tyan", "S1846", "http://www.tyan.com/archive/products/html/tsunamiatx.html" }, + { "Tyan", "S2466", "http://www.tyan.com/product_board_detail.aspx?pid=461" }, { "Tyan", "S2881", "http://www.tyan.com/product_board_detail.aspx?pid=115" }, { "Tyan", "S2882", "http://www.tyan.com/product_board_detail.aspx?pid=121" }, { "Tyan", "S2882-D", "http://www.tyan.com/product_board_detail.aspx?pid=127" }, @@ -380,10 +381,12 @@ { "Acorp", "6A815EPD", "http://web.archive.org/web/20021206163652/www.acorp.com.tw/English/default.…" }, { "agami", "Aruma", "http://web.archive.org/web/20080212111524/http://www.agami.com/site/ais-600…" }, { "Albatron", "PM266A Pro", "http://www.albatron.com.tw/English/Product/MB/pro_detail.asp?rlink=Overview…" }, /* FIXME */ + { "AOpen", "vKM400Am-S", "http://usa.aopen.com/products_detail.aspx?Auno=824" }, { "Artec Group", "DBE61", "http://wiki.thincan.org/DBE61" }, { "Artec Group", "DBE62", "http://wiki.thincan.org/DBE62" }, { "ASUS", "A7V8X-MX SE", "http://www.asus.com/product.aspx?P_ID=1guVBT1qV5oqhHyZ" }, { "ASUS", "P4B266", "http://www.ciao.co.uk/ASUS_Intel_845D_Chipset_P4B266__5409807#productdetail" }, + { "ASUS", "P4P800-E Deluxe", "http://www.asus.com/product.aspx?P_ID=INIJUvLlif7LHp3g" }, { "ASUS", "P5A", "ftp://ftp.asus.com.tw/pub/ASUS/mb/sock7/ali/p5a/" }, { "Biostar", "P4M80-M4", "http://www.biostar-usa.com/mbdetails.asp?model=p4m80-m4" }, { "Elitegroup", "K7VTA3", "http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=264&…" }, @@ -420,6 +423,9 @@ /* Verified non-working boards (for now). */ { "Abit", "IS-10", "http://www.abit.com.tw/page/en/motherboard/motherboard_detail.php?pMODEL_NA…" }, + { "ASRock", "K7VT4A+", "http://www.asrock.com/mb/overview.asp?Model=K7VT4A%%2b&s=" }, + { "ASUS", "A7V600-X", "http://www.asus.com/product.aspx?P_ID=L2XYS0rmtCjeOr4k" }, + { "ASUS", "M2N68", "http://www.asus.com/product.aspx?P_ID=iDZQ9yNK2CbKW6Zv"}, { "ASUS", "M3N78 Pro", "http://www.asus.com/product.aspx?P_ID=DVvm9CU0G1bCC4gp" }, { "ASUS", "MEW-AM", "ftp://ftp.asus.com.tw/pub/ASUS/mb/sock370/810/mew-am/" }, { "ASUS", "MEW-VM", "http://www.elhvb.com/mboards/OEM/HP/manual/ASUS%20MEW-VM.htm" },

1 0

[PATCH] Documentation update
by Stefan Reinauer 20 Aug '09

20 Aug '09

See patch -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866

3 2

comprehensive dumps for the Asus A7v600-x
by Putlinuxonit 20 Aug '09

20 Aug '09

Hi Luc, Sorry i didn't include the #superiotool -dV output last time. here is everything in one file. Udu E. Ogah .~~~~~~~~~~.

1 0

[Patch] Board enable for Asus P4P800-E Deluxe.
by Luc Verhaegen 20 Aug '09

20 Aug '09

First time i successfully dug one out of an AMI Bios. int16h ax=0xE0 is indeed the ticket. This one has its int16h vector at the standard location it seems: 0xF000:0xE82E. Not sure how general this is for AMI. It does seem that i will require dumps of the F segment for this to work though. Luc Verhaegen.

4 3

"lspci -vvnnxx" and "superiotool -d" dumps from an Asus m2n68 motherboard needing a board enable
by Putlinuxonit 20 Aug '09

20 Aug '09

Hi All, This board has it's chipset detected but the eeprom flash chip isn't even though it's an MXIC25L8005 chip which is listed in "flashrom -L" Just thought i'll put up the dumps. Do let me know if you need further testing. Udu E. Ogah

1 0

Not sure where to put this?
by Marko Kraljevic 20 Aug '09

20 Aug '09

Hi, I'm new to the list. I've been playing with flashrom some, and it's great. Thanks for the work guys. I've put a ZIF socket on a 3com NIC, for external programming. It seems to be working great. I've taken a picture, maybe it would be useful for the wiki or something. I'm not a terribly good programmer, but I'm pretty good with hardware generally... I'm going to be doing some more hardware work in the future. I think I'll make an ISA card with 32 and 28pin ZIF, and PLCC socket, on the 440BX board I have, addr is off the ISA bus, so I'll just buffer that. Data seems to go to the superIO chip, so I'll have to have a cheater socket under the stock BIOS ROM to steal /CS D0:7, etc. I think I'll buffer all the lines on the card, so that the bus doesn't get fried in case of a fried chip or whatnot. It will be a sort of general purpose flashing board. I think I'll try and implement support for the older 27xxx EPROMs at some point, which shouldn't be too difficult I don't think? anyways, here's the picture if anyone wants it: http://electrontube.org/img/3com_prog.jpg Mark

2 3

Asus A7v600-X works with stable v0.9.0 but not with bleeding edge
by Putlinuxonit 20 Aug '09

20 Aug '09

Hi All, I'd like to report than an Asus A7V600-X with bios 1009 works with flashrom 0.9.0 stable. The stock version found on the latest stable realease of systemrescuecd 1.2.3. There are some caveats however... find below a few dumps for your review. root@sysresccd% ./flashrom *flashrom v0.9.0* No coreboot table found. *Found chipset "VIA VT8237"*, enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. *Found chip "PMC Pm49FL002" (256 KB, LPC,FWH)* at physical address 0xfffc0000. No operations were specified. The strange thing is that when i tried using the bleeding edge r694 i get the following root@sysresccd /root % ./flashrom -w fimrwarea7v600-x.old *flashrom v0.9.0-r694* No coreboot table found. Found chipset "VIA VT8237", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "PMC Pm49FL002" (256 KB, LPC,FWH) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... Programming page: ERASE FAILED at 0x00000000! Expected=0xff, Read=0x03, failed byte count from 0x00000000-0x00003fff: 0x33a6 ERASE FAILED! ERASE FAILED! FAILED! Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net channel #flashrom or mail flashrom(a)flashrom.org ------------------------------------------------------------ DO NOT REBOOT OR POWEROFF! i then use the stock 0.9.0 version to reprogramme and i get this root@sysresccd /root % flashrom -w fimrwarea7v600-x.old Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA VT8237", enabling flash write... OK. Found chip "PMC Pm49FL002" (256 KB) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Programming page: 0015 at address: 0x0003c000 i* verify if it's written ok* root@sysresccd /root % flashrom -v fimrwarea7v600-x.old Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA VT8237", enabling flash write... OK. Found chip "PMC Pm49FL002" (256 KB) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Verifying flash... VERIFIED. root@sysresccd /root % flashrom -R *flashrom v0.9.0* so basically, When i use the stock v0.9.0 to dump and write back the firmware on my A7v600-x, everything is fine. when i try to use the current svn. r694, it fails. i had to reflash with stable 0.9.0 after the r694 failed. I've successfully rebooted and verified no damage done to motherboard. interestingly, I downloaded the latest version of the bios (1009) off asus website, same version as i'm running and when i unzip it yeilds an *.awd ( i guess award) file. This file is supposed to be the same version as the one i'm running but when i try both stock v0.9.0 and r694 on it. they both fail. Beats me. maybe the awardflasher file format is different from what I get when i do* "flashrom -r firmware-old.bin"* * * I've also compared md5 checksums on both the firmware-old.bin and the one downloaded off the asus website but they both give different results even though they are meant to be the same version (1009). Anyway, hats-off to the devs for all the good work. idlogin -- Udu E. Ogah .~~~~~~~~~~. attachments I've attached flashrom -V dumps for both 0.9.0 and r694 latest Asus bios for A7v600-X

2 4

[RFC] flashrom 0.9.1
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

Hi, there are no more pending flashrom patches for 0.9.1 and I would like to release it today or tomorrow. Draft 0.9.1 announcement is at http://www.coreboot.org/Flashrom/0.9.1 . Please test! Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

[PATCH] Fix romentry layout for programmers
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

Flashrom has the ability to use layout files with romentries, but this feature was not adapted to the programmer infrastructure and had undefined behaviour for flasher!=internal. The romentry handling had an off-by-one error which caused all copies to end up one byte short. Fix these issues. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-romentries_programmer/flash.h =================================================================== --- flashrom-romentries_programmer/flash.h (Revision 692) +++ flashrom-romentries_programmer/flash.h (Arbeitskopie) @@ -422,7 +422,7 @@ int show_id(uint8_t *bios, int size, int force); int read_romlayout(char *name); int find_romentry(char *name); -int handle_romentries(uint8_t *buffer, uint8_t *content); +int handle_romentries(uint8_t *buffer, struct flashchip *flash); /* cbtable.c */ int coreboot_init(void); Index: flashrom-romentries_programmer/flashrom.c =================================================================== --- flashrom-romentries_programmer/flashrom.c (Revision 692) +++ flashrom-romentries_programmer/flashrom.c (Arbeitskopie) @@ -930,8 +930,7 @@ // This should be moved into each flash part's code to do it // cleanly. This does the job. - /* FIXME: Adapt to the external flasher infrastructure. */ - handle_romentries(buf, (uint8_t *) flash->virtual_memory); + handle_romentries(buf, flash); // //////////////////////////////////////////////////////////// Index: flashrom-romentries_programmer/layout.c =================================================================== --- flashrom-romentries_programmer/layout.c (Revision 692) +++ flashrom-romentries_programmer/layout.c (Arbeitskopie) @@ -196,11 +196,11 @@ return -1; } -int handle_romentries(uint8_t *buffer, uint8_t *content) +int handle_romentries(uint8_t *buffer, struct flashchip *flash) { int i; - // This function does not safe flash write cycles. + // This function does not save flash write cycles. // // Also it does not cope with overlapping rom layout // sections. @@ -220,10 +220,9 @@ if (rom_entries[i].included) continue; - /* FIXME: Adapt to the external flasher infrastructure. */ - memcpy(buffer + rom_entries[i].start, - content + rom_entries[i].start, - rom_entries[i].end - rom_entries[i].start); + flash->read(flash, buffer + rom_entries[i].start, + rom_entries[i].start, + rom_entries[i].end - rom_entries[i].start + 1); } return 0; -- http://www.hailfinger.org/

2 2

[commit] r694 - trunk
by svn＠flashrom.org 19 Aug '09

19 Aug '09

Author: hailfinger Date: 2009-08-19 17:19:18 +0200 (Wed, 19 Aug 2009) New Revision: 694 Modified: trunk/flash.h trunk/flashrom.c trunk/layout.c Log: Flashrom has the ability to use layout files with romentries, but this feature was not adapted to the programmer infrastructure and had undefined behaviour for flasher!=internal. The romentry handling had an off-by-one error which caused all copies to end up one byte short. Fix these issues. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/flash.h =================================================================== --- trunk/flash.h 2009-08-19 15:03:28 UTC (rev 693) +++ trunk/flash.h 2009-08-19 15:19:18 UTC (rev 694) @@ -422,7 +422,7 @@ int show_id(uint8_t *bios, int size, int force); int read_romlayout(char *name); int find_romentry(char *name); -int handle_romentries(uint8_t *buffer, uint8_t *content); +int handle_romentries(uint8_t *buffer, struct flashchip *flash); /* cbtable.c */ int coreboot_init(void); Modified: trunk/flashrom.c =================================================================== --- trunk/flashrom.c 2009-08-19 15:03:28 UTC (rev 693) +++ trunk/flashrom.c 2009-08-19 15:19:18 UTC (rev 694) @@ -930,8 +930,7 @@ // This should be moved into each flash part's code to do it // cleanly. This does the job. - /* FIXME: Adapt to the external flasher infrastructure. */ - handle_romentries(buf, (uint8_t *) flash->virtual_memory); + handle_romentries(buf, flash); // //////////////////////////////////////////////////////////// Modified: trunk/layout.c =================================================================== --- trunk/layout.c 2009-08-19 15:03:28 UTC (rev 693) +++ trunk/layout.c 2009-08-19 15:19:18 UTC (rev 694) @@ -196,11 +196,11 @@ return -1; } -int handle_romentries(uint8_t *buffer, uint8_t *content) +int handle_romentries(uint8_t *buffer, struct flashchip *flash) { int i; - // This function does not safe flash write cycles. + // This function does not save flash write cycles. // // Also it does not cope with overlapping rom layout // sections. @@ -220,10 +220,9 @@ if (rom_entries[i].included) continue; - /* FIXME: Adapt to the external flasher infrastructure. */ - memcpy(buffer + rom_entries[i].start, - content + rom_entries[i].start, - rom_entries[i].end - rom_entries[i].start); + flash->read(flash, buffer + rom_entries[i].start, + rom_entries[i].start, + rom_entries[i].end - rom_entries[i].start + 1); } return 0;

1 0

[PATCH] Use : instead of = for programmer parameters
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

Current programmer parameter syntax is -p programmer=parameter Unfortunately, many parameters are of the form variable=val, so we get commandlines like this: flashrom -p it87spi=port=0x820 and this looks horrible. Using : instead of = would make such parameters look better: flashrom -p it87spi:port=0x820 As a side benefit, this patch mentions the programmer name in the error message if it is unknown. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-programmer_param_colon/flashrom.8 =================================================================== --- flashrom-programmer_param_colon/flashrom.8 (Revision 692) +++ flashrom-programmer_param_colon/flashrom.8 (Arbeitskopie) @@ -150,7 +150,7 @@ .sp The dummy programmer has an optional parameter specifying the bus types it should support. For that you have to use the -.B "flashrom -p dummy=type" +.B "flashrom -p dummy:type" syntax where .B type can be any comma-separated combination of @@ -158,11 +158,11 @@ in any order. .sp Example: -.B "flashrom -p dummy=lpc,fwh" +.B "flashrom -p dummy:lpc,fwh" .sp If you have multiple supported PCI cards which can program flash chips (NICs, SATA/IDE controllers, etc.) in your system, you must use the -.B "flashrom -p xxxx=bb:dd.f" +.B "flashrom -p xxxx:bb:dd.f" syntax to explicitly select one of them, where .B xxxx is the name of the programmer @@ -174,7 +174,7 @@ is the PCI function number of the desired NIC. .sp Example: -.B "flashrom -p nic3com=05:04.0" +.B "flashrom -p nic3com:05:04.0" .sp Currently the following programmers support this mechanism: .BR nic3com , @@ -183,14 +183,14 @@ The it87spi programmer has an optional parameter which will set the I/O base port of the IT87* SPI controller interface to the port specified in the parameter. For that you have to use the -.B "flashrom -p it87spi=port=portnum" +.B "flashrom -p it87spi:port=portnum" syntax where .B portnum is an I/O port number which must be a multiple of 8. .sp The ft2232spi programmer has an optional parameter specifying the controller type and interface/port it should support. For that you have to use the -.B "flashrom -p ft2232spi=model,port=interface" +.B "flashrom -p ft2232spi:model,port=interface" syntax where .B model can be any of @@ -208,9 +208,9 @@ The serprog programmer has an optional parameter specifying either a serial device/baud combination or an IP/port combination for communication with the programmer. For serial, you have to use the -.B "flashrom -p serprog=/dev/device:baud" +.B "flashrom -p serprog:/dev/device:baud" syntax and for IP, you have to use -.B "flashrom -p serprog=ip:port" +.B "flashrom -p serprog:ip:port" instead. More information about serprog is available in serprog-protocol.txt in the source distribution. .sp Index: flashrom-programmer_param_colon/flashrom.c =================================================================== --- flashrom-programmer_param_colon/flashrom.c (Revision 692) +++ flashrom-programmer_param_colon/flashrom.c (Arbeitskopie) @@ -708,7 +708,7 @@ namelen = strlen(name); if (strncmp(optarg, name, namelen) == 0) { switch (optarg[namelen]) { - case '=': + case ':': programmer_param = strdup(optarg + namelen + 1); break; case '\0': @@ -725,7 +725,7 @@ } } if (programmer == PROGRAMMER_INVALID) { - printf("Error: Unknown programmer.\n"); + printf("Error: Unknown programmer %s.\n", optarg); exit(1); } break; -- http://www.hailfinger.org/

2 2

[commit] r693 - trunk
by svn＠flashrom.org 19 Aug '09

19 Aug '09

Author: hailfinger Date: 2009-08-19 17:03:28 +0200 (Wed, 19 Aug 2009) New Revision: 693 Modified: trunk/flashrom.8 trunk/flashrom.c Log: Current programmer parameter syntax is -p programmer=parameter Unfortunately, many parameters are of the form variable=val, so we get commandlines like this: flashrom -p it87spi=port=0x820 and this looks horrible. Using : instead of = would make such parameters look better: flashrom -p it87spi:port=0x820 As a side benefit, this patch mentions the programmer name in the error message if it is unknown. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/flashrom.8 =================================================================== --- trunk/flashrom.8 2009-08-19 13:55:34 UTC (rev 692) +++ trunk/flashrom.8 2009-08-19 15:03:28 UTC (rev 693) @@ -150,7 +150,7 @@ .sp The dummy programmer has an optional parameter specifying the bus types it should support. For that you have to use the -.B "flashrom -p dummy=type" +.B "flashrom -p dummy:type" syntax where .B type can be any comma-separated combination of @@ -158,11 +158,11 @@ in any order. .sp Example: -.B "flashrom -p dummy=lpc,fwh" +.B "flashrom -p dummy:lpc,fwh" .sp If you have multiple supported PCI cards which can program flash chips (NICs, SATA/IDE controllers, etc.) in your system, you must use the -.B "flashrom -p xxxx=bb:dd.f" +.B "flashrom -p xxxx:bb:dd.f" syntax to explicitly select one of them, where .B xxxx is the name of the programmer @@ -174,7 +174,7 @@ is the PCI function number of the desired NIC. .sp Example: -.B "flashrom -p nic3com=05:04.0" +.B "flashrom -p nic3com:05:04.0" .sp Currently the following programmers support this mechanism: .BR nic3com , @@ -183,14 +183,14 @@ The it87spi programmer has an optional parameter which will set the I/O base port of the IT87* SPI controller interface to the port specified in the parameter. For that you have to use the -.B "flashrom -p it87spi=port=portnum" +.B "flashrom -p it87spi:port=portnum" syntax where .B portnum is an I/O port number which must be a multiple of 8. .sp The ft2232spi programmer has an optional parameter specifying the controller type and interface/port it should support. For that you have to use the -.B "flashrom -p ft2232spi=model,port=interface" +.B "flashrom -p ft2232spi:model,port=interface" syntax where .B model can be any of @@ -208,9 +208,9 @@ The serprog programmer has an optional parameter specifying either a serial device/baud combination or an IP/port combination for communication with the programmer. For serial, you have to use the -.B "flashrom -p serprog=/dev/device:baud" +.B "flashrom -p serprog:/dev/device:baud" syntax and for IP, you have to use -.B "flashrom -p serprog=ip:port" +.B "flashrom -p serprog:ip:port" instead. More information about serprog is available in serprog-protocol.txt in the source distribution. .sp Modified: trunk/flashrom.c =================================================================== --- trunk/flashrom.c 2009-08-19 13:55:34 UTC (rev 692) +++ trunk/flashrom.c 2009-08-19 15:03:28 UTC (rev 693) @@ -708,7 +708,7 @@ namelen = strlen(name); if (strncmp(optarg, name, namelen) == 0) { switch (optarg[namelen]) { - case '=': + case ':': programmer_param = strdup(optarg + namelen + 1); break; case '\0': @@ -725,7 +725,7 @@ } } if (programmer == PROGRAMMER_INVALID) { - printf("Error: Unknown programmer.\n"); + printf("Error: Unknown programmer %s.\n", optarg); exit(1); } break;

1 0

[PATCH] Improve error messages, protect the user
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

Disallow erase/write for known bad chips so people won't try without a clear understanding. If we want them to test, we can tell them to patch/edit flashchips.c. If write/erase failed, warn the user to get help and not shutdown/reboot the computer. Warn that the result of a forced read is often garbage. Too many users believed that a forced read meant that everything was fine. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-errormessages/flashrom.c =================================================================== --- flashrom-errormessages/flashrom.c (Revision 676) +++ flashrom-errormessages/flashrom.c (Arbeitskopie) @@ -221,6 +221,7 @@ { size_t size = flash->total_size * 1024; /* Flash registers live 4 MByte below the flash. */ + /* FIXME: This is incorrect for nonstandard flashbase. */ flash->virtual_registers = (chipaddr)programmer_map_flash_region("flash chip registers", (0xFFFFFFFF - 0x400000 - size + 1), size); } @@ -475,6 +476,15 @@ return 0; } +void emergency_help_message() +{ + fprintf(stderr, "Your flash chip is in an unknown state.\n" + "Get help on IRC at irc.freenode.net channel #flashrom or\n" + "mail flashrom(a)flashrom.org\n" + "------------------------------------------------------------\n" + "DO NOT REBOOT OR POWEROFF!\n"); +} + void usage(const char *name) { printf("usage: %s [-VfLzhR] [-E|-r file|-w file|-v file] [-c chipname]\n" @@ -743,6 +753,7 @@ printf("Run flashrom -L to view the hardware supported in this flashrom version.\n"); exit(1); } + printf("Please note that forced reads most likely contain garbage.\n"); return read_flash(flashes[0], filename); } // FIXME: flash writes stay enabled! @@ -808,14 +819,31 @@ buf = (uint8_t *) calloc(size, sizeof(char)); if (erase_it) { - if (erase_flash(flash)) + if (flash->tested & TEST_BAD_ERASE) { + fprintf(stderr, "Erase is not working on this chip. " + "Aborting.\n"); return 1; + } + if (erase_flash(flash)) { + emergency_help_message(); + return 1; + } } else if (read_it) { if (read_flash(flash, filename)) return 1; } else { struct stat image_stat; + if (flash->tested & TEST_BAD_ERASE) { + fprintf(stderr, "Erase is not working on this chip " + "and erase is needed for write. Aborting.\n"); + return 1; + } + if (flash->tested & TEST_BAD_WRITE) { + fprintf(stderr, "Write is not working on this chip. " + "Aborting.\n"); + return 1; + } if ((image = fopen(filename, "r")) == NULL) { perror(filename); exit(1); @@ -854,14 +882,18 @@ ret = flash->write(flash, buf); if (ret) { fprintf(stderr, "FAILED!\n"); + emergency_help_message(); return 1; } else { printf("COMPLETE.\n"); } } - if (verify_it) + if (verify_it) { ret = verify_flash(flash, buf); + if (ret) + emergency_help_message(); + } programmer_shutdown(); -- http://www.hailfinger.org/

2 6

[commit] r692 - trunk
by svn＠flashrom.org 19 Aug '09

19 Aug '09

Author: hailfinger Date: 2009-08-19 15:55:34 +0200 (Wed, 19 Aug 2009) New Revision: 692 Modified: trunk/flashrom.c Log: Disallow erase/write for known bad chips so people won't try without a clear understanding. Allow override with --force. If write/erase failed, warn the user to get help and not shutdown/reboot the computer. Warn that the result of a forced read is often garbage. Too many users believed that a forced read meant that everything was fine. Wait 1 second between erase and verify. This fixes a few reports where verify directly after erase had unpleasant side effects like corrupting flash or at least getting incorrect verify results. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/flashrom.c =================================================================== --- trunk/flashrom.c 2009-08-19 13:27:58 UTC (rev 691) +++ trunk/flashrom.c 2009-08-19 13:55:34 UTC (rev 692) @@ -234,6 +234,7 @@ { size_t size = flash->total_size * 1024; /* Flash registers live 4 MByte below the flash. */ + /* FIXME: This is incorrect for nonstandard flashbase. */ flash->virtual_registers = (chipaddr)programmer_map_flash_region("flash chip registers", (0xFFFFFFFF - 0x400000 - size + 1), size); } @@ -488,6 +489,15 @@ return 0; } +void emergency_help_message() +{ + fprintf(stderr, "Your flash chip is in an unknown state.\n" + "Get help on IRC at irc.freenode.net channel #flashrom or\n" + "mail flashrom(a)flashrom.org\n" + "------------------------------------------------------------\n" + "DO NOT REBOOT OR POWEROFF!\n"); +} + void usage(const char *name) { const char *pname; @@ -792,6 +802,7 @@ printf("Run flashrom -L to view the hardware supported in this flashrom version.\n"); exit(1); } + printf("Please note that forced reads most likely contain garbage.\n"); return read_flash(flashes[0], filename); } // FIXME: flash writes stay enabled! @@ -857,14 +868,44 @@ buf = (uint8_t *) calloc(size, sizeof(char)); if (erase_it) { - if (erase_flash(flash)) + if (flash->tested & TEST_BAD_ERASE) { + fprintf(stderr, "Erase is not working on this chip. "); + if (!force) { + fprintf(stderr, "Aborting.\n"); + return 1; + } else { + fprintf(stderr, "Continuing anyway.\n"); + } + } + if (erase_flash(flash)) { + emergency_help_message(); return 1; + } } else if (read_it) { if (read_flash(flash, filename)) return 1; } else { struct stat image_stat; + if (flash->tested & TEST_BAD_ERASE) { + fprintf(stderr, "Erase is not working on this chip " + "and erase is needed for write. "); + if (!force) { + fprintf(stderr, "Aborting.\n"); + return 1; + } else { + fprintf(stderr, "Continuing anyway.\n"); + } + } + if (flash->tested & TEST_BAD_WRITE) { + fprintf(stderr, "Write is not working on this chip. "); + if (!force) { + fprintf(stderr, "Aborting.\n"); + return 1; + } else { + fprintf(stderr, "Continuing anyway.\n"); + } + } if ((image = fopen(filename, "r")) == NULL) { perror(filename); exit(1); @@ -903,14 +944,24 @@ ret = flash->write(flash, buf); if (ret) { fprintf(stderr, "FAILED!\n"); + emergency_help_message(); return 1; } else { printf("COMPLETE.\n"); } } - if (verify_it) + if (verify_it) { + /* Work around chips which need some time to calm down. */ + if (write_it) + programmer_delay(1000*1000); ret = verify_flash(flash, buf); + /* If we tried to write, and now we don't properly verify, we + * might have an emergency situation. + */ + if (ret && write_it) + emergency_help_message(); + } programmer_shutdown();

1 0

[PATCH] Compile out FT2232 SPI if not selected
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

If FT2232H SPI is not enabled, it should be compiled out completely. We can't remove ft2232_spi.o from unconditional OBJS yet due to our makefile structure (make features), but this patch adds #ifdefs around all FT2232H code, so the net effect is the same. This is 0.9.1 material. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-ft2232_compileout/flash.h =================================================================== --- flashrom-ft2232_compileout/flash.h (Revision 684) +++ flashrom-ft2232_compileout/flash.h (Arbeitskopie) @@ -86,7 +86,9 @@ PROGRAMMER_NIC3COM, PROGRAMMER_SATASII, PROGRAMMER_IT87SPI, +#if FT2232_SPI_SUPPORT == 1 PROGRAMMER_FT2232SPI, +#endif #if SERPROG_SUPPORT == 1 PROGRAMMER_SERPROG, #endif @@ -426,9 +428,13 @@ SPI_CONTROLLER_SB600, SPI_CONTROLLER_VIA, SPI_CONTROLLER_WBSIO, +#if FT2232_SPI_SUPPORT == 1 SPI_CONTROLLER_FT2232, +#endif SPI_CONTROLLER_DUMMY, + SPI_CONTROLLER_INVALID /* This must always be the last entry. */ }; +extern const int spi_programmer_count; struct spi_command { unsigned int writecnt; unsigned int readcnt; Index: flashrom-ft2232_compileout/spi.c =================================================================== --- flashrom-ft2232_compileout/spi.c (Revision 684) +++ flashrom-ft2232_compileout/spi.c (Arbeitskopie) @@ -82,12 +82,14 @@ .write_256 = wbsio_spi_write_1, }, +#if FT2232_SPI_SUPPORT == 1 { /* SPI_CONTROLLER_FT2232 */ .command = ft2232_spi_send_command, .multicommand = default_spi_send_multicommand, .read = ft2232_spi_read, .write_256 = ft2232_spi_write_256, }, +#endif { /* SPI_CONTROLLER_DUMMY */ .command = dummy_spi_send_command, @@ -95,8 +97,11 @@ .read = NULL, .write_256 = NULL, }, + + {}, /* This entry corresponds to SPI_CONTROLLER_INVALID. */ }; +const int spi_programmer_count = ARRAY_SIZE(spi_programmer); int spi_send_command(unsigned int writecnt, unsigned int readcnt, const unsigned char *writearr, unsigned char *readarr) @@ -293,7 +298,9 @@ case SPI_CONTROLLER_VIA: case SPI_CONTROLLER_SB600: case SPI_CONTROLLER_WBSIO: +#if FT2232_SPI_SUPPORT == 1 case SPI_CONTROLLER_FT2232: +#endif case SPI_CONTROLLER_DUMMY: return probe_spi_rdid_generic(flash, 4); default: Index: flashrom-ft2232_compileout/ft2232_spi.c =================================================================== --- flashrom-ft2232_compileout/ft2232_spi.c (Revision 684) +++ flashrom-ft2232_compileout/ft2232_spi.c (Arbeitskopie) @@ -18,6 +18,8 @@ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA */ +#if FT2232_SPI_SUPPORT == 1 + #include <stdio.h> #include <stdint.h> #include <string.h> @@ -25,9 +27,6 @@ #include <ctype.h> #include "flash.h" #include "spi.h" - -#if FT2232_SPI_SUPPORT == 1 - #include <ftdi.h> /* the 'H' chips can run internally at either 12Mhz or 60Mhz. @@ -297,29 +296,4 @@ return 0; } -#else -int ft2232_spi_init(void) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} - -int ft2232_spi_send_command(unsigned int writecnt, unsigned int readcnt, - const unsigned char *writearr, unsigned char *readarr) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} - -int ft2232_spi_read(struct flashchip *flash, uint8_t *buf, int start, int len) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} - -int ft2232_spi_write_256(struct flashchip *flash, uint8_t *buf) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} #endif Index: flashrom-ft2232_compileout/flashrom.c =================================================================== --- flashrom-ft2232_compileout/flashrom.c (Revision 684) +++ flashrom-ft2232_compileout/flashrom.c (Arbeitskopie) @@ -122,6 +122,7 @@ .delay = internal_delay, }, +#if FT2232_SPI_SUPPORT == 1 { .name = "ft2232spi", .init = ft2232_spi_init, @@ -138,6 +139,7 @@ .chip_writen = fallback_chip_writen, .delay = internal_delay, }, +#endif #if SERPROG_SUPPORT == 1 { @@ -610,6 +612,10 @@ fprintf(stderr, "Programmer table miscompilation!\n"); exit(1); } + if (spi_programmer_count - 1 != SPI_CONTROLLER_INVALID) { + fprintf(stderr, "SPI programmer table miscompilation!\n"); + exit(1); + } setbuf(stdout, NULL); while ((opt = getopt_long(argc, argv, "rRwvnVEfc:m:l:i:p:Lzh", -- http://www.hailfinger.org/

2 2

[commit] r691 - trunk
by svn＠flashrom.org 19 Aug '09

19 Aug '09

Author: hailfinger Date: 2009-08-19 15:27:58 +0200 (Wed, 19 Aug 2009) New Revision: 691 Modified: trunk/flash.h trunk/flashrom.c trunk/ft2232_spi.c trunk/spi.c Log: If FT2232H SPI is not enabled, it should be compiled out completely. We can't remove ft2232_spi.o from unconditional OBJS yet due to our makefile structure (make features), but this patch adds #ifdefs around all FT2232H code, so the net effect is the same. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Reinauer <stepan(a)coresystems.de> Modified: trunk/flash.h =================================================================== --- trunk/flash.h 2009-08-19 10:46:23 UTC (rev 690) +++ trunk/flash.h 2009-08-19 13:27:58 UTC (rev 691) @@ -86,7 +86,9 @@ PROGRAMMER_NIC3COM, PROGRAMMER_SATASII, PROGRAMMER_IT87SPI, +#if FT2232_SPI_SUPPORT == 1 PROGRAMMER_FT2232SPI, +#endif #if SERPROG_SUPPORT == 1 PROGRAMMER_SERPROG, #endif @@ -436,9 +438,13 @@ SPI_CONTROLLER_SB600, SPI_CONTROLLER_VIA, SPI_CONTROLLER_WBSIO, +#if FT2232_SPI_SUPPORT == 1 SPI_CONTROLLER_FT2232, +#endif SPI_CONTROLLER_DUMMY, + SPI_CONTROLLER_INVALID /* This must always be the last entry. */ }; +extern const int spi_programmer_count; struct spi_command { unsigned int writecnt; unsigned int readcnt; Modified: trunk/flashrom.c =================================================================== --- trunk/flashrom.c 2009-08-19 10:46:23 UTC (rev 690) +++ trunk/flashrom.c 2009-08-19 13:27:58 UTC (rev 691) @@ -122,6 +122,7 @@ .delay = internal_delay, }, +#if FT2232_SPI_SUPPORT == 1 { .name = "ft2232spi", .init = ft2232_spi_init, @@ -138,6 +139,7 @@ .chip_writen = fallback_chip_writen, .delay = internal_delay, }, +#endif #if SERPROG_SUPPORT == 1 { @@ -610,6 +612,10 @@ fprintf(stderr, "Programmer table miscompilation!\n"); exit(1); } + if (spi_programmer_count - 1 != SPI_CONTROLLER_INVALID) { + fprintf(stderr, "SPI programmer table miscompilation!\n"); + exit(1); + } setbuf(stdout, NULL); while ((opt = getopt_long(argc, argv, "rRwvnVEfc:m:l:i:p:Lzh", Modified: trunk/ft2232_spi.c =================================================================== --- trunk/ft2232_spi.c 2009-08-19 10:46:23 UTC (rev 690) +++ trunk/ft2232_spi.c 2009-08-19 13:27:58 UTC (rev 691) @@ -18,6 +18,8 @@ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA */ +#if FT2232_SPI_SUPPORT == 1 + #include <stdio.h> #include <stdint.h> #include <string.h> @@ -25,9 +27,6 @@ #include <ctype.h> #include "flash.h" #include "spi.h" - -#if FT2232_SPI_SUPPORT == 1 - #include <ftdi.h> /* the 'H' chips can run internally at either 12Mhz or 60Mhz. @@ -297,29 +296,4 @@ return 0; } -#else -int ft2232_spi_init(void) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} - -int ft2232_spi_send_command(unsigned int writecnt, unsigned int readcnt, - const unsigned char *writearr, unsigned char *readarr) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} - -int ft2232_spi_read(struct flashchip *flash, uint8_t *buf, int start, int len) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} - -int ft2232_spi_write_256(struct flashchip *flash, uint8_t *buf) -{ - fprintf(stderr, "FT2232 SPI support was not compiled in\n"); - exit(1); -} #endif Modified: trunk/spi.c =================================================================== --- trunk/spi.c 2009-08-19 10:46:23 UTC (rev 690) +++ trunk/spi.c 2009-08-19 13:27:58 UTC (rev 691) @@ -82,12 +82,14 @@ .write_256 = wbsio_spi_write_1, }, +#if FT2232_SPI_SUPPORT == 1 { /* SPI_CONTROLLER_FT2232 */ .command = ft2232_spi_send_command, .multicommand = default_spi_send_multicommand, .read = ft2232_spi_read, .write_256 = ft2232_spi_write_256, }, +#endif { /* SPI_CONTROLLER_DUMMY */ .command = dummy_spi_send_command, @@ -95,8 +97,11 @@ .read = NULL, .write_256 = NULL, }, + + {}, /* This entry corresponds to SPI_CONTROLLER_INVALID. */ }; +const int spi_programmer_count = ARRAY_SIZE(spi_programmer); int spi_send_command(unsigned int writecnt, unsigned int readcnt, const unsigned char *writearr, unsigned char *readarr) @@ -293,7 +298,9 @@ case SPI_CONTROLLER_VIA: case SPI_CONTROLLER_SB600: case SPI_CONTROLLER_WBSIO: +#if FT2232_SPI_SUPPORT == 1 case SPI_CONTROLLER_FT2232: +#endif case SPI_CONTROLLER_DUMMY: return probe_spi_rdid_generic(flash, 4); default:

1 0

[ANNOUNCE] flashrom 0.9.1-rc1 has been released
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

flashrom 0.9.1-rc1 has been released. Draft 0.9.1 announcement is at http://www.coreboot.org/Flashrom/0.9.1 and will be moved to flashrom.org once the release is out. http://patchwork.coreboot.org/project/flashrom/list/ has all pending flashrom patches. The following are 0.9.1 material and need an Ack right now: Tidy up docs before release Add serprog to man page quick shot at BSD RDMSR support Compile out FT2232 SPI if not selected Improve error messages, protect the user A tarball will show up at http://qa.coreboot.org/releases/ soon. Regards, Carl-Daniel -- http://www.hailfinger.org/

1 1

quick shot at BSD RDMSR support
by Stefan Reinauer 19 Aug '09

19 Aug '09

This needs /dev/cpu0 from ports/sysutils It's untested and probably won't even compile.. Stefan -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866

4 7

[commit] r690 - trunk
by svn＠flashrom.org 19 Aug '09

19 Aug '09

Author: hailfinger Date: 2009-08-19 12:46:23 +0200 (Wed, 19 Aug 2009) New Revision: 690 Modified: trunk/flash.h trunk/physmap.c Log: Support rdmsr/wrmsr operations on FreeBSD. So far, AMD Geode LX is the only user of this infrastructure. It needs /dev/cpu0 from ports/sysutils on FreeBSD during runtime on Geode LX. Signed-off-by: Stefan Reinauer <stepan(a)coresystems.de> Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Idwer Vollering <vidwer(a)gmail.com> Acked-by: <putlinuxonit(a)gmail.com> Modified: trunk/flash.h =================================================================== --- trunk/flash.h 2009-08-18 23:51:22 UTC (rev 689) +++ trunk/flash.h 2009-08-19 10:46:23 UTC (rev 690) @@ -309,11 +309,21 @@ void physunmap(void *virt_addr, size_t len); int setup_cpu_msr(int cpu); void cleanup_cpu_msr(void); -#ifndef __DARWIN__ +#if !defined(__DARWIN__) && !defined(__FreeBSD__) && !defined(__DragonFly__) typedef struct { uint32_t hi, lo; } msr_t; msr_t rdmsr(int addr); int wrmsr(int addr, msr_t msr); #endif +#if defined(__FreeBSD__) || defined(__DragonFly__) +/* FreeBSD already has conflicting definitions for wrmsr/rdmsr. */ +#undef rdmsr +#undef wrmsr +#define rdmsr freebsd_rdmsr +#define wrmsr freebsd_wrmsr +typedef struct { uint32_t hi, lo; } msr_t; +msr_t freebsd_rdmsr(int addr); +int freebsd_wrmsr(int addr, msr_t msr); +#endif /* internal.c */ struct pci_dev *pci_dev_find_filter(struct pci_filter filter); Modified: trunk/physmap.c =================================================================== --- trunk/physmap.c 2009-08-18 23:51:22 UTC (rev 689) +++ trunk/physmap.c 2009-08-19 10:46:23 UTC (rev 690) @@ -215,6 +215,91 @@ fd_msr = -1; } #else +#if defined(__FreeBSD__) || defined(__DragonFly__) +#include <sys/ioctl.h> + +typedef struct { + int msr; + uint64_t data; +} cpu_msr_args_t; +#define CPU_RDMSR _IOWR('c', 1, cpu_msr_args_t) +#define CPU_WRMSR _IOWR('c', 2, cpu_msr_args_t) + +static int fd_msr = -1; + +msr_t rdmsr(int addr) +{ + cpu_msr_args_t args; + + msr_t msr = { 0xffffffff, 0xffffffff }; + + args.msr = addr; + + if (ioctl(fd_msr, CPU_RDMSR, &args) < 0) { + perror("CPU_RDMSR"); + close(fd_msr); + exit(1); + } + + msr.lo = args.data & 0xffffffff; + msr.hi = args.data >> 32; + + return msr; +} + +int wrmsr(int addr, msr_t msr) +{ + cpu_msr_args_t args; + + args.msr = addr; + args.data = (((uint64_t)msr.hi) << 32) | msr.lo; + + if (ioctl(fd_msr, CPU_WRMSR, &args) < 0) { + perror("CPU_WRMSR"); + close(fd_msr); + exit(1); + } + + return 0; +} + +int setup_cpu_msr(int cpu) +{ + char msrfilename[64]; + memset(msrfilename, 0, 64); + sprintf(msrfilename, "/dev/cpu%d", cpu); + + if (fd_msr != -1) { + printf("MSR was already initialized\n"); + return -1; + } + + fd_msr = open(msrfilename, O_RDWR); + + if (fd_msr < 0) { + perror("Error while opening /dev/cpu0"); + printf("Did you install ports/sysutils/devcpu?\n"); + return -1; + } + + return 0; +} + +void cleanup_cpu_msr(void) +{ + if (fd_msr == -1) { + printf("No MSR initialized.\n"); + return; + } + + close(fd_msr); + + /* Clear MSR file descriptor */ + fd_msr = -1; +} + +#else + #ifdef __DARWIN__ int setup_cpu_msr(int cpu) { @@ -251,4 +336,5 @@ } #endif #endif +#endif

1 0

[PATCH] Add serprog to man page
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

Add serprog documentation to the manpage. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-serprog_manpage/flashrom.8 =================================================================== --- flashrom-serprog_manpage/flashrom.8 (Revision 686) +++ flashrom-serprog_manpage/flashrom.8 (Arbeitskopie) @@ -150,6 +150,8 @@ .sp .BR "* ft2232spi" " (for flash ROMs attached to a FT2232H/FT4232H based USB SPI programmer)" .sp +.BR "* serprog" " (for flash ROMs attached to Urja's AVR programmer)" +.sp The dummy programmer has an optional parameter specifying the bus types it should support. For that you have to use the .B "flashrom -p dummy=type" @@ -182,16 +184,16 @@ .BR nic3com , .BR satasii . .sp -The it87spi has an optional parameter which will set the I/O base port of the -IT87* SPI controller interface to the port specified in the parameter. -For that you have to use the +The it87spi programmer has an optional parameter which will set the I/O base +port of the IT87* SPI controller interface to the port specified in the +parameter. For that you have to use the .B "flashrom -p it87spi=port=portnum" syntax where .B portnum is an I/O port number which must be a multiple of 8. .sp -The ft2232spi has an optional parameter specifying the controller type and -interface/port it should support. For that you have to use the +The ft2232spi programmer has an optional parameter specifying the controller +type and interface/port it should support. For that you have to use the .B "flashrom -p ft2232spi=model,port=interface" syntax where .B model @@ -206,6 +208,19 @@ .B 4232H and the default interface is .BR B . +.sp +The serprog programmer has an optional parameter specifying either a serial +device/baud combination or an IP/port combination for communication with the +programmer. For serial, you have to use the +.B "flashrom -p serprog=/dev/device:baud" +syntax and for IP, you have to use +.B "flashrom -p serprog=ip:port" +instead. More information about serprog is available in serprog-protocol.txt in +the source distribution. +.sp +Support for some programmers can be disabled at compile time. +.B "flashrom -h" +lists all supported programmers. .TP .B "\-h, \-\-help" Show a help text and exit. -- http://www.hailfinger.org/

2 2

[commit] r689 - trunk
by svn＠flashrom.org 19 Aug '09

19 Aug '09

Author: hailfinger Date: 2009-08-19 01:51:22 +0200 (Wed, 19 Aug 2009) New Revision: 689 Modified: trunk/flashrom.8 Log: Add serprog documentation to the manpage. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/flashrom.8 =================================================================== --- trunk/flashrom.8 2009-08-18 23:50:14 UTC (rev 688) +++ trunk/flashrom.8 2009-08-18 23:51:22 UTC (rev 689) @@ -146,6 +146,8 @@ .sp .BR "* ft2232spi" " (for flash ROMs attached to a FT2232H/FT4232H based USB SPI programmer)" .sp +.BR "* serprog" " (for flash ROMs attached to Urja's AVR programmer)" +.sp The dummy programmer has an optional parameter specifying the bus types it should support. For that you have to use the .B "flashrom -p dummy=type" @@ -178,16 +180,16 @@ .BR nic3com , .BR satasii . .sp -The it87spi has an optional parameter which will set the I/O base port of the -IT87* SPI controller interface to the port specified in the parameter. -For that you have to use the +The it87spi programmer has an optional parameter which will set the I/O base +port of the IT87* SPI controller interface to the port specified in the +parameter. For that you have to use the .B "flashrom -p it87spi=port=portnum" syntax where .B portnum is an I/O port number which must be a multiple of 8. .sp -The ft2232spi has an optional parameter specifying the controller type and -interface/port it should support. For that you have to use the +The ft2232spi programmer has an optional parameter specifying the controller +type and interface/port it should support. For that you have to use the .B "flashrom -p ft2232spi=model,port=interface" syntax where .B model @@ -202,6 +204,19 @@ .B 4232H and the default interface is .BR B . +.sp +The serprog programmer has an optional parameter specifying either a serial +device/baud combination or an IP/port combination for communication with the +programmer. For serial, you have to use the +.B "flashrom -p serprog=/dev/device:baud" +syntax and for IP, you have to use +.B "flashrom -p serprog=ip:port" +instead. More information about serprog is available in serprog-protocol.txt in +the source distribution. +.sp +Support for some programmers can be disabled at compile time. +.B "flashrom -h" +lists all supported programmers. .TP .B "\-h, \-\-help" Show a help text and exit.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom