The Inverse Assembler
When the analyzer captures a trace, it captures binary information.
The analyzer can then present this information in symbol, binary,
octal, decimal, hexadecimal, or ASCII. Or, if given information about
the meaning of the data captured, the analyzer can inverse assemble
the trace. The inverse assembler makes the trace list more readable
by presenting the trace results in terms of processor opcodes and data
transactions.
To use an inverse assembler
Most preprocessors include an inverse assembler in their software. Loading
the configuration file for the preprocessor sets up the logic analyzer to
provide certain types of information for the inverse assembler. This section
is provided in case you ever have to set up an analyzer for inverse assembly
yourself.
The inverse assembly software needs at least these five pieces of information:
•
Address bus. The inverse assembler expects to see the label ADDR, with
bits ordered in a particular sequence.
•
Data bus. The inverse assembler expects to see the label DATA, with bits
ordered in a particular sequence.
•
Status. The inverse assembler expects to see the label STAT, with bits
ordered in a particular sequence.
•
Start state for disassembly. This is the first displayed state in the trace list,
not
the cursor position. See the figure on the next page.
•
Tables indicating the meaning of particular status and data combinations.
The particular sequences that each label requires depends on the type of
chip the inverse assembler was designed for. Because of this, inverse
assemblers cannot generally be transferred between platforms.
To run the inverse assembler, you must be sure the labels are spelled
correctly as shown here, or as directed in your inverse assembler
documentation. Even a minor difference such as not capitalizing each letter
will cause the inverse assembler to not work.
3–20
Summary of Contents for 1660CS
Page 5: ...Introduction iv ...
Page 16: ...1 Logic Analyzer Overview ...
Page 24: ...2 Connecting Peripherals ...
Page 33: ...2 10 ...
Page 34: ...3 Using the Logic Analyzer ...
Page 55: ...3 22 ...
Page 56: ...4 Using the Trigger Menu ...
Page 75: ...4 20 ...
Page 76: ...5 Triggering Examples ...
Page 109: ...5 34 ...
Page 110: ...6 File Management ...
Page 119: ...6 10 ...
Page 120: ...7 Reference ...
Page 221: ...7 102 ...
Page 222: ...8 System Performance Analysis SPA Software ...
Page 241: ...SPA Time Interval System Performance Analysis SPA Software SPA measurement processes 8 20 ...
Page 252: ...9 Concepts ...
Page 284: ...10 Troubleshooting ...
Page 298: ...11 Specifications ...
Page 311: ...11 14 ...
Page 312: ...12 Operator s Service ...
Page 324: ...Troubleshooting Flowchart 2 Troubleshooting To use the flowcharts 12 13 ...
Page 337: ...Glossary 4 ...