HP 64782, User Manual, Page: 114 / 554

Examples Consider the following section summary from the linker load map output
listing.
SECTION SUMMARY
---------------
SECTION ATTRIBUTE START END LENGTH ALIGN
ABSOLUTE DATA 00000000 0000002F 00000030 0 (BYTE)
0 NORMAL 00000030 00000030 00000000 2 (WORD)
env NORMAL CODE 00000400 00000FC0 00000BC1 2 (WORD)
prog NORMAL CODE 00000FC2 00001A89 00000AC8 2 (WORD)
const NORMAL ROM 00001A8A 00001ACF 00000046 2 (WORD)
lib NORMAL CODE 00001AD0 00002663 00000B94 2 (WORD)
libc NORMAL CODE 00002664 00004881 0000221E 2 (WORD)
libm 00004882 00004882 00000000 0 (BYTE)
mon NORMAL CODE 00004882 000049CB 0000014A 2 (WORD)
envdata NORMAL DATA 00007000 00007155 00000156 4 (LONG)
data NORMAL DATA 00007156 00007721 000005CC 2 (WORD)
idata 00007722 00007722 00000000 0 (BYTE)
udata 00007722 00007722 00000000 0 (BYTE)
libdata NORMAL DATA 00007724 00007727 00000004 4 (LONG)
libcdata NORMAL DATA 00007728 00008153 00000A2C 2 (WORD)
mondata NORMAL DATA 00008154 00008177 00000024 2 (WORD)
stack NORMAL DATA 0000B000 00012FFF 00008000 4 (LONG)
heap NORMAL DATA 00013000 00016FFD 00003FFE 4 (LONG)
Notice the ABSOLUTE DATA, CODE, and ROM sections occupy locations 0
through 49CBH. Because the contents of these sections will eventually
reside in target system ROM, this area should be characterized as ROM when
mapped. This will prevent these locations from being written over
accidentally. If breaks on writes to ROM are enabled, instructions that
attempt to write to these locations will cause emulator execution to break
into the monitor.
Also, notice the DATA sections occupy locations 7000H through 8177H and
0B000H through 16FFDH. Since these sections are written to, they should
be characterized as RAM when mapped.
Configuring the Emulator
To add memory map entries
113