Table of Contents
Advertisement
616
BNC trigger break
Cause: This status message will be displayed if you have configured the emulator
to break on a BNC trigger signal and the BNC trigger line is activated during a
program run. The emulator is broken to the monitor.
617
CMB trigger break
Cause: This status message will be displayed if you have configured the emulator
to break on a CMB trigger signal and the CMB trigger line is activated during a
program run. The emulator is broken to the monitor.
618
trig1 break
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.
619
trig2 break
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.
620
Unexpected software breakpoint
Cause: If you have enabled software breakpoints, this message is displayed if a
software breakpoint instruction is encountered in your program that was not
inserted by a modify software_breakpoints set command and is therefore not in
the breakpoint table.
Action: Remove the breakpoint instructions in your code before assembly and link,
and use the modify software_breakpoints set command to reinsert them after the
program is loaded into memory.
621
Unexpected step break
Cause: System failure.
Action: Run performance verification (Terminal Interface pv command).
Chapter 13: Error Messages
Terminal Interface Messages
463
Advertisement
Table of Contents
