• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 2445 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Looking solution for Debugging Error -275 "timeout"

Shen Fu
Prodigy 50 points
Other Parts Discussed in Thread: CC1310

Hello, 

I am using a XDs100v3 to debugge CC1310 in my Code Composer Studio, but when I try to target the configuration, it always return error message like this:

"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 6.0.83.1) "

I have tried adjusting my JTAG connection for many times and still got that error, Does anyone know what are the possible reasons for that? Any suggestions will be appreciated. Thanks!

Shen

  • TI__Guru**** 169754 points

    Shen,

    Can you check section 5.22 of the page below?

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    Out of the scenarios I have seen reported on this issue, the software is usually causing the device to be somehow "locked" and therefore some sort of reset is required.

    Specifically for CC1310, you can try to launch the debugger without a project (see this short video) and, before connecting to the Cortex core, you can issue a mass erase from the Scripts menu.

    Hope this helps,

    Rafael

  • Mastermind 9045 points

    Hi,

    Do you use customized PCBA? According to my experience, if circuit design is ok then this issue might be caused by two reasons:

    (1) The PCBA is not well made. If you soldered the CPU then you have to ensure it is well soldered and flux are well cleaned.

    (2) The flash memory is erased but not fully erased. Well, this is a bit complicated to explain. CC26xx/CC13xx use the last sector of internal flash memory to store some information for boot-up. If this sector is corrupted then it can't boot correctly. For this case, you can use "Flash Programmer 2" to re-program the CPU and then use debugger to connect it.

    There might be some other issues and you should always check the circuit is well designed and power is supplied.