Daca metoda manuala de mai sus esueaza, daca KCC nu vrea sa se conecteze la receiver de nici un fel, si daca atunci cand va conectati la Kathrein aveti un mesaj de genul asta:
Code:
Board: STb7100-mboard
U-Boot 1.1.2 (STLINUX_2_0p1) (May 30 2007 - 16:03:49)
DRAM: 32 MB
write time out = 1, clock = 40
write time out = 1, clock = 40
Flash: 16 MB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
pll0 freq 531
pll1 freq 399
Net: VFD_Driver Init
VFD_Controller Type : NEW Kathrein VFD
board_version = 0
Button_value = 7
STB7100-REF>
iar receiverul ramane la prompt fara sa mai miste.
Sau daca dupa ce ati executat cu grija procedura de mai sus aveti un mesaj de genul:
Code:
STB7100-REF> bootm a4000000
## Booting image at a4000000 ...
Image Name: Emergency system (captaintrip)
Image Type: SH-4 Linux Kernel Image (gzip compressed)
Data Size: 2489622 Bytes = 2.4 MB
Load Address: 84401000
Entry Point: 84402000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel @à @@ - 0x00000000 - 0 ...
Linux version 2.6.11.12_stm20-33 (root@localhost.localdomain) (gcc-Version 3.4.3 (STMicroelectronics/Linux Base 3.4.3-19) [build Mar 10 2006]) #6 Mon Jul 2 01:01:25 CEST 2007
hm, page 002c9000 reserved twice.
hm, page 002ca000 reserved twice.
Explicatia e simpla. Tocmai ati belit sectorul de memorie flash in care e salvat environment-ul de la U-Boot, adica setarile bootloaderului care explica ce si cum sa incarce acesta automat la pornire.
Rezolvarea e simpla. Rescrieti environment-ul cu comenzile de mai jos. Faceti cut and paste, una cate una:
Code:
setenv bootdelay 1
setenv ethaddr 0:50:fd:ff:78:ce
setenv autoload n
setenv defbootargs "console=ttyAS0,115200 root=/dev/mtdblock3 mem=32m bigphysarea=1024 coprocessor_mem=2m@0x04000000,2m@0x04200000"
setenv bootmtd=set "bootargs ;boot"
setenv bootargs "console=ttyAS0,115200 root=/dev/mtdblock3 mem=32m bigphysarea=1024 coprocessor_mem=2m@0x04000000,2m@0x04200000"
setenv filesize
setenv monitor_base
setenv monitor_len
setenv monitor_sec
setenv load_addr
setenv unprot
setenv update
setenv bootcmd bootm a0040000
saveenv
Dupa care reporniti, ori de la buton de la spate, ori de la prompt cu 'reset'.
Merge ca uns
P.S.: Nu sunt 100% sigur dar cred ca de fapt asta explica si pauldemon mai sus cand spune ca "In unele cazuri imaginea poate fi intacta dar sa defectat bootloader-ul."