• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1116 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 and Luminary Micro ICDI: first time "error connecting to the target", second time works

Simon Obermeier
Prodigy 40 points

Other Parts Discussed in Thread: TM4C123GH6PGE

Hi,

I use:
- CCSv5.5 under Linux Ubuntu 13.10 x64
- Luminary Micro "BD-ICDI-B" JTAG Programmer
- Tiva TM4C123GH6PGE microcontroller as target (connected over JTAG)

All works fine, but there is one Problem. Every time I click on the "debug" symbol in CCS, there is a delay of a few seconds and then an error appears: "Error connecting to the target". On this message box there is a button "Retry". If I click on this button, the microcontroller gets flashed with the program and I can start debugging. Then all features work fine, I can make pause, watch registers, use breakpoints and so on. But next time I start the debugger, the same error occurs and I have to click on the "Retry" button.

The delay (I think it's a timeout of a few seconds) and the error box really sucks after a few houres of working...

Does anyone have an idea what the problem is and how I can fix it?

Thanks very much!

  • 0
    TI__Guru**** 484151 points

    Hi Simon,

    Can you capture the issue in a debug server log and zip it and attach it here? You'll need to enable logging first.

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#Debug_Server_Logging

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    Hi,


    Here is the log from the debug server. While it was logging, I started debugging, waiting for the error message, clicked on "retry" and after the debugger was started, I stopped the debugging mode.


    Thanks

    debugserver.log.zip
  • 0 in reply to Simon Obermeier
    Prodigy 40 points

    Hi,


    No idea what the problem is?

    The log from the debug server is huge, I could not find any interesting messages :-(

    If I can't fix the problem, is it possible to use OpenOCD for flashing/debugging the device? Will all Code Composer features (such as the graph for visualizing variables instantly) work also with OpenOCD?

    Thanks!

  • 0 in reply to Simon Obermeier
    TI__Guru**** 484151 points

    Simon, sorry for the delayed response.

    Thanks for the logs. the engineers analyzed the log and found that the stellaris debug dll returns a failure (1) for the first connection attempt and it takes 5 seconds to return this value. The second attempt returns 0 almost immediately. It seems like a bug and we are investigating why would happen.

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    No, problem, thanks for your help!


    By the way, I have made an installation script (install_ccs.sh) for myself to install CCS on Ubuntu 13.10 x64. With this script, you are able to install CCS on a fresh installation of Ubuntu (for example in a virtual machine). I think, maybe it could help you while you are searching for the bug. So I will attach the script (and some other files which are also needed) to this post. The only files which are also needed (but are too large to upload here) are "CCS5.5.0.00077_linux.tar.gz" and "SW-TM4C-2.1.0.12573.exe".

    I think with these files and a fresh installation of Ubuntu 13.10 x64 you are able to reproduce exactly the same situation as I have. If you have the time to do it :-)

    Thank you very much.

    install_ccs.zip