Philips BJ2.4U Service Manual

Service Modes, Error Codes, and Fault FindingEN 36 BJ2.4U/BJ2.5U PA5.Extra Info• Rebooting. When a TV is constantly rebooting due tointernal problems, most of the time no errors will be loggedor blinked. This rebooting can be recognized via a ComPairinterface and Hyperterminal (for Hyperterminal settings,see paragraph “Stand-by software upgrade). You will seethat the loggings which are generated by the main softwarekeep continuing. In this case (rebooting) diagnose has tobe done via ComPair.• Error 1 (I2C bus 1 blocked). When this error occurs, theTV will go to protection and the front LED will blink error 1.Now you can partially restart the TV via the SDM shortcutpins on the SSB. Depending on the software version it ispossible that this error will not work correct: in somesoftware versions error 34 was blinking in stead of error 1.• Error 2 (I2C bus 2 blocked). When this error occurs, theTV will go to protection and the front LED will blink error 2.Now you can partially restart the TV via the SDM shortcutpins on the SSB. Due to hardware restriction (I2 C bus 2 isthe fast I2 C bus) it will be impossible to start up the VIPER.When this error occurs, the TV will probably keeprebooting. Further diagnose has to be done via ComPair.• Error 3 (I2C bus 3 blocked). There are only three deviceson I 2 C bus 3: VIPER, Stand-by Processor, and NVM. TheStand-by Processor is the detection device of this error, sothis error will only occur if the VIPER or the NVM is blockingthe bus. This error will also blink when the NVM gives noacknowledge on the I 2 C bus (see error 44). Note that if the12 V supply is missing, the DC/DC supply on the SSB willnot work. Therefore the VIPER will not get supplies andcould block I2C bus 3. So, a missing 12 V can also lead toan error 3.• Error 4 (I2C bus 4 blocked). When this error occurs, theTV will go to protection and the front LED will blink error 4.Now you can start up the TV via the SDM short-cut pins onthe SSB. The TV will start up and ignore the error.Depending on the problem it is even possible that you havepicture.• Error 5 (Viper does not boot). This error will point to asevere hardware problem around the VIPER (supplies notOK, VIPER completely dead, I2 C link between VIPER andStand-by Processor broken, etc....).• Error 12 (12 V error). Except a physical problem with the12 V itself, it is also possible that there is something wrongwith the Audio DC Protection: see paragraph "HardwareProtections" for this.• Error 14 (Audio protection). The detection is done on theaudio board itself. Several items are monitored:overvoltage, overcurrent, audio supply voltages and theDC level on the speakers. If one of these items fails, theaudio protection will switch “off” the main supply. Allsupplies will drop, the standby processor “thinks” there is amains dip, and will reboot. At the beginning of the bootprocess, the audio-protection line is monitored: if this line is“active”, the set will go to protection and will blink error 14.• Error 27 (PNX2015 HD subsystem part). Diagnosing thiserror will not be possibly via the normal error codes. In casethis device can not communicate with the Viper via I²C, itwill not be possible to initialize the tunnelbus. Hence thesoftware will not be able to start up, and will re-bootconstantly. Diagnosing these problems will only bepossible via ComPair. In theory it is possible that the erroris logged in the NVM (that’s why this error is still mentionedhere).• Error 16. See remark for error 32.• Error 17. See remark for error 32.• Error 18(MPIF1). See also remark for error 32.• Error 29 (AVIP 1). Same remark as for error 27.• Error 31 (AVIP 2). Same remark as for error 27.• Error 32 (MPIF1). Together with error 32, it is possible youwill see error 16,17 and 18 along. These errors are nolonger valid.• Error 34 (Tuner 1). When this error is logged, it is not surethat there is something wrong with the tuner itself. It is alsopossible that there is something wrong with thecommunication between channel decoder and tuner. Seeschematic B2B.• Error 37 (Channel decoder). This error will always logerror 34 (tuner) extra. This is due to the fact that the tunerI 2 C bus is coming from the channel decoder.• Error 44 (NVM). This error will probably never occurbecause it is masked by error 3 (I2 C bus 3). The detectionmechanism for error 3 checks on an I 2 C acknowledge ofthe NVM. If NVM gives no acknowledge, the stand-bysoftware assumes that the bus is blocked, the TV goes toprotection and error 3 will be blinking.• Error 46 (Pacific 3). When this errors occurs the TV will goto stand-by. The reason for this is, when there is anoccasional boot problem of the Pacific, it will look like theTV has started up in stand-by mode, and the customer canswitch it "on" again. When there is an actual problem withor around the Pacific the TV will go to stand-by every timeyou try to start up. So this behavior is an indication of aPacific problem.• Error 53. This error will indicate that the VIPER has startedto function (by reading his boot script, if this would havefailed, error 5 would blink) but initialization was nevercompleted because of hardware peripheral problems(NAND flash, ...) or software initialization problems.Possible cause could be that there is no valid softwareloaded (try to upgrade to the latest main software version).Note that it takes 90 seconds before the TV goes toprotection in this case.• Error 63 (POWER OK). When this error occurs, it meansthat the POWER-OK line did not became “high”. This erroris only applicable for TV’s with a SDI display, a FHP displayor a Sharp full HD display. Depending on the softwareversion it is possible that the detection mechanism of thiserror does not function and that the TV keeps rebooting.5.6 The Blinking LED Procedure5.6.1 IntroductionThe blinking LED procedure can be split up into two situations:• Blinking LED procedure in case of a protection detected bythe stand-by processor. In this case the error isautomatically blinked. This will be only one error, namelythe one that is causing the protection. Therefore, you donot have to do anything special, just read out the blinks. Along blink indicates the decimal digit, a short blink indicatesthe units.• Blinking LED procedure in the “on” state. Via thisprocedure, you can make the contents of the error buffervisible via the front LED. This is especially useful for faultfinding, when there is no picture.When the blinking LED procedure is activated in the “on” state,the front LED will show (blink) the contents of the error-buffer.Error-codes > 10 are shown as follows:1. “n” long blinks (where “n” = 1 - 9) indicating decimal digit,2. A pause of 1.5 s,3. “n” short blinks (where “n”= 1 - 9),4. A pause of approx. 3 s.5. When all the error-codes are displayed, the sequencefinishes with a LED blink of 3 s,6. The sequence starts again.Example: Error 12 9 6 0 0.After activation of the SDM, the front LED will show:1. 1 long blink of 750 ms (which is an indication of the decimaldigit) followed by a pause of 1.5 s,2. 2 short blinks of 250 ms followed by a pause of 3 s,3. 9 short blinks followed by a pause of 3 s,4. 6 short blinks followed by a pause of 3 s,5. 1 long blink of 3 s to finish the sequence,6. The sequence starts again.