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

CCSv5 Bookmarks

Russ Franke
Prodigy 40 points


Is there somewhere that I can find information about Bookmarks? I am running a small program with interrupts and I need to check a value in my Main. The CC adds a bookmark to the start of Main which has action of "Remain Halted".  Where did this com from?  What can  do about it?

  • 0
    TI__Guru**** 162895 points

    Russ,

    We call them "breakpoints" instead of "bookmarks".  The editor has bookmarks to mark places in your code that you may want to refer to later and then the debugger has breakpoints which are used to halt execution.

    By default CCS sets up some breakpoints for you.  One of them is at main() as CCS will set this breakpoint and run the target so that it halts at main when the debugger is launched.  

    If you don't want CCS to setup the breakpoint at main you can disable that.  There are a few ways to do that.

    If you are in the "CCS Edit" perspective, right click on your project and select properties.  In the dialog box that opens select "Debug" in the tree on the left, then select "Auto Run and Launch" in the list in the middle and then under the "Auto Run Options" you can remove the "main" from the "run to symbol" edit box and also uncheck the "On a program load or restart box.

    If you are already in a debug session then you can also do this by going to the Tools menu and then select "Debugger Options" -> "Auto Run and Launch Options".

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 40 points

    Thank you for the quick reply.  I will be trying these hints this afternoon and hope I can get them right.  It has been a ffrustrating week with my project with these "automatic" breakpoints that I can't seem to control.

     

     

  • 0 in reply to JohnS
    Prodigy 40 points

    Thanks again for the hints.  I find that even though I set a "Breakpoint" in my main code, the hidden breakpoint still occurs and mine is gone.  I created both the interrupt code and the main in CCv5.3 and am trying to debug using the debug button.  I would like to "step thru" portions of my code to verify the pin readings there.  I have used this type of function before on IBM Mainframes and think I am familiar with how a debug works.

    I did the Edit function as described and try to do the Debugger options when necessary.  That is when my Breakpoints are erased and new ones are not allowed to be set as I am in Debug mode.

     

  • 0 in reply to Russ Franke
    TI__Guru**** 162895 points

    What device are you using?  I am guessing that it is a flash based device that requires the use of hardware breakpoints vs software breakpoints.  More info on the differences here: http://processors.wiki.ti.com/index.php/Breakpoint

    The summary is that you have a limited number of hardware breakpoints as they require physical resources on the device.

    The screen captures below are done using an F28335 which is a flash based microcontroller.  My program is loaded in flash so any breakpoints I set are going to be hardware breakpoints.  Note that some of the breakpoint resourses are reserved so that you can step the processor.

    In this capture I have the auto run to main option on (which uses a resource).  This limits me to 1 breakpoint for my own use.  You can see that when I set the second one it is disabled.

    Now I am going to turn off the option to run to main.  I go to the tools menu and select debugger options.  I select Auto Run on the left.  I clear the run to label on the right and also uncheck the box to auto run on load and restart.  I need to click the remember my settings button for this change to be saved for the next time I launch the debugger.

    I click the red square in the debug view to kill the debug session.  Then I click the bug button to launch the debugger again.  Now I can see that it does not run to main (it is at c_int00) and I can now set a second breakpoint.  When I try to set a 3rd breakpoint it is disabled.

    There is a decent amount of training material available as well that may be of some use.  Below are links to the main CCS training site and the second link is to the CCS Fundamentals workshop.  TI also has longer 1 and 3 day workshops that cover the device, software and tools.

    http://processors.wiki.ti.com/index.php/Category:CCS_Training

    http://processors.wiki.ti.com/index.php/CCSv5_Fundamentals_Workshop