Hello, both the versions you used share exactly the same kernel, so it is unclear to me the reason only the Jammy image boots. Actually, I don't understand why you did not use the multitool to install the armbian image and doing maintenance, but however... You can actually edit /boot/armbianEnv.txt and set verbosity=7 to have more kernel logging and perhaps something will pop up. Hint: dmesg log is basic stuff to do debugging, if you can provide it, it could be very useful.

So it just boots directly to oowow. There is a menu item for shutdown or reboot. Reboot tells you to remove any sdcards beforehand. So I didn't. And the sdcard booted. It has installed, and reboot works. I installed to emmc and nvme. So far so good. Tried the ts1040 screen once. It might ve not been plugged correctly. Dead computer. I need to try the other direction. Copper down.

I guess the older bootloaders does not work at all with eMCP chip, if I remember correctly you need at least ddrbin v1.09 when you have an eMCP. It could be that your board came with an even newer ddrbin or something a bit customized. I guess you should ask the vendor for the original firmware and install it again to solve the issue if the command rate switching did not change anything.

Hello, thank you! I tried changing this bit in multitool-1.11 but the result is the same. I could not locate the bit in the older bootloader, the one that ran one step further. The bootloader is RK322XMiniLoaderAll_V2.47_MarcosTvBox.bin mentioned here in the last message:

Reverified the sdcard image. The board boots directly into oowow. I dont see an obvious way to tell it to boot from sdcard. Holding the function button on power up does nothing.