@bohdi I'm trying to fill some gaps. When trying to boot an OpenWrt Mirabox uImage on my Shuttle Omninas KS10 (Armada 370), it stopped at 'Starting Kernel...'. The reason to try that image, is that it is confirmed to work on the Shuttle KD22, which seems to be a dual disk version of the KS10.
I was pointed to this thread, and indeed I could boot the box using your 'old u-boot compatible' kernel, in combination with the Mirabox dtb file. (Didn't try other dtb's)
Now the question is, why does the KD22 (bootlog) boot the OpenWrt Mirabox uImage, and doesn't the KS10? The stock bootlogs (KD22 and KS10) show they share the same u-boot.
Further, what does CONFIG_DEBUG_UART_PHYS and CONFIG_DEBUG_UART_VIRT actually mean? Google isn't helpful. Is it the hardware address of the UART? If yes, is it u-boot's task to configure it to use that address? Any idea why it changed?
I was pointed to this thread, and indeed I could boot the box using your 'old u-boot compatible' kernel, in combination with the Mirabox dtb file. (Didn't try other dtb's)
Now the question is, why does the KD22 (bootlog) boot the OpenWrt Mirabox uImage, and doesn't the KS10? The stock bootlogs (KD22 and KS10) show they share the same u-boot.
Further, what does CONFIG_DEBUG_UART_PHYS and CONFIG_DEBUG_UART_VIRT actually mean? Google isn't helpful. Is it the hardware address of the UART? If yes, is it u-boot's task to configure it to use that address? Any idea why it changed?