
GRMON3-UM
June 2019, Version 3.1.0
49
www.cobham.com/gaisler
Figure 4.13. The memory view
The Memory View can be used to access any addressable locations as seen by the current debug link. For example
IO registers in raw format. It is possible to specify the memory content presentation, for example ASCII string,
by adding a new rendering from the New Renderings... tab. Endian can also be selected in the right-click context
menu on a cell.
The Memory View is updated automatically at certain system events, for example when execution stops, or when
a breakpoint is hit and after single-step by the user. This behavior can be disabled as described in Section 4.6.1,
“Memory view update”.
NOTE: Even though GRMON GUI is CPU and context aware, the Memory View is global and always operate on
physical addresses: no MMU translation is performed by the Memory View.
4.5.6. Disassembly View
Disassembly View provides a convenient method to inspect the instruction memory of an application. It also pro-
vides, in combination with the CPU Registers View, a powerful method for inspecting how CPU state is updated
on instruction level when single-stepping.
Disassembly View is available from the main menu under Window > Show View > Disassembly. When adding a
new memory monitor, the user a dialog is displayed where the target address is specified.
The currently highlighed row represents the instruction which is to be issued when execution continues. Execution
history is also highlighted in shaded color to represent instructions which have been recently executed. The right-
most column of the Disassembly View describes the name of the function which the instruction belongs to, together
with the offset from the function symbol.