• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 1981 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/LAUNCHXL-CC2640R2: Error connecting to the target: (Error -275 @ 0x0)

Inseob Kim
Intellectual 545 points
Part Number: LAUNCHXL-CC2640R2


Tool/software: Code Composer Studio

Hi there,

After upgraded emulation package version 8.2.0.00004, I can't flash program to the launchpad with below an error message:

====== Texas Instruments XDS110 USB Debug Probe/IcePick_C ======
Error connecting to the target:
(Error -275 @ 0x0)
The attempt to poll a target device exceeded its timeout limit.
The utility or debugger has requested that a target device be
repeatedly accessed for a specific data or status value.
This has failed because the built-in limit for the maximum number
of attempts when polling the JTAG scan-path has been exceeded.
(Emulation package 8.2.0.00004)
====================== Retry / Cancel ======================

Sometimes I can't avoid this message even if restarting CCS.
How can I resolve this issue?

My CCS version 9.0.1

Best regards.

  • 0
    TI__Guru**** 171309 points

    Hi,

    Taking into consideration this worked before the update, I can think of one important change made to the newest TI Emulators package and XDS110 Debug Probes: the default TCLK speed.

    With this new emupack, some performance improvements enabled higher speeds up to 14MHz and the default was set to 8MHz, which was tested to be compatible with the Launchpads and development kits. However, this may be too high depending on the length of the connections and other physical factors.

    In this case, the first thing I would try is to reduce the TCLK to the previous default of 2.5MHz and see if you can get a stable connection.

    Details can be seen in the clip below, where I explore various scenarios to test the TCLK.
    https://www.youtube.com/watch?v=mKxaztkCsYw&t=27s

    It may simply be a coincidence, but another scenario is that this particular issue may be caused by faulty code loaded to the target. 

    https://e2e.ti.com/support/tools/ccs/f/81/t/503371 

    Hope this helps,

    Rafael