Hi all,
I am using a SEGGER J-Link EDU probe with JLinkGDBServer and arm-none-eabi- toolchain on Linux to debug some software I currently develop on an STM32F427II processor.
There is an SVCall done during initialization, using the instruction "svc 0". When running the code without debugger, it enteres the SVCall handler correctly and works as expected.
When debugging with arm-none-eabi-gdb through JLinkGDBServer I receive "Program received signal SIGTRAP, Trace/breakpoint trap." and stepping does not step over the instruction, but lands at the same instruction again. My SVCall handler is never called.
Is there some configuration that I am missing to disable this behaviour? - I am not interested in semihosting, I do not need this in my project. I would just like JLinkGDBServer to not stop on the SVC instruction.
Thanks a lot in advance,
Christian
I am using a SEGGER J-Link EDU probe with JLinkGDBServer and arm-none-eabi- toolchain on Linux to debug some software I currently develop on an STM32F427II processor.
There is an SVCall done during initialization, using the instruction "svc 0". When running the code without debugger, it enteres the SVCall handler correctly and works as expected.
When debugging with arm-none-eabi-gdb through JLinkGDBServer I receive "Program received signal SIGTRAP, Trace/breakpoint trap." and stepping does not step over the instruction, but lands at the same instruction again. My SVCall handler is never called.
Is there some configuration that I am missing to disable this behaviour? - I am not interested in semihosting, I do not need this in my project. I would just like JLinkGDBServer to not stop on the SVC instruction.
Thanks a lot in advance,
Christian