[HELP]: Wrong u_boot into flash

[solala]

hi kader,
please, can you attach your backup of mtd0 here?

since the above

set updt_boot "vfd LD;tftp 0x80000000 u-boot.bin;nand erase 0x00000000 0x00040000;nand write.jffs2 0x80000000 0x00000000 $filesize;vfd _End"

needs a formatted jffs2 filesystem and furthermore loads via tftp im not sure if that will work. The backup of the original mtd0 should show us the needed information

[kader_73]

hi solala

here the mtd0 file mtd0.zip


Regards

[solala]

looks like the sequence is correct, these are the embedded bootargs of your mtd0 backup:

bootdelay=0baudrate=115200
board=hdk7111_INPUT_CLOCK_RATE
targetname=muso
bootcmd=nand read.jffs2 0x80000000 0x00500000 0x00300000; bootm 0x80000000
hwnfconf=setenv nwhwnet device:eth0,hwaddr:$ethaddr
nfsserverconf=setenv nfs_server nfsroot=$serverip
ipconf=setenv ipaddrcfg ip=$ipaddr:$serverip:$gateway:$netmask:sdk:eth0ff
cramfsbootargs=run hwnfconf;run ipconf;setenv bootargs console=ttyAS0,115200 root=/dev/mtdblock2 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs $ipaddrcfg nwhwconf=$nwhwnet bigphysarea=5000 stb7111:eth0ff stmmaceth=msglvl:0,phyaddr:2,watchdog:4000,rxsize: 16 $MTD loglevel=0
nfsbootargs=run hwnfconf;run nfsserverconf;run ipconf;setenv bootargs console=ttyAS0,115200 root=/dev/nfs $nfs_server:/opt/STM/STLinux-2.3/devkit/sh4/target,nfsvers=2,rsize=4096,wsize=8192,nolock,tcp nwhwconf=$nwhwnet $ipaddrcfg stmmaceth=msglvl:0,phyaddr:2,watchdog:4000,rxsize: 16 bigphysarea=5000
ipaddr=192.168.6.253
serverip=192.168.6.111
ethaddr=002200:26
updt_all=nand erase clean;vfd updt_ker;updt_img
updt_boot=vfd LD;tftp 0x80000000 u-boot.bin;nand erase 0x00000000 0x00040000;nand write.jffs2 0x80000000 0x00000000 $filesize;vfd _End
updt_ker=vfd LD;tftp 0x80000000 vmlinux.ub.cram;nand erase 0x00500000 0x00300000;nand write.jffs2 0x80000000 0x00500000 $filesize;vfd _End
updt_img=vfd LD;tftp 0x80000000 root_ubi.img;nand erase 0x00800000 0x6000000;nand write.jffs2 0x80000000 0x00800000 $filesize;vfd _End
erase_config=nand erase 0x00400000 0x00100000
erase_eeprom=mw.b 80000000 ff 1000;eeprom_i2c write 0x80000000 0 0x001000
erase_env=nand erase 0x060000 0x20000

i think the following sequence should flash back your original loader to the loaders space:

usb reset
fatload usb 0:1 80000000 mtd0
nand erase 0x00000000 0x00040000
nand write.jffs2 0x80000000 0x00000000 $filesize

before really flashing to the loader space i would prefer to test the sequence at another non critical flash space and check the result:

usb reset
fatload usb 0:1 80000000 mtd0
nand erase 0x00100000 0x00040000
nand write.jffs2 0x80000000 0x00100000 0x40000
nand read.jffs2 0x80100000 0x00100000 0x40000
cmp.b 0x80100000 0x80000000 0x40000

when the answer is correct with '262144 bytes are the same' i would give it a try to flash to the loader space.
take care about the name of the binary file: in the example above i called it just 'mtd0' without any suffix. even take care that the file is really loaded (262144 bytes read...) after the fatload command.
well, good luck and hopefully we dont need a jtag

PS:
when the loader is flashed correctly you should delete the environment by

run erase_env

and restart the box. the restart will show a crc-error and set the embedded bootargs. after that the normal ird-update procedure is needed to flash the firmware of the proper reseller (remember we destroyed it with the flash test sequence)

[kader_73]

if I understand correctly, so I have to do a test with this sequence :

usb reset
fatload usb 0:1 80000000 mtd0
nand erase 0x00100000 0x00040000
nand write.jffs2 0x80000000 0x00100000 0x40000
nand read.jffs2 0x80100000 0x00100000 0x40000
cmp.b 0x80100000 0x80000000 0x40000

which is for no critical sapce ; and if the answer is '262144' then i can flash to loader space with the first sequence . right ?

regards

- - - Updated - - -

if I understand correctly, so I have to do a test with this sequence :

usb reset
fatload usb 0:1 80000000 mtd0
nand erase 0x00100000 0x00040000
nand write.jffs2 0x80000000 0x00100000 0x40000
nand read.jffs2 0x80100000 0x00100000 0x40000
cmp.b 0x80100000 0x80000000 0x40000

which is for no critical sapce ; and if the answer is '262144' then i can flash to loader space with the first sequence . right ?

regards

[solala]

yep, if any errors or unexpected outputs occur, then post them here before going on

[kader_73]

Oh yes, well done

It worked as expected , now my box is working fine again with v2.11.87 on board .

so THANK to you solala ; as you said "...., i think until weekend your box will run again with the right loader " and it is .

also to harryhase , Audioniek and everyone participated to solve this case .

Regards

[solala]

yipeeee

[samkooke]

hello i have even problem look the log:

usb upgrage
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Interface: USB
Device 0: Vendor: SanDisk Prod.: Cruzer Blade Rev: 1.26
Type: Removable Hard Disk
Capacity: 3819.0 MiB = 3.7 GiB (7821312 x 512)
Partition 1: Filesystem: FAT32 "NO NAME "
reading usb_uboot.img
reading usb_config.img
usb_config.img not found
reading usb_kernel.img
usb_kernel.img not found
reading usb_rootfs.img
usb_rootfs.img not found
reading usb_uboot.img
.....................
Skipping bad block at 0x00000000
Skipping bad block at 0x00020000


Bad block at 0x0 in erase block from 0x0 will be skipped
Bad block at 0x20000 in erase block from 0x20000 will be skipped
Bad block at 0x60000 in erase block from 0x60000 will be skipped
Bad block at 0x80000 in erase block from 0x80000 will be skipped
Bad block at 0xa0000 in erase block from 0xa0000 will be skipped
Bad block at 0xc0000 in erase block from 0xc0000 will be skipped
Bad block at 0xe0000 in erase block from 0xe0000 will be skipped
Writing data at 0x116800 -- 100% complete.


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... 1 Storage Device(s) found
reading uImage

** Unable to read "uImage" from usb 0:1 **
## Booting image at 80000000 ...
Image Name: 7119
Image Type: SuperH Linux Firmware (gzip compressed)
Data Size: 224775 Bytes = 219.5 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Wrong Image Type for bootm command

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

Bad block at 0x60000 in erase block from 0x60000 will be skipped
Bad block at 0x80000 in erase block from 0x80000 will be skipped
Bad block at 0xa0000 in erase block from 0xa0000 will be skipped
Bad block at 0xc0000 in erase block from 0xc0000 will be skipped
Bad block at 0xe0000 in erase block from 0xe0000 will be skipped
reading NAND page at offset 0x100000 failed
3145728 bytes read: ERROR
## Booting image at 80000000 ...
Image Name: 7119
Image Type: SuperH Linux Firmware (gzip compressed)
Data Size: 224775 Bytes = 219.5 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Wrong Image Type for bootm command
7119 >

[Audioniek]

Unless you did something wrong and as far as I can see, this is not a wrong bootloader in flash but damaged flashmemory (that is: a hardware error). You fail to mention which loader is (supposed to be) present in de receiver and which receiver its its; apparently you are trying to run an USB image for a Fortis HS7119 from a 4Gbyte Sandisk stick.

To begin with the beginning: what appears in the receiver display immediately after power on (should be L7.06 or L7.07 for an HS7119) and what receiver model are we talking about precisely?

If the receiver still shows a version number at power on, first try reflashing the correct boot loader using the channel-up procedure.

Regards,

Audioniek.

[samkooke]

hello Audioniek my problem is 7119 blocked on 7119 and flashes red impossible from put the original. loader L7.06. sorry name of recever is xeobox hs-7119.