1. Home
  2. Field-Programmable Gate Arrays
  3. Problem using xilinx usb download cable in linux

Problem using xilinx usb download cable in linux

Hi all,

I have spent quite some time on the net trying to find info on how to get the xilinx usb download cable to work with linux and I have reached a dead end. :(

I have installed the usb-driver from

formatting link
and I have managed to light up the green led to the usb download cable on the spartan 3e starter kit. The green led is going black every 6-8 second and then green again. I don't manage to get a connection to the board using Impact. lsusb gives me the following:

Bus 005 Device 012: ID 03fd:0008 Xilinx, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x03fd Xilinx, Inc. idProduct 0x0008 bcdDevice 0.00 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 2 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 280mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted cannot read device status, Operation not permitted (1)

and Impact says:

Connecting to cable (Usb Port - USB21). Checking cable driver. File version of /usr/share/xusbdfwu.hex = 1025(dec), 0401. libusb-driver.so version: 2007-10-08 15:43:55. Cable connection failed. Reusing B406EC01 key. Reusing 3806EC01 key. Reusing B506EC01 key. Reusing 3906EC01 key. Reusing B606EC01 key. Reusing 3A06EC01 key. Reusing B706EC01 key. Reusing 3B06EC01 key. PROGRESS_END - End Operation. Elapsed time = 0 sec. Cable autodetection failed. WARNING:iMPACT:923 - Can not find cable, check cable setup !

Any idea where to look??

Thanks!

/Roger

Reply to
roger
Loading thread data ...

I have not heard of this behaviour previously. For me this seems to indicate that the cable gets dis- and reconnected all the time. Do you see reoccuring dis-/reconnects in "dmesg".

What are the permissions on /dev/bus/usb/005/012 (or the current location of the cable)? This error might show there is a permission problem. You did add the MODE-line to an udev rules-file?

If you preload libusb-driver-DEBUG.so instead of libusb-driver.so you get a much more detailed output, which could tell why impact does not find the device (which according to your lsusb-output has the correct firmware loaded).

Regards, Michael

Reply to
Michael Gernoth

Thanks for the tips! I'll try that out soon.

/Roger

Reply to
roger

Hi Michael,

The permissions on /dev/bus/usb/005/016 is:

crw-rw-r-- 1 root root 189, 512 2007-11-12 18:37 001 crw-rw-rw- 1 root root 189, 527 2007-11-12 21:45 016

from the dmesg output you can see that the cable jumps around between different buses:

[14746.456000] usb 5-2: new high speed USB device using ehci_hcd and address 14 [14746.588000] usb 5-2: configuration #1 chosen from 1 choice [14746.972000] usb 5-2: USB disconnect, address 14 [14748.984000] usb 1-2: new full speed USB device using uhci_hcd and address 10 [14749.124000] usb 1-2: not running at top speed; connect to a high speed hub [14749.148000] usb 1-2: configuration #3 chosen from 1 choice [14778.480000] usb 1-2: USB disconnect, address 10 [14780.092000] usb 5-2: new high speed USB device using ehci_hcd and address 16 [14780.224000] usb 5-2: configuration #2 chosen from 1 choice

Any idea why I get this behaviour?

Thanks!

/Roger

Reply to
roger

That is ok.

There is probably a problem communicating at USB 2.0 with the cable and it falls back to USB 1.1 but then gets reconnected to the 2.0 hub. Try 'rmmod ehci_hcd' (as root) which disables the USB 2.0 part and see if it is stable at USB 1.1. If it is, try swapping the USB A-B cable.

Regards, Michael

Reply to
Michael Gernoth

Where are you plugged in? It sounds as if you are on a port that isn't giving enough power (not that the cable needs much).

If you aren't already, try plugging into the USB ports on the back of the machine that are directly part of the mainboard or I/O board. Often the front-panel ports are underpowered, and hubs just make it worse.

Plugging into a hub with an AC adapter would help if this is the case also.

ken

Reply to
Ken Ryan

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.