Aya A39FHD3901/2 - Vestel 17MB82 mainboard - LED blinking

[baboom]

Re: Aya A39FHD3901/2 - Vestel 17MB82 mainboard - LED blinking

Same serial trace, no USB device found.

You can try with 2 or 4GB USB stick formatted as FAT32. If you can find one with LED indicator will be better.

[KevinWysocki]

Re: Aya A39FHD3901/2 - Vestel 17MB82 mainboard - LED blinking

Same serial trace, no USB device found.

[yokoono]

Re: Aya A39FHD3901/2 - Vestel 17MB82 mainboard - LED blinking

Try recovery software. For stick.

[KevinWysocki]

Hi there,

My mother in law gave me an Aya TV, to take a look if I could do something to repair it.

At startup, LED constantly blinks and no image is shown (even if I light the screen, broken backlight is not the problem), also +12V power rail is fine.

After some research, it seems that NOR flash often fails on this mainboard, I have found the procedure to force flash upgrading with a USB key connected to mainboard USB port, pressing "OK" button on the remote and plugging the TV power cord.

Flash upgrade didn't seem to work, LED keeps blinking. I have found a post on Hackaday that tolds CPU serial lines are available on SCART connector so I connected a TTL Serial/USB converter and obtained this boot/kernel trace :

loader eeprom dump succeed.
===>There is no MB82_DEVELOPER,will check MB82_AUTOTEST !!!
===>There is no MB82_AUTOTEST,will Boot Normally!!! Environment is root=/dev/mtdblock2 rootwait lpj=1814528 console=ttyMT0,115200n1 quiet mtdparts=mt53xx-nor:192k(loader),1216k(kernel),8M(root),64k(ro),576k(rw)

hdr->ih_load = 0x8000

hdr->ih_ep = 0x8040

hdr->ih_size = 0x120c9c

kernel_size = 0x3100000

====>copy kernel to dram normal_case :kernel_size=1182940

 NOR boot

Do USB upgrade
total mem size: 0x8000000, fbm addr:0x3bc0000, fbm size: 0x4440000
USB upgrade stop
Boot reason: A/C power on
Offset:0x00000000
Installed:0x11223345, 0x11223345
Boot reason: A/C power on
dLastStandbyStatus = 0, dLastStandbyStatusOffset = 5, PDWNC_ReadWakeupReason() = 6
Boot reason: A/C power on
PDWNC_SetT8032LEDBlinkOn 1___________________________
Uncompressing Linux... done, booting the kernel.
<mt53xx_nor_init>hank:V0.7.2m(protect 0 flash)...
Flash Index: 0, MenuID: ef, DevID1: 40, DevID2: 17
Setup flash information successful, support list index: 31
Flash Index: 1, MenuID: ef, DevID1: 40, DevID2: 15
Setup flash information successful, support list index: 29
Disable write protect for flash #0 is illegal
SQUASHFS error: xz_dec_run error, data probably corrupt
[swapper(1)]squashfs_xz_uncompress .
SQUASHFS error: squashfs_read_data failed to read block 0x7e237a
SQUASHFS error: Unable to read metadata cache entry [7e237a]
SQUASHFS error: Unable to read directory block [7e237a:16a5]
SQUASHFS error: Unable to read metadata cache entry [7e237a]
SQUASHFS error: Unable to read directory block [7e237a:16a5]
SQUASHFS error: Unable to read metadata cache entry [7e237a]
SQUASHFS error: Unable to read directory block [7e237a:16a5]
SQUASHFS error: Unable to read metadata cache entry [7e237a]
SQUASHFS error: Unable to read directory block [7e237a:16a5]
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[<c0024624>] (unwind_backtrace+0x0/0xe4) from [<c0186aec>] (panic+0x68/0xe4)
[<c0186aec>] (panic+0x68/0xe4) from [<c0019500>] (init_post+0xac/0xd8)
[<c0019500>] (init_post+0xac/0xd8) from [<c00089e8>] (kernel_init+0x124/0x16c)
[<c00089e8>] (kernel_init+0x124/0x16c) from [<c001f71c>] (kernel_thread_exit+0x0/0x8)

Whatever if USB key is connected or not, trace keep being the same, it seems that USB key isn't detected. It's a 64GB USB Key, partition is FAT32. I tried to reduce the partition size to 100MB, it didn't changed the result.

Do you have any tips to upgrade flash content with a USB key ?