• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 369 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/LAUNCHXL-CC2640R2: debugging issue using breakpoints

BS1992
Intellectual 390 points

Part Number: LAUNCHXL-CC2640R2

Tool/software: Code Composer Studio

I am using LAUNCHXL-CC2640R2 for step by step debugging of Simple central project from sdk-1_40_00_45.

I place a breakpoints at some statements in .c files.while i am started the debug session using Resume tab,some of the breakpoints automatically gets disable.Why should this happen??

  • 0
    TI__Guru**** 474721 points

    Hello,

    Bhakti Sawant said:
    I place a breakpoints at some statements in .c files.while i am started the debug session using Resume tab,some of the breakpoints automatically gets disable.Why should this happen??

    There are many potential reasons why this can happen. We will need more details to narrow down the root causes.

    First off, please provide some basic information about your environment. Things like:

    -What exact version of CCS is being used?

    -What host OS?

    Then some information about how you are doing the debugging. Such as:

    -How and when are the breakpoints being set (double-clicking in the editor margin of the source file? via the breakpoints view? are they set before a debug session is launched?)

    -What do you mean by "disable"? Are the breakpoints simply greyed out? Or removed? Screenshots may help here

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 390 points

    Hello,

    1) The version of CCS used is - CCS7.2.0

    2) Debug probe - XDS110 USB debug probe

    3) OS - Windows 10,64 bits

    4) Breakpoint assignment method - double clicking in the editor margin of the source file before launching the debug session.

    5) Breakpoints get "disable" ,simply greyed out

    Below are screenshots before & after debug session:

    1) Before debug session Start:

    2) After debug session breakpoints get disable:

  • 0 in reply to BS1992
    TI__Guru**** 474721 points

    Bhakti Sawant said:

    4) Breakpoint assignment method - double clicking in the editor margin of the source file before launching the debug session.

    5) Breakpoints get "disable" ,simply greyed out

    I see what is happening. When you set breakpoints in step 4, CCS will allocate software breakpoints to be used once a debug session is started. After the debug session is started and the target is connected, CCS notices that the breakpoint locations specified in step 4 are in FLASH. Hence it has to use hardware breakpoints instead. The issue is that there a LIMITED number of hardware breakpoints available at one time. The actual number vary per device but for your device, I believe it is 6. Hence the debugger will apply 5 hardware breakpoints (one is used internally under the hood by the debugger) and the rest will be DISABLED (greyed out).

    This is what is happening on your end.

    For more information on hardware and software breakpoints, please see:

    https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#breakpoints

    Thanks

    ki