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: CCS Debuggging

Tool/software: Code Composer Studio

Hi,

1. Is there a way to to "next step" during CCS debugging - meaning stepping to the next line of code? I know there are "Step Into" & "Step Over" buttons, but there doesn't seem to be a "Step Next" button.

2. Is there a way to automatically load symbols for breakpoints?

3. Is there a way to automatically enable breakpoints when I am debugging?

  • Hello,

    Jack Loop said:
    1. Is there a way to to "next step" during CCS debugging - meaning stepping to the next line of code? I know there are "Step Into" & "Step Over" buttons, but there doesn't seem to be a "Step Next" button.

    "Step Over" is typically for this. It is "step over to the next line of (source code).

    Jack Loop said:
    2. Is there a way to automatically load symbols for breakpoints?

    Setting source level breakpoints would require debug symbols of the program to be loaded to the debugger. Those symbols are automatically loaded when your load the program.

    Jack Loop said:
    3. Is there a way to automatically enable breakpoints when I am debugging?

    Breakpoints automatically are enabled by default. Do you see otherwise?

    Thanks

    ki

  • For 2 & 3, I always have to load the symbols and enable the breakpoints manually. They aren't done automatically. How could I fix this?

  • It depends on how you are starting your debug session. If you are using the "Debug" button to debug a project, it will auto-load the program. If you are doing a "manual" launch, it will not. But for the latter, you can either modify the launch configuration to load a program or symbols (if the code is already in flash).

    As for breakpoints, the debugger will remember the breakpoints set for the previous debug session and try to apply them again on debugger launch. This assumes that the breakpoints were not clear before the debug session was terminated. If it was, you will need to set them again. You can also create a GEL or DSS script to automate setting of breakpoints.

    Thanks

    ki