WeTek Community Forum
Hi WeTek Fan! :)

Please check our WeTek Closed BETA program: http://www.wetekforums.com/v/discussion/31382/call-for-closed-beta-on-wetek-play-2?new=1

Give me also the feedback over the new look on our community forum: http://www.wetekforums.com/v/discussion/31383/new-forum-look?new=1

Thanks
MasterChief117

Problem in Nand Boot-up but working fine via SD card

hsk4uhsk4u Posts: 10WeTek Community Member
Hi All & Support team,

I am having strange issue with my 1 year + old WP1 Openelec version. I have PB Enigma on SD card and had Openelec latest version on Nand (Kodi 17.1).

Everytime I power off the box (by removing the power cable) and boot from SD card the box works fine but if I take out the SD card out to boot from the Nand I get error saying ..

Forced fsck failed. Your system is broken beyond repair
Please re-install OpenELEC

Press enter to shutdown now

I have reinstalled Openlec few time by using recovery method but as soon the box is power off and switched back to SD card the issue reappears on next boot up in Nand.

I have tried to install Liberelec latest version 8.** but still same issue.

Not sure how to fix it.

So the issue is with Nand boot-up and not SD card.

PS- I would like to install Liberelec on Nand so I can use TVheadedend and Kodi 17.3 and want to keep my PB Enigama on SD card.

Cheers

Comments

  • codesnakecodesnake Posts: 627WeTek Community Member, Developers
    I think it is not good idea to just remove the power cable. For system to shutdown properly you need to power it off with power button on the box or using power button on the remote.
  • AnimaAnima Posts: 1,633WeTek Support Team
    Hello

    You will need to make a clean installation on the NAND, since your device seems to be corrupt.

    You can still keep PBnigma on the Sdcard, just use a different one to install Openelec in the NAND.

  • hsk4uhsk4u Posts: 10WeTek Community Member
    Hi Anima

    Thanks for the reply. What do you mean by clean install? I have tried to install 2 time to install latest version of liberelc and openelec by using formated sd card and pin hole recovery method. Can you please send some instructions regarding clean install?

    Do I need R232 cable for that?

    What version is recommended to install on openelec wetek 1. I think originally it was version 5.**

    @codesnake thanks. I agree. I should be careful but I don't that is creating issue. I always have been doing the same way to power off and never had any issue in past.
  • codesnakecodesnake Posts: 627WeTek Community Member, Developers
  • AnimaAnima Posts: 1,633WeTek Support Team
    hsk4u said:

    Hi Anima



    Thanks for the reply. What do you mean by clean install? I have tried to install 2 time to install latest version of liberelc and openelec by using formated sd card and pin hole recovery method. Can you please send some instructions regarding clean install?



    Do I need R232 cable for that?



    What version is recommended to install on openelec wetek 1. I think originally it was version 5.**



    @codesnake thanks. I agree. I should be careful but I don't that is creating issue. I always have been doing the same way to power off and never had any issue in past.

    Hi

    that is exactly the process I mentioned. :)

    If you have tried it already without success, could you take a serial (RS-232) log? so we can see what is happening with it!

  • hsk4uhsk4u Posts: 10WeTek Community Member
    Thanks. I have ordered the adapter so will send the logs.

    Yes , I tried few time. I think, The issue happened when I tried to download IPTV player plugin on one of the Enigma image few weeks ago. It asked me to download several files and then crashed the box. Also never installed the plugin as well. I reverted back to PB Enigama but when I tried Openelec next time it came with message.

    Since then I tried three times with fresh clean but the issue return.

    BTW. How to check the logs?
  • ThrallThrall Posts: 2,786WeTek Support Team
  • hsk4uhsk4u Posts: 10WeTek Community Member
    Hi all,

    I have finally managed to get the logs. Please see below- this is not full log. I dont know how to attach the log file

    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.08.04 20:45:48 =~=~=~=~=~=~=~=~=~=~=~=
    EEEE I3000000032940xf3001103 03;77520EEEE I400000004294_M6_BL1_3431 >2534313
    TE : 77476
    BT : 22:19:13 Jan 15 2016

    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 : 1549641

    System Started


    U-boot(wetek@) (Jan 15 2016 - 22:18:55)

    aml_rtc_init
    aml rtc init first time!
    clr h-ram
    DRAM: 1 GiB
    relocation Offset is: 105c4000
    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: 70000 ,status =0
    key start_blk=2040,end_blk=2047,aml_nand_key_init:684
    aml nand key valid addr: ff010000
    aml nand key valid addr: ff210000
    aml nand key valid addr: ff410000
    aml nand key valid addr: ff610000
    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 "nand1":
    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 : "userdata"
    nand1 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] = 9fe85fa4
    Net: Meson_Ethernet
    init suspend firmware done. (ret:0)
    detect_storage
    nand exist return 0
    setenv storage nand
    reboot_mode=charging
    wipe_data=success
    ir init
    Hit Enter key to stop autoboot -- : 1  0
    exit abortboot: 0
    Checking for OpenElectv ...
    sdio_detect return 0
    [mmc_init] SDIO Port B:0, SD or TSD: Card did not respond to voltage select! mmc->block_dev.if_type=7
    Checking for Linux ...
    [mmc_init] SDIO Port B:0, SD or TSD: Card did not respond to voltage select! mmc->block_dev.if_type=7
    compatible nand
    Booting from nand ...

    NAND read: logo whole chip
    8388608 bytes read: OK
    [ImgPck]ver=0
    Creating 1 MTD partitions on "nand1":
    0x000001800000-0x000011c00000 : "mtd=0"
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    UBI: attaching mtd0 to ubi0
    UBI: physical eraseblock size: 2097152 bytes (2048 KiB)
    UBI: logical eraseblock size: 2080768 bytes
    UBI: smallest flash I/O unit: 8192
    UBI: VID header offset: 8192 (aligned 8192)
    UBI: data offset: 16384
    NAND bbt detect factory Bad block at b400000
    NAND bbt detect factory Bad block at b600000
    UBI: attached mtd0 to ubi0
    UBI: MTD device name: "mtd=0"
    UBI: MTD device size: 260 MiB
    UBI: number of good PEBs: 128
    UBI: number of bad PEBs: 2
    UBI: max. allowed volumes: 128
    UBI: wear-leveling threshold: 4096
    UBI: number of internal volumes: 1
    UBI: number of user volumes: 1
    UBI: available PEBs: 0
    UBI: total number of reserved PEBs: 128
    UBI: number of PEBs reserved for bad PEB handling: 2
    UBI: max/mean erase counter: 2/1
    UBIFS: mounted UBI device 0, volume 0, name "system"
    UBIFS: mounted read-only
    UBIFS: file system size: 235126784 bytes (229616 KiB, 224 MiB, 113 LEBs)
    UBIFS: journal size: 16646145 bytes (16256 KiB, 15 MiB, 6 LEBs)
    UBIFS: media format: w4/r0 (latest is w4/r0)
    UBIFS: default compressor: LZO
    UBIFS: reserved for root: 5182151 bytes (5060 KiB)
    Loading file 'KERNEL' to addr 0x82000000 with size 6345076 (0x0060d174)...
    Done
    hdcp get form storage medium: nand
    read:addr:0xff010000,phy_blk_addr:2040,phy_page_addr:8,aml_nand_get_key:125
    don't found keyname,uboot_key_read:1634
    prefetch hdcp keys from nand failed
    ## Booting kernel from Legacy Image at 82000000 ...
    Image Name: Linux-3.10.99
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 6345012 Bytes = 6.1 MiB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
    OK
    uboot time: 8574947 us.
    machid from environment: 0x4e27
    EFUSE machid is not set.
    Using machid 0x4e27 from environment

    Starting kernel ...


  • ThrallThrall Posts: 2,786WeTek Support Team
    This is the entire log?

    Can you let me know the files you used to reinstall LibreElec on the NAND?

    Best Regards

  • codesnakecodesnake Posts: 627WeTek Community Member, Developers
    @hsk4u After some investigation I found that it is not possible to use OE/LE in NAND and Enigma on SD-card. OE/LE and Enigma has different NAND partition tables in their configs. Amlogic NAND driver updates partition table on each boot, so when you boot Enigma from SD-card it screws up the NAND partition table and OE/LE cannot boot anymore because it expects different partition layout.
  • hsk4uhsk4u Posts: 10WeTek Community Member
    Part 2 of the log file
    Thrall said:

    This is the entire log?

    Can you let me know the files you used to reinstall LibreElec on the NAND?

    Best Regards

    Hi Thrall- Thank you for the response. no it is not full log. The log was too long and I could not copy all here as it exceeded the limit. How can I attached a file here?

    I used latest versions for Nand from these websites. Followed pin hole method to install.

    LibreELEC-WeTek_Play.arm-8.0.2.zip (info)

    https://libreelec.tv/downloads/wetek-play-and-wetek-openelec/

    http://openelec.tv/get-openelec




  • hsk4uhsk4u Posts: 10WeTek Community Member
    codesnake said:

    @hsk4u After some investigation I found that it is not possible to use OE/LE in NAND and Enigma on SD-card. OE/LE and Enigma has different NAND partition tables in their configs. Amlogic NAND driver updates partition table on each boot, so when you boot Enigma from SD-card it screws up the NAND partition table and OE/LE cannot boot anymore because it expects different partition layout.

    Hi Codesnake- Thanks for your time. I am not sure if it is correct though. I have been using PB Enigma (version 5.3) and Openelec for more than 1 year and it was working fine.

    However , it could be related to upgrade to PB Enigma 6.1 and Openelec/Liberelec version 8. I upgraded to PB Enigama2 few months ago which could be creating this problem?

    Over the week-end I tried to do Soft Recovery and Hard Recovery of the box by following tutorials on the site. I could not do any of them. On soft recovery I struggled to break the boot sequence by pressing Control + C. Nothing happens when I pressed Control C.

    Then I tried to do Hard Recovery. I think i followed the instructions correctly but I could not type anything on the Putty Terminal. After spending all my afternoon, I gave up and reinstalled Liberelec.

    I can confirm that the issue is with SD card boot-up- as soon as I boot from SD card (PB Enigama 6.1) it breaks the Nand install. I shall try to to reinstall PB Enigama 5.3 to confirm the issue is with the latest version of PB Enigma or something else.
  • codesnakecodesnake Posts: 627WeTek Community Member, Developers
    @hsk4u Why you try to do Soft/Hard recovery if you can install LibreELEC into NAND without problems? Or you want to install Android?

    BTW You can use some service such as pastebin.com to upload your logs and post just links here.
  • hsk4uhsk4u Posts: 10WeTek Community Member
    null
    Hi codesnake. I was not sure what to do so thought this will update the boot loader and fix the issue.

    Are you saying you can't use soft recovery on a working box? In my case the box was broken unless you reinstall liberelc/Openelec on nand.


    Anyway just to update. I have reinstalled pb Enigama 5.3 on sd card. And liberelc on Nand.

    It seems working now. So the issue was with 6.1 pb Enigama. It breaks the Nand.
Sign In or Register to comment.
© Copyright 2014 - Creative Dreams | Powered by Vanilla
All times are UTC