HP 64746 User Manual page 513

606
Unable to run after CMB break
Cause: System failure or target condition.
Action: Run performance verification (Terminal Interface pv command), and
check target system.
608 Unable to break
Cause: This message is displayed if the emulator is unable to break to the monitor
because the emulation processor is reset, halted, or is otherwise disabled.
Action: First, look at the emulation prompt and other status messages displayed to
determine why the processor is stopped. If reset by the emulation controller, use
the break command to break to the monitor. If reset by the emulation system,
release that reset. If halted, try reset and break to get to the monitor. If there is a
bus grant, wait for the requesting device to release the bus before retrying the
command. If there is no clock input, perhaps your target system is faulty. It's also
possible that you have configured the emulator to restrict to real time runs, which
will prohibit temporary breaks to the monitor.
610
Unable to run
Cause: System failure or target condition.
Action: Run performance verification (Terminal Interface pv command), and
check target system.
611 Break caused by CMB not ready
Cause: This status message is printed during coordinated measurements if the
CMB READY line goes false. The emulator breaks to the monitor. When CMB
READY is false, it indicates that one or more of the instruments participating in the
measurement is running in the monitor.
Action: None, information only.
612 Write to ROM break
Cause: This status message will be printed if you have enabled breaks on writes to
ROM and the emulation processor attempted a write to a memory location mapped
as ROM.
Action: None (except troubleshooting your program).
Chapter 13: Error Messages
Terminal Interface Messages
513