Yamaha DVD-C940 Service Manual page 18

DVD-C940/DV-C6680
QQ
3 7 63 1515 0
After one loop cycle: Display the 3-digit module bits
together with the last error code which occured in the loop
test. The 4 digits at the right side of the display (fig. 34) show
the last error that was found during the loop test. The leftmost
two digits (54) of this code indicates which nucleus resulted in
a fault. The rightmost two digits (03) refer to the faultcode
within that nucleus.
6.1 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)
SACD Media Access (SMA)
TE
L 13942296513
Diagnostic software (DS)
The tables in the next chapters list the error code and
corresponding problem. The Explantion column has a more
detailed 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).
UART Error Codes
Error Error
Number name
0000 BUF_OVE
RFLOW
0001 COMMUNI
CATION
0002 TIME OUT
BE Errors
Error
Number Error name
0101 S2B_ILL_CO
www
MMAND
0102 S2B_ILL_PAR
AM .
18
http://www.xiaoyu163.com
Component identification
000A
0016
001A
001C
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
communication problem
x ao
between UART and engine.
y
Command not allowed in this
state or unknown. Reason: see i
S2B_ILL_COMMAND error
http://www.xiaoyu163.com
8
Error
Number Error name
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
0109 S2B_SBC_NO
T_FOUND
010A S2B_TRAY
010B S2B_TOC_RE
AD
010C S2B_JUMP
010D S2B_NON_EX
IST_SES
010E S2B_NON_EX
IST_BCA
010F Speed setting A wrong or inappropraiate speed
0116 NO_DISC
011A TRAY_INIT
011B NO TOC INFO No TOC information in lead-in
Q Q
3 6 7 1 3
01F0 S2B_OVERR
UN
01F1 S2B_COMM_
TO
01F2 S2B_PARITY Byte received with parity error.
01F3 S2B_ILL_PHA
SE
01F4 S2B_ILL_NR_
OF_BYTES
SLPH Error Codes
Error
Number Error name
0000 COMMUNICA
TION
SSM Error Codes
Error
Code Error name
0006 SP_SYNCER
ROR
u163
.
0007 SP_EDCERR
OR
2 9 9 4 2 8
Explanation
home position.
Focus failure
within timeout
several retries.
PLL could not lock in Accessing
or Tracking state
Header timeout
Requested subcode item could
not be found.
Tray could not be opened or
closed completely.
TOC could not be read within
timeout period.
Requested seek could not be
performed.
Attempt to access a non-existing
session.
Caller tries to acces a non-
existing BCA area
value has been set
No disc selected
After reset, initialized tray
area or erase TOC found
1 5 0 5 8 2 9 9 4
Too many bytes received over
S2B Reason: see
S2B_ILL_COMMAND error
Not enough bytes are received
over S2B Reason: see
S2B_ILL_COMMAND error
Reason: see
S2B_ILL_COMMAND error
CMD IDC is not valid,
transmission out of sync.
Reason: see
S2B_ILL_COMMAND error
Byte count has an illegal value.
Reason: see
S2B_ILL_COMMAND error
Explanation
Error in I2C communication.
Reason: bad connection
between slave processor and
main processor.
Explanation
m
System cannot get synchronized
with sectors coming from disc.
co
Reason: Usually a damaged
disc or the player was dropped/
pushed during operation. If not,
the engine is malfunctioning.
Data coming from disc is
damaged. Reason: see
SP_SYNCERROR
9 9
2 8 9 9