I am experimenting with my new TUMPA board, never played with it before.
I have some MX25L6445E SPI flash chips at hand. This is a 8 pin chip, I connected them directly to SPI 1/2 interface on TUMPA. The datasheet can be found here:
http://www.macronix.com/QuickPlace/hq/PageLibrary4825740B00298A3B.nsf/h_Index/3F21BAC2E121E17848257639003A3146/$File/MX25L6406E,%203V,%2064Mb,%20v1.5.pdf
I used flashrom.exe from
http://www.flashrom.org, it is the latest build. OS is Windows XP 32 bit. Used libftdi_0.20_devkit_mingw32_08April2012 plus libusb 1.2.6.0.
After some experimenting, I can now read/write/erase the chip through SPI2 on TUMPA.
But I always had problem with SPI1. At first it read some wrong chip id, like 0xe1, 0x100b, the real chip id should be 0xc2 and 0x2017. Then later, flashrom simply reported that it couldn't find any more EEPROM device on SPI1. Does this mean SPI1 is defect? What should I check?
Good Probing on SPI 2:
Probing for Macronix MX25L6405, 8192 kB: probe_spi_mx_2017: id1 0xc2, id2 0x2017, id3 0xc2, id4 0x16
Probing for Macronix MX25L6445E, 8192 kB: probe_spi_mx_2017: id1 0xc2, id2 0x2017, id3 0xc2, id4 0x16
Found Macronix flash chip "MX25L6445E" (8192 kB, SPI) on ft2232_spi.
Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017
Bad probing on SPI 1:
Probing for Macronix MX25L1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff
Probing for Macronix MX25L3205, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff
Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff
Probing for Macronix MX25L6405, 8192 kB: probe_spi_mx_2017: id1 0xff, id2 0xffff
Probing for Macronix MX25L6445E, 8192 kB: probe_spi_mx_2017: id1 0xff, id2 0xffff
Probing for Macronix MX25L12805, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff