• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 650 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/TMDSEMU110-U: Can't get TMDSEMU110-U to work with any usb hub

Thales Maia
Prodigy 80 points
Part Number: TMDSEMU110-U

Tool/software: Code Composer Studio

Hello, I'm running Ubuntu 18.04 LTS. I'm configuring a new target, and when I test it, it only works when I direct connect the device.

I have three different hubs and none of them worked.

F280049 and XDS110 (TMDSEMU110-U).

Here are the outputs:

Using hub usb

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

/home/thales/.ti/ccs1010/0/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioxds110.so'.
The library build date was 'May  7 2020'.
The library build time was '20:44:54'.
The library package version is '9.2.0.00002'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-261' (0xfffffefb).
The title is 'SC_ERR_XDS110_FAIL'.

The explanation is:
Invalid response was received from the XDS110.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Without using a usb hub:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

/home/thales/.ti/ccs1010/0/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioxds110.so'.
The library build date was 'May  7 2020'.
The library build time was '20:44:54'.
The library package version is '9.2.0.00002'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Cable length doesn't seems to be a problem.

It's really difficult to use it without a hub since I only have two ports. I appreciate any suggestions.


Another odd behavior is that serial number is filled with zeros.

  • 0
    TI__Guru**** 171104 points

    Hi,

    I am not sure why the USB Hub is failing but, given the wide variety of hub chipsets and models, I would suggest trying a different unit to see if the issue is intrinsic to your unit. 

    Also, check if your HUB is powered - despite the XDS110 does not use much power, it may have trouble if other peripherals are attached as well. 

    I have a USB2.0 Belkin Hub and an USB3.0 Inland Hub that I used to connect various boards and the standalone XDS110 - both of them are powered, but unfortunately locked on my office due to the quarantine (otherwise I would provide the models and chipsets here for your reference). 

    The XDS110 unit not having the serial number is not relevant to the ability to connect. If you want, you can try to write the serial number by following the procedure shown at the XDS110 page at:

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 80 points

    Thanks for your reply .

    Here are the models that I tried.

    Bus 002 Device 119: ID 0a05:7211 Unknown Manufacturer hub -> Model 1
    Bus 002 Device 119: ID 0a05:7211 Unknown Manufacturer hub -> Model 2
    Bus 002 Device 122: ID 05e3:0608 Genesys Logic, Inc. Hub -> Model 3

    After your suggestion, I tried again all my previous test.

    I got it working with and external power source and the model bellow.

    Bus 002 Device 122: ID 05e3:0608 Genesys Logic, Inc. Hub

    It is really difficult to know the chipset when you buy a HUB, and I need to buy another one.

    Any suggestion?

  • 0 in reply to Thales Maia
    TI__Guru**** 171104 points

    Hi,

    The chipset of your Hub is manufactured by Genesys Logic but you are right: it is very difficult to find which Hub comes with what chipset. 

    What I would try is get a powered Hub from a reputable brand and see if they accept exchanges or returns in case it does not work for you. Here in the US brands such as Anker, Belkin or Trendnet usually have a reasonable reputation but, since nowadays the brands change their designs very quickly, I wouldn't be able to make a solid recommendation. Sorry.

    Regards,

    Rafael