User`s manual

Motorola Debugging C and Assembly Code 3-1
Chapter 3
Debugging C and Assembly Code
This chapter walks you through sample programs in both C and assembly language to
highlight the debugging facilities in Suite56 tools, particularly the hardware debugger
(such as
ads56800 or gds56300) and the simulator (such as sim56600 or gui56300).
The interfaces—both graphic and text-based—to the Suite56 simulator were deliberately
designed to be as similar as possible to those of the Suite56 ADS debugger. You can use
one very much as you use the other. Consequently, throughout this chapter, we will refer
to the graphic user interface and the text-based interface without distinguishing the
simulator from the Suite56 hardware debugger.
3.1 Initializing a Debugging Environment
There are many ways to customize your debugging environment, whether you use the
graphic user interface or the text-based, command-line interface. The following sections
outline those possibilities. For more detail about each topic, see the Motorola ADS User’s
Manual, particularly Chapter 3 about commands and Chapter 4 about the graphic user
interface, or the Motorola DSP Simulator Reference Manual, Chapter 9, about its graphic
user interface.
3.1.1 Choosing Preferences
To control which windows open automatically when you start the
debugger, in the graphic user interface, choose the File menu, and
choose Preferences. When the Preferences dialogue box opens, select
the windows that you want to open automatically at start up.
Additionally, if you click the Font button in that dialogue box, another
dialogue box opens for you to choose from the fonts available on your
system.
In the text-based interface, you set your preferences in a resource macro
file, as documented in the reference manual and explained in Section 5.1, "How do I
customize Suite56 tools for my tasks?," on page 5-1.