CSC Armbian for RK322X TV Boxes


jock

Recommended Posts


out of curiosity I have seen that the drm driver Lima (mali 400-450)
are in fair development,
https://cgit.freedesktop.org/drm/drm/log/?qt=grep&q=lima
and also the mesa opengl
https://gitlab.freedesktop.org/mesa/mesa/-/commits/master/src/gallium/drivers/lima
have you already tested these in developement?
if I want to do some tests, what should I do, who can help me? 
I never built in cross hardware

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

47 minutes ago, nokirunner said:


out of curiosity I have seen that the drm driver Lima (mali 400-450)
are in fair development,
https://cgit.freedesktop.org/drm/drm/log/?qt=grep&q=lima
and also the mesa opengl
https://gitlab.freedesktop.org/mesa/mesa/-/commits/master/src/gallium/drivers/lima
have you already tested these in developement?
if I want to do some tests, what should I do, who can help me? 
I never built in cross hardware

I'm interested in lima too.

At the current moment on libreelec it works very well on different platforms (rockchip, but also amlogic, don't know about allwinner but I guess it works fine either). On my armbian builds here, i don't know the reason why, it fails both in running X11 (which can be expected), but also Kodi without the X server, which in theory is the same configuration as libreelec.

 

Link to post
Share on other sites
4 minutes ago, nokirunner said:

@jock have you tried to compile the latest development-builds?
if you notice there are changes that concern a week ago on the mesa opengl

I didn't try to compile Kodi yet, but instead I did a quick test using the packaged one from Ubuntu Focal, which was 18.6 if I remember well.

It starts, I get to the splash screen, but then it hangs the board and can't even change to another virtual terminal.

Link to post
Share on other sites

@nokirunner yes, most probably it is the right firmware file, but for some reason the last time I tried it didn't work.

The driver is not very helpful in describing what is wrong, just fails with a bunch of cryptic debug messages and so.

But I guess I can give it another chance!

Link to post
Share on other sites

@nokirunner
which kernel is on original android? If you have my same rom you will notice it
At least on mine is 3.10.104
Actually we are on legacy 4.4.194 and main 5.5.xxxx

WE have the firmware and config from original rom,  should be ok using the 3.x.x config and firmware from old kernel , what we miss is the SOURCE driver for ssv6x5x to compile on legacy kernel 4.4.194
We have the one for ssv6051 , but SINCE the ssv6252 (ssv6x5x) is a dual band one 2.4 GHZ/5GHZ I suspect that in some manner the chip is recognized and then badly initiated
My personal 2 cents thought , personally on that board have tried quite every thing for that insane chip and no luck
on old boards with NO 5GHZ the driver is working (  a bit unstable but working) even on kernel 4.4.194 :(

Link to post
Share on other sites

@nokirunner

 

Quote

please, now get me a working wifi


 eh.... would be so easy , LOL :D
But i can send you a little usb hub , just in case, for external usb-wifi  and cam ahahaha
Ok serious , me and @jock already investigated this problem, with uart debugging , without uart debugging , me tried even with needles and woodoo, or exposing the board in a night of full moon  but .....:unsure:

Ok some other tries anyway we will do !!

Link to post
Share on other sites
1 hour ago, nokirunner said:

@fabiobassa
trust me, with woodoo, everything has happened so far because this wifi must now start working 😂

edit:

just to get you noticed, I have not found any ssv6051.ko file ... only ssv6x5x.ko
could this be a good sign?

My guess is that ssv6051p and ssv6256p share the same driver. Looking into the code I see no reference about ssv6x5x file name at all.

 

This is the dmesg messages related to ssv6051 module with ssv6256p firmware:

Spoiler

[   45.556757] generic_wifi_init_module
[   45.834624]
               *** sta_cfg_set, /etc/firmware/ssv6051-wifi.cfg ***

[   45.842138] ssv6xxx_sdio_init
[   45.843465] =======================================
[   45.843528] ==           RUN SDIO                ==
[   45.843539] =======================================
[   45.843555] ssv6xxx_set_sdio_clk:set sdio clk 25000000Hz
[   45.843659] mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 25000000Hz, actual 25000000HZ div = 0)
[   45.863765] SSV6XXX_SDIO mmc1:0001:1: vendor = 0x3030 device = 0x3030
[   45.873969] ssv6xxx_sdio_power_on
[   45.886730] SSV6XXX_SDIO mmc1:0001:1: dataIOPort 0x10000 regIOPort 0x10020
[   45.887390] ssv6xxx_dev_probe(): ssv6200 device found !
[   45.888102] ssv6xxx_sdio_irq_disable
[   45.888633] Read open File fail[/data/wifimac]!!!!
[   45.888721] Write open File fail!!!![/data/wifimac]
[   45.888735] MAC address from Software MAC mode[2]
[   45.888741] EFUSE configuration
[   45.888748] Read efuse chip identity[00000000]
[   45.888754] r_calbration_result- 0
[   45.888759] sar_result- 0
[   45.888768] crystal_frequency_offset- 0
[   45.888774] tx_power_index_1- 0
[   45.888783] tx_power_index_2- 0
[   45.888801] MAC address - 00:00:00:00:00:00
[   45.889458] Registering Vendor80211
[   45.889496] Register SSV cfg80211 vendor cmd(0x67) interface
[   45.889730] [MT-ENCRYPT]: create kthread ecf95540 for CPU 0, ret = 0
[   45.889817] SSV WLAN driver ssv6200: Crypto task 1304 running with priority 120.
[   45.889940] [MT-ENCRYPT]: create kthread ecf926c0 for CPU 1, ret = 0
[   45.890132] [MT-ENCRYPT]: create kthread ecf91f00 for CPU 2, ret = 0
[   45.890195] SSV WLAN driver ssv6200: Crypto task 1306 running with priority 120.
[   45.890309] [MT-ENCRYPT]: create kthread ecf93e00 for CPU 3, ret = 0
[   45.890365] SSV WLAN driver ssv6200: Crypto task 1307 running with priority 120.
[   45.891566] SSV WLAN driver ssv6200: Crypto task 1305 running with priority 120.
[   45.892313] Pre-load cipher
[   45.892345] SSV6XXX TX Task started.
[   45.892563] flash_file /tmp/flash.bin not found, disable sar
[   45.892591] SSV6051Q setting
[   45.892605] SSV6XXX_IQK_CFG_XTAL_24M
[   45.892618] SSV6051Q setting [0x5B606C72]
[   45.892625] TX power setting 0x5b606c72
[   45.892635] Volt regulator LDO
[   45.892766] SSV6XXX RX Task started.
[   45.895789] reset PLL
[   45.914280] @@@@@@@@@@@@
[   45.914320]  SDIO issue -- please check 0xCE01008C 00000000!!
[   45.914327]  It shouble be 0xEAAAAAAA!!
[   45.914336] @@@@@@@@@@@@
[   45.937648] calibation fail:[1]
[   45.959777] calibation fail:[2]
[   45.981931] calibation fail:[3]
[   46.004182] calibation fail:[4]
[   46.026301] calibation fail:[5]
[   46.048781] calibation fail:[6]
[   46.071022] calibation fail:[7]
[   46.093537] calibation fail:[8]
[   46.115729] calibation fail:[9]
[   46.137833] calibation fail:[10]
[   46.159976] calibation fail:[11]
[   46.182168] calibation fail:[12]
[   46.204509] calibation fail:[13]
[   46.226641] calibation fail:[14]
[   46.248736] calibation fail:[15]
[   46.270894] calibation fail:[16]
[   46.293056] calibation fail:[17]
[   46.315271] calibation fail:[18]
[   46.337411] calibation fail:[19]
[   46.359522] calibation fail:[20]
[   46.381625] calibation fail:[21]
[   46.403774] calibation fail:[22]
[   46.425883] calibation fail:[23]
[   46.448203] calibation fail:[24]
[   46.470381] calibation fail:[25]
[   46.492836] calibation fail:[26]
[   46.514988] calibation fail:[27]
[   46.537210] calibation fail:[28]
[   46.559383] calibation fail:[29]
[   46.581515] calibation fail:[30]
[   46.603728] calibation fail:[31]
[   46.625870] calibation fail:[32]
[   46.648113] calibation fail:[33]
[   46.670330] calibation fail:[34]
[   46.692797] calibation fail:[35]
[   46.715004] calibation fail:[36]
[   46.737205] calibation fail:[37]
[   46.759373] calibation fail:[38]
[   46.781603] calibation fail:[39]
[   46.803675] calibation fail:[40]
[   46.825797] calibation fail:[41]
[   46.847990] calibation fail:[42]
[   46.870248] calibation fail:[43]
[   46.892723] calibation fail:[44]
[   46.914889] calibation fail:[45]
[   46.937041] calibation fail:[46]
[   46.959255] calibation fail:[47]
[   46.981358] calibation fail:[48]
[   47.003487] calibation fail:[49]
[   47.025574] calibation fail:[50]
[   47.047707] calibation fail:[51]
[   47.069863] calibation fail:[52]
[   47.092331] calibation fail:[53]
[   47.114575] calibation fail:[54]
[   47.136721] calibation fail:[55]
[   47.158783] calibation fail:[56]
[   47.180975] calibation fail:[57]
[   47.203144] calibation fail:[58]
[   47.225262] calibation fail:[59]
[   47.247367] calibation fail:[60]
[   47.269600] calibation fail:[61]
[   47.291714] calibation fail:[62]
[   47.313747] calibation fail:[63]
[   47.335921] calibation fail:[64]
[   47.358070] calibation fail:[65]
[   47.380291] calibation fail:[66]
[   47.402418] calibation fail:[67]
[   47.424802] calibation fail:[68]
[   47.446886] calibation fail:[69]
[   47.469056] calibation fail:[70]
[   47.491270] calibation fail:[71]
[   47.513351] calibation fail:[72]
[   47.535462] calibation fail:[73]
[   47.557566] calibation fail:[74]
[   47.579698] calibation fail:[75]
[   47.601857] calibation fail:[76]
[   47.624048] calibation fail:[77]
[   47.646174] calibation fail:[78]
[   47.668596] calibation fail:[79]
[   47.690722] calibation fail:[80]
[   47.712856] calibation fail:[81]
[   47.734973] calibation fail:[82]
[   47.757146] calibation fail:[83]
[   47.779344] calibation fail:[84]
[   47.801606] calibation fail:[85]
[   47.823737] calibation fail:[86]
[   47.845878] calibation fail:[87]
[   47.868059] calibation fail:[88]
[   47.890308] calibation fail:[89]
[   47.912775] calibation fail:[90]
[   47.934958] calibation fail:[91]
[   47.957122] calibation fail:[92]
[   47.979265] calibation fail:[93]
[   48.001351] calibation fail:[94]
[   48.023461] calibation fail:[95]
[   48.045546] calibation fail:[96]
[   48.067706] calibation fail:[97]
[   48.090197] calibation fail:[98]
[   48.112805] calibation fail:[99]
[   48.135072] calibation fail:[100]
[   48.143782] ieee80211 phy0: Selected rate control algorithm 'ssv6xxx_rate_control'
[   48.175081] ieee80211 phy0: SSV6200 of South Silicon Valley
[   48.338231] IPv6: ADDRCONF(NETDEV_UP): p2p0: link is not ready
[   48.339953] SVN version 16529
[   48.339988] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[   48.339999] COMPILER HOST icomm-buildserver-T320
[   48.340009] COMPILER DATE 12-08-2017-10:34:54
[   48.340016] COMPILER OS linux
[   48.340025] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[   48.340742] CHIP TAG: 0
[   48.341639] CHIP ID: SSV6006C0        
[   48.355863] 0x800e0000
[   48.422300] ERROR!!Please check interface!
[   48.422359] [0xca000200]: 0x0c000000!=0x00000000
[   48.422369] SOS!SOS!
[   48.422380] Initialize ssv6200 mac fail!!
[   48.455241] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   48.455753] SVN version 16529
[   48.455782] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[   48.455792] COMPILER HOST icomm-buildserver-T320
[   48.455798] COMPILER DATE 12-08-2017-10:34:54
[   48.455805] COMPILER OS linux
[   48.455812] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[   48.456174] CHIP TAG: 0
[   48.456528] CHIP ID: SSV6006C0        
[   48.461840] 0x800e0000
[   48.501769] ERROR!!Please check interface!
[   48.501814] [0xca000200]: 0x0c000000!=0x00000000
[   48.501824] SOS!SOS!
[   48.501834] Initialize ssv6200 mac fail!!
[   48.536594] SVN version 16529
[   48.536637] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[   48.536646] COMPILER HOST icomm-buildserver-T320
[   48.536652] COMPILER DATE 12-08-2017-10:34:54
[   48.536658] COMPILER OS linux
[   48.536665] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[   48.536979] CHIP TAG: 0
[   48.537302] CHIP ID: SSV6006C0        
[   48.541859] 0x800e0000
[   48.577247] ERROR!!Please check interface!
[   48.577285] [0xca000200]: 0x0c000000!=0x00000000
[   48.577292] SOS!SOS!
[   48.577302] Initialize ssv6200 mac fail!!
[   48.581879] SVN version 16529
[   48.581920] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[   48.581927] COMPILER HOST icomm-buildserver-T320
[   48.581938] COMPILER DATE 12-08-2017-10:34:54
[   48.581944] COMPILER OS linux
[   48.581953] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[   48.582281] CHIP TAG: 0
[   48.583507] CHIP ID: SSV6006C0        
[   48.587482] 0x800e0000
[   48.623056] ERROR!!Please check interface!
[   48.623095] [0xca000200]: 0x0c000000!=0x00000000
[   48.623101] SOS!SOS!
[   48.623110] Initialize ssv6200 mac fail!!
[   48.637869] SVN version 16529
[   48.637916] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[   48.637929] COMPILER HOST icomm-buildserver-T320
[   48.637940] COMPILER DATE 12-08-2017-10:34:54
[   48.637946] COMPILER OS linux
[   48.637957] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[   48.638397] CHIP TAG: 0
[   48.639021] CHIP ID: SSV6006C0        
[   48.642206] 0x800e0000
[   48.677275] ERROR!!Please check interface!
[   48.677307] [0xca000200]: 0x0c000000!=0x00000000
[   48.677316] SOS!SOS!
[   48.677324] Initialize ssv6200 mac fail!!
[   48.682825] SVN version 16529
[   48.682863] SVN ROOT URL http://192.168.15.30/svn/software/project/release/android/box/rk3x28/6051.Q0.1009.21.400401/ssv6xxx
[   48.682873] COMPILER HOST icomm-buildserver-T320
[   48.682883] COMPILER DATE 12-08-2017-10:34:54
[   48.682889] COMPILER OS linux
[   48.682898] COMPILER OS ARCH x86_64-linux-gnu-thread-multi
[   48.683218] CHIP TAG: 0
[   48.683599] CHIP ID: SSV6006C0        
[   48.687398] 0x800e0000
[   48.722152] ERROR!!Please check interface!
[   48.722192] [0xca000200]: 0x0c000000!=0x00000000
[   48.722199] SOS!SOS!
[   48.722206] Initialize ssv6200 mac fail!!

 as you see, at a certain point it says something about a register not containing the expected value and then reports errors

Link to post
Share on other sites
12 minutes ago, nokirunner said:

as firmware there are two, but as kernel object I have found only one ...
so if math is not an opinion I have good hopes :D

I'm getting a bit suspicious about this ssv6x5x driver, which does not appear anywhere in rockchip source code. Maybe our ssv6051 is a stripped down or older release, or just an incompatible driver with 62xx series, despite it is heavily based on

Link to post
Share on other sites

Unfortunately things are not so easy as the can appear:
the driver for ssv6051 is 5.037.020 byte long
the driver for ssv6x5x is 6.791.040 byte long

the vermagic of jock's armbian compilation is 4.4.194-rk322x SMP mod_unload ARMv7 p2v8

the vermagic of android's compilation is         4.4.126 SMP preempt mod_unload modversions ARMv7 p2v8 

could also be that as you say is just one driver stripped down but the result is that is not working the ssv6051 on ssv6252 needings . And because of different vermagic even insmod -f (force) simpli refuses to load

Could be a good apport finding the sources ( whole sdk ) of the android rom. Full sdk including the kernel source
Any way @jock is the coder man, I am just the hardware supplier so wait till he enlight us

Where are you located @nokirunner ?



 

Link to post
Share on other sites

@fabiobassa

2 hours ago, fabiobassa said:

Where are you located @nokirunner ?

non si era capito? :lol:
 

 

2 hours ago, fabiobassa said:

Could be a good apport finding the sources ( whole sdk ) of the android rom. Full sdk including the kernel source
Any way @jock is the coder man, I am just the hardware supplier so wait till he enlight us


I'm having fun, so I'll see if I can sift the net like a good truffle mole ..
also because the usb wifi that i currently have available armbian tells me that the firmware are not loaded ... by the way, if i take the firmware from linux for x86 and insert it in the armbian do I have any chance that it works?

this source ... what do you say they could be?
https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx

https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx/tree/khadas-vim3-pie/ssv6x5x

Link to post
Share on other sites

guys, can someone explain something to me?
as soon as i installed the full firmware package from armbian comfig, the system became noticeably more responsive, almost reaching the capabilities of a real desktop, can anyone explain this to me?
have you checked ??
the reason why i installed the full signing package was because the usb wifi that i am using had no firmware installed ...

 P.S. I am very happy that I managed to install the octoprint server without difficulty
bO2kbaG.png

Link to post
Share on other sites

I apologize for the offtopic, but they have not answered me yet on the Libreelec forum.

@fabiobassa I understand that you figured out Libreelec for the RK32xx tv-box.

I configured the ir-remote, but I can not get PowerOn / WakeUp to work.

In /storage/.config/rc_keymaps/my_remote KEY_POWER, KEY_SLEEP, KEY_SUSPEND turn off the system.

But KEY_WAKEUP also just turns off!

I don’t understand anything already.

Did not solve this problem?

Link to post
Share on other sites
8 hours ago, nokirunner said:

non si era capito?

You disguised very well :D I would have said you were American, or Mexican

 

5 hours ago, nokirunner said:

as soon as i installed the full firmware package from armbian comfig, the system became noticeably more responsive, almost reaching the capabilities of a real desktop, can anyone explain this to me?

Nope didn't experience anything like that, but I will definitely check. Which image are you using?

In the meantime, could you run openssl speed -multi 4 rsa and post the summary results here? It's just an openssl benchmark to compare performances.

 

Link to post
Share on other sites

@Maker39
I am very sorry maker39 I didn't figure libreelc and remotes on those boards.

me and jock were focused on armbian and X11 port on 322x and indeed we have shared some patches and ideas and part of codes on the  excelent work of the author of that post but never really used libreelec on my boards. Usually they are kind to answer so just wait maybe they are busy with real life.
Personally cannot help 

Link to post
Share on other sites

@Maker39 The problem with power-on with remote is that the box is... powered off!

The original firmware does never really shut the box off, but keep it in suspend state in u-boot, u-boot "listens" and then is able to react to remote power key and trigger the bootstrap.

 

When you shut down in armbian or libreelec, the box is really powered down, so you need to do a full power-cycle. I didn't investigate too much into this problem, but this is a very common problem on most boards on different platforms when you switch away from original firmware.

Link to post
Share on other sites

Hmm guys, I'd like to say that you should stay away from Ubuntu Focal with mainline kernel images for now. This applies to people who downloaded the image in the past, because at the moment I didn't propose one in the first page.

 

There is a very strange issue with the system time that makes the image not work reliably. I opened a new thread about because at the moment I'm clueless about.

Link to post
Share on other sites
5 hours ago, jock said:

You disguised very well :D I would have said you were American, or Mexican

 

Nope didn't experience anything like that, but I will definitely check. Which image are you using?

In the meantime, could you run openssl speed -multi 4 rsa and post the summary results here? It's just an openssl benchmark to compare performances.

 

@jock don't tell me ... are you italian too?

Well there is to say that I experienced that the system had become very fluid, but today when I turned the TV box back on it no longer booted from sdcard ...
I have to investigate why, I put the sdcard in the pc, so I have access to the files, but I don't know what to manage ...

Link to post
Share on other sites

Hi everyone,

I'm new and interested in the linux topic on tv box, I have many unusable bricks with android, different types of cpu!
I know it will be annoying but the guide to clear the internal memory of the box is not clear to me, could someone make me understand the procedure better?

Greetings from Italy!

Link to post
Share on other sites
  • jock changed the title to CSC Armbian for RK322X TV Boxes
  • Igor pinned this topic