CSC Armbian for RK322x TV box boards

[Benedito Portela]

@lowscore I'did uploading for you!

https://drive.google.com/file/d/1kgyjLl0JXTwFfWfplOKuQY3vLv_KtYlr/view?usp=sharing

[Victor Picinin]

Hi!
I dont know if anyone else mentioned this here but here is my issue:

My RK3229 boots into armbian fine but after like 60sec the screen turns black and both blue LED stays on.
Is there a fix for this?

[Mateus Lima]

I'm trying to boot multitool, but my device is booting directly into android. I've flashed my sdcard using dd and balena, both works fine apparently, the box recognizes the sdcard (it shows on android file manager), but every time I reboot it, it only boots android... Does anyone have any clue of what should I do?

[RaptorSDS]

vor 19 Minuten schrieb Mateus Lima:

'm trying to boot multitool,

Do you try also toothpick (there is a recovery button behind headphone port) methode and SD-Card ? or USB boot , there are some box with lock bootloader

[jeffbzrr]

First of all, I would like to thank you for continuing to maintain this project.

 

I use an RK3228 MXQ running raspotify (another great project) playing music.

 

However, I can't equalize the sound? Is there a way to use a sound equalizer? I tried for ALSA and lost a few days in several things but nothing worked.

[Mateus Lima]

46 minutes ago, RaptorSDS said:

Do you try also toothpick (there is a recovery button behind headphone port) methode and SD-Card ?

What is this method about? Hold the button while it is booting with the sdcard inserted?

I also tried to boot using a usb drive flashed with multitool flashed, but it still boots into android. As for the bootloader, I'm booting it into bootloader mode, and it gets recognised, but "fastboot oem unlock" just prints three dots "..." and doesn't do nothing. In the guide there's a bootloader file I think, but it's not available anymore.

[Mateus Lima]

1 hour ago, Mateus Lima said:

my device

That's my device, I don't if showing it's board will be helpful.

[fabiobassa]

@Mateus Lima

 

I am not very sure this Is a rockchip board.. i see h3q ...may be an allwinner h3 ??????

 

Can you check removing the heatsink ?

 

Or check with USB ttl adapter ?

Edited 21 hours ago by fabiobassa

[Mateus Lima]

1 hour ago, fabiobassa said:

allwinner h3

Well, it seems that I have a very strange device, as I can boot armbian for devices using Allwinner H3, even tho the SoC shows It self as a RK322BA.

I don't know what's happening with my device, and unfortunately, there's no much information about it, just some users trying random armbian builds from devices with the same soc, which works, but features like wi-fi doesn't, probably something that can be fixed making a dtb for this device, which I don't know how to unfortunately.

[fabiobassa]

@Mateus Lima

 

It Is not the first neither will be the last time  that china manufacturers fake soc printing.

Have a look on allwinner forum 

[Victor Picinin]

Quote

My RK3229 boots into armbian fine but after like 60sec the screen turns black and both blue LED stays on.
Is there a fix for this?

This was a watchdog and trust os issue.

For anyone having this issue, i fixed by building a new multitool from OP github: https://github.com/paolosabatino/multitool/tree/master
Changing the RK322x TRUST_OS to: rk322x_tee_1.0.1-72-gf230aa2.bin

And them building a new armbian build replacing the armbian TRUST_OS with this same one. "rk322x_tee_1.0.1-72-gf230aa2.bin"

if anyone needs the builded files "multitool and armbian" feel free to email me at vitorpicinin@gmail.com

[fabiobassa]

@Victor Picinin

Hello Victor thank you for your work.

 

Also @jock and @ilmich managed to obtain free source trust and not the proprietary One but i rembember there were issues ( DMC scaling on DDR3 ??? )

 

Sure jock or ilmich can answer better

[jock]

Hello @Victor Picinin

 

yes the problem is exactly a watchdog in the proprietary trust os. Some people have issues after 60 seconds, others after 30 seconds and others after 30 minutes.

Being the proprietary Trust OS closed source, we can't know what is happening. I suspect it is a sort of automatic "suspend" feature of some sort, but can't be sure because digging into practically is diffucult.

 

What is sure is that if we use OPTEE Trust OS compiled from open sources (OPTEE is the base for the proprietary Trust OS too), there are no issues of sort, but we lose some features like DDR3 memory scaling and "virtual power off" (a suspend mode that can awaken the board via IR-control; there is a driver and a device tree overlay for that to work in armbian)

[Victor Picinin]

@jock do you have this OPTEE already builded for sharing?
The one in your multitool git did not work for me, also it shows the last change was 2 years ago hahahha.

[jock]

6 minutes ago, Victor Picinin said:

The one in your multitool git did not work for me, also it shows the last change was 2 years ago hahahha.

Multitool uses the proprietary miniloader blob for booting and it does not work with opensource OPTEE unfortunately. I guess the issue is related with this patch that allows mainline opensource u-boot to support proprietary Trust OS, but that's just an ineducated guess.

[Victor Picinin]

sorry for my confusion @jock im kinda new to this.

yeah it switched from a 1mim watchdog to a 30mim watchdog crash.

Is there a armbian distro that will work, what should i do here?

[jock]

2 minutes ago, Victor Picinin said:

Is there a armbian distro that will work, what should i do here?

Mmmh, the easiest thing you can do you can build an armbian image taking rk322x_tee_os.bin from this branch in my repo and overwrite rk322x_tee.bin in the same path of your armbian copy, then build a regular image which will have an opensource TEE and should have no issues anymore.

 

Actually you could even reinstall u-boot without reinstalling the whole system, but it is just a tiny bit more involved. If you can restart from scratch, rebuilding the image with opensource TEE is easier.