Remote power trouble

    Quote from tyrol_gangster

    Next day it somehow made it to the sleep mode (red led) ON ITS OWN!, I shut it down and it never woke again.

    If you have a Red Light and it won't cold boot or power on from remote but have a Red standby Light you have a bad soldering on the board.

    They use Flow soldering method on these boards.

    Heat gun on the board will reflow the solder. Google it.

    [S905x] Tanix Tx5 Pro

    #290

    Edited 3 times, last by kostaman (February 9, 2018 at 8:21 AM).

    I would like to test it on my sd-card, but I don't know what I have to do?

    In which folder or where on the sd-card I have to copy the "u-boot.bin.sd.bin"?

    Paul

    HI bumerc!

    How did you get those? Did you build them from sources??

    Please give use instructions on how to test it without bricking our devices.. ^^

    Fortune favors the brave! ;)

    Many will wait someone to have the courage and be the first one fixed/bricked its box. :D

    Probably - it won't be me, because I've lost interest in this H96Pro+ box and it's catching dust for quite some time...

    Quote from Paul69

    I would like to test it on my sd-card, but I don't know what I have to do?

    In which folder or where on the sd-card I have to copy the "u-boot.bin.sd.bin"?

    Paul

    I will soon provide a complete image (u-boot + LE) for testing purposes. To boot your box from the sd card, the bootloader in the internal memory must be deleted or you know exactly how you put your box in upgrade mode (eg by shorting the pins -> change bootsequence ..) I have no time at the moment to test it yourself and no h96pro + box.

    To test the bl301 firmware of this github I compiled a version for gxl_p212 devices (S905X) and successfully tested it on my mini m8s II board. Then I compiled a version for Q200 / 201 devices, you should test yourself.:)

    Hello guys, I have good news.:)

    I have compiled a new version of u-boot - adapted for the following board:

    H96 Pro +

    PCB: blue

    3G + 32G + 9377

    S32-V6 (LPDDR3), clock rate 800MHz

    Installation instructions and photos follow a little later.

    For other RAM memory types please use the links above.

    My test results (power off / on not yet tested).

    skybluega

    When I turn off I get the following error:

    gxm_q201_turn_off_log

    LibreELEC:~ # [ 40.982632@0] reboot: Power down

    bl31 reboot reason: 0x108

    bl31 reboot reason: 0x108

    system cmd 0.

    bl30 get wakeup sources!

    process command 00000006

    bl30 enter suspend!

    cpu clk suspend rate 1000000000

    suspend_counter: 1

    Enter ddr suspend

    first time suspend

    ddr suspend time: 1877us

    store restore gp0 pll

    process command 00000001

    CEC cfg:0x0000

    set vddee to 0x035cmv

    === PROCESS EXCEPTION: 04 ====== xPSR: 20000000 ===

    r0 :00000000 r1 :02a5f26b r2 :00000000 r3 :c883c298

    r4 :c883c294 r5 :1000c068 r6 :c883c1bc r7 :c883c2e0

    r8 :c883c2a0 r9 :c883c29c r10:00000000 r11:1000c022

    r12:00000000 sp :1000d320 lr :1000b5e3 pc :00000000

    Instruction access violation

    mmfs = 1, shcsr = 70001, hfsr = 0, dfsr = 0

    =========== Process Stack Contents ===========

    1000d340: 00000000 c883c298 0000000a 1000d400

    1000d350: 00000001 1000d600 00000000 00000000

    1000d360: 00000000 00000000 00000000 1000a071

    1000d370: 00000000 00000000 00000000 10000ac9

    GXM:oting...

    one of the reasons for an exception could be MPU mismatch

    see also here, starting with CFSR..

    Interesting is the state of the MMFSR (see Table 4.25), in our case:

    Code
    Instruction access violation
mmfs = 1, shcsr = 70001, hfsr = 0, dfsr = 0

    The bit assignment of the MMFS register is as follows:

    [1] DACCVIOL -> Data access violation flag..

    I have another idea, in a couple of hours I will report the results.

    regards