10-25-2014 04:11 AM
I just bought a brand new Platform Cable USB II from DigiKey for 220 EUR.
When I plug it in, it shows up as "unconfigured Cypress FX2" with USB IDs 04b4:8613.
This means, the EEPROM has not been programmed during production.
(Can provide serial number and close up photos if desired.)
Having used the Cypress FX2 USB chip myself years ago, I think I can program the EEPROM myself. However, I wonder which firmware file is the correct one. I cannot find any docs on that:
Would be a good idea to add some comments to the udev rules regarding this.
Q: Which of these hex files is the one for the Platform Cable USB II ?
Q: What does xusbdfwu.hex do and is it needed?
10-25-2014 08:50 AM
Recently (last week),
Microsoft released a patch that bricks non-FTDI chips (clones). It clears the code on ckoned USB devices, rendering them useless.
Look on Ars Technia, TechDirt, for the details.
If you just bought this from DigiKey, you should be contacting them for support.
10-25-2014 09:30 AM
OK ....so what?
I don't understand what that has to do with this case?
1. This is not an FTDI device but a Cypress FX2
2. This is an original Platform Cable USB II from all I can tell no clone.
3. This platform cable has not seen a single Windows box yet; I'm running Linux
I can of course send it back but I'd like to use the device.
10-25-2014 09:49 AM
To recap: Bought brand new from DigiKey for 220 EUR, put out of box (with all Xilinx papers in it, including 35 page DS593 color print on glossy paper), plugged into Linux computer and it enumerates as 03fd:0008.
The paper box with Xilinx logo says:
I probably could send it back but I'd like to use the device NOW, especially if it can be easily fixed.
10-26-2014 09:00 AM
By changing the udev rules to execute fxload (*_xp2.hex) once it sees the IDs 03fd:0008 (=unconfigured FX2), the platform cable is fully functional.
Trying to program the EEPROM on the platform cable to store the correct IDs or the firmware does not succeed.
It seems there's something wrong with the cable board.
So, I CAN work with it but since I occasionally use an FX2 device as well, the IDs collide with the platform cable which is unfortunate.
10-27-2014 01:50 AM
OK, managed to store IDs 02fd:0013 in EEPROM with Cypress development software. Now works as expected.
Still, could anyone please document which .hex file is for which platform cable?