Wester_Minsk

Multitool over SSH worked great!!
It took me 5 minutes to install in emmc.
Thank you very much!

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.

I switched to - Armbian 22.02 - Debian Bullseye minimal - mainline kernel 5.15.16

Everything is ok on my board.

I migrated the system to a usb3 ssd drive, and connected a usb3 hub with a 1 Gbit LAN.

On the new version of the image, the armbian-config works fine after migration.
 
Thank you so much for the new release!!!

There was a simple way, and it was in front of my nose.

This is the standard way from the official instructions of the Armbian:
 
Start the install script:
nand-sata-install
I chose:
of booting from eMMC/NAND, system to SATA/USB
 
The system migrates to a USB3 SSD
Restart and boot the system from USB3
 
now a stable start with USB3

14 hours up time on eMMC, with  Doker +HA + Pihole load. 
At the beginning there was one freeze, after which I removed the parameter "rk3318-box-emmc-hc200"  from the armbian-config. 
Then it works stably. 
This is already much better than it was, the changes are obvious. 
I will pick up a good sdcard, and start from it to eliminate the eMMC problem and continue testing. 

Logs complete
Android.log Armbian eMMC.log Armbian sdcard.log

14 hours up time on eMMC, with  Doker +HA + Pihole load. 
At the beginning there was one freeze, after which I removed the parameter "rk3318-box-emmc-hc200"  from the armbian-config. 
Then it works stably. 
This is already much better than it was, the changes are obvious. 
I will pick up a good sdcard, and start from it to eliminate the eMMC problem and continue testing. 

14 hours up time on eMMC, with  Doker +HA + Pihole load. 
At the beginning there was one freeze, after which I removed the parameter "rk3318-box-emmc-hc200"  from the armbian-config. 
Then it works stably. 
This is already much better than it was, the changes are obvious. 
I will pick up a good sdcard, and start from it to eliminate the eMMC problem and continue testing. 

https://disk.yandex.by/d/RYIADV5cMwpOmA

@Wester_Minskthanks for the firmware and photos. I had a quick look into the device tree and it looked quite standard to me: no particular hardware like Power Management ICs or other significant differences from regular tv boxes.
I will take a deeper look and check other compatibility things soon!

https://disk.yandex.by/d/RYIADV5cMwpOmA

@Wester_Minsk
 
Consider that I have plenty of 3318 faulty. Those that are faulty completely is a form of "good luck"
 
Those with intermittent fault are the worst , also because when they freeze nothing is written in logs.
 
This kind of freezing could be related to faulty emmc or/and DDR. Especially because you say that have to flash back every thing on emmc
 
One test , if you haven't already done , could be run every thing from SD. In other words erase emmc and do all the testing on SD.
if freezing doesn't occur you have your answer