Thanks Thanks:  0
Ergebnis 1 bis 4 von 4
  1. #1
    Anfänger
    Registriert seit
    26.12.2013
    Beiträge
    20
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    AZbox Elite HD DVB-S2/DVB-T
     
     
    Box 2:
    AZbox Premium+ HD DVB-S2/DVB-T
     
     

    Howto extract vmlinux from Enigma2 patch.e2? (AZbox Recovery)

    ** Questions for Help **

    My extract procedure failed (see below).

    What went wrong?
    - unpack_e2?
    - my vmlinux extract?

    What does the memory map of the AZbox look like?
    I feel poking in the dark.
    - Where to load tmp data in RAM?

    - Is the onboard flash (8MB) memory mapped?

    - What is the correct flash procedure for a recent E2 kernel?

    Thanks!
    Marjan
    ==

    ** AZbox broken **

    The inevitable happened: AZUp turned my AZbox into a brick!
    When sending the kernel image AZUp opened a message window
    saying "Cannot write to file". Since OK was the only
    option I pressed OK. But instead of aborting AZUP went on,
    logged that "flashing was done" and rebooted the system.
    My AZbox was stuck in "Booting.."!
    (I still don't know what caused this disaster.
    May be it was a WiFi failure of damn MS-Windows.)

    Nevertheless, as long there is "Yamon" there is hope!
    With Yamon we can flash a kernel image in the flash ROM.
    We only have to know "How to flash" and we need a kernel.


    ** Obtaining a kernel **

    How to obtain a recent (3.9.2) kernel image?
    Well, extract it from the distribution zip!
    So I searched for an "patch.e2" extraction tool and found it:

    "How to unpack a patch.e2 enigma2 file from linux » Official dAm2K Blog"
    http://dino.ciuffetti.info/2011/06/e...ch-from-linux/

    Dino Ciuffetti wrote a little C-program which decomposes a
    patch.e2 archive into a "cram.img" and "kernel.img" file.


    ** Extracted kernel image failed! **

    Before flashing the kernel image I decided to test this kernel
    in the AZbox by loading the "vmlinux_xload.zbf" in RAM.

    Using Dino's program I extracted a recent kernel
    and prepared the vmlinux image (detailed procedure: see below).

    However my extracted vmlinux image failed!
    Yamon didn't like my image by complaining about a wrong checksum.


    ** My extract procedure in detail **

    ## Enigma2: extract vmlinux from patch.e2
    ## ======================================
    ## Marjan 20140124

    $ gcc -o unpack_e2 -O2 -Wall unpack_e2.c

    $ unzip openatv-3.1-azboxhd-20140109_azup.zip
    Archive: openatv-3.1-azboxhd-20140109_azup.zip
    inflating: patch.e2

    $ ./unpack_e2 patch.e2
    Team name: OE-A
    Description: Alliance
    Version: .
    About: Enigma2
    Kernel description: ULK-3.9.2
    Size of cram image: 48701440 bytes (46.45 Mb)
    Size of kernel image: 6616064 bytes (6.31 Mb)
    Unpacking cramfs image to cram.img
    Unpacking kernel image to kernel.img

    $ su -
    Password:

    # cd $AZbox_dir
    # mount -r -t romfs -o loop kernel.img /mnt/img

    # ll /mnt/img
    total 0
    -rw-r--r-- 1 root root 6615821 Jan 1 1970 vmlinux_xload.zbf

    ## Copy vmlinux to tftpd dir
    # cp /mnt/img/vmlinux_xload.zbf /srv/tftp/


    # AZbox Premium+ Load vmlinux log
    # ===============================
    # Marjan 20140124

    YAMON> setenv ipaddr 192.168.1.201
    Updating XENV block at 0x48000000.
    .
    XENV verification OK.
    YAMON> setenv subnetmask 255.255.255.0
    Updating XENV block at 0x48000000.
    .
    XENV verification OK.
    YAMON> setenv gateway 192.168.1.254
    Updating XENV block at 0x48000000.
    .
    XENV verification OK.
    YAMON> net init
    net have been initialized
    ipaddr: 192.168.1.201
    subnetmask: 255.255.255.0
    gateway: 192.168.1.254

    YAMON> ping 192.168.1.254
    64 bytes ICMP-ECHO-REPLY user data received from 192.168.1.254
    YAMON>
    # ping to a non-existant ipaddr
    YAMON> ping 192.168.1.202
    ....
    Error : ARP-timeout, no reponse on ARP-request
    Hint : Check cable and IP-address of remote host
    YAMON>

    YAMON> load -b tftp://192.168.1.253/vmlinux_xload.zbf 0xb0100000
    About to load tftp://192.168.1.253/vmlinux_xload.zbf
    Press Ctrl-C to break
    .................................................. ..............
    .................................................. ..............
    .................................................. ..............
    .........

    Start = 0xb0100000, range = (0xb0100000,0xb074f30c), format = BINARY
    Length = 0x64f30d (6615821)
    Checksum = 0x852f690a

    YAMON> load zbf 0xb0100000
    Checking zboot signature.. it's a zboot file, signature OK.
    Decompressing to 0x90020000 ..
    Output length: 0x001a9d6c(1744236)
    unzip error!!orig_crc=0x820008af, crc=0xd2759b95
    Decompressing zboot file from 0xb0100000 to 0x90020000 fail
    Error : Internal, code = ffffffff
    YAMON>
    Angehängte Dateien Angehängte Dateien
    Geändert von Marjan (25.01.2014 um 16:28 Uhr) Grund: typo

    •   Alt Advertising

       

  2. #2
    Anfänger
    Registriert seit
    26.12.2013
    Beiträge
    20
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    AZbox Elite HD DVB-S2/DVB-T
     
     
    Box 2:
    AZbox Premium+ HD DVB-S2/DVB-T
     
     
    I'm one step further now..

    Dino's unpack_e2 program is OK!

    In a running AZbox I read partition 4 of the flashrom in a file:

    # dd if=/dev/mtdblock4 of=mtdblock4.img

    Then I compared my extracted "kernel.img" to "mtdblock4.img":

    -rw-r--r-- 1 Marjan Marjan 6616065 Jan 23 22:26 kernel.img
    -rw-r--r-- 1 Marjan Marjan 6815744 Jan 26 13:26 mtdblock4.img

    # cmp kernel.img mtdblock4.img
    kernel.img mtdblock4.img differ: byte 6616065, line 19564

    So upto byte 6616064 the files are the same.
    Byte 6616065 differs
    Bytes 6616066 - 6815744 are the free space left in part 4.

    The extracted vmlinux files are identical:

    -rw-r--r-- 1 root root 6615821 Jan 26 13:33 vmlinux_xload.zbf
    -rw-r--r-- 1 root root 6615821 Jan 26 13:33 vmlinux_xload-mtdblock4.zbf

    $ cmp vmlinux_xload.zbf vmlinux_xload-mtdblock4.zbf
    (no message)

    My conclusiion so far:
    The extracted "vmlinux_xload.zbf" is OK.
    But my procedure to load this file in the AZbox was apparently incorrect.

  3. #3
    Anfänger
    Registriert seit
    26.12.2013
    Beiträge
    20
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    AZbox Elite HD DVB-S2/DVB-T
     
     
    Box 2:
    AZbox Premium+ HD DVB-S2/DVB-T
     
     
    Question:

    Having a running AZbox can I simply use "dd" to flash the kernel image?

    # dd if=kernel.img of=/dev/mtdblock4

    Is this the way AZUp flashes the kernel?

  4. #4
    Anfänger
    Registriert seit
    22.10.2013
    Beiträge
    17
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Schönen guten Tag,
    interessiert mich auch gerade - ich habe die beiden Files extrahiert und suche einen Weg diese via telnet zu flashen.
    Hätte wer Infos?
    Thanks


Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Diese Website benutzt Cookies
Wir benutzen Cookies um Sitzungsinformationen zu speichern. Dies erleichtert es uns z.B. Dich an Deine Login zu erinnern, Einstellungen der Webseite zu speichern, Inhalte und Werbung zu personalisieren, Social Media Funktionen anzubieten und unser Datenaufkommen zu analysieren. Wir teilen diese Informationen ebenfalls mit unseren Social Media-, Werbe- und Analysepartnern.
     
Alle Zeitangaben in WEZ +1. Es ist jetzt 16:18 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2017 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 11,11%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com