• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 184 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.

TM4C1294NCPDT: CCS will randomly Pause/Suspend/Alt-F8

Doug Baker
Genius 3420 points
Part Number: TM4C1294NCPDT

Tool/software:

We have a custom board(s) with a TM4C1294NCPDT CPU and I used the LM ICDI board for a probe when debugging the code in CCS.  Everything works great except some times when running on the debugger CCS will *randomly* Pause/Suspend/Alt-F8.  I have tried different USB cables, using a USB repeater between the PC and the probe but it will still randomly pause a few times a day.   When it pauses, I just hit the green Resume (F8) and everything will resume running correctly.  

I am running CCS 8.3.2, TIRTOS 2.16.1.14, ICDI probe.

This is really not a big deal but it would be better if it didn't randomly pause.  Any ideas as to fix this?

Doug

  • 0
    TI__Guru**** 191766 points

    Hi Doug,

      Normally this should not happen. Can you first clear all breakpoints before you hit the run button. I suspect that there might be some stale breakpoints that were enabled in the past. Try it and I hope the problem should go away. What you can also try is to do 'Free Run'. Free Run will disengage the debugger. 

       

  • 0 in reply to Charles Tsai
    Genius 3420 points

    It will infrequently stop at a random place if no breakpoints are set.  I may try a different probe, I do have a XDS200 that should work.  The ICDI probe works better with the older tools (LM flash) though so that's why I have using the ICDI probe.

  • 0 in reply to Doug Baker
    TI__Guru**** 191766 points

    When it stops, can you tell at what line of code the processor is halted? Again, I have not come across an issue as such unless there is some stale breakpoint still in the debugger's system. Let me know if you see the same problem if you use XDS200.