Table of Contents
Advertisement
Action: Determine why the break failed, then correct the condition and retry the
command. See message 608.
603
Read PC failed during break
Cause: System failure or target condition.
Action: Try again.
604
Disable breakpoint failed: %s
Cause: System failure or target condition.
Action: Run performance verification (Terminal Interface pv command), and
check target system.
605
Undefined software breakpoint: %s
Cause: The emulator has encountered a software breakpoint in your program that
was not inserted with the modify software_breakpoints set command.
Action: Remove the breakpoint instructions in your code before assembly and link.
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.
Chapter 13: Error Messages
Terminal Interface Messages
461
Advertisement
Table of Contents
