WD TV Live Hub и проблема загрузки YAMON c HDD.

Обсуждение WD TV Live (SMP8655)

Moderator: Модераторы

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bombur on Fri Mar 02, 2012 17:45

bahosh wrote:С этого тоже не удалось попасть в YAMON вот лог....

Всё нормально, судя по логу, мы всё же продвинулись на 1 шаг вперёд, и надежда ещё есть! Я подправил адрес загрузки, и теперь нужно попробовать следующий вариант. И логи приложите, пожалуйста.
You do not have the required permissions to view the files attached to this post.
With respect,
bombur.
User avatar
bombur
Developer
 
Posts: 550
Joined: Wed Nov 03, 2004 13:41
Location: Kiev

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bahosh on Fri Mar 02, 2012 19:42

Вот лог 3-го теста....

Code: Select all
39idxfsefa7f66fd6a3bb16c939bafb7546b46d5595571bS

#xos2P62-100 (sfla 128kbytes. subid 0xb0/b0) [serial#cc8103c2f1752c7cffa600663c5ccd2f]
#stepxmb 0xac
*** No valid zxenv found in DevType 0 CS#0, phyblock#0 ! ***
*** No valid zxenv found in DevType 0 CS#0, phyblock#1 ! ***
No valid zxenv found in device group 0 CS#0
No valid zxenv found in device group 0 CS#1
No valid zxenv found in device group 1 CS#0
No valid zxenv found in device group 1 CS#1
Failed to init devtype 2 CS#0
SATA drive spin-up in progress, please standby...
#DRAM setup (method=0x10015858) ...
#DRAM0 Window  :    0x#24#24#28#24# (18)
#DRAM1 Window  :    0x#28#28#28#29# (20)
#DRAM0 Settings: WD=0x0a0a0a0a RG=0x08080908 RR=0x08080908 RF=0x090a0a0a
#DRAM1 Settings: WD=0x0a0a0a0a RG=0x0909090a RR=0x0909090a RF=0x0a0a0a0a
#poisoned 131072 pages with 0x6c438bc1
#step6*** zxenv has been customized compared to build ***
--- review xmasboot/configs/922-A2.config for details [xmbb7-ezboot98-nand_st2] ---
xloadsize=61748
xload rc=6
subrom SHA-256: 43b5383fcd2ecd1f5366bea4eafc03bd740dc0a113af58d02846c117fb581b5bezboot98 @0xd00e5a94 (nand_st2) (actual cpu=@499MHz/dsp=333MHz/sys=333MHz)
on 8654 rev ES5 (subid 0xb0) 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 = efa7f66fd6a3bb16c939bafb7546b46d5595571b (version 0x62)
xos2 serial = cc8103c2f1752c7cffa600663c5ccd2f
Using zbootxenv ga=0xcfd0bcbc (va=0xbbd0bcbc)

**************************************
* SMP86xx zboot start ...
* Version: 3.1.0
* Started at 0xd00ee720.
* 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 33332kHz
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:16:e8:81:03:c2
  MAC1: 00:16:e8:a6:00:66
XENV block processing completed.
Default boot index: 0, sel:0
xmboot booted from devtype: 4, chipsel: 1, phyblocknum: 0
Explicit boot order specified:
  0x40 : devtype=4, CS=0
  0x41 : devtype=4, 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 0xcf50bca0 (ga)
xmat romfs goes to 0xb350bca0 (va)
Trying devtype=4 chipsel=0
Failed to init!
Trying devtype=4 chipsel=1
SATA drive spin-up in progress, please standby...
Failed to init!
Failed to find valid xmat romfs in any device / chip select!
freeing xmat romfs buffer at 0xcf50bca0
xmat romfs process failed.
Trying devtype=4 chipsel=0
Failed to init!
Trying devtype=4 chipsel=1
reading z.boot0 (vzx=0xbbd0bcbc) is 0x00080000
Not a valid ROMFS
reading z.boot1 (vzx=0xbbd0bcbc) is 0x00000000
Found.
ROMFS found at 0x0x01740000, Volume name = YAMON_XLOAD
Found 1 file(s) to be processed in ROMFS.
Processing yamon-xload.zbf (start: 0x01740080, size: 0x00032190)
  Checking zboot file signature .. OK.
  Warning: header version mismatched.
  Execute at 0x84000000 denied.
Done with container 1.
read def_boot=0, status=6.
going to set def_boot=2, status=6!!
boot_image_buf = 24379392!
Failed to read zboot image!
read def_boot=2, status=6.
erase_storage_sign
Trying devtype=4 chipsel=0
Trying devtype=4 chipsel=1
write_firmware_sign
Trying devtype=4 chipsel=0
Trying devtype=4 chipsel=1
reading z.boot2 (vzx=0xbbd0bcbc) is 0x004c0000
Not a valid ROMFS
bahosh
 
Posts: 20
Joined: Tue Nov 22, 2011 21:46

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bombur on Sat Mar 03, 2012 12:49

bahosh wrote:Вот лог 3-го теста....

Хмм, может я подзабыл чего... :? Тогда попробуйте ещё такой вариант.
You do not have the required permissions to view the files attached to this post.
With respect,
bombur.
User avatar
bombur
Developer
 
Posts: 550
Joined: Wed Nov 03, 2004 13:41
Location: Kiev

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bahosh on Sat Mar 03, 2012 13:59

Вот 4-ый лог...

Code: Select all
39idxfsefa7f66fd6a3bb16c939bafb7546b46d5595571bS

#xos2P62-100 (sfla 128kbytes. subid 0xb0/b0) [serial#cc8103c2f1752c7cffa600663c5ccd2f]
#stepxmb 0xac
*** No valid zxenv found in DevType 0 CS#0, phyblock#0 ! ***
*** No valid zxenv found in DevType 0 CS#0, phyblock#1 ! ***
No valid zxenv found in device group 0 CS#0
No valid zxenv found in device group 0 CS#1
No valid zxenv found in device group 1 CS#0
No valid zxenv found in device group 1 CS#1
Failed to init devtype 2 CS#0
SATA drive spin-up in progress, please standby...
#DRAM setup (method=0x10015858) ...
#DRAM0 Window  :    0x#24#24#28#24# (18)
#DRAM1 Window  :    0x#28#28#29#29# (20)
#DRAM0 Settings: WD=0x0a0a0a0a RG=0x08080908 RR=0x08080908 RF=0x0a090a0a
#DRAM1 Settings: WD=0x0a0a0a0a RG=0x09090a0a RR=0x09090a0a RF=0x0a0a0a0a
#poisoned 131072 pages with 0x125e540a
#step6*** zxenv has been customized compared to build ***
--- review xmasboot/configs/922-A2.config for details [xmbb7-ezboot98-nand_st2] ---
xloadsize=61748
xload rc=6
subrom SHA-256: 43b5383fcd2ecd1f5366bea4eafc03bd740dc0a113af58d02846c117fb581b5bezboot98 @0xd00e5a94 (nand_st2) (actual cpu=@499MHz/dsp=333MHz/sys=333MHz)
on 8654 rev ES5 (subid 0xb0) 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 = efa7f66fd6a3bb16c939bafb7546b46d5595571b (version 0x62)
xos2 serial = cc8103c2f1752c7cffa600663c5ccd2f
Using zbootxenv ga=0xcfd0bcbc (va=0xbbd0bcbc)

**************************************
* SMP86xx zboot start ...
* Version: 3.1.0
* Started at 0xd00ee720.
* 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:16:e8:81:03:c2
  MAC1: 00:16:e8:a6:00:66
XENV block processing completed.
Default boot index: 0, sel:0
xmboot booted from devtype: 4, chipsel: 1, phyblocknum: 0
Explicit boot order specified:
  0x40 : devtype=4, CS=0
  0x41 : devtype=4, 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 0xcf50bca0 (ga)
xmat romfs goes to 0xb350bca0 (va)
Trying devtype=4 chipsel=0
Failed to init!
Trying devtype=4 chipsel=1
Not a valid ROMFS
Failed to find valid xmat romfs in any device / chip select!
freeing xmat romfs buffer at 0xcf50bca0
xmat romfs process failed.
Trying devtype=4 chipsel=0
Failed to init!
Trying devtype=4 chipsel=1
reading z.boot0 (vzx=0xbbd0bcbc) is 0x00080000
Not a valid ROMFS
reading z.boot1 (vzx=0xbbd0bcbc) is 0x00000000
Found.
ROMFS found at 0x0x01740000, Volume name = YAMON_XLOAD
Found 1 file(s) to be processed in ROMFS.
Processing yamon-xload.zbf (start: 0x01740080, size: 0x00032190)
  Checking zboot file signature .. OK.
  Warning: header version mismatched.
  Execute at 0xa7000000 denied.
Done with container 1.
read def_boot=0, status=6.
going to set def_boot=2, status=6!!
boot_image_buf = 24379392!
Failed to read zboot image!
read def_boot=2, status=6.
erase_storage_sign
Trying devtype=4 chipsel=0
Trying devtype=4 chipsel=1
write_firmware_sign
Trying devtype=4 chipsel=0
Trying devtype=4 chipsel=1
reading z.boot2 (vzx=0xbbd0bcbc) is 0x004c0000
Not a valid ROMFS
bahosh
 
Posts: 20
Joined: Tue Nov 22, 2011 21:46

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bombur on Sat Mar 03, 2012 18:02

bahosh wrote:Вот 4-ый лог...

Спасибо. Что ж, по всей видимости, они прикрыли все лазейки, и запустить ямон, не подписанный их сертификатом, не удастся. Правда, остаётся ещё один вариант - запустить с sata-винта вместо ямона их линукс-ядро... Даст ли это что-то, как считаете? Есть ли у ядра инструмент авто-восстановления прошивки с флешки?..
With respect,
bombur.
User avatar
bombur
Developer
 
Posts: 550
Joined: Wed Nov 03, 2004 13:41
Location: Kiev

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bahosh on Sat Mar 03, 2012 18:11

Если вы подскажите как это сделать, я попробую. а можно с вами связаться в аське?
bahosh
 
Posts: 20
Joined: Tue Nov 22, 2011 21:46

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby dreamW on Sat Mar 03, 2012 21:56

Подсунул в этот образ ямон из набора для 8643, ямон загрузился.

Ссылка: http://s1a.andboson.com/Tools/sata_yamon_hub


Есть другая проблема (которую я, кстати, в самом начале подозревал): не печатает ничего в консоли.

Т.е., вполне вероятно, что и попасть в родной ямон можно было, но просто нет сигнала.

Вопрос: Что делать, куда рыть человеку? Говорит, что с этим шнурком прошивает модемы без проблем.
Более того, мы с ним восстанавливали Ливку на этом шнурке какое-то время назад.

ЗЫ: линукс я тоже подсовывал, и даже стартовал процесс обновления, но почему-то процесс прерывался по ошибке записи: http://pastebin.com/jciiutH2
d-link dsm-320rd >> egreat m34a >> egreat s1a >> popcorn a-200
dreamW
 
Posts: 71
Joined: Wed Jan 12, 2011 11:52
Location: Черкассы, Украина

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bahosh on Sun Mar 04, 2012 09:16

Кстати вот лог загрузки Yamon

Code: Select all
#xos2P62-100 (sfla 128kbytes. subid 0xb0/b0) [serial#5711e2c0bd5240e9042cf14729543cb6]
#stepxmb 0xac
*** No valid zxenv found in DevType 0 CS#0, phyblock#0 ! ***
*** No valid zxenv found in DevType 0 CS#0, phyblock#1 ! ***
No valid zxenv found in device group 0 CS#0
No valid zxenv found in device group 0 CS#1
No valid zxenv found in device group 1 CS#0
No valid zxenv found in device group 1 CS#1
Failed to init devtype 2 CS#0
SATA drive spin-up in progress, please standby...
#DRAM setup (method=0x10015858) ...
#DRAM0 Window  :    0x#27#26#26#28# (19)
#DRAM1 Window  :    0x#29#28#28#28# (20)
#DRAM0 Settings: WD=0x090a090a RG=0x09090a09 RR=0x09090a09 RF=0x0909090a
#DRAM1 Settings: WD=0x0a0a0a0a RG=0x0a090a09 RR=0x0a090a09 RF=0x0a0a0909
#poisoned 131072 pages with 0x8e2475ed
#step6 *** zxenv has been customized compared to build ***
--- review xmasboot/configs/922-A2.config for details [xmbb7-ezboot98-nand_st2] ---
xloadsize=61748
xload rc=6
subrom SHA-256: 43b5383fcd2ecd1f5366bea4eafc03bd740dc0a113af58d02846c117fb581b5b
ezboot98 @0xd00e5a94 (nand_st2) (actual cpu=@499MHz/dsp=333MHz/sys=333MHz)
on 8654 rev ES5 (subid 0xb0) 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 = efa7f66fd6a3bb16c939bafb7546b46d5595571b (version 0x62)
xos2 serial = 5711e2c0bd5240e9042cf14729543cb6
Using zbootxenv ga=0xcfd0bcbc (va=0xbbd0bcbc)

**************************************
* SMP86xx zboot start ...
* Version: 3.1.0
* Started at 0xd00ee720.
* 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 33332kHz
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:16:e8:11:e2:c0
  MAC1: 00:16:e8:2c:f1:47
XENV block processing completed.
Default boot index: 0, sel:0
xmboot booted from devtype: 4, chipsel: 1, phyblocknum: 0
Explicit boot order specified:
  0x40 : devtype=4, CS=0
  0x41 : devtype=4, 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 0xcf50bca0 (ga)
xmat romfs goes to 0xb350bca0 (va)
Trying devtype=4 chipsel=0
Failed to init!
Trying devtype=4 chipsel=1
Not a valid ROMFS
Failed to find valid xmat romfs in any device / chip select!
freeing xmat romfs buffer at 0xcf50bca0
xmat romfs process failed.
Trying devtype=4 chipsel=0
Failed to init!
Trying devtype=4 chipsel=1
reading z.boot0 (vzx=0xbbd0bcbc) is 0x00080000
Not a valid ROMFS
reading z.boot1 (vzx=0xbbd0bcbc) is 0x00000000
Found.
ROMFS found at 0x0x01740000, Volume name = YAMON_XLOAD
Found 1 file(s) to be processed in ROMFS.
Processing yamon-xload.zbf (start: 0x01740080, size: 0x0002f354)
  Checking zboot file signature .. OK.
  Warning: header version mismatched.
   *** Fully Encrypted.
src_addr = 0x017400a0, dest addr = 0x01f40000
XLOADING src=0x817400a0, dest=0x81f40000, size=0x0002f334
xload.c:77: Waiting for XLOAD completion.
xload.c:87: XLOAD done, status = 0x6.
  Decompressing to 0x85200000 .. OK (356240/0x56f90).
  Load time total 0/0 msec.
Execute at 0x85200000 ..

CS 0 vendor id 0xec.......
CS 0 device id 0xda.......
................................................................................................................................................................................................................................................................doing Super block Sanity checks... location 4
doing Managment block Sanity checks ...

CS 1 vendor id 0x00.......
CS 1 device id 0x00.......



**********************************
* YAMON ROM Monitor
* Revision 02.13-SIGMADESIGNS-24-R2.13-17
**********************************
Memory:  code: 0x86000000-0x86060000, 0x85200000-0x85204000
reserved data: 0x86200000-0x86300000, 0x86700000-0x87000000
PCI memory: 0x86300000-0x86700000



NAND FLASH Driver Version [ S I G M  1.0.6 ] on CS 0

!! No NAND hardware found on CS 1 !!


Environment variable 'start' exists. After 2 seconds
it will be interpreted as a YAMON command and executed.
Press Ctrl-C (or do BREAK) to bypass this.

Run $r01:
YAMON>
bahosh
 
Posts: 20
Joined: Tue Nov 22, 2011 21:46

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby Poslanec on Sun Mar 04, 2012 18:13

dreamW wrote:...
Есть другая проблема (которую я, кстати, в самом начале подозревал): не печатает ничего в консоли.
Т.е., вполне вероятно, что и попасть в родной ямон можно было, но просто нет сигнала.
Вопрос: Что делать, куда рыть человеку? Говорит, что с этим шнурком прошивает модемы без проблем.
Более того, мы с ним восстанавливали Ливку на этом шнурке какое-то время назад.
...

у меня была похожая ситуация, когда первый раз подключался к Дюне Смарт Д1 -- не печатала :(
до этого данным шнурком прошил с десяток аппаратов - тоже думал ж..а

валялся от старого мобильника еще один шнурок - на том же чипе http://fotkidepo.ru/?id=album:32684 распаял - с ним дюна завелась с пол тыка. :D
Poslanec
 
Posts: 1
Joined: Tue Jun 01, 2010 21:38

Re: WD TV Live Hub и проблема загрузки YAMON c HDD.

Postby bahosh on Mon Mar 05, 2012 15:09

Poslanec wrote:у меня была похожая ситуация, когда первый раз подключался к Дюне Смарт Д1 -- не печатала :(
до этого данным шнурком прошил с десяток аппаратов - тоже думал ж..а

валялся от старого мобильника еще один шнурок - на том же чипе http://fotkidepo.ru/?id=album:32684 распаял - с ним дюна завелась с пол тыка. :D


Спасибо что ответили, но увы не помог ваш совет. Менял систему на XP, пробовал разные шнурки, но результат один и тотже не работает печаталка. После загрузки Линукс-Ядра, аппарат просит подсунуть ему флешку. Ставил разные версии прошивки, появляется строка апдейта и на 0% зависает. лог не сохраняется полнустью, а выкладывать его концовку смысла нет. Может есть еще какие нибудь идеи?

:) Может у кого есть дамп для програматора, рискну поднять флеш. В долгу не останусь, можно написать в личку что и как.
bahosh
 
Posts: 20
Joined: Tue Nov 22, 2011 21:46

PreviousNext

Return to WD TV Live

Who is online

Users browsing this forum: Web crawler and 1 guest