dead wetek?

There are 25 replies in this Thread which was already clicked 4,520 times. The last Post () by filipedbc.

  • this is my putty log


    EEEE I3000000032940xf3001103 03;77520EEEE I400000004294_M6_BL1_3431 >2534313
    TE : 77476
    BT : 11:09:43 Mar 26 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 : 42472 us


    HHH
    BootFrom SPI
    ucl decompress
    decomprõ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: 0 ,status =0
    key start_blk=2040,end_blk=2047,aml_nand_key_init:684
    aml nand key valid addr: ff000000
    aml nand key valid addr: ff200000
    aml nand key valid addr: ff400000
    aml nand key valid addr: ff600000
    CONFIG_KEYSIZE=0x10000; KEYSIZE=0xfffc; bbt=0x1330; default_keyironment_size=0xeccc
    i=0,register --- nand_key
    NAND bbt detect Bad block at 0
    Creating 2 MTD partitions on "nandnormal":
    0x000000800000-0x000001000000 : "mtd1"
    0x000001000000-0x000008000000 : "mtd2"
    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] = 9fe85cf4
    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:2f:b8
    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
    p


    - - - Updated - - -


    anyone now this error at start up wetek?
    BOOTP broadcast 1
    phy auto link failed
    phy auto link failed


    - - - Updated - - -


    hi guys, my problem is solved.
    i get good online help from wetek servicedesk.


    thanks paulo.


    this is what my problem fixed.


    Your uboot seems to be searching some network, I'll give you some instructions in order to erase the enviroment variables:
    Turn Off your WeTek by unpluging power cable
    Connect debug cable and start a terminal session
    Turn On WeTek, pluging in power cable
    As soon first log lines appear break boot by pressing CTR+C
    You should see now prompt "wetek#" and enter now this commands:
    sf probe 2
    sf erase 0x100000 0x8000
    reset

  • Hello, can you guys provide the files again? Thank you

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!