WeTek Community Forum

wetek ne demare plus

moh26moh26 Posts: 127WeTek Community Member
après une restauration d'origine wetek ne demare plus et bloque sur la lampe bleu

Comments

  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    N'a pas compris la question

  • moh26moh26 Posts: 127WeTek Community Member
    mon wetek et bloque n’affiche aucune image
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Téléchargez les 3 fichiers

    https://mega.co.nz/#F!tsQ22D4S!BKBruIQdleATY8gJNha7JQ


    Formater une carte mSD

    Copiez-collez les 3 fichiers sur la carte mSD puis faire comme dans la vidéo
    Débranchez le câble d'alimentation
    Mettez la carte mSD sur Wetek
    Appuyez sur le bouton "upgrade" sur le fond
    connecter l'alimentation à wetek
    attendre 7-10 secondes tout en appuyant sur le bouton "upgrade"

  • moh26moh26 Posts: 127WeTek Community Member
    j'ai essayer ces étapes et toujours le mémé problème
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Essayez d'installer OpenELEC

    sa la même procédure que android

    http://update.wetekos.com:8080/download/OpenELEC/NAND/OpenELEC-Amlogic.WeTek.Play.arm-5.0.8.zip

  • moh26moh26 Posts: 127WeTek Community Member
    toujours pas de réponse
  • moh26moh26 Posts: 127WeTek Community Member
    le mémé problème perciste
  • moh26moh26 Posts: 127WeTek Community Member
    es qu'il ya une autre solution
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
  • moh26moh26 Posts: 127WeTek Community Member
    désoler mes ça ne marche pas
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Avez-vous la connexion série sur votre PC?

  • moh26moh26 Posts: 127WeTek Community Member
    oui j'ai rs232
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Vous pouvez essayer le "hard recovery"

    Si cela ne fonctionne pas, s'il vous plaît envoyer un courriel à l'appui revendeur

    Si vous avez acheté sur Wetek.com, s'il vous plaît nous contacter ici

    Voir les attachements comment le faire

    Meilleures salutations

  • moh26moh26 Posts: 127WeTek Community Member
    [CODE=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.07.08 18:12:22 =~=~=~=~=~=~=~=~=~=~=~=
    EEEE I3000000032940xf3001103 03;77520EEEE I400000004294_M6_BL1_3431 >2534313
    TE : 77476
    BT : 16:48:10 May 4 2015

    CPU clock is 1200MHz


    wait pll-0x03 target is 0204 now it is 0x00000203

    DDR clock is 516MHz with Low Power & 2T mode

    DDR training :
    DX0DLLCR:40000000
    DX0DQTR:ffffffff
    DX0DQSTR:3db05001
    DX1DLLCR:40000000
    DX1DQTR:ffffffff
    DX1DQSTR:3db05001
    DX2DLLCR:40000000
    DX2DQTR:ffffffff
    DX2DQSTR:3db05001
    DX3DLLCR:40000000
    DX3DQTR:ffffffff
    DX3DQSTR:3db05001
    Stage 00 Result 00000000
    Stage 01 Result 00000000
    Stage 02 Result 00000000
    Stage 03 Result 00000000

    DDR init use : 42463 us

    HHH
    BootFrom SPI
    ucl decompress
    decompress true
    0x12345678
    Boot from int dev 1stSPI

    TE : 1303001

    System Started


    U-boot(wetek@) (May 04 2015 - 16:47:56)

    aml_rtc_init
    aml rtc init first time!
    clr h-ram
    DRAM: 1 GiB
    relocation Offset is: 105e0000
    MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6
    [mmc_register] add mmc dev_num=1, port=2, if_type=6
    SDIO Port B: 0, SDIO Port C: 1
    NAND: Amlogic nand flash uboot driver, Version U1.06.020 (c) 2010 Amlogic Inc.
    SPI BOOT : continue i 0
    No NAND device found!!!
    NAND device id: 2c 44 44 4b a9 0
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0x2c (Micron D revision NAND 4GiB MT29F32G08CBADA)
    1 NAND chips detected
    #####aml_nand_init, with RB pins and chip->chip_delay:20
    bus_cycle=5, bus_timing=6, start_cycle=6, end_cycle=7,system=5.0ns
    oob size is not enough for selected bch mode: NAND_BCH60_1K_MODE force bch to mode: NAND_BCH40_1K_MODE
    aml_chip->oob_fill_cnt =168,aml_chip->oob_size =744,bch_bytes =70
    multi plane error for selected plane mode: NAND_TWO_PLANE_MODE force plane to : NAND_SINGLE_PLANE_MODE
    aml_nand_init:oobmul =1,chip->ecc.layout->oobfree[0].length=16,aml_chip->oob_size=744
    aml nand env valid addr: 48000 ,status =0
    key start_blk=2040,end_blk=2047,aml_nand_key_init:684
    aml nand key valid addr: ff020000
    aml nand key valid addr: ff220000
    aml nand key valid addr: ff420000
    aml nand key valid addr: ff620000
    CONFIG_KEYSIZE=0x10000; KEYSIZE=0xfffc; bbt=0x1330; default_keyironment_size=0xeccc
    i=0,register --- nand_key
    NAND bbt detect Bad block at 0
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    Creating 8 MTD partitions on "nandnormal":
    0x000000800000-0x000001000000 : "logo"
    0x000001000000-0x000001800000 : "aml_logo"
    0x000001800000-0x000002000000 : "recovery"
    0x000002000000-0x000002800000 : "boot"
    0x000002800000-0x000042c00000 : "system"
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    0x000042c00000-0x000062c00000 : "cache"
    0x000062c00000-0x000072c00000 : "backup"
    0x000072c00000-0x0000ff000000 : "data"
    nandnormal initialized ok
    detect mx chiprevD :1 and nand_type: 40
    nand_curr_device =1
    SPI BOOT,spi_env_relocate_spec : env_relocate_spec 53
    SF: Detected MX25L3205D with page size 256, total 4 MiB

    SPI NOR Flash have write protect!!!
    In: serial
    Out: serial
    Err: serial
    register usb cfg[0][1] = 9fe85d1c
    Net: Meson_Ethernet
    init suspend firmware done. (ret:0)
    Hit Enter key to stop autoboot -- : 5 4 3 2 1 0
    exit abortboot: 0
    Amlogic Ethernet Init
    Success: reset mac OK!(0)
    ETH PHY hardware reset OK
    find net phy id=0x7c0f1, phyad=1
    set_mac_mode(0)
    final_addr[rx-tx]: 0x9feee000-0x9feee600
    Ethernet reset OK
    MAC address is e8:18:63:50:1a:ce
    phy auto link failed
    half duplex
    10m
    BOOTP broadcast 1
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 2
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 3
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 4
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 5
    phy auto link failed
    phy auto link failed

    Retry count exceeded; starting again
    phy auto link failed
    phy auto link failed
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 1
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 2
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 3
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 4
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 5
    phy auto link failed
    phy auto link failed

    Retry count exceeded; starting again
    phy auto link failed
    phy auto link failed
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 1
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 2
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 3
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 4
    phy auto link failed
    phy auto link failed
    BOOTP broadcast 5
    phy auto link failed
    phy auto link failed

    Retry count exceeded; starting again
    phy auto link failed
    phy auto link failed
    phy auto link failed

    ][/code]
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Lorsque vous court-circuit le laisser comme ça pendant 30 secondes

    jusqu'à ce que vous voyez quelque chose comme ça

    Putty.png

  • moh26moh26 Posts: 127WeTek Community Member
    apres j'ai brancher mon cable reseau
    j'ai ca
    EEEE I3000000032940xf300110303;77520EEEE I400000004294_M6_BL1_3431>2534313
    TE : 77476
    BT : 16:48:10 May 4 2015

    CPU clock is 1200MHz


    wait pll-0x03 target is 0204 now it is 0x00000203

    DDR clock is 516MHz with Low Power & 2T mode

    DDR training :
    DX0DLLCR:40000000
    DX0DQTR:ffffffff
    DX0DQSTR:3db05001
    DX1DLLCR:40000000
    DX1DQTR:ffffffff
    DX1DQSTR:3db05001
    DX2DLLCR:40000000
    DX2DQTR:ffffffff
    DX2DQSTR:3db05001
    DX3DLLCR:40000000
    DX3DQTR:ffffffff
    DX3DQSTR:3db05001
    Stage 00 Result 00000000
    Stage 01 Result 00000000
    Stage 02 Result 00000000
    Stage 03 Result 00000000

    DDR init use : 42464 us

    HHH
    BootFrom SPI
    ucl decompress
    decompress true
    0x12345678
    Boot from int dev 1stSPI

    TE : 1303599

    System Started


    U-boot(wetek@) (May 04 2015 - 16:47:56)

    aml_rtc_init
    aml rtc init first time!
    clr h-ram
    DRAM: 1 GiB
    relocation Offset is: 105e0000
    MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6
    [mmc_register] add mmc dev_num=1, port=2, if_type=6
    SDIO Port B: 0, SDIO Port C: 1
    NAND: Amlogic nand flash uboot driver, Version U1.06.020 (c) 2010 Amlogic Inc.
    SPI BOOT : continue i 0
    No NAND device found!!!
    NAND device id: 2c 44 44 4b a9 0
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0x2c (Micron D revision NAND 4GiB T29F32G08CBADA)
    1 NAND chips detected
    #####aml_nand_init, with RB pins and chip->chip_delay:20
    bus_cycle=5, bus_timing=6, start_cycle=6, end_cycle=7,system=5.0ns
    oob size is not enough for selected bch mode: NAND_BCH60_1K_MODE force bch to mde: NAND_BCH40_1K_MODE
    aml_chip->oob_fill_cnt =168,aml_chip->oob_size =744,bch_bytes =70
    multi plane error for selected plane mode: NAND_TWO_PLANE_MODE force plane to :NAND_SINGLE_PLANE_MODE
    aml_nand_init:oobmul =1,chip->ecc.layout->oobfree[0].length=16,aml_chip->oob_sie=744
    aml nand env valid addr: 48000 ,status =0
    key start_blk=2040,end_blk=2047,aml_nand_key_init:684
    aml nand key valid addr: ff020000
    aml nand key valid addr: ff220000
    aml nand key valid addr: ff420000
    aml nand key valid addr: ff620000
    CONFIG_KEYSIZE=0x10000; KEYSIZE=0xfffc; bbt=0x1330; default_keyironment_size=0xccc
    i=0,register --- nand_key
    NAND bbt detect Bad block at 0
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    Creating 8 MTD partitions on "nandnormal":
    0x000000800000-0x000001000000 : "logo"
    0x000001000000-0x000001800000 : "aml_logo"
    0x000001800000-0x000002000000 : "recovery"
    0x000002000000-0x000002800000 : "boot"
    0x000002800000-0x000042c00000 : "system"
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    0x000042c00000-0x000062c00000 : "cache"
    0x000062c00000-0x000072c00000 : "backup"
    0x000072c00000-0x0000ff000000 : "data"
    nandnormal initialized ok
    detect mx chiprevD :1 and nand_type: 40
    nand_curr_device =1
    SPI BOOT,spi_env_relocate_spec : env_relocate_spec 53
    SF: Detected MX25L3205D with page size 256, total 4 MiB

    SPI NOR Flash have write protect!!!
    In: serial
    Out: serial
    Err: serial
    register usb cfg[0][1] = 9fe85d1c
    Net: Meson_Ethernet
    init suspend firmware done. (ret:0)
    Hit Enter key to stop autoboot -- : 0
    exit abortboot: 0
    Amlogic Ethernet Init
    Success: reset mac OK!(0)
    ETH PHY hardware reset OK
    find net phy id=0x7c0f1, phyad=1
    set_mac_mode(0)
    final_addr[rx-tx]: 0x9feee000-0x9feee600
    Ethernet reset OK
    MAC address is e8:18:63:50:1a:ce
    duplex
    100m
    BOOTP broadcast 1
    DHCP client bound to address 192.168.2.10
    Using Meson_Ethernet device
    TFTP from server 0.0.0.0; our IP address is 192.168.2.10; sending through gatewy 192.168.2.1
    Filename 'AP ▒'.
    Load address: 0x82000000
    Loading: *
    TFTP error: 'Get not supported' (0)
    Starting again

    BOOTP broadcast 1
    DHCP client bound to address 192.168.2.10
    Using Meson_Ethernet device
    TFTP from server 0.0.0.0; our IP address is 192.168.2.10; sending through gatewy 192.168.2.1
    Filename 'AP ▒'.
    Load address: 0x82000000
    Loading: *
    TFTP error: 'Get not supported' (0)
    Starting again

    BOOTP broadcast 1
    DHCP client bound to address 192.168.2.10
    Using Meson_Ethernet device
    TFTP from server 0.0.0.0; our IP address is 192.168.2.10; sending through gatewy 192.168.2.1
    Filename 'AP ▒'.
    Load address: 0x82000000
    Loading: *
    TFTP error: 'Get not supported' (0)
    Starting again

    BOOTP broadcast 1
    DHCP client bound to address 192.168.2.10
    Using Meson_Ethernet device
    TFTP from server 0.0.0.0; our IP address is 192.168.2.10; sending through gatewy 192.168.2.1
    Filename 'AP ▒'.
    Load address: 0x82000000
    Loading: T T T T T T T T T T
    Retry count exceeded; starting again
    BOOTP broadcast 1
    DHCP client bound to address 192.168.2.10
    Using Meson_Ethernet device
    TFTP from server 0.0.0.0; our IP address is 192.168.2.10; sending through gatewy 192.168.2.1
    Filename 'AP ▒'.
    Load address: 0x82000000
    Loading: T T T T T T T T T T
    Retry count exceeded; starting again
    BOOTP broadcast 1
    DHCP client bound to address 192.168.2.10
    Using Meson_Ethernet device
    TFTP from server 0.0.0.0; our IP address is 192.168.2.10; sending through gatewy 192.168.2.1
    Filename 'AP ▒'.
    Load address: 0x82000000
    Loading: *
    Abort
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!
    wetek#<INTERRUPT>
    wetek#
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Pouviez-vous tapez les commandes?

    et puis essayez d'installer Android comme nous avons parlé dans les messages précédents?

  • moh26moh26 Posts: 127WeTek Community Member
    oui je peut taper les commandes
    qu'elle message
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    avez-vous tapé
    mmcinfo
    fatload mmc 0 0x82000000 u-boot.bin
    sf probe 2
    sf erase 0 60000
    sf write 0x82000000 0 60000
    sf erase 0x100000 0x8000
    reset
    


    Puis coupez wetek
    Essayez d'installer Android en utilisant le bouton "Upgrade"?

  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    Si cela ne fonctionne pas, s'il vous plaît envoyer un courriel à l'appui revendeur

    Si vous avez acheté sur Wetek.com, s'il vous plaît nous contacter ici

    De cette façon, l'appareil sera remplacé

  • moh26moh26 Posts: 127WeTek Community Member
    ça a marcher après les commande son flache d’image merci
  • moh26moh26 Posts: 127WeTek Community Member
    voici le log svp dite moi ou et le probleme
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    mais vous étiez en mesure de saisir les commandes?

  • moh26moh26 Posts: 127WeTek Community Member
    le problème et résolue mais je veut savoir d’où vient le problème pour l’éviter la prochaine fois et es que mon wetek n'est pas défectueux
  • MasterChief117MasterChief117 Posts: 3,707Administrator - WeTek Community Manager
    il pourrait être lors de l'écriture du fichier uboot, il aurait été corrompu

Sign In or Register to comment.
Help Center

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

© Copyright 2014 - Creative Dreams | Powered by Vanilla
All times are UTC