Quotebodhi So if the OpenWrt baseline MVEBU kernel enables CONFIG_DEBUG_UART_xxx then, It does, this is the default config for all mvebu targets: ~/openwrt $ grep 'EARLY_PRINTK\|DEBUG_UART' target/linux/mvebu/config-5.10 CONFIG_DEBUG_UART_8250=y CONFIG_DEBUG_UART_8250_SHIFT=2 CONFIG_DEBUG_UART_PHYS=0xd0012000 CONFIG_DEBUG_UART_VIRT=0xfec12000 CONFIG_EARLY_PRINTK=y and I cby Mijzelf - Debian
bodhi Wrote: ------------------------------------------------------- > I would look at the DTS for these 2 boxes Well, that is a problem. There are none. AFAIK the stock firmware doesn't use fdt, and GPL sources are not available. The KD22 thread on the OpenWrt forum concluded in: 'the Mirabox uImage (+dts) works'. bodhi Wrote: ----------------------------------------by Mijzelf - Debian
@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-bootby Mijzelf - Debian