Hi everone, I 'm new here and I 'm a green-hand in CE. Recently I am trying to port CE to my skyworth E900V21E box, which uses S905L2 (aka P261). I have read many topics in this forum and after that, I decided to port CE 9.2.8 to my box. However, I got troubled with booting. Although I have avoided cycle-rebooting, I still can’t boot CE successfully. The screen will stop at the first screen (aka bootloader screen). Here are my DTB file and the TTL log. Anyone can help me? Thx very much
(Due to new user limit, I uploaded my files to the github, and here are links:)
/dts-v1/;
/ {
interrupt-parent = <0x01>;
#address-cells = <0x02>;
#size-cells = <0x02>;
compatible = "amlogic,x7-5g\0amlogic,s905l2\0amlogic,meson-gxl";
model = "Amlogic Meson GXL (S905L2) X7 5G Tv Box";
aliases {
mmc0 = "/soc/apb@d0000000/mmc@70000";
mmc1 = "/soc/apb@d0000000/mmc@72000";
mmc2 = "/soc/apb@d0000000/mmc@74000";
serial0 = "/soc/bus@c8100000/serial@4c0";
ethernet0 = "/soc/ethernet@c9410000";
};
reserved-memory {
#address-cells = <0x02>;
#size-cells = <0x02>;
show original
GXLX:BL1:9ac50e:4a8da0;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 93539
BL2 Built : 17:21:16, Mar 19 2021.
gxl g767b31d - longyong.chen@droid02-sz
Board ID = 1, adc=77
set vcck to 1070 mv
set vddee to 1070 mv
CPU clk: 1200MHz
DDR4 chl: Rank0+1 @ 912MHz - FAIL
DDR4 chl: Rank0 @ 912MHz - FAIL
DDR4 chl: Rank0 16bit @ 912MHz - FAIL
DDR3 chl: Rank0+1 @ 792MHz - FAIL
DDR3 chl: Rank0 @ 792MHz
bist_test rank: 0 25 00 4a 3a 1a 5b 23 00 47 42 22 63 1f 00 3f 42 23 62 1d 00 3a 3f 20 5f 618 - PASS
Rank0: 1024MB(auto)-2T-11
AddrBus test pass!
show original
Thx for help! I haven’t change DDR4 settings because I haven’t figured out how DDR4 caused the problem yet. Do you have some ideas? Thx again!
Several days past, I still have no ideas.
I wonder if there 's a guide to port CoreELEC legacy to other S905 devices such as S905L2(p261)
vpeter
30 December 2024 14:45
8
No guide.
Maybe useful:
i am a chinese guy,there are so many s905L2B&3B TVbox users in china ,but there is no dtb for these devices,that is a big problem,i hope you can help us to solve it.
in my opinion，the dtb for it is gxl_p211 or gxl_p261.
i really want your help,please!
I have read the third topic and it said “you rework your decompiled DTB by yourself as it will take hours/days” . I have no idea for this solution, any guide for this? Thx.get_dvfs_info 0007. I have search the linux-amlogic source code and found nothing connected with this.
vpeter
31 December 2024 08:02
10
Use more verbose output by putting this in config.ini.
coreelec="nopkmute nosplash ssh debug loglevel=8"
I have mount the SYSTEM file but I can’t find the config.ini file, where is it?
vpeter
31 December 2024 12:18
13
Should be also there on first fat partition where SYSTEM file is.
I use my armbian to mount the SYSTEM file with :
sudo mount -t squashfs -o loop SYSTEM ~/system
And I tried:
cd ~/system && ls
It display this:
bin etc lib opt run storage system usr
dev flash media proc sbin sys tmp var
Is the partition I mounted right?
BTW, I got the file size with ls -lh and I got this:
-rwxr-xr-x 1 root root 795 Sep 7 2021 aml_autoscript
drwxr-xr-x 2 root root 8.0K Sep 7 2021 device_trees
-rwxr-xr-x 1 root root 12M Sep 7 2021 kernel.img
-rwxr-xr-x 1 root root 48 Sep 7 2021 kernel.img.md5
-rwxr-xr-x 1 root root 158M Sep 7 2021 SYSTEM
-rwxr-xr-x 1 root root 48 Sep 7 2021 SYSTEM.md5
vpeter
31 December 2024 12:35
16
SYSTEM file is squashfs file and there is nothing to do with it.
You should see config file on your created USB stick or SD card on first partition.
There’s no file named config.ini in the first partition, should I create one?
vpeter
31 December 2024 12:39
19
Give me the link of the image you are using.
https://github.com/CoreELEC/CoreELEC/releases/tag/9.2.8
The file name is CoreELEC-Amlogic.arm-9.2.8-Generic.img.gz.BalenaEcther.
vpeter
31 December 2024 12:48
22
I forgot this is very old image with even older kernel.
I think you are on your own.
Oooooops That’s a bad news for me.
So far, I still don’t know why the system is stuck here：
bootconsole [earlycon0] disabled
What that mean? Does it mean I should build a new kernel?
