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/IWR1642BOOST: "An attempt to connect to the XDS110 failed"

Part Number: IWR1642BOOST


Tool/software: Code Composer Studio

I am attempting to follow the instructions in the MMW SDK Users Guide (http://software-dl.ti.com/ra-processors/esd/MMWAVE-SDK/latest/exports/mmwave_sdk_user_guide.pdf, section 4. 4. How to connect xWR14xx/xWR16xx EVM to CCS using JTAG


My target setup is as follows:

When I attempt "Test Connection", I get the following error: (I have included the full output log at the end of this post)

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.

The board shows up in device manager as follows:

Following the recommendations from the error message, I attempted to update the XDS firmware using the readme directions from C:\TI\ccsv7\ccs_base\common\uscif\xds110, with the following result:


As you can see, there are two oddities: 1) Three fields are listed as <<Unknown>>, and 2) The device is apparently still in runtime mode even after the command to enter DFU mode.  

I tried this many times with the same result, including power cycling the board, and waiting longer or shorter times between sending the two commands.

After this, I tried the instructions for "Recovering a Bricked XDS110 Without JTAG".  However, when turning the board on with pin 97 grounded, I just get:

Any advice for how to successfully connect CCS to the board?

 

Additional Info:

My end goal is to run the capture demo.  I have successfully loaded "xwr16xx_capture_demo.bin" to the board, and can talk to the board just fine with teraterm on COM14: XDS110 Class Application/User UART.

 

Full JTAG connection failure error message:

 

[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)]------------------------------------

C:\Users\epahlke\AppData\Local\TEXASI~1\
CCS\TI\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 'jioxds110.dll'.
The library build date was 'Feb 8 2018'.
The library build time was '18:36:28'.
The library package version is '7.0.188.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

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

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

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the ReadMe.txt file there
for instructions.

[End: Texas Instruments XDS110 USB Debug Probe_0]

 

  • Hi,

    I have re-assigned this thread to the Emulation team

    thank you
    Cesar
  • Hi,

    Please apologize for the delay; your thread went under our radar.

    The problem you are seeing is described in further detail at:
    software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html

    Given that the Windows Control Panel shows the device properly instantiated (despite the xdsdfu certainly showing unexpected results) and you mentioned you are connected via Teraterm to the board, can you try to disconnect from it and try to connect using CCS? I suspect the Teraterm may be hijacking the XDS110 port, preventing anything else to connect to it.

    If this board still fails to work in this host, you can try to use it in another host and see if it works properly. This helps isolate if the issue is with the board or with the host. A similar thing with the boards: if you have a different board, you can compare its functionality in the original host.

    One last attempt that could be tried is to re-write the XDS110 bootloader. However, it also requires the pod to be put in "manual" mode, which is something you are unable to do.

    You mentioned that you tried to recover a bricked XDS110; if you followed the details shown in the link below, you already exhausted pretty much all the options to recover the pod (if it is, in fact, inoperative):
    processors.wiki.ti.com/.../XDS110

    In case you try all the alternatives below without success, you may need to return or repair the board.

    Hope this helps,
    Rafael