If you have trouble mapping memory
The emulator uses a best fit algorithm to assign memory blocks to map requests.
Because the memory block sizes available depend on the emulation memory
module installations and the use of the dual-port memory, it’s possible that a
256-byte map request may use 512 Kbytes. (The map term will be only 256 bytes.)
Most systems won’t have such differences between memory block size
requirements and available memory. However, certain emulation memory module
installations will aggravate the problem.
Also, use of the dual-port memory is controlled first by monitor selection and next
by explicit selection of a dual-port term in the map. If you choose a foreground
monitor, the dual-port memory block is reserved for the monitor. If you choose a
background monitor, and don’t explicitly map a term with the dp attribute, the
dual-port memory may be used to satisfy any map request. For example, if you
request a 256-byte map term and this memory block is available, it will be used to
satisfy the request because it is closest to the needed size. Or, if you request a term
that is slightly larger than another available block, the dual-port memory will be
used with another map term to satisfy the request. (For example, a 260-Kbyte
request may use one 256-Kbyte block and the 4-Kbyte dual-port memory.)
Refer to the section “Mapping Memory” in Chapter 8, "Configuring the Emulator",
for more information on memory allocation.
If emulation memory behavior is erratic
Check to see if you have installed HP 64171A or HP 64171B memory modules on
the emulation probe board. These memory modules are too slow to work with the
MC68040 emulator. Use HP 64172A, HP 64172B, or HP 64173A memory
modules.
Chapter 9: Solving Problems
If you have trouble mapping memory
361
Summary of Contents for 64783A
Page 30: ...xxx ...
Page 31: ...Part 1 Quick Start Guide 1 ...
Page 33: ...1 Getting Started 3 ...
Page 70: ...40 ...
Page 75: ...Part 2 Using The Emulator 45 ...
Page 140: ...110 ...
Page 141: ...4 Using the Emulator How to control the processor and view system resources 111 ...
Page 227: ...5 Using the Emulation Bus Analyzer How to record program execution in real time 197 ...
Page 290: ...260 ...
Page 331: ...8 Configuring the Emulator 301 ...
Page 382: ...352 ...
Page 383: ...9 Solving Problems What to do when the emulator doesn t behave as expected 353 ...
Page 397: ...Part 3 Reference 367 ...
Page 399: ...10 Using Memory Management Understanding logical and physical emulation and analysis 369 ...
Page 429: ...11 Emulator Commands The command syntax reference for the emulator softkey interface 399 ...
Page 443: ...copy Chapter 11 Emulator Commands copy 413 ...
Page 451: ...display Chapter 11 Emulator Commands display 421 ...
Page 457: ...DISPLAY MEMORY Chapter 11 Emulator Commands DISPLAY MEMORY 427 ...
Page 461: ...DISPLAY MMU Chapter 11 Emulator Commands DISPLAY MMU 431 ...
Page 464: ...DISPLAY TRACE Chapter 11 Emulator Commands DISPLAY TRACE 434 ...
Page 480: ...modify Chapter 11 Emulator Commands modify 450 ...
Page 501: ...set Chapter 11 Emulator Commands set 471 ...
Page 514: ... SYMB Chapter 11 Emulator Commands SYMB 484 ...
Page 582: ...552 ...
Page 583: ...13 Setting X Resources 553 ...
Page 598: ...568 ...
Page 606: ...576 ...
Page 613: ...16 Specifications and Characteristics 583 ...
Page 627: ...Part 4 Concept Guide 597 ...
Page 629: ...17 X Resources and the Graphical User Interface 599 ...
Page 639: ...Part 5 Installation and Service Guide 609 ...
Page 697: ...19 Installation and Service 667 ...
Page 746: ...Chapter 19 Installation and Service Verifying the Installation 716 ...
Page 755: ...20 Installing Updating Emulator Firmware 725 ...
Page 762: ...732 ...
Page 778: ...748 ...
Page 810: ...X server 554 604 X Window System 54 Index 780 ...