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.

Debugging MSP432 does not halt at breakpoints until Pausing execution

Hi all,

This may be a simple question, but I've been doing some work on the MSP432 Launchpad with my project and some example projects, and I've noticed that when I place breakpoints and Run to them, code composer will continue to run until I press Pause, and then it will stop at the next breakpoint. The code execution is working as expected, I just feel there's a setting I might be missing somewhere that will make code composer automatically stop at the breakpoints. 

I'm used to debugging with the MSP430 FET debugger and in my time looking into the on-board XDS110 debugger that I'm using, it sounds uniquely different from the MSP430FET (one of the key differences being that it's much slower). I was thinking the fact that it wasn't already setup to halt at each breakpoint might be a symptom of this debugger, but hopefully its just a setting i'm missing.

Thanks for any help someone can see,

  • Hi Lunatic911,
    Are you running the debugger in any special way, like free run?

    Are the break points grayed out?

    Under "Run" menu, is "Skip All Break Points" on?
  • I spoke to another TI'er, it turns out that Falcon has an errata that when the device is in LPM and power transitions are enabled, when device hits the break point, CCS wont notice it. Only when you press halt this is seen.

    Does this sound like it applies to what your are seeing?

  • I think my problem is similar but not exactly. I'm not doing any LPM or power transitions with this code.

    I'm just doing a standard Free-run to the next breakpoint. The breakpoints are blue, so I know they're set properly. I've also verified that "Skip all Breakpoints" is not selected.

    Thanks for the help,

  • Lunatic911,
    Interesting. I just took a MSP432 LP out of the box and set a breakpoint in the msp432p401_adc14_10 example, and it hit it.
    I'm using CCSv6.1.3 with a Rev1.0 board.

    CCS did need to update the FW on the LaunchPad. You can try doing this manually by following Section 6 of this wiki: processors.wiki.ti.com/.../XDS110

    After that try running the example I listed (in MSPWare), and break point the tempurature conversion in the while loop.

    What version of CCS are you running? What code were you trying to run?

  • For the record, I'm running CCSv6.1.1.00022 with a Rev1.0 board, and I tried the command prompt upgrading of the board's firmware with no such luck. However, I did try to load in one of the example projects from MSPWARE like you suggested, and to my amazement it stopped at breakpoints like usual. I'm going to compare Project Properties between my code and the example project. I bet there's a setting in the example that's not on mine. I'll report back when I find what's different. Thanks for the help,
  • Good to hear, Lunatic911!

    Definitely let me know what the setting was so I can make a note of that for the future.
  • Lunatic911,
    Did you ever figure out what that setting was?

    Also what MSP432 revision are you using? This may have played a factor...
  • So I was able to get it fixed, but really the only thing I changed that made it work was deleting all breakpoints and resetting some. Now it stops at a breakpoint automatically when running. I bet this was one of these strange Code Composer issues where you have to delete what you have and make a new one and it will correct itself.

    I was using MSP432 Rev. B on the black Launchpad dev. kit, but recently I switched to the red Rev. C Launchpad. I was only able to fix the debugging in this project today, and this problem persisted on the Rev. C board too. But thankfully, just starting fresh worked like a charm.

    Thanks again,

**Attention** This is a public forum