vincent

Members
  • Content Count

    6
  • Joined

  • Last visited

Everything posted by vincent

  1. Hi Jon, Thank you for your involvement. Did you receive the Tripp Lite hub and manage to reproduce the issue? Best regards, Vincent
  2. Hi Jon, The two hubs references are: - Tripp Lite U225-004-R - HP Z Display Z24i 24" Monitor (Integrated USB hub) Best regards, Vincent
  3. Hi Jon, Thank you for your message. We already used the concerned USB hubs with other peripherals (USB keys, Xilinx USB Cables, etc...). I logged the output of the dmseg for the two following scenarios: Scenario 1: When Digilent JTAG-HS3 cable is connected to USB port (No USB hub): [63143.414614] usb 3-6: new high-speed USB device number 56 using xhci_hcd [63143.431078] usb 3-6: New USB device found, idVendor=0403, idProduct=6014 [63143.431087] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [63143.431093] usb 3-6: Product: Digilent USB Device [63143.431097] usb 3-6: Manufacturer: Digilent [63143.431100] usb 3-6: SerialNumber: 210299A17A95 [63143.435385] ftdi_sio 3-6:1.0: FTDI USB Serial Device converter detected [63143.435453] usb 3-6: Detected FT232H [63143.435459] usb 3-6: Number of endpoints 2 [63143.435463] usb 3-6: Endpoint 1 MaxPacketSize 512 [63143.435469] usb 3-6: Endpoint 2 MaxPacketSize 512 [63143.435474] usb 3-6: Setting MaxPacketSize 512 [63143.435958] usb 3-6: FTDI USB Serial Device converter now attached to ttyUSB0 [63143.449324] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [63143.449353] ftdi_sio 3-6:1.0: device disconnected Then the bitstream loading via Impact works. Scenario 2: When USB hub is connected alone (No peripherals connected to the USB hub): [62924.426767] usb 3-13: new high-speed USB device number 54 using xhci_hcd [62924.439644] usb 3-13: New USB device found, idVendor=05e3, idProduct=0608 [62924.439654] usb 3-13: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [62924.439659] usb 3-13: Product: USB2.0 Hub [62924.440734] hub 3-13:1.0: USB hub found [62924.441060] hub 3-13:1.0: 4 ports detected When Digilent JTAG-HS3 cable is connected to the USB hub: [62987.236178] usb 3-13.2: new high-speed USB device number 55 using xhci_hcd [62987.252391] usb 3-13.2: New USB device found, idVendor=0403, idProduct=6014 [62987.252401] usb 3-13.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [62987.252406] usb 3-13.2: Product: Digilent USB Device [62987.252410] usb 3-13.2: Manufacturer: Digilent [62987.252414] usb 3-13.2: SerialNumber: 210299A17A95 [62987.255567] ftdi_sio 3-13.2:1.0: FTDI USB Serial Device converter detected [62987.255642] usb 3-13.2: Detected FT232H [62987.255649] usb 3-13.2: Number of endpoints 2 [62987.255655] usb 3-13.2: Endpoint 1 MaxPacketSize 512 [62987.255661] usb 3-13.2: Endpoint 2 MaxPacketSize 512 [62987.255667] usb 3-13.2: Setting MaxPacketSize 512 [62987.256331] usb 3-13.2: FTDI USB Serial Device converter now attached to ttyUSB0 [62987.270520] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [62987.270528] ftdi_sio 3-13.2:1.0: device disconnected Then the bitstream loading via Impact doesn't work. Best regards, Vincent
  4. Hi Jon, Thank you for your message. We are on Fedora 20 and unfortunately can't update to Vivado since our FPGA devices are quite old and only supported under Impact. Best regards, Vincent
  5. Hi Jon, Thank you for your support. Both hubs we tried on Linux were externally powered. A try on a Windows machine revealed a perfect behavior of both cables and hubs. Best regards, Vincent
  6. Hi, We would like to use several Digilent JTAG-HS3 cables (up to 8) on a PC with Linux via one or several USB hubs since the number of USB ports on all computers is limited but we currently don’t manage to make working a single JTAG-HS3 with a PC with Linux via a USB hub. We tested on two different usb hubs (1 dedicated device, 1 integrated to a screen) and computers (1 desktop, 1 laptop) but the only configurations which work are: no usb hub and either a usb port of the laptop or a usb port on the rear panel of the desktop. Can someone say us if similar issues are already known with this cable and/or test such a configuration by its own and come back on this thread? The Impact version to use is the 14.7 one. Best regards, Vincent