Blaupunkt 50" LED TV firmware please

[notallbad]

Re: Blaupunkt 50" LED TV firmware please

Yes I believe it is the correct board though would be useful to know whats on the reverse side of the board.

[vinceroger69]

Re: Blaupunkt 50" LED TV firmware please

i wonder if yokoono or diah can offer any help as into why the firmware update is not working on your tv it should be the correct files as direct from umc etc odd its still boot looping though.

[notallbad]

Re: Blaupunkt 50" LED TV firmware please

It was necessary to provide the Serial number from the label on the rear of the tv, the file received was only 34.3mb.

[vinceroger69]

Re: Blaupunkt 50" LED TV firmware please

It was necessary to provide the Serial number from the label on the rear of the tv, the file received was only 34.3mb.

you got the set sorted? i wonder if that was just like a software upgrade and not the full firmware files you need

[notallbad]

Re: Blaupunkt 50" LED TV firmware please

No, still not fixed.
Just stating what I provided for the file.

[R_J]

Re: Blaupunkt 50" LED TV firmware please

I suspect the data you changed in the service menu is stored elsewere,(maybe in the same nand/spi/eeprom) and upgrading or replacing the firmware is not changing that data. That way when firmware is upgraded, important data is not changed.

[notallbad]

Re: Blaupunkt 50" LED TV firmware please

I have at least now managed to connect via Usb-Uart, but what I do now is a mystery.
Connecting with a blank USB stick gets the filenames its looking for...worth noting for future reference.
FAC_BOOT_6308.cvt
AllUpgrade_6308RTEC.bin
AllUpgrade_6308_SOS.bin

"BIST0-OK
[123456789A][123456789A][123456789AB][123456789A]-5565
U[AT][MB][start ub][620]

U-Boot 2011.06-svn8303 (Sep 13 2014 - 11:34:21)

DRAM: 256 MiB

Hello U-Boot
Stack Pointer at: 87e84440
uboot held at [8f000000~90000000]
Now running in RAM - U-Boot at: 871f0180
NAND: DMA MODE
[NC_Init] SDR NAND is detected
CIS is found @Blk0
FCIE is set to 54MHz
128 MiB
*** Warning - set default for mtdparts, using default environment

Creating 1 MTD partitions on "nand0":
0x000000640000-0x000000840000 : "mtd=2"
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
UBI: attaching mtd1 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: attached mtd1 to ubi0
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 2 MiB
UBI: number of good PEBs: 16
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 250
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 1
UBI: total number of reserved PEBs: 15
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 1972/1944
Volume not found!

NAND read: device 0 offset 0x1c0000, size 0xa8
168 bytes read: OK
Volume "MPOOL" found at volume id 0
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Set MAC default
MAC: 0x0: 0x30: 0x1b: 0xba:0x2: 0xdb
It's the last cmd
<NULL>
No recovery information, needless to recovery

Changelist: 00112233
============= set bootargs ===============
Hit any key to stop autoboot: 0
AC on
Check USB port[0]:
No USB is connecting
usb init failed
Error, couldn't init Lowlevel part
Check USB port[1]:
Host type:2
scanning bus for devices...
[USB] interface[0] conf:1 value 8:
1 USB Device(s) found
scanning bus for storage devices... bulk max packet size: ep 200 ep2 200
max lun:0
1 Storage Device(s) found
** Partition 0 not valid on device 0 **

** Unable to use usb 0:0 for fatload **
reading FAC_BOOT_6308.cvt

** Unable to read "FAC_BOOT_6308.cvt" from usb 0:1 **
** Partition 2 not valid on device 0 **

** Unable to use usb 0:2 for fatload **
** Partition 3 not valid on device 0 **

** Unable to use usb 0:3 for fatload **
** Partition 4 not valid on device 0 **

** Unable to use usb 0:4 for fatload **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **
** Partition 0 not valid on device 0 **

** Unable to use usb 0:0 for fatload **
reading AllUpgrade_6308RTEC.bin

** Unable to read "AllUpgrade_6308RTEC.bin" from usb 0:1 **
** Partition 2 not valid on device 0 **

** Unable to use usb 0:2 for fatload **
** Partition 3 not valid on device 0 **

** Unable to use usb 0:3 for fatload **
** Partition 4 not valid on device 0 **

** Unable to use usb 0:4 for fatload **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **
** Partition 0 not valid on device 0 **

** Unable to use usb 0:0 for fatload **
reading AllUpgrade_6308_SOS.bin

** Unable to read "AllUpgrade_6308_SOS.bin" from usb 0:1 **
** Partition 2 not valid on device 0 **

** Unable to use usb 0:2 for fatload **
** Partition 3 not valid on device 0 **

** Unable to use usb 0:3 for fatload **
** Partition 4 not valid on device 0 **

** Unable to use usb 0:4 for fatload **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

** Invalid boot device **

UART BUS OFF!!
mapi_uartdebug::Start 0x0 UartDebug_Start now here"

[notallbad]

Re: Blaupunkt 50" LED TV firmware please

What I need to work out is how to change uart debug to off in Service Mode in debug mode.

[notallbad]

Re: Blaupunkt 50" LED TV firmware please

Well, decided to order another board so at least its up and running again. Eliminates power bd and panel etc..
Accessing terminal via uart I am able to do nandbin, nandbin2 & nandbinall which gives me
CIS_BFN.BIN
KL.BIN
MBOOT.BIN
MBOOTBAK.MBO
NAND.BIN
NAND.DEF (only 1kb?)
PART1.BIN
RTPM.BIN
UBI.BIN
UBILD.BIN
UBIRO.BIN

Can these be used to create an .img file to recover the old board? or is there a way to create the restore .img file that I'm missing?

Meanwhile I have ordered some parts to hack up an interface to the tsop48 nand in-circuit to attempt a dump to flash to the old board.

[Hypercool]

Re: Blaupunkt 50" LED TV firmware please

Was interested to know what happened next, I have same TV but a weird problem ithink capacitor may have gone weak since it takes turning it on about 10 times for it to stay on and number of times seems to be increasing day by day , started to leave it on all night in radio mode, now it turned off and won't stay on beyond the logo, and doesn't get to blue screen if no signal

[nomoresonys]

Re: Blaupunkt 50" LED TV firmware please

check the electrolytic capacitors near the connector on powerboard, the one with the cable from powerboard to mainboard, maybe one or more bad/weak, also check all your solder joints on the underside of board, examples of bad joints there: https://www.google.com/search?q=bad+...ih=607&dpr=1.5