HP 1660CS, Руководство пользователя

Страница: 291 / 347

Inverse Assembler Problems
This section lists problems that you might encounter while using the
inverse assembler.
When you obtain incorrect inverse assembly results, it may be unclear
whether the problem is in the preprocessor or in your target system. If
you follow the suggestions in this section to ensure that you are using
the preprocessor and inverse assembler correctly, you can proceed
with confidence in debugging your target system.
No inverse assembly or incorrect inverse assembly
This problem is due to incorrect synchronization, modified configuration,
incorrect connections, or a hardware problem in the target system. A locked
status line can cause incorrect or incomplete inverse assembly.
Verify that the inverse assembler has been synchronized by placing an
opcode at the top of the display (not at the input cursor) and pressing
the Invasm key.
Because the inverse assembler works from the first line of the trace display ,
if you jump to the middle of a trace and select Invasm, prior trace states are
not disassembled correctly. If you move to several random places in the trace
list and select Invasm each time, the trace disassembly is only guaranteed to
be correct from the top of the display forward for each selection.
See Also
"The Inverse Assembler" in chapter 3.
Ensure that each analyzer pod is connected to the correct preprocessor
cable.
There is not always a one-to-one correspondence between analyzer pod
numbers and preprocessor cable numbers. Preprocessors must supply
address (ADDR), data (DATA), and status (STAT) information to the
analyzer in a predefined order, so the cable connections for each
preprocessor are often altered to support that need. Thus, one preprocessor
might require that you connect cable 2 to analyzer pod 2, while another will
10–8