Philips 32PFL9603D/10 Service Manual page 43

Service Modes, Error Codes, and Fault Finding
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/
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
13:52:09 m_JffsMounted = 0
13:52:10 P: 63%
13:52:10 WRITE /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 !!
13:52:32 Operation Successful! Remove all inserted media and restart the TV set.
Problem analysisof a TV set.
During programming:
• The amount of Bad Blocks is bigger then promised by the
flash manufacture. This is checked on virgin boards.
• Bad blocks have been created during programming and
there is not enough good block anymore in the partition to
write data into. This can happen on boards which are being
reprogrammed.
• Mounting of the JFFS partitions take to long.
• When the flashutil UPG is being programmed on a boards
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.
• When the power drops the programming will be stop.
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.
• If a development UPG is used on a production SWUPG or
visa versa. Validation will fail.
• If loading fails (cannot read file error), it is mostly due to a
long USB cable or a bad USB stick.
• If the UPG size is bigger then the memory allocated by the
software upgrade application, then the UPG will not be
programmed. See the prints fo the SWUPG at startup.
Figure 5-24 Example UART log during normal user upgrade part 2.
Q529.1E LA
________> Writing to Squash
________> Finished writing to Squash
________> Writing to bffs2
________> Programming succesfull
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.
5. EN 43
I_17662_005b.eps
110608