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.

EKS-LM3S2965, Code Composer - Max number of Breakpoints

Other Parts Discussed in Thread: LM3S2965

Using the LM3S2965 evaluation board and code composer , version: 4.2.4.  Maximum number of breakpoints I can set is 3.  The LM3S2965 datasheet under Integrated Configurable Debug says there are 8 hardware breakpoint comparators.  So why can't I set 8 breakpoints?

  • PeterO,

    You should be able to use 6 breakpoints.  The other 2 are most likely reserved for stepping through code line-by-line or similar tasks in the debugger.

    Are you sure you don't have any other breakpoints set within your code, or any watchpoints?  Have you configured something in CCS that would use the other 3 breakpoints?

    -Rebecca

  • Peter - note that the debugger can automatically use some breakpoint resources. In addition to the two Rebecca mentioned, there are other actions like the auto-run to main option which will set a breakpoint at main and setting a breakpoint at the exit point of the application. C/IO will also use breakpoints. You can disable these options in the debugger options.

    Thanks

    ki

  • Ki and Rebecca, under Generic Debugger Options I've disabled "Halt at program termination" and "Enable CIO function use".

    Now I have maximum 5 interrupts.  With 5 interrupts I can't step through my code, which is ok and expected.  I still can't account for the other 3 interrupts.  Can you?

    My Generic Debugger Options settings are attached.

  • I see that the auto-run to main option is still enabled. That could be using up one HW resource. As for the other two resources, they may be reserved by the debugger for some other actions. I'll try to get confirmation of this.

    Thanks

    ki

  • Ki, did you find out, the other 2 breakpoints are reserved for the debugger?

  • Peter,

    I have confirmed that the debugger itself will not reserve any additional breakpoints for its own use. To see more details on active breakpoints, open a scripting console during a debug session and type in:

    activeDS.expression.evaluate("DEBUG_DumpBreakpoints()")

    This will output a detailed report on active breakpoints for the debug session,

    What I am confused about is that as I hunt around for information on the number of HW breakpoints available for Stellaris, the answer I see a lot is 6, not 8. For example:

    http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcontroller/f/471/t/44163.aspx

    Many of the Stellaris folks seem to confirm this answer.

    Thanks

    ki