fabiobassa

@Benedito Portela
 
https://opensource.rock-chips.com/wiki_Boot_option
 
Again ...here It Is
 
Post scriptum:
 Also we started from few infos captured here and there on the internet to assembly the whole picture and , when It didn t work , It was a hard, boring, tired work of trials and errors.
 
AGAIN : we dont own any of the new boards and NOBODY and repeat NOBODY even imagined to buy one for us to study.
 
So you and others are very welcome to study as we did by trials and errors and report here any success
 
Thank you for your apport 

@n3o  You bricked your own device and neglected to create a backup before doing so?  At this point I would think you are just trolling.  I have given up on trying to convince you that your time is better spent elswhere.   I'll let the other forum members decide for themselves if helping you is worth their time. 

Not until a sample happens to arrive in my hands

Yes, this is exactly the way I suggest to take confidence with the system: erase the internal flash to zero (does not matter if NAND or eMMC) to remove any trace of Android; then use Armbian from sdcard to bring up the system, experiment with rk322x-config to setup the board correctly so, in case of mistake, just plug the sdcard in a PC and revert the error; install packages, services, reinstall armbian from scratch with another kernel or rootfs (Debian bullseye, bookworm, Ubuntu Jammy LTS, latest Ubuntu, etc...) and do all your own experiments on the sdcard.
 
When finally you notice that the base system is stable with the proper led-conf and you're happy with the software setup, transfer it to internal flash or install armbian on internal flash with multitool.
 
Also, IMHO, boards with NAND have much better use with external sdcard than internal flash, since NAND are supported only with ancient 4.4 kernel and they still are problematic. Keep them erased and live easier with external sdcard.
 

fabiobassa, this link: 
 
https://drive.google.com/file/d/1_R6MzPGM2bzGdjuuU5m5_V8yAnAF0Suj/view?usp=drive_link
 
Thank you!

like i sad befor led are a old word it change some more
 
jock explain :
https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/?do=findComment&comment=163046
 
 
 
 
what do you mean recognize wifi ? complete empty SDIO device or a wifi with unknow id like 024c:D724 ( RTL8723DS , because i solder it myself  and no one else has this chip inside a rk322x box, so its not recognice automaticly )
Is wifi another problem ?  i thing that HDMI was your problem ?
 
 

Hi @n3o, are you using Windows? Linux ? OpenBSD? binary or compiled rkflashtool?
This is because
* on Linux maybe you don't have the right USB permission. You can switch to the super user account (super easy), or write an udev rule that chmod the USB node(easy if you know what are you doing)
* my rkflashtool uses libusb which on Windows needs the generic USB driver called WinUsb. With Windows 7 you need to right-click and install this file https://raw.githubusercontent.com/ilmich/rkflashtool/master/rockwinusb.inf. With Windows > 7 there is no need to install a driver, but you need to associate the unknown device with the USB generic driver WinUsb (I'm not a Windows user so try starting reading this link https://github.com/libusb/libusb/wiki/Windows#user-content-How_to_use_libusb_on_Windows)
* there is a bug on Windows (fixed with the latest alpha version) with multiple USB devices connected. Try, if you can, to have only the box connected with USB.
 
About your experiments, you wrote a lot, but I'm sorry, I'm too lazy to read.
So if I can give you some advice, format the internal storage and forget it. Write the Armbian version you like on the SD card and stop.
This is because in addition to having a few problems, sd cards with 64/128GB are cheap and for Linux use are better than the 'little' 8 GB of internal storage that you often find in our boxes.
 
Cheers
Michele
 
edit: rkflashtool is an external tool made with love by volunteers. Obviously, there is also the contribution of @jock and @fabiobassa, but for any problem with the tool, I ask you the courtesy of opening an issue here https://github.com/ilmich/rkflashtool/issues

@n3o  The members trying to help you are highly experienced. The important point here is for you not to treat their specific instructions as merely "suggestions" after which you go off and do your own thing.   That is where the frustration lies. 
 
Based on the energy other users and you have spent on this, I would just buy some other TV box or SBC that is already known to run Armbian without any issues instead of trying to resurrect an old tired piece of hardware.   Unless you are really short on cash,  this is what I would do.  However, if you really are so short on cash that you cannot afford another $20USD on something else, then I believe your priorities are all wrong.
 
I have an H20 RK3228A tv box that is in transit that has some documented booting issues with Armbian.  In a way, I am happy to see how this whole episode has progressed.  I'm happy because now I know what NOT to do.

dear friends
i remark that we continue to give help to someone that is not willing to listen and perhaps THIS IS FRUSTRATING and not the fact that the box is not booting

After discovered that IF ONLY HE had followed all the instructions that very kindly the users of this 3ad suggested instead of trying other magic combinations, and after we  already said thet we need uart logs and so now I  would like remember  we said to him to stay on legacy kenel that is 4.4.xxx

And guess !!

He flahsed Armbian_22.11.1_Rk322x-box_jammy_current_5.15.80_xfce_desktop.img.xz
in other words a 5.15.80 kernel

Do we need other words?

 

I had to ask my wife if I should answer in sarcastic, honest  and friendly or funny , she said be friendly , but I can not resist a little joke to start the day .
 
/joke on , Yes when you wait 28h 73m and 98s you will have a box that do all automatic and have the power of a i9 13990KH /joke off
 
friendly: you know what you are doing here, that will still be at 11% because that is the part of text that is display, and this page it like every other software the licenses page.
you know that you are in a DOS box like Linux console, you have to use keyboard like in good old times and scroll down with arrow keys and hit TAB to witch cursor location and hit SPACE or ENTER
 
If the keyboard does not work, please try another one and leave it plugged in right from the start of the box (there are still keyboards that do not work well under linux even though there is a basic driver for generic keyboards).
 
I don't know if flashing TV boxes is for you if you already have problems with a license text, I understand that you have already flashed the SD card correctly, but this is not windows 11 which automates everything and gets you through the setup agent with mouse and keyboard.
 
Please have in mind following :
 
We think that people should understand that this is all at their own risk and that they need to understand something about what they are about to do like uart adapter or working with ssh or console.

@n3o
Yes I know you want a box that will boot Armbian only with insert SD card and you are fine, now we have some difficulties and you try to read all that can help and try to do things by yourself while waiting.

You try to do the right steps but as last time please be more patient.

Yes we now know that you have some exp in software but not linux and not this box. Yes we understand that you try to understand every step and try to be a good help but please dont mix topic.
Not every box is the same, not every chip is the same, so not all pictures are like your box.
 
 
Jock want the log files, not picture of the boot from mutitool and/or log file of trying direct flash armbian on sd card and then boot.

We can not support Android or anything that comes from Android.

Yes we are very, very short in describing what we expect in every single step we want from everyone who has problem and ask for help.
But here are so many who just post not working and thats it or people who dont read first topic.
And also we are write so often to try to help and we think that many have already followed that our topic is Armbian on this box or dont understand that this all is also our free time and hobby. We think that people should understand that this is all at their own risk and that they need to understand something about what they are about to do like uart adapter or working with ssh or console.
 

DISCLAIMER
 
We don't own , have studied , have even seen ANY of the new mxq_r2b_lp3_v2.62_220225 boards

We don't know what is going on those, no further help, infos, tips avaible until we get one of

                                                                                                                                                  PLEASE STOP

asking why they don't work because       WE SIMPLY DON'T KNOW

Any of you can still donate one sample for further investigations
 
Thanks for understanding it !!!!
 

@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