Posts by ilmich

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

WinUSB (Winusb.sys) installation for developers - Windows drivers

Install WinUSB (Winusb.sys) in the device's kernel-mode stack as the USB device's function driver instead of implementing a driver.

learn.microsoft.com

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

GitHub - ilmich/rkflashtool: Tools for flashing Rockchip devices

Tools for flashing Rockchip devices. Contribute to ilmich/rkflashtool development by creating an account on GitHub.

github.com

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

Post

RE: [unoffical] LE-9.2/9.80-Images for RK3229/RK3228

Hey guys, I have an OTT MXQ 4K (not Pro) device with these specs (real and verified by me with my camera):

• RK3229 CBBKM43012 1552 CPU
• SanDisk P553072141 SDTNRGAMA-008G CP0813618 NAND
• NANYA NT5CC256M16DP-DI RAM (DDR3)
• Pulse H1102NL 1549-M ETH
• Espressif ESP8089 05215 P27X03 WiFi
• Board name T066-V1
• Firmware MXQ-4K_ota_20160308

-Do I have to get *any* file from Android to get remote working?

-Is a new release on the horizon? Latest is from April 2020 and I saw many commits on github, including…

ochentay4

August 17, 2020 at 2:17 AM

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.

Hi Gul-Dukat,

it's very strange, libreelec 9.2 and libreelec 10 have the same driver for remotes.

Instead on libreelec 11 I wrote that they may not work Please try the linked guide in the first post and share results

MIKMXIII I need some logs please (follow this guide https://wiki.libreelec.tv/support/log-files). The 6051p is supported on libreelec 11 because I've a board with same chip.

Hi all

I released the first build of libreelec 11 and then libreelec 10 goes into maintenance mode for a while.

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.

I also changed my approach, in the past release I backported some drivers from the legacy kernel for better usability.

With this version, I don't want to do it because my goal is to make my project an official port.

This doesn't mean that it will be less functional, but that it will take time to develop the missing drivers.

What I know is not working

- some remote controls (tested only mine). please follow this guide https://wiki.libreelec.tv/configuration/ir-remotes and I'm happy to add yours

- some strange wifi chip (only 6051p works for now)

- some strange usb wifi chip (I can add it if you help me)

- NAND (this is the hard part and the only legacy piece that remains)

- DDR3 frequency scaling (work in progress)

- blue/red/green leds (work in progress)

- wakeup from remote

- only one generic box supported (work in progress)

What is not working

- let me known and help me to fix

Extra Features

- nice UI improvements thanks to backported patches https://github.com/xbmc/xbmc/pull/22919 https://github.com/xbmc/xbmc/pull/21557

Cheers

Michele

thanks Gul-Dukat , that's my goal

but then the freeze is after a period of inactivity!? Normally it works without problems?!

However, studying legacy kernel I discovered that each box has tolerances for voltages. Who tolerates low voltages and who doesn't.

I have to create a small driver to handle this, but in this period I can work very little on it

But I'll try to give you some dtb's as soon as possible.

You can also continue to use the installation that works for you, and help me with troubleshooting by simply switch dtb.

There are no significant evolutions in the latest builds.

In the meantime, I also found this patch which looks very promising

Implement front to back rendering by sarbes · Pull Request #22919 · xbmc/xbmc

Description The PR splits the GUI rendering into two passes, if enabled in the advanced settings. In a first pass, all opaque elements get rendered in front to…

github.com

and would seem to greatly improve the UI performance on our beloved boxes. Fingers crossed.

Hi all,

new build available with:

- linux 5.10.172

- mesa 23.0.0

- updated libreelec to the latest upstream changes

- fix for rk3228 voltages (thanks Habitual6824)

- fix for sdcard boot on some board (thanks ochentay4)

- fix for USB Bluetooth dongle

- readded common whitelist video resolution for kodi player

- added t95vpro box (rk3228, ddr3, without spdif output)

Cheers

Michele

Quote from ochentay4

I suspect that the issue you fixed for LibreELEC could be similar for multitool. What do you think? Sadly, multitool doesnt boot at all, with any methods that i tried.

you are right, but multitool is a little operating system based on legacy u-boot and legacy rockchip kernel etc etc.

My Libreelec instead, is based on legacy-uboot but 5.10.x mainline kernel.

Quote from ochentay4

I hope you get a script working, and on my side I will try to learn how to flash IMGs with rkdeveloptool using a live Ubuntu (im not good with linux but I can learn).

I suggested you wait for my script because it's a safer choice.

You can though, but it's a thing for those who know what they're doing, do it directly from the sd card.

If you copy the libreelec image to the sd card and run the following command

dd if={path_of_image} of=/dev/rknand0

the internal memory will be overwritten.

But keep in mind:

- to allow booting, libreelec build scripts tag partitions with unique ids. These ids change with each build and are used to detect the boot partition.

So if you download an image and flash it to both nand and sdcard, then boot will always go to sd card if you reinsert the same.

You don't run the risk of breaking anything, I see you handy in the flash of the box and therefore you can easily restore it. But I just wanted to tell you what you can get into.

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