Posts by ilmich

Hi Habitual6824

thank you very much for the support you are giving me to make my port better.

Technically when using hardware decoding the cpu/gpu shouldn't be fully loaded so the temperature rise may be due to the ram clock.

I can certainly try to improve something, but keep in mind that to lower the price and save on components, the heat dissipation in these boxes is often non-existent. In some boxes there is not even a passive heat sink, and in others, it's too small.

For the 4k speech, maybe it's better if we try the same thing. So I ask you to try any of these videos

Samples - Official Kodi Wiki

both locally and via the network and share results. In this way, if you show me the problematic ones, I try to reproduce them in my box to understand what can be done ((if anything can be done).

I don't have a 4k TV so I usually see full HD content at most.

However, I will prepare a dtb similar to the legacy (which will become the default for the other boxes too)

Thanks again

Michele

edit: on mainline kernels, hardware decoding is implemented differently than on official rockchip kernels.

It's already a miracle that there is very good rockchip support for hardware decoding, and that's thanks to the immense effort of volunteers. This is to say that not everything that is supported by the legacy rockchip kernel, currently works on my port as well.

Hi, Habitual6824

thank you so much.

Last test (your dts is almost complete)

- CPU at 1.3Ghz

- GPU at 500MHZ

- DDR3 with max clock rate 800MHZ

let me know.

Hi Habitual6824,

thanks for your patience and your help

Hoping it hasn't crashed again, I ask you please to try the following dts

- rk3229-box-mxq4kpro.dtb.cpu --> I've reenabled 1.4 Ghz CPU clock (with dmc disabled and GPU max 400Mhz)

- rk3229-box-mxq4kpro.dtb.dmc --> I've reenabled dmc (ddr3 frequency scaling) (with CPU at 1.3Ghz and GPU max 400Mhz)

- rk3229-box-mxq4kpro.dtb.gpu --> I've reenabled 500Mhz GPU clock (with CPU at 1.3Ghz and dmc disabled)

so I can try to figure out where the problem lies. Obviously, the important thing is to avoid crashes, but if I can get the most out of our rockchip it's better.

regarding hardware video decoding, I noticed that you use kodi debug. Try turning it off. If I remember correctly the overlay showing cpu stats forces kodi not to use the best video decoding method (drmprime)

for booting from sd I don't know what to say. Probably the bootloader I use has some incompatibility with your board. I would need lower level logging via the UART serial port. Anyway, I'll try to take a look at it.

Hi Habitual6824,

the problem of booting from the sd card is strange because in your dmesg I see that it is correctly loaded.

[    0.795338] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    0.795454] mmc0: new high speed SDHC card at address 0007
[    0.796741] mmcblk0: mmc0:0007 SL16G 14.5 GiB
[    0.799982]  mmcblk0: p1

But if you have patience we will try to fix everything

But nothing starts!? Or is there an error you can send me!?

Quote

If there's no error in logs, does it mean that it crashes before it could log what causes the error?

yes

To avoid conflicts I ask you to delete the internal memory (via multitool) and try again with the sd card.

Also try with this dtb (like before), I reduced the clock frequency of cpu and gpu.

I also ask you to tell me which version of legacy libreelec works for you so that I can create an ad-hoc dts for your box.

Thank you

Hi Habitual6824,

try with this dtb (remove txt extension).

If you can boot from sd card replace this file into the first partition of the card.

You can also switch from a running system with

mount -o remount,rw /flash
cp {where_you_store_the_file} /flash
mount -o remount,ro /flash

the reboot.

Regarding high cpu usage, I've

- increased kernel tick

- changed cpu governor to ondemand

this is necessary for a better UI experience.

Hi, I try to briefly explain the problems you are looking at.

Unfortunately, although I receive boxes from time to time, I don't have all the variants

Anyway if

- the box does not start or you see errors --> cpu voltages

- the box freezes after a while (you notice this because the led that usually flashes when you use the remote control, stays still) --> gpu voltages.

- kodi restarts --> generic bug that may depend on corrupted file, unstable network, etc etc. However bugs that do not directly depend on the build (almost 80% of the times).

To solve the overheating problems, over time I have experimented with different voltages from the official ones and I thought I had found working ones more or less everywhere.

Instead, some time ago I received a box that crashed on boot and therefore with the January release I fixed a little bit.

Unfortunately in February I did another experiment and now you have problems.

My suggestion is to stick with the January release and better specify what happens to you (if it falls into one of the cases that I have indicated to you).

I also ask you to send me the output of this command (from an ssh shell inside the box)

hexdump /sys/devices/platform/11040000.efuse/rockchip-efuse0/nvmem

this is the internal rk3229 efuse, and inside there is the information to check if your box tolerate some voltages or not.

Cheers

Michele

thanks for logs.

try to switch dtb (according to 1stpost) in order to match your hardware.

default dtb is generic and without (for example) ddr3 frequency scaling

4k contents are unplayable with that dtb (and in general with boxes without ddr3)

make sure that also your network are reliable.

I don't see hardware errors in your logs

Hi Habitual6824,

try with my January build( archive folder ).

In the eternal search of optimal voltages settings, in my last build I've changed something.

Quote from dan25

Hi ilmich ,

Would you be interested in supporting the Grandstream GVC3212 perchance? Here is its vendor page, firmware, FCC documentation, and it appears to have an RK3228H chip onboard.

Hi dan25

all Rockchip devices work pretty much the same, so it wouldn't be impossible to do.

And it would be nice to do so, unfortunately without the device available it's difficult to test everything.

I found a tool

Grandstream-Firmware-HT802/FirmwarePatcher at master · BigNerd95/Grandstream-Firmware-HT802

Grandstream HT802 Reversing - Custom Firmware - Decrypt - Unpack - Grandstream-Firmware-HT802/FirmwarePatcher at master · BigNerd95/Grandstream-Firmware-HT802

github.com

that explodes the firmware you linked, but it needs a decryption key.

However the rk3228h should be the 64bit version of the rk3228.

Cheers

Michele

Hi all,

new build available with:

- linux 5.10.167

- mesa 23.0.0-rc4

- updated libreelec to the latest upstream changes

I started working on libreelec-11, but you have to be patient, private life is slowing me down.

Cheers

Michele

Hi all,

new build available with:

- linux 5.10.162

- mesa 22.3.2

- kodi 19.5

- updated libreelec to the latest upstream changes

This may be the latest build of Libreelec 10.0

Kodi Nexus is around the corner, and I will start working on Libreelec 11.

Cheers

Michele

Hi punter,

thanks for the logs

Feb 02 15:29:48.501460 LibreELEC kernel: mmcblk2: mmc2:0001 M8G2FA 7.45 GiB 
Feb 02 15:29:48.501580 LibreELEC kernel: mmcblk2boot0: mmc2:0001 M8G2FA partition 1 512 KiB
Feb 02 15:29:48.501699 LibreELEC kernel: mmcblk2boot1: mmc2:0001 M8G2FA partition 2 512 KiB
Feb 02 15:29:48.501831 LibreELEC kernel: mmcblk2rpmb: mmc2:0001 M8G2FA partition 3 128 KiB, chardev (243:0)

the internal emmc was successfully detected.

So which tool doesn't work, the multitool?!

Anyway, you can try to install the build directly from sd card. Copy the desired Libreelec build somewhere in the storage partition of sdcard and do something like this

dd if={path_to_image} of=/dev/mmcblk2

and if you want to make a backup first (which I suggest)

dd if=/dev/mmcblk2 of=sample_backup.img

There is a script to automate everything in my to-do list, but installing Libreelec in internal memory is a procedure for those who know what to do. So I preferred to wait for the builds to become more stable.

Try and let me known.

Michele

hi punter,

please, reboot the board because the kernel log is rotated and the first messages are lost.

thank you

hi punter, Lajos

please, could you share a full dmesg log?! The best way to do that is described here (https://wiki.libreelec.tv/support/log-files)

thanks a lot.

Michele

Hello anjarys

I'm glad you like it. What kind of box do you have!?!

Anyway, I haven't written a tutorial (yet), but the best tool is the multitool made by jock2 for armbian.

You can find it here https://forum.armbian.com/topic/12656-cs…k322x-tv-boxes/.

Basically, it's a small operating system that allows you to backup/restore internal memory and flash images. It works perfectly and you can find the details in the excellent guide by jock2. (clearly the guide is for armbian, but it also applies to libreelec images)

Let me know if you have any problems.

Cheers

Michele

other news.

I'm working on a fork of rkflashtool improving it as much as possible:

GitHub - ilmich/rkflashtool: Tools for flashing Rockchip devices

Tools for flashing Rockchip devices. Contribute to ilmich/rkflashtool development by creating an account on GitHub.

github.com

The goal is to create a tool (also graphical and for windows) to facilitate flash operations on internal memory (especially nand). The multitool is the best tool, but for those with nand devices, not the most optimal(yet).

Hi all,

new build available with:

- linux 5.10.158

- mesa 22.3.0

- upgraded and fixed legacy bootloader

- updated libreelec to the latest upstream changes

There's good news. Thanks to the libreelec community, I have official space for my builds. The new link can be found in the first post.

I'm starting to remove some old builds (gdrive for sure).

Cheers

Michele