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

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

BD500 Broadcast Profanity Delay Appendix F Diagnostics Page 43
©Eventide Inc. 1995-1999
doc release 10
F07 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 read back of an internal memory
location failed. This message was generated during burn-
in test operation.
F08 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 read back of an internal memory
location failed. This message is similar to F07 except that
the 1st word read back was correct and the 2nd was wrong.
This message was generated during burn-in test opera-
tion.
F09 During burn-in test operation the audio init function was
unable to initialize the input or output hardware on a digi-
tal audio card.
F10 During burn-in test operation the audio init function was
unable to initialize the input hardware on a digital audio
card.
F11 During burn-in test operation the audio init function was
unable to initialize the output hardware on a digital audio
card.
F12 The DSP DRAM has been checked via the DSP start-up
memory test. It passed the 1st memory test. However,
the 2nd test determined that the DRAM is small and not
suitable to be used with the installed audio card. The origi-
nal BD500 audio card could be supported with this size
DSP. The installed audio card needs more RAM for sup-
port. This message is reported during burn-in test opera-
tion.
F13 This error message indicates that during burn-in test op-
eration the coprocessor has complained many times about
getting an audio card interrupt many times while the co-
processor was busy processing an earlier audio card in-
terrupt. Normally a redundant audio card interrupt could
indicate that the sample rate glitched (not unlikely if us-
ing AES/EBU). This is not supposed to happen many times
in a short period however.
F14 During burn-in test operation the coprocessor is initial-
ized with the boot software, having passed several tests.
In this part of the program the sample clock interrupt sig-
nal to the coprocessor is being tested. This error indi-
cates that the sample clock is not running at all, even
though the current motherboard sample clock setting has
it that it should. Check the audio card, DSP card and
sample clock generator.
F16 During burn-in test operation the coprocessor is initial-
ized with the boot software, having passed several tests.
In this part of the program the sample clock interrupt sig-
nal to the coprocessor is being tested. This error indi-
cates that the sample clock is running slower than it
should, given the current motherboard sample clock set-
ting. Check the audio card, DSP card and sample clock
generator.
F17 During burn-in test operation the coprocessor is initial-
ized with the boot software, having passed several tests.
In this part of the program the sample clock interrupt sig-
nal to the coprocessor is being tested. This error indi-
cates that the sample clock is running faster than it should,
given the current motherboard sample clock setting.
Check the audio card, DSP card and sample clock gen-
erator.
F28 During burn-in test operation the audio board initializa-
tion read a 0 for the audio card ID. This could indicate
that the audio card is not installed, that the ID # is incor-
rect on the card, or that there is an interconnect problem
between the motherboard and the audio card.
F45 During burn-in test operation (after the coprocessor is al-
ready known to be working) a failure was reported by the
motherboard processor where it appears the coproces-
sor failed to receive a word of information from the moth-
erboard. The motherboard processor eventually got tired
of waiting. This is most likely caused by a software crash
on the coprocessor. The crash may have been caused by
intermittent hardware.
F46 This error indicates that during burn-in test operation the
motherboard processor was waiting for the coprocessor
to transmit a word of information to the motherboard when
it gave up waiting and generated this error message.
F47 During burn-in test operation a firmware error on the moth-
erboard processor occurred. The specific error is that set-
hostreadptr, part of the motherboard to coprocessor re-
ceive 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 success-
fully many times since the last power-up.
F48 During burn-in test operation the driver for motherboard
to coprocessor receive communications determined that
the coprocessor was hung up processing the previous
message (TxRDY/TxEMPTY). This indicates that the co-
processor 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.
F49 During burn-in test operation the motherboard processor
determined that we arrived at a programming instruction
waiting for the coprocessor to finish processing a hard-
ware interrupt previously issued by the motherboard. The
driver indicating the error is attempting to receive a word
from the coprocessor during sethostreadptr, part of the
coprocessor to motherboard communications driver. We
shouldn't get to this condition because the previous 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 program has a bug. Note that the
receive driver has been called and exited successfully
many times since the last power-up.
F50 This is the opposite of F49. This error occurs when wait-
ing to leave sethostreadptr, part of the coprocessor/moth-
erboard receive drivers. This error, issued only during
burn-in test operation , indicates that the coprocessor was
sent a hardware interrupt to transmit a data word and the
coprocessor 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.