Hi,
I need some help with a Philips 37PFL8605 board. TV has no image and gives error 53. Voltages are all ok. If i connect a uart it gives the below output.
FSBL-CI+ 550 (007)TLB-DONE
FLASH RESET
SECUREBOOT-ENABLED
U▒U
UBOOT-OK1
U-Boot 2009.01_Production (Jul 05 2010 - 11:09:21)
DRAM: 512 MB
NAND: 512 MiB
Bad block table found at page 262080, version 0x02
Bad block table found at page 262016, version 0x02
ECC failed step 0
nand_bbt: ECC error while reading bad block table
nand_read_bbt: Bad block at 0x000c0000
nand_read_bbt: Bad block at 0x005c0000
nand_read_bbt: Bad block at 0x00c80000
< lots of the same lines of errors here 3 or 4 pages>
nand_read_bbt: Bad block at 0x1fec0000
nand_read_bbt: Bad block at 0x1ffe0000
.Env: NAND @ 0x00580000
In: serial
Out: serial
Err: serial
Model: M1 (a1530100)
bootcmd1
BOOTREASON=coldboot
Sending: 00 04 00 02 05 00
Sending: 00 04 00 02 05 01
Creating 1 MTD partitions on "NAND 512MiB 3,3V 8-bit":
0x00b00000-0x07980000 : "mtd=2"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI warning: init_volumes: static volume 0 misses 4 LEBs - corrupted
UBI warning: init_volumes: static volume 1 misses 15 LEBs - corrupted
UBI error: init_volumes: not enough PEBs, required 844, available 841
UBI error: ubi_wl_init_scan: no enough physical eraseblocks (-3, need 1)
UBI error: ubi_init: cannot attach mtd0
UBI error: ubi_init: UBI error: cannot initialize UBI, error -12
UBI init error -12
My first guess was that the NAND had so many badblocks it had no longer enough room to create the MTD partition. So i made a dump of the original nand and wrote it back to a new NAND chip. However i have exact same problem. If i check the original nand on bad blocks then there are only a few. No i am wondering if the error is maybe about another flash device.
So maybe someone can explain a bit better what happens here. I assume it is still running in bootloader. Also maybe someone has a known working nand image.
Regards
Arnold
I need some help with a Philips 37PFL8605 board. TV has no image and gives error 53. Voltages are all ok. If i connect a uart it gives the below output.
FSBL-CI+ 550 (007)TLB-DONE
FLASH RESET
SECUREBOOT-ENABLED
U▒U
UBOOT-OK1
U-Boot 2009.01_Production (Jul 05 2010 - 11:09:21)
DRAM: 512 MB
NAND: 512 MiB
Bad block table found at page 262080, version 0x02
Bad block table found at page 262016, version 0x02
ECC failed step 0
nand_bbt: ECC error while reading bad block table
nand_read_bbt: Bad block at 0x000c0000
nand_read_bbt: Bad block at 0x005c0000
nand_read_bbt: Bad block at 0x00c80000
< lots of the same lines of errors here 3 or 4 pages>
nand_read_bbt: Bad block at 0x1fec0000
nand_read_bbt: Bad block at 0x1ffe0000
.Env: NAND @ 0x00580000
In: serial
Out: serial
Err: serial
Model: M1 (a1530100)
bootcmd1
BOOTREASON=coldboot
Sending: 00 04 00 02 05 00
Sending: 00 04 00 02 05 01
Creating 1 MTD partitions on "NAND 512MiB 3,3V 8-bit":
0x00b00000-0x07980000 : "mtd=2"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI warning: init_volumes: static volume 0 misses 4 LEBs - corrupted
UBI warning: init_volumes: static volume 1 misses 15 LEBs - corrupted
UBI error: init_volumes: not enough PEBs, required 844, available 841
UBI error: ubi_wl_init_scan: no enough physical eraseblocks (-3, need 1)
UBI error: ubi_init: cannot attach mtd0
UBI error: ubi_init: UBI error: cannot initialize UBI, error -12
UBI init error -12
My first guess was that the NAND had so many badblocks it had no longer enough room to create the MTD partition. So i made a dump of the original nand and wrote it back to a new NAND chip. However i have exact same problem. If i check the original nand on bad blocks then there are only a few. No i am wondering if the error is maybe about another flash device.
So maybe someone can explain a bit better what happens here. I assume it is still running in bootloader. Also maybe someone has a known working nand image.
Regards
Arnold
Comment