• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 547 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/XDS560TRACE: xds200

sathish kumar33
Prodigy 40 points
Part Number: XDS560TRACE
Other Parts Discussed in Thread: CC2640, CC2640R2F

Tool/software: Code Composer Studio

HHello,

 In past few days the XDS200 Emulator is not working properly.

 

hello ti,

   We are using xds200 debugger for our custom design  board to flash and debug the code (ccs2640). it was reliably working fine but suddenly it stopped programming.

Following is the Error Message while flashing our board using XDS200 jtag through Code Composer Studio.

 Cortex_M3_0: GEL Output: Memory Map Initialization Complete.

Cortex_M3_0: Failed Board Reset: (Error -180 @ 0x0) Internal error: Invalid error code. Restart the application. If error persists, please report the error. (Emulation package 6.0.407.3) 

IcePick_C: Error connecting to the target: (Error -180 @ 0x0) Internal error: Invalid error code. Restart the application. If error persists, please report the error. (Emulation package 6.0.407.3) 

 When we connect to smart flash Application xds200 not able to recognize the processor.

We kindly request you to  provide technical help to resolve this error. 

 

  • 0
    TI__Guru**** 171309 points
    Hi,

    This error is invalid for the XDS200, therefore I suspect something else may be causing CCS to be confused.

    Does the "Test Connection" button work or throws a different error? If it throws a different error, can to compare it against the list shown at the reference below? (you can search for the error number)

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

    The fact you mentioned this configuration worked well in the past, can you think of any difference that was made to your setup? Things such as updates to CCS, to Windows or something applicable to your hardware (jumpers, different power supply voltages, etc.).

    One additional detail is that you mention multiple types of Debug probes in your post and tags. In this case, make sure you are using the exact combination of Debug Probe and device.

    Despite I don't have a CC2640 device here (only a CC2640R2F), this configuration works well in my environment here.

    Hope this helps,
    Rafael