Hi there, I have tried your image with my MXQ Pro 4K (2GB RAM, 16GB storage, rtl8723bs,10/100Mbps LAN FC-518LS 1747) with the green board and code hx_s905x v2.42.
- By using the device tree gxl_p212_1g.dtb, I managed to get it booted to LE. I have tried it with gxl_p212_2g.dtb but no success. Eventually, I only got 1GB of RAM usable. On Android, I have checked with System Info, free -m, AIDA64 and they both say the box has 2GB of RAM. Also on the board has 2 block of 256x4 memory cell, so I'm pretty sure this board has 2GB of RAM, not fake ones.
- Also, is the cpu_freq max at 1200MHz? I have heard that this S905x can go up to 1536MHz, is it right? So why we have to limited it lower than it can deliver? Maybe for stability or heat issues?
Could you please have a look at my dtb.img extracted from Android Nougat v7.1.2, and help me to modify a dtb version for my box to get 2GB of usable RAM? Thanks in advance.
Note: I have tried to de-compiled it into dts, but from there, I have no idea what to modify, as well as when I did some changes, compile it back to dtb, put in the sdcard, and it stuck at S905X logo
It's not an easy process for me :(( Most of the differences between two files is this line:
linux,phandle = <0x2>;
phandle = <0x2>;
So I wondering if I can change all of them to match with the dts from android version? How to make it recognizes 2GB RAM and cpu_freq up to 1.536GHz?
And about the memory, I see this:
### From Android ###
memory@00000000 {
device_type = "memory";
linux,usable-memory = <0x0 0x100000 0x0 0x3ff00000>;
};
### From gxl_p212_1g.dtb ###
memory@00000000 {
device_type = "memory";
linux,usable-memory = <0x0 0x100000 0x0 0x3f000000>;
};
Am I just need to change 0x3f000000 into 0x3ff00000 then my box will see 2GB RAM? Or else?
White.
Update 14/07/2018:
Quote
1. The seller had conned me, item is on the returning way for a full refund.
2. I have bought another box with S905X, using the same SDCard with old LE 8.2.4.2 image that I use for the returned box, the same dtb.img file -> the cpu_freq is reading at 1512MHz. So for this matter, it should be something to do with bootloader or uboot or whatever it called... Is anyone have any idea? Thanks so much.