Hello,
I am debugging in an environment using BLE with nRF54, but after breaking, when I step through it, the debugger stops and I am having trouble.
The environment I am using is as follows.
Board: nRF54L15-DK
SDK: nRF Connect SDK v2.9.1
Source: DevAcademy/Bluetooth Low Energy Fundamentals/Lesson 3 – Bluetooth LE Connections/Exercise 1(l3_e1_sol)
The following changes were made to the l3_e1_sol source to use monitor mode:
Kconfig
CONFIG_CORTEX_M_DEBUG_MONITOR_HOOK=y
CONFIG_SEGGER_DEBUGMON=y
Execute the following command in the debugger terminal.
-exec monitor exec SetMonModeDebug=1
Messages displayed when stepping.
---
/__w/_temp/workspace/build/.build/HOST-x86_64-w64-mingw32/arm-zephyr-eabi/src/gdb/gdb/infrun.c:5825: internal-error: finish_step_over: Assertion `ecs->event_thread->control.trap_expected' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
/__w/_temp/workspace/build/.build/HOST-x86_64-w64-mingw32/arm-zephyr-eabi/src/gdb/gdb/infrun.c:5825: internal-error: finish_step_over: Assertion `ecs->event_thread->control.trap_expected' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
ERROR: GDB exited unexpectedly with exit code 3 (0x3). Debugging will now abort.
The program 'c:/Workspace/l3_e1_sol/build/l3_e1_sol/zephyr/zephyr.elf' has exited with code -1 (0xffffffff).
----
What are the problems in debugging using monitor mode?
