User`s manual

3-22 Suite56 DSP Tools User’s Manual Motorola
Symbolic Debugging in Assembly Code
3.3.1 Setting Breakpoints in Assembly Code
This section discusses software breakpoints in debugging an assembly program. The
observations about software breakpoints in Section 3.2.2, "About Software Breakpoints in
a C Program," on page 3-8, also apply to software breakpoints in assembly code.
For details about hardware breakpoints, see the family reference manual (e.g., Motorola
DSP56600 Family Manual) and the device manual (e.g., Motorola DSP56602 User’s
Manual), particularly chapters about the OnCE module and programming practices, for
your target device. Section 4.3, "Finding Well Hidden Bugs," on page 4-7, also offers
guidance about hardware breakpoints.
Breakpoints can have several different effects. How you set the breakpoint depends in part
on the effects that you want to achieve:
• To set a halt breakpoint.
In the graphic user interface, double-click in the Assembly window on the
instruction where you want the break to occur. The break command then appears
automatically in the Command window, and the Assembly window highlights the
address you clicked.
• To set a breakpoint that increments a counter:
In the graphic user interface, from the Execute menu, choose
Breakpoint, and then select Set. A dialogue box appears for
you to indicate in the Action pane which counter to increment.
•To set a breakpoint that writes to a Session window:
In the graphic user interface, from the Execute menu, choose
Breakpoint, and then select Set. In the dialogue box that
appears then, indicate Note in the Action pane of the window.
Regardless of how you set them, breakpoints are numbered, so that you can refer to them
as you watch them, disable them (i.e., turn them off), reenable them (i.e., turn them on
again), or direct execution to continue until it reaches a particular breakpoint. Moreover,
you can set more than one breakpoint at the same place to achieve more than one effect
(e.g., halt and increment a counter and write to the Session window and execute a
user-defined routine).
To continue execution after a breakpoint, in the graphic user interface, click the Go
button. In the text-based interface, type the
go command on the command line.