[UNOFFICIAL][Le11-10][RK3228/RK3229][box]Libreelec builds

**ilmich** · May 29, 2023 at 11:46 AM

for remotes, in libreelec 10 the driver used is the legacy one because it integrates switching off/on. Which you can't do with the mainline driver (you can manage the suspension, but not with which key/remote control to reactivate everything).

The legacy driver is taken as-is from the 4.4.x kernel and therefore the mapping is not easily modifiable through the official libreelec guide because they reside in the device tree (like android os).

You can modify as you saw the dts with the scancodes you prefer (the module has a debug mode where you can view them).

In libreelec 11 I plan to use a mix of opensource drivers/legacy suspension system, but I don't have much time for new developments these days

I'm sorry

Michele

dmladenov · May 29, 2023 at 1:29 PM

Quote from ilmich

Hi @dmladenov,
for remotes, in libreelec 10 the driver used is the legacy one because it integrates switching off/on. Which you can't do with the mainline driver (you can manage the suspension, but not with which key/remote control to reactivate everything).
The legacy driver is taken as-is from the 4.4.x kernel and therefore the mapping is not easily modifiable through the official libreelec guide because they reside in the device tree (like android os).
You can modify as you saw the dts with the scancodes you prefer (the module has a debug mode where you can view them).
In libreelec 11 I plan to use a mix of opensource drivers/legacy suspension system, but I don't have much time for new developments these days
I'm sorry
Michele

Display More

OMG. Now I need to learn how to compile the whole LibreELEC...

Is there an easy way to compile only my rk3229-box-v884k.dtb ? Do you have a guide ready for this job from scratch ?

Or if i make the changes for my remote (ir_keyXX {}...) in rk322x-box.dtsi can you compile it for me ?

**ilmich** · May 29, 2023 at 1:58 PM

Please explain what happens specifically (which keys don't work or just if you want to remap them).

Compiling a dtb is easy (you can find guides on google). But I can also compile it for you.

I only have 2 or 3 remotes, so if something new comes up that I can include in the build it would help others too.

Keep in mind that regardless of the driver I will use in libreelec 11, the starting configurations will be that of libreelec 10.

Thanks

Michele

dmladenov · May 29, 2023 at 7:42 PM

Quote from ilmich

Please explain what happens specifically (which keys don't work or just if you want to remap them).
Compiling a dtb is easy (you can find guides on google). But I can also compile it for you.
I only have 2 or 3 remotes, so if something new comes up that I can include in the build it would help others too.
Keep in mind that regardless of the driver I will use in libreelec 11, the starting configurations will be that of libreelec 10.
Thanks
Michele

Display More

I am attaching a picture of my remote.

The buttons outlined in red don't work for me and when I pressed them even the LED does not blink.

I just want to be able to use them too.

But I can't deal with the missing button codes.

I don't know how to debug them in your LE 10 with legacy driver.

With LibreELEC 9 (knaerzche) with working ir-keytable it was easier to see scancodes but they are absolutely different. I attached rc_keymap file V88.txt for example.

**ilmich** · May 30, 2023 at 8:55 AM

@dmladenov try the attached device tree (remove txt extension). I haven't mapped all the keys yet, because the work is a bit tedious

However, the scancodes are identical in both cases (mainline driver vs legacy driver). The only difference is how they are stored (in addition to what I have already explained about the device tree).

The rockchip driver uses a particular encoding

- first two bytes are the identification code of the remote control and is stored in little-endian ( in your case cc1d becomes 1dcc )

- the last byte is the key code and is stored inverted. For example, the power key has code 0x00 which becomes 0xff in rockchip encoding.

Given this, in the dts source it turns out that your remote control is this one and that the keys you indicated are actually missing.

Anyway, I hope to return to the mainline driver with libreelec 11.

When I started I didn't have enough experience to create my own patches and I preferred to create a 99% working system (even at the cost of using legacy code)

Let me known

Michele

dmladenov · May 30, 2023 at 6:49 PM

ilmich thanks for the detailed explanations.

Тhis is the result of the buttons not working before:

button HOME = KEY_HOME

button MOUSE = KEY_O

buttons PREVIOUS, NEXT, 1/A/a - they are not touched as you said

buttons RED, GREEN, YELLOW, BLUE - something is wrong here. LED flashes but no reactions in Kodi. I installed an Add-on Keymap Editor and it shows the same longer code 16839168 for all four buttons. For comparison, the HOME button is 61622 - only five digits like all other buttons.

Following your instructions this is what ir_key5 should look like specific to my needs:

(can you make rk3229-box-v884k.dtb)

Code

    ir_key5 {
        rockchip,usercode = <0x1dcc>;
        rockchip,key_table =
            <0xee KEY_ENTER>,
            <0xf0 KEY_BACK>,
            <0xf8 KEY_UP>,
            <0xbb KEY_DOWN>,
            <0xef KEY_LEFT>,
            <0xed KEY_RIGHT>,
            <0xf1 KEY_VOLUMEUP>,
            <0xfd KEY_VOLUMEDOWN>,
            <0xff KEY_POWER>,
            <0xf3 KEY_MUTE>,
            <0xbf KEY_MENU>,
            <0xbe KEY_1>,
            <0xba KEY_2>,
            <0xb2 KEY_3>,
            <0xbd KEY_4>,
            <0xb9 KEY_5>,
            <0xb1 KEY_6>,
            <0xbc KEY_7>,
            <0xb8 KEY_8>,
            <0xb0 KEY_9>,
            <0xb6 KEY_0>,
            <0xb5 KEY_BACKSPACE>,
            <0xfa KEY_RED>,
            <0xfe KEY_GREEN>,
            <0xf6 KEY_EPG>,
            <0xf2 KEY_BLUE>,
            <0xf9 KEY_PREVIOUS>,
            <0xf5 KEY_NEXT>,
            <0xfc KEY_HOME>,
            <0xb3 KEY_INFO>,
            <0xb7 KEY_SUBTITLE>;
    };

Display More

**ilmich** · May 31, 2023 at 1:33 PM

Hi dmladenov,

attached the compiled dtb. If it's all ok I'll include in my next build.

Quote from dmladenov

buttons RED, GREEN, YELLOW, BLUE - something is wrong here. LED flashes but no reactions in Kodi. I installed an Add-on Keymap Editor and it shows the same longer code 16839168 for all four buttons. For comparison, the HOME button is 61622 - only five digits like all other buttons.

mmmm, I checked what I had calculated and it seemed correct. However I don't know the addon you used so I'm not sure how to help you.

dmladenov · May 31, 2023 at 8:13 PM

@ilmich the things are terribly bad

The KEY_XXXX assignment of all problem buttons (RED, GREEN, YELLOW, BLUE, PREVIOUS, NEXT, 1/A/a, MOUSE) are not recognized in Kodi. I'm starting to think they should correspond to keyboard buttons.

May be the last try:

Code

    ir_key5 {
        rockchip,usercode = <0x1dcc>;
        rockchip,key_table =
            <0xee KEY_ENTER>,
            <0xf0 KEY_BACK>,
            <0xf8 KEY_UP>,
            <0xbb KEY_DOWN>,
            <0xef KEY_LEFT>,
            <0xed KEY_RIGHT>,
            <0xf1 KEY_VOLUMEUP>,
            <0xfd KEY_VOLUMEDOWN>,
            <0xff KEY_POWER>,
            <0xf3 KEY_MUTE>,
            <0xbf KEY_C>,
            <0xbe KEY_1>,
            <0xba KEY_2>,
            <0xb2 KEY_3>,
            <0xbd KEY_4>,
            <0xb9 KEY_5>,
            <0xb1 KEY_6>,
            <0xbc KEY_7>,
            <0xb8 KEY_8>,
            <0xb0 KEY_9>,
            <0xb6 KEY_0>,
            <0xb5 KEY_BACKSPACE>,
            <0xfe KEY_M>,
            <0xfa KEY_T>,
            <0xf6 KEY_E>,
            <0xf2 KEY_A>,
            <0xf9 KEY_PAGEDOWN>,
            <0xf5 KEY_PAGEUP>,
            <0xfc KEY_HOME>,
            <0xb3 KEY_I>,
            <0xb7 KEY_O>;
    };

Display More

**ilmich** · May 31, 2023 at 8:27 PM

Technically KEY_XXXX are kernel 'keyboard' events.. so you have to bind remote buttons to something that kodi recognizes (for example the 'o' key if you want information about the playback).

For my remote controls I had to do this (for example with the 'o' key and the 'i' key).

But I thought the mapping you sent was tested with kodi.

No problem though, you're helping me make a better build. The only thing is that I can make you a new version maybe tomorrow, if not in the next few days (it's holidays in my country)

Cheers

Michele

**ilmich** · June 1, 2023 at 6:59 PM

Hi @dmladenov

try this dtb and let me known.

Michele

dmladenov · June 1, 2023 at 7:20 PM

Hi @ilmich

hallelujah

Finally all the buttons are working. That was the goal. Now I can customize and precise the actions of each button in Kodi with a Keymap Editor Add-on as I always could with the other LibreELECs, CoreELECs ...

Thank You very super many hyper mega ultra much @ilmich

jaum20 · June 3, 2023 at 3:10 PM

Hi ilmich

Why threre is no audio passthrough options under Settings > System > Audio? I am using LibreELEC-RK322x.arm-10.0-nightly-20230525-43c4ed8-rk322x

**ilmich** · June 5, 2023 at 10:13 AM

Hi

dmladenov I thank you because my build is better with to your contribution.

jaum20 audio passthrough is disabled because

- spdif output: I have no way to test it.

- hdmi outputs: I imported some patches taken from the allwinner port (which has more or less the same driver for hdmi output) but it doesn't work, so I disabled it, for now, to focus on something else.

jaum20 · June 5, 2023 at 3:40 PM

Quote from ilmich

Hi
dmladenov I thank you because my build is better with to your contribution.
jaum20 audio passthrough is disabled because
- spdif output: I have no way to test it.
- hdmi outputs: I imported some patches taken from the allwinner port (which has more or less the same driver for hdmi output) but it doesn't work, so I disabled it, for now, to focus on something else.

Thank you for the response. I need hdmi passthrough, so I am locked to knaerzche’s biild for now

**ilmich** · June 7, 2023 at 8:41 AM

Hi jaum20

what version are you using!? Android doesn't support passthrough (and so in theory the legacy kernel that libreelec 9 is based on shouldn't either)

**ilmich** · June 7, 2023 at 9:40 AM

jaum20, try this build:

https://ilmich.libreelec.tv/test/LibreELEC-RK322x.arm-10.0-nightly-20230607-43c4ed8-rk322x.img.gz

If I understand correctly, in order for the HDMI passthrough to work, the audio track must have a certain codec (ac3 for example) in order to be sent unprocessed. At the moment I don't have files to test

Thank you

Michele

**ilmich** · June 7, 2023 at 3:26 PM

jaum20 I tried with a DVD (ac3 audio codec) and everything seems to work. The only flaw is that in the passthrough section several hdmi connectors are listed, but only one works (the other doesn't make any sound).

I still haven't figured out how to best configure the audio devices but let's say it's a marginal problem.

If you can do some testing too I would be grateful. In any case, I'll release this little update in a few days.

jaum20 · June 7, 2023 at 3:58 PM

I don't know what kind of sorcery knaerzche did, but I can confirm that the build I am using (LibreELEC-RK322x.arm-9.2-devel-20200427213119-b7186bc-rk3228a-mxq4kpro.img.gz) can do audio passthrough. I will make some tests with this build you provided and give you some feedback.

Thank you for your work

P.S. Everything working fine! I tested the passthrough with this file. You can find demo videos with ac3 audio files here.

Again, thank you very much