Table of Contents
Advertisement
Error Messages
Trace error during CMB execute (692)
Cause: System failure.
Action: Run performance verification (Terminal Interface pv command).
Trace file not found
Cause: You tried to load trace data file that does not exist.
Action: Find the correct name and path of the trace data file and try again.
Transfer failed to start (413)
Cause: Communication link or transfer protocol incorrect.
Action: Check link and transfer options.
trig1 break (618)
Cause: This status message will be displayed if you use the break_on_trigger
syntax of the trace command and the analyzer has found the trigger
condition while tracing a program run. The emulator is broken to the
monitor.
trig2 break (619)
Cause: This status message will be displayed if you have used the internal
trig2 line to connect the analyzer or external analyzer trigger output to the
emulator break input and the analyzer has found the trigger condition. The
emulator is broken to the monitor.
Trigger delay out of bounds: <bounds> (2042)
Cause: This error occurs when you attempt to specify an external timing
trigger delay outside the valid range. The external timing trigger delay must
be between 0 and 10 ms (in 10 ns increments).
Action: Re-enter the command with the trigger delay within the bounds
shown.
481
Advertisement
Table of Contents
