fabiobassa

@Minoro Hamada Supposing you removed the sdcard from the slot, the only way to tell you what is happening is providing logs from the serial interface. You may have a broken/read only eMMC. Also you did not specify what image, what kernel, what board you have...

@Mr-TNTplease can you send some picture of board ,
 
there are 2 boards with problem first wherer the right LED-Config has to been set with ssh after flash per LAN , the secound has a close bootloader which need a diffirent OPTEE area wich need to be flash seperatly
 
overall normaly when sd-card boot work than  later it should also boot from that , yyou can also flash armbian direct to sdcard and also try to boot from sdcard maybe as short term solution

Hello @Vladimir Trondin, as @fabiobassa already pointed out, there is no driver for ssv6158. Doing some research, it seems that it may use the ssv6x5x driver, but it would require adaptation, plenty of time, plenty of patience and you would not be sure if it will finally work.
 
About the eMMC of your board, it would be handy to get the output of dmesg command, but in the meantime you could do some experimentation with the emmc parameters in rk322x-config withing this page:
 

 
In particular, try to enable emmc-pins and emmc-ddr-ph45 or emmc-ddr-ph180 or emmc-hs200 (these last three are alternative, only one should be enabled) and see if your emmc gets detected after a reboot.
 
Also your board r3229q is not listed within the led-conf options, but I see some similarities with r329q board (led-conf2) MXQPRO_V72 (led-conf6), so you may start trying with those ones, or stick with generic since your wifi is already detected despite being useless.
 

It isn't very big problem, USB dongle Ralink MT7601U works fine.

Looks like problem is related to the newest versions, Armbian_22.02.0-trunk_Rk322x-box_focal_legacy_4.4.194_xfce_desktop.img.xz works fine. But wifi doesn't work (sv6158).

@E O Bernardini From the first page opening post is https://users.armbian.com/jock/rk322x/armbian/stable/ you find the last Jocks builds.

@Parth the soc is slow, it is one of the slowest socs around with a modest amount of memory on board , so don't expect stellar performance.
The image with debian bookworm is a minimal image: small and good for servers.
 
For all the other questions, you can consult the official armbian documentation  https://docs.armbian.com/ and related forums

@fabiobassa
 
my plan here is simple, i wanna use it as a linux box where i can have a 21inch touch screen display running a flutter app. and ofcourse some other nittygritty things like it would be controlling some hardware over usb, would have GSM for network connection and so on. since this is a cheap thing available than a raspberry pi, best to use this for the purpose.

@Parth
Even 3128 is working quite well with linux  just compile kernel with appropriate config and appropriate cpu platform

Regarding the garbage on uart, remember the uart speed is unusual  ( 1500000 NOT 115200 ) until it starts modified uboot that is 115200 so you have to take care of this note

I am the one in this project that discovered the uart pins on mostly of 322x boards and I can give for sure that if garbage comes out is:
wrong pin
wrong speed
lack of ground

On the software - firmware side   can give you answers  @jock  @RaptorSDS and all the friends athat daily work on those boards
 

@hfrts hello!
 
First of all: no documentation from the manufacturs of any kind. Cheap tv boxes come without any kind of documentation: they are dirty cheap hardware with barely working software.
 
The board footprint/silkscreen is indeed the first thing to look for to find the matching led-config: all known boards are listed within the rk322x-config script.
If your board is not listed, then the stock firmware (or its device tree) and photos of the board most of the time are enough to properly match an existing led-config with the board or create a new led-config for a new board.

ah ok , thank you , I'm going to test a usb key wifi

two methods ,
1. boot image first than automatic resize to bigger size ( most of the drive) , than put your image on card
 
2. use the compressed image of armbian on the sd card , the multotool also can use zip and tar and tar.xz and tar.gz

wirte the armbian image to SD Card and than insert and start , than it should boot from SD card like the multitool
 
i had nowadays 4 of this box, one old AMlogic s802 ( over 5 years in use with armbian scan and printserver) ) 1 xrk322x that work out of the box with armbian , one rk322x with resolder wifi from wired china chip to rtl8723ds , and now a rk3328 with android ( sadly sd card is on wrong sdio port)

I sent them a message, even sent an email and a whatsapp to the manufacture ( junuo ? hehe) , will see if I get a reply, google sadly doesn't help as seems it's the latest version of the board (v3.0), I really want to make this wifi work 😂 

The thing about SBC is that I already have one, the thing is that I spent some good time searching for a chip that would have multiple usb hosts instead of just one, and that's not easy to find, specially not below 50 euros, I came across the rk3228, that somehow is available at those tv boxes :(.

@Blyato From dmesg I see the wifi chip is just turned off:
 
[ 1.716294] mmc1: Failed to initialize a non-removable card  
I'm pretty confident that the issue is related to the GPIO power pin of the wifi chip being incorrectly set.
You mentioned you are using led-conf7, which is the right device tree for R29 boards, but it seems that your board is a different version/revision and requires some adjustment.
 
To do such adjustment, I definitely need the device tree or the backup of the stock android.
 
A possibility is to try other led-conf options and see if the wifi chip is at least recognized, but I don't suggest to do so because led-conf7 is vital for the stability of the R29 boards: without it, your board will probably be unable to boot at all.

BCM433x are normally good supported , do have rk322x-config and setup the right led config its help also with wifi enable signal
 

@fabiobassa@jock

 

@Socram Hello, it's definitely an rk322x. Despite the kernel is the same for rk322x and rk3288, the socs are profoundly different and so are the device trees. An image for rk322x would not boot on rk3288 and viceversa.
 
Anyway, you should run rk322x-config and use the appropriate led-conf for your board. AFAIR you should have two options: led-conf8 for h20 boards with two voltage regulators (better, looking at the board photos this should fit) and led-conf7 with r29/r2b/h20 boards with single voltage regulator (worse but more compatible).
 
You may go with led-conf8 first, see if it is stable under load. If not, go with led-conf7. Both the configs should make HDMI work

You're right! It's a RK3288. I thought it was a RK3228A because that's what the vendor advertised.
 
I realized the thing was actually replying to pings, removed the MicroSD, chrooted into the machine and created an user and enabled ssh, connected to it and sure enough:
[ 9.831684] rk3288-crypto 100a0000.cypto-controller: will run requests pump with realtime priority [ 9.831930] rk3288-crypto 100a0000.cypto-controller: Register ecb(aes) as ecb-aes-rk [ 9.832042] rk3288-crypto 100a0000.cypto-controller: Register cbc(aes) as cbc-aes-rk [ 9.832082] rk3288-crypto 100a0000.cypto-controller: Register ecb(des) as ecb-des-rk [ 9.832112] rk3288-crypto 100a0000.cypto-controller: Register cbc(des) as cbc-des-rk [ 9.832139] rk3288-crypto 100a0000.cypto-controller: Register ecb(des3_ede) as ecb-des3-ede-rk [ 9.832170] rk3288-crypto 100a0000.cypto-controller: Register cbc(des3_ede) as cbc-des3-ede-rk [ 9.832199] rk3288-crypto 100a0000.cypto-controller: Register sha1 as rk-sha1 [ 9.832232] rk3288-crypto 100a0000.cypto-controller: Register sha256 as rk-sha256 [ 9.832261] rk3288-crypto 100a0000.cypto-controller: Register md5 as rk-md5 I do see RK3288 references. Thanks for the tip!
armbian-hardware-monitor.zip
 
EDIT: No, I think this is actually a RK3229 based on the DTS. I also opened the device and, while I cannot read the specific part number because it is hidden under the heatsink, it's a plastic IC so it cannot be a RK3288 which was sold in a metal BGA package.
 
An except from the multitool dmesg log regarding the DRM:
[ 2.648953] [drm] Initialized drm 1.1.0 20060810 [ 2.656047] [drm] Rockchip DRM driver version: v1.0.1 [ 2.661464] rockchip-drm display-subsystem: devfreq is not set [ 2.668188] rockchip-drm display-subsystem: bound 20050000.vop (ops 0xb0d05b78) [ 2.676005] i2c i2c-0: of_i2c: modalias failure on /hdmi@200a0000/ports [ 2.682689] dwhdmi-rockchip 200a0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.690553] dwhdmi-rockchip 200a0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (inno_dw_hdmi_phy) [ 2.701808] rockchip-drm display-subsystem: bound 200a0000.hdmi (ops 0xb0cfe0d8) [ 2.709310] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.715950] [drm] No driver support for vblank timestamp query. [ 2.722040] rockchip-drm display-subsystem: failed to parse display resources [ 3.353464] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 3.354145] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13 [ 3.354154] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB [ 3.354161] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan [ 3.354168] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data [ 3.354174] dwhdmi-rockchip 200a0000.hdmi: picture aspect: 16:9 [ 3.354181] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture [ 3.354188] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content [ 3.354194] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601 [ 3.354202] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full [ 3.354209] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling [ 3.354216] dwhdmi-rockchip 200a0000.hdmi: video code: 16 [ 3.354223] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full [ 3.354230] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics [ 3.354236] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0 [ 3.354245] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0 [ 3.430974] Console: switching to colour frame buffer device 240x67 [ 3.598766] rockchip-drm display-subsystem: fb0: frame buffer device In the case of the latest version of Armbian:
[ 1.557514] inno-hdmi-phy 12030000.hdmi-phy: error -ENXIO: IRQ index 0 not found [ 1.558040] inno-hdmi-phy 12030000.hdmi-phy: phy_flag is: 0 [ 1.560579] rockchip-drm display-subsystem: bound 20050000.vop (ops 0xb1179c70) [ 1.560740] dwhdmi-rockchip 200a0000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 1.561045] dwhdmi-rockchip 200a0000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 1.561515] dwhdmi-rockchip 200a0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (inno_dw_hdmi_phy2) [ 1.563057] dwhdmi-rockchip 200a0000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.563492] rockchip-drm display-subsystem: bound 200a0000.hdmi (ops 0xb117d958) [ 1.564699] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0 [ 1.564912] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 1.565125] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes Seems it is unable to find the CRTC?
device-dtb-and-dts.zip multitool-dmesg.zip
 
EDIT 2: I can guarantee 100% this is a RK3228. Reading the eFuses:
root@multitool:~# cat /sys/bus/nvmem/devices/rockchip-efuse0/nvmem | od -tx1 -An 52 4b 23 82 81 f0 70 55 52 4b 58 32 32 30 33 33 00 00 00 00 0c 0e 26 05 00 04 01 00 00 78 00 00 Note bytes 0x02 and 0x03 are 0x23 0x82, which indicate a RK3228

this looking not as rk322x , i thing thats another main chip like rk328x or newer  , we see some box that boot multitool without rk322x
 

@primoitt thanks for those Infos, even if not strictly hardware related , they are usefull for building new distros
 
Could be also interesting open a specific thread related ti repositories issues and leave this for hardware specific

@primoitt thanks for those Infos, even if not strictly hardware related , they are usefull for building new distros
 
Could be also interesting open a specific thread related ti repositories issues and leave this for hardware specific

So VY 73 and Grazie, de LZ4TU  taaa ti ti taaa
*Excuse me for the offtopic but could not resist, for those not knowing Morse code and are not HAMs each CW QSO finish with TU, on morse: _  .._ meaning Thank You!
Good team here: @jock, @ilmich, @fabiobassa and so much great contributors, ofcourse the leading @Igor , Thanks again, wish you all good luck!

@suser
your avatar is a smith cart about impedence, I suppose.. Italian HAM here

This make me think that you have the right approach to problem : WHY IS NOT WORKING !!!
And not the simple " ok it will work in othe manner" but " what hell is going now"
 
This is the spirit that animated @jock @ilmich and myself when we approached to rk322x world

Unfortunately lack of documentation = trial and errors and understand code and compilation !! And again unsuccess and again trial and errors. Even actually the evil nand driver is ONLY proprietary, even if jock and ilmich actively searching for months a workaround

Welcome in the club 😅
 

I have few USB dongles working, bough for 1.5EU each, it was not a matter of money, nor WiFi desperately needed. It's was a matter of "make things working" or at least "to know why it is not working". Thanks everybody here, you are such a talents !