<HTML><BODY><div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div>
<base target="_self" href="https://e.mail.ru/">
<div id="style_15135773810000000437_BODY"><div class="class_1513582051">
Greetings<br><br>I have VMC1100 from Nexcom( nexcom.com).<br>While running<br> flashrom --programmer internal <br>I get an advice to send you output of <br>flashrom -VV -p internal<br>so here it is:<br><br><br><p>flashrom v0.9.8-r1888 on Linux 4.3.0VMC1100 (x86_64)<br>flashrom is free software, get the source code at <a href="http://www.flashrom.org" target="_blank">http://www.flashrom.org</a></p><p>flashrom was built with libpci 3.4.0, GCC 4.9.3, little endian<br>Command line (3 args): flashrom -VV --programmer internal<br>Calibrating delay loop... OS timer resolution is 1 usecs, 420M loops per second, 10 myus = 9 us, 100 myus = 94 us, 1000 myus = 954 us, 10000 myus = 9963 us, 4 myus = 4 us, OK.<br>Initializing internal programmer<br>No coreboot table found.<br>Using Internal DMI decoder.<br>DMI string chassis-type: "Desktop"<br>DMI string system-manufacturer: "NEXCOM"<br>DMI string system-product-name: "VMC 1100"<br>DMI string system-version: "1.0"<br>DMI string baseboard-manufacturer: "NEXCOM"<br>DMI string baseboard-product-name: "VMC 1100"<br>DMI string baseboard-version: "C"<br> ID 0xc8, version 1.0<br> Length 12 B, Parameter Table Pointer 0x000060<br>===<br>SFDP has autodetected a flash chip which is not natively supported by flashrom yet.<br>All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually.<br>You can help us by mailing us the output of the following command to flashrom@flashrom.org:<br>'flashrom -VV [plus the -p/--programmer parameter]'<br>Thanks for your help!<br>===<br>Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI) mapped at physical address 0x0000000000000000.<br>Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc8, id2 0x6017<br>Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xc8, id2 0x16<br>Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x89, id2 0x45, id1 is normal flash content, id2 is normal flash content<br>Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<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 0x89, id2 0x45, id1 is normal flash content, id2 is normal flash content<br>Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<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 0x89, id2 0x45, id1 is normal flash content, id2 is normal flash content<br>Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<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 0x89, id2 0x45, 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 0xff, id2 0xff, id1 parity violation, 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x89, id2 0x45, id1 is normal flash content, id2 is normal flash content<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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content<br>Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI).<br>No operations were specified.<br>Restoring MMIO space at 0x7f910938609c<br>Restoring MMIO space at 0x7f9109386098<br>Restoring MMIO space at 0x7f9109386096<br>Restoring MMIO space at 0x7f9109386094<br>Restoring MMIO space at 0x7f91093860fc</p>Is there any way to update BIOS with flashrom?<br><br><br>Sincerely yours,<br>Georgiy Okhokhonin<br>software engineer<br>AO «NPK «VIP»<br><a href="http://www.zaovip.ru" target="_blank" rel=" noopener noreferrer">www.zaovip.ru</a>
</div></div>
<base target="_self" href="https://e.mail.ru/">
</div>
</div></BODY></HTML>