Avnet Virtex-4 LX Evaluation Kit USB FX2 Issue

Hello,

I have recently bought a Virtex-4 LX25 evaluation board from Avnet. It has Cypress FX2 chip for USB 2.0 communication support. The generic USB driver provided by Cypress is of no use to me. Whenever I connect the USB of the board with the PC, the immediate message is "Unknown USB device". This happens because the VID and PID of the device received at the host is 0. I have tried installing the driver with EZUSBw2k.inf as well as CyUSB.inf but none has worked. Is there any body out there who has used the FX2 with Cypress provide generic USB driver? If someone has used USB with an Avnet board, that will prove very helpful to me. Looking forward to a sound advice. Thanks.

- Javed Rabbani

Reply to
jrabbani
Loading thread data ...

Sounds similar to the issue i had with the Cypress FX2 microcontroller. On some computers it does not start-up properly, even with the proper drivers installed (it was detected as an 'uknown device', while it should have worked even without any firmware). It turned out, that it works with other PC's i've tested it with (have you checked that?). In order to put it into working order, i had to program the onboard I2C EEPROM with startup bytes (i found the EEPROM image in an archive with the FX2 starter kit documentation). I don't know if your board is fitted with an EEPROM for firmware storage or if it uses another way to boot-up (I don't have the login/pass the Avnet website asked me about:)), but you might want to check that.

Reply to
Marek Kraft

: Hello,

: I have recently bought a Virtex-4 LX25 evaluation board from Avnet. It : has Cypress FX2 chip for USB 2.0 communication support. The generic : USB driver provided by Cypress is of no use to me. Whenever I connect : the USB of the board with the PC, the immediate message is "Unknown : USB device". This happens because the VID and PID of the device : received at the host is 0. I have tried installing the driver with

If you are seeing a VID and PID of 0 this suggests a hardware problem at a lower level than drivers! - I had this when shorting the USB D- to ground (got the pinout backwards on a connector). Possibly a bad cable or damaged PCB, or perhaps the CY7C68013 isn't correctly powered or booting. If there is bad firmware in the I2C eeprom (U12) you can try breaking the SCL and SDA tracks after the pullups and before the EEPROM to make the CY7C boot into its default state. This should be a last resort as it looks like there're no jumpers so you'd have to cut the tracks...

I don't know if bad firmware can lead to the chip failing badly enough that enumeration fails.

hth cds

Reply to
c d saunter

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.