Sign up here and you can log into the forum!

PLease help Unbrick WDTVLIVE

the place for WDLXTV-Live bugs

PLease help Unbrick WDTVLIVE   

Postby Flyer » Wed Feb 24, 2016 2:09 am

good afternoon!
prompt after an unsuccessful insertion of the device, namely
I started from a flash card updating on an original insertion of wdtvlive_1.06.43_V
the device was restarted and on the screen long showed 0%.
I uploaded an insertion, I rebooted the device all the same there were 0%.
then I inserted a flash card with an insertion
1.05.04_V_WDLXTV.COM_WDLXTV_LIVE-0.5.2.2.

everything was copied as it is necessary and perezaustitsya.

now the device is started shows a logo.....flash card doesn't react. the panel doesn't work.

model:
WDBAAP0000NBK-EESN

I connected a cable, Yamon started.
Code: Select all
YAMON> setxenv
(0x00)    4 x.boot 0x00005800
(0x00)    4 z.stage1_ga 0x81600000
(0x00)    4 x.pll.1.pll 0x01000024
(0x00)    4 x.mux 0x00000201
(0x00)    4 x.ddr.0.density 0x00000004
(0x00)    4 x.ddr.1.density 0x00000004
(0x00)    4 x.ddr.grade 0x00000004
(0x00)    4 x.ddr.fmin_mhz 0x000000c8
(0x00)    4 x.ddr.fmax_mhz 0x0000014d
(0x00)    4 x.ddr.method 0x10015858
(0x00)    4 x.ddr.verbose 0x00000001
(0x00)    4 a.avclk_mux 0x17400000
(0x00)    4 a.hostclk_mux 0x00000130
(0x00)    4 a.cd0_freq 0x00000000
(0x00)    4 a.cd1_freq 0x00000000
(0x00)    4 a.cd2_freq 0x05b8d800
(0x00)    4 a.cd3_freq 0x00000000
(0x00)    4 a.cd4_freq 0x01fca055
(0x00)    4 a.cd5_freq 0x00000000
(0x00)    4 a.cd6_freq 0x00000000
(0x00)    4 a.cd7_freq 0x00000000
(0x00)    4 a.cd8_freq 0x00000000
(0x00)    4 a.cd9_freq 0x00000000
(0x00)    4 a.cd10_freq 0x00000000
(0x00)    4 a.cd11_freq 0x00000000
(0x00)    4 a.irq_rise_edge_lo 0xff28ca00
(0x00)    4 a.irq_rise_edge_hi 0x0c10009f
(0x00)    4 a.irq_fall_edge_lo 0x0000c000
(0x00)    4 a.irq_fall_edge_hi 0x00000000
(0x00)    4 a.gpio_irq_map 0x000a0800
(0x00)    4 a.pcidev1_irq_route 0x01010101
(0x00)    4 a.pcidev2_irq_route 0x01010101
(0x00)    4 a.pcidev3_irq_route 0x01010101
(0x00)    4 a.pcidev4_irq_route 0x01010101
(0x00)    4 a.gpio_dir 0x00000880
(0x00)    4 a.gpio_data 0x00000880
(0x00)    6 a.gpio7_pulse 10000
(0x00)    4 a.pb_def_timing 0x03080202
(0x00)    4 a.pb_cs_config 0x00330003
(0x00)    4 a.pb_cs_config1 0x00000000
(0x00)    4 a.pb_cs_ctrl 0x00000000
(0x00)    4 a.pb_timing0 0x03080202
(0x00)    4 a.pb_use_timing0 0x000003f3
(0x00)    4 a.uart0_gpio_mode 0x0000006e
(0x00)    4 a.uart0_gpio_dir 0x00000000
(0x00)    4 a.uart0_gpio_data 0x00000000
(0x00)    4 a.uart1_gpio_mode 0x0000006e
(0x00)    4 a.uart1_gpio_dir 0x00000004
(0x00)    4 a.uart1_gpio_data 0x00000004
(0x00)    4 a.uart1_baudrate 0x0000e100
(0x00)    4 a.scard_5v_pin 0x00000000
(0x00)    4 a.scard_cmd_pin 0x00000001
(0x00)    4 a.scard_off_pin 0x00000002
(0x00)    4 a.scard1_5v_pin 0x00000000
(0x00)    4 a.scard1_cmd_pin 0x00000001
(0x00)    4 a.scard1_off_pin 0x00000002
(0x00)    9 a.board_id villa_d2
(0x00)   84 xmb.comment --- review xmasboot/configs/922-A2.config for details [xmbb7-ezboot98-nand_st2] ---

(0x00)    4 a.enable_devices 0x001b3efc
(0x00)    4 a.sata_channel_cfg 0x00000007
(0x00)    4 z.boot0 0x00080000
(0x00)    4 z.boot1 0x000c0000
(0x00)    4 z.boot2 0x003c0000
(0x00)    4 z.imatromfs_offset 0x006c0000
(0x00)    4 z.imatromfs_failsafe_offset 0x008c0000
(0x00)    4 z.imatromfs_size 0x01000000
(0x00)    4 z.imatromfs_mm 0x00000001
(0x00)    4 z.xmatromfs_offset 0x016c0000
(0x00)    4 z.xmatromfs_size 0x00100000
(0x00)    4 z.xmatromfs_mm 0x00000001
(0x00)    4 z.interactive_boot_idx_sel 0x00000001
(0x00)    4 z.bootdev_order 0x21200100
(0x00)    9 y.testvar yamonfoo
(0x00)   91 y.b0 nflash read 0x080000 0xa4a00000 0x040000 0; dump romfs 0xa4a00000; load zbf 0xa4a00080; go
(0x00)   91 y.b1 nflash read 0x0c0000 0xa7000000 0x740000 0; dump romfs 0xa7000000; load zbf 0xa7000090; go
(0x00)   91 y.b2 nflash read 0x000000 0xa4a00000 0x080000 0; dump romfs 0xa4a00000; load zbf 0xa4a00080; go
(0x00)   91 y.fb0 nflash read 0x080000 0x84a00000 0x040000 0; dump romfs 0x84a00000; load zbf 0x84a00080; go
(0x00)   91 y.fb1 nflash read 0x0c0000 0x87000000 0x740000 0; dump romfs 0x87000000; load zbf 0x87000090; go
(0x00)   91 y.fb2 nflash read 0x480000 0x84a00000 0x080000 0; dump romfs 0x84a00000; load zbf 0x84a00080; go
(0x00)  179 y.spug load uu 0xa4a00000; cksum 0xa4a00000 0x20000; nflash erase -p 0 0x20000 0; nflash write -p 0 0xa4a00000 0x20000 0; nflash read -p 0 0xa4a00001 0x20000 0; cksum 0xa4a00001 0x20000
(0x00)  241 y.pug load -b tftp://172.30.2.212/ES4/phyblock0-latest-0x20000padded.922-A2 0xa4a00000; cksum 0xa4a00000 0x20000; nflash erase -p 0 0x20000 0; nflash write -p 0 0xa4a00000 0x20000 0; nflash read -p 0 0xa4a00001 0x20000 0; cksum 0xa4a00001 0x20000
(0x00)  221 y.yug load -b tftp://172.30.2.212/ES4/zbimage-yamon-xload-latest-0x40000padded 0xa4a00000; cksum 0xa4a00000 0x40000; nflash write 0x80000 0xa4a00000 0x40000 0; nflash read 0x80000 0xa4a00001 0x40000 0; cksum 0xa4a00001 0x40000
(0x00)  226 y.lug load -b tftp://172.30.2.212/ES4/zbimage-linux-xload-latest-0x500000padded 0xa7000000; cksum 0xa7000000 0x740000; nflash write 0xc0000 0xa7000000 0x740000 0; nflash read 0xc0000 0xa7000001 0x740000 0; cksum 0xa7000001 0x740000
(0x00)  230 y.imu load -b tftp://172.30.2.212/imaterial/imaterial.romfs.latest 0xa7000000; nflash erase 0x00800000 0x00900000 0; nflash write 0x00800000 0xa7000000 0x00900000 0; nflash read 0x00800000 0xa7000010 0x00900000 0; dump romfs 0xa7000010
(0x00)  230 y.xmu load -b tftp://172.30.2.212/xmaterial/xmaterial.romfs.latest 0xa4a00000; nflash erase 0x01800000 0x00200000 0; nflash write 0x01800000 0xa4a00000 0x00200000 0; nflash read 0x01800000 0xa4a00010 0x00200000 0; dump romfs 0xa4a00010
(0x00)  236 y.pugUNSTABLE load -b tftp://172.30.2.212/ES2/phyblock0-UNSTABLE-0x20000padded 0xa4a00000; cksum 0xa4a00000 0x20000; nflash erase -p 0 0x20000 0; nflash write -p 0 0xa4a00000 0x20000 0; nflash read -p 0 0xa4a00001 0x20000 0; cksum 0xa4a00001 0x20000
(0x00)  142 y.commit nflash read -p 0 0xa4a00000 0x20000 0; copy $xenv_addr 0xa4a00000 0x4000; nflash erase -p 0 0x20000 0; nflash write -p 0 0xa4a00000 0x20000 0
(0x00)   14 y.ub go 0xa00e5284
(0x00)   62 y.nwk load -b tftp://172.30.2.212/ES2/vmlinux-latest.bin 0x84000000
(0x00)  116 y.nwg go . root=/dev/nfs nfsroot=172.30.63.13:/roots/debinst-yourlogin ip=::::::dhcp rdinit=/none console=ttyS0 mem=135MB
(0x00)    4 l.cs0_size 0x10000000
(0x00)    4 l.cs0_parts 0x0000000b
(0x00)    4 l.cs0_part1_offset 0x00000000
(0x00)    4 l.cs0_part1_size 0x00080000
(0x00)    4 l.cs0_part2_offset 0x00080000
(0x00)    4 l.cs0_part2_size 0x00040000
(0x00)    4 l.cs0_part3_offset 0x000c0000
(0x00)    4 l.cs0_part3_size 0x00300000
(0x00)    4 l.cs0_part4_offset 0x003c0000
(0x00)    4 l.cs0_part4_size 0x00300000
(0x00)    4 l.cs0_part5_offset 0x006c0000
(0x00)    4 l.cs0_part5_size 0x01000000
(0x00)    4 l.cs0_part6_offset 0x016c0000
(0x00)    4 l.cs0_part6_size 0x00800000
(0x00)    4 l.rootfs_part 0x00000007
(0x00)    4 l.cs0_part7_offset 0x01ec0000
(0x00)    4 l.cs0_part7_size 0x05a00000
(0x00)    4 l.cs0_part8_offset 0x078c0000
(0x00)    4 l.cs0_part8_size 0x05a00000
(0x00)    4 l.cs0_part9_offset 0x0d2c0000
(0x00)    4 l.cs0_part9_size 0x00020000
(0x00)    4 l.cs0_part10_offset 0x0d2e0000
(0x00)    4 l.cs0_part10_size 0x00020000
(0x00)    4 l.cs0_part11_offset 0x0d300000
(0x00)    4 l.cs0_part11_size 0x00020000
(0x00)    4 l.cs1_size 0x00000000
(0x00)   23 a.linux_cmd console=ttyS0 mem=200M
(0x00)    4 z.log2_xpu0_size 0x00000017
(0x00)    4 z.dsp0_size 0x00500000
(0x00)    4 z.zdata0_size 0x00004000
(0x00)    4 z.uzdata0_size 0x0000c000
(0x00)    4 z.log2_xpu1_size 0x00000015
(0x00)    4 z.dsp1_size 0x00084000
(0x00)    4 z.zdata1_size 0x00008000
(0x00)    4 z.uzdata1_size 0x00014000
(0x00)    4 z.ruamm0_offset 0x00000000
(0x00)    4 z.ruamm1_offset 0x0ca00000
(0x00)    4 z.stage2_ga 0xc0000000
(0x00)    4 z.xos_public_mm 0x00000001
(0x00)    4 z.log2_xos_public_size 0x00000011
(0x00)    4 z.channel_index_mm 0x00000001
(0x00)    4 z.ih_api_mm 0x00000001
(0x00)    4 z.ios_mm 0x00000000
(0x00)    4 z.ios_size 0x006acfc1
(0x00)    4 z.splashscreen_enabled 0x00000001
(0x00)    4 i.sp.scaler 0x00000004
(0x00)    4 i.sp.digital_enable 0x00000001
(0x00)    4 i.sp.component_enable 0x00000001
(0x00)    4 i.sp.analog_enable 0x00000001
(0x00)    4 i.sp.digital_standard 0x00000021
(0x00)    4 i.sp.component_standard 0x00000071
(0x00)    4 i.sp.analog_standard 0x0000007b
(0x00)   11 i.sp.picture splash.sdd
(0x00)    4 i.sp.hdmi_chip 0x00000001
(0x00)    4 i.sp.animation_enable 0x00000001
(0x00)  140 a.ps.mt3_hs
1b 20 00 01 01 03 00 00 01 04 00 00 1a 00 14 35
2b 13 65 45 21 00 01 00 1a 00 14 35 2b 13 65 45
21 00 01 00 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b
0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b
0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b
0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b
0b 0b 0b 0b 0c 0c 0c 0c 80 80 80 80 7d 7f 7d 7f
05 05 05 05 05 05 05 05 0c 0c 0c 0c 80 80 80 80
7c 7c 7a 7a 05 05 05 05 05 05 05 05
(0x00)    4 a.ps.pll2 0x0101203b
(0x00)    4 a.ps.pll0 0x00000000
(0x00)   12 a.standby.mt3_hs
2f 60 00 01 01 03 00 00 01 04 00 00
(0x00)    4 a.standby.pll2 0x00000000
(0x00)    4 a.standby.pll0 0x00000000
(0x00)    4 a.standby.gpio_dir 0x00000800
(0x00)    4 a.standby.gpio_data 0x00000000
(0x00)   17 a.eth_mac 00:90:a9:77:1a:3b
(0x00)    9 a.eth1_mac 00:16:e8.
(0x0f)    4 z.default_boot 0x00000002
(0x0f)    4 z.xmat_romfs_buf 0xcfc0bca0
(0x00)   12 y.xenv_addr "0xbbd0bcbc"
158 records, 5945 bytes

YAMON>


it is an apportion of parts of an insertion
possibly something not so with part5

help what to do??
https://www.dropbox.com/s/uhymycu6co8ekxp/%D0%BB%D0%BE%D0%B3.txt?dl=0
Log device (link to dropbox)

I am not a programmer!!
thanks in advance
Flyer
n00b
 
Posts: 8
Joined: Wed Feb 24, 2016 1:33 am

Re: PLease help Unbrick WDTVLIVE   

Postby mad_ady » Wed Feb 24, 2016 5:04 am

If you have a serial cable already, what does it show when booting normally (without breaking into yamon)?
User avatar
mad_ady
Developer
 
Posts: 4522
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: PLease help Unbrick WDTVLIVE   

Postby Flyer » Wed Feb 24, 2016 8:44 am

mad_ady wrote:If you have a serial cable already, what does it show when booting normally (without breaking into yamon)?

Log booting normaly

Link to Dropbox in first post

https://www.dropbox.com/s/uhymycu6co8ekxp/%D0%BB%D0%BE%D0%B3.txt?dl=0


Ps:
Sorry, about my slow enghlish
From Russia with love
=)
Flyer
n00b
 
Posts: 8
Joined: Wed Feb 24, 2016 1:33 am

Re: PLease help Unbrick WDTVLIVE   

Postby mad_ady » Wed Feb 24, 2016 11:15 pm

Ok, your log shows that the WDTV is able to boot from the internal ROM, but has some read errors while starting things like apache:

Code: Select all
Error -3 while decompressing!
84581e3c(8065)->8d820000(16384)
Error -3 while decompressing!
84571e93(8442)->8bd28000(16384)


This might be due to a bad flash chip or due to a slightly corrupted ROM (did you run md5sum on it before flashing?).

The good news is - since it boots the kernel and reads /init without issues, you can use any EXT3_BOOT firmware or root.bin on an attached USB drive to start the system from USB instead. This should give you a working system and you should be able to use it to reflash the device (check the firmware's md5sum, check your USB drive filesystem to avoid corruption).

Good luck!
User avatar
mad_ady
Developer
 
Posts: 4522
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: PLease help Unbrick WDTVLIVE   

Postby Flyer » Thu Feb 25, 2016 4:51 am

mad_ady
thanks for the answer!

I am not a programmer and I am afraid to make a mistake. :?
from where it is possible to download the root.bin or EXT3_BOOT firmware file?
I ask you describe process of reanimation of my device on steps. :|

very much I hope for your help, thanks
Flyer
n00b
 
Posts: 8
Joined: Wed Feb 24, 2016 1:33 am

Re: PLease help Unbrick WDTVLIVE   

Postby mad_ady » Thu Feb 25, 2016 5:16 am

Grab the root.bin from here: http://forum.wdlxtv.com/viewtopic.php?f=61&t=9210
Put it in the root of your USB drive, safely eject, plug it in the WDTV and reboot it and profit. :)
User avatar
mad_ady
Developer
 
Posts: 4522
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: PLease help Unbrick WDTVLIVE   

Postby Flyer » Thu Feb 25, 2016 6:32 am

mad_ady wrote:Grab the root.bin from here: http://forum.wdlxtv.com/viewtopic.php?f=61&t=9210
Put it in the root of your USB drive, safely eject, plug it in the WDTV and reboot it and profit. :)


thus it is possible to update an insertion if there is no video image?

I will try to make so with this version of an insertion today.
all previous similar attempts didn't yield result (the diode on a flash-USB doesn't burn)
Flyer
n00b
 
Posts: 8
Joined: Wed Feb 24, 2016 1:33 am

Re: PLease help Unbrick WDTVLIVE   

Postby mad_ady » Thu Feb 25, 2016 11:24 pm

If you plug in a USB device with a root.bin on it, it should be picked up during boot. If you don't get any activity, paste back the console log while booting with a root.bin. If it works, you should get an image. Try with a composite cable to be sure (maybe configuration has been corrupted as well). More details here: http://wiki.wdlxtv.com/Ext3_version
User avatar
mad_ady
Developer
 
Posts: 4522
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: PLease help Unbrick WDTVLIVE   

Postby Flyer » Wed Mar 02, 2016 12:14 am

perfectly!!
The device is started from the USB stick!!

but if the USB stick to pull out that start doesn't happen.

if the device is started that I can return it to a regular state?

how to return to a standard insertion?

many thanks for assistance!
Flyer
n00b
 
Posts: 8
Joined: Wed Feb 24, 2016 1:33 am

Re: PLease help Unbrick WDTVLIVE   

Postby mad_ady » Wed Mar 02, 2016 12:54 am

While it runs you need to leave the USB stick plugged in. All the firmware files are stored on the USB drive. You now need to do another firmware update (you can place the firmware files on the stick) and modify wdtvlive.ver to be higher than what's currently in the root.bin and after boot you should be presented with a New firmware detected prompt. You can update as usual and if there is no problem with the NAND chip you should be able to boot to a regular firmware afterwards.

Don't unplug the USB while it's flashing. If you get stuck at updating at 0%, remove the USB and reinsert it. It should continue (if your stick is formatted as FAT32) automatically.

If the NAND chip is damaged, you will probably be stuck in the same boot loop. I doubt you can do anything to fix the NAND chip...
User avatar
mad_ady
Developer
 
Posts: 4522
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Next

Return to Bugs

Who is online

Users browsing this forum: No registered users and 1 guest