Philips SACD 1000/001 Service Manual page 28

GB 28 5. SACD 1000
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:
Component name
Serial controller (UART)
Engine (BE)
Slave Processor (SLPH)
SACD Stream Manager (SSM) 001C
SACD Media Access (SMA)
Diagnostic software (DS)
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
Error Error
Number name
0000 BUF_OVE
RFLOW
0001 COMMU-
NICATION
BE errors
Error Error name
Number
0101 S2B_ILL_CO
MMAND
0102 S2B_ILL_PAR
AM
0103 S2B_SLEDGE Sledge could not be moved to
0104 S2B_FOCUS
0105 S2B_MOTOR Motor could not reach speed
0106 S2B_RADIAL Servo didn't get on track after
0107 S2B_PLL_LO
CK
0108 SBC_HEADE
R_TO
Diagnostic software, trouble shooting and test instructions
Component identification
000A
0016
001A
002E
Dxxx
Explanation
To many characters were offered in
too little time. Reason: system was
too busy doing other jobs.
Usually a protocol error. Reason:
bad connection between engine
and processor.
Explanation
Parameter(s) not valid for this
command. Reason: some com-
munication problem between
UART and engine.
Command not allowed in this
state or unknown. Reason: see
S2B_ILL_COMMAND error
home position.
Focus failure
within timeout
several retries.
PLL could not lock in Accessing
or Tracking state
Header timeout
Error Error name Explanation
Number
0109 S2B_SBC_NO Requested subcode item could
T_FOUND not be found.
010A S2B_TRAY Tray could not be opened or
closed completely.
010B S2B_TOC_RE TOC could not be read within
AD timeout period.
010C S2B_JUMP Requested seek could not be
performed.
010D S2B_NON_EX Attempt to access a non-existing
IST_SES session.
010E S2B_NON_EX
IST_BCA
01F0 S2B_OVERR Too many bytes received over
UN S2B
S2B_ILL_COMMAND error
01F1 S2B_COMM_ Not enough bytes are received
TO over
S2B_ILL_COMMAND error
01F2 S2B_PARITY Byte received with parity error.
Reason:
S2B_ILL_COMMAND error
01F3 S2B_ILL_PHA CMD IDC is not valid, transmis-
SE sion out of sync. Reason: see
S2B_ILL_COMMAND error
01F4 S2B_ILL_NR_ Byte count has an illegal value.
OF_BYTES Reason:
S2B_ILL_COMMAND error
SLPH error codes
Error Error name Explanation
Number
0000 COMMUNI- Error in I2C communication.
CATION Reason: bad connection be-
tween slave processor and main
processor.
SSM error codes
Error Error name Explanation
Code
0006 SP_SYNCER System cannot get synchronised
ROR 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 Data coming from disc is dam-
OR aged.
SP_SYNCERROR
0008 SP_CONTINU Sequence of sectors coming
ITYERROR from disc is incorrect. Reason:
see SP_SYNCERROR
0009 DMX_CONTI Sequence of sectors is incorrect.
NUITYER- Reason: problem with buffer
ROR 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
Reason: see
S2B Reason: see
see
see
Reason: see