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.

CCS/MSP-EXP430G2: When using CCS, how many breakpoints can I set for debugging MSP430 launchpad

Part Number: MSP-EXP430G2


Tool/software: Code Composer Studio

Hi, I'm using both 64-bit CCS 8.1.0 on my 64-bit Windows 10 computer and the CCS cloud to work with my MSP-EXP430G2 launchpad.

While debugging the C code, I had a few things in mind.

0. Is there a link from TI that describes the difference between CCS's SW/HW breakpoints?

1. Using the basic serial debugger which is on the launchpad, how many SW/HW breakpoints can I set while debugging?

I think there are limits to place those.

2. When using the CCS cloud version, does this limitation applies as well?

3. If I use a different debugger, like TMS320-XDS100-V3, or a different microcontroller/launchpad, such as the TM4C Tiva series,

will the breakpoint limit will change?

  • Hello,

    David__ said:
    0. Is there a link from TI that describes the difference between CCS's SW/HW breakpoints?

    See:

    http://processors.wiki.ti.com/index.php/How_Do_Breakpoints_Work#Hardware_vs._Software_Breakpoints

    David__ said:
    1. Using the basic serial debugger which is on the launchpad, how many SW/HW breakpoints can I set while debugging?

    There is no theoretical limit for SW breakpoints. For HW, the limitation is not based on the debug probe, but with the emulation logic on the device itself

    See Section 3.2.1 of: http://www.ti.com/lit/ug/slau157ar/slau157ar.pdf

    David__ said:
    2. When using the CCS cloud version, does this limitation applies as well?

    Yes

    David__ said:

    3. If I use a different debugger, like TMS320-XDS100-V3, or a different microcontroller/launchpad, such as the TM4C Tiva series,

    will the breakpoint limit will change?

    As mentioned in my answer for #1, the number of HW breakpoints is not determined by the debug probe but the on-chip emulation logic itself. Hence changing the debug probe will not matter, but changing the device will.

    Thanks

    ki