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

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

Page 36 Appendix F Diagnostics BD500 Broadcast Profanity Delay
©Eventide Inc. 1995-1999
doc release 10
A33 During start-up 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.
A34 This is the opposite of A33. This error occurs when wait-
ing to leave sethostwriteptr, part of the coprocessor/moth-
erboard processor transmit driver. This error, issued only
during start-up, 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.
A35 This is the opposite of A32. This error occurs during
start-up when waiting to leave sethostwriteptr, part of the
motherboard to coprocessor communications suite. This
error, issued only during start-up, 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.
A40 During start-up a firmware error on the motherboard pro-
cessor occurred. The specific error is that sethostread-
ptr, 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.
A41 During start-up, 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.
A42 During start-up the motherboard processor determined
that we arrived at a programming instruction waiting for
the coprocessor to finish processing a hardware interrupt
previously issued by the motherboard. The driver indicat-
ing the error is attempting to receive a word from the co-
processor 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 ex-
ited 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.
A43 This is the opposite of A42. This error occurs when wait-
ing to leave sethostreadptr, part of the coprocessor/moth-
erboard receive drivers. This error, issued only during
start-up, indicates that the coprocessor was sent a hard-
ware interrupt to transmit a data word and the coproces-
sor 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 motherboard to
coprocessor communications, or that the software on the
motherboard processor is wrong. Note that the receive
driver has been called and exited successfully many times
since the last power-up.
A44 This is the opposite of A41. This error occurs during
start-up when waiting to leave sethostreadptr, part of the
coprocessor/motherboard receive drivers. This error, is-
sued only during start-up, indicates that the coprocessor
was sent an address word and the coprocessor never read
the word, clearing the TxRDY/TxEMPTY bits.. This means
that the coprocessor receiver program is not functioning.
Note that the receive driver has been called and exited
successfully many times since the last power-up.
A45 This error occurs during start-up when waiting to leave
sethostreadptr, part of the coprocessor/motherboard re-
ceive drivers. This error, issued only during start-up, indi-
cates that the coprocessor was sent the address word
and the coprocessor read the address word, but never
sent the first data word. This means that the coprocessor
receiver program is not functioning. Note that the receive
driver has been called and exited successfully many times
since the last power-up.
A46 This error indicates a firmware error on the motherboard
processor. The error was reported during start-up when
a part of the motherboard processor driver to write to the
coprocessor was called during a read sequence.
A47 This error indicates a firmware error on the motherboard
processor. The error was reported during start-up when
a part of the motherboard processor driver to read from
the coprocessor was called during a write sequence.
A48 During start-up a test is made to see if the motherboard
CPU data space was initialized by the motherboard boot
code. This error indicates initialization did not take place.
This is a firmware error.
A50 The factory burn-in coprocessor external memory test pro-
gram was uploaded to the coprocessor successfully and
then run. This error message indicates that the test pro-
gram failed to make it to the first marker. This means that
the coprocessor test program crashed. This does not in-
dicate a memory failure although there may be a short
between memory select lines and processor control lines.
A51 The factory burn-in coprocessor external memory test pro-
gram was uploaded to the coprocessor successfully and
then run. This error message indicates that the test pro-
gram failed to make it to the second marker (end of write
phase). This means that the coprocessor test program
crashed. This does not indicate a memory failure although
there may be a short between memory select lines and
processor control lines.
A52 The factory burn-in coprocessor external memory test pro-
gram was uploaded to the coprocessor successfully and
then run. This error message indicates that the test pro-
gram failed to make it to the second marker (end of pre-
refresh read back phase). This means that the coproces-
sor test program crashed. This does not indicate a memory
failure although there may be a short between memory
select lines and processor control lines.