Letzte Themen:

Sony Vaio Notebook » Autor (Quelle): efe72 » Letzter Beitrag: efe72 Ersatz für Dreambox HD 8000 » Autor (Quelle): haie » Letzter Beitrag: zeus-crew Ruf mich an » Autor (Quelle): Duke » Letzter Beitrag: Duke Ebay Kleinanzeigen » Autor (Quelle): zeus-crew » Letzter Beitrag: Trike HD Plus stellt neuen Empfangsweg vor » Autor (Quelle): Dr.Dream » Letzter Beitrag: rqs Ein Gedicht das (vielleicht) polarisieren wird » Autor (Quelle): Beingodik » Letzter Beitrag: Beingodik Nokia Streaming Box 8000 / 8010 » Autor (Quelle): satron » Letzter Beitrag: satron Fire Stick was geht da ? » Autor (Quelle): crx » Letzter Beitrag: crx 23 Jahre Spinnes-Board » Autor (Quelle): Duke » Letzter Beitrag: DEF Win7, Rechner startet von heut auf morgen nicht mehr .... » Autor (Quelle): wegomyway » Letzter Beitrag: rqs
Ergebnis 1 bis 3 von 3

Thema: UFS 902 Display tot nach FW update

  1. #1
    Neuling
    Registriert seit
    May 2005
    Beiträge
    3
    Danke
    0
    Erhielt 0 Danke für 0 Beiträge
    FAQ Downloads
    0
    Uploads
    0

    Wink UFS 902 Display tot nach FW update

    Morgen.

    Wahnsinn, 7 Jahre hier und mein erster Beitrag.
    Habe am WE in meiner unendlichen Weisheit und unter leichten Alkoholeinfluß zum flashen der 902 die FW der 910 erwischt. Hat natürlich nicht geklappt.
    Die Kathi fährt hoch und kann einwandfei genutzt werden. Nur das Display ist tot. Beim Booten kommt noch "UFS 902" und das wars. Wenn ich das Bootlog richtig deute, soll das Modul vfd_driver_902.ko beim booten entladen werden. Wird nicht, es ist nicht vorhanden. Ein Teil der 910er FW steckt noch in der 902?

    Jetzt suche ich eine Möglichkeit, das Display in Gang zu kriegen.

    Eine Frage noch. Ist es möglich, die Images der UFS unter Linux zu mounten oder zu bearbeiten?

    Gruß an alle.


    edit: Kann die Bootlog nicht anhängen. Wer sie einsehen möchte, PM bitte
    Geändert von estela (03.06.12 um 11:50 Uhr)

  2. #2
    Moderator Avatar von Satfan123
    Registriert seit
    Oct 2000
    Beiträge
    7.425
    Danke
    31
    Erhielt 270 Danke für 151 Beiträge
    FAQ Downloads
    0
    Uploads
    0
    schin versucht die 902-er FW nachzuflashen ?
    Zur Info ich bin nicht Irata !!

    Mein Tipp für D-Box Dreambox Digi Receiver und CI Reparatur
    D-Box Dreambox Digireceiver Reparaturservice CI Modul Reparaturservice

  3. #3
    Neuling
    Themenstarter

    Registriert seit
    May 2005
    Beiträge
    3
    Danke
    0
    Erhielt 0 Danke für 0 Beiträge
    FAQ Downloads
    0
    Uploads
    0
    Ja, zweimal. Hier nochmal der Bootlog:

    Code:
    Board: STb7100-mboard
    other device
    
    
    U-Boot 1.1.2 (STLINUX_2_0p1) (Mar 24 2008 - 11:22:43)
    
    DRAM:  32 MB
     write time out = 2, clock = 40
    Flash: 16 MB
    In:    serial
    Out:   serial
    Err:   serial
    pll0 freq 531
    pll1 freq 399
    Net:   VFD_Driver Init
    board_version = 0
    Button_value = 7
    Hit any key to stop autoboot:  1  0 
    ## Booting image at a0040000 ...
       Image Name:   Linux 2.6
       Image Type:   SH-4 Linux Kernel Image (gzip compressed)
       Data Size:    1715381 Bytes =  1.6 MB
       Load Address: 84401000
       Entry Point:  84402000
       Verifying Checksum ... OK
       Uncompressing Kernel Image ... OK
    
    Starting kernel console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000 - 0x00000000 - 0 ...
    
    Linux version 2.6.17.14_stm22_0037 (kdhong@localhost.localdomain) (gcc version 4.1.1 (STMicroelectronics/Linux Base 4.1.1-21)) #221 PREEMPT Mon Nov 30 17:28:22 CET 2009
    STMicroelectronics STb7100 Reference board initialisation
    STb7100 version 3.x
    Built 1 zonelists
    Kernel command line: console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    st-coprocessor: Failed to reserve memory at 0x04000000
    st-coprocessor: Failed to reserve memory at 0x04200000
    PID hash table entries: 256 (order: 8, 1024 bytes)
    Using tmu for system timer
    Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
    Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Memory: 26160k/41984k available (2853k kernel code, 15804k reserved, 360k data, 88k init)
    PVR=04061100 CVR=30480000 PRR=00009100
    I-cache : n_ways=2 n_sets=256 way_incr=8192
    I-cache : entry_mask=0x00001fe0 alias_mask=0x00001000 n_aliases=2
    D-cache : n_ways=2 n_sets=512 way_incr=16384
    D-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
    Mount-cache hash table entries: 512
    CPU: STb710x
    NET: Registered protocol family 16
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    NET: Registered protocol family 2
    IP route cache hash table entries: 512 (order: -1, 2048 bytes)
    TCP established hash table entries: 2048 (order: 1, 8192 bytes)
    TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
    TCP: Hash tables configured (established 2048 bind 1024)
    TCP reno registered
    bigphysarea: Allocated 2984 pages at 0x847bb000.
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    Initializing Cryptographic API
    io scheduler noop registered
    io scheduler anticipatory registered (default)
    io scheduler deadline registered
    io scheduler cfq registered
    Device probe found data for platform device lirc
    lirc_dev: IR Remote Control driver registered, at major 61 
    lirc_dev: lirc_register_plugin: sample_rate: 0
    lirc_dev: lirc_register_plugin: plugin lirc_stm owner 00000000
    STM LIRC plugin has IRQ 125
     Lirc STM: Using IRB mode
    STMicroelectronics LIRC driver configured
    STPIO layer initialised
    VFD_Controller Type : NEW Kathrein VFD
    STMicroelectronics ASC driver initialized
    ttyAS0 at MMIO 0xb8032000 (irq = 121) is a asc
    ttyAS1 at MMIO 0xb8033000 (irq = 120) is a asc
    RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
    s_env_mac[0] = 0
    s_env_mac[1] = 0
    s_env_mac[2] = :
    s_env_mac[3] = 5
    s_env_mac[4] = 0
    s_env_mac[5] = :
    s_env_mac[6] = f
    s_env_mac[7] = d
    s_env_mac[8] = :
    s_env_mac[9] = f
    s_env_mac[10] = f
    s_env_mac[11] = :
    s_env_mac[12] = 1
    s_env_mac[13] = 2
    s_env_mac[14] = :
    s_env_mac[15] = 3
    s_env_mac[16] = 4
    get ether addr = 0, 50, fd, ff, 12, 34 
    mac hi address = 3412, lowaddress = fffd5000
    SMSC: --> init_module()
    SMSC: Driver Version = 1.21
    SMSC: Compiled: Apr 26 2009, 15:59:04
    SMSC: Platform: ST40 STMICRO r3
    SMSC: Driver Parameters
    SMSC:   lan_base         = 0x00000000, driver will decide
    SMSC:   bus_width        = 0, driver will autodetect
    SMSC:   link_mode        = 0x7F, 10HD,10FD,100HD,100FD,ASYMP,SYMP,ANEG
    SMSC:   irq              = 2
    SMSC:   int_deas         = 0xFFFFFFFF, use platform default
    SMSC:   irq_pol          = 1, IRQ output is active high
    SMSC:   irq_type         = 1, IRQ output is Push-Pull driver
    SMSC:   rx_dma           = 256, RX will use PIO
    SMSC:   tx_dma           = 256, TX will use PIO
    SMSC:   dma_threshold    = 200
    SMSC:   mac_addr_hi16    = 0x00003412
    SMSC:   mac_addr_lo32    = 0xFFFD5000
    SMSC:   debug_mode       = 0x00000007
    SMSC:   tx_fif_sz        = 0x00050000
    SMSC:   afc_cfg          = 0xFFFFFFFF, driver will decide
    SMSC:   tasklets         = 0, Tasklets disabled
    SMSC:   phy_addr         = 0xFFFFFFFF, Use internal phy
    SMSC:   max_throughput   = 0xFFFFFFFF, Use platform default
    SMSC:   max_packet_count = 0xFFFFFFFF, Use platform default
    SMSC:   packet_cost      = 0xFFFFFFFF, Use platform default
    SMSC:   burst_period     = 0xFFFFFFFF, Use platform default
    SMSC:   max_work_load    = 0xFFFFFFFF, Use platform default
    SMSC: -->Smsc911x_init(dev=0x846E55CC)
    SMSC: --> Platform_Initialize
    SMSC: Lan Base at 0xA2000000
    SMSC: <-- Platform_Initialize
    SMSC: dwLanBase=0xA2000000
    SMSC_WARNING:   LAN911x NOT Identified, dwIdRev==0xFFFFFFFF
    SMSC: <--Smsc911x_init(), result=-19
    SMSC_WARNING: error -19 registering device
    SMSC: <-- init_module()
    nwhw_config: device not found
    ata1: SATA max UDMA/133 cmd 0xB9209000 ctl 0xB9209820 bmdma 0x0 irq 170
    ata1: SATA link down (SStatus 0)
    scsi0 : sata_stm
    Generic ST boards onboard flash device: 0x01000000 (16.0Mb) at 0x00000000
    Onboard_Flash: Found 1 x16 devices at 0x0 in 16-bit bank
     Amd/Fujitsu Extended Query Table at 0x0040
    Onboard_Flash: CFI does not contain boot bank location. Assuming top.
    number of CFI chips: 1
    cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
    Creating 8 MTD partitions on "Onboard_Flash":
    0x00000000-0x00020000 : "Boot firmware : 	0xA000.0000-0xA001.FFFF"
    0x00040000-0x00200000 : "Kernel - 		0xA004.0000-0xA01F.FFFF"
    0x00200000-0x002a0000 : "Config FS - 		0xA020.0000-0xA029.FFFF"
    0x002a0000-0x004e0000 : "Root FS-		0xA02A.0000-0xA04D.FFFF"
    0x004e0000-0x00ae0000 : "APP_Modules		0xA04E.0000-0xA0AD.FFFF"
    0x00ae0000-0x00c00000 : "EmergencyRoot		0xA0AE.0000-0xA0BF.FFFF"
    0x00c00000-0x01000000 : "OtherData		0xA0C0.0000-0xA0FF.FFFF"
    0x00020000-0x00040000 : "BootConfiguration	0xA002.0000-0xA003.FFFF"
    ST40-ehci ST40-ehci.2: ST EHCI Host Controller
    ST40-ehci ST40-ehci.2: new USB bus registered, assigned bus number 1
    ST40-ehci ST40-ehci.2: irq 169, io mem 0xb91ffe00
    ST40-ehci ST40-ehci.2: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb1: Product: ST EHCI Host Controller
    usb usb1: Manufacturer: Linux 2.6.17.14_stm22_0037 ehci_hcd
    usb usb1: SerialNumber: STB7100_EHCI
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver libusual
    pegasus: v0.6.13 (2005/11/13), Pegasus/Pegasus II USB Ethernet driver
    usb 1-1: new high speed USB device using ST40-ehci and address 2
    usb 1-1: Product: USB 2.0  SATA BRIDGE   
    usb 1-1: Manufacturer: Super Top   
    usb 1-1: SerialNumber: M6116A016V20
    usb 1-1: configuration #1 chosen from 1 choice
    scsi1 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new driver pegasus
    usbcore: registered new driver asix
    usbcore: registered new driver cdc_ether
    usbcore: registered new driver net1080
    usbcore: registered new driver zaurus
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    stssc layer initialized
    STMicroelectronics - Coprocessors st231 Init
    st231-0 Coprocessor -------------------------------------------
        flags 0001 RAM start at 0xa4000000  size      0x00200000
                      cop. addr 0x04000000
        Channels : Not defined
        IRQ      : not used
    ---------------------------------------------------------------
    st231-1 Coprocessor -------------------------------------------
        flags 0001 RAM start at 0xa4200000  size      0x00200000
                      cop. addr 0x04200000
        Channels : Not defined
        IRQ      : not used
    ---------------------------------------------------------------
    TCP bic registered
    TCP highspeed registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    VFS: Mounted root (cramfs filesystem) readonly.
    Freeing unused kernel memory: 88k freed
    /etc/init.d/rcS running...
    Remounting root file system in read-write mode...mount: Can't find / in /etc/fstab
    : Success
    mount: Mounting / on (null) failed: Success
    [FAILED]
    /etc/rcS.d/S200mountfs: /etc/rcS.d/S200mountfs: 91: cannot create /etc/mtab: Read-only file system
    mount: Can't find / in /etc/fstab
    : Success
    mount: Mounting / on (null) failed: Success
    Mounting other file systems...[  OK  ]
    Bringing up the loopback interface...[  OK  ]
    Setting up hostname...(none)
    [  OK  ]
    
    
    BusyBox v1.1.0 (2006.03.02-09:48+0000) Built-in shell (ash)
    Enter 'help' for a list of built-in commands.
    
    insmod: /lib/modules/2.6.17.14_stm22_0037: No such file or directory
    insmod: vfd_driver.ko: no module by that name found
    TestModMgr::CheckTestMode CmdLine = console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    
    CMDLINE = console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    
    CMDLINE = console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    
    cannot fine test mode 
    config/start.sh does not exist.... running /app/start.sh
    PARAM : boot_param_version=22
    
    PARAM : board=stb7100ref_27
    PARAM : bootcmd=bootm a0040000
    PARAM : bootdelay=1
    PARAM : ethaddr=00:50:fd:ff:12:34:56
    PARAM : bootargs=console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    PARAM : stdin=serial
    PARAM : stdout=serial
    PARAM : stderr=serial
    PARAM : autoload=n
    BOOT PARAM VERSION = 22
    Check902.c main 84 Error
    I2CDevAdapter[0] ReadWithoutStop Error. 
    UFS-902 found
    vfd_driver: module license 'Marusys' taints kernel.
    Fault in unaligned fixup: 0000 [#1]
    
    Pid : 115, Comm:               insmod
    PC is at stpio_set_pin+0x28/0x60
    PC  : 84582588 SP  : 86635ee0 SR  : 40008000 TEA : 0bfdc3be    Tainted: P     
    R0  : 07b8aab0 R1  : 0bfdc3be R2  : 0bfdc3ba R3  : 00000002
    R4  : 7b8aab18 R5  : 00000001 R6  : 00000000 R7  : 40008000
    R8  : 00000008 R9  : 00000000 R10 : c0164cf4 R11 : 0000000c
    R12 : 84582560 R13 : 844299c0 R14 : 00000001
    MACH: ffffffb6 MACL: c9c9ca13 GBR : 2956b7a8 PR  : c0162248
    
    Call trace: 
    [<c0164b00>] vfd_dev_fops+0x0/0xffffe960 [vfd_driver]
    [<c0162758>] VFD_Number_Of_Digit_Set+0xb8/0x100 [vfd_driver]
    [<c0164afc>] vfd_type+0x0/0xffffe964 [vfd_driver]
    [<844299c0>] blocking_notifier_call_chain+0x0/0x40
    [<c0164b08>] vfd_dev_fops+0x8/0xffffe960 [vfd_driver]
    [<c0162db4>] vfd_init_func+0x194/0x3c0 [vfd_driver]
    [<8442f760>] param_get_int+0x0/0x20
    [<c0166008>] stb04xxx_vfd_init+0x8/0x20 [vfd_driver]
    [<84683f80>] mutex_unlock+0x0/0x60
    [<844299c0>] blocking_notifier_call_chain+0x0/0x40
    [<c0164c3c>] __this_module+0xbc/0xffffe8e0 [vfd_driver]
    [<c0164b80>] __this_module+0x0/0xffffe8e0 [vfd_driver]
    [<8443a7de>] sys_init_module+0x9e/0x360
    [<84405198>] syscall_call+0xc/0x10
    [<8443a740>] sys_init_module+0x0/0x360
    
    Segmentation fault
    VFD PIO Already Opened
    VFD PIO Already Opened
    VFD PIO Already Opened
    VFD_Controller Type : undefined
    VFD_Number_Of_Digit_Set : Other Type : NOT implemented
    VFD_Display_Write_On_Off : Other Type : NOT implemented
    VFD_Display_DutyCycle_Write : Other Type : NOT implemented
    rmmod: vfd_driver_902: No such file or directory
    SysConf device Init
    LMI_SYS VCR0 = 00d40000
    LMI_SYS VCR1 = 0f041000
    LMI_SYS MIM0 = 861a0247
    LMI_SYS MIM1 = 01010022
    LMI_SYS SCR = 00000000
    LMI_SYS STR = 35b06455
    LMI_SYS COC = 00000000
    LMI_SYS SDRA0 = 08001900
    LMI_SYS SDRA1 = 08001900
    LMI_SYS CIC = 00000249
    LMI_SYS SDMR0 = 00000000
    LMI_SYS SDMR1 = 00000000
    LMI_VID VCR0 = 00d40000
    LMI_VID VCR1 = 17101000
    LMI_VID MIM0 = 861a0247
    LMI_VID MIM1 = 01010022
    LMI_VID SCR = 00000000
    LMI_VID STR = 35b06455
    LMI_VID COC = 00000000
    LMI_VID SDRA0 = 14001900
    LMI_VID SDRA1 = 14001900
    LMI_VID CIC = 00000249
    LMI_VID SDMR0 = 00000000
    LMI_VID SDMR1 = 00000000
    TestModMgr::CheckTestMode CmdLine = console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    
    CMDLINE = console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    
    CMDLINE = console=ttyAS0,115200 root=/dev/mtdblock3 mem=41m bigphysarea=2984 coprocessor_mem=2m@0x04000000,2m@0x04200000
    
    cannot fine test mode 
    TestModeMgr::CheckMode : TestMode Disabled
    app launcher : insmod /app/modules/vfd_driver_902.ko
    Child PID...
    insmod: cannot insert `/app/modules/vfd_driver_902.ko': File exists (-1): File exists
    Invoke insmod /app/modules/vfd_driver_902.ko : PID Parent= 125, Child = 227
    Exit PID: 227, Child PID : 227
    Geändert von estela (03.06.12 um 22:09 Uhr)

Ähnliche Themen

  1. Galaxy S3: Probleme nach Update
    Von crx im Forum Android Forum (APK)
    Antworten: 0
    Letzter Beitrag: 16.11.12, 15:17
  2. smargo nach update KO ?
    Von dymby im Forum Cardsharing
    Antworten: 1
    Letzter Beitrag: 18.11.10, 00:26
  3. Nach Update - Barry Allen weg
    Von offi im Forum Dreambox 800 HD
    Antworten: 2
    Letzter Beitrag: 09.07.09, 20:57

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •