Command result: dmesg | paste http://ix.io/4lvF
h264 file still not playing.
I still have dmesg from android:
dmesg (158.0 KB)
Still failed to allocate memory for node 'linux,codec_mm_cma'
It is in android:
0.000000] <6>[ 0.000000@0] Booting Linux on physical CPU 0x0000000000 [0x411fd040]
[ 0.000000] <5>[ 0.000000@0] Linux version 5.4.86 (xjj@junuo) (Android (6443078 based on r383902) clang version 11.0.1 (https://android.googlesource.com/
[ 0.000000] <6>[ 0.000000@0] earlycon: aml-uart0 at MMIO 0x00000000fe07a000 (options '')
[ 0.000000] <6>[ 0.000000@0] printk: bootconsole [aml-uart0] enabled
[ 0.000000] <0>[ 0.000000@0] 05c00000 - 05d00000, 1024 KB, ramoops@0x07400000
[ 0.000000] <0>[ 0.000000@0] 05000000 - 05c00000, 12288 KB, linux,secmon
[ 0.000000] <0>[ 0.000000@0] 3f800000 - 40000000, 8192 KB, linux,meson-fb
[ 0.000000] <0>[ 0.000000@0] 7dc00000 - 80000000, 36864 KB, linux,ion-dev
[ 0.000000] <3>[ 0.000000@0] invalid size property in 'linux,ppmgr' node.
[ 0.000000] <0>[ 0.000000@0] 70c00000 - 7dc00000, 212992 KB, linux,codec_mm_cma
[ 0.000000] <0>[ 0.000000@0] 6f800000 - 70c00000, 20480 KB, linux,vdin1_cma
[ 0.000000] <7>[ 0.000000@0] cma: dma_contiguous_reserve(limit 80000000)
[ 0.000000] <7>[ 0.000000@0] cma: dma_contiguous_reserve: reserving 8 MiB for global area
[ 0.000000] <6>[ 0.000000@0] cma: Reserved 8 MiB at 0x000000006f000000
[ 0.000000] <7>[ 0.000000@0] On node 0 totalpages: 524288
@Secam7 please test this dtb:
If not please when possible enable tomorrow tmate so I can test multiple settings until I find the correct alignment.
This file reboots the box, although the memory is allocated correctly.
I made such changes and the video files play.
--- s4_s905w2_2g.dts.org 2023-01-17 16:43:19.410212453 +0100
+++ s4_s905w2_2g.dts 2023-01-17 19:57:15.571128222 +0100
@@ -2872,6 +2872,7 @@
spi1 = "/soc/apb4@fe000000/spi@50000";
tsensor0 = "/p_tsensor@fe020000";
};
+
memory@00000000 {
device_type = "memory";
linux,usable-memory = <0x00000000 0x00000000 0x00000000 0x80000000>;
@@ -2886,7 +2887,7 @@
record-size = <0x00020000>;
console-size = <0x00040000>;
ftrace-size = <0x00080000>;
- pmsg-size = <0x00010000>;
+ pmsg-size = <0x00020000>;
bconsole-size = <0x00010000>;
};
linux,secmon {
@@ -2932,7 +2933,7 @@
linux,codec_mm_cma {
compatible = "shared-dma-pool";
reusable;
- size = <0x00000000 0x2fc00000>;
+ size = <0x00000000 0xd000000>;
alignment = <0x00000000 0x00400000>;
linux,contiguous-region;
phandle = <0x00000060>;
@@ -2951,6 +2952,7 @@
phandle = <0x00000044>;
};
};
+
codec_mm {
compatible = "amlogic, codec, mm";
memory-region = <0x00000060 0x00000061>;
This line is suspect, high value : 0x2fc00000
Ok, here a new dtb only changed the codec_mm_cma size:
s4_s905w2_2g.dtb (63.9 KB)
@Secam7 when it does work please make me a dmesg again, thx.
With this dtb file, playback works, and here’s the dmesg: http://ix.io/4lzn
Edit
I have a question, this box has bluetooth 5.0.
Is there a chance to run it under CE-ne?
Hello,
I am new here. I try to boot CE on a box which has S905W2 and 2Gb of RAM.
I tried to use dtb from your CE nightly (s905w_2g) which didnt boot well, no framebuffer, hanged on hdmi timeout for vsync. Kodi doesnt start.
DTB extracted from device (Android One), boots a little futher but also /dev/fb0 and fb1 is not working, TEE for GPU is not being loaded with error 0x8 and also no HDMI output.
I try to boot this device to make it work with CE, i have plenty of knowledge about Buildroot, Linux Kernel, UART, Uboot and DTBs but i lack any documentation about those new devices. I had no problems creating own linux based images for old S905 but know this is nightmare.
Where should i start? Those info i have are too technical deep to post it here to typical user. I tried to disassemble in IDA some precompiled binaries but even recompiled kplayer from old platform makes kernel panic.
Did you try this one?
https://wiki.coreelec.org/coreelec:ce_support
Also the android DTB dump please
I have been testing NE on VIM4 mainly and GT King 2.
CEC has performed flaky, but I remember it working well around the 15/11/22 update.
Recently my device appears to suspend, the light goes off but immediately turns back on and my TV also turns back on. This is a pain.
On further testing the issue is not limited to CEC but even when I suspend device from menu. Turning of CEC does not help the issue.
Is there a way to check what causes it to turn back on.
There is a bug in the Android firmware, try again with BL30 injected.
1 Like
VIM4 already include BL30 when you installed CE image.
How could I replace it with the one I have in the emmc (does not start kodi)?
Was installing all of the skins, one at a time, and when I got to the “Apple” skin, CoreELEC crashed and then booted into Safe Mode.
It created a folder called “Kodi_Failed” folder of 2.90GB size.
I am attaching the Kodi-Failed log.
log-2023-01-18-21.49.44-FAILED.zip (320.8 KB)
I do have a backup from Dec. 25, 2022
I am guessing the “Kodi-Failed” folder, since it is almost 3GB, is the current data. How do I use that data to get the box back to where it was.
I is using my HK1Rbox X4 with the NE version from today, Jan. 18, 2023
Thanks.
BTW, I was testing all of the available skins, to see how the PVR guide looks on each skin.
As I recall, I was doing the same thing when the same thing happened last time and my box went back to first boot up.
Remove the offending addon/s and restore your data to your device
I restored the backup, did not take long. Now I’m back to watching Netflix.
Thought maybe with the logs, The devs, might find the cause of the box crashing.
Tomorrow, I will continue testing all the different skins and how they perform on this device.
Thanks for that info. I had disabled my CEC in peripherals for my GT King II. Appears to be working now.
1 Like
Flash Android to eMMC and make fresh install on external boot media.
There is currently a bug in kernel about ion dma buffer allocate. We are try to fix this shortly.