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.

CC debug error, CC1310DK, An attempt to connect to the XDS110 failed

Hi,

I'm assuming this is an easy fix for something I'm missing, I haven't played with uController for at least 3 years.

I have just received and now installed all the software for the CC1310DK, and I can't get CC to connect and debug the board. Smart RF Studio, SmartRF Flash all find the board no worries,  CC doesn't

The error message I get is:

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 6.0.222.0)

That doesn't particularly make sense to myself since the board is new so the firmware should be good, and the other programs don't seem to have an issue.

Details:

  • CC = v6.1.3.00033 
  • Windows 8.1
  • CC1310DK,  board for debug is SmartRF06

My guess  is there i some link the background I must set to CC.  CC was installed tot he default c:\ti space, the others to their default c:\programs files(x86)\Texas Instruments\..

Best Regards,

  • Mike Edmondson said:
    CC1310DK,  board for debug is SmartRF06

    The SmartRF06 is fitted with a XDS100v3 emulator, but from your error message the connection in CCS has been set to "Texas Instruments XDS110 USB Debug Probe".

    Try setting the connection in CCS to "Texas Instruments XDS100v3 USB Debug Probe".

  • Hi,

    I've meaning to reply to this for months sorry.

    If someone else hasn't had to deal with setting up environments before, the setting is deeper within the project properties, not under the big green button on the UI. (I knew it was simple)

    Note, there are all different types of debug probes, readup what each board actually has and make sure you have the drivers.


    (Things have changed since using non-os, old 1990s 8051 microcontroller architectures. :) -- Awesome, but you need to know their hidden tricks now)