• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 176 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/AWR1642BOOST: CCS/AWR1642

Claudio ANUCHNIK
Expert 1100 points
Part Number: AWR1642BOOST

Tool/software: Code Composer Studio

Hi all,

I debug my project(s) using CCS and after I quit the debugger if I want to make some changes and to debug it again, when I try to connect to the devices I get a popup message box wiht the following message:

__________________________________________________________

Error connecting to the target:
(Error -260 @ 0x0)
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.
(Emulation package 8.1.0.00012)

___________________________________________________________

It doesn"t matter if I restart or not power in the AWR1642BOOST board

I have to restart CCS in order to debug again

It happens for CCS9, CCS8 and CCS7

Thank you

Claudio

  • 0
    TI__Guru*** 149044 points
    Hi,

    We are checking with the CCS team and will get back to you

    thank you
    Cesar
  • 0
    TI__Guru**** 171104 points
    Claudio,

    That is rather unusual IF you are only working from inside CCS all the time.

    The explanation for the error is shown in the Debugging JTAG page below (just search for the error number):
    software-dl.ti.com/.../ccs_debugging_jtag_connectivity_issues.html

    The error itself is that the XDS110 endpoints could not be found. That or they are locked by another application. I tried to reproduce this here to no avail, and the only scenario where I could see this happening is if you are also running the mWave Demo Visualizer together with CCS.

    Apart from this, I can't necessarily pinpoint a root cause for the error, although if you are running the prior CCS releases before CCSv9 and is not closing them, there is a chance they are holding onto the XDS110 endpoint and preventing another version to connect. The fact you can connect at least once seems to indicate this to me.

    I will try to think about additional details and report back if I find anything relevant.

    Hope this helps,
    Rafael