HP 1660CS-Series User Manual page 335

Glossary
storage qualification Storage
qualification allows you to specify
the type of information to be stored
in memory. Use storage qualification
to prevent memory from being filled
with unwanted activity.
symbol An alphanumeric name
given to a specified bit-pattern or
range for the bits in a particular label
(see label). A label can have many
symbols, each having a different
meaning. For example, if the CYCLE
label includes the bits for the
Read/Write (R/W) and I/O signals,
one symbol might be I/O READ, with
I/O and R/W both high, while another
symbol might be I/O WRITE, with I/O
high and R/W low. Symbols are
named and specified in the Format
menu. Symbols are available only
when the associated label is on. Sym-
bols are also available for defining
trigger terms. See also label and
term.
term A resource for specifying
storage conditions or trigger condi-
tions. A term uses the bits in a label
to identify the condition for storage
or triggering. If symbols have pre-
viously been defined for the label,
they can be used as the conditions,
or you can specify new patterns or
ranges. For example, if the CYCLE la-
bel includes the symbols I/O READ
and I/O WRITE, term "a" could be I/O
Glossary–2
READ and term "b" could be I/O
WRITE, and the trigger/storage
macro could be to start storing at
term "a" and stop storing at term "b."
trace The record of target system
activity stored by the state or timing
analyzer. This record can be dis-
played as either a waveform or a
listing. See also listing and wave-
form.
trigger A reference event around
which you want to gather informa-
tion. In the analyzer, you might want
to trigger on a glitch in hardware or
entry to a subroutine in software.
When beginning, you might want to
trigger on the first occurrence of any
kind (trigger on "anystate"). As you
learn more about the problem you
are trying to isolate, you may enter
more specific trigger conditions.
When you want to gather a continu-
ous stream of activity leading up to a
system crash, you will want to trig-
ger on "no state." Note that some
microprocessors fetch instructions
on 32-bit boundaries. If you are trac-
ing activity of one of these
processors, and you specify trigger
on an address that is not on a 32-bit
boundary, that address will never ap-
pear on the address bus; therefore,
the analyzer will never find its trig-
ger. Make sure you specify triggers
that the analyzer will find. The state