Table of Contents
Advertisement
Software breakpoints should not be set, cleared, enabled, or disabled while the
CAUTION
emulator is running user code. If any of these commands are entered while the
emulator is running user code, and the emulator is executing code in the area where
the breakpoint is being modified, program execution may be unreliable.
All read accesses to the software breakpoint TRAP vector location will cause
the emulator to break into background. Only the read associated with the TRAP
instruction will cause a proper transfer to monitor. All other accesses will result in
undefined execution. Therefore, if software breakpoints are enabled, the TRAP
vector should not be accessed by any instruction other than a TRAP. Note that this
includes boot-up code that attempts to perform a checksum over the vector table
area. The status of the emulator may become undefined, and the monitor
program may become unusable.
This section shows you how to:
•
•
•
•
•
•
•
•
•
Display the breakpoints list.
Enable/disable breakpoints.
Set a permanent breakpoint.
Set a temporary breakpoint.
Set all breakpoints.
Deactivate a breakpoint.
Re-activate a breakpoint.
Clear a breakpoint.
Clear all breakpoints.
Chapter 6: Using the Emulator
Using Software Breakpoints
201
Advertisement
Table of Contents
