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/LAUNCHXL2-570LC43: LAUNCHXL2-570LC43

Part Number: LAUNCHXL2-570LC43

Tool/software: Code Composer Studio

Dear friends,

I am using LAUNCHXL2-570LC43 development kit for some applications and every thing works well on my laptop wich has windows 10, but when I try to use the same board with PC windows 7 with the same CCS I always get an error that the target is not connected, as shown below

I tried to install XDS110 driver, and reinstall CCS but always the same probelm.

on the laptop same CCS and same board work very well !!!!!! 

and when I click on test connection I get this output:

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

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

[Result]


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

C:\Users\ste\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 'Jan 24 2019'.
The library build time was '14:27:46'.
The library package version is '8.0.903.6'.
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]

-----------------------------------------------

could you please give me any suggestions for this problem ?

best regards

  • Hi,

    The conditions for the error to occur are well known and reported in the Debugging JTAG page at:

    software-dl.ti.com/.../ccs_debugging_jtag_connectivity_issues.html

    However, in your particular scenario I would first check the ability to find the probe outside of the CCS environment - you can check the utilty xdsdfu mentioned in the section "Updating the XDS110 Firmware" of the XDS110 page below
    dev.ti.com/.../

    If that still does not work, I would proceed to try to reinstall the Windows drivers, as described in the section "Troubleshooting" of the page above.

    There are a few other cases reported that deal with a similar scenario (the debug probe seems being already in use by another process). Unfortunately these issues are very difficult to reproduce given they seem very tied to the specific host.

    Hope this helps,
    Rafael
  • Dear Rafael,

    thank you very much for your quick answer.

    I tried all the steps but still not solved.

    as shown below no device found at all ....

    best regards

    Samer

  • I found the solution, all the USB ports on the pc are USB3 and USB3.1 so I installed an adapter for USB2 which work very well only with these Ports

    so maybe the XDS driver should be updated to be compatable with the new USB ports

    best regards

    thanks

  • Samer,

    Please apologize for the delay; I was out of the office yesterday.

    Thank you for providing the outcome of your scenario. I can say I haven't heard of this yet - I have been using XDS110 probes in USB3 ports for years now without a problem. All systems I have been using these are Dell desktops and laptops, as well as Toshiba laptops.

    I wonder if there is a similar incompatibility with the same USB3 Renesas chipset that used to cause problems with XDS200 Debug Probes. Details can be seen at the Troubleshooting section of the XDS200 page at:
    dev.ti.com/.../

    Regards,
    Rafael