HD6475368CP Datasheet, PDF (29/108 Pages) Agilent(Hewlett-Packard) – H8/536 Emulator PC Interface

Saving the
Configuration
To save the configuration, use the Enter key to exit the field in the last
field. (The End key on Vectra keyboards moves the cursor directly to
the last field.)
Mapping Memory
The H8/536 emulator contains 126 kilobytes of high-speed emulation
memory (no wait states required) that can be mapped at a resolution of
256 bytes.
The memory mapper allows you to characterize memory locations. It
allows you specify whether a certain range of memory is present in the
target system or whether you will be using emulation memory for that
address range. You can also specify whether the target system memory
is ROM or RAM, and you can specify that emulation memory be
treated as ROM or RAM. You can include function code information
with address ranges to further characterize the memory block.
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
"Configuring the Emulator" chapter).
The memory mapper allows you to define up to 16 different map terms.
Note
When you use the H8/536 internal ROM and RAM, you must map
memory space where internal ROM and RAM are located as each
emulation ROM and RAM.
Which Memory
Locations Should Be
Mapped?
Typically, assemblers generate relocatable files and linkers combine
relocatable files to form the absolute file. The linker load map listing
will show what locations your program will occupy in memory. A part
of linker load map listing for the sample program (cmd_rds.map) is
shown in Figure 2-4.
Getting Started 2-31