Bootloader reparieren AM510 (SF918SE+)

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Bootloader reparieren AM510 (SF918SE+)

      Hallo Forum,

      ich habe auf meinem Atemio AM510 HD, der wohl baugleich mit Octagon SF918SE+ ist, verschiedene Firmwares (von Octagon und Atemio) ausprobiert.

      Hierzu habe ich auch mit dem HDF-Flasher und Reseller-Changer von Leviathan und AAF herumexperimentiert. Das Ende vom Lied: Titannit sagte mir von der Bedienung her am meisten zu und sollte wieder auf die Box.

      Nach dem Flashen der Original-IRD per USB startete die Box zunüchst normal inkl. Start-Bildschirm, beendete sich dann und versuchte wieder neu zu starten. Jetzt bleibt die Box wohl im Loader hängen und kann wohl nicht mehr aus dem Flash booten.

      HDK7111> run usbboot

      ** Unable to use usb 0:1 for fatload **
      HDK7111> reset
      ...%).ÿ> FrTs
      Unknown command '00' - try 'help'
      . done
      Protected 1 sectors
      HDK7111>

      Es ist kein USB-Stick eingesteckt, d.h. ** Unable to use usb 0:1 for fatload ** ist ok.

      Bootargs scheinen aber ok zu sein:

      HDK7111> printenv
      baudrate=115200
      nfsserverconf=setenv nfs_server nfsroot=$serverip
      ipconf=setenv ipaddrcfg ip=$ipaddr:$serverip:$gateway:$netmask:sdk:eth0:off
      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 $MTD lo
      glevel=0
      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=323
      ip=ip=192.168.0.123:192.168.0.2:192.168.0.1:255.255.255.0:stb7111:eth0:off
      stmmaceth=stmmaceth=msglvl:0,phyaddr:2,watchdog:4000,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 INIT"; run usbbootargs
      ; sleep 1; vfd " E2 RUN"; bootm 84000000; fi
      bootdelay=0
      board=hdk7111_INPUT_CLOCK_RATE
      targetname=muso
      hwnfconf=setenv nwhwnet device:eth0,hwaddr:$ethaddr
      nfs_server=nfsroot=192.168.5.55
      mtdboot=vfd "FLASH"; usb stop; sleep 2; run cramfsbootargs; vfd "LOADING"; bootm
      0xa0060000
      bootcmd=vfd " PKTEAM"; sleep 2; vfd "SCANING"; if usb start; then run usbboot; f
      i; run mtdboot
      stdin=serial
      stdout=serial
      stderr=serial
      ethaddr=**:**:**:**:**:**

      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
      nwhwnet=device:eth0,hwaddr:**:**:**:**:**:**
      ipaddrcfg=ip=192.168.5.253:192.168.5.55:::sdk:eth0:off
      bootargs=console=ttyAS0,115200 root=/dev/mtdblock3 rootfstype=squashfs ip=192.16
      8.5.253:192.168.5.55:::sdk:eth0:off nwhwconf=device:eth0,hwaddr:00:1e:b8:04:1e:4
      a bigphysarea=5000 stb7111:eth0:off stmmaceth=msglvl:0,phyaddr:2,watchdog:4000,r
      xsize:16 mtdparts=physmap-flash:384K(Boot_firmware),1792K@0x00060000(kernel),576
      0K@0x1300000(App),14336K@0x220000(ROOT_FS),2944K@0x1020000(Device),1M@0x1b00000(
      CONFIG),4M@0x01c00000(User),32M@0(All),5760K@0x1300000(APP_ORG),5760K@0x1300000(
      APP_BAK) loglevel=0
      MTD=mtdparts=physmap-flash:384K(Boot_firmware),1792K@0x00060000(kernel),5760K@0x
      1300000(App),14336K@0x220000(ROOT_FS),2944K@0x1020000(Device),1M@0x1b00000(CONFI
      G),4M@0x01c00000(User),32M@0(All),5760K@0x1300000(APP_ORG),5760K@0x1300000(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 a1020000 +$filesize;erase
      a1020000 +$filesize;cp.b 80000000 a1020000 $filesize;protect on a1020000 +$file
      size;mtd_update;vfd _END
      updt_app=vfd LD;tftp 0x80000000 app.img;protect off a1300000 +$filesize;erase a1
      300000 +$filesize;cp.b 80000000 a1300000 $filesize;protect on a1300000 +$filesiz
      e;mtd_update;vfd _END

      Environment size: 3920/16380 bytes


      Was kann man tun? Bin für jeden Hinweis dankbar.


      Gruß
      Kinpump
    • Try this :
      - put the original FW on a formated FAT32 stick ( atemio.de/de/software-updates/…345-firmware-ohne-ci.html )
      - disconnect power supply
      - insert the stick
      - press CH-UP and keep it
      - reconnect the power supply
      - wait 12-15 seconds ... led is bliking ...release and wait ! up to 5 minutes ...
      If you are lucky ... the original FW will be restored ! then ...
      - if the image starts ... you must use Eisha's plugin to restore the
      original bootloader and environment for Atemio 500/510 !
      If this does not work you can try to load the image from scratch
      using the RS232 interface and the RS232 loader program Porter !
    • Danke fuer den Tip. Images lassen sich ueber USB installieren.
      In den IRD-Dateien scheint kein Bootloader enthalten zu sein. Die bootargs bleiben jedenfalls nach dem flashen jeweils unveraendert.
      Gibt es ein Ird-Datei, die nur den bootloader enthaelt bzw. hat jemand den loader einer am510 Hd mal gesichert?

      Gruss kinpump
    • Use this file-upload.net/download-43675…_flash_start_fix.zip.html loader
      from PKT witch will modify the environment in order to test the USB stick presence and load Enigma2 from MS ...
      then the loader can start the flash image ... anyway probably you must load after the FAC image for 918se+ !
      You need to connect your Atemio 510 with a null-modem serial cable and the loader program will write into
      your STB the Bootloader ver 6.2 for Octagon sf918se+ !
      In your place ...I will restore FAC 918se if the original does not start ...then using Eisha's plugin I'll declare as
      Atemio 500/510 ... then load Titan 1.10 and upgrade to Titan 1.13 ! I have Optibox Gekko witch is the same
      as 918se+ and Atemio 510 but the guys from atemio refuses to sell me a licence to use officialy Titan !!!
      wise guys !
    • Thanks for your tips, mihaip.

      Did you successfully flash you Gecko Box with Titan or are you going to try?

      My box is running again with every firmware (Atemio, Octagon), but Titan.

      After flashing it starts exactly once with reboot and u-boot promt then.

      INIT: version 2.86 booting
      [rcS] start /etc/init.d/rcS
      [rcS] booting ATEMIO_M13924_r3428_atemio510_titan
      [rcS] mount FW-FLASH (MTD2)
      [rcS] mount VAR-FLASH (MTD4)
      [rcS] mount SWAP-FLASH (MTD5)
      [rcS] startMounts
      [rcS] start start.sh first titan atemio510
      [start.sh] Thread 1 start
      [start.sh] [first] startTimeset
      [start.sh] [first] startConfig
      Sat Dec 12 20:00:00 UTC 1970
      [start.sh] [first] init stmfb
      [/var/etc/autostart/start.sh] start inetd
      [set_was_timer_wakeup] error reading /etc/enigma2/timers.xml
      [set_was_timer_wakeup] no timer aktiv
      [start.sh] Thread 1 end
      [start.sh] [first] enable HDMI
      [start.sh] [first] startBootlogo
      [start.sh] [first] startVfd
      [bootlogo.sh] start /var/etc/boot/bootlogo.sh
      [bootlogo.sh] use bootlogo jpg
      /var/etc/boot/bootlogo.sh: line 204: shmE2: not found
      /var/etc/boot/bootlogo.sh: line 204: shmE2: not found
      *** InfoBox v1.7 by GOst4711 and nit ***
      1280x720, 32bpp
      jpg image hight = 720
      jpg image width = 1280
      [start.sh] [first] startFrontpanel
      [start.sh] [first] skip init frontpanel
      [start.sh] [first] startEvremote titan atemio510
      init lircd
      [/var/etc/autostart/start.sh] start autofs
      ...
      [/var/etc/autostart/start.sh] start load autofs
      Model: hs7110
      vBoxType: 7
      ...
      [/var/etc/autostart/start.sh] start hotplug.sh first titan atemio510
      [/var/etc/autostart/start.sh] startNetwork: start
      [start.sh] [first] startAvs
      [networking] start eth0...
      [start.sh] [first] load audio firmware (/boot/audio.elf)
      copLoadFile (file /boot/audio.elf)
      [networking] eth0 using dhcp
      ustslave: Kernel Version: 23
      base_address 0x40400000
      seeking to 0
      seeking to 6000
      udhcpc (v1.19.2) started
      seeking to 1c920
      Sending discover...
      ...
      seeking to 24f60
      seeking to 210b00
      seeking to 210b38
      seeking to 210b70
      seeking to 28ff30
      seeking to 28ff38
      seeking to 28ff40
      seeking to 28ff48
      seeking to 2b4db0
      seeking to 2b4e00
      [start.sh] [first] load video firmware
      copLoadFile (file /boot/video.elf)
      ustslave: Kernel Version: 23
      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
      [start.sh] [first] init embx
      [start.sh] [first] init player 191
      Sending discover...
      Sending select for 192.168.220.225...
      Lease of 192.168.220.225 obtained, lease time 43200
      route: SIOCDELRT: No such process
      [start.sh] [first] startBootlogo cont
      [start.sh] [first] startReader titan atemio510
      adding dns 192.168.220.1
      [start.sh] Thread 2 start
      [start.sh] Thread 2 end
      ...
      [rcS] hotplug.sh first
      ...
      [rcS] starting titan
      [titan] copyright by NIT - version 1.10
      [titan] crontribut: obi, black, dvboxer, oxygen, gost
      [titan] using config: /var/etc/titan/titan.cfg
      [rcS] titan ended <- RTV: 100
      [rcS] start start.sh reboot 100 titan atemio510
      [start.sh] [reboot] ERROR titan REBOOT
      [reboot.sh] start /var/etc/boot/reboot.sh
      [reboot.sh] use reboot jpg
      /var/etc/boot/reboot.sh: line 56: shmE2: not found
      *** InfoBox v1.7 by GOst4711 and nit ***
      1280x720, 32bpp
      jpg image hight = 720
      jpg image width = 1280
      ------- Programmende
      /var/etc/boot/reboot.sh: line 56: shmE2: not found
      fuser: applet not found
      [emu.sh] emu not found emu=off
      INIT: Sending processes the TERM signal
      ------- Programmende
      Sending all processes the TERM signal...done.
      Sending all processes the KILL signal...done.
      Deactivating swap...done.
      Unmounting local filesystems...umount: /dev/mtdblock4 busy - remounted read-only
      done.
      ...%).��HDK7111>

      Perhaps Atemio implemented a copy protection, but the guy on the hotline didn't mention it.

      greets kinpump
    • There is no copy protection ! I use Titan 1.10 patched ( from Octagon Forum ) without any problem !
      - I modified the resseler ID of my Gekko into AM510
      - I loaded Titan 1.10 ( .ird ) in boot mode
      - I loaded FTP patch ( .ird) in boot mode
      - then ... settings, emus ....
      The only problem is that this version does not support online upgrade ... so some of the menu functions
      are hidden ... no additional skins , no plugins ... but the image works fine is fast and reliable !
      I can see any reason for your AM510 behaviour ! try to reflash ... You can download everything you need
      from octagon-forum.com/index.php?/t…18se-sf1008se-09feb-2012/
    • Eisha, du bist der Grösste!

      Die Box rennt wieder mit Titan. Gerade läuft das Online-Update auv Version 1.13. Besten Dank nochmal!

      @mihaip: Here's, what I did:

      HDK7111> protect off 1:2-255
      Un-Protect Flash Sectors 2-255 in Bank # 1
      ................................................................................
      ................................................................................
      ................................................................................
      .............. done
      HDK7111> erase 1:2-255
      Erase Flash Sectors 2-255 in Bank # 1
      ................................................................................
      ................................................................................
      ................................................................................
      .............. done
      HDK7111> protect on 1:2-255
      Protect Flash Sectors 2-255 in Bank # 1
      ................................................................................
      ................................................................................
      ................................................................................
      .............. done

      Then flash IRD with CHUP method.


      Gruß kinpump
    • Tnks ! this problem occurs because Fortis and Fulan loaders ( bootloaders
      as well serial loader programs ) just update the flash ...only those areas
      included into IRD file ... the result is a flash image with some areas not
      initialised ... some of them must remain as is ( user settings ) but some
      of them can contain system data eventualy corrupted ... if those are not
      initialized ( zeroed ) ... the restored image will not start or will go into
      a system error ! This is a programming error ! sometimes solved using a
      cleanup image ! or using Eisha's method ! Tnks !
      *
      If your receiver is an Octagon ( resselerID ) you can download a cleaner
      image from octagonfunclub.net/index.php?P…20SE%20Plus%20HD%20Single !!!
      *
      Fulan ( gm990, pingulux,alien ) made a "rescue image" witch is to be
      loaded in Boot mode and is a full backup of the flash so will initialize
      all !

    Unsere Partnerboards

    ^
    Flag Counter