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.

CC2340R5: Breakpoints are disabled automatically (gray out)

Part Number: CC2340R5

Tool/software:

When creating a new breakpoint it is autoamically disabled (turns gray)


Right clicking in the breakpoints margin and selecting Add breakpoint or just left click gives the same result
OS: Windows 10
CCS: Version: 20.1.1.8__1.7.1
Default VS Code API: 1.92.2

  • Hello Itamar Cohen,

    I hope you are doing well. With the CC2340R5 only 4 breakpoints can be active at once, so if we place more than 4 some will be disabled, you can view your active breakpoints in the breakpoint tab while in the debugging menu (*or you can clear all breakpoints). 

    If you did not exceed the maximum breakpoints you may need to re-install CCS Theia, as I have had a similar issue where breakpoints never went off while debugging and was solved by uninstalling and re-installing.

    Thanks,
    Alex F 

  • Lookslike I need to reinstall. Aalso with zero breakpoint it still disabled

    Should I install the same version: 20.1.1.8__1.7.1.  ?

  • Hello Itamar Cohen,

    You should be fine re-installing the same version, just make sure all required tools are downloaded during the installation process. 

    Thanks,
    Alex F

  • what packages I should install when installing CCS 20. I am only interested in developing for the CC2340R5

  • Are  the  MSPM0 Arm Cortex M0+microcontrollers and Wireless Conectivity will be suficient for developing for the CC2340 ?

  • Hello Itamar Cohen,

    Those should be enough for the CC2340R5, though if it still does not work the last resort is to install all.

    Thanks,
    Alex Fager

  • 1. Reinstalling helped. I can now enable breakpoints

    2. I also tried only to install the mentioned packages and indid it was enough

    3. May I sugest a few minor improvmenns:

    3.1 in the installation process, where you should select packages, when you cklick on a package you get some

    explanation about the TI products lines and their merits. For example if you click on the MSPM0 Arm.. the text says: Our scalable....

    and if you click on Wireless Connectivity... the text shown is: TI offers a protfolio of afordable...

    In other words, all kinds of marketing information completely irrelevant for the installation. 

    For the first if I am already installing TI product, you don't need to convince me to use this product, I am already using it !

    Secondly, It will be much more helpful to tell me the user something like: Include this package if you are developing for the CC2340R5 

    3.2 Your naming conventions are a bad combination of marketing polution and relevant information

    For example: simplelink_lowpower_f3_sdk_8_40_02_01 

    Do you have complicatedlink products or even highpower products ? what different it makes ? what is f3 ?

    I would call it f3_sdk_8_40_02_01

    Hope you get what I mean and escalate it to the right team.

    Thanks for your help