October 13 1995, Draft 1
404
Addendum to –– Evaluating and Programming the 29K RISC Family
trsearchnext [<label> {<pattern> | <address>}]
trsearchprev [<label> {<pattern> | <address>}]
Normally, one specifies a search <pattern> for a selected <label>. However, in
the case where the <label> is ADDR, then an <address> should be provided instead.
In such case, UDB will convert the address, which may be specified as a symbol, into
a hexadecimal string of eight characters.
After a <label> and <pattern> have been specified, UDB remembers them to
allow for further searching without having to specify the <label> and <pattern>
again. In particular, the
Next
and
Prev
keys in the trace frame have been overloaded,
such that Ctrl–Shift–Clicking them will issue these commands with no parameters.
UDB supports the binding of buttons to macro commands. This is a convenient
means of issuing “trsearchnext” commands. The following udb.rc command
sequence assigns buttons to the macro table associated with the Trace frame. Note
that user programmed buttons should be restricted to the left hand side of the window.
The example command creates two buttons. The
next
button can be used initiate a
“trsearchnext” command. Because the command–string does not finish with a “\r”
character, the user can enter the <pattern> from the command line interface.
# macro table
#
––––––
macro m=mtrace –f “next” {lb1}
macro m=mtrace –f “prev” {lb2}
button position command
––––
–––––
––––––––––––––––– . . .
“{com}trsearchnext ADDR ”
“{com}trsearchprev ADDR ”
7.9.3 Selecting Trace Signals
In section 7.8 under the headings
MonTIP Commands
and
UDB Commands
,
techniques for formatting the trace display were presented. Groups of processor sig-
nals, such as the address bus, are grouped together and assigned labels. The user can
always rely on the following four labels being available for display: ADDR, DATA,
LINE, TYPE. Different 29K family members, and different system configurations,
will provide a number of other useful labels, such as R/_W. Given the limited size of
the trace display, it is necessary to limit the number of trace labels.
Depending on the source level debugger selected, or if MonTIP is being used to
format the trace display, there may be synonyms for the main trace labels. For exam-
ple: ADDR is also known as SYM by UDB, and as SYMADDR by MonTIP. These
alternatives to ADDR, enable the traced address values to be presented symbolically,
even if the logic analyzer is configured to display them in, say, hexadecimal. An alter-
native implementation would have been to support a format parameter for control-
ling the displaying of selected labels. But, so far, this has not been the route taken by
source level debugger implementors. Note that if the SYM label is selected, it is nec-
essary to load a UDB symbol file. This file is produced by the
mksym
utility.
The DASM column is a synonym for DATA presented in disassembly format.
The trace processing algorithms used with the Am29040 processor place