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

Breakpoint question CCS3.3 vs CCS4.x

mdalik
Prodigy 140 points


We have recently migrated from CCS3.3 to CCS4 and we have encountered an unhappy difference in debugging behavior.

With CCS3, we could start a debugging session, let the code run for a while and then click on a line of code to set a breakpoint.  The breakpoint would be set and execution would stop if we hit the breakpoint.  This was really useful for exploratory debuggging where we aren't sure where we want to stop without seeing the target run for a while.

Using CCS4, we find that, after connecting to the target board, we can only set breakpoints when execution is halted -- if the target is running, we can't set a breakpoint.  So we have to know where we want breakpoints before we start up the target.

Is there a way to set CCS4 so that we can have the old behavior back?

We see this issue using both C2000 and Stellaris targets, and with XDS510, XDS100 v1, and XDS100 v2  emulators.

 

Thanks!   Erik

  • 0
    TI__Genius 16520 points

    In v4, the debugger has changed so that you can't modify the state if your target is running. Howver, you can change this behavior by openning the "Generic Debugger Options" view, under Tools menu and adjust the "Halt the target before any debugger access". Note that everytime that you access the debugger, it will halt the target.

    Regards,
    patrick

  • 0 in reply to Patrick Chuong
    Prodigy 140 points

    Patrick, apologies for a late reply.  I'll give this a try.  If this will halt the target to set the breakpoint, it won't give us the behavior we prefer.  If we can set a breakpoint and halt the target upon reaching the breakpoint, we'll be delighted.   

    Updated -- this behaves as CCS3.3 does.  I'm very happy.