HP 64782 User Manual page 114

Examples
Consider the following section summary from the linker load map output
listing.
SECTION SUMMARY
---------------
SECTION ATTRIBUTE
ABSOLUTE DATA
0 NORMAL
env NORMAL CODE
prog NORMAL CODE
const NORMAL ROM
lib NORMAL CODE
libc NORMAL CODE
libm
mon NORMAL CODE
envdata NORMAL DATA
data NORMAL DATA
idata
udata
libdata NORMAL DATA
libcdata NORMAL DATA
mondata NORMAL DATA
stack NORMAL DATA
heap NORMAL DATA
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.
START END
00000000 0000002F
00000030 00000030
00000400 00000FC0
00000FC2 00001A89
00001A8A 00001ACF
00001AD0 00002663
00002664 00004881
00004882 00004882
00004882 000049CB
00007000 00007155
00007156 00007721
00007722 00007722
00007722 00007722
00007724 00007727
00007728 00008153
00008154 00008177
0000B000 00012FFF
00013000 00016FFD
Configuring the Emulator
To add memory map entries
LENGTH ALIGN
00000030 0 (BYTE)
00000000 2 (WORD)
00000BC1 2 (WORD)
00000AC8 2 (WORD)
00000046 2 (WORD)
00000B94 2 (WORD)
0000221E 2 (WORD)
00000000 0 (BYTE)
0000014A 2 (WORD)
00000156 4 (LONG)
000005CC 2 (WORD)
00000000 0 (BYTE)
00000000 0 (BYTE)
00000004 4 (LONG)
00000A2C 2 (WORD)
00000024 2 (WORD)
00008000 4 (LONG)
00003FFE 4 (LONG)
113