Posts by ilmich

seems correct to me, but I don't use Windows so I'm not 100% sure. But you should see two partitions with blkid, with output similar to this (it's an experimental box, partition names are not real)

tvchiptryp:~ # blkid
/dev/rknand0p1: LABEL_FATBOOT="SYSTEM" LABEL="SYSTEM" UUID="3003-4337" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="22aeff87-01"
/dev/rknand0p2: LABEL="STORAGE" UUID="7e1f7cb6-2d57-45d8-bc99-ac316c2f31f6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="22aeff87-02"

Have you tried using a rufus alternative!?

try another sd card/reinstall libreelec.

There should be two partitions, the fact that there is only one makes me think that something went wrong with your installation.

let me know

it's very strange.. from these logs I see you have a 4gb sd card (mmc0) and internal memory (mmc2) of 8GB.

please post output of

- blkid

- content of file extlinux/extlinux.conf from first fat32 partition

In practice, when booting, libreelec tries to mount the partitions by recognizing them via an id (which you will see with the blkid output) written in the extlinux.conf file.

So another reason is that there is something wrong with this association.

hi JefersonBP2801,

please:

- start libreelec 10 and from the prompt with the error send a photo of the output of ` dmesg | grep mmc

- if you still have Android send the full version of the build that works for you

- if you can, get a CPU heatsink of at least 20x20mm because otherwise, you will have overheating problems

googling a bit I've discovered that:

- your soc is rk3228A

- your board has an mmc (which is better than nand),

- your board has an unsupported wifi chip (ssv6256p which you can confirm by analyzing your board)edit

edit: the problem you are having is related to the fact that after loading the kernel from the sd card, the kernel itself seems to disable/fault the sd controller.

This can depend on many factors (damaged sd card, particular wifi chip, etc). So having information about your operating system I can see how the hardware is configured.

HI, EmilB

your problem is not that strange. There are other cases of boxes not booting armbian or libreelec.

This depends on the android/bootloader version you have installed. In fact, bootloader from internal memory very often takes precedence, therefore old bootloaders cannot start the system correctly from the SD card.

This is why on the armbian forum it's recommended to clear the device's internal memory or to update the bootloader as you did then. But in fact, apart from some exceptional cases that I don't know about, it is difficult for a box not to boot from sd.

Regarding libreelec 11, it's not stable. Have you tried using Libreelec 10?!

In any case, I would need a log/screenshot of the problem, otherwise, it's impossible to try to help you

jaum20 I tried but it doesn't give me any problems. Can you test by creating the swap manually with something like this

dd if=/dev/zero of=/storage/swap bs=1M count=512
mkswap /storage/swap
swapon /storage/swap

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