User`s guide

Debugging for DSP56800E
Command-Line Debugging
228
Targeting MC56F83xx/DSP5685x Controllers
Listing 8.1 Example Tcl Script
set x 0;
while {$x < 5}
{
puts "x is $x";
set x [expr $x + 1]
}
NOTE The run debugging command synchronizes the debug events
between blocks in a script file. For example, after a go, next, or
step debugging command, run polls the debugging thread state
and refrains from executing the next line or block until the debugging
thread stops. However, the Tcl source command does not consider
the state of the debugging thread. Consequently, use the run
debugging command to execute script files that contain these
debugging commands: debug, go, next, stop, and kill.
Tcl support for using a start-up script
You can use a start-up script with the command-line debugger. (You can specify
command-line debugger commands in the script. For example, you might want to set
an alias or a color configuration.)
Name the start-up script CmdLineDefault.tcl. The command-line debugger
executes the start-up script the first time you open the command-line debugger
window, provided that the file is in the correct directory for the host platform you are
using. For Windows, place CmdLineDefault.tcl in the
\bin\Plugins\Support folder.
NOTE
Backup or rename the original version of CmdLineDefault.tcl
before overwriting it with your own customized version. It is always
a good idea to include any commands in the original
CmdLineDefault.tcl script in your customized version.