Denon AVR-E300 Service Manual page 50

Error
Details of Error code
Code
Connection to DPMS timed out
39
when Main CPU was rewritten.
Error (NG) message was received
3A when firmware was downloaded or
Main CPU was rewritten.
Error (line congestion) message
received when downloading
3B
firmware when Main CPU was
rewritten.
Error (connection failure) message
received when downloading
3C
firmware when Main CPU was
rewritten.
Failure to acquire (Boot Loader
3D Mode) IP address before rewriting
DM860A (AutoIP).
Failure to acquire (Boot Loader
3E Mode) IP address before rewriting
DM860A (when timed out).
Log-in to DPMS failed when
50 firmware such as DSP and PLD
was rewritten.
Line, etc., is busy when the log-in to
51 DPMS when firmware such as DSP
and PLD was rewritten.
Connection to DPMS failed when
52 firmware such as DSP and PLD
was rewritten.
Error message received regarding
firmware data after the log-in to
54
DPMS when firmware such as DSP
and PLD was rewritten.
When firmware such as DSP and
PLD was rewritten, request was
55
made for firmware data after the
log-in to DPMS, but it timed out.
Downloading firmware failed after
the log-in to DPMS when firmware
56
such as DSP and PLD was
rewritten.
Firmware download error received
(line congestion) after the log-in to
57
DPMS when firmware such as DSP
and PLD was rewritten.
Firmware download error received
(connection failure) after the log-
58
in to DPMS when firmware such as
DSP and PLD was rewritten.
NACK was received when "C"
5A
command sent to DSP, PLD etc.
NACK was received when "L"
5B
command sent to DSP, PLD etc.
Display
C o n n e c t i o n F a i l 3 9
D o w n l o a d
D o w n l o a d
D o w n l o a d
C o n n e c t i o n F a i l 3 D
C o n n e c t i o n F a i l 3 E
L o g i n f a i l e d
S e r v e r i s
C o n n e c t i o n F a i l 5 2
U p d a t i n g
U p d a t i n g
D o w n l o a d
D o w n l o a d
D o w n l o a d
C o n n e c t i o n F a i l 5 A
U p d a t i n g
50
Check the network connection.
Carry out the update in an
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 3 A
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 3 B
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 3 C
environment that has little network
load.
Check the network connection.
Carry out the update in an
environment that has little network
load.
Check the network connection.
Carry out the update in an
environment that has little network
load.
Carry out the update in an
environment that has little network
5 0
load.
Carry out the update in an
environment that has little network
b u s y 5 1
load.
Check the network connection.
Carry out the update in an
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 5 4
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 5 5
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 5 6
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 5 7
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Carry out the update in an
f a i l 5 8
environment that has little network
load.
Turn off and on the power.
Updating starts automatically.
Turn off and on the power.
f a i l 5 B
Updating starts automatically.
Coping strategies