@jockNow, I've finally solved this problem. Successfully flashed the latest version of armbian, https://github.com/armbian/community/releases/download/26.2.0-trunk.151/Armbian_community_26.2.0-trunk.151_Rk3318-box_noble_current_6.12.63_gnome_ desktop.img.xz Next, I will share my problem-solving journey. I found that I couldn't enter maskrom/loader mode anyway, and when I accidentally inserted the USB flash drive into the multitool.img into the TV box and powered it directly on, I found that it actually started the system directly in the USB flash drive. So I guess that it may have changed the boot order after flashing the loader.bin before, and the armbian system I flashed in before it continued to toss before it could be configured, probably because the system files of the root partition were corrupted, causing it to not boot normally. Therefore, I simply tried to flash the firmware of the rk3188-box in the official community directly into the USB flash drive, because after these images are flashed into the USB flash drive, there is only the root partition, that is, the system. And there is no boot partition. I guess the boot partition may have been written somewhere else, and I don't need to worry about it anymore. So, I plugged the USB flash drive into the latest rk3318 firmware into the box and waited for a few minutes after powering on it directly and starting it, it obtained the IP address assigned by my router DHCP, I was so excited, I quickly connected to the rk3318-box through SSH, and made the preliminary configuration. Quickly enter the command armbian-install and select item 2, and immediately write the system on the USB flash drive to emmc. After the writing is completed, turn it off, unplug the USB flash drive, power on, wait for a few minutes, and the startup is successful. It means that I have successfully flashed the phone this time. Thank you very much for your help. @jockand @fabiobassa, You're passionate and highly skilled.

@jockLater, I tried to install rkdeveloptool on another Linux server and flashed the loader.bin first and then the image by entering the command. Finally successfully flashed. But tragedy is about to be born, when the flash is successful, I did not SSH to connect to the new armbian and configure the relevant configuration immediately, but shut down and prepare to re-enter maskrom mode to flash the desktop version of the image again, the result is that this time I can no longer enter maskrom mode, no matter how long I press the reset button to plug in USB 2.0 OTG or press it, the box will no longer enter maskrom mode. Along with this, it could not start the Armbian system that was flashed before. I began to wonder if it was painted into bricks, but this board shouldn't be so fragile.

I found the reason. (Different function of Pin 100) cm5-io: PCIe_PWR_EN rpi-cm4-io: nEXTRST used for USB hub reset With rpi-cm4-io and no pcie device, linux sets PCIe_PWR_EN=0 (turn off pcie) But rpi-cm4-io thinks that nEXTRST=0 (always reset usb hub) The temporary solution is: For the pause of compile, please turn on kernel config When kernel config appears, sudo vi ./cache/sources/linux-kernel-worktree/6.1__rk35xx__arm64/arch/arm64/boot/dts/rockchip/rk3576-armsom-cm5-rpi-cm4-io.dts Add the following fix in order to always turn on pcie vcc3v3_pcie0: vcc3v3-pcie0 { ... regulator-boot-on; regulator-always-on; enable-active-high; ... }; I do not know how the .dts is generated, so the patch can be made by an expert of Armbian.

To be honest I don't know how to do this and even more I am not sure in correctness of of my code in term of conventions. I mean that for example I add #define-s with names ES8388_xxx to header file ES8228 and so on.

URGENT: Kernel update already applied, bootloader points to 6.12.58! Current state: - Running: 6.12.44 - Boot configured for: 6.12.58 (symlinks updated) - usr-merge still broken (duplicate files in /bin, /sbin) Questions: 1. Should I revert boot symlinks to 6.12.44 immediately? 2. ODROID HC4 specific: Which file actually boots (Image vs vmlinuz)? 3. Will 6.12.58 boot with broken usr-merge? 4. Emergency procedure if forced to reboot? NOTE: I'm NOT taking any action until getting community advice.