HP 64783A, Руководство пользователя

Страница: 545 / 816

Emulation memory access failed (Error 702)
Cause: This message is displayed if the emulator was unable to perform the
requested operation on memory mapped to the target system. In most cases, the
problem results from the emulator’s inability to break to the monitor to perform the
operation. Usually there are other error messages. Refer to them to fully
understand the cause of the error.
Action: See message "Unable to Break".
Emulator terminated hung bus cycle: <address> byte read (Status 170)
Cause: This status message will be displayed if the target system fails to provide
TA or TEA bus cycle termination for a particular cycle and the emulator terminates
the bus cycle in order to break from execution of the target program to execution
within the monitor, or to complete execution of a monitor command (which
accessed this memory address). This can happen on any access to target memory or
interlocked emulation memory (when you answered "Yes" to the "Emulator
Terminates Bus Cycles" attribute question).
The emulator will not terminate any hung bus cycles unless you explicitly say break
or you execute a monitor command (ie: "display memory 7000"). The emulator
will generate this status message each time it terminates a hung bus cycle. The
emulator never attempts to terminate bus cycles in program space (opcode fetches)
or for any addresses in the foreground monitor.
Enable breakpoint failed: <address> (Error 665)
Cause: System failure or target condition.
Action: Check memory mapping and configuration questions. This message is
usually accompanied by other messages. Look at those messages to better
understand the error and know which actions to take.
Chapter 12: Emulator Error Messages
Emulation memory access failed (Error 702)
515