Motorola CPU32 User's Guide download pdf (Page 98)

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 may be 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.

Ensure that each logic analyzer pod is connected to the correct

preprocessor connector.

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. 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 require you to

connect cable 5 to analyzer pod 2. See Chapter 2 for connection information.

Check the activity indicators for status lines locked in a high or low

state.

Verify that the STAT, DATA, and ADDR format labels have not been

modified from their default values.

These labels must remain as they are configured by the configuration file. Do

not change the names of these labels or the bit assignments within the labels.

Some preprocessors also require other data labels. See Chapter 3 for more

information.

E2480A Motorola CPU32 Preprocessor Interface 5–7

1 2 ... 93 94 95 96 97 98 99 100 101 102 103 ... 106 107

No comments

Motorola CPU32 User's Guide Page 98