Posts by ilmich

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

Hi jaum20,

the startup error is very strange.

I see the kernel tries to set the gpu clock to 600Mhz which my build does not.

Did you use the dts of my build!? or someone you adapted!?

Thanks

Michele

HI,

sorry if I reply late, next time I ask you the courtesy of writing in the dedicated thread ([UNOFFICIAL][RK3228/RK3229]Libreelec builds).

However there is currently no script for installing to internal storage mainly because my builds aren't 100% stable,

So installing to internal storage is for those who know what they are doing.

However there are two ways to install the nand build

- via the armbian multitool bootable via sd card (https://forum.armbian.com/topic/12656-cs…k322x-tv-boxes/)

- using the dd command directly from an sd-booted build of libreelec as explained here (RE: [UNOFFICIAL][RK3228/RK3229]Libreelec builds)

Let me know.

Michele

Hi foxy,

please try to be a little more specific.

This is to avoid the stupid question like.. "are you sure you have a rockchip rk3228"?!

for example, can you tell me if libreelec starts from the sd card!? and the multitool?! Are you just having problems installing it on internal storage?!

Finally, could you send some photos of the board contained in your box?! MXQ PRO 4K can also contain amlogic or allwinner chips.

Thanks

Michele

Hi shMatrix,

thanks, but it's not quite like that.

The tools that currently exist for Windows need a driver because they don't know the rockchip usb protocol.

My tool implements it in user space and therefore technically it doesn't need a driver, but only to access the device via USB.

On Windows there is a generic driver called winusb, but in practice, it must be associated with the rockchip box which connects via USB.

On windows 10 it is done with the procedure that I have indicated. On windows 7 it has to be done manually and maybe I figured out how.

Hi bacalazin,

sorry, but honestly windows is not my operating system so I tried just the basics

I did more tests and saw that the device must be configured as a generic winusb.

I'm trying to figure out if I can create an ad-hoc driver but in the meantime the guide I followed is this

WinUSB (Winusb.sys) installation for developers - Windows drivers

Install WinUSB (Winusb.sys) in the device's kernel-mode stack as the USB device's function driver instead of implementing a driver.

learn.microsoft.com

try and let me known.

Michele

I'm working on this tool because:

- I needed a simple tool for boards that I have without SD card

- have a tool that also works on Windows (for users who are in your situation)

So, given that the software is highly experimental and tested only by me:

- download prebuilt 64bit windows binary: https://github.com/ilmich/rkflash…-5.90Alpha1.zip

- extract it somewhere. The zip contains the executable and a bootloader for RK322x.

- put your box in loader mode (insert a toothpick into the A/V port and connect the OTG cable)

- then execute

rkflashtool.exe b 3 // this put your device in maskrom mode
rkflashtool.exe l rk32\rk322x_loader_v1.10.238_256.bin // this put your device in usbplug mode
rkflashtool.exe d > backup.img // optional, this do a full backup of your nand
rkflashtool.exe f path_to_uncompressed_libreelec_img.img // flash the image
rkflashtool.exe a rk32\rk322x_loader_v1.10.238_256.bin // install bootloader on nand

The box must be in USBplug mode for the tool to work properly, so the first two commands are mandatory.