We can update eMMC storage content automaticity, we need prepare special removable disk preparation

• write OOWOW system image to removable device
• 

BOARD.*.emmc.img.zst put into root on 2n SD partition with label dump

Stored into rescue/config/autoinstall on 1st SD partition with label rescue

/config/autoinstall

BOARD.image_name[.BYTES-bytes].img.[zst|gz] [-sBYTES] [-r]
 
# BOARD         board name [ VIM1 | VIM2 | VIM3 | VIM3L |  Edge | Edge2 | VIM1S | VIM4 ]
# .BYTES-bytes   write size limitation tag
# -sBYTES       write size limitation parameter
# -r            resize fs parameter

/config/autoinstall

VIM3.hg_1.0.emmc.img.zst

/config/autoinstall

VIM3.hg_1.0.emmc.img.zst -s15634268160

/config/autoinstall

VIM3.hg_1.0.emmc.img.zst -s15634268160 -r 

/config/autoinstall

VIM3.hg_1.0.15634268160-bytes.emmc.img.zst -r 

edit-and-save-auto-install-config

~$ echo VIM3.hg_1.0.emmc.img.zst -s15634268160 > /config/autoinstall
~$ krescue.configs -s

print-auto-intall-config

~$ krescue.configs -p | grep autoinstall
config_autoinstall="VIM3.hg_1.0.emmc.img.zst -s15634268160"

display-auto-intall-config

~$ cat /config/autoinstall
VIM3.hg_1.0.emmc.img.zst -s15634268160

disable-autoinstall

~$ rm /config/autoinstall && krescue.config -s 

can write only 11100000000 bytes for example

check.sh

tail -c+11100000000 VIM3.hg_1.0.emmc.img | hexdump -C

resiez_root_fs.sh

root@localhost:~# df /
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/rootfs     14779408 5847484   8741216  41% /
 
root@localhost:~# resize2fs /dev/rootfs 
resize2fs 1.45.5 (07-Jan-2020)
Filesystem at /dev/rootfs is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 2
The filesystem on /dev/rootfs is now 7587840 (4k) blocks long.
 
root@localhost:~# df /
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/rootfs     29808700 5848092  23618452  20% /