Unofficial LE for RK356x RK3328\RK3399 RK3588(s)

    Ver 20250303 for rk33xx and rk356x kernel 6.12.17


    Quote from Elicity

    ust read the rk3588 status from collabora,

    I have been testing LE with the main core for a long time (see the link for details https://github.com/LibreELEC/Libr…ment-2631095501 ).

    LE with the main core starts and works, but for now there is a problem, the HDMI frequency synchronization out of the box does not work (perhaps this is a local problem of my monitor), I have not yet delved into the essence of the problem, LE with the 6.1 core on the 3588 is enough for me.

    I can give you a link to test images with the main core for those who want to try, perhaps on their hardware or with additional settings on the command line, KODI will work fully.

    20250303-3588-test
    Посмотреть и скачать с Яндекс Диска
    disk.yandex.ru
    Quote from chewitt

    Most of the codecs aren't upstream yet either.

    the performance of the 3588 is so high that it does not require HW decoders for video playback up to 4K in the banal SW mode :)

    Quote from balbes150

    the performance of the 3588 is so high that it does not require HW decoders for video playback up to 4K in the banal SW mode :)

    RPi5 is the same for common media formats. Codecs are not a barrier to an LE image, but HDMI needs to be reliable. I think Jonas is still working on some HDMI support.

    I have Rock Pi 4 (RK3999)

    Who knows if there will be an improvement in the smoothness of the Kodi interface, which was broken with the release of version LibreELEC 12.0.2?
    In LibreELEC v. 12.0.0, 12.0.1 the Kodi interface worked very smoothly. Then the update 12.0.2 was released where it was broken and v. 13.xx.

    Or can compile an image with some parameter for a smooth interface?

    Quote from chewitt

    but HDMI needs to be reliable.

    I looked at mainline again and I think the earliest would be 6.15, now that would be somewhere in July which also includes audio support. But to be honest I think if 26th of December presents us with an image we are very lucky. I'm sure they are working very hard to get it all in before 6.18 which afaict will become the latest stable.

    All n All, patience is key :saint:

    I'm waiting for Kwiboo to finish with u-boot support. Once that's done we'll ship an image using whatever codecs are upstream and everything else using software decode, and then periodic kernel bumps will bring more codecs and features over time. I will go nag Jonas again..

    Quote from chewitt

    I'm waiting for Kwiboo to finish with u-boot support.

    This has been implemented and is working for a long time.

    Rockchip: add initial support for RK356x and RK3588 by Kwiboo · Pull Request #7864 · LibreELEC/LibreELEC.tv
    This PR introduces initial support for Rockchip RK356x devices. U-Boot 2023.07, scheduled for 03 July 2023, will be the first version with decent support for…
    github.com


    Run LE from u-boot 2024.10

    DR V1.09 a930779e06 typ 22/11/21-17:50:56
    LPDDR4X, 2112MHz
    channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
    channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
    channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
    channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
    Manufacturer ID:0x6
    CH0 RX Vref:30.7%, TX Vref:21.8%,21.8%
    CH1 RX Vref:32.7%, TX Vref:23.8%,22.8%
    CH2 RX Vref:31.7%, TX Vref:21.8%,21.8%
    CH3 RX Vref:33.7%, TX Vref:22.8%,22.8%
    change to F1: 528MHz
    change to F2: 1068MHz
    change to F3: 1560MHz
    change to F0: 2112MHz
    out
    U-Boot SPL board init
    U-Boot SPL 2017.09-armbian (Jun 20 2023 - 14:17:33)
    Trying to boot from MMC2
    Trying fit image at 0x4000 sector
    ## Verified-boot: 0
    ## Checking atf-1 0x00040000 ... sha256(6a4a192c10...) + OK
    ## Checking u-boot 0x00a00000 ... sha256(f5da679ec9...) + OK
    ## Checking fdt-1 0x00ac66e0 ... sha256(a52cd719a6...) + OK
    ## Checking atf-2 0x000f0000 ... sha256(569ee96047...) + OK
    ## Checking atf-3 0xff100000 ... sha256(70505bb764...) + OK
    Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
    Total: 716.223 ms

    INFO: Preloader serial: 2
    NOTICE: BL31: v2.3():v2.3-831-g92b1674a5:derrick.huang, fwver: v1.47
    NOTICE: BL31: Built : 16:18:39, Sep 4 2024
    INFO: spec: 0x1
    INFO: code: 0x88
    INFO: ext 32k is not valid
    INFO: ddr: stride-en 4CH
    INFO: GICv3 without legacy support detected.
    INFO: ARM GICv3 driver initialized in EL3
    INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
    INFO: l3 cache partition cfg-0
    INFO: system boots from cpu-hwid-0
    INFO: disable memory repair
    INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
    ERROR: dfs get fsp_params[0] error, 0xfead0001 != 0xfead0004
    ERROR: dfs get fsp_params[1] error, 0xa54 != 0xfead0004
    ERROR: dfs get fsp_params[2] error, 0xbc != 0xfead0004
    ERROR: dfs get fsp_params[3] error, 0x3f0033 != 0xfead0004
    ERROR: loader&trust unmatch!!! Please update loader if need enable dmc
    ERROR: current trust bl31 need match with loader ddr bin V1.13 or newer
    ERROR: current loader need match with trust bl31 V1.07-V1.37
    INFO: BL31: Initialising Exception Handling Framework
    INFO: BL31: Initializing runtime services
    WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
    ERROR: Error initializing runtime service opteed_fast
    INFO: BL31: Preparing for EL3 exit to normal world
    INFO: Entry point address = 0xa00000
    INFO: SPSR = 0x3c9


    U-Boot 2024.10 (Mar 31 2025 - 15:13:49 +0300)

    Model: Radxa ROCK 5B
    DRAM: 16 GiB
    Core: 351 devices, 32 uclasses, devicetree: separate
    MMC: mmc@fe2c0000: 1, mmc@fe2d0000: 2, mmc@fe2e0000: 0
    Loading Environment from nowhere... OK
    In: serial@feb50000
    Out: serial@feb50000
    Err: serial@feb50000
    Model: Radxa ROCK 5B
    Net: No ethernet found.
    Hit any key to stop autoboot: 0
    Scanning for bootflows in all bootdevs
    Seq Method State Uclass Part Name Filename
    --- ----------- ------ -------- ---- ------------------------ ----------------
    Scanning bootdev '[email protected]':
    0 extlinux ready mmc 1 [email protected] /extlinux/extlinux.conf
    ** Booting bootflow '[email protected]_1' with extlinux
    1: LibreELEC
    Retrieving file: /KERNEL
    append: boot=UUID=3103-0153 disk=UUID=223bb7bf-2783-4489-a3ed-7c12b0e35c07 quiet console=ttyS2,1500000 console=tty0 systemd.debug_shell=ttyS2 coherent_pool=2M cec.debounce_ms=5000
    Retrieving file: /rockchip/rk3588-rock-5b.dtb
    ## Flattened Device Tree blob at 12000000
    Booting using the fdt blob at 0x12000000
    Working FDT set to 12000000
    Loading Device Tree to 00000000edbb0000, end 00000000edbdd41f ... OK
    Working FDT set to edbb0000

    Starting kernel ...


    and u-boot 2025.01


    U-Boot 2025.01 (Apr 01 2025 - 11:05:20 +0300)

    Model: Radxa ROCK 5B
    DRAM: 16 GiB
    fusb302 usb-typec@22: TCPM: PD transmit data failed: -110
    Core: 355 devices, 34 uclasses, devicetree: separate
    MMC: mmc@fe2c0000: 1, mmc@fe2d0000: 2, mmc@fe2e0000: 0
    Loading Environment from nowhere... OK
    In: serial@feb50000
    Out: serial@feb50000
    Err: serial@feb50000
    Model: Radxa ROCK 5B
    Net: No ethernet found.
    Hit any key to stop autoboot: 0
    Scanning for bootflows in all bootdevs
    Seq Method State Uclass Part Name Filename
    --- ----------- ------ -------- ---- ------------------------ ----------------
    Scanning bootdev '[email protected]':
    0 extlinux ready mmc 1 [email protected] /extlinux/extlinux.conf
    ** Booting bootflow '[email protected]_1' with extlinux
    1: LibreELEC
    Retrieving file: /KERNEL
    append: boot=UUID=0104-0615 disk=UUID=03dee71e-b8ea-4889-9600-3b3ab7ac68e6 quiet console=ttyS2,1500000 console=tty0 systemd.debug_shell=ttyS2 coherent_pool=2M cec.debounce_ms=5000
    Retrieving file: /rockchip/rk3588-rock-5b.dtb
    ## Flattened Device Tree blob at 12000000
    Booting using the fdt blob at 0x12000000
    Working FDT set to 12000000
    Loading Device Tree to 00000000ecbb5000, end 00000000ecbe241f ... OK
    Working FDT set to ecbb5000

    Starting kernel ...

    But the last post in that thread states:

    'These are the minimal changes with which KODI launches on rock5b. But there is a bug, a distortion of the image, perhaps it is due to incorrect parameters in the core, HDMI synchronization is disrupted (perhaps the reason is different, this is just my guess).'

    So does this not indicate that there are still issues with it creating distortion of the image, requiring a little more work?