& Runs DDR4 @ 792MHZ -
nop, "PASS" is missing behind
Posts by bumerc
-
-
-
So far only theoretically. I need a full log with RAM initialization and a beta tester.
-
ok it worked
and its powering on and off from the remote in le 8.2.2.3 kszaq build
can i get a link to your latest ddr3 uboot @ 792
just incase the one in S912_H96_3G_DDR34_171120_MAC_ubootfix
is an old build with problems
I'm not concerned with the composition of Android systems. Later I will provide the link with update.
-
Sorry im not explaining it right
PC3-12800 Runs at 800mhz which is 1600 DDR
is the 912mhz the actual mhz e.g. 1824 DDR
Supported DDR3 CLK Range:
7-7-7: 375 ~ 533mhz
9-9-9: 533 ~ 667mhz
11-11-11: 667 ~ 800mhz
12-12-12: 800 ~ 933mhz
13-13-13: 933 ~ 1066mhz
-
It bricked btw flashing 912
flashing my stock bootloader back now via sd card
That's why I need log from Serial console
-
sorry dont work for me!
These dtb files are from the Android stock ROM and must first be adapted to LE / CE kernels.
-
is that 912mhz/1824ddr
or
406mhz/912mhz ddr
Both memory variants run at 912Mhz
-
is there any way to get that without serial access as i dont have a serial cable
No.
Please test the u-boot@912Mhz_DDR3. I doubt that your stock uboot runs over the 1000..Mhz range
-
i would like to retain alteast the ram speed that the stock uboot uses
then i need a log from stock u-boot
-
I can not connect the box to the pc to extract the device tree in abd shell , help!!!
hi, here your dtb file.. extracted from orig. Android 6.0 FW
-
-
...Maybe a small piece in u-boot, wrong memory addressing or something.
All devices with LPDDR3 work without problems with this u-boot, except yours. Mine runs day and night. Nobody has any trouble with his box until now.
At the memory addressing nothing was changed.
-
Please make some photos of the PCB, memory type (ddr3, ddr4 or lpddr3) is crucial
Edit: You have DDR3-
1600..? I'll post it late at night. -
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.
You seem to be using some application that causes the kernel crash, this has nothing to do with u-boot.
Please use dtb from here (gxm_q201_3g_gbit_phy.dtb), I made a small mistake.
Ask CE developers about the possibility of adding rgmii support to q201 dtb.
-
I do not see any bugs that could be caused by the bootloader.
please do another test:
1. Erase the bootloader partition (/dev/bootloader) and turn off the box.
2. Format sdcard in FAT32 -> flash u-boot.bin.sd.bin on sdcard -> copy u-boot.bin to P1 -> insert sdcard in the box and turn it on
3. enter the following commands in the uboot terminal (gxm_q201_v1 # ...):
Codestore erase boot fatload mmc 0 ${loadaddr} u-boot.bin store rom_write ${loadaddr} 0 100000 defenv saveenv4. Switch off the box again -> remove sdcard with u-boot.bin.sd.bin -> insert sdcard with CoreELEC -> switch on and continue testing.
Please trythis dtb -
Thank you for your reply.
I have fixed the bug. You do not have to disable the CEC driver
Download (for LPDDR3 Devices)
-
i've updated the LE9 last build with an Devel Update because 4K isuesses... now the box will not power on again after switch off with remote...
need a new uboot?
For testing - try switching the box on and off without HDMI cable.
