Yesterday, I wanted to dump content of flash memory using TUMPA SPI interface. When I ran "flashrom -p ft2232_spi:type=tumpa,port=B", Flashrom was unable to find the board. Later it turned out that my TUMPA had wrong pid (0x6010). Because the FT_Prog is available only for Windows I was looking for some Linux alternative but the only thing I found was ftdi-eeprom package in Debian repos which allowed me to dump the EEPROM content but not change the pid using some easy way. Later I was checking dmesg and noticed some strange USB related messages. I ran lsusb and I saw nameless 0x0000:0x0000 device which l identified as TUMPA. Now whenever TUMPA is connected to a PC (Tried two different PC with Windows and Linux) it always does have 0000 vid and pid.
http://rtr.ca/ft232r/ is some program to set parameters of FT2232 (EDIT: Noticed that it is for FT232, that is the reason it fails) (page is down now, you can look at it at
http://web.archive.org/web/20131230143543/http://rtr.ca/ft232r/) but it just fails with "eeprom reconstruction self-test failed, aborting". Here is dmesg output after TUMPA is connected:
usb 6-1: new high-speed USB device number 47 using ehci-pci
usb 6-1: New USB device found, idVendor=0000, idProduct=0000
usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 6-1: Product: USB Serial Converter
usb 6-1: Manufacturer: Acme Inc.
There is no more /dev/ttyUSB0 or /dev/ttyUSB1. I also dumped the EEPROM contents second time and they match the ones from when it was working.
Is there any way to revive it? Or is it dead?
EDIT2:
Not really sure how I managed to do this, but my TUMPA is back (still wrong pid, gonna use FT_Prog now though).