HP 64767 User Manual page 123

Writes to emulation ROM will be inhibited. Writes by user code to target system
memory locations mapped as ROM or guarded memory will result in a break to the
monitor but are not inhibited (that is, the write still occurs).
Emulation memory ranges can have the attributes: lock or nolock. The lock
attribute specifies that emulation memory accesses in the range be synchronized to
the target system RDY signal. The nolock attribute specifies that emulation
memory accesses are not synchronized to the target RDY — it is the same as
specifying no attribute.
Examples
Consider the following section summary from the linker load map output listing.
SEGMENT SUMMARY
---------------
SEGMENT CLASS
NMENT COMBINE
prog_main CODE
Public
lib CODE
Public
prog_init_system CODE
Public
prog_update_sys CODE
Public
prog_proc_spec CODE
Public
env CODE
Public
libm CODE
Public
libc CODE
Public
data
Public
const
Public
??SEG
graph Public
mm_check
Common
libcdata
Public
envdata
Public
idata
Public
udata
Public
heap
Public
userstack
Public
libmconst
Chapter 5: Configuring the Emulator
GROUP START
80000
806C4
8158C
81642
81C60
81CB0
82ABD
82ABE
10B26
863AA
00010
863A7
10114
10000
110DE
110DE
110DE
120DE
863A4
Mapping Memory
END LENGTH ALIG
806C2 006C3 Word
8158A 00EC7 Word
81641 000B6 Word
81C5E 0061D Word
81CAF 00050 Word
82ABC 00E0D Word
82ABD 00000 Byte
85FCB 0350E Word
110DD 005B8 Word
863EF 00046 Word
00010 00000 Para
863A8 00002 Byte
10B25 00A12 Word
1010F 00110 Word
110DE 00000 Byte
110DE 00000 Byte
120DD 01000 Word
19FDD 07F00 Word
863A4 00000 Byte
123