Posts by TheChief

That could be. I just wonder, that the original bootloader works with no problem. I try to get another device.

Quote from bumerc

TheChief

test this please:

u-boot@792Mhz_lpddr3

u-boot@792Mhz_lpddr3_forced_rgmii

Both versions freezes after some minutes running, I have no more idea and give up. Maybe something is broken and i get another device.

TWRP already running on my box. Will try to make a backup there. Didnt think on that. Thanks.

Before i do another test, is there any way to create a backup of the entire Android system including working u-boot, that i can easily flash with Burning tool? Would save much time.

Just get this:

GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 90010

BL2 Built : 13:27:37, Oct 25 2017. gxl g56b77aa - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
LPDDR3 chl: Rank0+1 @ 792MHz

bist_test rank: 0 17 0b 23 33 1b 4b 10 00 21 3f 26 58 1b 0b 2c 31 19 49 18 04 2d 32 17 4d 717  rank: 1 17 0a 24 33 1c 4b 10 00 20 3d 27 54 1a 0a 2b 31 1a 49 18 04 2d 2f 15 4a 717
Rank0: 2048MB(auto)-2T-3

Rank1: 1024MB(auto)-2T-3
AddrBus test pass!
-s
emmc switch 3 ok
BL2: rpmb counter: 0x000000ac
emmc switch 0 ok
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl33 from eMMC, src: 0x00050200, des: 0x01000000, size: 0x00066c00
NOTICE:  BL3-1: v1.0(release):7c45a4f
NOTICE:  BL3-1: Built : 14:09:28, Oct 13 2017
NOTICE:  BL31: GXL normal boot!
NOTICE:  BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3255-1a77b01 2017-09-15 16:58:02 xiaobo.gu@droid12]
OPS=0x82
wdt: reset registers!
68 ed de 3e 1c 0 71 de c5 d5 8c 71 [1.150944 Inits done]
secure task start!

=== PROCESS EXCEPTION: 04 ====== xPSR: 01000000 ===
r0 :00000001 r1 :1000b4bc r2 :1000b088 r3 :1000b068
r4 :1000d400 r5 :00000000 r6 :00000000 r7 :00000000
r8 :00000000 r9 :00000000 r10:00000000 r11:00000000
r12:00000000 sp :1000d350 lr :1000a039 pc :1000a68a
Data access violation, mfar = 1000b084
mmfs = 82, shcsr = 70001, hfsr = 0, dfsr = 0

=========== Process Stack Contents ===========
1000d370: 00000000 00000000 00000000 10000ac9
1000d380: 00000000 00000000 00000000 00000000
1000d390: 00000000 00000000 00000000 00000000
1000d3a0: 00000000 00000000 00000000 00000000

Thanks, will try later and give you response.

Quote

You forgot to mention that it just does not work for you. What is the length of your network cable? Does the router have 1Gbit connection, or only 100Mbit? If you have CE installed, try this dtb

What can change the DTB file, if Android also crashes? Cable lenght is maybe 1 or 2 meter, gigabit connection is no problem (AVM 7490)

I see, that i have Longsys LTM8830 WLAN chip instead of Atheros 9377, but dont think, it causes the crashes. I use cable connection.

Quote from bumerc

You forgot to mention that it just does not work for you. What is the length of your network cable? Does the router have 1Gbit connection, or only 100Mbit? If you have CE installed, try this dtb

I wrote "For me..."

But we can continue discussion in the other thread.

Quote from johnberg

Thank you very much TheChief.

I read this thread about "U-boot", but I think it is a little bit too risky for me to do.

When I read "at your own risk" and "brick your box" I am getting a little bit scared.

It is also difficult to find the one and only workaround.

I think I keep it as it is and just boot to Andoid at the end of the evening, press the red button and it is also shutdown properly

For me the uboot fix does not work. Don't know why. My system then always crashes/hangs, but power on/off works.

Quote from johnberg

is this really the solution to power down the device right from LE?

Is this bringing the device in the same wakeup modus as when you boot to internal (Android) first and then shut off with the red button on the original remote?

This is the way I power down now and I am looking so long for a proper solution to power off right from LE.

I am using Wrxtasy's 8.2.4-subtitles-ff and have a H96 Pro+

Update

Ik tried workaround from Kszaq above.

But it does not have any effect on powering off from LE.

If you power off you can't boot anymore with the remote and need to off/on powersupply.

When I Winscp to the sleep.conf.d folder again after reboot even a new sleep.conf.sample file has been created together with the modified sleep.conf file

How do I get this standby modus without needing to boot to Android and power off from there

Display More

johnberg

Read this thread, beginning around page 6. Maybe you find the fixed u-boot for your device here.

No, i meant it looks good for me with disabled deinterlacing. With enabled i have the same issue.

Maybe depends in TV or Receiver. For me Video looks good. Dont know, if they do additional video processing.

I'm not sure, because Android also crashes/freezes and without you u-boot CE/LE/Android not. Has nothing to do with CE/LE or Android i think. Maybe a small piece in u-boot, wrong memory addressing or something.

Followed you steps, but still crashing with with your uboot. DTB doesnt work for me, is it for LE9? If i use q201 from coreelec image, i have no Wired Network. Dont worry, dont spend more time in my problem. I dont know, why it doesnt work on my box.

With this build it looks better for me. Hope i will get now freezes anymore.

EDIT: No, still crashing

Seems to do more tests now:

GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0;EMMC:0;                        READ:0;0.0;CHK:0;
TE: 86468

BL2 Built : 20:32:17, Sep  8 2017.
gxl g6296b83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
LPDDR3 chl: Rank0+1 @ 792MHz
DDR0_PUB_CATR0 1 value
DDR0_PUB_CATR0: 0x00141020....
DDR0_PUB_CATR1: 0x0203aaaa....
DDR0_PUB_PGSR0: 0x8000003f....
Rank0: 2048MB(auto)-2T-3
Rank1: 1024MB(auto)-2T-3
DataBus test pass!
AddrBus test pass!
-s

Quote from bumerc

only q201, q200 will not work. I will do another build especially for you. Furthermore, I advise you to use the kernel with the latest changes.

Thanks. But the config for the board would be also interesting, that i can compile by myself. You can also PM me your configuration file.

With q201 i get Addr bus failed, with DDR_TYPE set to LPDDR3@792Mhz

Ah ok, i see. Did you use q200 or q201 for your system? What configs did you set? My u-boot just detects 1500MB RAM, so maybe i missed something.

And what about the Memory speed changes? Is there any special reason, that u disabled auto detection?