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.

LP-MSPM0C1104: Unable to place software breakpoints

Part Number: LP-MSPM0C1104
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

I'm working with the LP-MSPM0C1104, however I'm not able to debug efficiently since all software breakpoints get disabled once i start the debugger.

For example, if I open the example project timix_timer_mode_one_shot_standby and i compile it with no optimization (-o 0):

However, as soon as i start the debugger the first breakpoint will be "converted" to an hardware breakpoint and all others will be removed:


Therefore the program will not halt execution at lines 40 or 51, however it will halt at the __BKPT() instruction of line 53

Furthermore, if i try to Step Over, nothing happens and i get the following error:

Breakpoint Manager: _JobHardwareBreakpoint::ARM_DEBUG_V6M_bpu_add_breakpoint: FPB : All resources are in use.[22062]

Software versions used:

  • Theia CCS    v.20.1.0.445
  • MSPM0 SDK   v.2.4.0.06
  • SysConfig     v.1.22.0
  • Compiler: TI Clang v4.0.2LTS
  • Hi Bruno,
    The C family offers only two hardware breakpoints. If you want to use more than that, I would recommend adding __NOP() before the code and add break point in this line, or to use a software breakpoint __BKPT().

    Best Regards,

    Diego Abad

  • Hi!

    Sadly i am only able to use 1 hw breakpoint.

    Furthermore, adding __NOP() before the code and adding a break point at that line does not work either, as can be seen in the attached pictures at line 51.

    Am i missing something? Is there a setting in CCS i need to tweak?

    Thanks,
    Bruno

  • Hi Bruno,
    I replicated your issue, and you are correct. It seems that a breakpoint already happens by default in the main (when the program starts). I'm not sure how to remove that breakpoint, however. Our CCS expert is out of the office for the time being. My recommendation for now is to stick to software breakpoints.
    Best Regards,
    Diego Abad

  • This is it!

    This comment solved my issue, i had not thought of "it seems that a breakpoint already happens by default in the main".

    To solve this issue: inside Project -> Properties -> Debug I disabled the setting "Halt at program exit for TI compilers (requires a breakpoint)"

    Now i am able to use both hardware breakpoints

    Thanks a lot!

    Bruno