Maker39

Wow !!! it's magic !
I have WiFi

Wow !!! it's magic !
I have WiFi

@Maker39 it looks to me that you're running an "old" image: the kernel reports it has been compiled 21th Sep 2022, but the esp8089 driver and wifi fixes have been introduced the 3rd Oct 2022. Use a newer image or do apt update && apt upgrade.
 
The emmc in those logs looks fine to me, it is detected correctly and I don't see any error.
Upgrade and send again the URL from armbianmonitor -u

Multitool update!
 
Hello! I'm pleased to announce that multitool finally got network and SSH access, and now can be used on headless systems!
 
The latest release will retrieve an IP from the network DHCP server automatically, so you can consult your local network router to discover what IP the box got.
SSH access can be obtained logging in as root user; no password is requested.
Example with IP 192.168.1.18:
paolo@predatorg:~$ ssh root@192.168.1.18 Welcome to Multitool SSH session! root@multitool:~#  
 
Link-local access:
 
Multitool will also, by default, listen to link-local 169.254.120.120/16 address. This is useful if you have no DHCP server or have troubles retrieving the IP address.
Note that to access such private IP you need to set a network interface of your PC on the same subnet, or also use a virtual interface.
 
Here there is an example using ip assigning address 169.254.89.32/16 to virtual interface eth0:1 (address can be changed at your pleasure, interface must be the same interface you use to access the box, ie: wlan0, enp0s25, or whatever):
ip addr add 169.254.89.32/16 brd + dev eth0 label eth0:1  
or if you prefer old but good ifconfig:
ifconfig eth0:1 169.254.89.32/16  
then the multitool is accessible to 169.254.120.120:
paolo@predatorg:~$ ssh root@169.254.120.120 Welcome to Multitool SSH session! root@multitool:~#  
Of course link-local access won't work if you have multiple devices running multitool on the same network, since all of them will conflict because they have the same IP; in such case use the IP provided by DHCP.

@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

@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

@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

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 .

@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
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?

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 .

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 .

Hello guys, good news!
 
RK322x now is mainlined into armbian! This is the download page: https://www.armbian.com/rk322x-tv-box/
From now on your board will get all the benefits of being part of Armbian ecosystem, including kernel updates!
 
Support and developing images will still be provided in this forum thread as usual, so for the thread followers nothing will change
 
edit: I'm in the middle of testing the images and it seems there's something wrong with the bootloader, so don't download them yet!

Great job!
Thanks to you I finally have a working image for my MXq-4k ,
PCB silkscreen : MXQ-S-V3.0-20180126 ZN
Hw: Allwinner H3, 1G DDR3, 8G NAND, XR819
XR819 work
All 4 USB enable from armbian-config
cpufreq is working.
Because i have NAND system transfer to eMMC does not work ...
 
 

@jock Thanks for update.
Auto Detect work fine for me. And interface more understood.
Great job !

Hello, images have been updated in first page, coming with a more detailed rk322x-config script that will prevent future NAND/eMMC mistakes and provides some more info about the board.
Also mainline kernel has been pushed to 5.6 and now an Ubuntu Focal image is also proposed, albeit having a very slow desktop experience and requires the user to uninstall chrony package which is broken and prevents date and time synchronization from network.

@Alex83
I try to explain what happened.
The wifi device is attached to the SDIO bus, which is disabled in the generic device tree that is loaded at first boot, that's why the command does not work. In the next release of the images I will fix this.
 
When you called rk322x-config, you choose boards which have no support for nand, so at next reboot it has been disabled and the system was not able to boot anymore. Objectively, at the current stage the user is unaware of this important information making the selection. I'm already addressing this issue providing more info to the rk322x-config script that prevents this kind of mistakes.
You could restore the system boot using the Multitool, getting a shell, mounting the armbian partition on rknand0 and then removing the fdtfile= line from /boot/armbianEnv.txt
Anyway you could try the mxq-pro-4k box which has NAND and SSV6051 support, you should have no more surprises.
 
Unfortunately, on legacy kernel, wifi requires some kernel module juggling (ie: blacklisting and whitelisting). I would really like to fix this at root, but I only have boards with ssv6051/ssv6256 chips and the worst offenders are the realtek modules, so heading into kernel modules which I can't test is a jump in the dark.
 
About hardware acceleration, all the kernel modules are there, just the software is not compiled to use it. Video players that come with debian/ubuntu are not aware about rockchip acceleration. At this stage you need to compile things by yourself unfortunately. I will take a look to the Mediascript for RK3288 that maybe can be used for a proof of concept, but I don't know how much can be used for RK322x

Wifi rtl8703bs
root@rk322x-box:~# cat "/sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1/modalias"
sdio:c07v024CdB703
ps Here's another, it may come in handy
rtl8189etv
sdio:c07v024Cd8179
ssv6051
sdio:c07v3030d3030
 

Fine !
I tried the new Multitool and new images.
1. Multitool problem with mmcblk2 on (Iconbit XDS16 and XDS8)  blue board marked T95N-RK3229_512X4-20170803_V1.5) solved!
2. Trouble with
Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop
Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal
stop at "random: nonblocking pool is initialized"
Solved after edit device tree (for me is hk1mini ) As said @jock You can change status="disabled" into status="okay" in dwmmc@30020000
 
So far, that's all I have.
Later, I’ll probably try to heap all the information on these Tv-boxes, maybe they will need a separate dtb for them.
These boxes are common in Russia and CIS countries.  In Europe is excusive apparently

Hello guys, finally, after a huge and time consuming effort, me and @fabiobassa have a working method for installing Armbian on NAND devices!
 
The method is called steP-nand (Ste Puttane di NAND) and is available as an option in the multitool only for boxes equipped with NANDs.
 
What you need:
a fresh copy of the multitool a fresh copy of the armbian images installation instructions Everything can be found in the first page of the thread.
Enjoy!

"You can change status="disabled" into status="okay" from your HK1 device tree to activate the emmc node. "
Then recompile dtb, reboot and it should work."
Yes, it work !
Now i boot from sd and move system to eMMC.
System started and loaded succesfully .
 
ps Maybe because of these settings the image recorded by Multitool did not load?

"You can change status="disabled" into status="okay" from your HK1 device tree to activate the emmc node. "
Then recompile dtb, reboot and it should work."
Yes, it work !
Now i boot from sd and move system to eMMC.
System started and loaded succesfully .
 
ps Maybe because of these settings the image recorded by Multitool did not load?

Yes !!!   it worked
 
p.s. since with such a powerful tool I can now save and restore the android on this box I tried to flash armbian in eMMC .
Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal    fully loaded
but
Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop
Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal
stop at "random: nonblocking pool is initialized"
 

@MMarcio @nokirunner
Here we are, here there is the first version of the Multitool.
That's an image to burn on an sd card: plug it into the tvbox and it will boot allowing backup, restore, erase and image burn on the internal eMMC.
To burn armbian/libreelec images directly to internal eMMC memory, place the compressed images into images folder of the sdcard and use the relative function of the Multitool. Any feedback is welcome!
 
@Mark Khevin Rogacion I'm sorry but your box is unlucky to have a NAND chip instead of more common eMMC memory. Since there are no open drivers for rockchip nand, there are limited functionalities (like no kernel/uboot updates) and putting the rootfs on the NAND still require manual working. Me and @fabiobassa are working on a way to let armbian installation work the best, but at the moment you should stick to external sdcard.

Since the changes from 10.04.2020 and the replacement of images on rk322x-box.
Firmware replaced with new ones.
LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal 2GB
LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal 2GB
LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop 4GB
These are img from first post with Libreelec bootloader for boot without erase eMMC. Just insert a card and turn on power.
 
Google Drive https://drive.google.com/open?id=1uoQvZUUFZyCWYFtatlTSJvJSSjUuJYLm
 
26.06.2020
Because at the moment, the firmware has lost its relevance. Deleted.