Forum Post: Two XDS100v2 connected via USB 3.0

Hello,

I faced into a problem when using two XDS100v2 which are connected to my PC via USB 3.0.

To be concrete, our SAFETI-HSK-RM48 kit has two XDS100v2 build in which are connected via a TUSB8040A hub (also on the board). When I connect the kit to the PC I can normally distinguish between the two XDS100v2 with their serial number (TIMON001 and TISAF001). This is working very well when the kit is connected to a USB 2.0 EHCI Controller, but not if connected to a USB 3.0 XHCI controller.

In the case the kit is connected to an XHCI controller CCS 6.0 will always connect to the XDS100v2 which is on the second port of the TUSB8040A hub (SN: TIMON001).

I couldn't find any differences in the Windows Device Manager between if the kit is connected to the EHCI or to the XHCI.

The xds100serial.exe tool shows me exactly the same output, no regards of the kit is connected to the EHCI or the XHCI:

0403/a6d0  XDS100v1/v2     TIMON001    Texas Instruments Inc.XDS100 Ver 2.0
0403/a6d0  XDS100v1/v2     TISAF001    Texas Instruments Inc.XDS100 Ver 2.0

One interesting point is, that the Windows Device Manager shows me different "Device Instance Path" and "Siblings" for the same emulator, regardless if the kit is connected via EHCI or XHCI. The following list should clarify what I mean, please compare the "Device Instance Path" and "Siblings" for the same ports. The "Device Instance Path" seems to be correct, but the "Siblings" seems to be inverted:

• Device Instance Path
  • Port_#0001.Hub_#0009
    • USB\VID_0403&PID_A6D0\TISAF001
  • Port_#0002.Hub_#0009
    • USB\VID_0403&PID_A6D0\TIMON001
• Siblings
  • Port_#0001.Hub_#0009
    • USB\VID_0403&PID_A6D0\TIMON001
  • Port_#0002.Hub_#0009
    • USB\VID_0403&PID_A6D0\TISAF001

Has somebody already tried such a setup with two XDS100v2 at a PC with USB 3.0?
Is there a workaround available?

Thanks,
Christian