flashrom

flashrom@flashrom.org

5 participants
9161 discussions

Bad MX25L4005AM2C ?
by ondrej ondrej 17 Dec '17

17 Dec '17

Hi flashrom maintainers, I failed to read a MX25L4005AM2C (this name is written on chip) via the "Olimex ARM-USB-OCD-H". Maybe this chip have wrong id? Id for this chip in datasheet is Id1=0xC2, Id2=0x2013 flashrom v0.9.9-98-g3083ed9 on Linux 4.0.5-gentoo (x86_64) flashrom was built with libpci 3.2.0, GCC 4.8.4, little endian Command line (5 args): ./flashrom -V -p ft2232_spi:type=arm-usb-ocd-h -o test.txt Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing ft2232_spi programmer Using device type Olimex ARM-USB-OCD-H channel A. Disable divide-by-5 front stage Set clock divisor MPSSE clock: 60.000000 MHz, divisor: 2, SPI clock: 30.000000 MHz No loopback of TDI/DO TDO/DI Set data bits The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT26DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT26DF161A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT26F004, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45CS1282, 16896 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB011D, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB021D, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB041D, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB081D, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB161D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB321C, 4224 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB321D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB321E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel AT45DB642D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ESMT F25L008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ESMT F25L32PA, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B05T, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B10T, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B20T, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B40T, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B80T, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B16T, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B32T, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25B64T, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25F64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25Q40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25Q80(A), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25Q16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25Q32(A/B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25Q64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25Q128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25QH16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25QH32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25QH64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25QH128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25S32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon EN25S64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ESI ES25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ESI ES25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ESI ES25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25LQ40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25LQ80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25LQ32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25LQ64(B), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25LQ128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q20(B), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q40(B), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q80(B), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q16(B), 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q32(B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q64(B), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q128B, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25Q128C, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25T80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25VQ21B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25VQ40C, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25VQ41B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25VQ80C, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for GigaDevice GD25VQ16C, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Intel 25F160S33B8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Intel 25F160S33T8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Intel 25F320S33B8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Intel 25F320S33T8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Intel 25F640S33B8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Intel 25F640S33T8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ISSI IS25LP128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ISSI IS25WP128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX23L1654, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX23L3254, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX23L6454, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX23L12854, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L1635D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L3205(A), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L3273E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L6405, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L6405D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L12805D, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L25635F/MX25L25645E/MX25L25665E, 32768 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX66L51235F, 65536 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25U1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25U3235E/F, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25U6435E/F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25U12835F, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix MX25L6495F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25P128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M45PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M45PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M45PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron N25Q256..3E/MT25QL256, 32768 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Micron N25Q512..3E/MT25QL512, 65536 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Nantronics N25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Nantronics N25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Nantronics N25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Nantronics N25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Nantronics N25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LD256C, 32 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LD512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LD010(C), 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LD020(C), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LD040(C), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LQ020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LQ040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LQ080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LQ016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LQ032C, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for PMC Pm25LV010A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LV020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LV040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LV080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC Pm25LV016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Sanyo LE25FW203A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Sanyo LE25FW403A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for Spansion S25FL004A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL016A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL032A/P, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL064A/P, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL204K, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL208K, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL132K, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL164K, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL127S-64kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL127S-256kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL128P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL128P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL128S......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL128S......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL129P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Spansion S25FL129P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xe1, id2 0x9 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x9, id2 0x9 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xe1, id2 0x9 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xe1, id2 0x9 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xe1, id2 0x9 Probing for SST SST25VF020B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xe1, id2 0x9 Probing for SST SST25VF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xe1, id2 0x9 Probing for SST SST25WF020A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25WF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25WF080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25VF080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25VF016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25VF032B, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25VF064C, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25WF512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25WF010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25WF020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25WF040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST SST25WF080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q40.V, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q80.V, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q16.V, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q32.V, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q64.V, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q128.V, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q256.V, 32768 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q20.W, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q40.W, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q80.W, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q16.W, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q32.W, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25Q128.W, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25X10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25X20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25X40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25X80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25X16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25X32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond W25X64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Unknown SFDP-capable chip, 0 kB: Signature = 0xffffffff (should be 0x50444653) No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Atmel unknown Atmel SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Eon unknown Eon SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for PMC unknown PMC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for SST unknown SST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for ST unknown ST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009 Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ft2232_spi. Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xe1, id2 0x9 Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! No operations were specified.

1 0

Re: [flashrom] Varification trouble - flashrom v0.9.9-r1954, Intel I210 NIC over SPI, Microchip SST25VF040B
by Lamont Dean 14 Dec '17

14 Dec '17

I've checked voltages on write protect and hold pins and searched through the code hoping for some extra bit of insight. I've now changed to the Microchip SST26VF016B flash chip that I wanted originally and have added the part to the flashrom flashchips.h and .c. Flashrom now recognizes the SST26VF016B flash chip and tries to program it but can't verify the code. The SST26VF016B doesn't have the block protection that the others do and programs once the write enable command is sent. Flashrom looks like its sending the right enable code so I'm not sure what's going on. Thanks, LaMont ... flashrom> sudo flashrom -VVVV -p nicintel_spi:pci=01:00.0 -w Dev_Start_I210_Copper_MCTP_16Mb_A2_3.25_0.03.bin flashrom v0.9.9-r1954 on Linux 4.4.38-tegra (aarch64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.3.1, GCC 5.4.0 20160609, little endian Command line (5 args): flashrom -VVVV -p nicintel_spi:pci=01:00.0 -w Dev_Start_I210_Copper_MCTP_16Mb_A2_3.25_0.03.bin Calibrating delay loop... OS timer resolution is 1 usecs, 2524M loops per second, 10 myus = 16 us, 100 myus = 106 us, 1000 myus = 1000 us, 10000 myus = 9988 us, 4 myus = 12 us, OK. Initializing nicintel_spi programmer Found "Intel Unprogrammed i210 Gigabit Ethernet Controller" (8086:1531, BDF 01:00.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable page_size=1000 pre-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 post-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: programmer_map_flash_region: mapping A25L05PT from 0x00000000ffff0000 to 0x0000000000000000 RDID returned 0xbf 0x26 0x41 0xbf. probe_spi_rdid_generic: id1 0xbf, id2 0x2641 ... "depreciated" ... Probing for Generic unknown SPI chip (REMS), 0 kB: REMS returned 0xff 0xff. probe_spi_rems: id1 0xff, id2 0xff Found SST flash chip "SST26VF016B" (2048 kB, SPI). === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! programmer_map_flash_region: mapping SST26VF016B from 0x00000000ffe00000 to 0x0000000000000000 Block protection is disabled. Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:S, 0x002000-0x002fff:S, 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:S, 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, 0x015000-0x015fff:S, 0x016000-0x016fff:S, ... "depreciated" ... 0x1ec000-0x1ecfff:S, 0x1ed000-0x1edfff:S, 0x1ee000-0x1eefff:S, 0x1ef000-0x1effff:S, 0x1f0000-0x1f0fff:S, 0x1f1000-0x1f1fff:S, 0x1f2000-0x1f2fff:S, 0x1f3000-0x1f3fff:S, 0x1f4000-0x1f4fff:S, 0x1f5000-0x1f5fff:S, 0x1f6000-0x1f6fff:S, 0x1f7000-0x1f7fff:S, 0x1f8000-0x1f8fff:S, 0x1f9000-0x1f9fff:S, 0x1fa000-0x1fafff:S, 0x1fb000-0x1fbfff:S, 0x1fc000-0x1fcfff:S, 0x1fd000-0x1fdfff:S, 0x1fe000-0x1fefff:S, 0x1ff000-0x1fffff:S Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, failed byte count from 0x00000000-0x001fffff: 0x352ba Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! programmer_unmap_flash_region: unmapped 0x0000000000000000 On Tue, Dec 12, 2017 at 11:07 AM, Lamont Dean <lamont.dean(a)imsar.com> wrote: > Okay, I'm seeing it better now and it isn't removing the block protection. > > On Tue, Dec 12, 2017 at 10:23 AM, Lamont Dean <lamont.dean(a)imsar.com> > wrote: > >> Hello, >> >> Flashrom can find the Intel I210 NIC SPI connected to the SST25VF040B >> flash chip and seems to program but fails to verify and gave me this email >> to write to about it. The output is included below. Before and after a >> power cycle the Intel I210 still says its in its unprogrammed state. >> >> I'd like to program a Microchip SST26VF016B flash in place of the >> ...25VF040... but its not on the list so I'm going through the comments I >> found on the wedsite Design Guide >> <https://www.flashrom.org/Development_Guidelines>. I'm new to Linux and >> things so we'll see how it goes. >> >> Any help you can offer would be greatly appreciated. >> >> Thanks, >> >> LaMont Dean >> Hardware Engineer >> ImSAR, LLC. >> >> ...flashrom> sudo flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c >> SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin >> flashrom v0.9.9-r1954 on Linux 4.4.38-tegra (aarch64) >> flashrom is free software, get the source code at https://flashrom.org >> >> flashrom was built with libpci 3.3.1, GCC 5.4.0 20160609, little endian >> Command line (7 args): flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c >> SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin >> Calibrating delay loop... OS timer resolution is 1 usecs, 2531M loops per >> second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus >> = 10022 us, 4 myus = 4 us, OK. >> Initializing nicintel_spi programmer >> Found "Intel Unprogrammed i210 Gigabit Ethernet Controller" (8086:1531, >> BDF 01:00.0). >> === >> This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output >> to flashrom(a)flashrom.org if it works for you. Please add the name of your >> PCI device to the subject. Thank you for your help! >> === >> PCI header type 0x00 >> Requested BAR is of type MEM, 32bit, not prefetchable >> PCI header type 0x00 >> Requested BAR is of type MEM, 32bit, not prefetchable >> page_size=1000 >> pre-rounding: start=0x0000000050800000, len=0x1000, >> end=0x0000000050801000 >> post-rounding: start=0x0000000050800000, len=0x1000, >> end=0x0000000050801000 >> The following protocols are supported: SPI. >> Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping >> SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 >> RDID returned 0xbf 0x25 0x8d. probe_spi_rdid_generic: id1 0xbf, id2 0x258d >> Found SST flash chip "SST25VF040B" (512 kB, SPI) on nicintel_spi. >> Chip status register is 0x1c. >> Chip status register: Block Protect Write Disable (BPL) is not set >> Chip status register: Auto Address Increment Programming (AAI) is not set >> Chip status register: Block Protect 3 (BP3) is not set >> Chip status register: Block Protect 2 (BP2) is set >> Chip status register: Block Protect 1 (BP1) is set >> Chip status register: Block Protect 0 (BP0) is set >> Chip status register: Write Enable Latch (WEL) is not set >> Chip status register: Write In Progress (WIP/BUSY) is not set >> Resulting block protection : all blocks >> programmer_unmap_flash_region: unmapped 0x0000000000000000 >> programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 >> to 0x0000000000000000 >> Some block protection in effect, disabling... Block protection could not >> be disabled! >> Chip status register is 0x1c. >> Chip status register: Block Protect Write Disable (BPL) is not set >> Chip status register: Auto Address Increment Programming (AAI) is not set >> Chip status register: Block Protect 3 (BP3) is not set >> Chip status register: Block Protect 2 (BP2) is set >> Chip status register: Block Protect 1 (BP1) is set >> Chip status register: Block Protect 0 (BP0) is set >> Chip status register: Write Enable Latch (WEL) is not set >> Chip status register: Write In Progress (WIP/BUSY) is not set >> Resulting block protection : all blocks >> Reading old flash chip contents... done. >> Erasing and writing flash chip... Trying erase function 0... >> 0x000000-0x000fff:W, 0x001000-0x001fff:S, 0x002000-0x002fff:W, >> 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, >> 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, >> 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, >> 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, >> 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, >> 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, >> 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, >> 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, >> 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, >> 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W, 0x020000-0x020fff:W, >> 0x021000-0x021fff:W, 0x022000-0x022fff:W, 0x023000-0x023fff:W, >> 0x024000-0x024fff:W, 0x025000-0x025fff:W, 0x026000-0x026fff:W, >> 0x027000-0x027fff:W, 0x028000-0x028fff:W, 0x029000-0x029fff:W, >> 0x02a000-0x02afff:W, 0x02b000-0x02bfff:W, 0x02c000-0x02cfff:W, >> 0x02d000-0x02dfff:W, 0x02e000-0x02efff:W, 0x02f000-0x02ffff:W, >> 0x030000-0x030fff:W, 0x031000-0x031fff:W, 0x032000-0x032fff:W, >> 0x033000-0x033fff:W, 0x034000-0x034fff:W, 0x035000-0x035fff:W, >> 0x036000-0x036fff:W, 0x037000-0x037fff:W, 0x038000-0x038fff:S, >> 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, >> 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, >> 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, >> 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, >> 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, >> 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, >> 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, >> 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, >> 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, >> 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, >> 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, >> 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, >> 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, >> 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, >> 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, >> 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, >> 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, >> 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, >> 0x06f000-0x06ffff:S, 0x070000-0x070fff:S, 0x071000-0x071fff:S, >> 0x072000-0x072fff:S, 0x073000-0x073fff:S, 0x074000-0x074fff:S, >> 0x075000-0x075fff:S, 0x076000-0x076fff:S, 0x077000-0x077fff:S, >> 0x078000-0x078fff:S, 0x079000-0x079fff:S, 0x07a000-0x07afff:S, >> 0x07b000-0x07bfff:S, 0x07c000-0x07cfff:S, 0x07d000-0x07dfff:S, >> 0x07e000-0x07efff:S, 0x07f000-0x07ffff:S >> Erase/write done. >> Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, >> failed byte count from 0x00000000-0x0007ffff: 0x3527c >> Your flash chip is in an unknown state. >> Please report this on IRC at chat.freenode.net (channel #flashrom) or >> mail flashrom(a)flashrom.org, thanks! >> programmer_unmap_flash_region: unmapped 0x0000000000000000 >> >> >

1 0

Flashrom Tutorial
by Anand Ratna 13 Dec '17

13 Dec '17

Sir, My Name is Anand Ratna, I did MTech in computer science. I am very much interested in Vlsi things. I am beginner, I want to understand the whole thing from beginning. I want to use flashrom to perform experiments on micro-controllers. But I am not getting how to install and use it. i don’t find any documents or tutorials. Please guide me. Thanks Anand Ratna

1 0

FAILED: ASUS P8H77-M PRO
by Lyubomyr Lytvynskyy 13 Dec '17

13 Dec '17

Hello. Today I try to flash BIOS on my motherboard to support NVMe devices and get terrible message in log "DO NOT REBOOT OR POWEROFF!" After reading BIOS again I saw that flash contents is not changed. Is it safe to reboot my PC now? Can you suggest how can I flash my BIOS? You can see read and write logs in attachment. Best regards, Lyubomyr

1 0

Re: [flashrom] Varification trouble - flashrom v0.9.9-r1954, Intel I210 NIC over SPI, Microchip SST25VF040B
by Lamont Dean 12 Dec '17

12 Dec '17

Okay, I'm seeing it better now and it isn't removing the block protection. On Tue, Dec 12, 2017 at 10:23 AM, Lamont Dean <lamont.dean(a)imsar.com> wrote: > Hello, > > Flashrom can find the Intel I210 NIC SPI connected to the SST25VF040B > flash chip and seems to program but fails to verify and gave me this email > to write to about it. The output is included below. Before and after a > power cycle the Intel I210 still says its in its unprogrammed state. > > I'd like to program a Microchip SST26VF016B flash in place of the > ...25VF040... but its not on the list so I'm going through the comments I > found on the wedsite Design Guide > <https://www.flashrom.org/Development_Guidelines>. I'm new to Linux and > things so we'll see how it goes. > > Any help you can offer would be greatly appreciated. > > Thanks, > > LaMont Dean > Hardware Engineer > ImSAR, LLC. > > ...flashrom> sudo flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c > SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin > flashrom v0.9.9-r1954 on Linux 4.4.38-tegra (aarch64) > flashrom is free software, get the source code at https://flashrom.org > > flashrom was built with libpci 3.3.1, GCC 5.4.0 20160609, little endian > Command line (7 args): flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c > SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin > Calibrating delay loop... OS timer resolution is 1 usecs, 2531M loops per > second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus > = 10022 us, 4 myus = 4 us, OK. > Initializing nicintel_spi programmer > Found "Intel Unprogrammed i210 Gigabit Ethernet Controller" (8086:1531, > BDF 01:00.0). > === > This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output > to flashrom(a)flashrom.org if it works for you. Please add the name of your > PCI device to the subject. Thank you for your help! > === > PCI header type 0x00 > Requested BAR is of type MEM, 32bit, not prefetchable > PCI header type 0x00 > Requested BAR is of type MEM, 32bit, not prefetchable > page_size=1000 > pre-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 > post-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 > The following protocols are supported: SPI. > Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping > SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 > RDID returned 0xbf 0x25 0x8d. probe_spi_rdid_generic: id1 0xbf, id2 0x258d > Found SST flash chip "SST25VF040B" (512 kB, SPI) on nicintel_spi. > Chip status register is 0x1c. > Chip status register: Block Protect Write Disable (BPL) is not set > Chip status register: Auto Address Increment Programming (AAI) is not set > Chip status register: Block Protect 3 (BP3) is not set > Chip status register: Block Protect 2 (BP2) is set > Chip status register: Block Protect 1 (BP1) is set > Chip status register: Block Protect 0 (BP0) is set > Chip status register: Write Enable Latch (WEL) is not set > Chip status register: Write In Progress (WIP/BUSY) is not set > Resulting block protection : all blocks > programmer_unmap_flash_region: unmapped 0x0000000000000000 > programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 > to 0x0000000000000000 > Some block protection in effect, disabling... Block protection could not > be disabled! > Chip status register is 0x1c. > Chip status register: Block Protect Write Disable (BPL) is not set > Chip status register: Auto Address Increment Programming (AAI) is not set > Chip status register: Block Protect 3 (BP3) is not set > Chip status register: Block Protect 2 (BP2) is set > Chip status register: Block Protect 1 (BP1) is set > Chip status register: Block Protect 0 (BP0) is set > Chip status register: Write Enable Latch (WEL) is not set > Chip status register: Write In Progress (WIP/BUSY) is not set > Resulting block protection : all blocks > Reading old flash chip contents... done. > Erasing and writing flash chip... Trying erase function 0... > 0x000000-0x000fff:W, 0x001000-0x001fff:S, 0x002000-0x002fff:W, > 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, > 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, > 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, > 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, > 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, > 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, > 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, > 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, > 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, > 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W, 0x020000-0x020fff:W, > 0x021000-0x021fff:W, 0x022000-0x022fff:W, 0x023000-0x023fff:W, > 0x024000-0x024fff:W, 0x025000-0x025fff:W, 0x026000-0x026fff:W, > 0x027000-0x027fff:W, 0x028000-0x028fff:W, 0x029000-0x029fff:W, > 0x02a000-0x02afff:W, 0x02b000-0x02bfff:W, 0x02c000-0x02cfff:W, > 0x02d000-0x02dfff:W, 0x02e000-0x02efff:W, 0x02f000-0x02ffff:W, > 0x030000-0x030fff:W, 0x031000-0x031fff:W, 0x032000-0x032fff:W, > 0x033000-0x033fff:W, 0x034000-0x034fff:W, 0x035000-0x035fff:W, > 0x036000-0x036fff:W, 0x037000-0x037fff:W, 0x038000-0x038fff:S, > 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, > 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, > 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, > 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, > 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, > 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, > 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, > 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, > 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, > 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, > 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, > 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, > 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, > 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, > 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, > 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, > 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, > 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, > 0x06f000-0x06ffff:S, 0x070000-0x070fff:S, 0x071000-0x071fff:S, > 0x072000-0x072fff:S, 0x073000-0x073fff:S, 0x074000-0x074fff:S, > 0x075000-0x075fff:S, 0x076000-0x076fff:S, 0x077000-0x077fff:S, > 0x078000-0x078fff:S, 0x079000-0x079fff:S, 0x07a000-0x07afff:S, > 0x07b000-0x07bfff:S, 0x07c000-0x07cfff:S, 0x07d000-0x07dfff:S, > 0x07e000-0x07efff:S, 0x07f000-0x07ffff:S > Erase/write done. > Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, failed > byte count from 0x00000000-0x0007ffff: 0x3527c > Your flash chip is in an unknown state. > Please report this on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom(a)flashrom.org, thanks! > programmer_unmap_flash_region: unmapped 0x0000000000000000 > >

1 0

Varification trouble - flashrom v0.9.9-r1954, Intel I210 NIC over SPI, Microchip SST25VF040B
by Lamont Dean 12 Dec '17

12 Dec '17

Hello, Flashrom can find the Intel I210 NIC SPI connected to the SST25VF040B flash chip and seems to program but fails to verify and gave me this email to write to about it. The output is included below. Before and after a power cycle the Intel I210 still says its in its unprogrammed state. I'd like to program a Microchip SST26VF016B flash in place of the ...25VF040... but its not on the list so I'm going through the comments I found on the wedsite Design Guide <https://www.flashrom.org/Development_Guidelines>. I'm new to Linux and things so we'll see how it goes. Any help you can offer would be greatly appreciated. Thanks, LaMont Dean Hardware Engineer ImSAR, LLC. ...flashrom> sudo flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin flashrom v0.9.9-r1954 on Linux 4.4.38-tegra (aarch64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.3.1, GCC 5.4.0 20160609, little endian Command line (7 args): flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin Calibrating delay loop... OS timer resolution is 1 usecs, 2531M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus = 10022 us, 4 myus = 4 us, OK. Initializing nicintel_spi programmer Found "Intel Unprogrammed i210 Gigabit Ethernet Controller" (8086:1531, BDF 01:00.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable page_size=1000 pre-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 post-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 The following protocols are supported: SPI. Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 RDID returned 0xbf 0x25 0x8d. probe_spi_rdid_generic: id1 0xbf, id2 0x258d Found SST flash chip "SST25VF040B" (512 kB, SPI) on nicintel_spi. Chip status register is 0x1c. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Resulting block protection : all blocks programmer_unmap_flash_region: unmapped 0x0000000000000000 programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 Some block protection in effect, disabling... Block protection could not be disabled! Chip status register is 0x1c. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Resulting block protection : all blocks Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:S, 0x002000-0x002fff:W, 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W, 0x020000-0x020fff:W, 0x021000-0x021fff:W, 0x022000-0x022fff:W, 0x023000-0x023fff:W, 0x024000-0x024fff:W, 0x025000-0x025fff:W, 0x026000-0x026fff:W, 0x027000-0x027fff:W, 0x028000-0x028fff:W, 0x029000-0x029fff:W, 0x02a000-0x02afff:W, 0x02b000-0x02bfff:W, 0x02c000-0x02cfff:W, 0x02d000-0x02dfff:W, 0x02e000-0x02efff:W, 0x02f000-0x02ffff:W, 0x030000-0x030fff:W, 0x031000-0x031fff:W, 0x032000-0x032fff:W, 0x033000-0x033fff:W, 0x034000-0x034fff:W, 0x035000-0x035fff:W, 0x036000-0x036fff:W, 0x037000-0x037fff:W, 0x038000-0x038fff:S, 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, 0x06f000-0x06ffff:S, 0x070000-0x070fff:S, 0x071000-0x071fff:S, 0x072000-0x072fff:S, 0x073000-0x073fff:S, 0x074000-0x074fff:S, 0x075000-0x075fff:S, 0x076000-0x076fff:S, 0x077000-0x077fff:S, 0x078000-0x078fff:S, 0x079000-0x079fff:S, 0x07a000-0x07afff:S, 0x07b000-0x07bfff:S, 0x07c000-0x07cfff:S, 0x07d000-0x07dfff:S, 0x07e000-0x07efff:S, 0x07f000-0x07ffff:S Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, failed byte count from 0x00000000-0x0007ffff: 0x3527c Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! programmer_unmap_flash_region: unmapped 0x0000000000000000

1 0

Error Message - Your flash chip is in an unknown state.
by Kazer Soze 12 Dec '17

12 Dec '17

Good morning I have a "W25Q128.V" chip on my board and i made a backup off the old boot. I have try to inject the new one but no luck at all. I have this error message appear. "Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x000af000! Expected=0xff, Found=0x00, failed byte count from 0x000af000-0x000affff: 0x500 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... FAILED at 0x00036bca! Expected=0x00, Found=0x04, failed byte count from 0x00000000-0x00ffffff: 0x1ea6 Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!" Any chance that you could help me please?

1 0

W836xx: QNAP 253a: flashrom -V
by uno 10 Dec '17

10 Dec '17

./flashrom -V -p internal flashrom v0.9.8-unknown on Linux 4.2.8 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian Command line (3 args): ./flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 745M loops per second, 10 myus = 10 us, 100 myus = 109 us, 1000 myus = 1009 us, 10000 myus = 10020 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Other" DMI chassis-type is not specific enough. DMI string system-manufacturer: "Default string" DMI string system-product-name: "Default string" DMI string system-version: "Default string" DMI string baseboard-manufacturer: "AMI Corporation" DMI string baseboard-product-name: "Aptio CRB" DMI string baseboard-version: "Default string" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Please send the output of "flashrom -V -p internal" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found ITE EC, ID 0x8528, Rev 0x0a on port 0x2e. ======================================================================== WARNING! You may be running flashrom on an unsupported laptop. We could not detect this for sure because your vendor has not setup the SMBIOS tables correctly. You can enforce execution by adding '-p internal:laptop=this_is_not_a_laptop' to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Aborting. Error: Programmer initialization failed. [/share/Public] #

1 0

Re: [flashrom] chipset not found
by David Hendricks 10 Dec '17

10 Dec '17

On Wed, Dec 6, 2017 at 8:29 PM, David Velasco <david(a)bemusic.al> wrote: > Hi carl, > > I have the following error: > > # flashrom --programmer internal > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > WARNING: *No chipset found. Flash detection will most likely fail.* > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > # flashrom --programmer internal > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > WARNING: No chipset found. Flash detection will most likely fail. > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > # flashrom > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Please select a programmer with the --programmer parameter. > Previously this was not necessary because there was a default set. > To choose the mainboard of this computer use 'internal'. Valid choices are: > internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, > it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, > nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, > ch341a_spi. > > > I can give you the result of > > lspci -nnvvvxxx > > Yes, please copy + paste lspci output to https://paste.flashrom.org/ .

1 0

chipset not found
by David Velasco 07 Dec '17

07 Dec '17

Hi carl, I have the following error: # flashrom --programmer internal flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. WARNING: *No chipset found. Flash detection will most likely fail.* No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. # flashrom --programmer internal flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. WARNING: No chipset found. Flash detection will most likely fail. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. # flashrom flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Please select a programmer with the --programmer parameter. Previously this was not necessary because there was a default set. To choose the mainboard of this computer use 'internal'. Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. I can give you the result of lspci -nnvvvxxx Thanks!

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom