Specifications

Table Of Contents
ARM Debugger 85 ARM specific SYStem Commands
©1989-2014 Lauterbach GmbH
If specific windows, that display memory or variables should be updated while the program is running select
the memory class E: or the format option %E.
UDMON3
UDMON
UDMON uses a data format which shall not be used anymore. It still works for
compatibility reasons. UDMON3 shall be used.
A run-time memory access is done via a Usermode Debug Monitor.
The application is responsible for calling the monitor code periodically. The call
is typically included in a periodic interrupt or in the idle task of the kernel. For
runtime memory access UDMON3 behaves exactly as TSMON3. See the
example in the directory demo/arm/etc/runtime_memory_access and see the
picture at TSMON3.
Besides runtime memory access UDMON3 allows run mode debugging.
Handling of interrupts when the application is stopped is possible when the
background monitor is activated. On-chip breakpoints and manual program
break are only possible when the application runs in user (USR) mode. See
also the example in the directory demo/arm/etc/background_monitor.
RealMON A run-time memory access is done via the Real Monitor from ARM.
TrkMON Select TRK for Run Mode Debugging of Symbian OS. DCC is used as
communication interface.
GdbMON Select T32server (extended gdbserver) for Run Mode Debugging of embedded
Linux. DCC is used as communication interface. For more information refer to
”RTOS Debugger for Linux - Run Mode” (rtos_linux_run.pdf).
Denied No memory access is possible while the CPU is executing the program.
Data.dump E:0x100
Var.View %E first