Posts by ilmich

jaum20 I've never tried it but theoretically you shouldn't have any problems if you use the storage partition.

Do you have some logs to show me and maybe the procedure you followed!?

EmilB please try to be more specific. Won't boot from sd card!? What kind of problem?! (black screen but leds on, no leds on, screen errors).Do you have an android operating system installed on internal memory!? If so what version?!

All my libreelec builds share the same bootloader so if it won't boot your problem is elsewhere.

Thank you

Michele

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, 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

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)

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.

Hi @dmladenov

try this dtb and let me known.

Michele

Hi camelator,

to add a new board (not a new soc/architecture) after downloading the source of libreelec edit this file by adding the right information

LibreELEC.tv/uboot_helper at d195c401878bb921aa60cec87945bc7f59df1725 · LibreELEC/LibreELEC.tv

Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.

github.com

and then launch the build specifying the new board (and if all works make an official pull request )

Of course, the dts must exist in the kernel (upstream or patched).

edit: this is the basic step, clearly things get complicated based on how a board is more or less similar to others already present

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

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 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

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

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

Hi jaum20

this is normal because libreelec 10 has an older version of fuse.

I can add it to my build, but can you please try this first (symlink to old fusermount)?

Cheers

Michele

Hi all,

new build of libreelec-10 available with:

- linux 5.10.180

- mesa 23.0.3

- fix boot from sdcard in some circustance (thanks jaum20 for reporting and testing and jock2 for solution)

Cheers

Michele

@bemenaker, my builds are for rockchip rk3228/rk3229, not for rk3328 I'm sorry.

@pigwoz, you need to switch dtb as explained in the 2nd post ( "Initial Setup" section) using the one with suffix -ovclk.

Michele

Hi jaum20,

try this build. It's a preview of the next update that I decided to do to include the fix for your problem.

Index of /test/

Keep in mind one thing though. Your problem is related to a boot component of your armbian installed in nand.

I won't go into too much detail but basically you have an opensource trustos (optee) that is loaded on boot (If you look at the log you sent me, the errors related to 'sip v2' are related to the fact that the opensource trustos is probably not compatible).

Libreelec instead uses the proprietary one because it gives you the possibility of having ddr3 scaling and startup via remote control.

Therefore, if you should have problems in this sense, the only solution is, in your case, to update the trustos you have in the nand. But this might give you problems with armbian.

If I remember correctly, armbian also switched to using the same trustos as libreelec at some point (maybe jock2 can help us with that).

So maybe the solution is even simpler and consists of some update that you can easily apply.

Quote from jaum20

Should I switch the dtb after install as showed on the post #2?

yes, mainly this is needed in order to configure leds and some other features.

Thanks a lot and let me know

Michele

jaum20,

thank you so much for your precious support. Try doing the same thing they suggested in the past with this dtb that I am attaching (remove .txt extension).

I have a question, how did you install armbian?! Via usb cable, or multitool, or what?!

jaum20 wich armbian?! legacy?! stable?!

I've a spare box, so I can try to reproduce the issue.

thanks

Michele