Some problem with editing STB firmware image...

Discussion in 'General Linux' started by jeninicicek, Feb 4, 2013.

  1. jeninicicek

    jeninicicek New Member

    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    I want update my STB running linux so I need acces to it... I can flash with firmware over LAN, I have this firmware and I want modified it... It´s normal gzipped cpio... I can extract it by | gunzip | cpio -i --make-directories. Then I was trying compress it again without changes with find ./ | cpio -H newc -o | gzip -c > _newfile_, but then it doesn´t work and console write this:
    Code:
    RebootLinux version 2.6.11.12_stm20-33  (gcc version 3.4.3 (STMicroelectronics/Linux Base 3.4.3-19) [build Mar 10 2006]) #1 Wed Sep 8 11:32:36 CEST 2010
    ADB STB initialisation
    STb7100 version 3.x
    Built 1 zonelists
    Kernel command line: console=ttyAS0,115200 splasharea=4096,0x0B000000           
    PID hash table entries: 512 (order: 9, 8192 bytes)
    Calculated peripheral clock value 65108 differs from sh_pclk value 66000000, fixing..
    PLL1     : 531.00MHz
    PLL2     : 402.00MHz
    ST40 CPU : 265.50MHz
    ST40 BUS : 132.75MHz
    ST40 PER :  66.37MHz
    SLIM     : 265.50MHz
    ST231    : 402.00MHz
    STBUS    : 201.00MHz
    EMI      : 100.50MHz
    LMI      : 201.00MHz
    Console: colour dummy device 80x25
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 67712k/126976k available (1898k kernel code, 59196k reserved, 227k data, 39412k init)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: STb710x
    Kernel panic - not syncing: invalid compressed format (err=1)
     <1>Unable to handle kernel NULL pointer dereference at virtual address 0000000c
    pc = 84438808
    *pde = 00000000
    Oops: 0000 [#1]
    
    Pid : 1, Comm:              swapper
    PC is at __queue_work+0x28/0xa0
    PC  : 84438808 SP  : 86df7eac SR  : 400081f0 TEA : 0000000c    Not tainted
    R0  : 00000000 R1  : 00000008 R2  : 845f4634 R3  : 00000000
    R4  : 00000001 R5  : 845f4634 R6  : 86cab044 R7  : 86cab03c
    R8  : 845f4634 R9  : 00000000 R10 : 00000000 R11 : 86df6000
    R12 : 86df7ed0 R13 : 86caad3c R14 : 844251a0 R15 : 86df7eac
    MACH: 0000008b MACL: 000000c0 GBR : 00000000 PR  : 84438800
    
    Call trace:
    [<844388dc>] queue_work+0x5c/0xe0
    [<8442f95c>] run_timer_softirq+0xdc/0x260
    [<844f6e20>] blank_screen_t+0x0/0x20
    [<84445852>] handle_IRQ_event+0x52/0xe0
    [<8442ac7a>] __do_softirq+0x5a/0xe0
    [<8442ad46>] do_softirq+0x46/0x60
    [<844d1980>] __const_udelay+0x0/0x20
    [<844170c0>] do_IRQ+0x0/0x60
    [<8442ae66>] irq_exit+0x46/0x80
    [<8441ee80>] sub_preempt_count+0x0/0xa0
    [<844170ee>] do_IRQ+0x2e/0x60
    [<8441406e>] ret_from_irq+0x0/0x12
    [<844d1960>] __delay+0x0/0x20
    [<844d1980>] __const_udelay+0x0/0x20
    [<844d1962>] __delay+0x2/0x20
    [<84424398>] panic+0xb8/0x100
    [<84411112>] init+0x32/0xf20
    [<84412004>] kernel_thread_helper+0x4/0x20
    
    Kernel panic - not syncing: Aiee, killing interrupt handler!
    
    Where can be a problem?

Share This Page