• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 1701 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/TMDSSK3358: breakpoints in startup_ARMCA8.S are ignored

Attila Csosz
Intellectual 710 points

Part Number: TMDSSK3358

Tool/software: Code Composer Studio

Hi,

It seems breakpoints in startup_ARMCA8.S are ignored even if I put breakpoint to 'Branch to main' in startup_ARMCA8.S .

  • 0
    TI__Guru**** 484901 points

    Hello,

    How are you setting this breakpoint? And when? Also provide the exact CCS version you are using and the exact behavior you witness when you try to set the breakpoint. For example, explain what you mean by "ignored" (is the breakpoint successfully set but it never halts there? Or does the brekapoint never gets enabled?)

    A screenshot of your environment would be helpful. One that shows the source file and the breakpoints view like below:

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 710 points

    My CCS version: Version: 7.3.0.00019

    Before debugging I have built the project and put two breakpoint: one in main.c, one in startup_ARMCA8.S . I start the debugging by pressing the Debug button. The debugger doesn't stop in startup_ARMCA8.S, it stops in main.c (at beginning of main) . When I press the Resume button the debugger stops at the breakpoint in main.c (this is correct) .

    The screenshots:

    My simple project (I have not changed the S, lds file )

    example.zip

  • 0 in reply to Attila Csosz
    Intellectual 710 points

    Another problem: the forum engine removes my screenshots. Trying again:

  • 0 in reply to Attila Csosz
    TI__Guru**** 484901 points
    Thanks. I can reproduce this error. It is odd. If I disable auto-run to main and then have the code start at the entry point. I can set the breakpoint successfully in the source file and reach it successfully. If I terminate, enable auto-run to main, and start the debug session again, it will reach the breakpoint

    But if I don't set the breakpoint that way (using the method you were using), the breakpoint is not applied correctly. I am investigating further.

    Thanks
    ki
  • 0 in reply to Ki
    TI__Guru**** 484901 points

    Ok, (with help from the engineer) I've determined the root cause of this behavior.

    If you set a breakpoint before a debug session has started and then start the debugger, CCS will try to automatically apply that breakpoint after the debugger has connected to the CPU.

    However...

    For multi-CPU targets (like many Sitara devices), this will not happen because the debugger does not know which CPU that breakpoint should be applied to. So it will leave it unattached.

    To check to see if the breakpoint is unattached, you can go to the menu for the Breakpoints view and group by Debug Contexts

    Note that in the screenshot below, you can see that the breakpoint is "unattached"

    You can then "attach" the breakpoint to the current debug context via:

    You will be prompted to choose the CPU to apply the breakpoint too:

    Now the breakpoint will be applied (attached):

    If you terminate the debugger and start another debug session, the breakpoints will be auto-attached to the same CPU again since it will remember you last setting. However, if you delete the breakpoints and then try to apply them again outside the debug session, the same steps will need to be repeated.

    Note that because you have "auto-run to main" enabled, it will always run to main. You can always disable this if you wish to start at the entry point in the assembly file instead.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 484901 points
    I forgot to mention that you need to be in a debug session to use the option to attach to a debug context.