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

Hi

My name is Stephen and I work at Arm.

The Execution Level (e.g. EL1N) that you've seen in other answers applies to Arm processors which implement the Armv8-A architecture. Your Cortex-A15 implements Armv7-A architecture, so has no ELs.

As a first step, check that you are compiling the source files with "-g".  This adds debug information into object files to allow debug at source level.

Check that your final linked executable contains debug information using, e.g.
fromelf your.axf
and confirm that it contains some debug_* sections.

Check that the debug information is being loaded into the debugger.  For example, do you see variables appearing in the Variables view?

Cortex-A15 implements TrustZone, and can operate in Secure or Non-secure (Normal) worlds.
If the debugger loads debug information from the image when in Secure world, but your application runs in Normal world, then you might need to load debug information for Normal world with e.g.
add-symbol-file your.axf N:0
The zero here means a zero offset between the addresses given in the debug information and the actual load address of your executable.  You might need a non-zero value if e.g. your code relocates itself at run-time.

Hope this helps

Stephen

Hi

My name is Stephen and I work at Arm.

The Execution Level (e.g. EL1N) that you've seen in other answers applies to Arm processors which implement the Armv8-A architecture. Your Cortex-A15 implements Armv7-A architecture, so has no ELs.

As a first step, check that you are compiling the source files with "-g".  This adds debug information into object files to allow debug at source level.

Check that your final linked executable contains debug information using, e.g.
fromelf your.axf
and confirm that it contains some debug_* sections.

Check that the debug information is being loaded into the debugger.  For example, do you see variables appearing in the Variables view?

Cortex-A15 implements TrustZone, and can operate in Secure or Non-secure (Normal) worlds.
If the debugger loads debug information from the image when in Secure world, but your application runs in Normal world, then you might need to load debug information for Normal world with e.g.
add-symbol-file your.axf N:0
The zero here means a zero offset between the addresses given in the debug information and the actual load address of your executable.  You might need a non-zero value if e.g. your code relocates itself at run-time.

Hope this helps

Stephen

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