Thursday, 29 October 2015

HOW TO UPGRADE RESCURE SPARK THROUGH USB METHOD

Upgrade rescure sw have 2 method by 1. THROUGH USB or  by TFTP

Upgrade rescure spark by USB Preparation:

1. We only recommend Kingston USB stick, we don’t support USB hard disk
2. Please make sure your USB stick only have 1 partition and the file system is
FAT32
3. Set default booting system to [spark].
Upgrade Step:
1. Make sure [C:/spark] is exist, if not, please create this folder.
2. copy [mImage] and [userfsub.img] to [C:/spark]
3. Connect USB stick to STB
4. Keep Pressing [OK] Button in Front Panel, then power on STB.
5. After 5 seconds, you will see [Forc] in LED, release [OK] button and press
[Right] Button.
6. if everything OK, You will see [U LD] shining in LED
7. if upgrade success, You will see [SUCC] and STB reboot automatically
8. If upgrade not finishes in 5 minutes, then there must be something wrong, please

check your configuration and re-try.

Upgrade rescure spark by tftp

Preparation: 

1.Install TFTP tools [csicotftp11.rar] to your PC 

2.Set your PC IP addr to [192.168.40.19] 3.connect your PC to STB by LAN, now we only support LAN, do not support WLAN 4.Set default booting system to [spark] Upgrade Step: 1.copy [mImage] and [userfsub.img] to any folder of your PC, for example [C:/spark] 2.select folder in TFTP tools: 

3.Keep Pressing [OK] Button in Front Panel, then power on STB.

4.After 5 seconds you will see [Forc] in LED, release [OK] button and press [Right] Button. 

5.If everything OK, You will see [T LD] shining in LED and you will see some debug information in TFTP Server, like “Mon Oct 25 14:02:36 2010: Sending 'mImage' file to 192.168.40.19 in binary mode Mon Oct 25 14:02:39 2010: Successful. Mon Oct 25 14:02:50 2010: Sending 'userfsub.img' file to 192.168.40.19 in binary mode Mon Oct 25 14:03:33 2010: Successful.” 

6.if upgrade success, You will see [SUCC] and STB reboot automatically If upgrade not finishes in 5 minutes, then there must be something wrong, please check your configuration and re-try.

0 comments: