Posts by ilmich

Quote from fsdonato

My new log, build 2023/11/19

[   15.710420] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43342-sdio for chip BCM43342/1
[   15.710896] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43342-sdio.rockchip,rk322x-box.bin failed with error -2
[   15.711133] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43342-sdio.bin failed with error -2

missing firmware, in the next build your wifi should work

Can you please tell me if, also checking with Android, your board also has Bluetooth? What is the name of your box (not board)? Do the LEDs work well? Do you try to see by switching to other device trees if your box already has a good configuration?

I want to make a specific device tree, but I need this information.

Quote from anjarys

Hi, attached remote config for greenet.txt

Thank you so much.

Quote from anjarys

And it would be nice if you add wifi driver for SV6256P on your next build, too?

No working driver for now. I'll suggest to use ethernet, or external usb wifi dongle.

Hi fsdonato, please share a new log. The WiFi chip is supported by the kernel with a little patch, so maybe the fix is easy.

anjarys if you have a working remote mapping, please share the results. I'll add your remore config on my next build

Quote from FurmanSK

Anything major relating to h265/HEVC or 4k?

Only the switch from U-Boot legacy --> U-Boot mainline.

Quote from chewitt

LibreComputer are upstream champions so I would expect their boards to work correctly.

board works correctly but ddr3 clock is set to 330mhz(https://github.com/u-boot/u-boot/…r4-666.dtsi#L26) that is too low for 4k contents. A ddr3 clock scaler exists, but without someone that upstream a driver, ddr3 clock is fixed and initialized at boot.

sorry FurmanSK, busy at work.

Keep in mind that libreelec use U-Boot mainline (not the legacy one with proprietary blobs that maybe librecompurer folks suggests).

So the low DDR clock is defined in the device tree for roc-cc of U-Boot mainline source code.

You can try libreelec 10 where U-Boot legacy and binary blobs are used in place of the mainline and see if there are some differences.

Hi all,

a new build of libreelec 11 available with:

- mesa 23.3.0-rc4 and dav1d 1.3.0

- added esp8089 and bcm43342 wireless driver (not tested because I don't have such chip)

- tune ssv6051p wireless driver

- fix Bluetooth driver on t95d box

- ddrbin v1.11

- tune CPU and DDR3 scaling governor

- various fixes and improvements

The build is very stable but some features are missing (like NAND).

My build of Libreelec 11 has some breaking changes that make it incompatible with previous Libreelec 10 builds. In other words, there is no easy way to upgrade your Libreelec 10 setup to Libreelec 11.

Cheers

Michele

fsdonato  markosc with this build I've made some experiments regarding wifi (missing driver and speed problem with ssv6051p). Please try and let me known

Hi fsdonato,

I'll do my best to support various hardware, but regarding kodi addons, I'll not guarantee because it's out of my scope.

Quote from fsdonato

Error "simple iptv one or more items failed"

Sadly I've not found the error in your logs.

However, I discovered that perhaps there is hope for your WiFi. I'm compiling a patch created by jock2 that should help. I will let you know

markosc is the wifi 6051p? because it could also depend on the CPU/DDR clocks which in this version of libreelec are lower (heat and optimizations that make overclocking less useful). I've made some improvements that I hope to release soon and that you might try. this is because libreelec 10 and libreelec 11 practically share the same kernel code (obviously adapted to the latest kernel versions)

Hi fsdonato,

unfortunately, the r29s are very particular as boards. jock2 fixed them up recently because he had one available. If you can't do without wifi, I recommend getting a USB adapter because if I remember correctly, there are no usable drivers for that chip.

But I'll try to do something.

Cheers

Michele

Hi MIKMXIII,

Quote from MIKMXIII

but I only noticed a lowering of the volume power with my soud bar compared to libreelec 10.

connected with analogic port?

Quote from MIKMXIII

then its remote control also works but the bluthoot key doesn't work.

sorry, but I don't understand. Are you talking about the remote control of the box or the sound bar? Which bluetooth button?

Hi FurmanSK,

I've builted a version of bootloader with 534Mhz ddr4.

So first make a backup of your installation and after

- download this bootloader https://ilmich.libreelec.tv/rk3328/u-boot-rockchip.bin

- flash it in your bootmedia (from a linux machine or directly in a ssh session of your libreelec installation)

dd if=u-boot-rockchip.bin of=${BOOT_DISK} bs=32k seek=1

where ${BOOT_DISK} is your boot device (for example /dev/mmcblk0)

If works you should see an higher pll_dpll in clk_summary.

Let me known.

Michele

I need to recheck with my boards, but

    pll_dpll                          1        1        0   664000000          0     0  50000         Y
       dpll                           1        1        0   664000000          0     0  50000         Y
          clk_ddr                     2        2        0   664000000  

this should be the clock of ddr. Internally clock is divided by 2 so your ram frequency is 332Mhz.

I imagine that the GUI is also not very fluid, especially at high resolutions.

Without the drivers I mentioned, one way to overclock the RAM is via bootloader. In practice, when the bootloader initializes the RAM it tries to use a higher clock. This can create problems because high clocks need a higher voltage (which the DMC manages automatically).

I'll try to study this official build and see if I can do something, but I can't guarantee because I have no way to try.

Hi FurmanSK,

share the output of

cat /sys/kernel/debug/clk/clk_summary

if this sysfs entry exists, it will show info about every hardware clock on your board.

Overclock is a bit harder because it depends on what the official builds for rk3328 contain.

In the soc rk3228 (and I believe in others too) there is a ddr controller called dmc (dynamic memory controller) which can manage the frequency of the ddr chips at runtime (scaling it up and down).

To work it needs legacy blobs and driver which I imagine (but I don't know) are excluded from the official builds.

On rk3228 works because my build is unofficial and I've assembled such legacy pieces.

I'm not an expert of others rockchip socs, but with rk3228 (not the same of the one discussed in this thread) the only boards that can handle 4k contents are the ones with ddr3 and clock rate >= 600mhz.

maybe can be useful to check also type and clock of DDR RAM.

Hi all,

a new build of libreelec 11 available with:

- mesa 23.2.1

- support for OneTv Lite box (thanks to usr4864 and jock2)

- support for more boxes (from libre10)

- various fixes and improvements

The build is very stable but some features are missing (like NAND).

My build of Libreelec 11 has some breaking changes that make it incompatible with previous Libreelec 10 builds. In other words, there is no easy way to upgrade your Libreelec 10 setup to Libreelec 11.

Cheers

Michele

great! Thanks for sharing your remote mapping.

can you please try shutdown and power on with power key?

I'll try to see if I can do something regarding wifi

because in your case there are two rc devices rc0 (typically cec) and rc1 (the RF remote receiver). if you launch ir-keytable without params you can show the list of all available rc devices.

you need to specify rc1 device when launching ir-keytable. The cec protocol is cec protocol and you can't change that.

so try with

ir-keytable -p nec -t -s rc1

let me know.

Michele

EDIT: However, since it's a new remote if you send me a working mapping that I can add to the official build I would be grateful.

used rc1 as rc device? can you please share the command line you used? I'll try on my box.

However, unless your receiver is connected differently at gpio level it seems strange to me. I'll also check the dts of your firmware later.

Which remote protocol are you using with ir-keytable? (NEC, NECX etc etc)

EDIT: according to your dmesg the ir receiver (rc1 for ir-keytable) driver is up and running

[   25.467831] rc rc1: rockchip_ir_recv as /devices/platform/110b0030.ir-receiver/rc/rc1
[   25.468373] input: rockchip_ir_recv as /devices/platform/110b0030.ir-receiver/rc/rc1/input2
[   25.485955] rockchip_ir 110b0030.ir-receiver: rockchip SIP initialized, version 0x2