User`s guide

Debugging for DSP56800E
Command-Line Debugging
227Targeting MC56F83xx/DSP5685x Controllers
Command-Line Debugging
In addition to using the regular CodeWarrior IDE debugger windows, you also can
debug on the command-line. When you debug on the command-line, you can use:
• Commands included in the Tcl script language
• Additional debugging commands that are specific to the debugger
Tcl Support
This section describes how the command-line debugger handles Tcl support.
Automatically resolving clashing commands
Several command-line debugging commands clash with built-in Tcl commands. The
command-line debugger resolves them as shown in Table 8.2
when the mode is set to
auto.
Tcl support for executing script files
Tcl usually executes a script file as one large block; Tcl returns only after the entire
file executes. However, the run debugging command executes script files line by line.
If a particular line is not a complete Tcl command, the run command appends the
next line until it gets a complete Tcl script block.
For example, the Tcl source command executes the script in Listing 8.1
as one
block, but the run debugging command executes it as two blocks: the set statement
and the while loop.
Table 8.2 Resolving Clashing Commands
Command Resolution
load When you enter the command with one argument containing .eld or
.mcp, the command-line debugger loads the project. Otherwise, the
debugger calls the Tcl load command.
break When you enter the command with no argument and in a script file, the
command-line debugger calls the built-in Tcl break command. Otherwise,
the debugger uses the break command to control breakpoints.
close When you enter the close command with no argument, the command-line
debugger closes the current debugging session. Otherwise, the
debugger calls the built-in Tcl close command.