Table of Contents
Advertisement
Chapter 12: Error Messages
Terminal Interface Messages
157
Unable to set trace vector to <TRACE_ENTRY_address>; vector table write
failed
Cause: In order to step when using a foreground monitor, the trace vector must
contain the address of the monitor program's TRACE_ENTRY label (which equals
the monitor base address plus 800H). The step command reads the trace vector on
each step to make sure it contains the correct address value. If the trace vector does
not contain the correct value, the emulator attempts to write the correct value. This
error occurs when the vector table is in target memory and the write fails.
Action: Make sure the vector base register points to the correct location in target
memory and that the memory system is writeable and is operating correctly.
158
Trace vector modified to <TRACE_ENTRY_address> for single stepping
Cause: In order to step when using a foreground monitor, the trace vector must
contain the address of the monitor program's TRACE_ENTRY label (which equals
the monitor base address plus 800H). The step command reads the trace vector on
each step to make sure it contains the correct address value. If the trace vector does
not contain the correct value, the emulator attempts to write the correct value. This
message informs you the emulator was successful in writing the correct value to the
trace vector.
159
Unable to set trace vector to <TRACE_ENTRY_address>; vector table in
TROM
Cause: In order to step when using a foreground monitor, the trace vector must
contain the address of the monitor program's TRACE_ENTRY label (which equals
the monitor base address plus 800H). The step command reads the trace vector on
each step to make sure it contains the correct address value. If the trace vector does
not contain the correct value, the emulator attempts to write the correct value. This
error occurs when the vector table is in memory mapped as target ROM.
Action: If the vector table is really in target ROM memory, its trace vector must
already contain the correct address value.
162
Double bus fault occurred
Cause: This message informs you of a double bus fault in the emulation
microprocessor. The most common cause of this error message is running or
stepping from target memory locations that do not exist.
460
Advertisement
Table of Contents
