Hello,
I am working with the Arm Cortex-R5F CPU.
I would like to know how to configure the debugger so that execution halts at the instruction causing the fault, before entering the abort handler. Specifically, my goal is to stop at a breakpoint whenever an invalid memory access occurs (e.g., accessing an unmapped or protected address), instead of only observing the crash once control has already moved into the abort handler.
Could you please advise on the recommended way to achieve this on R5F?
Thank you,Regards,
Eli Mordel
Hi,
I am working with TI’s AM2434 device, which has 4 Arm Cortex-R5F CPUs. My toolchain setup is:
Compiler/Linker: GCC (via TI’s Code Composer Studio IDE)
Debugger/Probe: XDS200 JTAG
I would like to configure the debugger so that execution halts at the instruction causing the fault, before entering the abort handler. Specifically, my goal is to trap and break whenever an invalid memory access occurs (e.g., an access to an unmapped or protected memory region).
Could you please advise on the recommended way to achieve this with the R5F CPU and my setup?
Thanks and regards, Eli Mordel
I'm sorry, but I have never used the TI tools.
A cursory search tells me that the Tools > Arm Advanced Features menu allows you to set vector catch breakpoints.
Vector Catch will stop on the vector table address that the processor jumps to, you do not need to provide a handler at this time.
This happens immediately when the invalid access occurs.
If you have further questions on the tools you are using I suggest you post the question to TI's own forum:https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum
Thanks !
Regards,
Eli