Table of Contents
Advertisement
Error Messages
Break failed (602)
Cause: The break command was unable to break the emulator to the monitor.
Action: Determine why the break failed, then correct the condition and retry
the command. See message 608.
Breakpoint code already exists: %s (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: 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.
Breakpoint disable aborted (671)
Cause: Occurs when <CTRL>c is entered when disabling software
breakpoints.
Breakpoint enable aborted (670)
Cause: Occurs when <CTRL>c is entered when setting software breakpoints.
Breakpoint list full; not added: %s (664)
Cause: The software breakpoint table is already reached the maximum of 32
breakpoints. The breakpoint you just requested, with address %s, was not
inserted.
Action: Clear breakpoints that are no longer in use. Then, set the new
breakpoint.
Breakpoint not added: %s (668)
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.
Breakpoint remove aborted (669)
Cause: Occurs when <CTRL>c is entered when clearing a software
breakpoint.
449
Advertisement
Table of Contents
