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
├── RELEASEOn 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.
Hi all,
new build available with:
- updated libreelec source (10.0.2)
- ssv6051p wireless driver
- other fixes and small optimizations
Hi all,
new build available with:
- updated mesa (gpu works better)
- safe device tree (without ddr3), and possibility to change it via shell script (login into libreelec with ssh)
about this last feature I will document better in the main post, but in the meantime:
rkelec:~ # rk322x-dtb-switch.sh
usage: /usr/bin/rk322x-dtb-switch.sh [list|switch|help]
show show current device tree
list show available device trees
switch [device tree] switch to a device tree
help show this helplist available dtbs
rkelec:~ # rk322x-dtb-switch.sh list
rk3229-box-mxq4kpro-ovclk
rk3229-box-mxq4kpro
rk3229-box-ovclk
rk3229-box-v88mars-ovclk
rk3229-box-v88mars
rk3229-boxswitch, for example, to rk3229-box-v88mars
rkelec:~ # rk322x-dtb-switch.sh switch rk3229-box-v88mars
Device tree rk3229-box-v88mars founded
Are you sure(y/n)?y
Mounting flash rw
Switching dtb
Mounting flash ro
Switching is ok, now you need to reboot!!and reboot box.
for the leds tomorrow I'll release a new build with some 'legacy' device trees.
I've also developed a simple shell script for choosing the right one even on a running libreelec instance (useful in case of nand install).
other issues are WIP
ps: try to suspend instead of power off the box. I've developed a simple hack that resume with remotes
For the wifi driver (6051p) I trust you.
I remember you said a while ago that nand might never be supported but now yes...
thanks, although to do that I went out of 'standard' libreelec as that driver is 'legacy'. however mine is and will remain an unofficial build and my goal is to make as many things work as possible
hi JoeEdison,
thanks for your feedback, in the next build I updated the driver for the mesa gpu, where i saw some good optimizations.
Now that my build is working more or less well I am starting to refine it.
Unfortunately, the initial idea of having a universal device is not good for everyone. So the idea is
- create a safe device, which should allow booting on all boards
- recreate the legacy device trees so that everyone can choose their own (a bit like the amlogic port) manually or with a shell script
regarding the 6051p, I'm still having trouble getting it to work.
alexwhites in the meantime you can confirm me that with the build that works for you, you have no video resolution problems?!?!
Hi all,
I've released an updated build with support for NAND and other things. See changelog in the first post.
alexwhites try it and let me know.
