Debugging Memory Map
The DMM GUI
720
Microcontrollers Debugger Manual
Memory Read Caching
The Refresh memory when halting option controls the debugger memory cache. When
this option is checked, internal images/caches of memory data are always deleted and the
data is always retrieved from hardware when required by the debugger. When unchecked
(usually by default for Non-Volatile Memory areas), the DMM keeps a copy of the data
and does not read or retrieve the data from hardware until next application loading/
programming.
NOTE Each declared memory address range in the GUI has its own private code cache
monitored by the DMM.
TIP The DMM CACHINGOFF command can fully disable the caching feature for the
entire DMM, that is, for all defined memory ranges. The DMM CACHINGON
command re-enables the caching feature.
Access while Running
Use the No memory access while running option to discard debugger access to a
memory range, typically accessed while running. This feature is useful to protect on-chip
I/O Register flags from being triggered by debugger memory reads due to display
refreshes.
Remarks
It is possible to create as many memory ranges as wanted, down to a single byte.
Deleting Default/Factory ranges generates warning dialogs. Some settings are required for
the debugger to debug and removing ranges leads to erroneous debugging information.
All GUI settings can be done by debugger commands.
Settings and DMM changes are saved in the current user project. The user can always
restart from draft pressing the Revert to Default button.
Automatic DMM range remapping can be disabled by a debugger command.
The default settings are retrieved from a complete database describing each derivative, or,
in some cases, describing the CPU core (when not necessary to go to derivative level).