Table of Contents
Advertisement
Note
4-6 Configuration the Emulator
Blocks of memory can also be characterized as guarded memory.
Guarded memory accesses will generate "break to monitor" requests.
Writes to ROM will generate "break to monitor" requests if the "Enable
breaks on writes to ROM?" configuration item is enabled (see the
"Debug/Trace Configuration" section which follows).
For example, you might be developing a system with the following
characteristics:
input port at 0f00 hex
output port at 0f100 hex
program and data from 1000 through 2fff hex
Suppose that the only thing that exists in your target system at this time
are input and output ports and some control logic; no memory is
available. you can reflect this by mapping the I/O ports to target system
memory space and the rest of memory to emulation memory space:
delete all <RETURN>
1000h thru 2fffh emulation rom
<RETURN>
0f000h thru 0f1ffh emulation ram
<RETURN>
end <RETURN>
When mapping memory for your target system programs, you may
wish to characterize emulation memory locations containing programs
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.
Advertisement
Table of Contents
