<HTML><BODY><p>[darkprof@SUT tusl-2c]$ sudo flashrom -w 1014tc.001 <br>Пароль: <br>flashrom v0.9.5.1-r1509 on Linux 3.0-ARCH (i686), built with libpci 3.1.9, GCC 4.6.2 20120120 (prerelease), little endian<br>flashrom is free software, get the source code at http://www.flashrom.org</p><p>Calibrating delay loop... OK.<br>sh: dmidecode: команда не найдена<br>dmidecode execution unsuccessful - continuing without DMI info<br>Found chipset "Intel ICH2". Enabling flash write... OK.<br>Found Winbond flash chip "W49V002FA" (256 kB, FWH) at physical address 0xfffc0000.<br>===<br>This flash part has status UNTESTED for operations: ERASE WRITE<br>The test status of this chip may have been updated in the latest development<br>version of flashrom. If you are running the latest development version,<br>please email a report to flashrom@flashrom.org if any of the above operations<br>work correctly for you with this flash part. Please include the flashrom<br>output with the additional -V option for all operations you tested (-V, -Vr,<br>-VE, -Vw), and mention which mainboard or programmer you tested.<br>Please mention your board in the subject line. Thanks for your help!<br>Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.<br>Reading old flash chip contents... done.<br>Erasing and writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0000ffff: 0xfee7<br>ERASE FAILED!<br>Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0003ffff: 0x36050<br>ERASE FAILED!<br>FAILED!<br>Uh oh. Erase/write failed. Checking if anything changed.<br>Good. It seems nothing was changed.<br>Writing to the flash chip apparently didn't do anything.<br>This means we have to add special support for your board, programmer or flash chip.<br>Please report this on IRC at irc.freenode.net (channel #flashrom) or<br>mail flashrom@flashrom.org!<br>-------------------------------------------------------------------------------<br>You may now reboot or simply leave the machine running.<br>[darkprof@SUT tusl-2c]$ sudo flashrom -Vw 1014tc.001 <br>Пароль: <br>flashrom v0.9.5.1-r1509 on Linux 3.0-ARCH (i686), built with libpci 3.1.9, GCC 4.6.2 20120120 (prerelease), little endian<br>flashrom is free software, get the source code at http://www.flashrom.org</p><p>Calibrating delay loop... OS timer resolution is 1 usecs, 476M loops per second, delay more than 10% too short (got 84% of expected delay), recalculating... 380M loops per second, delay more than 10% too short (got 69% of expected delay), recalculating... 364M loops per second, delay more than 10% too short (got 65% of expected delay), recalculating... 525M loops per second, 10 myus = 10 us, 100 myus = 93 us, 1000 myus = 1022 us, 10000 myus = 15445 us, 4 myus = 4 us, OK.<br>Initializing internal programmer<br>No coreboot table found.<br>sh: dmidecode: команда не найдена<br>dmidecode execution unsuccessful - continuing without DMI info<br>Found chipset "Intel ICH2" with PCI ID 8086:2440. Enabling flash write... <br>BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0<br>OK.<br>The following protocols are supported: FWH.<br>Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content<br>Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content<br>Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content<br>Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x25, id2 0xdc, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Found Winbond flash chip "W49V002FA" (256 kB, FWH) at physical address 0xfffc0000.<br>Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0x32<br>Found Winbond flash chip "W49V002FA" (256 kB, FWH).<br>===<br>This flash part has status UNTESTED for operations: ERASE WRITE<br>The test status of this chip may have been updated in the latest development<br>version of flashrom. If you are running the latest development version,<br>please email a report to flashrom@flashrom.org if any of the above operations<br>work correctly for you with this flash part. Please include the flashrom<br>output with the additional -V option for all operations you tested (-V, -Vr,<br>-VE, -Vw), and mention which mainboard or programmer you tested.<br>Please mention your board in the subject line. Thanks for your help!<br>Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.<br>Reading old flash chip contents... done.<br>Erasing and writing flash chip... Trying erase function 0... 0x000000-0x00ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0000ffff: 0xfee7<br>ERASE FAILED!<br>Reading current flash chip contents... done. Looking for another erase function.<br>Trying erase function 1... 0x000000-0x03ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x25, failed byte count from 0x00000000-0x0003ffff: 0x36050<br>ERASE FAILED!<br>Looking for another erase function.<br>No usable erase functions left.<br>FAILED!<br>Uh oh. Erase/write failed. Checking if anything changed.<br>Good. It seems nothing was changed.<br>Writing to the flash chip apparently didn't do anything.<br>This means we have to add special support for your board, programmer or flash chip.<br>Please report this on IRC at irc.freenode.net (channel #flashrom) or<br>mail flashrom@flashrom.org!<br>-------------------------------------------------------------------------------<br>You may now reboot or simply leave the machine running.<br>Restoring PCI config space for 00:1f:0 reg 0x4e<br>[darkprof@SUT tusl-2c]$ <br></p></BODY></HTML>