Table of Contents
Advertisement
Chapter 12: Emulator Error Messages
Break condition configuration aborted (Error 653)
Break condition configuration aborted (Error 653)
Cause: Occurs when <CTRL> c is entered during bc display.
Break condition must be specified (Error 652)
Cause: You tried to define a breakpoint without specifying the break condition to
enable or disable.
Action: Reenter the breakpoint command along with the enable/disable flag and the
break condition you wish to modify.
Break due to cause other than step (Error 689)
Cause: An activity other than a step command caused the emulator to break. This
could include any of the break conditions or a <CTRL> c break.
Breakpoint code already exists: <address> (Error 667)
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: Remove the breakpoints from your program code and try to insert
breakpoints again.
Breakpoint disable aborted (Error 671)
Cause: Occurs when <CTRL> c is entered when disabling software breakpoints.
Breakpoint enable aborted (Error 670)
Cause: Occurs when <CTRL> c is entered when setting software breakpoints.
Breakpoint not added: <address> (Error 668)
Cause: The emulator tried to insert a breakpoint in a memory location which could
not be accessed.
Action: Insert breakpoints only within memory ranges mapped to emulation or
target RAM or ROM.
406
Advertisement
Table of Contents
