[HELP]: Wrong u_boot into flash

[kader_73]

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 )


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 :


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.


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]

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]

@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 (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]

.......
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]

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]

goodmorning ;

@ solala

here is the output of command given above :


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 >


7119 > help
? - alias for 'help'
askenv - get environment variables from stdin
autoscr - run script from memory
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
bootmenu- check boot key.
bootp - boot image via network using BootP/TFTP protocol
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
dhcp - invoke DHCP client to obtain IP/boot params
echo - echo args to console
eeprom - EEPROM sub-system
ethaddr - read/write MAC address EEPROM sub-system
exit - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fsinfo - print information about filesystems
fsload - load binary file from a filesystem image
go - start application at address 'addr'
help - print online help
i2c - I2C sub-system
icrc32 - checksum calculation
iloop - infinite loop on address range
imd - i2c memory display
iminfo - print header information for application image
imm - i2c memory modify (auto-incrementing)
imw - memory write (fill)
inm - memory modify (constant address)
iprobe - probe to discover valid I2C chip addresses
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
ls - list files in a directory (default /)
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing)
mtdparts- define flash/nand partitions
mtest - simple RAM test
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
pmb - displays the contents of the PMB
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sleep - delay execution for some time
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
usb - USB sub-system
usbboot - boot from USB device
usbupg - update s/w from usb host memorystick
version - print monitor version
vfd - put string to front display.
7119 >


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

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]

... 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]

output help nand

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

7119 > nand info

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


output command :

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]

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]

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



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

[samkooke]

good evening what demo do you have?

[kader_73]

good evening ;

it's an hs7819 reseller ID 27 xx 20 A0

[samkooke]

forever clone to xeobox 7200 id 271520A0 xeobox 270920A0.

[kader_73]

forever clone to xeobox 7200 id 271520A0 xeobox 270920A0.

Sorry , but reading your PM i guess you don't understand what is going on here , anyway , thanks for trying help !!!

[kader_73]

Hello ;


.........
oh, and just to prepare the next steps ..........

Should I wait more for the next steps, or maybe there is no chance ? :confused:

Regards

[kader_73]

Doing some research in stlinux site, I found this


For NAND Flash

In the case of NAND flash, the flash should be explicitly erased, prior to writing to it.
In the case of NAND, then most access operations need to be multiples of certain page/block sizes. For simplicity, the following code assumes that u-boot.bin fits in 256 KiB (0x40000). However, you may use smallest figures that are appropriately aligned.

MB680> nfs $load_addr /export/u-boot.bin
MB680> nand erase 0 40000
MB680> nand write $load_addr 0 40000


Since the U_Boot variable "load_addr=0x80000000" , can I use these two commands as prescribed after the mtd0 file being loaded on RAM.

I'm trying doing my best , but still need help .

Regards

[kader_73]

hello again ;

still with my f*** machine, i tried to boot from usb as said in the help using usbboot command , mtd0 in root fat32


7119 > usbboot 0x80000000 0:1

Loading from USB device 0, partition 1: Name: usbda1
Type: U-Boot

** Bad Magic Number **
7119 >

[harryhase]

please try and post output



set bootcmd "nand read.jffs2 0x80000000 0x00500000 0x00300000; bootm 0x80000000"

boot

[solala]

hi harry,
was vermutest du am offset 0x500000? soll da in dem flashlayout der ursprünglichen firmware nen kernel liegen? obwohl ich die kiste nicht kenne wäre das sehr ungewöhnlich

[harryhase]

Das sind die environment von meiner 7119; Irgendwas hat er ja sich ja geflasht und einen bootloader hat er ja auch;
Die Idee dahinter ist ein Image lauffähig zu bekommen; Dann den Reseller per plugin ändern; dann richtigen (definierten) Bootloader rein und ein Image wieder drüber braten.
Da ich nicht weiß welche resellerid er jetzt hat kann er weder Image noch bootloader drüber flashen.

Du hast bestimmt noch was anderes im Kopf?!

[Audioniek]

@solala: The memory layout of the Fortis HS7119 using Fortis stock firmware is this:
Fortis HS7119 L7.07 memory map
------------------------------

By memory address:

Start End Size Type Purpose MTD IRD fixed DecSt DecSz
0x000000000 - 0x0003FFFFF 0x000400000 Flash, bootloader 0 0 Y 0 MB 4 MB
0x000400000 - 0x0004FFFFF 0x000100000 Flash, configuration 5 2,3,4,5? Y 4 MB 1 MB
0x000500000 - 0x0007FFFFF 0x000300000 Flash, kernel 1 6 Y 5 MB 3 MB
0x000800000 - 0x0067FFFFF 0x006000000 Flash, application 2 1 Y 8 MB 96 MB
0x006800000 - 0x00FFFFFFF 0x009000000 Flash, user? 6 9? Y 104 MB 144 MB
0x00F800000 - 0x00FFFFFFF 0x000800000 Flash, ? 8 - Y 248 MB 8 MB
0x800000000 - 0x8FFFFFFFF 0x100000000 RAM

With loader 7.XX Fortis is back to flashing partitions at fixed addresses, IRD partition types 7, 8 and probably 9 are no longer flashable with a .IRD file.

Regards,

Audioniek.

[kader_73]

good morning ,

Just for more info , before uploading the u-boot to my box i changed the reseller id to 27 01 00 A0 with boxkit . the origin one was 27 xx 20 A0 , Ld 7.27

Regards

[kader_73]

please try and post output



set bootcmd "nand read.jffs2 0x80000000 0x00500000 0x00300000; bootm 0x80000000"

boot




hi harry,
was vermutest du am offset 0x500000? soll da in dem flashlayout der ursprünglichen firmware nen kernel liegen? obwohl ich die kiste nicht kenne wäre das sehr ungewöhnlich

here the printenv


7119 > printenv
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
mtdids=nand0=gen_nand.1

Environment size: 699/131068 bytes
7119 > mtdboot=nand read.jffs2 0x80000000 0x00060000 0x00300000; bootm 0x80000000
ERROR: There is a global environment variable with the same name.
Unknown command 'read.jffs2' - try 'help'
## Booting image at 80000000 ...
Bad Magic Number
7119 >

[solala]

the output of printenv is _not_ the output of the original loader. remember: there was a crc error right at the first start you posted above. so the actual loader overwrote the env with his own proper values.

[kader_73]

well understood ,
there is some news here , i could using usbupg command uploading the usb_uboot.img file( for the sf918+ included in the backup folder of the startkit)to my receiver , here is the output on startup


' Îs

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

Reading data from 0x7ff800 -- 100% complete.
3145728 bytes read: OK
Bad Magic Number
HDK7111>


also I could confirm with "sscom32" connected that the reseller id in now is 27 01 00 A0 ; do you think that i can upgrade using porter loader the last octagon 918gse+ SW without risk ? Or mybe should i use a reseller changer to change 1008GSE+ to 00 A0 and then load it to the box to get the correct loader in when the next restart .

regards

[harryhase]

Octagon SF-918G SE+ Difference:270100A0

Do you have tried to flash a 918g image? i'm wondering why the image didn't start?

some environment are diffrent to my 918g, but i can't see a real problem, but you can try (without save !!!)


set board "hdk7111_INPUT_CLOCK_RATE"
set targetname "muso"
set bootcmd "nand read.jffs2 0x80000000 0x00500000 0x00300000; bootm 0x80000000"
set hwnfconf "setenv nwhwnet device:eth0,hwaddr:$ethaddr"
set ipconf "setenv ipaddrcfg ip "$ipaddr:$serverip:$gateway:$netmask:sdk:eth0:off"
set updt_all "nand erase clean;vfd updt_ker;updt_img"
set updt_boot "vfd LD;tftp 0x80000000 u-boot.bin;nand erase 0x00000000 0x00040000;nand write.jffs2 0x80000000 0x00000000 $filesize;vfd _End"
set updt_ker "vfd LD;tftp 0x80000000 vmlinux.ub.cram;nand erase 0x00500000 0x00300000;nand write.jffs2 0x80000000 0x00500000 $filesize;vfd _End"
set updt_img "vfd LD;tftp 0x80000000 root_ubi.img;nand erase 0x00800000 0x6000000;nand write.jffs2 0x80000000 0x00800000 $filesize;vfd _End"
set erase_config "nand erase 0x00400000 0x00100000"
set erase_eeprom "mw.b 80000000 ff 1000;eeprom_i2c write 0x80000000 0 0x001000"
set erase_env "nand erase 0x060000 0x20000"
set stdin "serial"
set stdout "serial"
set stderr "serial"

boot

[kader_73]

i'm taying flashing with 918g+ now , but as you know the porter take wile , and i hope get the box start after that . if so that will be my lucky day . and then i can usr the boxkit and change the reseller id to 20 A0 again . i hope so !!!

[harryhase]

boxkit is working fine ... but with the known reseller it should be pssible to flash the right bootloader (maybe better asking solala before flashing new bootloader) and remeber you will need the right environment for the loader ..

[kader_73]

yes maybe you're right , i stop dowloading now , waiting Solal answer .

[harryhase]

you can try #26 (http://www.hdmedia-universe.com/board/showthread.php?6530-HELP-Wrong-u_boot-into-flash&p=76555&viewfull=1#post76555) above

[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 7178


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:eth0:of f
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:eth0:off 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=00:11:22:33:00: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 :sm49:

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 :ba31:

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]

:36_2_25: 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.

[samkooke]

hello all no one to help me.

[solala]

as audioniek said: the box is possibly broken (all those bad block messages are not normal) so i think you should send it back to your dealer

[samkooke]

ok thank you solala it is not guaranteed by usb it functions when I put picture HDMU.

[Audioniek]

my problem is 7119 blocked on 7119 and flashes red

From this I grasp the display shows 7119 immediately after power on, combined with a blinking red LED. First of all, the original boot loader cannot
display the text 7119, not even a broken one (it should display L7.00, L7.06 or L7.07). The blinking red LED shows there is some code executing and that the loader cannot find an image anywhere. It is highly probable that the boot loader is just fine.

That leaves two options:
1.NAND flash memory has a hardware failure
2.There is no valid image in flash and the receiver cannot read your USB stick properly (or the image on the stick is corrupt).

Try this:
Power the receiver off by pulling the DC plug on the back. Press and hold channel down on the receivers front panel and insert the DC power plug again. Keep holding the front panel key until the display shows OFF, then release it.

Flash a factory image using the channel up procedure. After a restart this should yield a running stock firmware with steady green LED. If it does, consider using another USB stick. Not all sticks work well; the receiver is rather particular in this respect.

Regards,

Audioniek.

[samkooke]

good evening Audioniek I have flashed in internal flash at first placed upgrade_loader_7119.ird and usb_kernel.img and usb_rootfs.img and flashes red and green I have is handling but it does not work thanks.

[kader_73]

hello ,
@Audioniek,

First of all, the original boot loader cannot
display the text 7119, not even a broken one (it should display L7.00, L7.06 or L7.07).
that would be the case if the receiver contains the original bootloader, but I think in the case of our friend , he alredy flashed the box with "upgrade_loader_boxtype.ird" - an ird u_boot buitl for loading kernel and rootfs from flash - contained in the startkit from one of HDBOX E2 image.
that one show the boxtype on the vfd as soon as started.

@ samkook
in the kit there a folder named "back" wherein there is file named "usb_uboot.img" ( the original boot for your box) , try to use the current enverenment commands to flash it again into flash and then try with any .ird file ( not kernel and rootf img file) to restor it .

Regards

[samkooke]

hello kader_73 I have made this action several times hopeless always blocked thanks.

[Audioniek]

So far you have not told us much what happens EXACTLY after a flash try except the information-less statements "blocked" and "does not work", so unless you tell us something we can work with, we cannot do much. The following is therefore a complete guess.

If you indeed have flashed the file kader_73 suspects, channel-up should still work, provided the .IRD you try to flash has the correct resellerID. I suspect he current resellerID in this crap loader is 270200A0. If the resellerID's do not match te Original loader displays Er.10; what the current loader does in such cases I have no way of knowing.

So here is the next option: download this file (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=1111&d=1342210676) and unpack it. Use a good reseller changer to set the resellerID to 270200A0 (many change the A0 to 00). Flash the resulting file using channel-up. If successful, the resellerID of the receiver is 270100A0 (Octagon SF918G SE+).

I do not know why people change bootloaders without need; Enigma2 and Neutrino can be built to run with an unchanged factory boot loader with an HS7119 (and on a HS7429 and HS7819 for that matter). Why almost nobody does this is not clear to me.

Ergo: NEVER, absolutely NEVER, change a bootloader unless:

you know what you are doing,
you want to say goodbye to the not-so-bad and very stable factory firmware,
you know beforehand what resellerID the receiver has after the change,
you want to lose most, if not all recovery possiblities and your warranty if there is one,
you are prepared to run into serious trouble or even brick your receiver if something goes wrong,
there is a way back you completely understand and are capable of performing it with the means at your disposal,
AND finally: there is a very good reason for changing the loader (to be able to run Enigma2 is not one).


Regards,

Audioniek.

[solala]

... but 5 years ago there was no possibility to do ANYTHING useful with the original loaders ;)

[samkooke]

So far you have not told us much what happens EXACTLY after a flash try except the information-less statements "blocked" and "does not work", so unless you tell us something we can work with, we cannot do much. The following is therefore a complete guess.

If you indeed have flashed the file kader_73 suspects, channel-up should still work, provided the .IRD you try to flash has the correct resellerID. I suspect he current resellerID in this crap loader is 270200A0. If the resellerID's do not match te Original loader displays Er.10; what the current loader does in such cases I have no way of knowing.

So here is the next option: download this file (http://www.hdmedia-universe.com/board/attachment.php?attachmentid=1111&d=1342210676) and unpack it. Use a good reseller changer to set the resellerID to 270200A0 (many change the A0 to 00). Flash the resulting file using channel-up. If successful, the resellerID of the receiver is 270100A0 (Octagon SF918G SE+).

I do not know why people change bootloaders without need; Enigma2 and Neutrino can be built to run with an unchanged factory boot loader with an HS7119 (and on a HS7429 and HS7819 for that matter). Why almost nobody does this is not clear to me.

Ergo: NEVER, absolutely NEVER, change a bootloader unless:

you know what you are doing,
you want to say goodbye to the not-so-bad and very stable factory firmware,
you know beforehand what resellerID the receiver has after the change,
you want to lose most, if not all recovery possiblities and your warranty if there is one,
you are prepared to run into serious trouble or even brick your receiver if something goes wrong,
there is a way back you completely understand and are capable of performing it with the means at your disposal,
AND finally: there is a very good reason for changing the loader (to be able to run Enigma2 is not one).


Regards,

Audioniek.

hello Audioniek I flasher enigma2 in internal flash last year it function well and since 15 days more image simply turn on the front panel 7119 and flashes red and green and impossible to put the original thanks.

[kader_73]

Hello ,

@ Audioniek

I do not know why people change bootloaders without need; Enigma2 and Neutrino can be built to run with an unchanged factory boot loader with an HS7119 (and on a HS7429 and HS7819 for that matter). Why almost nobody does this is not clear to me

The fact is that untill now there is no E2 image for flash for these Fortis model boxs ( hs 7x19 ), despite that the hardware provides the ability to do it ( NAND flash with 256 M size) . I personally uses the flash-tool from your git and it works perfect , I even tested with HDMU image - copaying the whool image to release folder , keeping the original uImage and modules and i have the HDMU on flash - just for fun ) .
Most of people want to have Enigma2 into flash , and as far as i know , only Capital , HDready and Infinty images (from a slovaque team i think !!) are built for . and these images need the specifique u-boot ( not original one ) to be loaded on flash .
the question is : why both HDMU nad PKT teams , deans of E2 sh4 don't provide flash image for these models , is this for some reasons legality ?

Regards

[samkooke]

hello kader is exactly that the designer of enigma2 image is jirkas :platino hdready capitol and infinity NAND flash.

[harryhase]

what is the advantage, flashing emigma into flash?

[samkooke]

hello must ask the designer's image:gigablue,vu+,xtrend,dreambox.

[kader_73]

what is the advantage, flashing emigma into flash?

I don't know if there is a listed difference ragerding hardware performence (I am not a technician in the field) but I think there must be.

for someone who has chosen enigma, why does he keep an app that will never use or at least rarely , do you imagine yourself installing one system on your PC disck for using an other one on usb port ( for me, that's pretty close).
in addition, you will have to condemn a usb port which you can use it for anything else .

Regards

[harryhase]

okay, no advantage ;)
For more usb ports i can use a hub.
Booting from usb, i'm able to use a fortis image in flash AND an enigma2 on usb.
For watching tv the fortis image is the best (and maybe in some month must have for ci+)
For playing aroudn enigma is the best.

[samkooke]

hello harryhase exactly the last image is both functions enigma2 or original captitol or infinity enigma2 if you can test it and tell us what thanks.

[harryhase]

do you have a link for us, maybe per pn

[samkooke]

send me a pm

[Audioniek]

... but 5 years ago there was no possibility to do ANYTHING useful with the original loaders ;)

You are right, but I am talking about nowadays, and the community has learnt a lot in the mean time. As for Fortis HD receivers, ALL can run Neutrino in flash with the factory bootloader without even changing the bootargs, and as far as Enigma2 goes, the same is true but for the only limiting factor there is the available amout of flash memory, which rules out the first and second generation of Fortis HD receivers, apart from the HS8200.

As kader_73 confirms, just use the patches and .configs from my git; the flash environment of it even creates directly flashable .IRD files, provided you feed it the correct resellerID.

As far as I am concerned this will be repeated with the fourth generation of Fortis receivers, I have reached the point that the kernel starts and the /etc/init.d/rcS is executed.

In summary: nowadays there is no longer a need to change the factory bootloader on a Fortis HD receiver.

Regards,

Audioniek.

- - - Aktualisiert - - -


hello Audioniek I flasher enigma2 in internal flash last year it function well and since 15 days more image simply turn on the front panel 7119 and flashes red and green and impossible to put the original thanks.

Well, you have done it again: not providing the info I asked for, but just telling (again) "it does not work". So again:

What is the resellerID in the current bootloader? (I can tell you up front it is NOT in the standard location, so you have to ask the author of your current loader.)
What does the display say when you try to flash the correct factory loader after using a good resellerchanger?
What does the serial log say when you try to flash the correct factory loader after using a good resellerchanger?

If you cannot provide a sensible anser to these questions, we cannot help you.

Regards,

Audioniek.

- - - Aktualisiert - - -


what is the advantage, flashing emigma into flash?

1. On some models you use the only available USB port, so a hub is required to be able to record;
2. Speed: in flash everything runs quite a bit smoother, boot time is halved (worse even with a hub);
3. WAF (Wife Acceptance Factor) is zero or lower, in particular with a hub;
4. These receivers where never designed to run an image off an USB stick: in flash is technically more correct;
5. A running Enigma2 constantly writes to the USB stick. USB sticks are not suitable for this kind of use as most do not have wear levelling techniques.

In short: only use a USB stick if you absolutely want to have the choice between factory firmware or Enigma2 at each receiver start.

Regards,

Audioniek.

[samkooke]

hello Audioniek my recever is dead for internal flash but by usb is work bad block:NAND: nand_read_bbt: Bad block at 0x00000000
is no good thanks.

- - - Updated - - -


hello Audioniek my recever is dead for internal flash but by usb is work bad block:NAND: nand_read_bbt: Bad block at 0x00000000
is no good thanks.

last image is very good infinity enigma2 do both .

[kader_73]

Bonsoir samkooke ,

Ce que tu annonce là ne fait pas avancer les choses , c'est claire qu'il y a des block défectueux dans ton flash NAND que le boot ne peut pas charger pour démarrer le système . alors qu'en usb ça ne pose pas de problème du moment que ce dernier est intacte .

Ce que Audioniek essaye de dire , c'est donner plus d'infos sur l’état actuelle de votre boite a savoir :
quelle est le resellerID dans le boot actuelle ( cela il suppose déjà qu'il n'est pas à sa localisation standard ) , toi seul tu peu savoir sur quel resellerID était ton demo avant de perdre le flash.
qu'est ce que ça affiche sur le VFD lorsque tu essaye d'introduire l'original soft avec le bon resellerID.
est qu'est ce que le serial log ( putty ) affiche lors du flashage ( avec le bon resellerID toujours). si possible afficher le log ici .

A toi de fournir ces infos pour pouvoir t'aider ; alors si tu te contente avec l'image sur USB et tu veux rester sur celle ci et laisser tomber le flash , cela ne fait de mal à personne .


cdlt

[samkooke]

bonjour kader j'ai tres bien compris ce que disais Audioniek le recepteur ne repond a rien sur le vdf il est sur 7119 et clignote rouge et vert le resellerID de mon recepteur etais:270900A0 j'ai tout essayer il ne prend plus les fichiers IRD il bloque sur usb merci a tous qui ont essayer de m'aider.

[Abdallah Mef]

hello everybody ,,i have the same problem,,i flash wrong boot to my forever 7420 i read all the replies but i cant understand exactly
mr kader how i can flash my original boot with the original file usb_boot.img i find it in forum ,,the currently id of my device is 7810
thanks,

[Audioniek]

We need to know if your receiver still shows some signs of life on the serial port when it is switched on. Can you provide that info?

Regards,

Audioniek.

[kader_73]

hello ;

@Abdallah Mef ; as Audioniek said , we need to know if is stilll possible to access to the receiver's flash using the serial port , if so the case can be solved by writing the correct U_boot into the right address.

to know this, so connect your STB to a terminal via serial port , open the console ( i e putty -speed 115200) and switch on your receiver. If there is anything displayed, post the output here.

b Regards

[lolo909]

Hello,
could you help me please to restore Openbox s6 with L6.26 loader. Reseller ID is changed to Octagon 1008SE+.
My kids watch cartoons on it so it's crucial tuner at home :)
I had enigma on usb stick but it crashed and I can't boot up tuner from usb or flash again.
I can upload octagon firmware with Porter or CH UP method but it doesn't want to start and hangs up.
Below logs from putty:

without usb

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.09.21 00:31:14 =~=~=~=~=~=~=~=~=~=~=~=
FrTs


% Í(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
stopping USB..


(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear 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 **


init started: BusyBox v1.14.2 (2012-03-12 15:08:37 KST)
root::0:0:root:/root:/bin/sh

with usb

% Í(Re)start USB...
Front USB: scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
system volume information/
268435456 root.img
2990942 uimage


2 file(s), 1 dir(s)


reading uImage
.................................................. .................................................. .................................................. .................................................. .................................................. ..........................................
ret=> 2990942
Wait [1]
Wait [2]
Wait [3]
Wait [4]
Wait [5]
Wait [6]
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /mnt/root.img is mounted.
/mnt/root.img: recovering journal
/mnt/root.img: clean, 6235/65536 files, 159121/262144 blocks
mount root
INIT: version 2.86 booting
init frontpanel
Mount /dev in tmpfs
Copying device nodes to /dev
Starting portmap daemon....
Starting DEBUG Interface
Mounting local filesystems...
Cleaning /tmp.
Hostname: SF918SE+.
starting telnetd
init stmfb
LOADING MODULES
load a firmware
copLoadFile (file /boot/audio.elf)
ustslave: Kernel Version: 24
base_address 0x40400000
seeking to 0
seeking to 5e00
seeking to 12460
seeking to 1ab60
seeking to 154300
seeking to 154338
seeking to 154370
seeking to 191a58
seeking to 191a60
seeking to 191a68
seeking to 191a70
seeking to 1aae40
seeking to 1aaf00
load v firmware
copLoadFile (file /boot/video.elf)
ustslave: Kernel Version: 24
base_address 0x40000000
seeking to 0
seeking to e2dc0
seeking to e2df8
seeking to e2e30
seeking to e8fe8
seeking to e8ff4
seeking to e9000
seeking to 115710
seeking to 117800
init embx
init AVS
init player 191
starting vsftpd
Starting FTP server: vsftpd.
Model: hs7110
vBoxType: 7
Input device name: "TDT RC event driver"
Selected Remote: Fortis HDBOX RemoteControl
RemoteControl Map:
MENU - 04 - 139
RED - 4B - 398
GREEN - 4A - 399
YELLOW - 49 - 400
BLUE - 48 - 401
EXIT - 1C - 174
TEXT - 0D - 388
EPG - 08 - 365
REWIND - 58 - 168
FASTFORWARD - 5C - 208
PLAY - 55 - 207
PAUSE - 07 - 119
RECORD - 56 - 167
STOP - 54 - 128
STANDBY - 0A - 116
MUTE - 0C - 113
CHANNELUP - 5E - 104
CHANNELDOWN - 5F - 109
VOLUMEUP - 4E - 115
VOLUMEDOWN - 4F - 114
INFO - 06 - 138
OK - 1F - 352
UP - 00 - 103
RIGHT - 02 - 106
DOWN - 01 - 108
LEFT - 03 - 105
RECALL - 09 - 396
ZOOM - 0B - 372
VFORMAT - 0E - 371
RESOLUTION - 0F - 375
TVRADIO - 1A - 373
SLEEP - 1E - 409
OPEN - 40 - 394
FAV - 41 - 364
CHECK - 42 - 353
UPUP - 43 - 414
DOWNDOWN - 44 - 415
NEXT - 4C - 407
LAST - 50 - 412
PIP - 51 - 357
SWAP - 52 - 354
LIST - 53 - 370
0BUTTON - 10 - 11
1BUTTON - 11 - 2
2BUTTON - 12 - 3
3BUTTON - 13 - 4
4BUTTON - 14 - 5
5BUTTON - 15 - 6
6BUTTON - 16 - 7
7BUTTON - 17 - 8
8BUTTON - 18 - 9
9BUTTON - 19 - 10
Frontpanel Map:
STANDBY - 00 - 116
OK - 06 - 352
MENU - 05 - 139
VOLUMEUP - 04 - 115
VOLUMEDOWN - 03 - 114
CHANNELUP - 01 - 104
CHANNELDOWN - 02 - 109
Supports Long KeyPress: 1
processComplex >
period 10, delay 140
Using period=10 delay=140
[SEM] DOWN
showSinglePic /boot/bootlogo.mvi
VIDEO_SELECT_SOURCE MEMORY (Success)
VIDEO_PLAY (Success)
VIDEO_CONTINUE: (Success)
VIDEO_CLEAR_BUFFER: (Invalid argument)
LOADING E2
starting e2->

print command

bootdelay=0
baudrate=115200
board=hdk7111_INPUT_CLOCK_RATE
targetname=muso
hwnfconf=setenv nwhwnet device:eth0,hwaddr:$ethaddr
nfsserverconf=setenv nfs_server nfsroot=$serverip
ipconf=setenv ipaddrcfg ip=$ipaddr:$serverip:$gateway:$netmask:sdk:eth0:of f
cramfsbootargs=run hwnfconf;run ipconf;setenv bootargs console=ttyAS0,115200 roo t=/dev/mtdblock3 rootfstype=squashfs $ipaddrcfg nwhwconf=$nwhwnet bigphysarea=50 00 stb7111:eth0:off stmmaceth=msglvl:0,phyaddr:2,watchdog:4000,rxsize: 16 logleve l=0 $MTD
nfsbootargs=run hwnfconf;run nfsserverconf;run ipconf;setenv bootargs console=tt yAS0,115200 root=/dev/nfs $nfs_server:/opt/STM/STLinux-2.3/devkit/sh4/target,nfs vers=2,rsize=4096,wsize=8192,nolock,tcp nwhwconf=$nwhwnet $ipaddrcfg stmmaceth=m sglvl:0,phyaddr:2,watchdog:4000,rxsize:16 bigphysarea=5000
ipaddr=192.168.5.253
serverip=192.168.5.55
updt_boot=vfd LD;tftp 0x80000000 u-boot.bin;protect off 1:0-1;erase 1:0-1;cp.b 0 x80000000 0xa0000000 $filesize;protect on 1:0-1;vfd _End
updt_boot_all=vfd LD;tftp 0x80000000 u-boot.bin;protect off 1:0-255;erase 1:0-25 5;cp.b 80000000 0xa0000000 $filesize;protect on 1:0-255;vfd _End
updt_appb=vfd LD;tftp 0x80000000 app.img;protect off 1:64-103;erase 1:64-103;cp. b 80000000 0xa0800000 $filesize;protect on 1:64-103;vfd _End
updt_user=vfd LD;tftp 0x80000000 user.img;protect off 1:224-255;erase 1:224-255; cp.b 80000000 0xa1c00000 $filesize;protect on 1:224-255;vfd _End
erase_config=protect off 1:216-223;erase 1:216-223;protect on 1:216-223
erase_env=protect off 1:2-2;erase 1:2-2;protect on 1:2-2
filesize=2DC
ip=ip=192.168.0.123:192.168.0.2:192.168.0.1:255.25 5.255.0:stb7111:eth0:off
stmmaceth=stmmaceth=msglvl:0,phyaddr:2,watchdog:40 00,rxsize:16
usbbootargs=run hwnfconf; run ipconf; setenv bootargs console=ttyAS0,115200 prin tk=0 root=/dev/sda2 rw rootdelay=5 ${ip} nwhwconf=$nwhwnet ${stmmaceth} bigphysa rea=6000 coprocessor_mem=4m@0x40000000,4m@0x40400000 init=/bin/devinit
usbboot=if fatload usb 0:1 84000000 uImage; then vfd "USB"; run usbbootargs; boo tm 84000000; fi
mtdboot=vfd "Flash"; run cramfsbootargs; bootm a0060000
bootcmd=vfd "PKT"; sleep 2; vfd "Scan"; if usb reset; then run usbboot; fi; run mtdboot
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:1e:b8:04:94:4e


updt_ker=vfd LD;tftp 0x80000000 vmlinux.ub.cram;protect off a0060000 +$filesize; erase a0060000 +$filesize;cp.b 80000000 a0060000 $filesize;protect on a0060000 + $filesize;mtd_update;vfd _END
MTD=mtdparts=physmap-flash:384K(Boot_firmware),1792K@0x00060000(kernel) ,7040K@0x 1320000(App),14464K@0x220000(ROOT_FS),2944K@0x1040 000(Device),1M@0x1b00000(CONFI G),4M@0x01c00000(User),32M@0(All),7040K@0x1320000( APP_ORG),7040K@0x1320000(APP_B AK)
updt_img=vfd LD;tftp 0x80000000 root.img;protect off a0220000 +$filesize;erase a 0220000 +$filesize;cp.b 80000000 a0220000 $filesize;protect on a0220000 +$filesi ze;mtd_update;vfd _END
updt_dev=vfd LD;tftp 0x80000000 device.img;protect off a1040000 +$filesize;erase a1040000 +$filesize;cp.b 80000000 a1040000 $filesize;protect on a1040000 +$file size;mtd_update;vfd _END
updt_app=vfd LD;tftp 0x80000000 app.img;protect off a1320000 +$filesize;erase a1 320000 +$filesize;cp.b 80000000 a1320000 $filesize;protect on a1320000 +$filesiz e;mtd_update;vfd _END


Environment size: 3217/16380 bytes
HDK7111>

[Audioniek]

First of all, you have the correct loader in your receiver, as it is a Fortis HS7810A variant. The files you have attached show that the receiver tries to start an image for a HS7110 (Octagon SF918SE+) from USB, which is a different receiver.

So give it a try with the correct image, one for an Octagon SF1008SE+.

You should also be able to put an original Octagon SF1008SE+ factory firmware into flash but using the channel-up procedure, you do not need Porter for that. Are you sure the reseller in the loader is set to 250200A0? If not you should get Er10 messages at the start of flashing.

Regards,

Audioniek.

[lolo909]

Thank you for answer.
I've tried many different versions of images for SF1008SE+ to start (both HDMU and PKT).
I quoted logs for SF918SE+ because it was last one I tried to start. (I could upload it before and tuner worked without display.)


I'm able to put an original Octagon SF1008SE+ factory firmware into flash through channel-up procedure and Porter as well. Everytime with succes but it doesn't want to start.


How to check the reseller number in already uploaded loader?

[Audioniek]

The begin with your last question: there is no easy way to find out the reseller ID in the loader. I know of two ways. The first is flash a factory firmware. If this succeeds the reseller ID in the firmware file matched and can be displayed in a hex editor: they are the four bytes at offset 6 into the .ird file. The other way is more elaborate. In a telnet session, dump /dev/mtd0 into a file on an attached USB stick with cat /dev/mtd0 > /STORAGE/USB0/<filename>. This is the binary boot loader. Then display its contents in a hex editor. The reseller ID is at offset 0x0470. To check you have done it right, look at the three bytes following the reseller ID: they should be 00 26 06 (the bootloader version is reverse order)

After your first comment (the things you already tried) I am pretty sure your receiver has a hardware defect, most likely a RAM chip of the SoC itself.

The only thing I can think of that I would try is reflash the boot loader itself, as both channel-up and Porter still seem to work. In that case I would revert to the beginning and reflash the original Openbox loader, followed by an original Openbox firmware. If problems still persist, it is a hardware error for sure.

Regards,

Audioniek.

[lolo909]

I can't flash a factory firmware. Display says Er.10 everytime I want to upload Loader or Software for Openbox S6. I'm rather sure that I uploaded loader for Octagon 1008SE+. I will try and dump /dev/mtd0 into a file later.


Is there any option to change boot loader again? Could I change boot loader if I had backup of the original mtd0? I read about it in this thread few posts above.

[Audioniek]

If the display says Er.10 when trying to flash, the .ird file has a different reseller ID than the one currently in the boot loader.

The only option to change the boot loader is to reflash it, in this case using channel-up or Porter. For this you need a .ird file with a boot loader containing the reseller ID you want in it (I recommend the original Openbox S6 ID) and having the reseller ID in the current boot loader. I can prepare such a file for you.

Regards,

Audioniek.

[lolo909]

I believe that I did as you wrote. I changed octagon loader into openbox with leviathan_reseller_changer_v13 but I've still got Er.10.
It would be nice if you can prepare right boot loader for Openbox S6 HD. I will give it a try with that one.
Thanks in advance.

[Audioniek]

Attached is a .zip file. In it is a .ird file containing a loader V6.27 with reseller ID 250900A0 (= Openbox S6 HDPVR). The .ird file itself has the reseller ID 250200A0 (= Octagon SF1008 SE+ HD Intelligence). The latter reseller ID must must match the reseller ID currently in the receiver to achieve flashing, and can be changed using a reseller changer.

Meanwhile, there may be a simpler way to find out the reseller ID in the current loader. For this you need a serial log while attempting to flash a .ird file using channel-up. Do the following:

- Set up a serial connection with the receiver and confirm it works;
- Unpack the .zip file and put the .ird file to be flashed on a USB stick. The file must be the only .ird file on the stick;
- Power down the receiver through the mains switch on the back;
- Insert the USB stick in the receiver;
- Press and hold the channel-up key on the front panel;
- While keeping the channel-up depressed power on the receiver with the mains switch on the back;
- Release the channel-up key when the display shows SCan;
- Watch the serial log, in particular if you get an Er.10.

You will see a log of detecting the .ird file on the USB stick and reading it in on the serial port. After that some lines appear, one of which has both the reseller ID of the current loader and the reseller ID of the .ird file. Flashing will only occur when they are the same. When they are different, take note of the value not matching the reseller ID of the .ird file. This is the reseller ID of the loader currently in the receiver. Change the .ird file in the attachment accordingly with a reseller changer and flashing should occur.

Please note that some reseller changers (particularly older ones) write the fourth reseller ID byte back as 0x00 whereas in this case it must be 0xA0.

Flashing the loader is done in the blink of an eye. When it is complete, the receiver will have the reseller ID 250900A0 and should be able to flash an unchanged original firmware .ird file intended for it.

Success!

Regards,

Audioniek.

Attachment: 14352

[lolo909]

Hi Adionek,
Thank you for loader upload. Here is current status:
- loader L627 uploaded successfully
- original Openbox S6 HD firmware uploaded successfully
- tuner hangs during boot up from flash
- tuner hangs during boot up of HDMU from USB


Below are logs from putty.


Any suggestion what to do next? Is it hardware damage and I can't help with it anything else?

Loader upload

% Í(Re)start USB...
Front USB: scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
system volume information/
115230 openbox_s6_l627_r250200a0.ird
==> find ird openbox_s6_l627_r250200a0.ird [115230 ] <==


1 file(s), 1 dir(s)


==> usb_loading start openbox_s6_l627_r250200a0.ird
reading openbox_s6_l627_r250200a0.ird
...........
ret=> 115230
Loader_Parser: index(0) addr[84000000] size(181224), resize(262144)
Loader_Parser: flash write etc[idx 0, addr 0, size (181224)]
Loader_WriteFlash size=0x2c3e8 offset=0xa0000000 data_start 84000000
..==> unprotect 0


.. done
==> erase firtst 0 last 1
..==> protect 0


tuner boots up from flash

%rTs Ô(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
stopping USB..


(Re)start USB...
Front USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Rear 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 **
init started: BusyBox v1.14.2 (2012-03-12 15:08:37 KST)


tuner boots up from pendrive

%rTs Ô(Re)start USB...
Front USB: scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
262144000 root.img
3010445 uimage


2 file(s), 0 dir(s)


reading uImage
.................................................. .................................................. .................................................. .................................................. .................................................. ...........................................
ret=> 3010445
Wait [1]
Wait [2]
Wait [3]
Wait [4]
Wait [5]
Wait [6]
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /mnt/root.img is mounted.
/mnt/root.img: clean, 5651/64000 files, 108927/256000 blocks
mount root
INIT: version 2.88 booting
init frontpanel
WAIT 1 min
mknod: /dev/avs: File exists
mknod: /dev/fuse: File exists
[mountvirtfs] Mount /dev in tmpfs
[mountvirtfs] Copying device nodes to /dev
Starting portmap daemon....
Loading autofs
Starting autofs
[mountall] Mounting local filesystems...
mount: mounting LABEL=RECORD on /hdd failed: No such file or directory
Cleaning /tmp /var/run /var/lock.
Hostname: HS7810A.
init stmfb
LOADING MODULES
load firmware
copLoadFile (file /boot/audio.elf)
ustslave: Kernel Version: 24
base_address 0x40400000
seeking to 0
seeking to 5e00
seeking to 12460
seeking to 1ab60
seeking to 154300
seeking to 154338
seeking to 154370
seeking to 191a58
seeking to 191a60
seeking to 191a68
seeking to 191a70
seeking to 1aae40
seeking to 1aaf00
copLoadFile (file /boot/video.elf)
ustslave: Kernel Version: 24
base_address 0x40000000
seeking to 0
seeking to 60980
seeking to 148478
seeking to 1484b0
seeking to 1484e8
seeking to 158858
seeking to 158864
seeking to 158880
seeking to 184d94
seeking to 186e00
init embx
init AVS
skip mpeg2
Model: 'hs7810a'
vBoxType: 8
Input device name: "TDT RC event driver"
Selected Remote: Fortis RemoteControl
RemoteControl Map:
MENU - 04 - 139
RED - 4B - 398
GREEN - 4A - 399
YELLOW - 49 - 400
BLUE - 48 - 401
EXIT - 1C - 174
TEXT - 0D - 388
EPG - 08 - 365
REWIND - 58 - 168
FASTFORWARD - 5C - 208
PLAY - 55 - 207
PAUSE - 07 - 119
RECORD - 56 - 167
STOP - 54 - 128
STANDBY - 0A - 116
MUTE - 0C - 113
CHANNELUP - 5E - 104
CHANNELDOWN - 5F - 109
VOLUMEUP - 4E - 115
VOLUMEDOWN - 4F - 114
INFO - 06 - 358
OK - 1F - 352
UP - 00 - 103
RIGHT - 02 - 106
DOWN - 01 - 108
LEFT - 03 - 105
BACK - 09 - 158
ZOOM - 0B - 372
VMODE - 0E - 47
RESOLUTION - 0F - 393
TVRADIO - 1A - 378
SLEEP - 1E - 142
OPEN - 40 - 361
FAV - 41 - 364
TIMER - 42 - 362
UPUP - 43 - 414
DOWNDOWN - 44 - 415
NEXT - 4C - 407
LAST - 50 - 412
PIP - 51 - 375
MEDIA - 52 - 226
LIST - 53 - 395
0BUTTON - 10 - 11
1BUTTON - 11 - 2
2BUTTON - 12 - 3
3BUTTON - 13 - 4
4BUTTON - 14 - 5
5BUTTON - 15 - 6
6BUTTON - 16 - 7
7BUTTON - 17 - 8
8BUTTON - 18 - 9
9BUTTON - 19 - 10
Frontpanel Map:
STANDBY - 00 - 116
OK - 06 - 352
MENU - 05 - 139
VOLUMEUP - 03 - 115
VOLUMEDOWN - 04 - 114
CHANNELUP - 01 - 104
CHANNELDOWN - 02 - 109
Supports Long KeyPress: 1
processComplex >
period 10, delay 120
Using period=10 delay=120
[SEM] DOWN