Remote power trouble

    this is log of another u-boot (from beelink official firmware for GT1 Ultimate)

    this version con pass ram check at: DDR4 chl: Rank0+1 @ 912MHz - PASS

    Btw also this uboot version has the power on bug on H96 pro +

    Quote from bumerc

    please also test this uboot from the other github

    u-boot

    this u-boot can boot:

    but the power on bug is present:

    i've libreelec booted, turn off my board with remote and the system log this:

    after that i cannot power on with remote

    Quote from gulp79

    this u-boot can boot:

    Code
    BL2 Built : 20:32:17, Sep  8 2017.gxl g6296b83 - xiaobo.gu@droid12set vdd cpu_a to 1120 mvset vdd cpu_b to 1050 mvset vddee to 1000 mvBoard ID = 3CPU clk: 1200MHzDQS-corr enabledDDR scramble enabledDDR4 chl: Rank0+1 @ 792MHzRank0: 2048MB(auto)-2T-18Rank1: 1024MB(auto)-2T-18DataBus test pass!AddrBus test pass!-sLoad fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000New fip structure!Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x0002c600Load bl33 from eMMC, src: 0x00050200, des: 0x01000000, size: 0x00066400NOTICE:  BL3-1: v1.0(release):a625749NOTICE:  BL3-1: Built : 11:25:15, Aug 25 2017NOTICE:  BL31: BL33 decompress passmpu_config_enable:ok[Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07]OPS=0x82wdt: reset registers!a1 14 cc 9c 7a 4a 4f e 1 4 c0 16 [0.292295 Inits done]secure task start!high task start!low task start!ERROR:   Error initializing runtime service opteed_fastU-Boot 2015.01-g2735815-dirty (Apr 06 2018 - 21:58:59)DRAM:  3 GiBRelocation Offset is: b6eb6000register usb cfg[0][1] = 00000000b7f5b858[CANVAS]canvas initboot_device_flag : 1Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.init bus_cycle=6, bus_timing=7, system=5.0nsreset failedget_chip_type and ret:fffffffeget_chip_type and ret:fffffffechip detect failed and ret:fffffffenandphy_init failed and ret=0xfffffff1MMC:   aml_priv->desc_buf = 0x00000000b3eb66b0aml_priv->desc_buf = 0x00000000b3eb89d0SDIO Port B: 0, SDIO Port C: 1emmc/sd response timeout, cmd8, status=0x1ff2800emmc/sd response timeout, cmd55, status=0x1ff2800init_part() 293: PART_TYPE_AML[mmc_init] mmc init successdtb magic 5f4c4d41      Amlogic multi-dtb tool      Multi dtb detected      Multi dtb tool version: v2 .      Support 2 dtbs.        aml_dt soc: gxm platform: q201 variant: 3g        dtb 0 soc: gxm   plat: q201   vari: 2g        dtb 1 soc: gxm   plat: q201   vari: 3g      Find match dtb: 1start dts,buffer=00000000b3ebb200,dt_addr=00000000b3ec7200      Amlogic multi-dtb tool      Multi dtb detected      Multi dtb tool version: v2 .      Support 2 dtbs.        aml_dt soc: gxm platform: q201 variant: 3g        dtb 0 soc: gxm   plat: q201   vari: 2g        dtb 1 soc: gxm   plat: q201   vari: 3g      Find match dtb: 1parts: 1000:      logo   0000000002000000 101:  recovery   0000000002000000 102:       rsv   0000000000800000 103:       tee   0000000000800000 104:     crypt   0000000002000000 105:      misc   0000000002000000 106:      boot   0000000002000000 107:    system   0000000080000000 108:     cache   0000000020000000 209:      data   ffffffffffffffff 4init_part() 293: PART_TYPE_AMLeMMC/TSD partition table have been checked OK!check pattern successmmc env offset: 0x27400000In:    serialOut:   serialErr:   serialreboot_mode=normal[store]To run cmd[emmc dtb_read 0x1000000 0x40000]_verify_dtb_checksum()-917: calc 6046a875, store 6046a875_verify_dtb_checksum()-917: calc 6046a875, store 6046a875dtb_read()-1039: total valid 2dtb_read()-1106: do nothing      Amlogic multi-dtb tool      Multi dtb detected      Multi dtb tool version: v2 .      Support 2 dtbs.        aml_dt soc: gxm platform: q201 variant: 3g        dtb 0 soc: gxm   plat: q201   vari: 2g        dtb 1 soc: gxm   plat: q201   vari: 3g      Find match dtb: 1vpu: clk_level in dts: 7vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)vpu: vpu_clk_gate_init_offvpp: vpp_inithpd_state=1[1080p60hz] is invalid for cvbs.set hdmitx VIC = 16config HPLL = 2970000HPLL: 0xc000027bconfig HPLL donej = 4  vid_clk_div = 1hdmitx: set enc for VIC: 16HDMITX-DWC addr=0x10004006 rd_data=0x40Error: HDMITX-DWC exp_data=0xff mask=0x9frx version is 1.4 or below  div=10hdmtix: set audiohdmitx phy setting donevpp: vpp_pq_load pq val error !!!Net:   dwmac.c9410000amlkey_init() enter![EFUSE_MSG]keynum is 4[BL31]: tee size: 0...

    but the power on bug is present:

    i've libreelec booted, turn off my board with remote and the system log this:

    Code
    LibreH96:~ # [   43.593559@0] reboot: Power downbl31 reboot reason: 0x108bl31 reboot reason: 0x108system cmd  0.bl30 get wakeup sources!process command 00000006bl30 enter suspend!cpu clk suspend rate 1000000000suspend_counter: 1Enter ddr suspendfirst time suspendddr suspend time: 1886usstore restore gp0 pllprocess command 00000001CEC cfg:0x0000set vddee to 0x035cmv=== PROCESS EXCEPTION: 04 ====== xPSR: 20000000 ===r0 :00000000 r1 :02c59fb1 r2 :00000000 r3 :c883c298r4 :c883c294 r5 :1000c068 r6 :c883c1bc r7 :c883c2e0r8 :c883c2a0 r9 :c883c29c r10:00000000 r11:1000c022r12:00000000 sp :1000d320 lr :1000b58b pc :00000000Instruction access violationmmfs = 1, shcsr = 70001, hfsr = 0, dfsr = 0=========== Process Stack Contents ===========1000d340: 00000000 c883c298 0000000a 1000d4001000d350: 00000001 1000d600 00000000 000000001000d360: 00000000 00000000 00000000 1000a0711000d370: 00000000 00000000 00000000 10000ac9GXM:oting...

    after that i cannot power on with remote

    1. Therefore, you should test the two versions and not search other forums. So it is very difficult to help someone. uboot gt1 does not support * 3g.dtb, the manufacturer did not integrate it for whatever reason

    Code
    Find match dtb: 0

    for * 3g.dtb support there should be a "1" in the place

    2. this uboot does not contain a custom suspend FW and there seems to be a problem with the size calculation. It should only serve for testing to locate the bug.

    The bug is localized, we just have to figure out the most suitable frequency rate. Wait for the update.

    Remote power trouble

    Maybe i dont understand it right. I boot with my normal LE sdcard, write zero to /dev/env and /dev/bootloader and than i insert the Emergency System and write the new boot loader?

    Did i forget something, because if i power off without a bootloader, the system doesnt boot? Or should it boot from SDCard2? Because in my case, it didnt work and i had to restore via USB Burning tool

    Quote from TheChief

    Remote power trouble

    Maybe i dont understand it right. I boot with my normal LE sdcard, write zero to /dev/env and /dev/bootloader and than i insert the Emergency System and write the new boot loader?

    Correctly

    Quote

    Did i forget something, because if i power off without a bootloader, the system doesnt boot? Or should it boot from SDCard2? Because in my case, it didnt work and i had to restore via USB Burning tool

    it should boot from the sdcard2. Please note - the bootloader in the installation guide is only suitable for devices with LPDDR3 memory (blue pcb v5 and v6).

    I have flashed this u-boot via Android ROM customization method:

    u-boot.bin_DDR3@792Mhz

    This time - there was no need to revive the box by short-circuiting certain pins on the eMMc... :)

    However,

    LE still cannot power up from the remote, once it has been powered down.

    How can I gather any serial debug information for eventual troubleshooting further?

    Thank you in advance! :thumbup:

    P.S. I am using gxm_q200_3g.dtb on my green v2.2 board...

    Quote

    it should boot from the sdcard2. Please note - the bootloader in the installation guide is only suitable for devices with LPDDR3 memory (blue pcb v5 and v6).

    I have the blue one S32-V6 (LPDDR3).

    I will try it again later. Maybe the second SD card is broken.

    There are two reasons for this. 1. The remote control code does not match the code in the bootloader. 2. Your power supply is poor quality or slightly weak.

    So you can tell if the power supply is not ok.

    - Pull out the HDMI cable on the box.

    - Turn on the box and wait until it has completely booted.

    - Then switch off the box by remote control again.

    - After switching off, try switching the box on by remote control.

    When the box starts up, it's up to the bad power supply.

    Please post your remote.conf file

    Edited once, last by bumerc (April 9, 2018 at 7:30 PM).

    There's new development on my case:

    With this build - CoreELEC-S912.arm-9.0-devel-1523265719 - the box works FLAWLESSLY!

    Therefore,

    here's a link to an amended Android ROM (Wisdom), in which the fixed u-boot.bin_DDR3@792Mhz has been already incorporated and it's been tested on green v2.2 H96Pro+ board:

    S912_H96_3G_DDR34_171120_MAC_ubootfix.7z

    Flash the ROM via USB Burning Tool v2.1.2 or Burn Card Maker v2.0.3 on your own risk, of course. :P

    Good luck! :thumbup:

    Thank you, @bumerc !

    PayPal account for a small token of gratitude, please. :blush:

    I would not recommend trying the abovementioned ROM on LPDDR3.

    Apparently the u-boot here is for normal DDR3,

    and there is an enourmous chance to brick the box if you flash it on LPDDR3 one.