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

Страница: 575 / 816

Trig1 signal cannot be driven and received (Error 1302)
Cause: This error occurs when you attempt to specify the internal trig1 signal as the
trace arm condition while the same analyzer’s trigger output is currently driving the
trig1 signal. This error also occurs if you attempt to specify that the trigger output
drive the internal trig1 signal while that signal is currently specified as the arm
condition for the same analyzer.
Action: You can either change the arm or the trigger output specification; in either
case, make sure they do not use the same internal signal.
trig2 break (Async_Stat 619)
This status message will be displayed if you have used the internal trig2 line to
connect the analyzer trigger output to the emulator break input and the analyzer has
found the trigger condition. The emulator is broken to the monitor.
Trig2 signal cannot be driven and received (Error 1303)
Cause: This error occurs when you attempt to specify the internal trig2 signal as the
trace arm condition while the same analyzer’s trigger output is currently driving the
trig2 signal. This error also occurs if you attempt to specify that the trigger output
drive the internal trig2 signal while that signal is currently specified as the arm
condition for the same analyzer.
Action: You can either change the arm or the trigger output specification; in either
case, make sure they do not use the same internal signal.
Unable to access deMMUer while analysis trace is in process (Error 163)
Cause: You tried to issue a command that requires access to the deMMUer while
the analyzer was running a trace. You cannot load, enable or disable the deMMUer
while an analysis trace is in process.
Action: Wait for the trace to complete or stop the trace before changing the state of
the deMMUer.
Chapter 12: Emulator Error Messages
Trig1 signal cannot be driven and received (Error 1302)
545