Table of Contents
Advertisement
667
Breakpoint code already exists: %s
Cause: You attempted to insert a breakpoint; however, there was already a
software breakpoint instruction at that location which was not already in the
breakpoint table.
Action: Your program code is apparently using the same instructions as used by
the software breakpoints feature. Remove the breakpoint instructions from your
program code and use the modify software_breakpoints set command to insert
them.
668
Breakpoint not added: %s
Cause: You tried to insert a breakpoint in a memory location which was not
mapped or was mapped as guarded memory.
Action: Insert breakpoints only within memory ranges mapped to emulation or
target RAM or ROM.
669
Breakpoint remove aborted
Cause: Occurs when <CTRL>c is entered when clearing a software breakpoint.
670
Breakpoint enable aborted
Cause: Occurs when <CTRL>c is entered when setting software breakpoints.
671
Breakpoint disable aborted
Cause: Occurs when <CTRL>c is entered when disabling software breakpoints.
680
Stepping failed
Cause: Stepping has failed for some reason.
Action: Usually, this error message will occur with other error messages. Refer to
the descriptions of the accompanying error messages to find out more about why
stepping failed.
684
Failed to disable step mode
Cause: System failure.
Action: Run performance verification (Terminal Interface pv command).
Chapter 12: Error Messages
Terminal Interface Messages
471
Advertisement
Table of Contents
