Marantz SA-12S1, Service Manual

Page: 16 / 164

14
5.2.3 Errorlog
Explanation:
The application errors will be logged in the NVRAM. The
maximum number of error bytes that will be visible is 16. The
first word (4 digits) of the byte is the component identification;
the last word is the error code.
The diagnostics software will present a combination of this
component identification plus an error code on the local
display (and on the attached terminal). The last reported
error is shown as < 00000000, the oldest visible error as
00000000> and the errors in between as < 00000000 >.
The devices that may report errors are the serial controller
(UART), the basic engine (BE), the slave processor (SLPH),
the SACD Stream Manager (SSM) and the SACD Media
Access (SMA). The identification of these components is as
follows:
The tables in the next chapters list the error code and
corresponding problem. The column ‘Explanation’ holds a
more elaborate description and the most likely reason for the
error.
Some examples:
002E0000 ( SMA reported a timeout error
0016010A ( Engine could not fully close or open the tray
D0010001 ( Flash checksum failed (for other DS errors, see
description of nucleui error codes in paragraph 5.4.
UART error codes
BE errors
SLPH error codes
SSM error codes
Component name Component identification
Serial controller (UART) 000A
Engine (BE) 0016
Slave Processor (SLPH) 001A
SACD Stream Manager (SSM) 001C
SACD Media Access (SMA) 002E
Diagnostic software (DS) Dxxx
Error
Number Error
name Explanation
0000 BUF_OVE
RFLOW To many characters were offered in
too little time. Reason: system was
too busy doing other jobs.
0001 COMMU-
NICATION Usually a protocol error. Reason:
bad connection between engine
and processor.
Error
Number Error name Explanation
0101 S2B_ILL_CO
MMAND Parameter(s) not valid for this
command. Reason: some com-
munication problem between
UART and engine.
0102 S2B_ILL_PAR
AM Command not allowed in this
state or unknown. Reason: see
S2B_ILL_COMMAND error
0103 S2B_SLEDGE Sledge could not be moved to
home position.
0104 S2B_FOCUS Focus failure
0105 S2B_MOTOR Motor could not reach speed
within timeout
0106 S2B_RADIAL Servo didn't get on track after
several retries.
0107 S2B_PLL_LO
CK PLL could not lock in Accessing
or Tracking state
0108 SBC_HEADE
R_TO Header timeout
0109 S2B_SBC_NO
T_FOUND Requested subcode item could
not be found.
010A S2B_TRAY Tray could not be opened or
closed completely.
010B S2B_TOC_RE
AD TOC could not be read within
timeout period.
010C S2B_JUMP Requested seek could not be
performed.
010D S2B_NON_EX
IST_SES Attempt to access a non-existing
session.
010E S2B_NON_EX
IST_BCA
01F0 S2B_OVERR
UN Too many bytes received over
S2B Reas on: see
S2B_ILL_COMMAND error
01F1 S2B_COMM_
TO Not enough bytes are received
over S2B Reason: see
S2B_ILL_COMMAND error
01F2 S2B_PARITY Byte received with parity error.
Reason: see
S2B_ILL_COMMAND error
01F3 S2B_ILL_PHA
SE CMD IDC is not valid, transmis-
sion out of sync. Reason: see
S2B_ILL_COMMAND error
01F4 S2B_ILL_NR_
OF_BYTES Byte count has an illegal value.
Reason: see
S2B_ILL_COMMAND error
Error
Number Error name Explanation
0000 COMMUNI-
CATION Error in I2C communication.
Reason: bad connection be-
tween slave processor and main
processor.
Error
Code Error name Explanation
0006 SP_SYNCER
ROR System cannot get synchronised
with sectors coming from disc.
Reason: Usually a damaged
disc or the player was dropped/
pushed during operation. If not,
the engine is malfunctioning.
0007 SP_EDCERR
OR Data coming from disc is dam-
aged. Reason: see
SP_SYNCERROR
0008 SP_CONTINU
ITYERROR Sequence of sectors coming
from disc is incorrect. Reason:
see SP_SYNCERROR
0009 DMX_CONTI
NUITYER-
ROR Sequence of sectors is incorrect.
Reason: problem with buffer
RAM
000A LLD_ERROR An illegal audio format was of-
fered to the decoder. Reason:
unknown audio type on disc or
problem with buffer RAM
000B BCU_ERROR Internal problem in Furore chip
Error
Number Error name Explanation