• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1158 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.

Error occurs when use XDS100V3 to connect CC3200 in CCS6

YZ You
Prodigy 30 points

Other Parts Discussed in Thread: CC3200

Hi,

I got a trouble when i used  XDS100V3  to debug CC3200 in CCS6.

The hardware connection between XDS100V3 and CC3200 as following picture shows:

  I connect xds100v3 to cc3200 and config the connection configuration in CCS6, The test connection in cc6 is successful.

 but when i click debug button to debug, the error occurs:

I hope somebody can help me to slove this issue, i wil appreciate your help.

  • 0
    TI__Guru**** 171809 points

    Hi,

    The messages indicate the hardware connection is fine, but the problem may be in the target configuration file (an invalid configuration of the XDS100v3 or an invalid device, for example) or in the device itself (the cortex core is being held in reset or is not powered properly).

    Unfortunately I do not have a suitable CC3200 board to connect an external JTAG debugger, but the screenshots below should be enough to enable connecting with the default options.

    Tab basic:

    Tab advanced:

    These settings were obtained using CCSv6.1.2.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 30 points
    Hello Rafael,

    Thanks for your quick reply!
    I think my target configuration in CCS6 is same as your picture shows and i am sure the target configuration is right.
    Becasue i can enter debug interface and debug my firmware when i first click debug button.
    but the second time i want to debug by clicking the debug button, the error occurs(as the bottom picture in my first post shows).
    And, if i restart my computer, then i can enter debug interface just at every first time.
    I don't why this happens.
  • 0 in reply to YZ You
    Prodigy 30 points
    Hello Rafael,

    I have sloved this issue, The root reason for this problem is the clock of debuger, 1.0M is too high, i slow down it to 200Khz.
    Now, the debug is working very well.
    Thanks for you help again.