Hi ochentay4,
but what did you install in nand!? Android or legacy libreelec!?
Anyway for the multitool keep asking for help in the armbian forum and follow any indications from jock2 and fabiobassa . They are my mentors, but it's not always easy for someone on the other side of the forum to help if someone just says "it doesn't work".
However I'm working on a script that automates the installation to internal memory, but it will take me a while.
Hi ochentay4
yes, installing on nand is supported.
The best tool is the multitool from armbian.
Another method is with usb cable and rkdevelop tool.
woow thank you so much.
now read the first post because by default the device is generic.. you need to switch the dts in order to enable ddr3 frequency scaling.. leds etc etc
Hi, thanks a lot
the last test,
https://ilmich.libreelec.tv/test/LibreELEC-RK322x.arm-10.0-nightly-20230302-b1e877a-rk322x.img.gz
unfortunately not having the board I don't know how to help you if it doesn't work.
However, I see that the sd controller is not working.
This may depend on
- the controller is not active (strange)
- you are using a bad or incompatible sd card (with the mainline kernel).
The rk3229 can also support uhs sd cards but in practice, it depends on the box
In my build, the speed of the sd bus doesn't go to the maximum to have better compatibility.
Hi ochentay4, thanks for the help,
try with this test build
https://ilmich.libreelec.tv/test/LibreELEC-RK322x.arm-10.0-nightly-20230301-b1e877a-rk322x.img.gz
in this build I've disabled some sdio gpio reset that can (if I remeber correctly) conflict with sd card reader.
Legacy dts seems similar to mine regarding sdcard controller.
For dmesg try typing
dmesg | grep mmcand make a picture (there is no alternative)
The error you are getting is related to the kernel not being able to detect your sd card (or controller).
Please try running the dmesg command from the prompt you see in the error phase (connect a USB keyboard to type it) and send some useful info.
Otherwise I don't know how to help you, the causes of the failed boot can be many. Having a box with nand also depends on what you have installed as a bootloader in internal memory.
However, as soon as I have some time, I'll do a test by installing legacy libreelec in one of my boxes to try to understand something.
I tried some videos taken here
Downloads – Videos » libde265 HEVC — H.265 High Efficiency Video Coding
and downloaded locally. (also with network but I don't use samba, but a simple HTTP server on my nas)
I haven't noticed any slowdowns for fullhd. 4k has problems, but today I can only test with a ddr2 box that can't handle it, so it's normal.
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
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: p1But if you have patience we will try to fix everything
But nothing starts!? Or is there an error you can send me!?
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 /flashthe 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/nvmemthis 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.
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
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
