• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 2095 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.

XDS200 connection problem

Michael Antares
Intellectual 340 points

I just purchased an XDS200 debug probe. I have been successfully using an Olimex xds100v2 device but wanted a faster device. The target is a custom board with a TM4C1294 Tiva processor. Using CCS version 6.1.3, the connection is JTAG, the program is using TI-RTOS. The Test Connection test shows an OK scan test. However when I try to run the program (again, no problem using the XDS100v2 probe) i have no breakpoint response and no system_printf output. If I hover over the debug icon it reports that it is running. The pause button is grayed out. CCS is running in a Windows 10 Pro OS environment.

To say that I am at my wits end is an understatement :(.

  • 0
    TI__Guru**** 169894 points
    Hi,

    Would you mind attaching a screenshot of your CCS session when you see the problem? I can't precisely understand what you see as the problem.

    Regards,
    Rafael
  • 0 in reply to desouza
    Intellectual 340 points

    Thanks for the reply Rafael. I don't think a screen shot would help much but i'll try and describe my problem more clearly.

    Starting point is everything is cool when I use an Olimex XDS100v2 debug probe. Why not keep using it then? It's just to effing slow! So I spent $300+ to purchase a TI XDS200 probe, supposedly much faster downloads.

    Setting it up, I went into the .ccxml program, switched from the XDS100v2 probe to the XDS2xx USB Debug Probe and pressed the "Test Connection" button. It reported back that the test was successful, great, I thought. 

    However when I try to use it with my program it does not throw an exception but neither does it work. Doesn't respond to breakpoints (including stopping first at main), and doesn't display several printf statements that are in the program. If I hover over the green debug icon it reports that the program is running. Perhaps it is but if I can't set breakpoints or see  printf statements I'm working in the blind as you no doubt appreciate.

    Hopefully this will make my problem more understandable...

  • 0 in reply to Michael Antares
    Guru 92251 points

    Michael Antares said:
    Setting it up, I went into the .ccxml program, switched from the XDS100v2 probe to the XDS2xx USB Debug Probe and pressed the "Test Connection" button.

    The .launches subdirectory in a project contains some cached debug settings. Sometimes, when changing the Debug Probe in an existing .ccxml file I have seen strange failures which disappeared when deleted the .launches subdirectory and then started another debug session. Can you try that.

    If removing the .launches subdirectory doesn't fix the issue can you then try:

    1) Creating a new project, e.g. a hello world program, and see if the the XDS2xx USB Debug Probe can successfully work in a new project.

    2) Enable Debug Server Logging, and post the debug server log file for a failed debug session.

  • 0 in reply to Chester Gillon
    Intellectual 340 points
    Thanks Chester,
    I did not find a .launches subdirectory in my project but did as you suggested and downloaded a simple non-RTOS TivaWare project. It does respond normally to the XDS200 probe. SO....onwards and upwards. I'll enable the debug server logging as you suggest and go from there. I can also just really dumb down my program to bare essentials and see where it gets in trouble and/or compare what's different in the two programs config other than the obvious.
  • 0 in reply to Michael Antares
    Intellectual 340 points
    A further question is why my program is fine with the XDS100v2 debugger but not the XDS200...
  • 0 in reply to Michael Antares
    Intellectual 340 points
    Thanks again Chester,
    I did locate the .launch directory, deleted it as you suggested and, voila, problem solved. If you're ever in the San Francisco Bay Area I owe you a beer or two.
  • 0 in reply to Michael Antares
    TI__Guru**** 169894 points
    Michael,

    Thank you for reporting back your findings. By the way, Chester's suggestion is also mentioned in section 6 of the CCSv6 troubleshooting page at:

    processors.wiki.ti.com/.../Troubleshooting_CCSv6

    Regards,
    Rafael
  • 0 in reply to desouza
    Intellectual 340 points

    thanks for the info Rafael. I did look through that document but not thoroughly enough it seems...