Philips DVD763SA/051 Explanation, Some Examples, Uart Error Codes, Be Errors, Slph Error Codes

Diagnostic Software, Trouble Shooting and Test Instructions DVD763SA 5. EN 29

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. 5-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. For further explanation of this error code, refer to chapter 5.8 (Nuclei Error Codes).

5.6.1Errorlog

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	Component identification
Serial controller (UART)	000A
Engine (BE)	0016
Slave Processor (SLPH)	001A
SACD Stream Manager	001C
(SSM)
SACD Media Access (SMA)	002E
Diagnostic software (DS)	Dxxx

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 further explanation of DS errors, see description of nucleui error codes in paragraph 5.8.

UART Error Codes

Error	Error
Number	name	Explanation
0000	BUF_OVE	To many characters were offered in
	RFLOW	too little time. Reason: system was
		too busy doing other jobs.
0001	COMMUNI	Usually a protocol error. Reason:
	CATION	bad connection between engine
		and processor.
0002	TIME OUT
BE Errors
Error
Number	Error name		Explanation
0101	S2B_ILL_CO		Parameter(s) not valid for this
	MMAND		command. Reason: some
			communication problem
			between UART and engine.
0102	S2B_ILL_PAR		Command not allowed in this
	AM		state or unknown. Reason: see
			S2B_ILL_COMMAND error

Error
Number	Error name	Explanation
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	PLL could not lock in Accessing
	CK	or Tracking state
0108	SBC_HEADE	Header timeout
	R_TO
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	Caller tries to acces a non-
	IST_BCA	existing BCA area
010F	Speed setting	A wrong or inappropraiate speed
		value has been set
0116	NO_DISC	No disc selected
011A	TRAY_INIT	After reset, initialized tray
011B	NO TOC INFO	No TOC information in lead-in
		area or erase TOC found
01F0	S2B_OVERR	Too many bytes received over
	UN	S2B Reason: see
		S2B_ILL_COMMAND error
01F1	S2B_COMM_	Not enough bytes are received
	TO	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	CMD IDC is not valid,
	SE	transmission out of sync.
		Reason: see
		S2B_ILL_COMMAND error
01F4	S2B_ILL_NR_	Byte count has an illegal value.
	OF_BYTES	Reason: see
		S2B_ILL_COMMAND error
SLPH Error Codes
Error
Number	Error name	Explanation
0000	COMMUNICA	Error in I2C communication.
	TION	Reason: bad connection
		between slave processor and
		main processor.
SSM Error Codes
Error
Code	Error name	Explanation
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
	OR	damaged. Reason: see
		SP_SYNCERROR