Sign up here and you can log into the forum!

(SOLVED)bricked wdtv live and successfull Serial conection

Have a question about devices internals, memory layout, reverse engineering, etc---This is the place for anything so technical that it would cause a n00b's head to 'splode

(SOLVED)bricked wdtv live and successfull Serial conection   

Postby kilnakorr » Wed Mar 14, 2012 10:22 am

Hi

I know I don't have the brains to do this, but maybe some of you smarter people, can help me a bit.

As the topic says, I have a wdtv live in a coma, but managed to, get a serial connection going. The following code from putty when adding power to the wdtv live: (obviously I can see some errors in the code, but no idea how I can fix it ))

Code: Select all
39idxfsef2f712148b75194ab1d3c691b55bd4d3a5e956dS

#xos2P4a-99 (sfla 128kbytes. subid 0xac/ac) [serial#fbbe1cdd8c5f3412b645f2645ff49fec]
#stepxmb 0xac
#DRAM setup (method=0x10015858) ...
#DRAM0 Window  :    0x#24#22#22#24# (17)
#DRAM1 Window  :    0x#26#26#24#22# (17)
#DRAM0 Settings: WD=0x0b0b0b0a RG=0x08080808 RR=0x08080808 RF=0x09090909
#DRAM1 Settings: WD=0x0c0b0b0b RG=0x09090808 RR=0x09090808 RF=0x09090909
#poisoned 131072 pages with 0xe5a99263
#step6 @0*** zxenv has been customized compared to build ***
--- review xmasboot/configs/922-A2.config for details [xmbb7-ezboot98-nand_st2] ---
xloadsize=59444
xload rc=6
subrom SHA-256: 43b5383fcd2ecd1f5366bea4eafc03bd740dc0a113af58d02846c117fb581b5b
ezboot98 @0xd00e5a94 (nand_st2) (actual cpu=@499MHz/dsp=333MHz/sys=333MHz)
on 8655 rev ES5 (subid 0xac) a2=0x00000002 a3=0x00000003
step12
#step22
ruamm0 [0x80000000,0x8f2f0000[ (~254738432 bytes)
ruamm1 [0xcca00000,0xcfd60000[ (~53870592 bytes)
[0xcfd20000,xos_public_ga=0xcfd20000[ and [0xcfd40000,0xcfd5ffff[ are lost for alignment)
channel#ei
x_ga=0xcfd1fcd4
[0x8e800000,ios_ga=0x8e800000[ and [0x8eeacfc1,0x8f2f0000[ are lost for alignment)
GW32 0x0006f008 0xc0000000 [va=0x84000000]
GW32 0x0006f00c 0xc4000000 [va=0x88000000]
GW32 0x0006f010 0xc8000000 [va=0x8c000000]
step33
xos2k client version=19, server version=19
xos2 SHA-1 = ef2f712148b75194ab1d3c691b55bd4d3a5e956d (version 0x4a)
xos2 serial = fbbe1cdd8c5f3412b645f2645ff49fec
Using zbootxenv ga=0xcfd0bcbc (va=0xbbd0bcbc)

**************************************
* SMP86xx zboot start ...
* Version: 3.1.0
* Started at 0xd00ed770.
* Configurations (chip revision: 1):
*    Enabled checkpoints.
**************************************
DRAM0 dunit_cfg/delay0_ctrl (0x3514001a/0x4565132b).
DRAM1 dunit_cfg/delay0_ctrl (0x3514001a/0x4565132b).
Using UART port 0 as console.
Board ID.: villa_d2
Setting up H/W from XENV block at 0xbbd0bcbc.
  Setting <SYSCLK avclk_mux> to 0x17400000.
  Setting <SYSCLK hostclk_mux> to 0x00000130.
  Setting <IRQ rise edge trigger lo> to 0xff28ca00.
  Setting <IRQ fall edge trigger lo> to 0x0000c000.
  Setting <IRQ rise edge trigger hi> to 0x0c10009f.
  Setting <IRQ fall edge trigger hi> to 0x00000000.
  Setting <IRQ GPIO map> to 0x000a0800.
  Setting <PB default timing> to 0x03080202.
  Keeping <PB timing0> to 0x03080202.
  Keeping <PB Use timing0> to 0x000003f3.
  Keeping <PB CS Config> to 0x00330003.
  Enabled Devices: 0x001b3efc
    PCIHost Ethernet Ethernet1 IR FIP I2CM I2CS USB PCIDev1 PCIDev2 PCIDev3 PCIDev4 SATA SCARD SCARD1
  PCI IRQ routing:
    IDSEL 1: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
    IDSEL 2: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
    IDSEL 3: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
    IDSEL 4: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
  Smartcard pin assignments:
    OFF pin = 2
    5V pin = 0
    CMD pin = 1
  Smartcard1 pin assignments:
    OFF pin = 2
    5V pin = 0
    CMD pin = 1
cd#0 disabled
cd#1 disabled
cd#2 want 96000000Hz: setting of 0x0000000021c00000-2^28
cd#2 cannot measure
cd#3 disabled
cd#4 want 33333333Hz: setting of 0x0000000061333343-2^28
cd#4 measured to 33336kHz
cd#5 disabled
cd#6 disabled
cd#7 disabled
cd#8 disabled
cd#9 disabled
cd#10 disabled
cd#11 disabled
  GPIO dir/data = 0x00000880/0x00000880
  UART0 GPIO mode/dir/data = 0x6e/0x00/0x00
  UART1 GPIO mode/dir/data = 0x6e/0x04/0x04
  UART2 GPIO mode/dir/data = 0x00/0x00/0x00
  Generate pulse(s) with GPIO7 .. 1,0(16us),1
  MAC0: 00:90:a9:93:f7:b2
  MAC1: 00:16:e8:45:f2:64
XENV block processing completed.
Default boot index: 2, sel:2
xmboot booted from devtype: 0, chipsel: 0, phyblocknum: 0
Explicit boot order specified:
  0x00 : devtype=0, CS=0
  0x01 : devtype=0, CS=1
  0x20 : devtype=2, CS=0
  0x21 : devtype=2, CS=1
WARNING: ezboot encroaches upon ruamm#0 zone
ezboot buffers, setup in DRAM bank#0:
  Alloting 1048576 bytes for heap.
  Alloting 8388608 bytes for reading.
  Alloting 8388608 bytes for decryption.
xmat romfs goes to 0xcfc0bca0 (ga)
xmat romfs goes to 0xb3c0bca0 (va)
Trying devtype=0 chipsel=0
nand_probe 0x0xd00f6ed0
nand_Mg_open 0
Reading NAND CS0, addr 0x016c0000, size 0x00000800 to 0xb3c0bca0
Reading NAND CS0, addr 0x016c0800, size 0x00021400 to 0xb3c0c4a0
File xtask_loader.xload found
Trying devtype=0 chipsel=0
Reading NAND CS0, addr 0x078bf800, size 0x00000800 to 0xd011f3bc
sign_addr=0x078bfffc *sign=66, *sign=77, *sign=75, *sign=70757766
firmware OK.
found imat romfs @ 0x006c0000
imap romfs goes to 0xcec0bc90 (ga)
imap romfs goes to 0xb2c0bc90 (va)
Trying devtype=0 chipsel=0
Reading NAND CS0, addr 0x006c0000, size 0x00000800 to 0xb2c0bc90
Reading NAND CS0, addr 0x006c0800, size 0x00141000 to 0xb2c0c490
File itask_loader.iload found
Channel pending 1602
Channel pending 954384
Channel pending 2001488
Channel pending 3092222
Channel pending 4182968
Channel pending 5273804
Channel pending 6364552
Channel pending 7455286
Channel pending 8546002
Channel pending 9636766
Trying devtype=0 chipsel=0
reading z.boot2 (vzx=0xbbd0bcbc) is 0x003c0000
Reading NAND CS0, addr 0x003c0000, size 0x00000800 to 0x01740000
Reading NAND CS0, addr 0x003c0800, size 0x002a7000 to 0x01740800
Found.
ROMFS found at 0x0x01740000, Volume name = MIPSLINUX_XLOAD
Found 1 file(s) to be processed in ROMFS.
Processing vmlinux_xload.zbf (start: 0x01740090, size: 0x002a7424)
  Checking zboot file signature .. OK.
  Warning: header version mismatched.
   *** Fully Encrypted.
src_addr = 0x017400b0, dest addr = 0x01f40000
XLOADING src=0x817400b0, dest=0x81f40000, size=0x002a7404
xload.c:77: Waiting for XLOAD completion.
xload.c:87: XLOAD done, status = 0xbb.
XLOAD failed.
Done with container 2.
Skipping boot container 3.
Skipping boot container 4.
Skipping boot container 5.
Skipping boot container 6.
Skipping boot container 7.
Trying devtype=0 chipsel=1
nand_probe 0x0xd00f6ed0
Failed to init!
Trying devtype=2 chipsel=0
Last edited by kilnakorr on Thu Mar 15, 2012 11:24 am, edited 2 times in total.
kilnakorr
DLX'er
 
Posts: 50
Joined: Fri Mar 09, 2012 3:50 am

Re: WANTED: bricked wdtv live and successfull Serial conecti   

Postby RMerlin » Wed Mar 14, 2012 10:44 am

Did you do a crossflash (i.e. flashing a Plus firmware on a Live, Live Streaming on a Live, etc...)) to cause the problem?
WDLXTV Webend maintainer. Visit http://www.lostrealm.ca/wdlxtv to see my other WDLXTV projects.
If you like my work, please consider donating.
User avatar
RMerlin
WDLXTV Team
 
Posts: 3236
Joined: Sat Jun 26, 2010 9:25 am
Location: Montreal, Canada

Re: WANTED: bricked wdtv live and successfull Serial conecti   

Postby kilnakorr » Wed Mar 14, 2012 10:49 am

I am pretty sure I didn't. I was trying to flash with custom firmware (the right one) but installation never started. The device just froze up on logo screen, and completely dead.
kilnakorr
DLX'er
 
Posts: 50
Joined: Fri Mar 09, 2012 3:50 am


Re: bricked wdtv live and successfull Serial conection.(almo   

Postby recliq » Thu Mar 15, 2012 2:05 am

I'd say you wait for b-rad to comment on this, he's probably the one who can tell you what's going wrong.
Your WD TV seems to fail to boot the kernel (or doesn't even get there because XLOAD fails). Not sure how this can be fixed but if anyone can tell you it's b-rad.
­WDLXTV Project Maintainer
-:] If you like my contributions feel free to donate for a beer or a new flash drive. ...and always remember: RTFM! (README, FAQ, WIKI) [:-
User avatar
recliq
WDLXTV Team
 
Posts: 5036
Joined: Thu Apr 15, 2010 8:09 am
Location: Kiel, Germany

Re: bricked wdtv live and successfull Serial conection.(almo   

Postby kilnakorr » Thu Mar 15, 2012 2:29 am

thanks both of you. Having a little issue with the connection itself, as It seems I cannot send commands to the player (Grrrrrrr). Will keep you updated. I know b-rad is the go-to guy on this one, but who can tell when he's got time to look into it? ;)
kilnakorr
DLX'er
 
Posts: 50
Joined: Fri Mar 09, 2012 3:50 am

Re: bricked wdtv live and successfull Serial conection.(almo   

Postby KAD » Thu Mar 15, 2012 7:41 am

you'll have to be patient, b-rad's been quite busy with other stuff
If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
User avatar
KAD
Global Moderator
 
Posts: 4021
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: bricked wdtv live and successfull Serial conection.(almo   

Postby kilnakorr » Thu Mar 15, 2012 8:02 am

I know...It seems that loading yamoo with '0' works fine, pressing '1' starts some huge process and my usb pen now gets read!! Something fails though, and I swear I so something with "wdtv_live_plus" somewhere (not good since it's just the liver version :? )

Gonna see if I can figure out some stuff while waiting for b-rad to magically appear :)
kilnakorr
DLX'er
 
Posts: 50
Joined: Fri Mar 09, 2012 3:50 am

Re: bricked wdtv live and successfull Serial conection.(almo   

Postby RMerlin » Thu Mar 15, 2012 4:07 pm

kilnakorr wrote:I know...It seems that loading yamoo with '0' works fine, pressing '1' starts some huge process and my usb pen now gets read!! Something fails though, and I swear I so something with "wdtv_live_plus" somewhere (not good since it's just the liver version :? )

Gonna see if I can figure out some stuff while waiting for b-rad to magically appear :)


Best way to catch b-rad is to see if he's around on IRC.

Based on your log I have a feeling you ended up flashing your device with the wrong firmware, that's why I asked that question. If you get to Yamon there's probably a chance it's recoverable, but only b-rad has the know-how to do this.
WDLXTV Webend maintainer. Visit http://www.lostrealm.ca/wdlxtv to see my other WDLXTV projects.
If you like my work, please consider donating.
User avatar
RMerlin
WDLXTV Team
 
Posts: 3236
Joined: Sat Jun 26, 2010 9:25 am
Location: Montreal, Canada

Re: (SOLVED)bricked wdtv live and successfull Serial conecti   

Postby kilnakorr » Thu Mar 15, 2012 10:50 pm

I got yamon and everything is fixed, not sure how but fixed :)
kilnakorr
DLX'er
 
Posts: 50
Joined: Fri Mar 09, 2012 3:50 am

Next

Return to WDTV Live

Who is online

Users browsing this forum: bass-c and 0 guests