fabiobassa

@Maker39
not more than yesterday, in private chat @jock and me we were saying that this 3ad is SUPER because many others users, such as you actively help people.
This is right spirit of a forum

@zero48, With people like @jock and @fabiobassa , this board couldn't win this fight
Congratulations on your success
 
I was rooting for you, but nothing could help

@Flávio Lima
hello Flavio it depends what scope you have for this box, I can say even 1gb of ram is okay
Wait if @jock has some mirror for older versions
 

@zero48
I said it:
this box WILL WORK !!!

Congrats
 

Gents, 
 
Finally got it Installed , I'm so happy !! 
 
Now I'll check whats working or not (not interested in WIFI in case of failure) .
 
I used Armbian_20.11_Rk322x-box_buster_current_5.9.10_minimal.img  ( I dont need Desktop for my purpose)
 
Thanks Very much @jock and @fabiobassa for your patience and guide .
 
Sincerely
 
 
 
 

@zero48
Apparently you have emmc and not NAND flash, so use the other instructions

The wireless is fully working with overlays=wlan-alt-wiring wlan8189-etv-al.Thanks again!!!!!!!!!
 

That solved the problem !!
Now the SDcard it is accepting the image (testing with Focal which is bigger) flawlessly
 
  
 
Thanks very much to you and @fabiobassa for the support and patience 
 
Kudos !! 
 

@Flávio Lima
 Bom Dia Flavio,
yes the forum is in english please be so kind to use that language.

Despite of this I understand a bit portoguese so for your question and as far as I know rk322x board DO NOT HAVE 4 gb ram, almost at actual time
the maximum I have seen is 2 giga
Usually shishion 5G have 2 giga of ram
 

@zero48
Your board is one on which we worked a lot, is well known and totally and well supported in armbian.
It has NAND so pay attention : you have to use stePnand for internal installation ;
it has DDR3 upvto 768 MHz so is one of my favourites for his speed
You will be very satisfied of it !!!
 
Thank you for photos, cheers
 
EDIT:
Those lovely China producers..
It should be a 3228 with one or two giga of ram. Look at what they say .. 4 GB ram......
 
Anyway you can check those infos with the efuse and with " free"  command.
 
Please read back the forum since there are many useful infos you can grab from the board with some command lines

@zero48
indeed the procedure that maker is suggesting you is correct and one of the best
And really the booting sequence of those boards allow the box to boot from internal, search if exist a trustos and uboot on the card and then boot from the card if valid things are found.
I guess android is working, or are you  trying to boot with shorten pins and/or android erased ? If yes please revert to ideal cndition of android in place and working
last question : have you sufficient skill to setup a uart converter to debug what is going on ? On that board solder a pl2303 is very easy

And please guys , when you receive support is a costless thing to just put a " like ( heart icon) " , not for vanity having as many likes is possible , but because this helps the reputations and reliability of users trying to help your efforts and also strengthens the sense of community and the purpose of a forum.
ty @Maker39
 

@zero48
I would do like this:
1. through Rufus completely format SD by disabling "Quick format"
2. Write Multitool.img.xz .
After that, in Win, the card should be seen as 2GB FAT32 with some files, such as:
/backups
/bsp
/extlinux
/images
kernel.img
LICENSE
rk322x-box.dtb
3. Insert "Multitool" SD on box and PowerON.
Should be boot and repartition FAT32 for whole space.
 
p.s. Is there Android 10 in your box? Maybe there the bootloader somehow works differently?

@zero48
 
as already @Maker39 said you don 't need nothing to start from sd but the sd itself
Mee too I always use win32disk imager so first extract the content of the xz file and burn it with win32imager

Try Rufus https://rufus.ie/
 I always keep "Rufus", "Win32 Disk Imager" and "HP USB Disk Storage Format Tool" handy for recording images.
And you no need press "magic button" for boot with Multitool .

@nokirunner

this was exactly the same question when I approached to linux study on those devices:

well . thanks to study and many people that explained to me now I know that linux IS NOT android and the opposite is also true, and YES they violate the GPL but if you are able to go in China to yell on this, well buy a ticket for me too.
In case of wifi they don't violate any since is proprietary driver and nowhere is written that they must open the code to every one

the desktop subsystem is perfect on Android with all jingles and bells, now you take the SAME kernel they use, the same modules and libraries they have in rootfs  and NO!!!  it doesn't work at the same manner under linux,  and since we must adapt something to linux phylosophy and we HAVEN'T documentation sometimes at all, sometimes half-half , I truly believe that is quite  a  miracle we have a true linux platform on those devices

sadly to admit it but this is the truth

@nokirunner

this was exactly the same question when I approached to linux study on those devices:

well . thanks to study and many people that explained to me now I know that linux IS NOT android and the opposite is also true, and YES they violate the GPL but if you are able to go in China to yell on this, well buy a ticket for me too.
In case of wifi they don't violate any since is proprietary driver and nowhere is written that they must open the code to every one

the desktop subsystem is perfect on Android with all jingles and bells, now you take the SAME kernel they use, the same modules and libraries they have in rootfs  and NO!!!  it doesn't work at the same manner under linux,  and since we must adapt something to linux phylosophy and we HAVEN'T documentation sometimes at all, sometimes half-half , I truly believe that is quite  a  miracle we have a true linux platform on those devices

sadly to admit it but this is the truth

Hi. This is my experience with H96mini (CPU 3228A without sd slot).
 
Download and compile rkdeveloptool (https://github.com/rockchip-linux/rkdeveloptool)
Download rk322x_loader.bin and your favorite OS image from forum (decompress image from .xz format to .img)
 
While continuing to press the button inside AV port(use toothstick), then connect power cable to device.  Release the button insiede AV port, then connect the TV box to the PC using USB port number 1, the closest one to the edge. 
Device will boot in mask rom mode.
Run following commands:
./rkdeveloptool db rk322x_loader.bin
./rkdeveloptool wl 0x0 your_image_os.img
./rkdeveloptool rd
 
Don't poweroff device.
Connect devide to monitor or TV using HDMI.
 
Wait while device booting.
 
Good luck!

LOL  I didn't associate, stupid me, I'm distracted.
 
 

i will try, but i don't know if i will succeed, the last time i compiled a kernel, those rare times i did it was over ten years ago

@jock @fabiobassa - to explain the difference between the addresses by the maskrom vs loader mode makes sense ... i think i did this hybrid setup with original initial boot blocks and mainline u-boot back then because i was thinking that this is the only way to get it working with the existing trust image ... where is it actually defined if trust images will be used or not - is it somewhere fused in the hw or is it just a matter of the initial boot blocks? if its just a matter of the boot blocks, then i should even be able to replace the entire boot with something adjusted self compiled maybe ... another reason i did it that way was that shortly before i did something similar for a rk3318 box for which there was no atf i could build myself (rk3328 one did not work) so i had to keep the original initial boot blocks there ...
 
best wishes - hexdump

Never heard about rockchip 3028, it is quite sure you have a rk3328, or maybe the little rk3318 brother.
To be sure, you should read what's printed on the soc itself. There is also this table: https://forum.xda-developers.com/showpost.php?p=56219933&postcount=2 that matches the USB vendor/device ids with the soc. I don't know if it is verified.
 
Once you got the SoC, you will need the usbplug binary for both the db and ul commands, but this will flash another rockchip proprietary loader, which I don't know it is what you want...
 
edit: I just read about @hexdump instructions, that's a good recipe on how to compile and install mainline u-boot as a bootloader, but I'm understand it correctly, there is some chain-loading between proprietary u-boot and mainline u-boot. You can customize the boot options and avoid being slave of the rockchip u-boot binaries, but requires manual intervention. I would point out some clarifications: as @fabiobassa once told me, the 0x2000 offset when using rl/wl commands of rkdeveloptool is due to maskrom or loader mode: in maskrom mode there is no offset, so you can write the entire eMMC/NAND. In loader mode the first 0x2000 sectors are hidden, hence the offset.
 

you might have a look at this, but you are on your own then (no warranties or support from my side) - for me it worked to get my h96max h2 which cannot boot from sd card too working by installing an adjusted u-boot - https://github.com/hexdump0815/u-boot-misc/blob/master/readme.rk3328-no-sd-boot

@victroniko
 
Ty for all tests, combinations, ideas you are experimenting/experiencing.
 
People such as you and other great persons ( and this post is full of clever minds) are ALWAYS welcome.
 
Cheers

Good news, expecially for @nokirunner and @DaviMesquita
 
Finally we managed to make the ssv6x5x driver work on the ssv6256p chipset and it turns out the it is also working pretty well. I removed most of the logging messages it was spamming on the dmesg log, now it is much more silent and it is ok this way. Teaming with @fabiobassa we optimized performances quite a bit, so expect ~60 Mbit/s at least on optimal setups. It works on both 2.4Ghz and 5Ghz bands.
 
The driver will be included in the armbian images soon, but in the meantime anyone can test it.
Download ssv6x5x.koand put it into /lib/modules/$(uname -r)/kernel/drivers/net/wireless Download ssv6x5x-wifi.cfgand put it into /lib/firmware Download ssv6x5x-sw.bin and put it into /lib/firmware Run depmod -a Add blacklist ssv6051 in /etc/modprobe.d/blacklist-rk322x-box.conf (ssv6051 and ssv6x5x kernel modules clashes, we need to blacklist ssv6051 for the other to work) Reboot!  
Any testing report is appreciated!
 

@DaviMesquita
For those boxes is really a jungle !!
Those Chinese tend to grab the first avaible cheap chip and put inside so a big variety of possibilities.
@Jock contacted me and maybe now is the moment to " put hands " in this sluttish driver.
 
@Ztrawberry the driver for ssv6051 doesn't suit sv 6x5x this is the problem and that project for a universal image is a nice idea but me and jock and other clever programmers  ( the same man  that bring libreelec to life on those boards @knaerzche ) own so many different boards that  has been reached great maturity  on rk 322x . Mostly bugs are well known ( ssv6x5x among others) and still working on them
Of course support , ideas and suggestions are highly appreciated

@paulml

your board is a 3228b with 1 giga ram and nand 
1) once more , and unfortunately at the moment , your board has a nand storage
2) as long as you run by sd card and SKIP the approach to flash internal storage ( since it is nand) everything will be ok
3) simply don't touch internal android installation and run from sd, for the moment

tool for manage even nand is on the way :-)