• State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 120 subscribers
  • Views 2436 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cortex A15 ARMDS 22.2 Breakpoints not working in C code, only in assembly?

Raghu Halharvi

Hello,

Any help here will be appreciated, My target is A15 running threadx code, breakpoints work fine in *.s or Assembly file but don't respond or stuck in *.c file

I am new to ARMDS interface, I did look at this discussion but didnt know where to pass the extra flag/option EL1N:0 in ARMDS 22.2

https://community.arm.com/support-forums/f/armds-forum/47140/breakpoints-not-working-in-c-code-only-in-assembly

 

Parents
  • 0 in reply to Stephen Theobald

    Hello Stephen,

    Thanks for the response

    I have made sure the optimization level is minimum -O0 with -g and also verified there is no optimisation done by the compiler.

    The firmware is directly loaded into RAM by the loader, the offset is 0, attached the screenshot, added the N:0 as argument in debug connection tab.

Reply
  • 0 in reply to Stephen Theobald

    Hello Stephen,

    Thanks for the response

    I have made sure the optimization level is minimum -O0 with -g and also verified there is no optimisation done by the compiler.

    The firmware is directly loaded into RAM by the loader, the offset is 0, attached the screenshot, added the N:0 as argument in debug connection tab.

Children
  • 0 Arm Employee Badge in reply to Raghu Halharvi

    Hi again

    The "N:0" is an argument for an "add-symbol-file" command, not an argument for the program.

    An "add-symbol-file" command is used to load debug information from a debug .axf into the debugger.
    See developer.arm.com/.../add-symbol-file

    To execute an "add-symbol-file" command, open the "Commands" view.  At the bottom of the "Commands" view is a "Command" field.  
    In the "Command" field, enter:
    add-symbol-file \path\to\your.axf

    If your program switches between security states, you may need both
    add-symbol-file \path\to\your.axf N:0
    and
    add-symbol-file \path\to\your.axf S:0

    These commands can also be added into the Debugger tab of the Debug Configuration, or into a .ds script file, to help automate the process.

    Hope this helps

    Stephen