Posts by ilmich

Hi all,

new build available with:

- linux 5.10.111

- mesa 21.0.1

oneillb this build was tested for some days without particular freezes/issues. Try it and let me know.

sorry oneillb,

looking at the name of the image you are using they are not mine.

Try these (clearly the speech made in the previous post is valid)

libreelec-rk322x – Google Drive

What builds did you use ?! Mine or knaerzche's ?!

However the alfawise a8 does not have nand support, so you should try other images.

Unfortunately, unlike the images for Libreelec 10, these are custom for each device. So if NAND support is not enabled for that device, both the bootloader and the device tree do not use it.

You can try with the v88mars which is very similar.

Please note that my builds are a bit more up to date, but in fact consider them not maintained anymore.

Cheers

Michele

oneillb,

this is partially a good news.

Because the system is stable as hardware, but unfortunately there are some software bugs(kernel in this case). Looking at the dmesg it looks like a null reference while trying to do filesystem operations.

I'm preparing a new build with the latest 5.10.x kernel, hopefully it will fix.

hi oneillb,

i'm away from home for a little vacation.

but, wich kind of issue?! freeze or crash?!

Freeze are often voltage/power.. but crash maybe is another thing.

Can you share some logs?? Are you using some addons?! Crash is with some particular file formats?! For example I've noticed some crash with xvid files (maybe lack of MPEG4 hardware decoding)

regarding dtb.. alfawise is similar to v88mars.. try and let me know.

thanks a lot for testing

Quote from oneillb

I do get a warning that the driver cannot write to the idbloader area of the NAND, so maybe the request to write over the idbloader is not happening. Are there different types of NAND out there? and does the above image contain the required NAND drivers? (What I think is the NAND chip on my board is labelled 7MG22 NW814, but that doesn't give many results on google so I'm not 100% sure).

hi oneillb, it's correct. At some point the rockchip released a driver which is no longer able to update the loader (

https://github.com/rockchip-linux…a197b77b6e448fc)

The multitool driver should be able to update it (because it has an old kernel).

This is because once the nand was deleted, you were able to restore android. Which you couldn't have done otherwise.

I have used it successfully with

- empty nand

- nand with android installed

- nand with another operating system

and I have never had problems on my boards.

The only difference from your procedure is that I unzip the image before using it with the multitool (multitool supports compressed images, I've just never tried it).

An alternative procedure is the flash through the open source rockchip tools (if you have linux available) explained here RE: [unoffical] LE-9.2/9.80-Images for RK3229/RK3228

I don't mention it often because multitool is the simplest method, and I've never had any particular problems.

Let me know

oneillb, typically wifi errors like yours are due to arp protocol issues.

I don't know how to explain the cause, but basically the router loses the indication of the mac address of the box, which becomes unreachable.

I solved it by increasing the frequency of beacon signals.

For example in my router (dlink 3782) the option is called

Signal-Interval: Set the rate at which your wireless network is advertised. The default is 100 milliseconds

I hope it will be useful

hi oneillb,

I'm glad my build is working fine for you.

I have more or less the same board as you and you are lucky, because it's one of the best around.

To install the build in NAND I used the multitool, but I didn't skip the idbloader.

That option is needed, because some NAND drivers skip the first sectors(even if you erase NAND). But it doesn't work for everyone.

Try ignoring that option and let me know.

edit: I'm slowly improving the documentation of the first post.

hi JoeEdison,

compiled device trees are in the tar version of my builds

LibreELEC-RK322x.arm-10.0-nightly-20220408-c3a59e9-rk322x
├── 3rdparty
│   └── bootloader
│       ├── idbloader.img
│       ├── rk3229-box-hk1mini-ovclk.dtb
│       ├── rk3229-box-hk1mini.dtb
│       ├── rk3229-box-mxq4kpro-ovclk.dtb
│       ├── rk3229-box-mxq4kpro.dtb
│       ├── rk3229-box-tx2-ovclk.dtb
│       ├── rk3229-box-tx2.dtb
│       ├── rk3229-box-v88mars-ovclk.dtb
│       ├── rk3229-box-v88mars.dtb
│       ├── rk3229-box.dtb
│       ├── trust.img
│       └── uboot.img
├── CHANGELOG
├── README.md
├── RELEASE

On my google drive, oldest builds are in the archive folder.

However I'm working on a new build.

In a slower way, but because the build is quite complete.

Hi all,

new build available with:

- linux 5.10.109

- small stability fixes

- backported rockchip remotectl with wakeup/suspend

- ddr3 at 534mhz by default for better compatibility (for example green screen issues)

I would like to thank jock2 and fabiobassa for the support (including moral) and the community behind libreelec.

This operating system is great. As well as the official support for rockchip boards (my job is nothing compared to those who, for example, have been involved in hardware decoding).

Without these people, I would never have been able to make a great alternative to Android for my boxes.

Thanks again

Hi all,

just to say that i have backported the rockchip driver for the remote. This is because it was easier for me, to develop power off/power on via remote.

Also, all legacy libreelec remotes are now supported.

I will wait a few more days before releasing, because there are also other small changes that I want to test thoroughly.

Hi dale,

unfortunately I don't know how to help you.

My images are tested to be flashed as is. You are even using the miniloader from another project (which has a lot in common with this one anyway). I understand that you have difficulty in making it work, but unfortunately for me it becomes difficult to understand where the problem lies.

I can tell you that in today's build I removed a miniloader that was giving me problems. Try and tell me if it's better.

dale, I took a look at your device tree.

It looks like an v88mars (ddrw, nand, ssv6051p) but with the addition of ddr3 scaling.

My images have just that as device tree (without ddr3 scaling support for greater compatibility in the first installation phase). It's very strange. Can you please share miniloader, trust etc etc etc?!

Hi all,

new build available with:

- updated mesa

- linux 5.10.107

- dmabuf enabled

- small stability fixes

hi dale, can you please explain your procedure?! are you using some sort of rockchip flash tool?!

Sadly I don't understand if you have erased flash and burn my image, or you are trying to flash manually every single pieces (this second method never works)

U-Boot, trustos, miniloader are in the TAR version of my builds.

Hi dale, yes... my images contains miniloader, uboot, trustos... in short, it can be flashed directly on the nand / emmc with the various rockchip tools.

I always recommend for those who want to make a backup.

edit: and to assume all the risks involved. the tests were done on a board with nand (mine) and a board with emmc (thanks jock2) so it works. But the rk3229 boards are so many that is difficult for me to give you a certainty, apart that you can't hard brick the board (you can ever go back to another working firmware)

hi MIKMXIII, unfortunately in the last build I changed some kernel parameters which led to some regressions. If you don't need the driver for the 6051p try the previous build. However there are some important changes upstream, as soon as they are released I will update my build. thanks for your patience.

tsbarcelos it seems you have a different chip version than the one supported by the driver. a lot of my patches come from armbian, and unfortunately not having a box with that chip I can't help much. For now, I advise you to use an external wifi.

dale i don't know why you didn't install my build directly in nand / emmc (previous backup). But keep in mind that:

- the mainline kernel needs a partition table to work (legacy doesn't)

- I haven't seen your device tree yet .. but the legacy ones obviously can't work on mainline kernels. try to use mine directly.

Hi, sorry for the late reply, but I took a little break

JoeEdison cec should be enabled. My box does not support it, but if you tell me that with the legacy it worked I try to take a look.

alexwhites wifi gives me problems too, I'll try to understand where is the problem (i think jock2 is right about the cause)

dale tell me which legacy image works for you. I suspect universal dtb has some problem with your board.