Hi all,
new build of libreelec-10 available with:
- linux 5.10.180
- mesa 23.0.3
- fix boot from sdcard in some circustance (thanks jaum20 for reporting and testing and jock2 for solution)
Cheers
Michele
Hi all,
new build of libreelec-10 available with:
- linux 5.10.180
- mesa 23.0.3
- fix boot from sdcard in some circustance (thanks jaum20 for reporting and testing and jock2 for solution)
Cheers
Michele
Hi jaum20,
try this build. It's a preview of the next update that I decided to do to include the fix for your problem.
Keep in mind one thing though. Your problem is related to a boot component of your armbian installed in nand.
I won't go into too much detail but basically you have an opensource trustos (optee) that is loaded on boot (If you look at the log you sent me, the errors related to 'sip v2' are related to the fact that the opensource trustos is probably not compatible).
Libreelec instead uses the proprietary one because it gives you the possibility of having ddr3 scaling and startup via remote control.
Therefore, if you should have problems in this sense, the only solution is, in your case, to update the trustos you have in the nand. But this might give you problems with armbian.
If I remember correctly, armbian also switched to using the same trustos as libreelec at some point (maybe jock2 can help us with that).
So maybe the solution is even simpler and consists of some update that you can easily apply.
Should I switch the dtb after install as showed on the post #2?
yes, mainly this is needed in order to configure leds and some other features.
Thanks a lot and let me know
Michele
thank you so much for your precious support. Try doing the same thing they suggested in the past with this dtb that I am attaching (remove .txt extension).
I have a question, how did you install armbian?! Via usb cable, or multitool, or what?!
jaum20 wich armbian?! legacy?! stable?!
I've a spare box, so I can try to reproduce the issue.
thanks
Michele
Hi jaum20,
the startup error is very strange.
I see the kernel tries to set the gpu clock to 600Mhz which my build does not.
Did you use the dts of my build!? or someone you adapted!?
Thanks
Michele
HI,
sorry if I reply late, next time I ask you the courtesy of writing in the dedicated thread ([UNOFFICIAL][RK3228/RK3229]Libreelec builds).
However there is currently no script for installing to internal storage mainly because my builds aren't 100% stable,
So installing to internal storage is for those who know what they are doing.
However there are two ways to install the nand build
- via the armbian multitool bootable via sd card (https://forum.armbian.com/topic/12656-cs…k322x-tv-boxes/)
- using the dd command directly from an sd-booted build of libreelec as explained here (RE: [UNOFFICIAL][RK3228/RK3229]Libreelec builds)
Let me know.
Michele
Hi foxy,
please try to be a little more specific.
This is to avoid the stupid question like.. "are you sure you have a rockchip rk3228"?!
for example, can you tell me if libreelec starts from the sd card!? and the multitool?! Are you just having problems installing it on internal storage?!
Finally, could you send some photos of the board contained in your box?! MXQ PRO 4K can also contain amlogic or allwinner chips.
Thanks
Michele
Hi shMatrix,
thanks, but it's not quite like that.
The tools that currently exist for Windows need a driver because they don't know the rockchip usb protocol.
My tool implements it in user space and therefore technically it doesn't need a driver, but only to access the device via USB.
On Windows there is a generic driver called winusb, but in practice, it must be associated with the rockchip box which connects via USB.
On windows 10 it is done with the procedure that I have indicated. On windows 7 it has to be done manually and maybe I figured out how.
Hi bacalazin,
sorry, but honestly windows is not my operating system so I tried just the basics
I did more tests and saw that the device must be configured as a generic winusb.
I'm trying to figure out if I can create an ad-hoc driver but in the meantime the guide I followed is this
try and let me known.
Michele
I'm working on this tool because:
- I needed a simple tool for boards that I have without SD card
- have a tool that also works on Windows (for users who are in your situation)
So, given that the software is highly experimental and tested only by me:
- download prebuilt 64bit windows binary: https://github.com/ilmich/rkflash…-5.90Alpha1.zip
- extract it somewhere. The zip contains the executable and a bootloader for RK322x.
- put your box in loader mode (insert a toothpick into the A/V port and connect the OTG cable)
- then execute
rkflashtool.exe b 3 // this put your device in maskrom mode
rkflashtool.exe l rk32\rk322x_loader_v1.10.238_256.bin // this put your device in usbplug mode
rkflashtool.exe d > backup.img // optional, this do a full backup of your nand
rkflashtool.exe f path_to_uncompressed_libreelec_img.img // flash the image
rkflashtool.exe a rk32\rk322x_loader_v1.10.238_256.bin // install bootloader on nand
The box must be in USBplug mode for the tool to work properly, so the first two commands are mandatory.
Hi ochentay4,
I've continued my fork of rkflashtool
which is now able to update the bootloader. It's a highly experimental tool (I'm a volunteer) but it should help you flash libreelec to internal memory. It can also be compiled for windows, but at the moment I don't have a machine to do it.
Hi deckard,
the images you can download, unless otherwise specified, are raw images of the operating system.
This means that you have to use them by writing them directly to a boot device (whether it's a hard disk, a USB stick, SD card, internal memory etc etc etc).
95% of rk3229 android boxes allow to boot from sd card, so use any tool to write image to sd card ( https://wiki.libreelec.tv/installation/create-media).
Once the image has been written, insert the sd card and power up the box.
edit: for modern libreelec builds try [UNOFFICIAL][RK3228/RK3229]Libreelec builds
Ok then yes, 10 can be installed in nand. The recommended method is using the armbian multitool but if I remember correctly it didn't work with this board.
However I don't know the status of your board, but the one I have has android 4.4. So the multitool problem could depend on an old bootloader that doesn't activate the sd card correctly.
However this board is very well made (good heat sink, external antenna, easy to use uart) so as soon as I have some time I will try the multitool to try to understand where the problem is.
Another method is to use a usb-a to usb-a otg cable and flashing tools, but it's a bit more 'complicated'
Hi ochentay4,
If you are referring to 11, unfortunately if you have a NAND device still not. I'm working (slowly) on it.
Anyway I just got a board similar to this one
finally, I can try to experiment directly with esp wifi chips
Hi all,
new build of libreelec-10 available with:
- linux 5.10.176
- mesa 23.0.1
- backported some Kodi Nexus patches to speed up UI rendering (now 25fps at 720p it's not a utopia)
Cheers
Michele
Hi all,
new build of libreelec-11 available with:
- linux 6.1.19
- mesa 23.0.0
- reverted https://github.com/xbmc/xbmc/pull/22919 (for now)
- estuary skin optimization. removed the ability to set a background graphic pattern for performance reason
- small fixes and improvements
This build is an alpha release (not for daily usage), it contains some changes that break the update from 10 and it is strongly recommended to install only on sdcard (currently) and stay with libreelec 10 if something doesn't work.
Cheers
Michele
Thank you chewitt,
I noticed it too. I will try to support sarbes, hoping his patches land in kodi. It's doing a great job with the help of renderdoc, and 'less powerful' devices benefit much more than others (where the changes aren't even noticeable).
With other patches, I reached 30fps at 720p resolution, which for the rk322x is a miracle with Estuary skin.
Gul-Dukat please wait next build, I've removed the offending patch (but I will use your pictures as a sample to explain the issue better to the developer)
MIKMXIII you don't have the possibility to use ethernet?! In that case, I try to share something useful for debugging.