Texas Instruments CDT370, User Manual

Page: 42 / 83

Trace Commands
3-6
To select the frame to display within the Inspect window, enter an adequate
frame number, select the Bottom frame (with the
ALT B
keys or by clicking
it with the mouse), or select the Top frame (with the
ALT T
keys or by clicking
it with the mouse). Once the choice is made, simply quit the Position window
with the
ALT O
(for OK) or
ALT A
(for Cancel). The Trace Window will then
be updated accordingly.
T (Top Samples) positions the screen at the top of the trace buffer. The oldest
samples in the buffer are displayed, starting with index 0.
B (Bottom Samples) positions the screen at the bottom of the trace buffer. The
most recent samples in the buffer are displayed. If the buffer is full, the highest
index is 2046. Otherwise, the highest index is one less than the total.
Saving trace information (the S command)
When the Save Command is invoked, the following dialog box is opened:
Save trace buffer
File name [................................................................]
<<OK>> <Cancel>
Start [.....] to End [.....]
The Save command saves trace samples to a disk file for later inspection. Any
number of samples can be saved, up to the number that were recorded. Just
type in the filename of the file where you want to store the trace information
and hit the enter key or click the O (for O. K.) with the mouse.
Enter the indices of the first and last samples if you want specific frames to be
saved.
The default start index is 0, and the default end index is the last sample taken;
using both defaults causes the whole trace buffer to be saved. The specified
trace samples are read from the emulator, formatted just as they would be for
display on the screen, and written to the file. If many samples are saved, this
process can be somewhat lengthy. For example, saving a full trace buffer of
2048 samples may take approximately 30 seconds.
Execute from the trace screen
You can execute code while you are viewing the trace screen. You use the F8
or F10 command from the trace menu. After the code executes, the debugger
will update the trace screen by reading the new trace samples from the emula-
tor and displaying the most recent ones.