Page 42
Appendix F Diagnostics
BD500 Broadcast Profanity Delay
©Eventide Inc. 1995-1999
doc release 10
E42
During run time 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.
E43
This is the opposite of E42. This error occurs when wait-
ing to leave sethostreadptr, part of the coprocessor/moth-
erboard receive drivers. This error, issued only during
run time, 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.
E44
This is the opposite of E41. This error occurs during run
time when waiting to leave sethostreadptr, part of the co-
processor/motherboard receive drivers. This error, issued
only during run time, 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.
E45
This error occurs during run time when waiting to leave
sethostreadptr, part of the coprocessor/motherboard re-
ceive drivers. This error, issued only during run time, in-
dicates 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.
E46
This error indicates a firmware error on the motherboard
processor. The error was reported during run time when
a part of the motherboard processor driver to write to the
coprocessor was called during a read sequence.
E47
This error indicates a firmware error on the motherboard
processor. The error was reported during run time when
a part of the motherboard processor driver to read from
the coprocessor was called during a write sequence.
E90
During run time the UI sent a bad command to the copro-
cessor drivers. This would indicate a firmware error.
E91
The configuration storage drivers reported a firmware er-
ror where a call was made to the driver with an invalid
register number.
E92
The User Interface program reports a firmware error where
a change state was issued with the same state number
as the previous state.
E93
During start-up the configuration storage drivers reported
a firmware error. Too many configuration storage elements
are defined. This normally happens during software de-
velopment when changes to the storage requirements are
made.
E94
During run-time the auxiliary port driver (delayed control
lines) reported that the delay amount is longer than al-
lowed. This would indicate a firmware error.
E95
The configuration storage drivers indicate a failure in firm-
ware where the initialization pointers in the configuration
table are not correct.
EA1
During DSP_START1 a firmware error on the motherboard
processor occurred. The specific error is that sethost-
writeptr, 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.
EA2
During DSP_START1 a firmware error on the motherboard
processor occurred. The specific error is that sethost-
readptr, 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.
EA3
This error message indicates two problems. The first is
that a firmware or hardware error occurred. The second
is that we don't know what the error message was. This
itself is a firmware error. The error was reported during
DSP_START1.
EA4
During DSP_START2 a firmware error on the motherboard
processor occurred. The specific error is that sethost-
writeptr, 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.
EA5
During DSP_START2 a firmware error on the motherboard
processor occurred. The specific error is that sethost-
readptr, 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.
EA6
This error message indicates two problems. The first is
that a firmware or hardware error occurred. The second
is that we don't know what the error message was. This
itself is a firmware error. The error was reported during
DSP_START2.
F01
During burn-in test operation the audio board initializa-
tion couldn't identify the audio card. This could indicate
there is a new audio card unknown to this software ver-
sion, that the ID # is incorrect on the card, or it could be
an interconnect problem between the motherboard and
the audio card.
F03
During burn-in test operation the auxiliary port driver (de-
layed control lines) reported that the delay amount is
longer than allowed. This would indicate a firmware er-
ror.
F05
During burn in test operation the UI sent a bad command
to the coprocessor drivers. This would indicate a firm-
ware error.
