CSC Armbian for RK322x TV box boards

[Joshua allen]

fabiobassa it's an off topic question so I was trying to be nice. And keep the 1uwstiona more on target to what was originally asked

[fefpi]

Hello,

I am new to Armbian, but have access to a lot of RK3228A  boards and up to now I have installed  it on some.

I noticed that a big part of these boards have the Wi-Fi module sv6x5x, like sv6158, sv6212p, 6051 and sv6030p (the last one is not 6x5x, but ok)
I also noticed that this type of module kind of  had support in the past, since older RK322x images came up with the corresponding Wi-Fi driver (ssv6x5x), but the newer images don't seen to come with it.

The problem lies on the fact that older images (legacy kernel) are not supported anymore.

 

So my question is:

Is there a way to select some configs on the Armbian framework to build images that come with this driver? If not, is there any tips on where I can get the source code and how I can compile it myself ?

[djmuted]

Looks like I got really unlucky and received an unusual version of the MXQ PRO 4K (5G version). It has a weird WiFi chip called EA6521QF. I could not find much about it online. 
My stock Android ROM contains the following kernel modules: 8189es.ko, 8723cs.ko, rk29-ipp.ko, ssv6051.ko, 8723bs.ko, 9012p.ko, skw.ko, ssv6x5x.ko, vcodec_service.ko, ssv6558.ko, skw_sdio.ko and 8189fs.ko
If anyone is interested, I can provide a MultiTool eMMC backup. 

EDIT: I found some firmware files for that chip in the stock ROM as well:
EA6621QT_SEEKWAVE_R00005.ini, EA6621QT_SEEKWAVE_R00005.bin, EA6521QF_SEEKWAVE_R00005.ini, EA6521QT_SEEKWAVE_R00005.bin, EA6621Q_SEEKWAVE_R00005.bin, EA6521QF_SEEKWAVE_R00005.bin, EA6521QT_SEEKWAVE_R00005.ini, EA6621Q_SEEKWAVE_R00005.ini

Looks like skw.ko and skw_sdio.ko are the kernel modules for this chip. I'll try to load them under the legacy kernel later and share the results. 

Edited February 11 by djmuted
Added firmware files

[djmuted]

Sorry for double posting, I found some source code for that EA6521QF WiFi kernel module here: https://github.com/TinkerBoard-Android/rockchip-android-external-wifi_driver in ea6621q directory (version 2.0.240304.e998adb)

I managed to compile it and it works. Place the .bin files in /lib/firmware and place the .ko modules in /lib/modules/4.4.194-rk322x/kernel/net/wireless
Change permissions of all these files to 664 and chown root:root.
Add these lines to the end of /etc/modules

skw_sdio
skw_bootcoms
skw

Run depmod -a and reboot.

These modules were compiled for the legacy kernel, they will not work with anything else (however you should be able to build these modules from source for newer kernels).
Tested on this Armbian build: https://users.armbian.com/jock/web/rk322x/armbian/stable/Armbian_22.02.0-trunk_Rk322x-box_bullseye_legacy_4.4.194_minimal.img.xz

No changes to the device tree are needed. 

EA6521QT_SEEKWAVE_R00005.bin EA6521QF_SEEKWAVE_R00005.bin EA6621Q_SEEKWAVE_R00005.bin EA6621QT_SEEKWAVE_R00005.bin RAM_RW_KERNEL_DRAM.bin ROM_EXEC_KERNEL_IRAM.bin skw_bootcoms.ko skw_sdio.ko skw.ko

Edited February 13 by djmuted
Added compiled modules and firmware

[anzvanie]

On 12/28/2024 at 12:57 AM, Asriel Nguyen said:

Hey, sorry for late response

Here are the images

https://alist.genshin.gay/rk3229

Also, I did solder an sd slot but it seems to be boot looping (the flash drive flickering). That's just my guess

I have a same board with @Asriel Nguyen, following the instruction for NAND board without SD card but after step write u-boot-main, my board unable to boot.

[Helio]

Hello everyone! I have a mxq Box with txcz-mxq-ep-v10 board rk3228a processor, the only multitool image that works is bad-trust, even so it works for about 30 seconds then it turns off (black screen), what could be wrong? Thank you very much!

[anzvanie]

On 2/20/2025 at 3:54 PM, anzvanie said:

I have a same board with @Asriel Nguyen, following the instruction for NAND board without SD card but after step write u-boot-main, my board unable to boot.

@jock @Asriel Nguyen finally I found the solution.

Rockchip has an official document say:

 

Quote

The physical address of  offset in wl command is the offset plus 0x2000, eg:

"rkdeveloptool wl 0x2000 uboot.img" will write uboot.img to emmc 0x4000 address.

 

https://opensource.rock-chips.com/wiki_Rockusb#Maskrom_mode

 

So, the command of write u-boot-main.img is

 

rkdeveloptool wl 0x2000 u-boot-main.img

 

After write u-boot, you able to boot MultiTool from OTG USB

Edited February 27 by anzvanie

[anzvanie]

@jock I've install Armbian with legacy kernel downloaded from the following link.
https://users.armbian.com/jock/web/rk322x/armbian/stable/Armbian_22.02.0-trunk_Rk322x-box_bullseye_legacy_4.4.194_minimal.img.xz

 

But I've problem that this version has architecture is "linux/arm/v7" which prevents me to run many docker images only support aarch64.

Do you know any other build of Armbian with legacy kernel which support aarch64.

Thank you so much.

 

[MattWestB]

RK322Xs is 32 bit ARM CPUs and can only running 32 bit OS so not possible installing aarch64 OS on the hardware.

Also it have not enough RAM (normally 1 or 2 G) for running very large docker containers.

[Void Spirit]

Hello. "rkdeveloptool wl 0x2000 u-boot-main.img" this line must be entered in the file itself "uboot.img" in the folder "bsp? Or just rename the file. please tell me more precisely. I don't understand at all. I've tried all kinds of multitool. Always a black screen

Edited March 6 by Void Spirit

[Enzo Esteban]

Hello guys @jock @fabiobassa and @everyone who can supports

I'm Esteban, an engineering student at UNESP in Sorocaba (Brasil). It's a pleasure to be in touch with this community.

 

I've been having a problem that I haven't been able to solve for days, and my last attempt was to contact. I've been studying for a long time how to de-identify TV boxes, and I realized that the model that the college provided (TX9) is not authentic, because it has a different processor than the one indicated by the manufacturer. In any case, the problem is the following:

 

We need Wi-Fi access, preferably on-board. I know and have already tested wireless USB Wi-Fi, it works normally, as well as with cable, but because we have a huge amount of TV boxes to de-identify, and give them another project purpose, we would like to make it easier and use the on-board itself, but the easy way is proving difficult.

 

I disassembled my TV box, and checked, in addition to the software, the hardware, which both indicate that my processor is a Rockchip RK 3228, and my Wi-Fi antenna is an SV6051. Internal flash eMMC

 

I've been studying not only on this repository, but also several foreign forums, and I saw that both mention that because this antenna is very old, there is no driver compatible with kernels > 4.5. So, I've been testing all the images I could find on the internet, from higher kernels 5... to legacy 4.4 <... But I was unsuccessful in enabling the Wi-Fi.

 

I don't know what else to do, I would like someone give me some support to see if we can solve this problem. Here are some ISOs from your website that you provided that I've already tested, but when running Linux, it doesn't recognize the Wi-Fi antenna, in the command
rk322x-config It always indicates that Wifi device not avaliable

 

Edited Friday at 05:20 AM by Enzo Esteban
just missing the @

[RaptorSDS]

Dear Esteban

vor 4 Stunden schrieb Enzo Esteban:

. But I was unsuccessful in enabling the Wi-Fi.

Did you try the LED-Config settings , like we multiple times tell that led-config also switch Wifi-enable pin to diffirent settings or ports  ,

 

be aware that there are so many rk322x box and other box around , with so many cheap and creepy hardware also fake and misleading prints on chip and reycling hardware

 

[Enzo Esteban]

1 hour ago, RaptorSDS said:

Did you try the LED-Config settings , like we multiple times tell that led-config also switch Wifi-enable pin to diffirent settings or ports  ,

 

 

Nah i didnt make this, i read about it, but you know when you are so focus on one think that you dont know more what are you doing? is me now about these tv box bro

 

i will try this tomorrow, and will keep all my energy on this  until next week. i will give attenttion on this LEDS, forum have 94 pages i read full 40 +- and start a burnout in my brain

[Enzo Esteban]

i've explore all rk322x options but no sucesfull. 🫠 🆘

[RaptorSDS]

vor 11 Minuten schrieb Enzo Esteban:

i've explore all rk322x options but no sucesfull.

thats weird because ssv6051 is a know hardware for this box , when no led-config work than we need a dtb/dtbo of orginal android from this box

 

else, maybe you can try LibreElec and look if is found there than we have idee whats wrong --> or maybe a bad chip or fake chip

[jock]

2 hours ago, Enzo Esteban said:

i've explore all rk322x options but no sucesfull. 🫠 🆘

As said several times in this thread, the marketing name does not mean anything. You have to look to the silkscreen on the boards (or post some decent photos of the board on this forum), that tells you much more. leds-config are based upon that, and not about the marketing name, which is just a random placeholder, as you experienced by yourself.

 

About the wifi chip, a driver for ssv6051p chip is available in mainline kernel (version 6.12), and is an attempt to fix the vendor kernel (version 4.4) driver by @ilmich and me and mostly it works. If you have another ssv6xxx chip, no luck, you won't gain any driver for mainline kernel and you have to restore to vendor kernel, which is way older, unmaintained and unsuggested.

 

If rk322x-config does not detect any wifi chip, it is because the wifi chip is turned off and must be first turned on; that's one of the purposes of the led-config utilities. Beware that you have to reboot the board and run again rk322x-config to see if the chip has been turned on or not.

 

 

[Enzo Esteban]

Hey guys good morning, thanks for all thats supports! 😊

i am totaly new on linux so i am really lost and somethinks... 

 

1.

10 hours ago, jock said:

About the wifi chip, a driver for ssv6051p chip is available in mainline kernel (version 6.12), and is an attempt to fix the vendor kernel (version 4.4) driver by @ilmich and me and mostly it works. If you have another ssv6xxx chip, no luck, you won't gain any driver for mainline kernel and you have to restore to vendor kernel, which is way older, unmaintained and unsuggested.

 

12 hours ago, RaptorSDS said:

thats weird because ssv6051 is a know hardware for this box , when no led-config work than we need a dtb/dtbo of orginal android from this box

 

 

I checked these kernels, after some hours tryng on diferents ones, the version "Armbian_24.2.5_Rk322x-box_bookworm_current_6.6.22_xfce_desktop" that i take on "https://armbian.hosthatch.com/archive/rk322x-box/archive/" works for me!!
after changing leds configs, the one who works was "led conf2"
so my wifi device: South Silicon Valley 6051/6256p - device ID: 3030:3030
well done, 50% problem solved 😁 ✅

now i am having problem how i can connect my wifi on this. i was studyng about this, i saw someone telling for disable one and just let wlan0 (??) ( dont know how do )
after tryng and reading this forum i reach in this result:

ls /sys/bus/sdio/devices

mmc1:0001:1                     

lsmod | grep ssv
ssv6051 151552 0

so i think it recognize WIFI as well. ✅

so i tryed to connect to wifi, by 3 methods

 

1. By armbian-config

wifi option didnt shows,

 

2. By sudo nmtui
Create a new wifi conection with ssid and password, nothings happends

 

3. By sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=BR

network={
    ssid="SSID USER"
    psk="Password"
    key_mgmt=WPA-PSK
}

 

also dont works, so can help with step by step how can i solve this connection?
 

[jock]

@Enzo Esteban without logs it is impossible to give any hint

[fabiobassa]

@Enzo Esteban

unfortunately ssv6051 and ssv6256  present themself as "South Silicon Valley 6051/6256p device ID: 3030:3030"

if you have ssv6256 it will not work

is a 5ghz wifi  tvbox?
can u supply some high resolution board photo ?

[Enzo Esteban]

5 hours ago, jock said:

@Enzo Esteban without logs it is impossible to give any hint

With logs do you want? how do this? @jock

 

4 hours ago, fabiobassa said:

if you have ssv6256 it will not work

is a ssv6051p, follow the images @fabiobassa

 

 

Edited Saturday at 06:32 PM by Enzo Esteban

[fabiobassa]

@Enzo Esteban
can you check with great precision the stamp on the cpu ? In second image

To me it seems a 3328 ......... and not a 3228 . Great difference my friend !!!!!!!!!!!!

If it is really a 3328 you are simply doing ALL WRONG . They are totally different cpu's and totally different drivers

The 3328 is a 64 bit aarch64 architecture

The 3228 is a 32 bit armhf architecture

BTW if you are in Brasil, try to contact this people . Basing on our early study they did a distro fitting on these cheap tvboxes

https://github.com/educabox/educabox/tree/main

 

Edited Sunday at 09:15 AM by fabiobassa

[Александр Соколов]

I have a question about disabling bootdelay=1 in u-boot, why can't I disable it. After entering the command to save saveenv to mmc0 (sd) the error "Saving Environment to EXT4... ** Unable to use mc O:auto for saveenv **" after the command mmc dev 1 the situation does not change. What am I doing wrong? I'm just trying to disable ttyS2 so that commands from the device connected to it do not interrupt the boot, because u-boot sees data from ttyS2 as like keyboard input.

[Enzo Esteban]

7 hours ago, fabiobassa said:

To me it seems a 3328 ......... and not a 3228 . Great difference my friend !!!!!!!!!!!!

If you don't tell me, I would never realize.

i check two times, but print is verry bad, so i sujest was 3228, so by now my job here is finish

idk why, this TX9 fake has 3328, and have also 322x, so i will make this on many of them and verify one by one.

 

by now i will go to 

 

thnks guys!

[jock]

11 hours ago, Александр Соколов said:

I have a question about disabling bootdelay=1 in u-boot, why can't I disable it. After entering the command to save saveenv to mmc0 (sd) the error "Saving Environment to EXT4... ** Unable to use mc O:auto for saveenv **" after the command mmc dev 1 the situation does not change. What am I doing wrong? I'm just trying to disable ttyS2 so that commands from the device connected to it do not interrupt the boot, because u-boot sees data from ttyS2 as like keyboard input.

The environment has never been actually tested. Once it was saving and restoring it from a sector on eMMC, but then later changed to the "default" ext4 environment, but never tested even because older u-boot were used to corrupt ext4 partitions when trying to write to it.

[Александр Соколов]

I even made a boot partition on fat 32 to save the settings, the system loads and works. But as if u-boot has no rights to write in the env file on the boot partition. Maybe there are patches that can be applied to u-boot?

[Void Spirit]

Hello everyone. I really need help. I've been trying to install Armbian for two weeks. I have an X96 Mini TV box (2/16 fake) and a real 1/8. I've installed several different versions of Android (7.1, 8.1, 10). I tried to install various multitools, but every time I get a black screen. I recorded the images using balenaEtcher. Then I successfully installed LibreELEC. It's possible that I was using incompatible Armbian images, but why can't I run the multitools?

[RaptorSDS]

vor 5 Stunden schrieb Void Spirit:

Android (7.1, 8.1, 10).

android 8.1 possible but 10 i thing its a fake 7.1 , Android mostly only poor patch together for exact one box i have many bad exp with port a android (also from same main cpu) to another box

 

all android and linux are config by dtb files , there are the information for kernel wich memory and voltage and many other stuff , ( this box have 3 diffirent memory system nand flash, emmc and eMCP flash) so a wrong dtb could be a non start box

also in last time many box have problems with hdmi port an start without display but its than maybe possible to start ssh from network lan port of this box

 

maybe also fake rk3228 cpu you tool also report a s905w chip , we have see sold as h6 ,print as amlogic at android  and inside a motorola cpu 

 

[MattWestB]

Some board have no standard HDMI config and is not being activated on standard boot with Multitool and other Armbian images.

Best is trying one current multitool on SD-card and booting and look on the LED if its continuous lighting or start flashing slowly after some minutes (first boot takes longtime then resizing the SD-card). If getting blink = system have booting OK. Then connect with SSH to the device (thru Ethernet or the comport on the PCB) and making the mulltitool things. After installed do the same  on the installed Armbian.

[Void Spirit]

Unfortunately, the indicator was always red. No flickering. The color changed only when the system was started (android). Is it possible to install Armbian via a USB cable?