Table of Contents
Advertisement
Action: In most cases, the problem results from the emulator's inability to break to
the monitor to perform the operation. See message 608.
702
Emulation memory access failed
Cause: System failure.
Action: Run performance verification (Terminal Interface pv command).
707
Request access to guarded memory: %s
Cause: The address or address range specified in the command included addresses
within a range mapped as guarded memory. When the emulator attempts to access
these during command processing, the above message is printed, along with the
specific address or addresses accessed.
Action: Re-enter the command and specify only addresses or address ranges within
emulation or target RAM or ROM. Or, you can remap memory so that the desired
addresses are no longer mapped as guarded.
710
Memory range overflow
Cause: Accessing a word or short word, for example display memory 0ffffffff
blocked word will cause a rounding error that overflows physical memory.
Action: Reduce memory display request.
725
Unable to load new memory map; old map reloaded
Cause: There is not enough emulation memory left for this request.
Action: Reduce the amount of emulation memory requested.
726
Unable to reload old memory map; hardware state unknown
Cause: System failure.
Action: Run performance verification (Terminal Interface pv command).
754
Memory modify aborted; next address: %s
Cause: This message is displayed if a break occurs during processing of a modify
memory command. The break could result from any of the break conditions
(except a software breakpoint) or could have resulted from a <CTRL>c break.
Chapter 12: Error Messages
Terminal Interface Messages
473
Advertisement
Table of Contents
