Table of Contents
Advertisement
If trace disassembly appears to be partially incorrect
If trace disassembly appears to be partially
incorrect
Check to see if the analyzer began disassembly of the trace on a long-word
boundary but the instruction started on the low word within the long word. This
will make disassembly incorrect. You can start disassembly on the low word
within the long word by use of tl -d -ol <trace list line number>.
If the trace list seems correct for a few states after disassembly starts, and then it
seems incorrect, restart disassembly of the trace at the low word where disassembly
first becomes incorrect tl -ol <trace list line number>.
If an instruction seems to have incorrect data associated with it, you can read down
the trace list to see if you can find correct data for the instruction on another line.
You can cause the disassembler to realign the instruction with the correct data by
entering a command like tl -d -ol <trace list line number containing instruction>
<trace list line number containing data>. For example, tl -d -0l 38 47.
If you see unexplained states in the trace list
Check to see that the sequence, storage, and trigger specifications are set up to
exclude the states you don't need.
If you are using the built-in terminal interface, try using the tl <instruction_state>
<operand_state> command to inform the dequeuer which operand state belongs
with the named instruction state.
If you are using the built-in terminal interface, try using the -ol option to the tl
command to begin disassembly from the low word of the starting state, instead of
the high word.
Check to see if some of the program in the range covered by the trace might have
executed from internal processor RAM memory. If so, these cycles won't appear in
the trace list, which will confuse the disassembler. Use the show cycles feature of
the processor to make internal RAM cycles visible to the analyzer. Obtain the
Chapter 6: Solving Problems
111
Advertisement
Table of Contents
