[HELP]: Wrong u_boot into flash

**kader_73** · 19.04.2014

Hello ;

I have done a mistake , i load into my hs7819 box a wrong u-boot image which is for hs 7119 , now i'm stuck with this (putty log )

Code:

Board: STx7111-7119  [32-bit mode]


U-Boot 1.3.1 (Nov 16 2013 - 09:55:12) - stm23_0046

DRAM:  256 MiB
NAND:  256 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
set ethaddr 00:1e:b8:0a:ae:a3
done
Setup mac address.
done
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
## Booting image at 80000000 ...
Bad Magic Number

NAND read: device 0 offset 0x60000, size 0x300000

reading NAND page at offset 0x60000 failed
 3145728 bytes read: ERROR
## Booting image at 80000000 ...
Bad Magic Number
7119 >

I tried to load the correct one ( usb_uboot.img for hs7819) using CH UP method but noway ; log :

Code:

 Board: STx7111-7119  [32-bit mode]


U-Boot 1.3.1 (Nov 16 2013 - 09:55:12) - stm23_0046

DRAM:  256 MiB
NAND:  256 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
set ethaddr 00:1e:b8:0a:ae:a3
done
Setup mac address.
done
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage

** Unable to read "uImage" from usb 0:1 **
## Booting image at 80000000 ...
Bad Magic Number

NAND read: device 0 offset 0x60000, size 0x300000

reading NAND page at offset 0x60000 failed
 3145728 bytes read: ERROR
## Booting image at 80000000 ...
Bad Magic Number
7119 >

How can I solve this ? any help please .

just for info , i have a copy of each mtdx , which i saved before with comand line (dd if=/dev/mtdx of=/tmp/mtdx ); if it can be useful.

Code:

 dev:    size   erasesize  name
mtd0: 00400000 00020000 "boot"
mtd1: 00300000 00020000 "kernel"
mtd2: 06000000 00020000 "rootfs"
mtd3: 08000000 00020000 "NAND 2"
mtd4: 08000000 00020000 "NAND 3"
mtd5: 00100000 00020000 "config"
mtd6: 09000000 00020000 "user"
mtd7: 10000000 00020000 "ALL"
mtd8: 00500000 00020000 "config1"

Regards

**solala** · 19.04.2014

what about the preset uboot... are the uboot commands working? try

print

and post the output here. try

help

and post the output here. try

fatload usb 0:1 80000000 anyfile.bin

where anyfile.bin has to be a file of a few kbyte in the root directory of an attached fat32 usb stick.
if those things are working it might be possible to flash the original uboot just by a few commands in the serial console

**Audioniek** · 20.04.2014

@kader73:

Your box is apparenty still able to do channel up. Channel up only works for files in the Fortis .ird format. If you have the correct bootloader as binary file you can create your own loader-ird by using the fup program. Fup is available for linux and windows. If you would like to try this option, I can tell you how to proceed. There is one proviso: you need to know the current resellerID that is in the current loader.

The simple way is to use a resellerchanger (or fup) on this file after unpacking it: http://www.hdmedia-universe.com/board/attachment.php?attachmentid=1094&d=1342114958 (loader L7.26 Octagon) and then use channel up. Your box will then have the Octagon resellerID though.

Regards,

Audioniek.

**harryhase** · 20.04.2014

Zitat von solala

.......
fatload usb 0:1 80000000 anyfile.bin
......

if this works and the image is running, with boxkit it's possible to change the reseller.

**kader_73** · 20.04.2014

hello ;

Thank you for all the answers; unfortnetly I'm on dutye and I have to be up tomorrow morning, so please be pation with me (and sorry for that) ! I will try all options once at home, and give more details.

thank you again.

Regards

**kader_73** · 21.04.2014

goodmorning ;

@ solala

here is the output of command given above :

Code:

 7119 > print
bootargs=console=ttyAS0,115200 panic=1 ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw coprocessor_mem=4m@0x40000000,4m@0x40400000
bootcmd=if usb reset; then run usbboot; fi; run mtdboot
bootdelay=3
baudrate=115200
ipaddr=192.168.1.25
serverip=192.168.1.10
preboot=if ethaddr; then echo "Setup mac address."; else echo "Use default mac address.";fi ;bootmenu
mtdboot=nand read.jffs2 0x80000000 0x00060000 0x00300000; bootm  0x80000000
usbboot=fatload usb 0:1 0x80000000 uImage; bootm 0x80000000
board=hdk7111
monitor_base=CFG_FLASH_BASE
monitor_len=0x00040000
monitor_sec=1:0-4
load_addr=0x80000000
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:1e:b8:0a:ae:a3
update=00

Environment size: 675/131068 bytes
7119 >

Spoiler:

Do you mean by anyfile.bin this one which size 256 KB ??

Code:

dev:    size   erasesize  name
mtd0: 00400000 00020000 "boot"

@ Audioniek ;

I tried with the .ird file , but the ch up doesn't work , because I think the u_boot into flash was made to load the E2 (kernel and the rootfs) which they are .img file . but even I use the usb_uboot.img given in the back folder I get no think ; this is the point . So I think the way is to write the appropiate file directly on the flash using the u_boot command line.

Regards

**solala** · 21.04.2014

... So I think the way is to write the appropiate file directly on the flash using the u_boot command line.

exactly that was my idea...
obviously the present loader wants to boot an uImage by using the ch up button, so in the result the update procedure doesnt work as expected.
anyfile.bin... i just wanted to know if you are able to load any file (e.g. an uboot.bin) from usb stick to RAM. if this works then you can go on and flash the loaded binary directly from RAM to the NAND and would be ready with the recover.
for example: if your backup of the mtd0 is named mtd0.bin then copy the file to an usb stick, fat32 formated, and try to load that file by the following commands

usb reset
fatload usb 0:1 80000000 mtd0.bin

and post the output here (output has to be something like '262144 bytes loaded..'

- - - Aktualisiert - - -

oh, and just to prepare the next steps please post the output of

help nand

and the output of

nand info

**kader_73** · 21.04.2014

output help nand

Code:

7119 > help nand
nand info                  - show available NAND devices
nand device [dev]     - show or set current device
nand read[.jffs2]     - addr off|partition size
nand write[.jffs2]    - addr off|partition size - read/write `size' bytes starting
    at offset `off' to/from memory address `addr'
nand erase [clean] [off size] - erase `size' bytes from
    offset `off' (entire device if not specified)
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off - mark bad block at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
nand lock [tight] [status] - bring nand to lock state or display locked pages
nand unlock [offset] [size] - unlock section

7119 >

output nand info

Code:

7119 > nand info

Device 0: NAND 256MiB 3,3V 8-bit, sector size 128 KiB
7119 >

output command :

Code:

7119 > usb reset
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
7119 > fatload usb 0:1 80000000 mtd0
reading mtd0
.........................

262144 bytes read
7119 >

One more thing, I used this command "dd if=/dev/mtd0 of=/tmp/mtd0 bs=128k count=2" to save the file mtd0, while this was in a tutorial given for an hs7810 (NOR flash 32M) that I applied on my 7819 . I hope that the resulting file is correct. I'm afraid to screw up the u_boot and then find myself with a dead box !!

**harryhase** · 21.04.2014

no fear; solala know what he says !!!

@solala if you need more infos, i have a working 7119 - 918g se+ - it should be the same flash layout like the 7819 - Octagon 1008g se+

**kader_73** · 21.04.2014

Zitat von harryhase

no fear; solala know what he says !!! ...

yeh , of course he is ; i just want to give maximum infos to him for helping me .

Thema: [HELP]: Wrong u_boot into flash

Themen-Optionen

Anzeige

[HELP]: Wrong u_boot into flash

The Following 2 Users Say Thank You to solala For This Useful Post:

The Following User Says Thank You to Audioniek For This Useful Post:

Berechtigungen