Copyright 2008 Koninklijke Philips Electronics N.V.
All rights reserved. No part of this publication may be reproduced, stored in a
retrieval system or transmitted, in any form or by any means, electronic,
mechanical, photocopying, or otherwise without the prior permission of Philips.
2 - EXT1, EXT2: Video YPbPr - In, CVBS - In/Out, Audio - In/
Out
1-Audio R 0.5 V
2-Audio R 0.5 V
3-Audio L 0.5 V
4-Ground Audio Gnd H
5-Ground Blue Gnd H
6-Audio L 0.5 V
7-Video Pb 0.7 V
8-Function Select 0 - 2 V: INT
9-Ground Gnd H
10 - n.c.
11 - Video Y 1 V
12 - n.c.
13 - Ground Gnd H
14 - Ground Gnd H
15 - Video Pr 0.7 V
20
21
Figure 1-2 SCART connector
E_06532_001.eps
/ 1 kohm k
RMS
/ 10 kohm j
RMS
/ 1 kohm k
RMS
/ 10 kohm j
RMS
/ 75 ohm j
PP
4.5 - 7 V: EXT 16:9
9.5 - 12 V: EXT 4:3 j
/ 75 ohm j
PP
/ 75 ohm j
PP
2
1
050404
Figure 1-1 Connection overview
16 - Status/FBL 0 - 0.4 V: INT
17 - Ground Video Gnd H
18 - Ground FBL Gnd H
19 - Video CVBS 1 V
20 - Video CVBS/Y 1 V
21 - Shield Gnd H
Technical Specifications, Connections, and Chassis Overview
I_18020_088.eps
110908
A
MAIN SUPPLY PANEL
G
I/O PANEL
LD
LV DS2DP
BOARD
1.3Chassis Overview
KEYBOARD CONTROL
E
PA NE L
EN 5Q529.1E LC1.
Figure 1-7 PWB/CBA locations Hub -1-
SMALL SIGNAL
BOARD
I_18020_087.eps
B
110908
Figure 1-8 PWB/CBA locations Hub -2-
Page 6
EN 6Q529.1E LC1.
I_18020_089.eps
110908
J
IR & LED PANEL
M
MONITOR BOARD
Technical Specifications, Connections, and Chassis Overview
Figure 1-9 PWB/CBA locations Monitor
Page 7
Safety Instructions, Warnings, and Notes
2.S afety Instructions, Warnings, and Notes
EN 7Q529.1E LC2.
Index of this chapter:
2.1 Safety Instructions
2.2 Warnings
2.3 Notes
2.1Safety Instructions
Safety regulations require the following during a repair:
•Connect the set to the Mains/AC Power via an isolation
transformer (> 800 VA).
•Replace safety components, indicated by the symbol h,
only by components identical to the original ones. Any
other component substitution (other than original type) may
increase risk of fire or electrical shock hazard.
Safety regulations require that after a repair, the set must be
returned in its original condition. Pay in particular attention to
the following points:
•Route the wire trees correctly and fix them with the
mounted cable clamps.
•Check the insulation of the Mains/AC Power lead for
external damage.
•Check the strain relief of the Mains/AC Power cord for
proper function.
•Check the electrical DC resistance between the Mains/AC
Power plug and the secondary side (only for sets that have
a Mains/AC Power isolated power supply):
1. Unplug the Mains/AC Power cord and connect a wire
between the two pins of the Mains/AC Power plug.
2. Set the Mains/AC Power switch to the “on” position
(keep the Mains/AC Power cord unplugged!).
3. Measure the resistance value between the pins of the
Mains/AC Power plug and the metal shielding of the
tuner or the aerial connection on the set. The reading
should be between 4.5 MΩ and 12 MΩ.
4. Switch “off” the set, and remove the wire between the
two pins of the Mains/AC Power plug.
•Check the cabinet for defects, to prevent touching of any
inner parts by the customer.
2.2Warnings
•All ICs and many other semiconductors are susceptible to
electrostatic discharges (ESD w). Careless handling
during repair can reduce life drastically. Make sure that,
during repair, you are connected with the same potential as
the mass of the set by a wristband with resistance. Keep
components and tools also at this same potential.
•Be careful during measurements in the high voltage
section.
•Never replace modules or other components while the unit
is switched “on”.
•When you align the set, use plastic rather than metal tools.
This will prevent any short circuits and the danger of a
circuit becoming unstable.
2.3Notes
2.3.1General
•Measure the voltages and waveforms with regard to the
chassis (= tuner) ground (H), or hot ground (I), depending
on the tested area of circuitry. The voltages and waveforms
shown in the diagrams are indicative. Measure them in the
Service Default Mode (see chapter 5) with a colour bar
signal and stereo sound (L: 3 kHz, R: 1 kHz unless stated
otherwise) and picture carrier at 475.25 MHz for PAL, or
61.25 MHz for NTSC (channel 3).
•Where necessary, measure the waveforms and voltages
with (D) and without (E) aerial signal. Measure the
voltages in the power supply section both in normal
operation (G) and in stand-by (F). These values are
indicated by means of the appropriate symbols.
•Manufactured under license from Dolby Laboratories.
“Dolby”, “Pro Logic” and the “double-D symbol”, are
trademarks of Dolby Laboratories.
2.3.2Schematic Notes
•All resistor values are in ohms, and the value multiplier is
often used to indicate the decimal point location (e.g. 2K2
indicates 2.2 kΩ).
•Resistor values with no multiplier may be indicated with
either an “E” or an “R” (e.g. 220E or 220R indicates 220 Ω).
•All capacitor values are given in micro-farads (μ=× 10
nano-farads (n =× 10
•Capacitor values may also use the value multiplier as the
decimal point indication (e.g. 2p2 indicates 2.2 pF).
•An “asterisk” (*) indicates component usage varies. Refer
to the diversity tables for the correct values.
•The correct component values are listed in the Spare Parts
List. Therefore, always check this list when there is any
doubt.
2.3.3BGA (Ball Grid Array) ICs
Introduction
For more information on how to handle BGA devices, visit this
URL: www.atyourservice.ce.philips.com (needs subscription,
not available for all regions). After login, select “Magazine”,
then go to “Repair downloads”. Here you will find Information
on how to deal with BGA-ICs.
BGA Temperature Profiles
For BGA-ICs, you must use the correct temperature-profile,
which is coupled to the 12NC. For an overview of these profiles,
visit the website www.atyourservice.ce.philips.com (needs
subscription, but is not available for all regions)
You will find this and more technical information within the
“Magazine”, chapter “Repair downloads”.
For additional questions please contact your local repair help
desk.
2.3.4Lead-free Soldering
Due to lead-free technology some rules have to be respected
by the workshop during a repair:
•Use only lead-free soldering tin Philips SAC305 with order
code 0622 149 00106. If lead-free solder paste is required,
please contact the manufacturer of your soldering
equipment. In general, use of solder paste within
workshops should be avoided because paste is not easy to
store and to handle.
•Use only adequate solder tools applicable for lead-free
soldering tin. The solder tool must be able:
– To reach a solder-tip temperature of at least 400°C.
– To stabilize the adjusted temperature at the solder-tip.
– To exchange solder-tips for different applications.
•Adjust your solder tool so that a temperature of around
360°C - 380°C is reached and stabilized at the solder joint.
Heating time of the solder-joint should not exceed ~ 4 sec.
Avoid temperatures above 400°C, otherwise wear-out of
tips will increase drastically and flux-fluid will be destroyed.
To avoid wear-out of tips, switch “off” unused equipment or
reduce heat.
•Mix of lead-free soldering tin/parts with leaded soldering
tin/parts is possible but PHILIPS recommends strongly to
-9
), or pico-farads (p =× 10
-12
-6
),
).
Page 8
EN 8Q529.1E LC3.
E_06532_024.eps
260308
MODEL :
PROD.NO:
~
S
32PF9968/10
MADE IN BELGIUM
220-240V 50/60Hz
128W
AG 1A0617 000001
VHF+S+H+UHF
BJ3.0E LA
Directions for Use
avoid mixed regimes. If this cannot be avoided, carefully
clear the solder-joint from old tin and re-solder with new tin.
2.3.5Alternative BOM identification
It should be noted that on the European Service website,
“Alternative BOM” is referred to as “Design variant”.
The third digit in the serial number (example:
AG2B0335000001) indicates the number of the alternative
B.O.M. (Bill Of Materials) that has been used for producing the
specific TV set. In general, it is possible that the same TV
model on the market is produced with e.g. two different types
of displays, coming from two different suppliers. This will then
result in sets which have the same CTN (Commercial Type
Number; e.g. 28PW9515/12) but which have a different B.O.M.
number.
By looking at the third digit of the serial number, one can
identify which B.O.M. is used for the TV set he is working with.
If the third digit of the serial number contains the number “1”
(example: AG1B033500001), then the TV set has been
manufactured according to B.O.M. number 1. If the third digit is
a “2” (example: AG2B0335000001), then the set has been
produced according to B.O.M. no. 2. This is important for
ordering the correct spare parts!
For the third digit, the numbers 1...9 and the characters A...Z
can be used, so in total: 9 plus 26= 35 different B.O.M.s can be
indicated by the third digit of the serial number.
Identification: The bottom line of a type plate gives a 14-digit
serial number. Digits 1 and 2 refer to the production center (e.g.
AG is Bruges), digit 3 refers to the B.O.M. code, digit 4 refers
to the Service version change code, digits 5 and 6 refer to the
production year, and digits 7 and 8 refer to production week (in
example below it is 2006 week 17). The 6 last digits contain the
serial number.
Figure 2-1 Serial number (example)
2.3.6Board Level Repair (BLR) or Component Level Repair
(CLR)
If a board is defective, consult your repair procedure to decide
if the board has to be exchanged or if it should be repaired on
component level.
If your repair procedure says the board should be exchanged
completely, do not solder on the defective board. Otherwise, it
cannot be returned to the O.E.M. supplier for back charging!
2.3.7Practical Service Precautions
•It makes sense to avoid exposure to electrical shock.
While some sources are expected to have a possible
dangerous impact, others of quite high potential are of
limited current and are sometimes held in less regard.
•Always respect voltages. While some may not be
dangerous in themselves, they can cause unexpected
reactions that are best avoided. Before reaching into a
powered TV set, it is best to test the high voltage insulation.
It is easy to do, and is a good service precaution.
3.Directions for Use
Directions for use can be downloaded from the following
websites:
For easy servicing of the monitor of the set, there are a few
possibilities created:
•The buffers from the packaging.
•Foam bars (created for Service).
4.2.1Foam Bars
Figure 4-3 Cable dressing monitor
4.3Assy/Panel Removal Hub
4.3.1Bottom Cover and -Shield
Warning: Disconnect the mains power cord before removing
the rear cover.
Refer to next figures for details.
1. Place the hub upside-down and remove the bottom cover
by removing the screws [1].
2. Remove the bottom shield by removing the screws [2]
indicated with an arrow.
Figure 4-4 Foam bars
The foam bars (order code 3122 785 90580 for two pieces) can
be used for all types and sizes of Flat TVs. See figure “Foam
bars” for details. Sets with a display of 42" and larger, require
four foam bars [1]. Ensure that the foam bars are always
supporting the cabinet and never only the display.
Caution: Failure to follow these guidelines can seriously
damage the display!
By laying the TV face down on the (ESD protective) foam bars,
a stable situation is created to perform measurements and
alignments. By placing a mirror under the TV, the screen can
be monitored.
Figure 4-5 Bottom Cover and -Shield -1-
Page 12
EN 12Q529.1E LC4.
I_18020_093.eps
081008
2
2
2
2
2
2
2
2 22
2
I_18020_094.eps
190908
22
1
I_18020_095.eps
190908
1
I_18020_096.eps
110908
2
3
(2x)
1
Mechanical Instructions
Figure 4-6 Bottom Cover and -Shield -2-
4.3.2Key Board
Refer to next figure for details.
1. Unplug the key board connector [1] from the IR & LED
board.
2. Remove the screws [2].
3. Lift the unit and take it out of the set.
When defective, replace the whole unit.
Figure 4-7 Keyboard Control Panel
4.3.3Fan
Figure 4-8 Fan
4.3.4Small Signal Board (SSB)
Refer to next figures or details.
1. Remove fan.
2. Unplug keyboard cable [1] on SSB.
3. Unplug flat cable [2] on SSB.
4. Unplug two LVDS connectors [3] on SSB. These are very
fragile connectors!
5. Lift the flatcable gently with a screwdriver [4] that leads to
the underlaying I/O Panel.
6. Remove three screws near side I/O Panel.
7. Remove four screws near back I/O Panel (including the two
screws of the VGA connector).
8. Remove all remaining screws that secure the SSB.
9. Slide the SSB sidewards out of the hub.
Refer to next figure for details.
1. Unplug connector [1].
2. Lift the fan from the set. During replacement, ensure you
replace it at its original position.
When defective, replace the unit.
Figure 4-9 Small Signal Board -1-
Page 13
Figure 4-10 Small Signal Board -2-
I_18020_097.eps
110908
4
I_18020_119.eps
151008
11223
4
I_18020_144.eps
151008
5
5
5
5
5
5
5
I_18020_098.eps
151008
1
1
4.3.5Subframe underneath SSB
Refer to next figures for details.
1. Remove keyboard, fan and SSB.
2. Remove two screws [1] on Additional I/O Panel (near cinch
plugs).
3. Remove two screw [2] on Additional I/O Panel (near
SCART plug).
4. Remove screw [3].
5. Unclamp flat cable coming from Power Supply Unit [4].
6. Take the board out.
7. Remove screws on the subframe indicated with an arrow
[5].
8. Lift the subframe on the right side, then lift the subframe
forwards, then take the subframe out of the hub.
Mechanical Instructions
4.3.6Additional I/O Panel
Refer to section “Subframe underneath SSB”.
When defective, replace the whole unit.
4.3.7Display Port Panel Hub
EN 13Q529.1E LC4.
Figure 4-12 Subframe -2-
Refer to next figure for details.
1. Remove screws [1].
2. Unplug the other connectors.
3. Remove all fixation screws.
4. Take the board out.
Figure 4-11 Subframe -1-
Figure 4-13 Display Port Panel Hub
Page 14
EN 14Q529.1E LC4.
I_18020_100.eps
110908
1
11
1
1
1
I_18020_101.eps
110908
11
I_18020_102.eps
110908
1
2
1
1
111
1
1
1
1
I_18020_103.eps
110908
44
3
I_18020_104.eps
110908
22
555
1
(2x)
1
(2x)
334
4.3.8Power Supply Unit
Refer to next figure for details.
1. Remove the fixation screws [1].
2. Lift the board.
3. Unplug the connector to the mains inlet.
4. Unplug the connector from the supply connector to the
screen.
5. Take the supply out.
When defective, replace the whole unit.
Mechanical Instructions
Figure 4-16 IR & LED Panel -1-
Figure 4-14 Power Supply Unit
4.4Assy/Panel Removal Monitor
4.4.1Sound Interface
Refer to next figure for details.
1. Remove stand (four screws).
2. Lift set from stand.
3. Remove soundbar.
4. Remove sound interface by removing the screws [1].
When defective, replace the whole module.
Figure 4-17 IR & LED Panel -2-
4.4.3Display Port Panel
Refer to next figure for details.
1. Unplug connectors [1].
2. Unplug LVDS connectors [2]. Be careful, as these are very
fragile connectors.
3. Remove screws [3] and subframe [4].
4. Remove screws [5].
When defective, replace the whole unit.
4.4.2IR & LED Board
Refer to next figures for details.
1. Remove lower part of VESA stand [1].
2. Remove flare [2] (six screws).
3. Unplug connector [3].
4. Remove screws [4].
When defective, replace the whole unit.
Figure 4-15 Sound Interface
Figure 4-18 Display Port Panel Monitor
Page 15
Mechanical Instructions
Stand
Back Cover
Soundbar
Stand
Bracket
Flare
Sound Interface
Leading Edge
I_18020_105.eps
151008
EN 15Q529.1E LC4.
4.4.4LCD Panel
SPECIAL NOTICE
The dis-assembly, re-assembly and/or exchange of the
LCD Panel is an elaborate process. Reason for this is the
mounting method of the Panel in the cabinet. Due to physical
restraints, no screws could be used, but instead adhesive
foams and -tapes are used.
Use gloves where indicated to avoid personal injury and
pollution of the LCD Panel (dust and/or fingerprints).
Exactly follow the instructions to avoid warranty issues,
especially when a defective LCD Panel has to be returned to
the supplier.
Step A. to F. describe the removal of the LCD Panel of the
cabinet.
Step K. to N. describe the mounting of the LCD Panel back into
the cabinet.
Step G. to J. describe which additional actions have to be taken
in the event the original LCD Panel has to be replaced.
Additional Spare Parts are needed when remounting the (new)
LCD Panel in the cabinet. These spare parts can be ordered as
one Service Kit using ordering code 3122 785 91150. The kit
contains the following items:
•5 x Foam L × W × T = 20 × 43 × 0.5 mm.
•6 x Foam L × W × T = 70 × 50 × 0.5 mm.
•4 x Foam L × W × T = 30 × 43 × 0.5 mm.
•1 x Foam L × W × T = 55 × 20 × 0.8 mm.
•5 x Cable clamp (wire saddle) 11.2 mm.
LCD Panel Removal
A. Refer to next figure for details.
1. Remove stand.
2. Remove soundbar.
3. Remove backcover.
4. Remove sound interface.
5. Remove flare.
6. Remove stand bracket.
7. Remove leading edge.
Figure 4-19 LCD Panel -1-
Page 16
EN 16Q529.1E LC4.
I_18020_106.eps
110908
1
3
2
I_18020_107.eps
180908
B. Bend metal lips in each corner of Front open.
Mechanical Instructions
Figure 4-20 LCD Panel -2-
C. Remove thermal foams (3x) between LCD-panel and upper
wall of metal Front.
1. Pull the upper bend open.
2. Move out the thermal foam with e.g. a screwdriver.
3. Pull out the thermal foam.
Figure 4-21 LCD Panel -3-
Page 17
Mechanical Instructions
1
3
2
I_18020_108.eps
110908
1
3
2
I_18020_109.eps
180908
D. Release two side walls of metal Front (use gloves).
1. Place thumb against each upper corner of the metal Front.
2. Place fingers against LCD Panel.
3. Push out LCD Panel in each corner until tape in middle of
side wall releases.
EN 17Q529.1E LC4.
Figure 4-22 LCD Panel -4-
E. Release bottom wall of metal Front (use gloves).
1. Place hands in top/middle of metal Front and LCD Panel.
2. Pull metal Front and LCD Panel further apart until 2 tapes
in bottom wall release.
3. Take out LCD Panel.
Figure 4-23 LCD Panel -5-
Page 18
EN 18Q529.1E LC4.
1
3
2
I_18020_110.eps
110908
F. Removing tapes/foams from LCD Panel (use “Label Off 50”;
“Intronics L50/200”).
1. Remove remains of thermal foam on top of LCD Panel.
2. Remove remains of double-sided tapes (4x) on front of
LCD Panel.
3. Remove protective foam on bottom of LCD Panel.
Mechanical Instructions
For re-assembly instructions, proceed with step K.
Figure 4-24 LCD Panel -6-
Page 19
Mechanical Instructions
Vesa Brackets
Connector
Plate
PCB
Isolator
Plates
I_18020_111.eps
151008
1
3
2
I_18020_112.eps
120908
LCD Panel Replacement
Instructions G to J apply if you have to replace the LCD
Panel.
G. Remove VESA brackets, PCB connector plate, wiring, and
isolator plates.
EN 19Q529.1E LC4.
Figure 4-25 LCD Panel -7-
H. Remove all remaining tapes/foams/cable clamps.
1. Remove remaining tapes for wiring.
2. Remove cable clamps (five times).
3. Remove all backlight blocking foams.
4. Remove all glue remains with “Label Off 50”.
Figure 4-26 LCD Panel -8-
Page 20
EN 20Q529.1E LC4.
12
Isolator
Plates
3
10±510±5
3
10±5
AB
C
A
B
C
B
A
B
BBBC
C
B
A
A
B
C
C
A
I_18020_113.eps
171008
1
3
2
Vesa Brackets
Connector
Plate
PCB
I_18020_114.eps
180908
I. Prepare new LCD Panel.
1. Take new LCD Panel and place two isolator plates.
2. Glue new foams on LCD Panel with the following
specifications:
- four times foam L × W × T = 20 × 43 × 0.5 mm [A].
- six times foam L × W × T = 70 × 50 × 0.5 mm [B].
- four times foam L × W × T = 30 × 43 × 0.5 mm [C].
3. Figure [3] show the upper- and lower foams.
Mechanical Instructions
Figure 4-27 LCD Panel -9-
J. Assemble VESA brackets, PCB, connector plate, and wiring.
1. Assemble VESA brackets, PCB and connector plate.
2. Assemble cable clamps:
- five times cable clamp 11.2 mm.
3. Assemble wiring.
Figure 4-28 LCD Panel -10-
Page 21
Mechanical Instructions
1
3
2
1
2
3
2
I_18020_115.eps
171008
1
3
2
A
B
I_18020_116.eps
180908
K. Assemble metal Front and LCD Panel (use gloves).
1. Take a new metal Front and remove liners of double-sided
tapes (four times).
2. Insert LCD Panel as shown in picture: first top side, then
cantilever down.
3. Bend down metal lips in each corner (4 times).
EN 21Q529.1E LC4.
Figure 4-29 LCD Panel -11-
L. Assemble Leading Edge.
1. Assemble Leading Edge on Front.
2. Glue protective foam across edge of metal Front and LCD
Panel with the following specifications:
1 time foam L × W × T = 55 × 20 × 0.8 mm [A].
3. Glue light-blocking foam upon LED-PCB with the following
specifications:
1 time foam L × W × T = 20 × 43 × 0.5 mm [B].
Figure 4-30 LCD Panel -12-
Page 22
EN 22Q529.1E LC4.
Stand
Back Cover
Soundbar
Stand
Bracket
Sound Interface
I_18020_118.eps
180908
M. Assemble Flare.
1. Place flare upon LCD Panel as shown in picture: first on top
side.
2. Cantilever flare down while pulling it slightly open (to avoid
scratches from metal Front).
3. Fix flare on Panel (six screws).
Mechanical Instructions
1
1
1
3
3
Figure 4-31 LCD Panel -13-
N. Assemble Stand Bracket, Sound Interface, Back Cover,
Soundbar and Stand.
1. Remove protective foils on both sides of Flare.
2
I_18020_117.eps
171008
Figure 4-32 LCD Panel -14-
Page 23
4.5Set Re-assembly
To re-assemble the whole set, execute all processes in reverse
order, except for the Monitor. To re-assembly the Monitor,
follow the instructions in the applicable section of this Manual.
Notes:
•While re-assembling, make sure that all cables are placed
and connected in their original position. See figure “Cable
dressing”.
•Pay special attention not to damage the EMC foams on the
SSB shields. Ensure that EMC foams are mounted
correctly.
Mechanical Instructions
EN 23Q529.1E LC4.
Page 24
EN 24Q529.1E LC5.
I_18020_146.eps
190908
1
SDM1SDM
1
SDM2SPI-P
Service Modes, Error Codes, and Fault Finding
5.S ervice Modes, Error Codes, and Fault Finding
Index of this chapter:
5.1 Test Points
5.2 Service Modes
5.3 Stepwise Start-up
5.4 Service Tools
5.5 Error Codes
5.6 The Blinking LED Procedure
5.7 Protections
5.8 Fault Finding and Repair Tips
5.9 Software Upgrading
5.1Test Points
As most signals are digital, it will be difficult to measure
waveforms with a standard oscilloscope. However, several key
ICs are capable of generating test patterns, which can be
controlled via ComPair. In this way it is possible to determine
which part is defective.
Perform measurements under the following conditions:
•Service Default Mode.
•Video: Colour bar signal.
•Audio: 3 kHz left, 1 kHz right.
5.2Service Modes
Service Default mode (SDM) and Service Alignment Mode
(SAM) offers several features for the service technician, while
the Customer Service Mode (CSM) is used for communication
between the call centre and the customer.
This chassis also offers the option of using ComPair, a
hardware interface between a computer and the TV chassis. It
offers the abilities of structured troubleshooting, error code
reading, and software version read-out for all chassis.
(see also section “5.4.1 ComPair”).
– Skip/blank of non-favourite pre-sets.
How to Activate SDM
For this chassis there are two kinds of SDM: an analog SDM
and a digital SDM. Tuning will happen according table “SDM
Default Settings”.
•AnalogSDM: use the standard RC-transmitter and key in
the code “062596”, directly followed by the “MENU” button.
Note: It is possible that, together with the SDM, the main
menu will appear. To switch it “off”, push the “MENU”
button again.
•DigitalSDM: use the standard RC-transmitter and key in
the code “062593”, directly followed by the “MENU” button.
Note: It is possible that, together with the SDM, the main
menu will appear. To switch it “off”, push the “MENU”
button again.
•AnalogSDM can also be activated by connecting for a
moment the solder pad (see figure “Service mode pads”)
on the SSB with the indication “SDM” [1], to GND.
5.2.1Service Default Mode (SDM)
Purpose
•To create a pre-defined setting, to get the same
measurement results as given in this manual.
•To override SW protections detected by stand-by
processor and make the TV start up to the step just before
protection (a sort of automatic stepwise start up). See
section “5.3 Stepwise Start-up”.
•To start the blinking LED procedure where only layer 2
errors are displayed. (see also section “5.5 Error Codes”)
Specifications
Table 5-1 SDM default settings
RegionFreq. (MHz)
Europe, AP(PAL/Multi)475.25PAL B/G
Europe, AP DVB-T546.00 PID
•All picture settings at 50% (brightness, colour, contrast).
•All sound settings at 50%, except volume at 25%.
•All service-unfriendly modes (if present) are disabled, like:
– (Sleep) timer.
– Child/parental lock.
– Picture mute (blue mute or black mute).
– Automatic volume levelling (AVL).
Video: 0B 06 PID
PCR: 0B 06 PID
Audio: 0B 07
Default
system
DVB-T
Figure 5-1 Service mode pads
After activating this mode, “SDM” will appear in the upper right
corner of the screen (when a picture is available).
How to Navigate
When the “MENU” button is pressed on the RC transmitter, the
set will toggle between the SDM and the normal user menu
(with the SDM mode still active in the background).
How to Exit SDM
Use one of the following methods:
•Switch the set to STAND-BY via the RC-transmitter.
•Via a standard customer RC-transmitter: key in “00”sequence.
5.2.2Service Alignment Mode (SAM)
Purpose
•To perform (software) alignments.
•To change option settings.
•To easily identify the used software version.
•To view operation hours.
•To display (or clear) the error code buffer.
How to Activate SAM
Via a standard RC transmitter: key in the code “062596”
directly followed by the “INFO” button. After activating SAM
Page 25
PHILIPS
MODEL:
32PF9968/10
PROD.SERIAL NO:
AG 1A0620 000001
040
39mm
27mm
(CTN Sticker)
Display Option
Code
E_06532_038.eps
240108
Service Modes, Error Codes, and Fault Finding
EN 25Q529.1E LC5.
with this method a service warning will appear on the screen,
continue by pressing the red button on the RC.
Contents of SAM:
•Hardware Info.
– A. SW Version. Displays the software version of the
main software (example: Q591E-1.2.3.4 =
AAAAB_X.Y.W.Z).
•AAAA= the chassis name.
•B= the region: A= AP, E= EU, L= Latam, U = US.
For AP sets it is possible that the Europe software
version is used.
•X.Y.W.Z= the software version, where X is the
main version number (different numbers are not
compatible with one another) and Y.W.Z is the sub
version number (a higher number is always
compatible with a lower number).
– B. SBY PROC Version. Displays the software version
of the stand-by processor.
– C. Production Code. Displays the production code of
the TV, this is the serial number as printed on the back
of the TV set. Note that if an NVM is replaced or is
initialized after corruption, this production code has to
be re-written to NVM. ComPair will foresee in a
possibility to do this.
•Operation Hours. Displays the accumulated total of
operation hours (not the stand-by hours). Every time the
TV is switched “on/off”, 0.5 hours is added to this number.
•Errors (followed by maximum 10 errors). The most recent
error is displayed at the upper left (for an error explanation
see section “5.5 Error Codes”).
•Reset Error Buffer. When “cursor right” (or the “OK
button) is pressed followed by another “OK” button touch,
the error buffer is reset.
•Alignments. This will activate the “ALIGNMENTS” submenu.
•Dealer Options. Extra features for the dealers.
•Options. Extra features for Service. For more info
regarding option codes, see chapter 8 “Alignments”.
Note that if the option code numbers are changed, these
have to be confirmed with pressing the “OK” button before
the options are stored. Otherwise changes will be lost.
•Initialize NVM. The moment the processor recognizes a
corrupted NVM, the “initialize NVM” line will be highlighted.
Now, two things can be done (dependent of the service
instructions at that moment):
– Save the content of the NVM via ComPair for
development analysis, before initializing. This will give
the Service department an extra possibility for
diagnosis (e.g. when Development asks for this).
– Initialize the NVM.
Note: When the NVM is corrupted, or replaced, there is a high
possibility that no picture appears because the display code is
not correct. So, before initializing the NVM via the SAM, a
picture is necessary and therefore the correct display option
has to be entered. Refer to chapter 8 “Alignments” for details.
To adapt this option, it’s advised to use ComPair (the correct
HEX values for the options can be found in chapter 8
“Alignments”) or a method via a standard RC (described
below).
Changing the display option via a standard RC
: Key in the
code “062598” directly followed by the “MENU” button and
“XXX” (where XXX is the 3 digit decimal display code as
mentioned in table “Option code overview” in chapter 8
“Alignments”. Remark : there is only one display option code
here “168” used for this chassis). If the above action is
successful, the front LED will go out as an indication that the
RC sequence was correct. After the display option is changed
in the NVM, the TV will go to the Stand-by mode. If the NVM
Figure 5-2 Location of Display Option Code sticker
•Store - go right. All options and alignments are stored
when pressing “cursor right” (or the “OK” button) and then
the “OK”-button.
•SW Maintenance.
– SW Events. Not useful for Service purposes. In case
of specific software problems, the development
department can ask for this info.
– HW Events. Not useful for Service purposes. In case
of specific software problems, the development
department can ask for this info.
•Test settings. For development purposes only.
•Upload to USB. To upload several settings from the TV to
an USB stick, which is connected to the SSB. The items are
“Channel list”, “Personal settings”, “Option codes”,
“Display-related alignments” and “History list”. First a
directory “repair\” has to be created in the root of the USB
stick. To upload the settings select each item separately,
press “cursor right” (or the “OK” button), confirm with “OK”
and wait until “Done” appears. In case the download to the
USB stick was not successful “Failure” will appear. In this
case, check if the USB stick is connected properly and if
the directory “repair” is present in the root of the USB stick.
Now the settings are stored onto the USB stick and can be
used to download onto another TV or other SSB.
Uploading is of course only possible if the software is
running and if a picture is available. This method is created
to be able to save the customer’s TV settings and to store
them into another SSB.
•Download to USB. To download several settings from the
USB stick to the TV. Same way of working as with
uploading. To make sure that the download of the channel
list from USB to the TV is executed properly, it is necessary
to restart the TV and tune to a valid preset if necessary.
Note: The “History list item” can not be downloaded from
USB to the TV. This is a “read-only” item. In case of
specific problems, the development department can ask
for this info.
•Development file versions. Not useful for Service
purposes, this information is only used by the development
department.
How to Navigate
•In SAM, the menu items can be selected with the
“CURSOR UP/DOWN” key (or the scroll wheel) on the RCtransmitter. The selected item will be highlighted. When not
all menu items fit on the screen, move the “CURSOR UP/
DOWN” key to display the next/previous menu items.
•With the “CURSOR LEFT/RIGHT” keys (or the scroll
wheel), it is possible to:
– (De) activate the selected menu item.
– (De) activate the selected sub menu.
•With the “OK” key, it is possible to activate the selected
action.
was corrupted or empty before this action, it will be initialized
first (loaded with default values). This initializing can take up to
20 seconds.
How to Exit SAM
Use one of the following methods:
•Press the “MENU” button on the RC-transmitter.
Page 26
EN 26Q529.1E LC5.
Service Modes, Error Codes, and Fault Finding
•Switch the set to STAND-BY via the RC-transmitter.
5.2.3Customer Service Mode (CSM)
Purpose
When a customer is having problems with his TV-set, he can
call his dealer or the Customer Helpdesk. The service
technician can then ask the customer to activate the CSM, in
order to identify the status of the set. Now, the service
technician can judge the severity of the complaint. In many
cases, he can advise the customer how to solve the problem,
or he can decide if it is necessary to visit the customer.
The CSM is a read only mode; therefore, modifications in this
mode are not possible.
When in this chassis CSM is activated, a test pattern will be
displayed during 5 seconds (1 second Blue, 1 second Green
and 1 second Red, then again 1 second Blue and 1 second
Green). This test pattern is generated by the PNX5100. So if
this test pattern is shown, it could be determined that the back
end video chain (PNX5100, LVDS, and display) of the SSB is
working.
New in this chassis are two test patterns with fixed colours:
•When the Green key is pushed while in CSM (toggle function) : a fixed testpattern by the “FPGA transmitter”
device located on the LVDS panel will be generated. The
selftest of this device is confirmed positive with a fully
Green picture displayed on the screen.
•When the Yellow key is pushed while in CSM (toggle function) : a fixed testpattern by the “FPGA receiver”
device located on the monitor will be generated. The
selftest of this device is confirmed positive with a fully
Yellow picture displayed on the screen.
When CSM is activated and there is a USB stick connected to
the TV, the software will dump the complete CSM content to the
USB stick. The file (CSM.txt) will be saved in the root of the
USB stick. This info can be handy if no information is displayed.
Also when CSM is activated, the layer 1 error is displayed via
blinking LED on the HUB. Only the latest error is displayed.
(see also section “5.5 Error Codes”).
How to Activate CSM
Key in the code “123654” via the standard RC transmitter.
Note: Activation of the CSM is only possible if there is no (user)
menu on the screen!
How to Navigate
By means of the “CURSOR-DOWN/UP” knob (or the scroll
wheel) on the RC-transmitter, can be navigated through the
menus.
Contents of CSM
The contents are reduced to 4 pages: General, Software
versions/General, Quality items and Addtitional Info. The group
names itself are not shown anywhere in the CSM menu.
General
•Set Type. This information is very helpful for a helpdesk/
workshop as reference for further diagnosis. In this way, it
is not necessary for the customer to look at the rear of the
TV-set. Note that if an NVM is replaced or is initialized after
corruption, this set type has to be re-written to NVM.
ComPair will foresee in a possibility to do this.
•Production Code. Displays the production code (the serial
number) of the TV. Note that if an NVM is replaced or is
initialized after corruption, this production code has to be
re-written to NVM. ComPair will foresee a in possibility to
do this.
•Installed date. Indicates the date of the first installation of
the TV. This date is acquired via time extraction.
•Options 1. Gives the option codes of option group 1 as set
in SAM (Service Alignment Mode).
•Options 2. Gives the option codes of option group 2 as set
in SAM (Service Alignment Mode).
•12NC SSB. Gives an identification of the SSB as stored in
NVM. Note that if an NVM is replaced or is initialized after
corruption, this identification number has to be re-written to
NVM. ComPair will foresee in a possibility to do this. This
identification number is the 12nc number of the SSB.
Remark: the content here can also be a part of the 12NC
SSB in combination with the serial number.
•12NC display. Shows the 12NC of the display
•12NC supply. Shows the 12NC of the supply.
•12NC “bolt-on”. Shows the 12NC of the “BOLT-ON”module.
•12NC LED dimming panel. Shows the 12NC of the LED
dimming panel.
Software versions/General
•Current main SW. Displays the built-in main software
version. In case of field problems related to software,
software can be upgraded. As this software is consumer
upgradeable, it will also be published on the Internet.
Example: Q591E_1.2.3.4
•Standby SW. Displays the built-in stand-by processor
software version. Upgrading this software will be possible
via ComPair or via USB (see chapter Software upgrade).
Example: STDBY_3.0.1.2.
•MPEG4 software. Displays the MPEG4 software (optional
for sets with MPEG4).
•PNX5100 boot NVM. Displays the SW-version that is used
in the PNX5100 boot NVM.
•LED dimming SW. Displays the SW-version for the LED
dimming panel.
•MPEG4 (blue to toggle). Displays the activation of
MPEG4 reception functionality (on/off).
Quality items
•Signal quality. Bad / average /good
•Child lock. Not active / active. This is a combined item for
locks. If any lock (Preset lock, child lock, lock after or
parental lock) is active, the item shall show “active”.
•Table channel changed. This item is for development
purpose.
•Key missing. This is a combined item for keys. The keys
have a separate bit and the sum is displayed in decimal
value.
– HDMI key valid = 001
– MAC key valid = 010
Important remark here : due to a software bug, the
MAC key is missing and not valid when “2” is displayed
in CSM.So, if for instance the HDMI and MAC keys are
both valid, the decimal value in CSM “1” is displayed
and not “3”.
– BDS key valid = 100
If 3 keys are valid the value: “5” is displayed (should be
“7” but due to the software bug it is not).
For value:
“0” in CSM: MAC stored, HDCP invalid.
“1” in CSM: MAC stored, HDCP valid.
“2” in CSM: no MAC, HDCP invalid.
“3” in CSM: no MAC, HDCP valid.
•CI slot present. If the common interface module is
detected the result will be “YES”, else “NO”.
•HDMI input format. The detected input format of the
HDMI.
•HDMI audio input stream. The HDMI audio input stream
is displayed: present / not present.
•HDMI video input stream. The HDMI video input stream
is displayed: present / not present.
Page 27
Service Modes, Error Codes, and Fault Finding
Active
Semi
St by
St by
Mains
on
Mains
off
GoToProtection
-WakeUp requested
-Acquisition needed
-No data Acquisition
required
-tact SW pushed
-last status is hibernateafter mains ON
- St by requested
-tact SW pushed
WakeUp
requested
Protection
WakeUp
requested
(SDM)
GoToProtection
Hibernate
-Tact switch Pushed
-last status is hibernateafter mains ON
Tact switch
pushed
I_17660_124.eps
140308
EN 27Q529.1E LC5.
Additional Info
•12NC LVDS2DP board. Displays the 12NC of the built-in
LVDS-to-DisplayPort software.
•12NC monitor board. Displays the 12NC of the monitor
board.
•SW version DPTX. Displays the built-in DisplayPort TX
software version.
•SW version DPRX. Displays the built-in DisplayPort RX
software version.
•SW version FPGA e-box. Displays the built-in FPGA ebox (HUB) software version.
•SW version FPGA monitor. Displays the built-in FPGA
monitor software version.
•SW version microP monitor. Displays the built-in monitor
microprocessor software version.
•SW version NVM monitor. Displays the built-in monitor
NVM software version.
How to Exit CSM
Press “MENU” on the RC-transmitter.
5.3Stepwise Start-up
When the TV is in a protection state due to an error detected by
stand-by software (error blinking is displayed) and SDM is
activated via shortcutting the pins on the SSB, the TV starts up
until it reaches the situation just before protection. So, this is a
kind of automatic stepwise start-up. In combination with the
start-up diagrams below, you can see which supplies are
present at a certain moment. Important to know is, that if e.g.
the 3V3 detection fails and thus error layer 2 = 18 is blinking
while the TV is restarted via SDM, the Stand-by Processor will
enable the 3V3, but the TV set will not go to protection now.
The TV will stay in this situation until it is reset (Mains/AC
Power supply interrupted). Caution: in case the start up in this
mode with a faulty FET 7U08 is done, you can destroy all IC’s
supplied by the +3V3, due to overvoltage (12V on 3V3-line). It
is recommended to measure first the FET 7U08 or other FET’s
on shortcircuit before activating SDM via the service pads.
The abbreviations “SP” and “MP” in the figures stand for:
•SP: protection or error detected by the Stand-by Processor.
•MP: protection or error detected by the MIPS Main
Processor.
Figure 5-3 Transition diagram
Page 28
EN 28Q529.1E LC5.
No
EJTAG probe
connected ?
No
Yes
Release AVC system r eset
Feed warm boot script
To I_17660_125b.epsTo I_17660_125b.eps
Cold boot?
Yes
No
Set I²C slave address
of Standby µP to (A0h)
An EJTAG probe (e.g. WindPower ICE probe) can
be connected for Linux Kernel debugging
purposes.
This will a llow access to NVM a nd
NAND FLASH and can not be done
earlier because the FLASH needs to
be in Write Protect as long as the
supplies are not available.
Detect EJTAG debug probe
(pulling pin of the probe interface to
ground by inserting EJTAG probe)
Relea se AVC system r eset
Feed cold boot script
Release AVC system r eset
Feed initializing boot script
disable alive mechanism
Initialise I/O pins of the st-by µP:
- Switch reset-AVCLOW (reset state)
- Switch WP-NandFlash LOW (protected)
- Switch reset-system LOW (reset state)
- Switch reset-5100 LOW (reset state)
- Switch reset-Ethernet LOW (reset state)
- Switch reset-ST7100 LOW (reset state)
- keep reset-NVM high, Audio-reset and Audio-Mute-Up HIGH
Off
Standby Supply starts running.
All standby supply voltages become available .
st-by µ P resets
Stand by or
Protection
Mains is app lied
- Switch Audio-Reset high.
It is low in the standby mode if the standby
mode lasted longer than 10s.
start keyboard scanning, RC detection. Wake up reasons are
off.
If the protection state was left by short circuiting the
SDM pins, detection of a protection condition during
startup will stall the startup. Protection conditions in a
playing set will be ignored. The protection mode will
not be entered.
Switch LOW the RESET-NVM line to allow access to NVM. (Add a
2ms delay before trying to address the NVM to allow correct NVM
initialization, this is not issue in this setup, the delay is automatically
covered by the architectural setup)
Release Reset-PNX5100.
PNX5100 will start b ooting.
Wait 10ms (minimum) to allow the bootscript
of the PNX5100 to configure the PCI arbiter
Before PNX8541 boots, the PNX5100 should have
set its PCI arbiter (bootscript command). To allow
this, approx. 1ms is needed. This 1ms is extended
to 10ms to also give some relaxation to the supplies.
Switch HIGH the WP-NandFlash to
allow access to NAND Flash
+12V, +/-12Vs, AL and Bolt-on power
is switched on, followed by the +1V2 DCDC converter
Enable the supply fault detection
algorithm
No
Yes
Detect-1 I/O line
High?
Switch ON Platform and display supply by switching
LOW the Standby line.
This enables the +3V3 and
+5V converter. As a result,
also +5V-tuner, +2V5, +1V8PNX8541 and +1V8-PNX5100
become available.
yes
Enable the DCDC converter for +3V3 and
+5V. (EN ABLE-3V3)
Voltage output error:
Layer1: 2
Layer2: 18
Important remark; the appearance of the +12V
will start the +1V2 DCDC converter automatically
No
Yes
Supply-fault I/O
High?
The supply-fault line is a
combination of the DCDC
converters and the audio
protection line.
1V2 DCDC or class D error:
Layer1: 2
Layer2: 19
Enter protection
No
Detect2 high received
within 1 second?
Power-OK er ror:
Layer1: 3
Layer2: 16
Enter protection
Yes
No
Supply-fault I/O
High?
3V3 / 5V DCDC or class D error:
Layer1: 2
Layer2: 11
Enter protection
Wait 50ms
Enter protection
Delay of 50ms needed because of the latency of the detect-1 circuit.
This delay is also needed for the PNX5100. The reset of the
PNX5100 should only be released 10ms after powering the IC.
Detect2 should be polled on the standard 40ms
interval and startup should be continued when
detect2 becomes high.
Yes
No
Detect -2 I/ O line
High?
Disable 3V3, switch standby
line high and wait 4 seconds
Added to make the system more robust to
power dips during startup. At this point the
regular supply fault detection algorithm which
normally detects power dips is not up and
running yet.
I_17660_125a.eps
140308
Service Modes, Error Codes, and Fault Finding
Figure 5-4 “Off” to “Semi Stand-by” flowchart (part 1)
Page 29
Service Modes, Error Codes, and Fault Finding
Yes
MIPS reads the wake up reason
from standby µP.
Semi-Standby
initialize tuner, Master IF and channel
decoder
Initialize video processing IC's
Initiali ze source sele ction
initialize AutoTV by triggering CHS AutoTV Init interface
3-th try?
No
Blink Code as
error code
Bootscript ready
in 1250 ms?
Yes
No
Enable Alive check mechanism
Wait until AVC starts to
communicate
SW initializatio n
succeeded
within 20s?
No
Switch Standby
I/O line high.
RPC start (comm. protocol)
Set I²C slave address
of Standby µP to (60h)
Yes
Disable all supply related protections and
switch off the +3V3 +5V DC/DC converter.
switch off the remaining DC/DC
converters
Wait 5ms
Switch AVC PNX85 41
in reset (active low )
Wait 10ms
Switch the NVM reset
line HIGH.
Flash to Ram
image transfer succeeded
within 30s?
No
Yes
Code =
Layer1: 2
Layer2: 53
Code =
Layer1: 2
Layer2: 15
Initialize Ambilight with Lights off.
Timing need to be updated if
more mature info is available.
Timing needs to
be updated if more
mature info is
available.
Timing needs to be
updated if more
matur e info is
available.
Downloaded
successfully ?
Download firmware into the channel
decoder
Third try?No
No
Yes
Log channel decoder error:
Layer1: 2
Layer2: 37
Yes
Initialize audio
Enter protection
Release reset MPEG4 module:
BOLT-ON-IO: High
MPEG4 module will start booting
autonomously.
Wait 3000 ms
Start alive IIC polling
mechanism
POR polling positive?
yes
No
Log SW event:
STi7100PorFailure
Wait 200 ms
POR polling positive?yes
No
bootSTi7100PorFailure:
Log HW error
Layer1: 2
Layer2: 38
and generate cold boot
Alive
polling
Log SW event
STi7100AliveFailedError
and generate fast cold reboot
eventually followed by a cold
reboot.
NOK
Reset-system is switched HIGH by the
AVC at the end of the bootscript
AVC releases Reset-Ethernet when the
end of the AVC boot-script is detected
This cannot be done through the bootscript,
the I/O is on the standby µP
Reset- system is connected to USB
From I_17660_125a.epsFrom I_17660_125a.eps
-reset,
4to1HDMI Mux and channel decoder.
Reset-Audio and Audio-Mute-Up are
switched by MIPS code later on in the
startup process
Reset-syst em is switched HIGH by the
AVC at the end of the bootscript
AVC releases Reset-Ethernet when the
end of the AVC boot-script is detected
Reset-Audio and Audio-Mute-Up are
switched by MIPS code later on in the
startup process
Switch on the display in case of a LED backlight
display by sending the TurnOnDisplay(1) (I²C)
command to the PNX5100
In case of a LED backlight display, a LED DIM panel is
present which is fed by the Vdisplay. To power the LED DIM
Panel, the Vdisplay switch driven by the PNX5100 must be
closed. The display startup sequence is taken care of by the
LED DIM panel.
I_17660_125b.eps
140308
EN 29Q529.1E LC5.
Figure 5-5 “Off” to “Semi Stand-by” flowchart (part 2)
Page 30
EN 30Q529.1E LC5.
Service Modes, Error Codes, and Fault Finding
Constraints taken into account:
- Display may only be started when valid LVDS output clock can be delivered by the AVC .
- Between 5 and 50 ms after power is supplied, display should receive valid lvds clock .
- minimum wait time to switch on the lamp after power up is 200ms.
action holder: AVC
action holder: St-by
autonomous action
The assumption here is that a f ast toggle (<2s)
can only happen during ON-> SEMI -> ON. In
these states, the AVC is still act ive and can
provide the 2s delay. If the transitio n ON-> SEMI-
>STBY -> SEMI -> ON can be made in less than 2s,
the semi -> stby transition has to be delayed
CPipe already generates a valid output
clock in t he semi -standb y state : display
startup can start immediately when leaving
The timings to be used in
combination with the PanelON
comman d for t his specific display
The higher level requirement is that audio and
video should be demuted without transient
effects and that the audio should be demuted
maximum 1s before or at the same time as the
until the requirement is met.
the semi-standby state.
TurnOnDisplay(1) (I²C) command to the PNX5100
unblanking of the video.
Semi Standby
Wait until previous on-state is left more than 2
seconds ago. (to prevent LCD display problems)
Assert RGB video blanking
Switch on the display by sending the
wait 250ms (min. = 200ms)
Switch on LCD backlight
(Lamp-ON)
Wait until valid and stable audio and video , corresponding to
the requested output is delivered by the AVC.
Switch Audio -Reset low and wait 5ms
Release audio mute and wait 100ms before any other audio
handling is done (e.g. volume change)
and audio mute
Initialize audio and video
processing IC's and functions
according needed use case.
The higher level requirement is that the
ambilig ht functionality may not be switched on
before the backlight is turned on in case the
set contains a CE IPB inverter supply.
Figure 5-6 “Semi Stand-by” to “Active” flowchart
unblank the video.
Switch on the Ambilight functionality according the last status
settings.
Active
I_17660_126.eps
140308
Page 31
Service Modes, Error Codes, and Fault Finding
Active
Semi Standby
action holder: AVC
autonomous action
action holder: St-by
Initialize audio and video
processing IC's and functions
according needed use case.
Assert RGB video blanking
and audio mute
Wait until previous on-state is left more than 2
seconds ago. (to prevent LCD display problems)
The assumption here is that a f ast toggle (<2s)
can only happen during ON->SEMI ->ON. In
these states, the AVC is still act ive and can
provide t he 2s delay. If the t ransition ON -> SEMI-
->STBY-> SEMI -> ON can be made in less than 2s,
the semi - > stby transition has to be delayed
until the requirement is met.
Switch Audio-Reset low and wait 5ms
Constraints taken into account:
- Display may only be started when valid LVDS output clock can be delivered by the AVC .
- Between 5 and 50 ms after power is supplied, display should receive valid lvds clock .
- minimum wait time to switch on the lamp after power up is 200ms.
- To have a reliable operation of the backlight, the backlight should be driven with a PWM duty cycle of 100%
during the first second. Only after this first one or two seconds, the PWM may be set to the required output level
(Note that the PWM output should be present before the backlight is switched on). To minimize the artefacts, the
picture should only be unblanked after these first seconds.
Restore dimming backlight feature, PWM and BOOST output
and unblank the video.
Wait until valid and stable audio and video, corresponding to the requested
output is delivered by the AVC
AND
[the backlight PWM has been on for 1s (internal inverter LPL displays
OR the backlight PWM has been on for 2s (external inverter LPL displays)] .
The higher level requirement is that audio and
video should be demuted without transient
effects and that the audio should be demuted
maximum 1s before or at the same time as the
unblanking of the video.
Release audio mute and wait 100ms before any other audio
handling is done (e.g. volume change)
CPipe already generates a valid output
clock in t he semi -standby state: d isplay
startup can start immediately when leaving
the semi-standby state.
wait 250ms (min. = 200ms)
Switch on LCD backlight
(Lamp-ON)
Switch off the dimming backlight feature, set
the BOOST control to nominal and make sure
PWM output is set to 100%
Switch on the display by sending the
TurnOnDisplay(1) (I²C) command to the PNX5100
Switch on the Ambilight functionality according the last status
settings.
The higher level requirement is that the
ambilig ht functionality may n ot be swit ched on
before the backlight is turned on in case the
set contains a CE IPB inverter supply.
I_17660_127.eps
140308
EN 31Q529.1E LC5.
Figure 5-7 “Semi Stand-by” to “Active” flowchart LCD with preheat
Page 32
EN 32Q529.1E LC5.
Active
Semi Standby
action holder: AVC
autonomous action
action holder: St-by
Initialize audio and video
processing IC's and functions
according needed use case.
Assert RGB video blanking
and audio mute
Wait until previous on-state is left more than 2
seconds ago. (to prevent LCD display problems)
The assumption here is that a f ast toggle (<2s)
can only happen during ON-> SEMI -> ON. In
these states, the AVC is still active an d can
provide the 2s delay. If the transition ON -> SEMI-
>STBY->SEMI->ON can be made in less than 2s,
the semi -> stby transition has to be delayed
until the requirement is met.
Switch Audio -Reset low and wait 5ms
Constraints taken into account:
- Display may only be started when valid LVDS output clock can be delivered by the AVC.
- Between 5 and 50 ms after power is supplied, display should receive valid lvds clock .
- minimum wait time to switch on the lamp after power up is 200ms.
unblank the video.
Wait until valid and stable audio and video , corresponding to
the requested output is delivered by the AVC.
The higher level requirement is that audio and
video should be demuted without transient
effects and that the audio should be demuted
maximum 1s before or at the same time as the
unblanking of the video.
Release audio mute and wait 100ms before any other audio
handling is done (e.g. volume change)
CPipe already generates a valid output
clock in t he semi -standby state : display
startup can start immediately when leaving
the semi-standby state.
wait 250ms (min. = 200ms)
TBC in def. spec
Switch on LCD backlight
(Lamp-ON)
Switch on the display by sending the OUTPUTENABLE (I²C) command to the LED DIM panel
Switch on the Ambilight functionality according the last status
settings.
The higher level requirement is that the
ambilig ht functionality may n ot be swit ched on
before the backlight is turned on in case the
set contains a CE IPB inverter supply.
I_17660_128.eps
140308
Service Modes, Error Codes, and Fault Finding
Figure 5-8 “Semi Stand-by” to “Active” flowchart (LED backlight)
Page 33
Service Modes, Error Codes, and Fault Finding
Semi Standby
Active
action holder: AVC
autonomous action
action holder: St-by
Wait 25 0ms (min. = 200ms)
Mute all sound outputs via softmute
Mute all video outputs
switch off LCD backlight
Force ext audio outputs to ground
(I/O: audio reset)
And wait 5ms
Switch off the display by sending the
TurnOnDisplay(0) (I²C) command to the PNX5100
switch o ff Ambilight
Set main amplifier mute (I/O: audio-mute)
Wait 100ms
Wait until Ambilight has faded out
(fixed wait time of x s)
The higher level requirement is that the
backlight may not be switched off before the
ambilight functionality is turned off in case the
set contains a CE IPB inverter supply.
I_17660_129.eps
140308
EN 33Q529.1E LC5.
Figure 5-9 “Active” to “Semi Stand-by” flowchart (LCD non DFI)
Page 34
EN 34Q529.1E LC5.
transfer Wake up reasons to the Stand by µP.
Stand by
Semi Stand by
action holder: MIPS
autonomous action
action holder: St-by
Disable all supply related protections and switch off
the DC/DC converters (ENABLE-3V3)
Switch OFF all supplies by switching HIGH the
Standby I/O line
Switch AVC system in reset state
Switch reset-PNX5100 LOW
Switch reset-ST7100 LOW
Switch Reset-Ethernet LOW
Important remark:
release reset audio 10 sec after
entering st andby to save pow er
Wait 5ms
Wait 10ms
Switch the NVM reset line HIGH
Switch het WP-Nandflash LOW
Delay transition until ramping down of ambient light is
finished. *)
If ambientlight functionality was used in semi -standby
(lampadaire mode), switch off ambient light
*) If this is not performed and the set is
switched to standby when the switch off of
the ambilights is still ongoing , the lights will
switch off abruptly when the supply is cut.
Switch Memories to self-refresh (this creates a more
stable condition when switching off the power).
I_17660_130.eps
140308
Service Modes, Error Codes, and Fault Finding
Figure 5-10 “Semi Stand-by” to “Stand-by” flowchart
Page 35
Service Modes, Error Codes, and Fault Finding
Protection
action holder: MIPS
autonomous action
action holder: St-by
Redefine wake up reasons for protection
state and transfer to stand-by µP.
Log the appropriate err or and
set stand-by flag in NVM
MP
Ask stand-by µP to enter protection state
Flash the Protection-LED in order to indicate
protection state*(*): This can be the standby LED or the ON LED
depending on the availability in the set
SP
Switch off LCD lamp supply
Wait 250ms (min. = 200ms)
Switch off LVDS signal
Switch off 12V LCD supply within a time frame of
min. 0.5ms to max. 50ms after LVDS switch off.
If needed to speed up this transition,
this block could be omitted . This is
depending on the outcome of the
safety investiga tions .
Disable all supply related protections and switch off
the +1V8 and the +3V3 DC/DC converter.
Switch OFF all supplies by switching HIGH the
Standby I/O line.
Switch AVC in r eset state
Wait 5ms
Wait 10ms
Switch the NVM r eset line H IGH.
I_17660_131.eps
140308
EN 35Q529.1E LC5.
Figure 5-11 “To Protection State” flowchart
5.4Service Tools
5.4.1ComPair
Introduction
ComPair (Computer Aided Repair) is a Service tool for Philips
Consumer Electronics products. and offers the following:
1. ComPair helps to quickly get an understanding on how to
repair the chassis in a short and effective way.
2. ComPair allows very detailed diagnostics and is therefore
capable of accurately indicating problem areas. No
knowledge on I
because ComPair takes care of this.
2
C or UART commands is necessary,
3. ComPair speeds up the repair time since it can
automatically communicate with the chassis (when the uP
is working) and all repair information is directly available.
4. ComPair features TV software up possibilities.
Specifications
ComPair consists of a Windows based fault finding program
and an interface box between PC and the (defective) product.
The ComPair II interface box is connected to the PC via an
USB cable. For the TV chassis, the ComPair interface box and
the TV communicate via a bi-directional cable via the service
connector(s).
The ComPair fault finding program is able to determine the
problem of the defective television, by a combination of
automatic diagnostics and an interactive question/answer
procedure.
Page 36
EN 36Q529.1E LC5.
E_06532_036.eps
150208
TO
UART SERVICE
CONNECTOR
TO
UART SERVICE
CONNECTOR
TO
I2C SERVICE
CONNECTOR
TO TV
PC
HDMI
I
2
C only
Optional power
5V DC
ComPair II Developed by Philips Brugge
RC out
RC in
Optional
Switch
PowerModeLink/
Activity
I
2
C
ComPair II
Multi
function
RS232 /UART
Service Modes, Error Codes, and Fault Finding
How to Connect
This is described in the chassis fault finding database in
ComPair.
Figure 5-12 ComPair II interface connection
Caution: It is compulsory to connect the TV to the PC as
shown in the picture above (with the ComPair interface in
between), as the ComPair interface acts as a level shifter. If
one connects the TV directly to the PC (via UART), ICs will be
blown!
How to Order
ComPair II order codes:
•ComPair II interface: 3122 785 91020.
•Software is available via internet:
http://www.atyourservice.ce.philips.com
•ComPair UART interface cable for Q52x.x.
(using 3.5 mm Mini Jack connector): 3104 311 12742.
Note: While encounting problems, contact the local support
desk.
5.4.2Memory and Audio Test
With this tool you can test the memory of the PNX8541, as well
if the PNX5100 is enabled and audio-testing.
What is needed?
– An USB-stick.
– “TESTSCRIPT Q529” (3104 337 05021). Downloadable
from the Philips Service website from the section “Software
for Service only”.
– A ComPair/service cable (3104 311 12742)
Procedure
Create a directory “JETTFILES” under the root of the USB-stick
– Place “MemoryTestPNX8635.bin” and “autojett.bin”
(available in “TESTSCRIPT Q529”) under the directory
“JETTFILES”
– Install the computer program “BOARDTESTLOGGER”
(available in “TESTSCRIPT Q529”) on the PC
– Connect a “ComPair/service”-cable from the service-
connector in the set to the COM1-port of the PC
– Start-up the program “BOARDTESTLOGGER” and select
“COM1”
– Put the USB stick into the TV and startup the TV while
pressing the “i+”-button on a Philips DVD RC6 remote
control (it’s also possible to use a TV remote in “DVD”mode)
– On the PC the memory test is shown now. This is also
visible on the TV screen.
– In “BOARDTESTLOGGER” an option “Send extra UART
command” can be found where you can select “AUD1”.
This command generates hear test tones of 200, 400,
1000, 2000, 3000, 5000, 8000 and 12500Hz.
5.4.3LVDS Tool
Support of this LVDS Tool has been discontinued.
5.5Error Codes
5.5.1Introduction
The error code buffer contains all detected errors since the last
time the buffer was erased. The buffer is written from left to
right, new errors are logged at the left side, and all other errors
shift one position to the right.
When an error occurs, it is added to the list of errors, provided
the list is not full. When an error occurs and the error buffer is
full, then the new error is not added, and the error buffer stays
intact (history is maintained).
To prevent that an occasional error stays in the list forever, the
error is removed from the list after more than 50 hrs. of
operation.
When multiple errors occur (errors occurred within a short time
span), there is a high probability that there is some relation
between them.
Below the way errors will be displayed on the HUB:
•There is a simple blinking LED procedure for board level
repair (home repair) so called LAYER 1 errors next to the
existing errors which are LAYER 2 errors.(see table 5-2
error code overview).
– LAYER 1 errors are one digit errors.
– LAYER 2 errors are 2 digit errors.
•In protection mode.
– From consumer mode: LAYER 1.
– From SDM mode: LAYER 2.
•Fatal errors, if I2C bus is blocked and the set reboots,
CSM and SAM are not selectable.
– From consumer mode: LAYER 1.
– From SDM mode: LAYER 2.
Important remark:
For all errors detected by MIPS which are fatal =>
rebooting of the TV set (reboot starts after LAYER error
1 blinking), one should short the solder paths at startup from the power OFF state by mains interruption and
not via the power button to trigger the SDM via the
hardware pins.
•In CSM mode
– When entering CSM: error LAYER 1 will be displayed
by blinking LED. Only the latest error is shown.
•In SDM mode
– When SDM is entered via Remote Control code or the
hardware pins, LAYER 2 is displayed via blinking LED
on the HUB.
•In the ON state
– In “Display error mode”, set with the RC commands
“mute_06250X _OK” LAYER 2 errors are displayed via
blinking LED on the HUB.
•Error display on screen.
– In CSM no error codes are displayed on screen.
– In SAM the complete error list from the HUB only is
shown!
Basically there are three kinds of errors:
•Errors detected by the Stand-by software which lead to protection. These errors will always lead to protection and
an automatic start of the blinking LED (HUB) LAYER error
1.(see section “5.6 The Blinking LED Procedure”).
•Errors detected by the Stand-by software which not lead to protection. In this case the LED from the HUB
should blink the involved error. See also section “5.5 Error
Codes, 5.5.4 Error Buffer, Extra Info”. Note that it can take
Page 37
Service Modes, Error Codes, and Fault Finding
up several minutes before the TV starts blinking the error
(e.g. LAYER error 1 = 2, LAYER error 2 = 15 or 53).
•Errors detected by main software (MIPS). In this case
the error will be logged into the error buffer and can be read
out via ComPair, via blinking LED method LAYER error 12, or in case picture is visible, via SAM.
Important remark :
Errors on the monitor are displayed by blinking LED only during
the start up.They will be displayed only once or twice.
5.5.2How to Read the Error Buffer
Use one of the following methods:
•On screen via the SAM (only when a picture is visible).
E.g.:
– 00 00 00 00 00: No errors detected
– 23 00 00 00 00: Error code 23 is the last and only
detected error.
– 37 23 00 00 00: Error code 23 was first detected and
error code 37 is the last detected error.
– Note that no protection errors can be logged in the
error buffer.
•Via the blinking LED procedure. See section 5.5.3 How to
Clear the Error Buffer.
•Via ComPair.
EN 37Q529.1E LC5.
5.5.3How to Clear the Error Buffer
Use one of the following methods:
•By activation of the “RESET ERROR BUFFER” command
in the SAM menu.
•With a normal RC, key in sequence “MUTE” followed by
“062599” and “OK”.
•If the content of the error buffer has not changed for 50+
hours, it resets automatically.
5.5.4Error 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.
If possible, check the entire contents of the error buffer. In
some situations, an error code is only the result of 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 stand-by processor.
•Via sensing of analog values on the stand-by processor or
the PNX8541.
•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.
2
C communication.
Page 38
EN 38Q529.1E LC5.
Table 5-2 Error code overview
Service Modes, Error Codes, and Fault Finding
DescriptionLayer 1 Layer 2
2
I
C3213MIPSEBL / EBSCL/D-SSBSSB
2
C4514MIPSEBL / EBSCL/D-DISPDisplay (LED back light only)
I
by
PNX doesn’t boot (HW cause) 215Stby µPEBLPNX8541 I
Monitored
Error/
Error Buffer/
Prot
Blinking LED DeviceDefective Board
2
C blocked SSB
12V316Stby µPPBL/Supply
1V2, 3V3, 5V to low218Stby µPPBL/SSB
1V2 or Class D219Stby µPPBL/SSB
3V3/5V DCDC to high211Stby µPPBL/SSB
Temp protection312MIPSPBL/EB/SSB
PNX 5100221MIPSEEBPNX5100SSB
HDMI mux223MIPSEEBAD8197ASSB
2
C switch224MIPSEEBPCA9540SSB
I
Master IF226MIPSEEBTDA9898SSB
FPGA Ambilight228MIPSEEB/SSB
Tuner234MIPSEEBUV1783S/TD1716SSB
Channel Decoder DVB-T237MIPSEEBTDA10048SSB
ST7100238MIPSEEBST7100SSB
FAN I2C expander741MIPSEEBPCA 9533SSB
T° sensor742MIPSEEBLM 75SSB
FAN 743/44MIPSEEB/FAN
main NVM2/MIPSEXSTM24C128SSB
Channel decoder DVB-C248MIPSEEBTDA 10023SSB
PNX doesn’t boot (SW cause) 253Stby µPEBLPNX8541SSB
DP Tx654MIPSEEBGM60028LVDS2DP
FPGA LVDS Rx655MIPSEEB
DP port not connected556MIPSEEBDP cable/monitor/
Extra Info
•Rebooting. When a TV is constantly rebooting due to
internal problems, most of the time no errors will be 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 Tips, 5.8.6
Logging). It’s shown that the loggings which are generated
by the main software keep continuing. In this case
diagnose has to be done via ComPair.
•Error 11 (3V3/5V too high). This protection can occur
during start up (LAYER error 1 = 2). Be careful to overrule
this protection via SDM for the reason supply related
devices can be possibly destroyed here.
•Error 12 (Temp protection). Current situation: when
temperature rises above limit inside the HUB, the
protection is triggered and the TV set is switched “OFF”. No
indication will be displayed on the LED of the HUB, yet
error layer = 12 is logged and will be displayed when SDM
is active.
•Error 13 (I
2
C bus 3 blocked). At the time of release of this
manual, this error was not working as expected. Current
situation: when this error occurs, the TV will constantly
reboot due to the blocked bus. The best way for further
diagnosis here, is to use ComPair.
•Error 15 (PNX8541 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 PNX8541
(supplies not OK, PNX 8541 completely dead, I
between PNX and Stand-by Processor broken, etc...).
When error 15 occurs it is also possible that I
blocked (NVM). I
2
C2 can be indicated in the schematics as
2
C link
2
C2 bus is
follows: SCL-UP-MIPS, SDA-UP-MIPS, SCL-2 or SDA-2.
Other root causes for this error can be due to hardware
problems with : NVM PNX5100, PNX5100 itself, DDR’s.
•Error 16 (12V). This voltage is made in the power supply
of the HUB and results in protection (LAYER error 1 = 3) in
case of absence. When SDM is activated we see blinking
LED LAYER error 2 = 16.
•Error 18 (1V2-3V3-5V too low). All these supplies are
generated by the DC/DC supply on the SSB. If one of these
supplies is too low, protection occurs and blinking LED
LAYER error 1 = 2 will be displayed automatically. In SDM
this gives LAYER error 2 = 18.
•Error 19 (1V2 or class D). If one of the 1V2 supplies is too
high or too low in the start up procedure the supply fault
becomes low.
•Error 21 (PNX 5100). At the time of release of this manual,
this error was not working as expected. Current situation:
when there is no I
2
C communication towards the PNX5100
after startup (power off by disconnection of the mains
cord), LAYER error 2 will blink continuously via the blinking
LED procedure in SDM. (startup the TV with the solder
paths short to activate SDM).
•Error 23 (HDMI). When there is no I
2
C communication
towards the HDMI mux after start up, LAYER error 2 = 23
will be logged and displayed via the blinking LED
procedure if SDM is switched on.
•Error 26 (Master IF). When there is no I
2
C communication
towards the Master IF after start up, LAYER error 2 = 26
will be logged and displayed via the blinking LED
procedure when SDM is switched on.
•Error 28 (FPGA ambilight). When there is no I
2
C
communication towards the FPGA ambilight after start up,
LAYER error 2 = 28 will be logged and displayed via the
blinking LED procedure if SDM is switched on. Note that it
can take up several minutes before the TV starts blinking
LAYER error 1 = 2 in CSM or in SDM, LAYER error 2 = 28.
•Error 34 (Tuner). When there is no I
2
C communication
towards the tuner after start up, LAYER error 2 = 34 will be
logged and displayed via the blinking LED procedure when
SDM is switched on.
•Error 37 (Channel decoder DVBT). When there is no I
2
communication towards the DVBT channel decoder after
start up, LAYER error 2 = 37 will be logged and displayed
via the blinking LED procedure if SDM is switched on.
•Error 38 (STI7100). When there is no I
2
C communication
towards the STI7100 after startup (power off by
C
Page 39
Service Modes, Error Codes, and Fault Finding
EN 39Q529.1E LC5.
disconnection of the mains cord), LAYER error 2 = 38 will
be logged and displayed via the blinking LED procedure in
SDM (startup the TV with the solder paths short to activate
SDM). Remark : if the error occurs during the ON state, the
TV will constantly reboot and no LED blinking will be
displayed. This rebooting can be recognized via a ComPair
interface and Hyperterminal (for Hyperterminal settings,
see section “5.8 Fault Finding and Repair Tips, 5.8.6
Logging”). It is shown that the loggings which are
generated by the main software keep continuing. Check in
the logging for keywords like e.g. “Device error 38”.
•Main NVM HUB. When there is no I
2
C communication
towards the main NVM, LAYER error 1 = 2 will be
displayed via the blinking LED procedure. In SDM, LAYER
error 2 can be 19 here. Check the logging for keywords like
2
“I
C bus blocked”.
•Error 42 (Temperature sensor). At the time of release of
this manual, this error was not working as expected.
Current situation: when this error occurs, the TV will
endlessly reboot due to the blocked bus. The best way for
further diagnosis here, is to use ComPair or check the
logging.
•Error 48 (Channel decoder DVBC). When there is no I
2
communication towards the DVBC channel decoder after
start up, LAYER error 2 = 48 will be logged and displayed
via the blinking LED procedure while SDM is active.
•Error 53. This error will indicate that the PNX8541 has
read his bootscript (when this would have failed, error 15
would blink) but initialization was never completed because
of hardware problems (NAND flash, ...) or software
initialization problems. Possible cause could be that there
is no valid software loaded (try to upgrade to the latest main
software version). Note that it can take up to 2 minutes
before the TV starts blinking LAYER error 1 = 2 or in SDM,
LAYER error 2 = 53.
•Error 55 (FPGA LVDS Rx). At the time of release of this
manual, this error was not working as expected. Current
situation: When there is no I2C communication towards the
LVDS2DP panel, the TV set will start rebooting and no
blinking on the hub will be displayed. The reset-start spacer
is displayed on the monitor LED once in a while as start of
the error blinking but none are logged. Because no picture
is available, the only way to detect failure on the FPGA
device is to check in the logging from the hub (via service
connector hub) prints as: “setting lvdsrx output enable to 1,
was 0”. This betrays the failure of the FPGA LVDS Rx.
5.5.5Monitor Errors for Essence
When an error of the monitor appears, it is displayed by a
blinking LED on the monitor triggered via the acknowledge of
C
the failing device. This is only once or twice. When the error
dissappears or when the I2C command is not repeated, the
blinking LED stops. Resetting the errors of the monitor is not
possible via the item “clear errors” in SAM and can not be read
out either in the error buffer, they only will be displayed via
blinking LED during start-up.
Table 5-3 Start-up errors Essence
DefectActionError on E-boxError on monitor
Supply cable and DP cable
unplugged
Supply cable and DP cable
unplugged
Supply cable unpluggedStart up with mains cord
Supply cable unpluggedStart up from Standby
DP cable unpluggedStart up with mains cord
DP cable unpluggedStart up from Standby
E-box defectSupply faultBlinking LED error 3
E-box defectSSB defect, DP initialized Blinking LED error 2
Start up with mains cord
or tact switch (HUB)
Start up from Standby
with RC6 (monitor)
or tact switch (HUB)
with RC6 (monitor)
or tact switch (HUB)
with RC6 (monitor)
Blinking LED error 5
No LED
Logging error 56 (layer 2)
No reactionNo LED and no RC6
blinking
Blinking LED error 5
Standby
Logging error 56 (layer 2)
Blinking LED error 5
Logging error 56 (layer 2)
Blinking LED error 5
RC6 blinking, Standby
LED, no error
No picture, no error
Logging error 56 (layer 2)
No RC 6 blinking
No picture, no error
Standby
if no 24V : Standby
Logging error layer 2 if
possible
24V=OK : no picture, no
error
No error
Logging error layer 2
E-box defectSSB defect, DP not
initialized
E-box defectDP boar defectBlinking LED error 6
Blinking LED error 2
Logging error layer 2
No picture, no error
No picture, no error
Logging error layer 2
Monitor defectFPGANo errorBlinking LED error 2
Logging error 2
Monitor defect3V3 monitorBlinking LED error 5
Logging error 56 (layer 2)
Monitor defect12V monitorBlinking LED error 5
Logging error 56 (layer 2)
Monitor defectDP port defectBlinking LED error 5
Blinking LED error 3
Logging error 3
Blinking LED error 4
Logging error 4
No picture, no error
Logging error 56 (layer 2)
Monitor defectDP RXBlinking LED error 5
Logging error 56 (layer 2)
Blinking LED error 6
Logging error 6
Monitor defectNVMNo errorBlinking LED error 7, No
logging possible
Extra Info
•At the time of release of this manual, errors as mentioned
above in table 5-3 can possibly not fully work as expected
due to unresolved software bugs.
Page 40
EN 40Q529.1E LC5.
Service Modes, Error Codes, and Fault Finding
5.6The Blinking LED Procedure
5.6.1Introduction
The blinking LED procedure can be split up into two situations:
•Blinking LED procedure LAYER error 1. In this case the
error is automatically blinked when the TV is put in CSM.
This will be only one digit error, namely the one that is
referring to the defective board (see table “Table 5-2 Error
code overview”) which causes the failure of the TV. This
approach will especially be used for home repair and call
centres. The aim here is to have service diagnosis from a
distance.
•Blinking LED procedure LAYER error 2. Via this procedure,
the content of the error buffer can be made visible via the
front LED of the HUB. In this case the error contains
2 digits (see table “Table 5-2 Error code overview”) and will
be displayed when SDM (hardware pins) is activated. This
is especially useful for fault finding and gives more details
regarding the failure of the defective board.
Important remark:
For all errors detected by MIPS which are fatal =>
rebooting of the TV set (reboot starts after LAYER error 1
blinking), one should short the solder paths at start-up from
the power OFF state by mains interruption and not via the
power button to trigger the SDM via the hardware pins.
When one of the blinking LED procedures is activated, the front
LED of the HUB will show (blink) the content of the error buffer.
Error codes greater then 10 are shown as follows:
1. “n” long blinks (where “n” = 1 to 9) indicating decimal digit
2. A pause of 1.5 s
3. “n” short blinks (where “n”= 1 to 9)
4. A pause of approximately 3 s,
5. When all the error codes are displayed, the sequence
finishes with a LED blink of 3 s
6. The sequence starts again.
Example: Error 12 8 6 0 0.
After activation of the SDM, the front LED will show:
1. One long blink of 750 ms (which is an indication of the
decimal digit) followed by a pause of 1.5 s
2. Two short blinks of 250 ms followed by a pause of 3 s
3. Eight short blinks followed by a pause of 3 s
4. Six short blinks followed by a pause of 3 s
5. One long blink of 3 s to finish the sequence
6. The sequence starts again.
5.6.2How to Activate
Use one of the following methods:
•Activate the CSM. The blinking front LED of the HUB will
show only the latest layer error 1, this works in “normal
operation” mode or automatically when the error/protection
is monitored by the standby processor. At the time of this
release, this layer error 1 blinking was not working as
expected.
In case no picture is shown and there is no LED blinking,
read the logging to detect whether “error devices” are
mentioned. (see section “5.8 Fault Finding and Repair
Tips, 5.8.6 Logging”).
•Activate the SDM. The blinking front LED of the HUB will
show the entire contents of the layer error 2 buffer, this
works in “normal operation” mode or when SDM (via
hardware pins) is activated when the tv set is in protection.
Important remark:
For all errors detected by MIPS which are fatal =>
rebooting of the TV set (reboot starts after LAYER error 1
blinking), one should short the solder paths at start up from
the power OFF state by mains interruption and not via the
power button to trigger the SDM via the hardware pins.
•Transmit the commands “MUTE” - “062500” - “OK” with a normal RC. The complete error buffer is shown.
Take notice that it takes some seconds before the blinking
LED starts.
•Transmit the commands “MUTE” - “06250x” - “OK” with a normal RC (where “x” is a number between 1
and 5). When x = 1 the last detected error is shown, x = 2
the second last error, etc.... Take notice that it takes some
seconds before the blinking LED starts.
5.7Protections
5.7.1Software Protections
Most of the protections and errors use either the stand-by
microprocessor or the MIPS controller as detection device.
Since in these cases, checking of observers, polling of ADCs,
and filtering of input values are all heavily software based,
these protections are referred to as software protections.
There are several types of software related protections, solving
a variety of fault conditions:
•Protections related to supplies: check of the 12V, +5V,
+3V3 and 1V2.
•Protections related to breakdown of the safety check mechanism. E.g. since the protection detections are done
by means of software, failing of the software will have to
initiate a protection mode since safety cannot be
guaranteed any more.
Remark on the Supply Errors
The detection of a supply dip or supply loss during the normal
playing of the set does not lead to a protection, but to a cold
reboot of the set. If the supply is still missing after the reboot,
the TV will go to protection.
Protections during Start-up
During TV start-up, some voltages and IC observers are
actively monitored to be able to optimize the start up speed,
and to assure good operation of all components. If these
monitors do not respond in a defined way, this indicates a
malfunction of the system and leads to a protection. As the
observers are only used during start up, they are described in
the start up flow in detail (see section “5.3 Stepwise Start-up”).
5.7.2Hardware Protections
The only real hardware protection in this chassis appears in
case of an audio problem e.g. DC voltage on the speakers. The
DC check circuit pulls the “A-STBY” line low and will paralize
the Class-D audio.
5.7.3Important remark regarding the blinking LED indication
As for the blinking LED indication, the blinking of error layer 1
can be switched off by pushing the power button on the
keyboard.
This condition is not valid after the set was unpowered (via
mains interruption). The blinking LED starts again and can only
be switched off by unplugging the mains connection.
This can be explained by the fact that the MIPS can not load
the keyboard functionality from software during the start up and
doesn’t recognizes the keyboard commands at this time.
Page 41
Service Modes, Error Codes, and Fault Finding
EN 41Q529.1E LC5.
5.8Fault Finding and Repair Tips
Read also section “5.5 Error Codes, 5.5.4 Error Buffer, Extra
Info”.
5.8.1Audio Amplifier
The Class D-IC 7D10 has a powerpad for cooling. When the IC
is replaced it must be ensured that the powerpad is very well
pushed to the PCB while the solder is still liquid. This is needed
to insure that the cooling is guaranteed, otherwise the Class DIC could break down in short time.
5.8.2CSM
When CSM is activated and there is a USB stick connected to
the TV, the software will dump the complete CSM content to the
USB stick. The file (CSM.txt) will be saved in the root of the
USB stick. If this mechanism works it can be concluded that a
large part of the operating system is already working (MIPS,
USB...)
5.8.3DC/DC Converter
Introduction
The onboard supply consists of 5 DC/DC converters and 7
linear stabilizers. The DC/DC converters have all +12V input
voltage and deliver:
1. +1V2-PNX8541 supply voltage, stabilised close to
PNX8541 chip.
2. +1V2-PNX5100 supply voltage, stabilised close to
PNX5100 chip.
3. +3V3 (overall 3.3 V for onboard IC’s).
4. +5V for USB and Conditional Access Interface and +5V5TUN tuner stabilizer.
5. +33VTUN for analogue only tuners (AP diversity).
The linear stabilizers are providing:
1. +1V supply voltage (out of +1V2-PNX8541), stabilized
close to ST7101 chip (MPEG4 diversity).
2. +1V8-PNX5100.
3. +1V8-PNX8541 (reserved because +1V8-PNX5100 used
also for DDR2 interface of PNX8541 via 5FB0).
4. +2V5 (MPEG4 diversity).
5. +1V2-STANDBY (out of +3V3-STANDBY).
6. +5V-TUN (out of +5V5-TUN).
7. +3V3-STANDBY (out of +12V, reserved).
+3V3-STANDY and +1V2-STANDBY are permanent voltages.
Supply voltages +1V2-PNX8541, +1V2-PNX5100 and +1V are
started immediately when +12V incoming voltage is available
(+12V is enabled by STANDBY signal, active low). Supply
voltages +3V3, 2V5, +1V8-PNX5100, +1V8-PNX8541, +5V
and +5V-TUN are switched-on directly by signal ENABLE-3V3
(active low) when +12V and previous mentioned voltages are
all available.
Debugging
The best way to find a failure in the DC/DC converters is to
check their starting-up sequence at power-on via the mains
cord, presuming that the standby microprocessor and the
external supply are operational. Take STANDBY signal highto-low transition as reference.
When +12V rises above 10V then +1V2-PNX8541, +1V2PNX5100 and +1V are started immediately. Then, after
ENABLE-3V3 goes low, all the other supply voltages should
rise within 10 ms. Boost voltages should be OK when +1V2PNX8541, +1V2-PNX5100 are available (FU07 and FU8A,
around 19V).
SUPPLY-FAULT signal should be high when all supply
voltages are started-up.
Tips
•Usually, when supply voltage is short-circuited to GND, the
corresponding DC/DC converter is making audible noise.
•The drop voltage across resistors 3U70 and 3U3T is
100 mV to 2000 mV.
•Defective (in short-circuit) power MOS-FET’s lead usually
to their controller IC broken; if one or more high-side MOSFET’s (7U05, 7U08, 7U0D-1 or 7U0H-1) is broken then the
platform can be heavily damaged if started in SDM-mode
(SUPPLY-FAULT signal is then ignored, while higher than
normal supplies will be generated).
•The +33VTUN generator circuit (7U0P + 7U0Q +
surrounding components) has low output current
capability. In case of too low or no output voltage check
transistor 7U0P (gate voltage pulses of about 10 V
amplitude and drain voltage pulses of about 35 V
amplitude) and the load (not more than 4.5 mA).
•High output ripple voltage of DC/DC converters can be
caused by defective (cracked or bad soldered) ceramic
capacitors in the feedback (DC or AC) input or output
filtering.
5.8.4Exit “Factory Mode”
When an “F” is displayed in the screen's right corner, this
means that the set is in “Factory” mode, and it normally
happens after a new SSB has been mounted.
To exit this mode, push the “VOLUME minus” button on the
TV's local keyboard control for 10 seconds (this disables the
continuous mode).
Now push the “MENU” button for 10 seconds untill the “F”
disappears from the screen.
5.8.5FAN selftest
A FAN-selftest can be done by pushing the red coloured button
on the remote control while the TV set is in CSM. Fore further
details, exit CSM and check the status of the FAN in the error
buffer via SAM (062596 + info button on the remote control). In
case of failure, the corresponding errors are displayed in the
error buffer (error 41,42,43, 44).
5.8.6Logging
When something is wrong with the TV set (f.i.the set is
rebooting) you can check for more information via the logging
in Hyperterminal. The Hyperterminal is available in every
Windows application via Programs, Accessories,
Communications, Hyperterminal. Connect a “ComPair UART”cable (3104 311 12742) from the service connector in the TV
set to the “COM1”-port of the PC. After start-up of the
Hyperterminal, fill in a name (f.i. “logging”) in the “Connection
Description” box, then apply the following settings:
1. COM1
2. Bits per second = 38400
3. Data bits = 8
4. Parity = none
5. Stop bits = 1
6. Flow control = none
During the start-up of the TV set, the logging will be displayed.
This is also the case during rebooting of the TV set (the same
logging appears time after time). Also available in the logging
is the “Display Option Code” (useful when there is no picture),
look for item “DisplayRawNumber” in the beginning of the
logging. Tip: when there is no picture available during rebooting
you are able to check for “error devices” in the logging (LAYER
2 error) which can be very helpful to determine the failure cause
of the reboot. For protection state, there is no logging.
Page 42
EN 42Q529.1E LC5.
I_18020_145.eps
190908
X530EDID1
X530EDID2
X530EDID3
5.8.7Loudspeakers
Make sure that the volume is set to minimum during
disconnecting the speakers in the ON-state of the TV. The
audio amplifier can be damaged by disconnecting the speakers
during ON-state of the set! Sometimes the set can go into
protection, but that is not always the case.
5.8.8Tuner
Attention: In case the tuner is replaced, always check the tuner
options!
5.8.9UI over PCI bus
The UI is not integrated in the RGB signal but is sent from
PNX8541 to PNX5100 via the PCI bus. TXT and MHEG are
integrated in the RGB signal. So when TXT signal is available
but no UI, check the PCI bus.
5.8.10 Display option code
Attention: In case the SSB is replaced, always check the
display option code in SAM, even when picture is available.
Performance with the incorrect display option code can lead to
unwanted side-effects for certain conditions.
Service Modes, Error Codes, and Fault Finding
5.8.11 Upgrade EDID NVM
To upgrade the EDID NVM pin 7 of the EDID NVM has to be
short circuited to ground. Therefore some test points are
foreseen (figure “EDID-NVM pins”). See ComPair for further
instructions.
Figure 5-13 EDID-NVM pins
5.8.12 SSB Replacement
Follow the instructions in the flowchart in case a SSB has to be
exchanged. See figure “SSB replacement flowchart”.
Page 43
Service Modes, Error Codes, and Fault Finding
START
Create “r epair” directory on USB stick and
connect USB stick to TV-set
Go to SAM mode and save the TV settings
via “Upload to USB”.
Set is still
operating?
- Replace SSB board by a Service SSB.
- Make the SSB fit mechanically to the set.
Go to SAM mode, and reload settings
via “Download from USB”.
Saved settings
on USB stick?
Program “Display Option” code via 062598 MENU, followed by 3 digits code (this code
can be found on a sticker inside the set).
Check and perform alignments in SAM
according to the Service Manual.
E.g. option codes, colour temperature...
Connect PC via ComPair interface to Service
connector.
END
Yes
After entering “Display Option” code, set is
going to Standby (= validation of code).
Restart the set.
In case of settings reloaded from USB , the set type ,
serial number , Di splay 12 NC, are automaticall y stored
when enter ing dis play opti ons .
No
- C heck if corr ect “D ispl ay Option” code is pr ogram med .
- Ver ify “ Option C odes” ac cordi ng stick er ins ide the set .
- D efault set tings for Whi te driv e ... see Servi ce Manual
Final check of all menus in CSM.
Special attention for HDMI Keys.
Program “set type number”, “serial number”,
and “display 12NC”.
Update main software in this step, by using
“autorun.upg” file.
Start TV in Jett mode (DVD i+ (OSD))
Open ComPair browser Q52x.
Noisy picture with bands/lines is visible and the
red LED is continuous “on”
(sometimes also the letter “F” is visible).
Press 5 s. the “Volume minus” button on the local
cntrl until the red LED switches “off”, and then
press 5 s. the MENU button of the local cntrl.
The picture noise is replaced by blue mute!
Unplug the mainscord to verify the correct
disabling of the factory-mode.
Program “Display Option” code via 062598 MENU,
followed by 3 digits code (this code can be found
on a sticker inside the set ).
After entering “Display Option” code, set is going
to Standby (= validation of code).
Restart the set.
Set is sta rting up in “Fa ctory” mode .
Start-up set.
Set behaviour?
H_16771_007.eps
171008
EN 43Q529.1E LC5.
Figure 5-14 SSB replacement flowchart
Page 44
EN 44Q529.1E LC5.
Service Modes, Error Codes, and Fault Finding
5.9Software Upgrading
5.9.1Introduction
The set software and security keys are stored in a NANDFlash, which is connected to the PNX8541 via the PCI bus.
It is possible for the user to upgrade the main software via the
USB port. This allows replacement of a software image in a
stand alone set, without the need of an E-JTAG debugger. A
description on how to upgrade the main software can be found
in the DFU.
Important: When the NAND-Flash must be replaced, a new
SSB must be ordered, due to the presence of the security keys!
(copy protection keys, MAC address, ...). It is however also
possible to replace the NAND-Flash with a good one from a
scrap-board.
Perform the following actions after SSB replacement:
1. Set the correct option codes (see sticker inside the TV).
2. Update the TV software (see the DFU for instructions).
3. Perform the alignments as described in chapter 8 (section
“Reset of Repaired SSB”).
4. Check in CSM if the HDMI keys are valid.
For the correct order number of a new SSB, always refer to the
Spare Parts list!
5.9.2Main Software Upgrade
•The “UpgradeAll.upg” file is only used in the factory.
•The “FlashUtils.upg” file is only used by service centra
which are allowed to do component level repair on the
SSB.
Automatic Software Upgrade
In “normal” conditions, so when there is no major problem with
the TV, the main software and the default software upgrade
application can be upgraded with the “AUTORUN.UPG”
(FUS part of the one-zip file: e.g. 3104 337 04731 _FUS
_Q591E_ 1.25.5.0_commercial.zip). This can also be done by
the consumers themselves, but they will have to get their
software from the commercial Philips website or via the
Software Update Assistant in the user menu (see DFU). The
“autorun.upg” file must be placed in the root of the USB stick.
How to upgrade:
1. Copy “AUTORUN.UPG” to the root of the USB stick.
2. Insert USB stick in the set while the set is in ON MODE.
The set will restart and the upgrading will start
automatically. As soon as the programming is finished, a
message is shown to remove the USB stick and restart the
set.
Manual Software Upgrade
In case that the software upgrade application does not start
automatically, it can also be started manually.
How to start the software upgrade application manually:
1. Disconnect the TV from the Mains/AC Power.
2. Press the “OK” button on a Philips TV remote control or a
Philips DVD RC-6 remote control (it is also possible to use
a TV remote in “DVD” mode). Keep the “OK” button
pressed while reconnecting the TV to the Mains/AC Power.
3. The software upgrade application will start.
Attention!
In case the download application has been started manually,
the “autorun.upg” will maybe not be recognized.
What to do in this case:
1. Create a directory “UPGRADES” on the USB stick.
2. Rename the “autorun.upg” to something else, e.g. to
“software.upg”. Do not use long or complicated names,
keep it simple. Make sure that “AUTORUN.UPG” is no
longer present in the root of the USB stick.
3. Copy the renamed “upg” file into this directory.
4. Insert USB stick into the TV.
5. The renamed “upg” file will be visible and selectable in the
upgrade application.
Back-up Software Upgrade Application
If the default software upgrade application does not start (could
be due to a corrupted boot 2 sector) via the above described
method, try activating the “back-up software upgrade
application”.
How to start the “back-up software upgrade application”
manually:
1. Disconnect the TV from the Mains/AC Power.
2. Press the “INFO”-button on a Philips remote control or
“CURSOR DOWN” button on a Philips DVD RC-6 remote
control (it is also possible to use a TV remote in “DVD”
mode). Keep the “INFO”-button (or “cursor down” button)
pressed while reconnecting the TV to the Mains/AC Power.
3. The software upgrade application will start.
5.9.3Stand-by Software Upgrade via USB
In this chassis it is possible to upgrade the Stand-by software
via a USB stick. The method is similar to upgrading the main
software via USB.
Use the following steps:
1. Create a directory “UPGRADES” on the USB stick.
2. Copy the Stand-by software (part of the one-zip file, e.g.
StandbySW_CFT55_35.0.0.0.upg) into this directory.
3. Insert the USB stick into the TV.
4. Start the download application manually (see section “
Manual Software Upgrade”.
5. Select the appropriate file and press the “red” button to
upgrade.
5.9.4Content and Usage of the One-Zip Software File
Below the content of the One-Zip file is explained, and
instructions on how and when to use it.
•1.1 Ambilight_PRFAM_x.x.x.x.zip. Not to be used for
Q529.1E LC sets.
•1.2 bootProm_PNX5100_Q591X_x.x.x.x.zip. A
programmed device can be ordered via the regional
Service organization.
•1.3 Cabinet_ACOUS_x.x.x.x.zip. Not to be used by
Service technicians.
•1.4 Ceisp2padll_P2PAD_x.x.x.x.zip. Not to be used by
Service technicians. For ComPair development only.
•1.5 DDC_Q591X_x.x.x.x.zip. Contains the content of the
VGA NVM. See ComPair for further instruction.
•1.6 Display_DISPT_x.x.x.x.zip. Not to be used by Service
technicians.
•1.7 EDID_Q591X_x.x.x.x.zip. Contains the EDID content
of the different EDID NVM’s. See ComPair for further
instructions.
For sets with four HDMI connectors.
–For HDMI 1 NVM, use “*port 1*.bin”
–For HDMI 2 NVM, use “*port 2*.bin”
–For HDMI 3 NVM, use “*port 3*.bin”
•1.8 EJTAGDownload_Q591X_x.x.x.x.zip. Only used by
service centra which are allowed to do component level
repair.
•1.9 Factory_Q591X_x.x.x.x_commercial.zip. Only for
production purposes, not to be used by Service
technicians.
•2.0 FlashUtils_Q591X_x.x.x.x_commercial.zip. Not to
be used by Service technicians.
•2.1 LightGuide_TV522_x.x.x.x_.zip. Not to be used by
Service Technicians.
•2.2 FUS_Q591X_x.x.x.x_commercial.zip. Contains the
“autorun.upg” which is needed to upgrade the TV main
software and the software download application.
•2.3 MOP_RXSXX_x.x.x.x.zip. Not to be used for Q529.1E
LC sets.
Page 45
Service Modes, Error Codes, and Fault Finding
-JBL
- version.txt
- boot batch file #1
µBTM
partition table
Backup
- boot batch file #2
- Linux Kernel including
Ramdisk image with
-minimal RFS
- SW dow nload app #1
-JETT
Block 0
- boot batch file #3
- TM application
- Linux Kernel including
Ramdisk image with
-minimal RFS
- SW dow nload app #2
Application R/W data
Application 'data' partition
Root File System
- minimal R FS
- MIPS user-space TV app
- Application R/O rrfs data
Application R/O upgradable data
Application 'B oot' partition
SQUASHFS partition
JFFS2 partition #1
JFFS2 partition #0
(split in 2 virtual partitions on
ceinfra level, based on path)
BFFS partition #0
BFFS partition #1
BFFS partition #2
Application R/O once data
- PNX5100 image
BFFS partition #3
I_17662_001.eps
110608
EN 45Q529.1E LC5.
•2.4 OAD_Q591X_x.x.x.x.zip. Not to be used by Service
•2.5OpenSourceFile_Q591X_x.x.x.x.zip. Not to be used
•2.6 PQPrivate_U5228_x.x.x.x.zip. Not to be used by
•2.7 PQPublic_U5228_x.x.x.x.zip. Not to be used by
•2.8 ProcessNVM_Q591X_x.x.x.x.zip. Default NVM
•2.9 StandbySW_CFTxx_x.x.x.x_commercial.zip.
•3.0 stmp4_xxxx.xxxx.xxxx.zip. This is a separate
•3.1 UpgradeAll_Q591X_x.x.x.x_commercial.zip. Only
•3.2 UpgradeExe_Q591X_x.x.x.x.zip. Not to be used by
5.9.5Explanation UART log
How to log and change settings: see section 5.8.5 Logging.
What's inside the flash of a TV set
Technicians.
by Service technicians.
Service technicians.
Service technicians.
content. Must be programmed via ComPair.
Contains the Stand-by software in “upg” and “hex” format.
– The “StandbySW_xxxxx_prod.upg” file can be used to
upgrade the Stand-by software via USB.
– The “StandbySW_xxxxx.hex” file can be used to
upgrade the Stand-by software via ComPair.
– The files “StandbySW_xxxxx_exhex.hex” and
“StandbySW_xxxxx_dev.upg” may not be used by
Service technicians (only for development purposes).
MPEG4 SW (is also part of the FUS autorun.upg). Not to
be used by Service Technicians.
for production purposes, not to be used by Service
technicians.
Caution: Never try to use this file, because it will
overwrite the HDCP keys ! ! !
Service Technicians.
Figure 5-15 Sections in a flash device
Explanation of the sections
The flash of TV520 sets consists of a boot-block (block 0), a
number of BFFS (Boot Flash File System) partitions, one
SquashFS (compressed read-only filesystem for Linux.
SquashFS is intended for general read-only filesystem use, for
archival use) partition and a number of JFFS (Journaling Flash
File System) partitions. The BFFS partitions contain the
program code and compile-time data. The SquashFS partition
contains the Linux rootfs including the standard RFS (Root File
System) directory structures (dev,lib, modules, … ) and MIPS
executables (elf).
For the purpose of SWUPG (SoftWare UPGrade application)
the following points are important:
•The boot-block (block 0) contains also the partition table.
This table indicates which partitions there are on this
system and where they are located on the flash. All
programs that want to access the flash contents should use
this table.
•At system start-up the BTM (Boot Manager) loads the JBL
(Jaguar Boot Loader) from /bffs0. The JBL then starts
interpreting the boot.bat file from the highest available
BFFS partition. If no boot.bat is found there, the next lower
partition is tried.
•/bffs1 partition contains:
1. kernel image.
2. ramdisk image of RFS holding bare minimum (no
debug tooling), including mod/libs , the SW backup
upgrade executable, the Jett executable and the helper
executable (init + MTD utils used to flash).
3. boot batch file.
•The backup SWUPG is stored in the /boot1 BFFS partition
in the factory, together with a boot.bat that by defaults
loads this SWUPG. This way the set will always load this
SWUPG if nothing is in /bffs2.
•/bffs2 partition contains:
1. kernel image.
2. ramdisk image of RFS holding bare minimum (no
debug tooling), including mod/libs , the SW backup
upgrade executable and the helper executable (init +
MTD utils used to flash).
3. TM image.
4. boot batch file.
•In /boot2 an additional SWUPG shall always be written,
either in the factory or by the end-user through an upgrade,
which will overrule the one in /boot1. Here also the TM
image is stored and a boot.bat which by default loads the
main TV application, but falls back on the /boot2/SWUPG
if that fails.
•/bffs3 partition contains PNX5100 images.
•In SquashFS, the TV application RFS flashed as a partition
image. Content identical to the RAMDISK RFS at the
exception that it includes the TV application in stead of
SWUPG.
•JFFS2 partition0 contains the R/O once data, which can
only written be written in the factory.
•JFFS2 partition1 contains the R/W data.
Startup sequence TV
The UART doesn't show the standby output.
Page 46
EN 46Q529.1E LC5.
UªUretail Jan 16 2008 12:03:04 _____> µµBTM startup
Boot deviceST NAND512W3A
BFFS init
OK
Searching BootLoader.tdfLoad /bffs0/BootLoader.tdf- Done _____> Bootloader sta rtup
Start /bffs0/BootLoader.tdf
JBL (boottime improvement
BootLoader OS_R0.7.2assert Feb 25 2008 12:49:28Searching boot.bat
Execute /bffs2/boot.bat from label [4] _____> Application selection startup (SWUPG on bffs2)
* SR4->USB SW DL boot2
* On error goto 6
* Load /bffs2/Kernel.tdf - ok
* Load /bffs2/RFSBoot2.tdf - ok
* MemFill 0x87fff000 0x1000 0xff
* Signal 30
* Cmd Line
CMD_LINE arguments passed by JBL : console=ttyS0,38400n8 mem=60M kgdb=ttyS1 l
oglevel=3 init=/init ip=none jffs2_gc_delay=0 root=/dev/ram lpj=1196032 rd_sta
rt=0x80500000 rd_size=1568768* Start /bffs2/Kernel.tdf"htv520EU/92 startup script ..."
"Mounting file systems"
Total usertime mount for /proc: 0,000000 [Sec]
Total systemtime mount for /proc: 0,000000 [Sec]
Total usertime mount for /sys: 0,000000 [Sec]
Total systemtime mount for /sys: 0,010000 [Sec]
Total usertime mount for /dev/shm: 0,000000 [Sec]
Total systemtime mount for /dev/shm: 0,000000 [Sec]
Total usertime mount for /dev/pts: 0,000000 [Sec]
Total systemtime mount for /dev/pts: 0,000000 [Sec]
"Loading PNX5100 Image"
"Launching SW Download Application From Boot2" ______> extra information telling which application is started up
checking hotboot: NO
Standby version 40.x.0.0
start_Init clearing m_InitDoneBlunk
Using errlib version 0.9
Errlib 0.9 registered from process 147
3533 - ReferenRW partition: 4
mounting partition 4 to jffs2 file system passed RW partition: 5
mounting partition 5 to jffs2 file system passed
mounted: </dev/mtdblock6>
Mount check passes, 0 iterations
mounted: </dev/mtdblock7>
Mount check passes, 0 iterations
pffsN_OnMounted sets m_InitDoneBlunk to true
InitCehtvData done
ReadCehtvData ConfigVersion: [0.01] OK
ReadCehtvData ProductID: [Q591E] OK
ReadCehtvData OUI: [0000903E] OK
ReadCehtvData HardwareModel: [0203] OK
ReadCehtvData HardwareVersion: [0100] OK
ConvertAscii2Bin started
ConvertAscii2Bin done
ConvertAscii2Bin started
ConvertAscii2Bin done
ReadCehtvData PublicKey: OK
ReadCehtvData done, ConfigOK: TRUE
Could allocate 36701184. _____>The amount of memory free to load the upg into. If upg size >
free memory, upg will not be programmed
redirecting 1 to 20
00 005.151 Startup m_InitDoneBlunk: 1, m_InitDoneMain: 1
00 005.151 /mnt/jffs0/rupg/tvplf/cetv/display found - Layoutcheck OK
00 005.151 Display flash file : Layout version = 8 ; Content version = 17
00 005.151 Display flash file : Project Id = 1 ; Branch Id = 0
00 005.151 version string: DISPT_001.000.008.017
00 005.151 Using screen option 142, name LCD LGD WUF SAA1 42"
00 005.151 MMIO address obtained from pnx5xxx drv = 0x28000000
00 005.151 redirecting 2 to 23
00 005.164 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnk
nownAttachedError, -1 )" notification given
00 005.165 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnk
nownAttachedError, -1 )" notification given
00 005.167 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnk
nownAttachedError, -1 )" notification given
00 005.169 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnk
nownAttachedError, -1 )" notification given
00 005.171 ***GVC: T2 - ceisusb_m.c (817): "usbdevspN_OnPhysicalDeviceConnecte
d( 0 )" notification given...
00 005.310 startr_init
00 005.310 Startup m_InitDoneBlunk: 1, m_InitDoneMain: 1
00 005.413 gfxptr: 2dea0000
00 005.413 malloc 776605704
00 005.413 Starting STi710x device with i2c protocol version v0.5 !
00 005.413 ST TurnOn first attemptS18,0,Q591E_0.39.0.0
00 005.751 Go!!!!!!!
00 005.850 Por: 1
00 005.860 ST start up OKST SW Version: MPEG4.001.000.000.029
00 005.870 ST HW Version: MP4HW.000.000.012.002
00 005.872 Amount of upgs on usb 0
00 005.874 No upg files found!
00 009.182 ***GVC: T2 - ceisusb_m.c (1199): "usbdevspN_OnNewDevice( 0 )" notification given.
00 009.271 ***GVC: T2 - ceisusb_m.c (1408): "usbdevspN_OnDriveMounted( 0 )" notification given
00 009.273 OnDriveMounted : 0
00 009.559 ceapps OnUpgradesChanged : 0
00 009.567 Amount of upgs on usb 20
--------------------------------- Here Application is started up ------------------------------------------------
00 009.772 20 upgs found on USB. Press right to enter the list. _____>Amount of upgs found.
I_17662_002.eps
110608
Service Modes, Error Codes, and Fault Finding
Figure 5-16 Example UART log during SWUPG startup (DVD OK).
Page 47
Service Modes, Error Codes, and Fault Finding
UªUretail Jan 16 2008 12:03:04
Boot deviceST NAND512W3A
BFFS init
OK
Searching BootLoader.tdfLoad /bffs0/BootLoader.tdf- Done
Start /bffs0/BootLoader.tdf
JBL (boottime improvement
BootLoader OS_R0.7.2assert Feb 25 2008 12:49:28Searching boot.bat
Execute /bffs2/boot.bat from label [6]
unknown command, line 302
Execute /bffs1/boot.bat from label [6]
* boot1: SR6->USB SW DL boot1
* On error goto 70
* Load /bffs1/Kernel.tdf - ok
* Load /bffs1/RFSBoot1.tdf - ok
* MemFill 0x87fff000 0x1000 0xff
* Signal 30
* Cmd Line
CMD_LINE arguments passed by JBL : console=ttyS0,38400n8 mem=60M kgdb=ttyS1 loglevel=3 init=/init ip=none root=/dev/ram lpj=1196032 rd_start=0x80500000 rd_
size=1818624* Start /bffs1/Kernel.tdf"htv520EU/92 startup script ..."
"Mounting file systems"
Total usertime mount for /proc: 0,000000 [Sec]
Total systemtime mount for /proc: 0,000000 [Sec]
Total usertime mount for /sys: 0,000000 [Sec]
Total systemtime mount for /sys: 0,000000 [Sec]
Total usertime mount for /dev/shm: 0,000000 [Sec]
Total systemtime mount for /dev/shm: 0,000000 [Sec]
Total usertime mount for /dev/pts: 0,000000 [Sec]
Total systemtime mount for /dev/pts: 0,000000 [Sec]
"Loading PNX5100 Image"
"Launching SW Download Application From Boot1"
checking hotboot: NO
Standby version 40.x.0.0
start_Init clearing m_InitDoneBlunk
Using errlib version 0.9
Errlib 0.9 registered from process 147
3562 - ReferenRW partition: 4
mounting partition 4 to jffs2 file system passed
RW partition: 5
mounting partition 5 to jffs2 file system passed
mounted: </dev/mtdblock6>
Mount check passes, 0 iterations
mounted: </dev/mtdblock7>
Mount check passes, 0 iterations
pffsN_OnMounted sets m_InitDoneBlunk to true
InitCehtvData done
ReadCehtvData ConfigVersion: [0.01] OK
ReadCehtvData ProductID: [Q591E] OK
ReadCehtvData OUI: [0000903E] OK
ReadCehtvData HardwareModel: [0203] OK
ReadCehtvData HardwareVersion: [0100] OK
ConvertAscii2Bin started
ConvertAscii2Bin done
ConvertAscii2Bin started
ConvertAscii2Bin done
ReadCehtvData PublicKey: OK
ReadCehtvData done, ConfigOK: TRUE
Could allocate 36701184.
Startup m_InitDoneBlunk: 1, m_InitDoneMain: 1
/mnt/jffs0/rupg/tvplf/cetv/display found - Layoutcheck OK
Display flash file : Layout version = 8 ; Contentversion = 17
Display flash file : Project Id = 1 ; Branch Id = 0
version string: DISPT_001.000.008.017
Using screen option 142, name LCD LGD WUF SAA1 42"
MMIO address obtained from pnx5xxx drv = 0x28000000
redirecting 1 to 22
00 005.181 redirecting 2 to 23
00 005.185 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnknownAttachedError, -1 )" notification given
00 005.187 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnknownAttachedError, -1 )" notification given
00 005.188 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnknownAttachedError, -1 )" notification given
00 005.190 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnknownAttachedError, -1 )" notification given
00 005.192 ***GVC: T2 - ceisusb_m.c (817): "usbdevspN_OnPhysicalDeviceConnected( 0 )" notification given...
00 005.364 startr_init
00 005.364 Startup m_InitDoneBlunk: 1, m_InitDoneMain: 1
00 005.465 gfxptr: 2dea0000
00 005.465 malloc 776605704
00 005.465 Starting STi710x device with i2c protocol version v0.5 !
00 005.471 ST TurnOn first attemptS18,0,Q591E_0.39.0.0
00 005.806 Go!!!!!!!
00 005.910 Por: 1
00 005.920 ST start up OKST SW Version: MPEG4.001.000.000.029
00 005.930 ST HW Version: MP4HW.000.000.012.002
00 005.932 Amount of upgs on usb 0
00 005.934 No upg files found!
00 009.212 ***GVC: T2 - ceisusb_m.c (1199): "usbdevspN_OnNewDevice( 0 )" notification given.
00 009.297 ***GVC: T2 - ceisusb_m.c (1408): "usbdevspN_OnDriveMounted( 0 )" notification given
00 009.299 OnDriveMounted : 0
00 009.586 ceapps OnUpgradesChanged : 0
00 009.594 Amount of upgs on usb 20
00 009.854 20 upgs found on USB. Press right to enter the list.
I_17662_003.eps
110608
Figure 5-17 Example UART log during SWUPG startup (DVD down).
EN 47Q529.1E LC5.
Page 48
EN 48Q529.1E LC5.
UªUretail Jan 16 2008 12:03:04
Boot deviceST NAND512W3A
BFFS init
OK
Searching BootLoader.tdfLoad /bffs0/BootLoader.tdf- Done
Start /bffs0/BootLoader.tdf
JBL (boottime improvement
BootLoader OS_R0.7.2assert Feb 25 2008 12:49:28Searching boot.bat
Execute /bffs2/boot.bat from label [1]
* SR1->Coldboot
* On error goto 60
* Load /bffs2/atvTm0App.tdf - ok
* Load /bffs3/tmpvbPnx51xxApp.tdf - ok
* Load /bffs2/cdDownloadTM0.tdf - ok
* Starting earlyStartTM* Load /bffs3/tmvprPnx51xxCoApp_tm2.tdf - ok
* Load /bffs3/tmvprPnx51xxCoApp_tm3.tdf - ok
* Load /bffs2/Kernel.tdf - ok
* MemFill 0x87fff000 0x1000 0xff
* Signal 30
* Cmd Line
CMD_LINE arguments passed by JBL : console=ttyS0,38400n8 mem=48M kgdb=ttyS1 l
oglevel=3 root=/dev/mtdblock5 lpj=1196032 init=/init ip=none jffs2_gc_delay=30
* Start /bffs2/Kernel.tdf"htv520EU/92 startup script ..."
"Mounting file systems"
Total usertime mount for /proc: 0,000000 [Sec]
Total systemtime mount for /proc: 0,000000 [Sec]
Total usertime mount for /sys: 0,000000 [Sec]
Total systemtime mount for /sys: 0,000000 [Sec]
Total usertime mount for /dev/shm: 0,000000 [Sec]
Total systemtime mount for /dev/shm: 0,000000 [Sec]
Total usertime mount for /dev/pts: 0,000000 [Sec]
Total systemtime mount for /dev/pts: 0,010000 [Sec]
"Mounting the flash file systems"
Total usertime mount for /mnt/jffs0: 0,000000 [Sec] _______> Mount time for JFFS partitions
Total systemtime mount for /mnt/jffs0: 0,080000 [Sec]
"Loading PNX5100 Image"
"Launching TV application"
------------------------------------------ Here TV Application is starting up ---------------------Using errlib version 0.9
Errlib communication with plfapp failed, will retry later
redirecting 1 to 14
00 002.414 128MB memory on board
00 002.414 128MB memory MAP
00 002.414 checking hotboot: NO
00 002.414 Standby version 40.x.0.0
00 002.414 start_Init clearing m_InitDoneBlunk
00 002.414 Using errlib version 0.9
00 002.414 Errlib 0.9 registered from process 118
00 002.414 2343 - Reference timestamp
00 002.414 mounted: </dev/mtdblock6>
00 002.414 Mount check passes, 0 iterations
-1 002.919 starting : /philips/apps/tveu 4 0 0
00 003.082 RU Flash file not found in /mnt/jffs0/rupg/tvplf/tv520avi/cabinet3
I_17662_004a.eps
110608
Service Modes, Error Codes, and Fault Finding
Figure 5-18 Example UART log during SWUPG startup (Normal startup) part 1.
Page 49
Service Modes, Error Codes, and Fault Finding
00 003.082 RO Flash file not found in /mnt/jffs0/ro/tvplf/tv520avi/cabinet3
00 003.082 Local flash file not found in file/cabinet3
00 003.082 RU Flash file found in /mnt/jffs0/rupg/tvplf/tv520avi/cabinet
00 003.082 Cabinet flash file : Layout version = 4 ; Content version = 16
00 003.082 Cabinet flash file : Project Id = 0 ; Branch Id = 39
00 003.082 version string: ACSTS_000.039.004.016
-1 003.182 amApp : InitDirectFB
-1 003.182 Grabbing keyboard
-1 003.182 amApp : InitSaWMan
-1 003.182 AppMan: Process added (118) [1]!
-1 003.182 AppMan: Process added (116) [2]!
-1 003.182 AppMan: Window added (0,0-1x1) [1] - 1!
00 003.304 Using cabinet option 3, name MS7_speaker_B 2K7
00 003.304 /mnt/jffs0/rupg/tvplf/cetv/pqprivate found
00 003.304 PQ private flash file : Layout version = 8 ; Content version = 0
00 003.304 PQ private flash file : Project Id = 1 ; Branch Id = 0
00 003.304 version string: PRFPV_001.000.008.000
00 003.304 /mnt/jffs0/rupg/tvplf/cetv/ambientlight found
00 003.304 Ambientlight flash file : Layout version = 3 ; Content version = 9
00 003.304 Ambientlight flash file : Project Id = 1 ; Branch Id = 0
00 003.349 version string: PRFAM_001.000.003.009i5100pow_Init
00 003.382
00 003.382 /mnt/jffs0/rupg/tvplf/cetv/pqpublic found
00 003.382 PQ public flash file : Layout version = 4 ; Content version = 2
00 003.382 PQ public flash file : Project Id = 0 ; Branch Id = 0
00 003.406 version string: PRFPB_000.000.004.002plfdmx_mdmx: DEBUG_ERROR_PRINT enabled
00 003.431 Platform Application from Apr 13 2008 22:31:30,
00 003.431 built on PC: BEQBRGBRG1TSS15 by user: beq00908
00 003.431 CCM_build_id:
00 003.431 Startup m_InitDoneBlunk: 0, m_InitDoneMain: 1
00 003.782 Check TM download idrv_DspReady_Ready
01 003.879 tvApp : entered main....
01 003.885 amApp is passing 4 arguments
01 003.890 tvApp : Param 1 = 4 Param 2 = 0
01 003.892 Tvmain: start_Init called
00 003.974 Create Thread with priority 70 (=45)
00 003.974 Create Thread with priority 70 (=45)
00 003.974 Create Thread with priority 70 (=45)
00 003.974 Create Thread with priority 70 (=45)
00 003.974 Create Thread with priority 70 (=45)
00 003.974 Create Thread with priority 70 (=45)
01 003.985 Using errlib version 0.9
00 003.988 Starting STi710x device with i2c protocol version v0.5 !
00 003.995 ST TurnOn first attemptCreate Thread with priority 70 (=45)
00 003.995 Create Thread with priority 70 (=45)
00 003.995 Create Thread with priority 70 (=45)
00 003.995 Create Thread with priority 70 (=45)
00 004.004 PNX5100: Using PCI communication for all i2c write messsages!!
00 004.007 PNX5100: Input Wdw: 1944 1104 Output Freq: 100
00 004.009 PNX5100: Input Wdw: 1944 1104 Output Freq: 120
00 004.013 Create Thread with priority 70 (=45)
00 004.015 PNX5100: Hardware Id [5100hwid]
00 004.017 Software Id [20080408]
00 004.019 BootNvm Id [ 8]
00 004.023 5100 Drv GetBootstatus via PCI : 0
00 004.038 Errlib 0.9 registered from process 164
00 004.064 TM download OK
01 004.067 (*) FusionDale/Config: Parsing config file '/etc/fusiondalerc'.
01 004.072 *--------------) FusionDale v0.1.1 (--------------*
01 004.072 (c) 2006-2007 directfb.org
01 004.072 ----------------------------------------------01 004.078 (*) Fusion/SHM: NOT using MADV_REMOVE (2.6.18.0 < 2.6.19.2)! [0x02061200]
01 004.089 (*) Direct/Thread: Running 'Fusion Dispatch' (MESSAGING, 184)...
00 004.099 Por: 1
00 004.102 ST start up OKST SW Version: MPEG4.001.000.000.029
00 004.105 ST HW Version: MP4HW.000.000.012.002
00 004.107 5100 Drv GetBootstatus via PCI : 0
00 004.112 Firmware version 3.10 for TDA10048 succesfully downloaded
00 004.263 5100 Drv GetBootstatus via PCI : 2
00 004.265 PNX5100&&&&&& Bootstatus on 2 after 2 retries
-1 004.333 AppMan: Process added (164) [3]!
00 004.445 i5100pow_TurnOn
00 004.451 phatvEngine5100Proxy__pow_TurnOn using udma driver for autotv !!gOemRegTbl:0x3292D0
00 004.508 cetvbend_mpowon: iambl_SetState onoff = 0
-1 004.517 icplfapisetup_powN_OnTvPowerChanged for state 2
01 004.702 svspow_m.c:2922::Start Init of svspow called.MsecSinceInit: 1791999581
01 004.707 svspow_m.c:2251::Wakeup Reason is coldboot
01 004.730 svspow_m.c:2954::Quick Turn On Initiated
01 004.730 svspow_m.c:1380::Double call in InitialiseSoftware
-1 005.262 Ungrabbing keyboard
01 005.267 svspow_m.c:2854::REQUEST_PS for cmd: 5
00 005.270 cetvbend_mpowon: powon_TurnOn
01 005.289 <5> 5278 ZAP_END - UnBlank GCK****************Hot key received by tvApp
01 005.289 svspow_m.c:4705::HK_PREPARE_PS received for cmd = 5
01 005.289 GCK******************Hot key prepare PS received by psc
01 005.289 svspow_m.c:4049::powctl_SetPowerMode to PscPowOn
-1 005.296 Called icplfapisetup_pow_SetTvPower( 3 )
I_17662_004b.eps
110608
Figure 5-19 Example UART log during SWUPG startup (Normal startup) part 2.
EN 49Q529.1E LC5.
Page 50
EN 50Q529.1E LC5.
-1 005.296 Sending HK_PREPARE_PS to application index 1, window 0x5132da00
01 005.315 svspow_m.c:1575::Reached SW Turn On 1
-1 005.327 icplfapisetup_powN_OnTvPowerChanged for state 3
01 005.338 svspow_m.c:1634::Reached HandleTurnOn1Event with Event = 16
01 005.342 svspow_m.c:1634::Reached HandleTurnOn1Event with Event = 1
01 005.432 RB Analog file name /mnt/jffs0/boot/tv/hysvc/HsvAntennaAnalogTable
01 005.435 RB Digts file name /mnt/jffs0/boot/tv/hysvc/HsvAntennaDigPtcTable
01 005.437 RB digsrvc file name /mnt/jffs0/boot/tv/hysvc/HsvAntennaDigSrvcTable
01 005.439 FrequecnyMap file name /mnt/jffs0/boot/tv/hysvc/HsvAntennaFreqMapTable
01 005.443 Analog file::IsImmediateFlashUpdateReqd set to:0
01 005.444 RB Analog file open Sucessfull
01 005.446 Proceed1:1
01 005.448 generating dig tables
01 005.452 digts_Open ::DigTsfp:18157056,tempval2:2
01 005.454 digts::IsImmediateFlashUpdateReqd set to:0
01 005.464 digsrvc_Open::DigSrvcfp:18157424,tempval:2
01 005.466 DigSrvcfp::IsImmediateFlashUpdateReqd set to:0
01 005.469 freqmap_Open::freqMapfp:18157792,tempval:2
01 005.471 freqMapfp::IsImmediateFlashUpdateReqd set to:0
01 005.475 ANTENNA_FLASH_ANALOG_TABLE: records:21
01 005.478 NoOfRecordsInFlash::ANTENNA_FLASH_DIG_PTC_TABLE:12
01 005.512 NoOfRecordsInFlash::ANTENNA_FLASH_DIG_SRVC_TABLE:117
01 005.514 NoOfRecordsInFlash::ANTENNA_FLASH_FREQMAP_TABLE:0
01 005.516 RB Analog file closed
00 005.519 cetvbend_mpowon: cetvambi_ambilight_Disable
01 005.526 CurrentONID = 9018
01 005.528 euins_m:Medium from NVM = 0
01 005.544 svspow_m.c:3586::cesvc powntf received for Ssby
01 005.546 svspow_m.c:1634::Reached HandleTurnOn1Event with Event = 2
01 005.573 svspow_m.c:750::Set has reached Semisby state
00 005.577 cetvbend_mpowon: iambl_SetState onoff = 0
01 005.582 cbmhgoad_mcallisto: mDownloadErrorOccured = FALSE
01 005.584 cbmhgoad_mswupdt: mScanningRequired = FALSE - mMsgArrived = 0, MsgType = 65535
01 005.586 cbmhgpow_mpow: sbyoad_IsPending = FALSE
01 005.590 svspow_m.c:1718::Reached SW Turn On 2
00 005.704 cetvbend_mpowon: iambl_SetState onoff = 0
01 005.784 cbmhgpow_mpow: selrqd_IsProgSelReqd = TRUE
01 005.792 <5> 5792 ZAP_BEGIN - SelectProgram
01 005.794 svspow_m.c:953::First Preset Seln made at 1792000672
01 005.827 svbas pgselN_OnProgramChangeRequested
00 005.844 DVB-T decoder selected
00 005.846 avptda10023_menable.c: ena_Disable()
01 005.896 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 1
00 006.059 ***Restoring Ad Routing and enable direct control
01 006.162 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 16
01 006.195 svspow_m.c:3634::cesvc powntf received for ON
01 006.197 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 2
00 006.211 ***Writing the Ad Routing parameters...
00 006.464 tmtv520avinst__vipN_OnImageFormatChanged
01 006.752 hsvprins: hsvprins__feapiN_OnStationFound
01 006.936 hsveuins_mdig.c: 2178: hsveuins__ictrlN_OnEvent:
01 006.936 sigstr_SetSigStrengthMeasured called with val = 1
00 007.131 ceplfresgate__vid_StopDemux
00 007.131 ceplfresgate__aud_StopDemux
00 007.146 ceplfresgate__pcr_StopDemux
01 007.148 Mohanan: ConvertToSTVideoType : 2
01 007.153 hsvdvbmpl : dmxmed_SetVideoPid pid 600 type 2
00 007.163 ceplfresgate__vid_StartDemux
01 007.172 Mohanan: ConvertToSTAudioType : 0x2000000
01 007.174 hsvdvbmpl : dmxmed_SetAudioPid pid 601 type 5
00 007.182 ceplfresgate__aud_StartDemux
01 007.185 hsvdvbmpl : dmxmed_SetPcrPid pid 600
00 007.191 ceplfresgate__pcr_StartDemux
00 007.191 usecase = 4
00 007.484 tmtv520avinst__vipN_OnVideoPresentChanged
00 007.486 direct ceplfresgate_vipN_OnVideoPresentChanged to 2
00 007.491 m_FieldFreq = 50tmtv520avinst__vipN_OnNumberOfVisibleLinesChanged
00 007.494 direct ceplfresgate_vipN_OnNumberOfVisibleLinesChanged
00 007.507 tmtv520avinst__vipN_OnImageFormatChanged
01 007.571 svspow_m.c:4589::First pgsel completed at 1792002449
00 007.575 cetvbend_mpowon: cetvdisplay_preheatN_OnEvent
00 007.577 cetvbend_mpowon: UpdateAmbientLight => cetvambi_ambl_SetState
01 007.587 <5> 7583 ZAP_END - UnBlank
01 007.589 svbas pgselN_OnProgramChangeCompleted
01 007.960 svspow_m.c:4753::Detected Mute = FALSE in vmtN
01 007.964 <5> 7959 ZAP_END - UnBlank
01 007.966 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 2048
01 007.968 RFS not found in environment
01 007.977 RFS not found in environment
01 007.979 FLASH system, mount request for partition 2 accepted
00 008.331 Timeout on mountcheck
01 008.692 svspow_m.c:4760::flashopN_OnPartitionMounted::partitionid:2
00 008.769 cetvbend_mpowon: cetvambi_ambilight_Disable
00 009.002 argv[0] is /philips/bin/networkhelper
00 009.002 udhcpc gave me deconfig
00 009.002 HandleUdhcpcNotif : msgq is 32769
01 009.155 svspow_m.c:4772::Sent flashopN_OnPartitionMounted::MOUNT_ON_EVENT
01 009.158 svspow_m.c:1872::gfx setpower ON
01 009.162 svspow_m.c:1875::gfx powntf for ON
01 009.164 cbmhgpow_mpow: SetPower to ON
01 009.166 cbmhgpow_mpow: OnPowerChanged
01 009.168 svspow_m.c:3428::cbmhg powntf received for ON
01 009.171 svspow_m.c:1913::cbmhg setpower On
01 009.267 svspow_m.c:1926::JUICE setpower On
01 009.279 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 16
01 009.282 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 256
-1 009.292 AppMan: Window added (0,0-852x480) [4] - 2!
01 009.298 Surface 0, PlaneId 2 in AttachSurface
00 009.989 argv[0] is /philips/bin/networkhelper
00 009.989 udhcpc gave me bound
00 009.989 udhcpc gave me bound
I_17662_004c.eps
110608
Service Modes, Error Codes, and Fault Finding
Figure 5-20 Example UART log during SWUPG startup (Normal startup) part 3.
Page 51
Service Modes, Error Codes, and Fault Finding
00 009.989 IP address is 192.168.1.22
00 009.989 subnet mask is 255.255.255.0
00 009.989 $router is 192.168.1.1
00 009.989 First Gateway is 192.168.1.1
00 009.989 $dns is 192.168.1.1
00 009.989 DNS1 is 192.168.1.1
00 009.989 Interface is eth0
00 009.989 HandleUdhcpcNotif : msgq is 32769
00 010.083 route: SIOC[ADD|DEL]RT: No such process
01 010.623 svspow_m.c:3497::juice powntf received for ON
01 010.626 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 512
01 010.641 svspow_m.c:1943::ceapps setpower On
-1 010.657 AppMan: Switch focus to 0x5132d600 [4]
00 010.702 (!!!) *** WARNING [color keying does not work on UPPER layer] *** [Philips/DirectFB/systems/cetvfb/primary.c:202 in get_color_minmax()]
01 010.868 svspow_m.c:3479::apps powntf received for ON
-1 010.881 AppMan: Window added (0,0-720x576) [5] - 0!
01 010.897 Surface 1, PlaneId 0 in AttachSurface
01 011.083 svspow_m.c:1803::Reached HandleTurnOn2Event with Event = 1024
01 011.086 svspow_m.c:693::Set Reached on state at 1792005965
01 011.088 svspow_m.c:755::Set has reached ON state
01 011.091 InitCehtvData done
01 011.312 ReadCehtvData ConfigVersion: [0.01] OK
01 011.312 ReadCehtvData ProductID: [Q591E] OK
01 011.312 ReadCehtvData OUI: [0000903E] OK
01 011.312 ReadCehtvData HardwareModel: [0203] OK
01 011.312 ReadCehtvData HardwareVersion: [0100] OK
01 011.312 ConvertAscii2Bin started
01 011.312 ConvertAscii2Bin done
01 011.312 ConvertAscii2Bin started
01 011.312 ConvertAscii2Bin done
01 011.312 ReadCehtvData PublicKey: OK
01 011.339 ReadCehtvData done, ConfigOK: TRUE
00 011.666 cetvbend_mpowon: iambl_SetState onoff = 1
00 011.668 cetvbend_mpowon: iambl_SetState onoff => cetvambi_ambl_SetState
00 011.672 cetvbend_mpowon: cetvambi_ambilight_Enable
-1 011.884 HK_PREPARE_PS_DONE received for cmd: 5, src: 1
-1 011.884 Remaining PowerChangeBitmap: 0
-1 011.884 starting : /philips/apps/spettApp
-1 011.884 starting : /philips/apps/media
01 011.905 svspow_m.c:2871::PREPARE_PS_DONE for cmd: 5
01 011.994 cbmhgpow_mpow: mRegisterAlarm - ClockSet
02 012.518 *--------------) FusionDale v0.1.1 (--------------*
02 012.518 (c) 2006-2007 directfb.org
02 012.518 ----------------------------------------------02 012.524 Using errlib version 0.9
02 012.524 ***SPETT*** FusionDale Init done
02 012.524 ***SPETT*** Windows created
00 012.530 Errlib 0.9 registered from process 226
00 012.530 *** DirectFB Surface allocation FALLBACK! Acquiring id 7 with size 376320
-1 016.098 Relayout of window 5
00 017.948 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnknownAttachedError, -1 )" notification given
00 018.154 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnknownAttachedError, -1 )" notification given
00 018.727 ***GVC: T2 - ceisusb_m.c (951): "usbdevspN_OnDeviceError( DeviceUnknownAttachedError, -1 )" notification given
00 024.079 --- pass 0 --00 024.082 freeMem : 26620
00 024.084 pgmajfault : 0
00 024.086 sectorsread: 11440
01 035.636 Merging eit data
01 035.650 Merging eit data
01 035.656 1419 records after eliminating duplicates
01 035.663 1419 records after eliminating duplicates
I_17662_004e.eps
110608
Service Modes, Error Codes, and Fault Finding
Figure 5-22 Example UART log during SWUPG startup (Normal startup) part 5.
•The “Application selection startup” part in the logs shows
which application is being started up: backup SWUPG,
normal SWUPG, TV application, …
•In the TV application (Normal startup) case, there is no
print on the UART which shows the software has started up
completely. When startup issues arise, the best way to
tackle them is by comparing the bad UART print with a
correct print of the same release.
Upgrade of a TV set.
Following cannot be seen during industrial mode!
•When the Industrial Mode is enabled with command 203,
no prints can be seen anymore on the UART. This is to not
interfere with the P2P protocol.
•When in normal mode, the UART will show what the
actions are during the upgrade.
•At certain periods in time during programming, the total
size currently flashed (Totalsize flashed) and the size
which should be finally flashed (TotalProgramSize) will be
printed.
Page 53
Service Modes, Error Codes, and Fault Finding
13:51:07 Tv520_Eu_0.61_prod <--- Upgrade now
13:51:11
13:51:11
13:51:11 Software is equal or older,
13:51:11 - press OK to stop
13:51:11 - press down + OK to continue
13:51:11
13:51:12 L: 13%
13:51:15 L: 94%
13:51:16 V: 1%
13:51:29 V: 98%
13:51:30 P: 0%
13:51:31 P: 0%
13:51:31 /data/rupg/* is being scanned for size
13:51:31 current flashsize: 7949008:
13:51:31 current flashsize: 8006889:
13:51:31 current flashsize: 8016293:
13:51:31 /data/rw/* is being scanned for size
13:51:31 current flashsize: 8016309:
13:51:31 /squash/* is being scanned for size
13:51:31 current flashsize: 15196597:
13:51:31 /bffs2/* is being scanned for size
13:51:31 current flashsize: 15208584:
13:51:31 current flashsize: 15208658:
13:51:31 current flashsize: 19590958:
13:51:31 current flashsize: 21687842:
13:51:31 current flashsize: 22703738:
13:51:31 current flashsize: 24080366:
13:51:31 m_JffsMounted = 3
13:51:31 Sync called
13:51:31 Sync DONE
13:51:31 CheckUnMount: /mnt/jffs0
13:51:31 /mnt/jffs0 is mounted
13:51:31 Unmount /mnt/jffs0
13:51:31 /mnt/jffs0 is not mounted
13:51:31 umounting /mnt/jffs0 ok
13:51:31 umounting partition 4 from jffs2 file system passed
13:51:31
13:51:31 Sync called
13:51:31 Sync DONE
13:51:31 CheckUnMount: /mnt/jffs1
13:51:31 /mnt/jffs1 is mounted
13:51:31 Unmount /mnt/jffs1
13:51:31 /mnt/jffs1 is not mounted
13:51:31 umounting /mnt/jffs1 ok
13:51:31 umounting partition 5 from jffs2 file system passed
13:51:31 FORMAT 2
13:51:31 Totalsize flashed: 0, TotalProgramSize: 24080366
13:51:31 m_JffsMounted = 0
13:51:31 P: 0%
13:51:32 P: 0%
13:51:32 P: 0%
13:51:33 P: 0%
13:51:33 Format succesfull ____________> Format 2 (bffs2 partition) succesfull
13:51:33 Totalsize flashed: 0, TotalProgramSize: 24080366
13:51:33 m_JffsMounted = 0
13:51:33 P: 0%
13:51:33 FORMAT 3 ____________> Format 3 (Squash partition) succesfull
13:51:33 Totalsize flashed: 0, TotalProgramSize: 24080366
13:51:33 m_JffsMounted = 0
13:51:33 spawning flash_eraseall
13:51:33 param: flash_eraseall
13:51:33 param: -q
13:51:33 param: /dev/mtd5
13:51:33 P: 0%
13:51:34 P: 0%
13:51:34 P: 0%
13:51:34 status: 1 ,erasing partimage partition succesfull
13:51:34 Totalsize flashed: 0, TotalProgramSize: 24080366
13:51:34 m_JffsMounted = 0
13:51:34 P: 0%
13:51:34 /data/rupg/
13:51:34 Totalsize flashed: 0, TotalProgramSize: 24080366
13:51:34 m_JffsMounted = 0
13:51:34 JFFS found to write /data/rupg/ceapps ________> Writing to JFFS
13:51:35 mounting partition 4 to jffs2 file system passed
13:51:35
13:51:35 Totalsize flashed: 0, TotalProgramSize: 24080366
13:51:58 m_JffsMounted = 1
13:51:58 Sync called
13:51:58 Sync DONE
13:51:58 CheckUnMount: /mnt/jffs0
13:51:58 /mnt/jffs0 is mounted
13:51:58 Unmount /mnt/jffs0
13:51:58 /mnt/jffs0 is not mounted
13:51:58 umounting /mnt/jffs0 ok
13:51:58 umounting partition 4 from jffs2 file system passed
13:51:58
13:51:58 P: 31%
13:51:58 /data/rw/
13:51:58 Totalsize flashed: 8016293, TotalProgramSize: 24080366
13:51:58 m_JffsMounted = 0
13:51:58 JFFS found to write /data/rw/cehtv ________> Writing to JFFS
I_17662_005a.eps
110608
Figure 5-23 Example UART log during normal user upgrade part 1.
EN 53Q529.1E LC5.
Page 54
EN 54Q529.1E LC5.
13:51:58 P: 31%
13:51:59 P: 31%
13:51:59 mounting partition 5 to jffs2 file system passed
13:51:59
13:51:59 Totalsize flashed: 8016293, TotalProgramSize: 24080366
13:51:59 m_JffsMounted = 2
13:51:59 Sync called
13:51:59 Sync DONE
13:51:59 CheckUnMount: /mnt/jffs1
13:51:59 /mnt/jffs1 is mounted
13:51:59 Unmount /mnt/jffs1
13:51:59 /mnt/jffs1 is not mounted
13:51:59 umounting /mnt/jffs1 ok
13:51:59 umounting partition 5 from jffs2 file system passed
13:51:59
13:51:59 P: 31%
13:51:59 WRITE /squashFS/ ________> Writing to Squash
13:51:59 Totalsize flashed: 8016309, TotalProgramSize: 24080366
13:51:59 m_JffsMounted = 0
13:51:59 v1 squash
13:51:59
13:51:59 Totalsize flashed: 8016309, TotalProgramSize: 24080366
13:51:59 spawning nandwrite
13:51:59 param: nandwrite
13:51:59 param: -z
13:51:59 param: 7180288
13:51:59 param: /dev/mtd5
13:51:59 param: /philips/pipe
13:51:59 execute nandwrite OK
13:51:59 Writing data to block 0
13:51:59 P: 31%
13:51:59 Writing data to block 4000
13:52:09 /philips/pipe could is closed ________> Finished writing to Squash
13:52:09 m_JffsMounted = 0
13:52:10 P: 63%
13:52:10 WRITE /bffs2/ ________> Writing to bffs2
13:52:10 Totalsize flashed: 15196597, TotalProgramSize: 24080366
13:52:10 m_JffsMounted = 0
13:52:10 Totalsize flashed: 15196597, TotalProgramSize: 24080366
13:52:32 Totalsize flashed: 24080366, TotalProgramSize: 24080366
13:52:32 Completed !! ________> Programming succesfull
13:52:32 Operation Successful! Remove all inserted media and restart the TV set.
I_17662_005b.eps
110608
Service Modes, Error Codes, and Fault Finding
Figure 5-24 Example UART log during normal user upgrade part 2.
Problem analysis of a TV set.
During programming:
•The amount of Bad Blocks is bigger then promised by the
•Bad blocks have been created during programming and
•Mounting of the JFFS partitions take to long.
•When the flashutil UPG is being programmed on a boards
•When the power drops the programming will be stop.
•If a development UPG is used on a production SWUPG or
•If loading fails (cannot read file error), it is mostly due to a
•If the UPG size is bigger then the memory allocated by the
flash manufacture. This is checked on virgin boards.
there is not enough good block anymore in the partition to
write data into. This can happen on boards which are being
reprogrammed.
which already contains a different Partition Table, the
writing of the bootblock (μBTM and partitionTable ) will fail.
This can only happen on non virgin boards.
Depending on when the power drop is the result will be
different.
1. FUS UPG. The SWUPG will try to reprogram the UPG
once the power is back.
2. Flashutil UPG. Cannot recover anymore, because
nothing is in flash anymore. Has to be reprogrammed
on the line again.
3. Upgrade All. Depending when the power drop
happens. When it happens in the beginning, the board
will only be reprogrammable on the line.
visa versa. Validation will fail.
long USB cable or a bad USB stick.
software upgrade application, then the UPG will not be
programmed. See the prints fo the SWUPG at startup.
During startup:
•Compare the UART logging on the problem board/set with
a normal startup behaviour. Identify till which point the
logging reaches.
•If a crash happens, it will be outputted on the UART. In the
background the information of the dump will be written into
JFFS0. The UPG to copy the dump content out of flash
should be available for everybody.
Page 55
Service Modes, Error Codes, and Fault Finding
13:47:58 Debug dump 000000: Fatal error: time = N/A, millis = 127020, error = test reboot, SW version = Q581E
13:47:58 -0.61.0.0 Release
13:47:59 Unmounting jffs2 filesystems
13:47:59 Unmounting </mnt/jRestarting system.
13:47:59 ffs1>
13:47:59 UnmountinBUG: scheduling with irqs disabled: htv520eu/0x00000000/147
13:47:59 g </mnt/jffs0>
13:47:59 ehci_hcd 0000:00:0b.2: dma_pool_destroy ehci_qtd, a12b4000 busy
13:47:59 ehci_hcd 0000:00:0b.2: dma_pool_destroy ehci_qh, a188e000 busy
13:48:05
13:48:05
13:48:06 uBTM NDK R5.2b retail Feb 7 2007 11:56:37
13:48:06 Boot device - ST NAND512W3A
13:48:06 BootFFS initialization - OK
13:48:06 uBTM has been enabled with ECC
13:48:06 Searching BootLoader.tdf
13:48:06 File System ID is BFFS_ID
13:48:06 Loading /bffs0/BootLoader.tdf-Done
13:48:06
13:48:06 Starting /bffs0/BootLoader.tdf
13:48:06 JBL enabled with ECC check
13:48:06
13:48:06 Initialize I2C module
I_17662_006.eps
110608
Figure 5-25 Example UART log during problem.
Problem solution.
When programming fails:
•Check in the NVM at address 0x1D02 (BadBlocksAmount).
This items is 2 bytes.
1. If, after programming the flashutil UPG, this value is
still the same as the one of the process NVM, then the
amount of bad blocks was bigger then described by the
flash manufacturer.
2. If the value is filled in, it has to be checked if it's not to
close the maximum amount possible.
3. If the value is low, no problem.
•If mounting fails, it will be shown on the UART. This can
only be seen when industrial mode is disabled.
•As the UART logs are disabled when in industrial mode, it
is always good to have a set (or minimal setup) where the
problem board can be tested in. In this way the problem
can be reproduced in the normal mode of the SWUPG and
the prints will be visible!
EN 55Q529.1E LC5.
When startup fails:
•When a crash happens (only in the TV application!) and is
followed by debug dump UART output, then a copy of the
dump can put on a USB stick
1. This can only be done in the TV application, so if the
TV application keeps on crashing there is no way to
copy the dump of the flash to a USB stick.
2. When the TV application has started up completely,
CSM can be entered by pressing 1, 2, 3, 6, 5, 4.
3. Then put the remote in DVD mode and press 2, 6, 7, 9.
4. The file Dump_seetypeplate_seetypeplate.bin can be
found now on the USB storage device. The
seetypeplate_seetypeplate will be filled in depending
on the type of set.
5. This .bin file can only be interpreted in a Philips
development centre. Please give this input to your
Philips Service contact person.
•Compare the UART logging on the problem board/set with
a normal startup behaviour. Identify till which point the
logging reaches.
Page 56
EN 56Q529.1E LC5.
Personal Notes:
E_06532_012.eps
131004
Service Modes, Error Codes, and Fault Finding
Page 57
Block Diagrams, Test Point Overview, and Waveforms
6.Block Diagrams, Test Point Overview, and Waveforms
Wiring Diagram Essence
WIRING E SSENCE
57Q529.1E LC6.
IPI
LC D DISPLAY
8 152
8120
1M71
7P
1319
8319
1M20
9P
1319
14P
1FDP
20P
DISPLAY
SOCKET
1F51
51P
M
(1004)
1F52
41P
MONITOR
(1032)
13DP
8P
POWER
SOCKET
8 150
1735
1316
12P
1E06
3P
UART
4P
8 735
1316
8316
IPI
1M201M01
IR LED PANEL
J
(1132)
RL
(1132)
DISPLAY LINK CABLE
8000
8 150
8 151
1F42
41P
DISPLAY
SOCKET
1FDP
20P
1G5 0
41P
1F41
51P
1G5 0
51P
LD
1M71
4P
LVDS2DP
(1030)
8 405
POWER SOCET
1F01
3P
B
8395
1M95
11P
SSB
(1011)
X419
8P
X416
11P
1M20
9P
G
1E99
30P
I/O
(1026)
1E99
30P
A
8 408
8 199
1T99
PSU
(1050)
KEYBOARD CONTROL
E
(1010)
1M01
9P
8 101
Side IO
Back IO
I_18020_125.eps
101008
Page 58
Block Diagrams, Test Point Overview, and Waveforms