Eventide BD500, Руководство оператора

Страница: 45 / 58

BD500 Broadcast Profanity Delay Appendix F Diagnostics Page 41
©Eventide Inc. 1995-1999
doc release 10
D39 After the initial coprocessor boot and after the test suites,
the final operating system is uploaded to the coproces-
sor. This error message indicates that the communica-
tions is working but that readback of an internal memory
location failed.
D40 This is the same as D38 except that the first readback
worked and the second failed.
E01 At startup the coprocessor was looked for by inspecting
the registers in the coprocessor that indicate communi-
cations status. All status bits were set to 1, indicating
that the communications lines were floating. The mother-
board processor has decided that there is no coproces-
sor card installed. This is a fatal error.
E02 At startup the five volt power supply level is checked. This
indicates that the voltage was out of range.
E03 Errors occured during communications between the main
processor and the front panel coproessor. This message
indicates the number of errors per minute exceeded ac-
ceptable limites during run-time.
E04 Errors occured during communications between the main
processor and the front panel coproessor. This message
indicates the number of errors per minute exceeded ac-
ceptable limites during startup related operations..
E05 The front panel communications stopped working for a
long period of time. This error indicates that this hap-
pened during run-time. The UI has been instructed to abort
to BYPASS.
E06 The front panel communications stopped working for a
long period of time. This error indicates that this hap-
pened before run-time started.
E18 This indicates that the coprocessor is running and an-
swering but the audio processing loop isn’t running. If
this happens immediately after going from BYPASS to in-
line this means that the audio sample clock isn’t getting
to the coprocessor . This may be caused by a broken or
missing audio card.
E19 This error message indicates that during run-time the co-
processor has complained many times about getting an
audio card interrupt many times while the coprocessor
was busy processing an earlier audio card interrupt .
Normally a redundant audio card interrupt could indicate
that the sample rate glitched (not unlikely if using AES/
EBU). This is not supposed to happen many times in a
short period however.
E21 During run-time (after the coprocessor is already known
to be working) a failure was reported by the motherboard
processor where it appears the coprocessor failed to re-
ceive a word of information from the motherboard. The
motherboard processor eventually got tired of waiting. This
is most likely caused by a software crash on the copro-
cessor. The crash may have been caused by intermittent
hardware.
E22 Similar to E21, this error indicates that during run-time
the motherboard processor was waiting for the coproces-
sor to transmit a word of information to the motherboard
when it gave up waiting and generated this error mes-
sage.
E30 During run time a firmware error on the motherboard pro-
cessor occured. The specific error is that sethostwriteptr,
part of the motherboard to coprocessor transmit driver
suite, was called with bad parameters. This looks like a
programming bug but might (unlikely) have been caused
by a hardware problem on the motherboard.
E32 During run time the motherboard processor determined
that we arrived at a programming instruction waiting for
the coprocessor to finish processing a data word trans-
mission previously issued by the motherboard. We
shouldn't get here because the previous process that
would have issued that hardware interrupt would not have
exited without the dataword transmission being cleared.
This means that the coprocessor trashed it's own incom-
ing data bits (TxRDY/TxEMPTY) without the motherboard
CPU initiating it, or that the motherboard program has a
bug and somehow got out of the transmit function without
waiting for the data bits to be clear.
E33 During run time the motherboard processor determined
that the coprocessor was in a bad state. The coproces-
sor has a pending hardware interrupt (CVR full) that should
have been handled already. The driver indicating the er-
ror is sethostwriteptr, part of the system to transmit a word
to the coprocessor. We shouldn't to this condition because
the previous motherboard driver that would have issued
that hardware interrupt would not have exited without the
interrupt being cleared. This means that the coprocessor
went back into the interrupt state (CVR full) without the
motherboard CPU initiating it, or that the motherboard pro-
gram has a bug. Note that the receive driver has been
called and exited successfully many times since the last
power-up.
E34 This is the opposite of E33. This error occurs when wait-
ing to leave sethostwriteptr, part of the coprocessor/moth-
erboard processor transmit driver. This error, issued only
during run time, indicates that the coprocessor was sent
a hardware interrupt to receive a data word and the co-
processor never accepted the hardware interrupt. This
means that the coprocessor is locked up with interrupts
disabled, or that there is a hardware function in the moth-
erboard to coprocessor communications, or that the soft-
ware on the motherboard processor is wrong. Note that
the receive driver has been called and exited success-
fully many times since the last power-up.
E35 This is the opposite of E32. This error occurs during run
time when waiting to leave sethostwriteptr, part of the
motherboard to coprocessor communications suite. This
error, issued only during run time, indicates that the co-
processor was sent a data word and the coprocessor never
read the word, clearing the TxRDY/TxEMPTY bits.. This
means that the coprocessor receiver program is not func-
tioning. Note that this driver has been called and exited
successfully many times since the last power-up.
E40 During run time a firmware error on the motherboard pro-
cessor occured. The specific error is that sethostreadptr,
part of the motherboard to coprocessor receive driver
suite, was called with bad parameters. This looks like a
programming bug but might (unlikely) have been caused
by a hardware problem on the motherboard. Note that
this driver has been called and exited successfully many
times since the last power-up.
E41 During run time, the driver for motherboard to coproces-
sor receive communications determined that the copro-
cessor was hung up processing the previous message
(TxRDY/TxEMPTY). This indicates that the coprocessor
did something or that the motherboard program has a bug.
Note that the receive driver has been called and exited
successfully many times since the last power-up.