Table of Contents
Advertisement
•
Via ComPair.
5.5.3
How to Clear the Error Buffer
Use one of the following methods:
•
By activation of the "RESET ERROR BUFFER" command
in the SAM menu.
•
If the content of the error buffer has not changed for 50+
hours, it resets automatically.
5.5.4
Error Buffer
In case of non-intermittent faults, clear the error buffer before
starting to repair (before clearing the buffer, write down the
content, as this history can give significant information). This to
ensure that old error codes are no longer present.
Table 5-2 Error code overview
Description
2
I
CM3 (SSB + SRF bus)
2
I
CM2 (BE bus)
2
I
CM1(FE bus)
Fusion doesn't boot (HW cause)
12V
Display supply (POK)
HDMI mux
I2C switch
Channel dec DVB-T2
Channel dec DVB-S2
Lnb controller
Hybrid Tuner
Main NVM
Tuner DVB-S2
Class-D
FPGAScanBacklight
T° sensor SSB/Display
Light sensor
µP touch control
RF4CE
MIPS doesn't boot (SW cause)
FPGA HDR
FPGA Lattice Backlight
TCON µP (SHARP)
TCON ASIC (SHARP)
VCON cal (SHARP)
Extra Info
•
Rebooting. When a TV is constantly rebooting due to
internal problems, most of the time no errors willbe logged
or blinked. This rebooting can be recognized via a ComPair
interface and Hyperterminal (for Hyperterminal settings,
see section
"5.8 Fault Finding and Repair
Logging). It's shown that the loggings which are generated
by the main software keep continuing.
2
•
C bus M3, SSB + SRF bus blocked). Current
Error 13 (I
situation: when this error occurs, the TV can reboot due to
the blocked bus. The best way for further diagnosis here, is
to check the logging output.
2
•
C bus M2, BE bus blocked). Current situation:
Error 14 (I
when this error occurs. The best way for further diagnosis
here, is to check the logging output.
2
•
C bus M1, FE bus blocked). Current situation:
Error 18 (I
when this error occurs. The best way for further diagnosis
here, is to check the logging output.
•
Error 15 (Fusion doesn't boot). Indicates that the main
processor was not able to read his bootscript. This error will
point to a hardware problem around the Fusion (supplies
not OK, Fusion device completely dead, link between Mips
and Stand-by Processor broken, etc...)
Other root causes for this error can be due to hardware
problems regarding the DDR's and the bootscript reading
from the Fusion device.
Service Modes, Error Codes, and Fault Finding
Monitored
Layer 1
Layer 2
by
2
13
MIPS
2
14
MIPS
2
18
MIPS
2
15
Stby µP
3
16
Stby µP
3
17
MIPS
2
23
MIPS
2
24
MIPS
2
27
MIPS
2
28
MIPS
2
31
MIPS
2
34
MIPS
2
35
MIPS
2
36
MIPS
2
37
MIPS
2
38
MIPS
2
42
MIPS
6
43
MIPS
6
44
MIPS
6
46
MIPS
2
53
Stby µP
5
61
MIPS
5
62
MIPS
7
54
MIPS
7
55
MIPS
7
56
MIPS
Tips,
5.8.6
If possible, check the entire contents of the error buffer. In
some situations, an error code is only the result o f another error
code and not the actual cause.(e.g. a fault in the protection
detection circuitry can also lead to a protection)
There are several mechanisms of error detection:
•
Via error bits in the status registers of ICs.
•
Via polling on I/O pins going to the standby processor.
•
Via sensing of analog values on the standby processor or
the Mips.
•
Via a "not acknowledge" of an I
Take notice that some errors need several minutes before they
start blinking or before they will be logged. So in case of
problems wait 2 minutes from start-up onwards, and then
check if the front LED is blinking or if an error is logged.
Error/
Error Buffer/
Prot
Blinking LED
Device
E
BL / EB
SSB
E
BL / EB
SSB
E
BL / EB
SSB
P
BL
Fusion
P
BL
/
E
EB
/
E
EB
SII9387
E
EB
PCA9540
E
EB
CXD2834
E
EB
STV0903
E
EB
LNBH25
E
EB
SUT-RE214Z
E
EB
STM24C64
E
EB
STV6110
E
EB
TAS 5731 PHP
E
EB
XC6SLX4
E
EB
LM 75
E
EB
TSL2571
E
EB
/
E
EB
/
P
BL
FUSION
E
BL
Xilinx Spartan
E
BL
Lattice
E
BL
/
E
BL
/
E
BL
/
•
Error 16 (12V). This voltage is made in the power supply
and results in protection (LAYER 1 error = 3) in case of
absence. When SDM (maintain grounding continuously) is
activated we see blinking LED LAYER 2 error = 16.
•
Error 17 (Display Supply). Here the status of the "Power
OK" is checked by software,no protection will occur during
failure of the display supply, only error logging. LED
blinking of LAYER 1 error = 3 in CSM, in SDM this gives
LAYER 2 error = 17.
•
Error 23 (HDMI mux). When there is no I
communication towards the HDMI mux after start-up,
LAYER 2 error = 23 will be logged and displayed via the
blinking LED procedure if SDM is switched on.
•
Error 24 (I2C switch). When there is no I
communication towards the I
error = 24 will be logged and displayed via the blinking LED
procedure when SDM is switched on.
•
Error 27 (Channel dec DVB-T2). When there is no I
communication towards the DVB-T channel decoder,
LAYER 2 error = 27 will be logged and displayed via the
blinking LED procedure if SDM is switched on.
•
Error 28 (Channel dec DVB-S2). When there is no I
communication towards the DVB-S channel decoder,
LAYER 2 error = 28 will be logged and displayed via the
blinking LED procedure if SDM is switched on.
back to
div. table
QFU2.1E LA
5.
2
C communication.
Defective Board
SSB
SSB
SSB
SSB
Supply
Supply
SSB
SSB
SSB
SSB
SSB
SSB
SSB
SSB
SSB
SSB
T° sensor on SSB/Display
Set
Set
Set
SSB
Display
Display
Display
Display
Display
2
C
2
C
2
C switch, LAYER 2
EN 35
2
C
2
C
2013-Apr-05
Advertisement
Table of Contents
