fabiobassa

@wslab wrong thread, please refer to the first page of the correct thread, everything is written in there: https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/
 

witch version do you want to install to nand ?  newer Kernel can not work with nand there are many problems
do you clean the nand befor flash armbian ?
 
i got this screen every time after rk322x-config set in ENv.txt the parameter nand or nand-emmc  , i have to remove it that only standart setting are load
 

@jock & @fabiobassa, thanks for pointing out that my device was nand, I somehow mistook it for emmc. After struggling for long time I followed the unbrick guide and I was able to recover the device by flash it with the android using Android Tool. I got a new SD card, loaded it with multitool, however there was a slight hiccup in backing up the flash on rknand as the progress bar in multitool was stuck at 0% for a very long time, so I decide to skip the backup and used focal image with legacy kernel and my box is now running armbian. Thanks for helping out

@art3mis_17 your board is ddr3 and nand storage NOT EMMC
 
Is suggested go find a working sd adapter because you need stePnand method by multitool
 
As alternate method you can try to flash android image on It.
 
You can device device for sure but need some tools as a good sd
 
 

@TU-Student the reason why we often write .. read the first post .. is because someone has already wasted time and health trying to make everything work.
The reason why some boxes do not boot from the sd card is because there is an old bootloader or one that does not activate the sd controller at the boot stage (often vendor's choice).
So if you are unlucky, and multitool/armbian doesn't boot, the safest way is to delete the internal memory because in this mode (maskrom) the soc activates the sd card and starts the OS from there (99.9999999% of the time)
If you need a backup (of a system that for me is unusable) you can use the USB OTG cable method (with tools like rkdeveloptool or my fork of rkflashtool)
 
@fangis strange, the 6051p I think is the best supported chip. what's your problem?!

Hi all,
 
I'm not writing to ask for help, but only to share my experience, and to thank @jock for his work in allowing us to use linux with these boxes.
My board is an android tv with soc rk3229/NAND/DDR3/Wifi SSV6051p which I'm using as a network appliance (pihole - simple nas - network web server).
 
I followed the instructions in the first post and understood that the NAND is not supported, I preferred to empty it to avoid old bootloader problems and installed armbian bookworm on the SD card.
The rest is linux... I installed the software I needed and now the box provides services for my home network without any problems (and I reused hardware that otherwise would have gone in the trash).
Thanks again @jock and of course the armbian community
 
Cheers
Michele

It's no secret indeed, but the armbian image has been engineered NOT to work that way on purpose because I did not wanted anything to do with existing old/buggy/limited bootloaders, miniloaders, trusts or whatever...
 
 

@fabiobassa I agree.
 
I think back some decade ago, when the tv boxes have appeared,
then you could buy some box that actually matched the description. they often also had that cool usb drive appearance.
But then now they are really popular, especially some models. here I think the
most famous is that mxq pro box. So now when you buy it it's a real lottery, 
it can be anything. especially because now the sellers want to advertise a 64 bit cpu and sell something worse.
I was trying to boot linux for rk33xx and failing, only understood what was going on when I installed a terminal emulator
and then saw user rk322x.
 

@fangis
 
I have a tx9 with allwinner cpu
 
That is the reason i CONTINUE to claim that commercial names are fake.
 
It would be so easy to put a male-male USB cable and look what PID and VID Is coming out

Wow ! Can I have one ? ?
 
here I tested a sdcard image on my parents mxq pro box, and for basic tasks it's fine.
Chromium basic browsing
libreoffice
etc!
And of course all the command-line programs and servers will work fine too.
From what I read tx9 should have an amlogic cpu, so no wonder why some of them aren't booting ?
 

@art3mis_17
@fabiobassa is totally right, you will need a working sd adapter because you have a NAND chip and not an eMMC chip; I just add a quick note: you must use the image with legacy kernel if you want to install to NAND. Refer to the first page for detailed instructions.

@ojogoperdi

I am SURE you read the whole 3ad ( did you, isn't it ??? ) and I am SURE you and your team realized that multitool is based upon LEGACY kernel that is the MOST COMPATIBLE ever kernel tha t boots quite every box

This said , I am also sure you and your team realized that saying TX9 box is a little bit as saying "water"..
Sparkling ? Flat ? Cold? Warm ? Salty? With sugar ?
TX9 means NOTHING is just a commercial brand !!!!

 It seems it is emmc from what you wrote and emmc are the easiest to boot since they don't mess with nand and FTL  . To be sure it always boots from external sd is enough to erase the flash and it will boot form the stuff on the sd. I believe you already read this:

https://opensource.rock-chips.com/wiki_Boot_option

DDR2 ? DDR3? the ram is 1T or 2T ??

The only way to anser to a failing boot is attach a UART to the box

I don't personally know this box so I cannot point you where rxd txd are on it, if present or just hiddend pads but I guess in your university you own an oscilloscope to further investigate where serial signals are

About new kernels they should boot quite smoothly even from SD since the early stages of booting (  idbloader and trust or optee in his opensource version should be already in the right places) but missing uart log it is difficult to give you an answer

As last resource we wait for a @jock 's answer regarding this behaviour but without serial log is a bit a nightmare

Regards

@mcs
 
Yes follow the link on 1st post
This board Is very powerfull

@mcs
 
You have nand and ddr3
 
Must use miltitool and stepNand with LEGACY image

But RTL8723as is not 8723bs , you should not mix them . 
 
8723as has definitive a diffirent firmware than bs https://kernel.googlesource.com/pub/scm/linux/kernel/git/jes/linux/+/rtl8xxxu-8188eu/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h
 
many of the RTL 8723xx are part of Kernel 5 , it should be detect by linux automaticly with the right firmware/driver combination
 
have you check the chip by open the box ? maybe its a 8723ds (bs and ds have same format and pinout ) ,8723as has a diffirent board format so its very unusal that this board have another print extra for this 8723as format
 
 
 
 

@remlei OS agent for ARM 32 and supervised select Pi 3 (not 64 bit version) and also need patching the boot parameters for getting the install working OK by faking GRUB settings.

I successfully installed supervised install of HA using the images here https://users.armbian.com/jock/rk322x/armbian/stable/
 
what I did usually after armbian is installed is perform apt update and upgrade. after that I follow the most generic instruction how to install supervised install of HA, the only thing you need to watch out is install the right architecture for the os_agent.
 
after that its just a matter of how to fix that unsupported install to supported.
 
also a fair warning, do not install esphome on this box, the ram alone will make this box slow to crawl or worst crash the entire thing.

@guitoscan
 
Welcome in the club 🙃 
rk322x are often " assembled" with the first avaible piece of chip laying around in producer factory.
 
We have spent now more than 3 years reading of rkdevelootools android tools factory tools and so on and yet no clue with some boards we dont own

@guitoscan
 
Welcome in the club 🙃 
rk322x are often " assembled" with the first avaible piece of chip laying around in producer factory.
 
We have spent now more than 3 years reading of rkdevelootools android tools factory tools and so on and yet no clue with some boards we dont own

It is widely known that often they reuse those chips which are not up to the specs. They pick parts from the trash and assemble the tvboxes.
 
Sure you are not the only one, but helping solve the problem without the board in my lab for tests is difficult anyway.

Let's look into the crystal ball, I see something, it could be that something is not right here and someone has problems with a rk322x box. hope you understand this little fun, it would be of course especially with such a time pressure of only a week surprising if we could really solve your problem with such a crystal ball, so let's start here. Describe your box in more detail, which multitool which problem from which point, why this solution not something else and much much more ....

@spinning banner Hello!
Unfortunately R29 boards seem to have a widely well-known issue with HDMI output, which is not working for some unknown reason.
Some research has already been done in the past on device trees, inspecting photos and logs, but still the problem is unknown, as long as I don't have such a board in my lab to really study where the problems are.
 
The S9012P wifi chip also is a no-name chip, as long as I remember it is a chinese chip with no known drivers that "emulates" a realtek chip (not a broadcom one, like those which AP6xxx are based upon), but I can be wrong.
 @RaptorSDS did some research on that chip, but as far as I know, there is no solution because there is no driver for that (see https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/page/57/#comment-156548)
 
R29 is a quite weird board actually; despite being very similar to others, has some compatibility issues all-around and it does not surprise me the multitool has troubles with emmc, although it should have none.
From the android dmesg I see on android the eMMC runs at 31.25 MHz; Multitool runs it at standard 50 MHz, and that may be the cause of the flash storage issues on multitool.
The reason could be a  very poor quality board or eMMC,  because ALL the boards with eMMC I have ever seen runs the eMMC at 50Mhz perfectly fine and I never had to downclock the eMMC frequency to solve an issue like that.
 
 

@Khalid Pro
 
hello man, are you aware of some terms such as " please", "thank you" and so going on?

Any way we don t talk of roms here,  google is the best friend in these cases

@primoitt perhaps you should consult first page on "Multimedia" paragraph.
The way to go on mainline kernel is, as suggested by @fabiobassa, use ffmpeg, but AFAIK you still have to patch it manually with some libreelec patches to let it work.

Thank You , ok switching things by adding a part of it