Table of Contents
Advertisement
Note
4-14 Configuring the Emulator
and constants (locations which should not be written to) as ROM. This
will prevent programs and constants from being written over
accidentally, and will cause breaks when instructions attempt to do so.
You should map all memory ranges used by your programs before
loading programs into memory. This helps safeguard against loads
which accidentally overwrite earlier loads if you follow a map/load
procedure for each memory range.
Internal RAM and SFR
The emulator uses internal RAM of emulation processor to emulate
user program. When you direct the emulator to display the contents of
internal RAM or SFR area, the emulator breaks to the monitor and the
monitor program reads the contents of memory. Therefore, execution
of user program is suspended to perform your direction. However, you
can configure the emulator so that write cycles are performed to both
internal RAM (or SFR) and emulation memory. In this case, you can
display the data written to emulation memory without suspending
program execution.
To use this feature, you need to map these area to emulation RAM
(eram). When you do this, you can display the contents of emulation
memory with "display memory" command without suspending user
program execution. You still can display the contents of internal RAM
by specifying "fcode i" syntax in "display memory" command.
For example, to see the contents of address 100 hex in internal RAM,
you can do both of the following:
display memory fcode none 100h
(This command accesses emulation memory)
display memory fcode i 100h
(This command accesses internal RAM of
emulation processor.)
Advertisement
Table of Contents
