Posts by Yasai-san

Elicity

> Is it this one: https://lkml.org/lkml/2025/8/7/872 ?
> Patch: https://lkml.org/lkml/diff/2025/8/7/872/1
Yes!
I did confirm this patch locally, HDMI audio is working on my R6C/S.

And this is known chewitt.

Rockchip: add support for RK3588, RK3576, and RK356X devices by chewitt · Pull Request #10420 · LibreELEC/LibreELEC.tv

This supersedes #7864 which has been waiting for numerous upstream dependencies to reach mythical "minimum viable product" state for LibreELEC use.…

github.com

This is merged latest version(12c4579bd9)

Elicity

> Works fine on the NanoPi-R6C except for audio ( no audio device detected )
NanoPi-R6C/R6S HDMI audio will be added in near future.
Update patch file is exist.

> only 4GB of the 8GB memory is recognized
This is suppressed boot parameter of /extlinux/extlinux.conf in now.
By previous versions readme.md (projects/Rockchip/devices/RK356X/README.md),

* ram is limited to ~4gb with `mem=3838M` (memory range `0x00200000` - `0xefffffff`)
 - there is an issue with importing decoded video frames into display stack
 - old work-in-progress patches broke display stack for older socs

RK3588 and RK3576 are same as RK356X
I don't know this has been updated or not, sorry.

On Radxa ROCK 5C (RK3588S) - Not ROCK 5C Lite (RK3582)

Display is shown with 1027 x 768 size on Full HD display.
Splash logo screen and kodi both are shown this size.

By dmesg, "i2c read error" and "i2c read timed out" are several times logged.

Quote

grep -i i2c /storage/logfiles/rock5c-dmesg.log

[ 0.066093] /i2c@fec90000/audio-codec@11: Fixed dependency cycle(s) with /i2s@fe470000
[ 0.184302] dwhdmiqp-rockchip fde80000.hdmi: registered DesignWare HDMI QP I2C bus driver
[ 0.185054] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.185855] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.186658] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.187448] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.188237] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.189026] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.266051] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.266978] dwhdmiqp-rockchip fde80000.hdmi: i2c read error
[ 0.286834] i2c_dev: i2c /dev entries driver
[ 0.289605] /i2s@fe470000: Fixed dependency cycle(s) with /i2c@fec90000/audio-codec@11
[ 0.289636] /i2c@fec90000/audio-codec@11: Fixed dependency cycle(s) with /i2s@fe470000
[ 0.372812] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 0.476079] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 0.582648] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 0.685980] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 0.789433] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 0.892825] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 0.996105] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.099448] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.202722] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.309330] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.415990] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.519314] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.622666] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.729329] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.836082] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 1.942703] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.046023] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.152662] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.262691] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.365989] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.469350] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.572776] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.676065] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.779393] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.882669] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 2.986100] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 3.089376] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 3.192722] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 3.296060] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.199448] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.302789] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.406110] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.509439] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.612777] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.716098] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.819383] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 7.922773] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.026106] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.129383] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.232773] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.336058] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.439381] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.542771] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.646121] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.749435] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.852715] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 8.956097] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 9.059436] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
[ 9.162774] dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out

Display More

I'm sorry just report only.
I can't find any good information for this.

By mainline linux device tree, Orange Pi 3B has 2 HW revisions V1.1 and V2.1.

I met the ethernet problem on my V2.1 revision device when V1.1 dtb file was used.
But, it was able to use the ethernet when V2.1 dtb file is used.

Please check your HW revision and your dtb file I hope.
HW revision is printed in board.

If you want to boot LE with microSD on Banana Pi M5/M2Pro,
please read the following BPI wiki before do it.

Erase EMMC for SDcard Bootup

If Android is remained in eMMC, LE with microSD is not able to boot.
Like I was

I confirmed the PR#10024-LE13/PR#10025-LE12 on Odroid XU4 night build.
Both have no panic(?) log. It seems to good.

LE13 image : LibreELEC-Exynos.arm-13.0-nightly-20250502-098deba-odroid-xu4.img.gz
This is PR#10024-LE13 boot log.LE13-disable-CONFIG_PROVE_LOCKING-bootlog-XU4.log
This is PR#10024-LE13 all log.LE13-disable-CONFIG_PROVE_LOCKING-log-2025-05-02-11.18.14.zip

LE12 image : LibreELEC-Exynos.arm-12.0-nightly-20250501-8fe8900-odroid-xu4.img.gz
This is PR#10025-LE12 boot log.LE12-disable-CONFIG_PROVE_LOCKING-bootlog-XU4.log
This is PR#10025-LE12 all log.LE12-disable-CONFIG_PROVE_LOCKING-log-2025-05-02-11.06.47.zip

Thanks!
ASAI, Shigeaki

I will confirm your #10024-LE13 / #10025-LE12 on next nightly build.
Many thanks!

chewitt

panic was not shown in boot log when # CONFIG_PROVE_LOCKING is not set on LE12.
It seems to fix.

Coule you please check my test result?
my modification is not-set-CONFIG_PROVE_LOCKING-in-kernelconfig.txt
bootlog is LE12-bootlog-(not-set-CONFIG_PROVE_LOCKING).log
all log is LE12(not-set-CONFIG_PROVE_LOCKING)log-2025-05-01-09.02.46.zip

P.S.
Lakka-v6.x is same, there was no panic.

Resolved

I also confirmed the fix boot fail problem on Odroid XU4 LE12 night build.
- LibreELEC-Exynos.arm-12.0-nightly-20250501-18f208b-odroid-xu4.img.gz

This is boot log.LE12-fixed-bootlog-XU4.log
This is all log.LE12-log-2025-05-01-05.55.20.zip

LE12 boot log has something panic information.
But this is another problem and LE13 has no panic info.
So, I change this post to "resolve".

Thanks a lot!
ASAI, Shigeaki

Thank you very much.

I confirmed the fix boot fail problem on Odroid XU4 LE13 night build.
- LibreELEC-Exynos.arm-13.0-nightly-20250501-2a40145-odroid-xu4.img.gz

This is boot log.LE13-fixed-bootlog-XU4.log
This is all log.log-2025-05-01-03.24.38.zip

I will also confirm on LE12 Odroid XU4 LE13 night build when it is uploaded.
After that, I will change to "resolve" this post.

Thanks!
ASAI, Shigeaki

I tried to build with your patch.
Build will failed probably.
Because u-boot has no arch/arm/dts/exynos5422-odroidxu4.dts

make[3]: *** No rule to make target 'arch/arm/dts/exynos5422-odroidxu4.dtb', needed by 'dtbs'. Stop.
attached build logLE-Samsung-Exynos-arm-build.log, Line 2257

This may good to use "CONFIG_DEFAULT_DEVICE_TREE="exynos5422-odroidxu3"" I think.

Thank you very much your fix
I will confirm the fix on LE nightly build (fix included version).

This is patch for Odroid XU4 boot fail fix.

Exynos: Fix bootfail on Odroid XU4 u-boot · ShigeakiAsai/LibreELEC.tv@c19bd00

github.com

Thanks,
ASAI, Shigeaki

I'm sorry if it's wrong place.

Odroid XU4 can't boot LE12/13.
- LE12: LibreELEC-Exynos.arm-12.0-nightly-20240813-1322868-odroid-xu4.img.gz
LE12-nightly-20240813-bootlog.txt
- LE13: LibreELEC-Exynos.arm-13.0-nightly-20250429-17d2e4e-odroid-xu4.img.gz
LE13-nightly-20250429-bootlog.txt

Both boot are stopped on u-boot DRAM reporting.

This boot fail is also happened on Lakka, and reported as issue #1999. (https://github.com/libretro/Lakka-LibreELEC/issues/1999)

As this report, Lakka is working with odroid-xu3 image + odroid-xu4 dtb on XU4 device.
And, I confirmed LE13 nightly build also working with odroid-xu3 image + odroid-xu4 dtb on XU4 device.

This problem seems to be related with XU4 u-boot defconfig.
(1/3) Add "CONFIG_SYS_MALLOC_LEN=0x5004000" LibreELEC-bootlog(1-Add-CONFIG_SYS_MALLOC_LEN).log
... DRAM size is shown but still freeze.
(2/3) Add "CONFIG_SYS_MEM_TOP_HIDE=0x01600000" LibreELEC-bootlog(2-Add-CONFIG_SYS_MEM_TOP_HIDE).log
... initcall failed is shown and system halted.
(3/3) Add "# CONFIG_EXYNOS_TMU is not set" LibreELEC-bootlog(3-unSet-CONFIG_EXYNOS_TMU).log
... linux is started and splash screen is shown.

These 3 configs are contained in XU3 u-boot defconfig.

Can I create new pull request for this?

Thanks,
ASAI, Shigeaki