Monitor Mode Debug only works if halting debug is disabled.ĭebug Halting Control and Status Register (DHCSR), 0圎000EDF0 We’ll explore how to configure the handler in theįollowing sections.
Monitorcontrol github full#
This bit can only be set via the JTAG/SWD connection and is only reset when a full Notably, the C_DEBUGEN settingĪbove must be cleared.
Otherwise, you are bound to confuse yourself when you are trying to test the feature and have a debugger connected via JTAG/SWD: If you are trying to use Monitor Mode Debug, I recommend adding a check on boot for Power-On-Reset (POR) occurs or a debugger clears the bit on exit. MON_EN - Controls whether the DebugMonitor exception is enabled or not.The core configuration for the DebugMonitor exception is controlled in the upper 16 bits of the The system is running! Debug Exception and Monitor Control Register (DEMCR), 0圎000EDFC This can also be a useful way to keep an active GDB session open and probe its state while MON_PEND - Can be used to trigger a DebugMonitor exception irrespective of whether or not.“events” will cause the exception to fire. MON_STEP - Can be toggled from the DebugMonitor exception to enable hardware.Software can use this bit to convey state about monitor mode.
When trying to debug! DebugMonitor Exception Configuration Nuances They allow you to guarantee the system is halted any time an exception path is hit which can be useful These only take effect when using halting debug NOTE: The lower bits ( VC_HARDERR, etc) controls whether or not a debug trap occurs automatically when When set, upon return from the exception handler, the core will execute a single instruction and then return to the DebugMonitor exception. This can be a useful feature to guarantee that certain high priority operations (i.e Bluetooth The DebugMonitor exception will only be triggered for debug events when the group priority of theĮxception is greater than the current execution priority. Radio scheduling) continue to run while you step through the code in other parts of the system.Īn important consequence however is it does mean any interrupts running above this priority of theĭebugMonitor exception will not be debuggable when using debug monitor support.Ĭonfiguring the DebugMonitor exception priority will require updating SHPR3. Stepping over a breakpoint is a several step process: Typedef struct _attribute_ (( packed )) ContextStateFrame Debug Monitor Continue and Step Support This means all other interrupts will be able to run while debugging code not C Code to Enable the DebugMonitor Exceptionįor simplicity in our example app we will set the DebugMonitor exception to the lowest configurable More details can beįound in our post about ARM Cortex-M exception handling.
0 kommentar(er)
