Альтернативные способы восстановления прошивки с200

Обсуждение Popcorn C200/A200

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

Re: Альтернативные способы восстановления прошивки с200

Postby Fido on Wed Aug 28, 2013 19:27

Gennadyi wrote:
Если можно:
1. Лог загрузки YAMON-а без замыкания ножек
2. Значения переменных в YAMON


было
Code: Select all
#xos2P52-100 (sfla 128kbytes. subid 0x00/af) [serial#901a63b2386db0210f29ced8f57ece33]
xmb 0xb5
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
SATA drive spin-up in progress, please standby...
#chpll 0x01000024/0x00000201 -> 0x01000030/0x00000101... actual sys=330MHz
#DRAM setup (method=0x10015858) ...
#DRAM0 Window  :    0x#22#24#20#22# (16)
#DRAM1 Window  :    0x#22#24#22#22# (17)
#DRAM0 Settings: WD=0x0b0b0b0b RG=0x08080708 RR=0x08080708 RF=0x0a0a0a0a
#DRAM1 Settings: WD=0x0a0b0b0a RG=0x08080808 RR=0x08080808 RF=0x0909090a
#poisoned 131072 pages with 0xb1dfbc49
#step6*** zxenv has been customized compared to build ***
--- review xmasboot/configs/947-E2.config for details [xmbb7-ezboot98-nand_st2] ---
xloadsize=59172
xload rc=6
subrom SHA-256: 43b5383fcd2ecd1f5366bea4eafc03bd740dc0a113af58d02846c117fb581b5b
ezboot98 @0xd00e5a94 (nand_st2) (actual cpu=@661MHz/dsp=330MHz/sys=330MHz)
on 8643 rev ES3 (subid 0x00) a2=0x00000002 a3=0x00000003
step12
#step22
ruamm0 [0x8c000000,0x8f2f8000[ (~53444608 bytes)
ruamm1 [0xc0004000,0xcfff0000[ (~268353536 bytes)
[0xcffb0000,xos_public_ga=0xcffc0000[ and [0xcffe0000,0xcffeffff[ are lost for alignment)
x_ga=0xcffafcd4
[0xcf79fcbc,ios_ga=0xcf800000[ and [0xcfc00000,0xcff9fcbb[ are lost for alignment)
GW32 0x0006f008 0x80000000 [va=0x84000000]
GW32 0x0006f00c 0x84000000 [va=0x88000000]
GW32 0x0006f010 0x88000000 [va=0x8c000000]
step33
xos2k client version=19, server version=19
xos2 SHA-1 = 696b15f57c540829defeeee9f4a092007337a124 (version 0x52)
xos2 serial = 901a63b2386db0210f29ced8f57ece33
Using zbootxenv ga=0xcf79bcb0 (va=0xbb79bcb0)

**************************************
* SMP86xx zboot start ...
* Version: 3.1.0
* Started at 0xd00ecca8.
* Configurations (chip revision: 3):
*    Enabled checkpoints.
**************************************
DRAM0 dunit_cfg/delay0_ctrl (0x35140017/0x4565132b).
DRAM1 dunit_cfg/delay0_ctrl (0x35140017/0x4565132b).
Using UART port 0 as console.
Board ID.: 947-E2
Setting up H/W from XENV block at 0xbb79bcb0.
  Setting <SYSCLK avclk_mux> to 0x17400000.
  Setting <SYSCLK hostclk_mux> to 0x00000131.
  Setting <IRQ rise edge trigger lo> to 0xff288a06.
  Setting <IRQ fall edge trigger lo> to 0x00008000.
  Setting <IRQ rise edge trigger hi> to 0x0c10001f.
  Setting <IRQ fall edge trigger hi> to 0x00000000.
  Setting <IRQ GPIO map> to 0x000a0000.
  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: 0x001103f8
    Ethernet Ethernet1 IR FIP I2CM I2CS SDIO USB SATA
cd#0 disabled
cd#1 disabled
cd#2 want 96000000Hz: setting of 0x0000000021c00000-2^28
cd#2 cannot measure
cd#3 disabled
cd#4 measured to 129604kHz
cd#5 disabled
cd#6 want 96000000Hz: setting of 0x0000000021c00000-2^28
cd#6 measured to 0kHz
cd#7 disabled
cd#8 disabled
cd#9 disabled
cd#10 disabled
cd#11 disabled
  GPIO dir/data = 0x00004880/0x00004880
  UART0 GPIO mode/dir/data = 0x6e/0x00/0x00
  UART1 GPIO mode/dir/data = 0x00/0x00/0x00
  UART2 GPIO mode/dir/data = 0x00/0x00/0x00
  MAC0: 00:16:e8:1a:63:b2
  MAC1: 00:16:e8:29:ce:d8
XENV block processing completed.
Default boot index: 0
sb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntxmboot booted from devtype: 4, chipsel: 0, phyblocknum: 0
Explicit boot order specified:
  0x40 : devtype=4, CS=0
  0x41 : devtype=4, CS=1
ezboot buffers, setup in DRAM bank#0:
  Alloting 2097152 bytes for heap.
  Alloting 16777216 bytes for reading.
  Alloting 16777216 bytes for decryption.
xmat romfs goes to 0xcf59bca0 (ga)
xmat romfs goes to 0xb359bca0 (va)
Trying devtype=4 chipsel=0
Not a valid ROMFS
Trying devtype=4 chipsel=1
Failed to init!
Failed to find valid xmat romfs in any device / chip select!
freeing xmat romfs buffer at 0xcf59bc94
xmat romfs process failed.
Trying devtype=4 chipsel=0
reading z.boot0 (vzx=0xbb79bcb0) is 0x00080000
Found.
ROMFS found at 0x0x04240000, Volume name = YAMON_XLOAD
Found 1 file(s) to be processed in ROMFS.
Processing yamon-xload.zbf (start: 0x04240080, size: 0x0002f384)
  Checking zboot file signature .. OK.
  Warning: header version mismatched.
   *** Fully Encrypted.
src_addr = 0x042400a0, dest addr = 0x05240000
XLOADING src=0x842400a0, dest=0x85240000, size=0x0002f364
xload.c:77: Waiting for XLOAD completion.
xload.c:87: XLOAD done, status = 0x6.
  Decompressing to 0x85200000 .. OK (356320/0x56fe0).
  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-24
**********************************
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 !!


YAMON>
YAMON>
YAMON>
YAMON>
Fido
 
Posts: 18
Joined: Tue Jun 19, 2012 11:19

Re: Альтернативные способы восстановления прошивки с200

Postby Fido on Wed Aug 28, 2013 19:31

еще два варианта загрузки. Это и с замыканием и без.
Code: Select all
#xos2P52-100 (sfla 128kbytes. subid 0x00/af) [serial#901a63b2386db0210f29ced8f57ece33]
xmb 0xb5
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
SATA drive spin-up in progress, please standby...
#chpll 0x01000024/0x00000201 -> 0x01000030/0x00000101... actual sys=330MHz
#DRAM setup (method=0x10015858) ...
#DRAM0 Window  :    0x#22#24#20#22# (16)
#DRAM1 Window  :    0x#22#22#22#22# (17)
#DRAM0 Settings: WD=0x0b0b0b0b RG=0x08080708 RR=0x08080708 RF=0x0a0a0a0a
#DRAM1 Settings: WD=0x0a0b0b0a RG=0x08080808 RR=0x08080808 RF=0x090a090a
39idxfs696b15f57c540829defeeee9f4a092007337a124S


Code: Select all
#xos2P52-100 (sfla 128kbytes. subid 0x00/af) [serial#901a63b2386db0210f29ced8f57ece33]
xmb 0xb5
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
39idxfs696b15f57c540829defeeee9f4a092007337a124S
Fido
 
Posts: 18
Joined: Tue Jun 19, 2012 11:19

Re: Альтернативные способы восстановления прошивки с200

Postby Fido on Wed Aug 28, 2013 19:33

после безрезультатных пару десятков попыток загрузиться с замкнутыми контактами получилось повторить загрузку без замыкания

Code: Select all
39idxfs696b15f57c540829defeeee9f4a092007337a124S

#xos2P52-100 (sfla 128kbytes. subid 0x00/af) [serial#901a63b2386db0210f29ced8f57ece33]
xmb 0xb5
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
SATA drive spin-up in progress, please standby...
#chpll 0x01000024/0x00000201 -> 0x01000030/0x00000101... actual sys=330MHz
#DRAM setup (method=0x10015858) ...
#DRAM0 Window  :    0x#22#24#20#22# (16)
#DRAM1 Window  :    0x#22#24#22#22# (17)
#DRAM0 Settings: WD=0x0b0b0b0b RG=0x08080708 RR=0x08080708 RF=0x0a0a0a0a
#DRAM1 Settings: WD=0x0b0b0b0a RG=0x08080808 RR=0x08080808 RF=0x0909090a
#poisoned 131072 pages with 0x41e50ef0
#*** zxenv has been customized compared to build ***
--- review xmasboot/configs/947-E2.config for details [xmbb7-ezboot98-nand_st2] ---
xloadsize=59172
xload rc=6
subrom SHA-256: 43b5383fcd2ecd1f5366bea4eafc03bd740dc0a113af58d02846c117fb581b5b
ezboot98 @0xd00e5a94 (nand_st2) (actual cpu=@661MHz/dsp=330MHz/sys=330MHz)
on 8643 rev ES3 (subid 0x00) a2=0x00000002 a3=0x00000003
step12
ruamm0 [0x8c000000,0x8f2f8000[ (~53444608 bytes)
ruamm1 [0xc0004000,0xcfff0000[ (~268353536 bytes)
[0xcffb0000,xos_public_ga=0xcffc0000[ and [0xcffe0000,0xcffeffff[ are lost for alignment)
channel_#ei
_ga=0xcffafcd4
[0xcf79fcbc,ios_ga=0xcf800000[ and [0xcfc00000,0xcff9fcbb[ are lost for alignment)
GW32 0x0006f008 0x80000000 [va=0x84000000]
GW32 0x0006f00c 0x84000000 [va=0x88000000]
GW32 0x0006f010 0x88000000 [va=0x8c000000]
step33
xos2k client version=19, server version=19
xos2 SHA-1 = 696b15f57c540829defeeee9f4a092007337a124 (version 0x52)
xos2 serial = 901a63b2386db0210f29ced8f57ece33
Using zbootxenv ga=0xcf79bcb0 (va=0xbb79bcb0)

**************************************
* SMP86xx zboot start ...
* Version: 3.1.0
* Started at 0xd00ecca8.
* Configurations (chip revision: 3):
*    Enabled checkpoints.
**************************************
DRAM0 dunit_cfg/delay0_ctrl (0x35140017/0x4565132b).
DRAM1 dunit_cfg/delay0_ctrl (0x35140017/0x4565132b).
Using UART port 0 as console.
Board ID.: 947-E2
Setting up H/W from XENV block at 0xbb79bcb0.
  Setting <SYSCLK avclk_mux> to 0x17400000.
  Setting <SYSCLK hostclk_mux> to 0x00000131.
  Setting <IRQ rise edge trigger lo> to 0xff288a06.
  Setting <IRQ fall edge trigger lo> to 0x00008000.
  Setting <IRQ rise edge trigger hi> to 0x0c10001f.
  Setting <IRQ fall edge trigger hi> to 0x00000000.
  Setting <IRQ GPIO map> to 0x000a0000.
  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: 0x001103f8
    Ethernet Ethernet1 IR FIP I2CM I2CS SDIO USB SATA
cd#0 disabled
cd#1 disabled
cd#2 want 96000000Hz: setting of 0x0000000021c00000-2^28
cd#2 cannot measure
cd#3 disabled
cd#4 measured to 129600kHz
cd#5 disabled
cd#6 want 96000000Hz: setting of 0x0000000021c00000-2^28
cd#6 measured to 0kHz
cd#7 disabled
cd#8 disabled
cd#9 disabled
cd#10 disabled
cd#11 disabled
  GPIO dir/data = 0x00004880/0x00004880
  UART0 GPIO mode/dir/data = 0x6e/0x00/0x00
  UART1 GPIO mode/dir/data = 0x00/0x00/0x00
  UART2 GPIO mode/dir/data = 0x00/0x00/0x00
  MAC0: 00:16:e8:1a:63:b2
  MAC1: 00:16:e8:29:ce:d8
XENV block processing completed.
Default boot index: 0
sb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntsb!ntxmboot booted from devtype: 4, chipsel: 0, phyblocknum: 0
Explicit boot order specified:
  0x40 : devtype=4, CS=0
  0x41 : devtype=4, CS=1
ezboot buffers, setup in DRAM bank#0:
  Alloting 2097152 bytes for heap.
  Alloting 16777216 bytes for reading.
  Alloting 16777216 bytes for decryption.
xmat romfs goes to 0xcf59bca0 (ga)
xmat romfs goes to 0xb359bca0 (va)
Trying devtype=4 chipsel=0
Not a valid ROMFS
Trying devtype=4 chipsel=1
Failed to init!
Failed to find valid xmat romfs in any device / chip select!
freeing xmat romfs buffer at 0xcf59bc94
xmat romfs process failed.
Trying devtype=4 chipsel=0
reading z.boot0 (vzx=0xbb79bcb0) is 0x00080000
Found.
ROMFS found at 0x0x04240000, Volume name = YAMON_XLOAD
Found 1 file(s) to be processed in ROMFS.
Processing yamon-xload.zbf (start: 0x04240080, size: 0x0002f384)
  Checking zboot file signature .. OK.
  Warning: header version mismatched.
   *** Fully Encrypted.
src_addr = 0x042400a0, dest addr = 0x05240000
XLOADING src=0x842400a0, dest=0x85240000, size=0x0002f364
xload.c:77: Waiting for XLOAD completion.
xload.c:87: XLOAD done, status = 0x6.
  Decompressing to 0x85200000 .. OK (356320/0x56fe0).
  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-24
**********************************
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 !!


YAMON>
Fido
 
Posts: 18
Joined: Tue Jun 19, 2012 11:19

Re: Альтернативные способы восстановления прошивки с200

Postby Fido on Wed Aug 28, 2013 19:36

Gennadyi wrote:2. Значения переменных в YAMON

как их снять?
следуя http://www.jackslab.org/?p=274
2.0 Display enviroment variables
Using ‘setenv’ without any other arguments to display all enviroment variables:


получаю
Code: Select all
YAMON> setenv

xenv_addr (R/W)  0xbb79bcb0
Fido
 
Posts: 18
Joined: Tue Jun 19, 2012 11:19

Re: Альтернативные способы восстановления прошивки с200

Postby Gennadyi on Thu Sep 12, 2013 20:37

Fido wrote:вот что получилось. Теперь ямон грузится с винта без замыкания ножек на микросхеме

Code: Select all
YAMON> load -b tftp://172.16.x.x/xosu-xos2P4a_8644_ES1_prod_000a.xload 0xa7000000
........................
YAMON> xkc xload 0x3131 0xa7000000 0x7dd4 0x190000
XLOADING src=0x83000000, dest=0x00190000, size=0x00007dd4
Waiting for XLOAD completion...
XLOAD done. status = 0x10 .. NOT OK.


Получается xos не загрузился правильно ?
Code: Select all
YAMON> load -b tftp://172.16.x.x/ios.bin.gz_8644_ES1_dev_0006.xload 0xa7000000
.....................................
XLOADING src=0x83000000, dest=0x00190000, size=0x00020a44
Waiting for XLOAD completion...
XLOAD done. status = 0x6 .. OK.

а ios загрузился ?
Gennadyi
Moderator
 
Posts: 942
Joined: Mon Nov 01, 2004 16:43

Re: Альтернативные способы восстановления прошивки с200

Postby Reyter on Mon Sep 16, 2013 11:06

А то, что и для xos и для ios одинаково dest=0x00190000 - это правильно?
Сорри за глупый вопрос :)
TechnoSonic MP101 4MB 162 MHz 8500B DVD-drive: FUSS DV9929B f/w sp-mp-1.51
HDX BD-1 HDD 2TB f/w 4.14
User avatar
Reyter
Administrator
 
Posts: 989
Joined: Mon Nov 01, 2004 11:50
Location: Russia, Ryazan

Re: Альтернативные способы восстановления прошивки с200

Postby Fido on Mon Sep 16, 2013 17:09

Gennadyi wrote:Получается xos не загрузился правильно ?
а ios загрузился ?

сюдя по ответам yamon - да


в итоге поведение аппарата не изменилось

есть еще методы восстановления? могу проверять любые т.к. терять уже нечего ;)
Fido
 
Posts: 18
Joined: Tue Jun 19, 2012 11:19

Re: Альтернативные способы восстановления прошивки с200

Postby Gennadyi on Wed Sep 18, 2013 19:15

Fido wrote:в итоге поведение аппарата не изменилось
есть еще методы восстановления? могу проверять любые т.к. терять уже нечего ;)


Вот с поведением как-раз не все понятно. !
В каком случае он грузится в YAMON c HDD без замыкания ?
И что на консоли когда HDD не подключен ?
Gennadyi
Moderator
 
Posts: 942
Joined: Mon Nov 01, 2004 16:43

Re: Альтернативные способы восстановления прошивки с200

Postby Fido on Wed Sep 18, 2013 21:08

Gennadyi wrote:Вот с поведением как-раз не все понятно. !
В каком случае он грузится в YAMON c HDD без замыкания ?
И что на консоли когда HDD не подключен ?

YAMON грузится без замыкания после команды reboot
после долгого выключения(обесточивания) надо замыкать
Fido
 
Posts: 18
Joined: Tue Jun 19, 2012 11:19

Re: Альтернативные способы восстановления прошивки с200

Postby None on Thu Sep 19, 2013 14:38

Fido wrote:
Gennadyi wrote:Вот с поведением как-раз не все понятно. !
В каком случае он грузится в YAMON c HDD без замыкания ?
И что на консоли когда HDD не подключен ?

YAMON грузится без замыкания после команды reboot
после долгого выключения(обесточивания) надо замыкать

Eсли-бы xos/ios прогрузились удачно, то загрузка yamon с hdd была-бы возможна только со старого образа выложенного в ветке посвященной восстановлению традиционным способом(до степ-стоне прошивки), более того - если-бы Вы после этого залили в аппарат свой старый, ранее сохраненный, xenv, то удачно-бы восстановили прошивку.
Тренируйте лоб, ещё очень много не пробитых стен!
User avatar
None
Administrator
 
Posts: 1162
Joined: Tue Nov 02, 2004 10:19
Location: Москва

PreviousNext

Return to Popcorn C200/A200

Who is online

Users browsing this forum: Web crawler and 0 guests