Changing the ranges to 0xf1000000 in the devicetree fixed it. The Kernel is now trying to boot.by kbch - Debian
Hello I'm trying to run Mainline Kernel on the Western Digital EX2 NAS (Armada 370). But if I try to boot the built Kernel it stops without any Kernel output. I've used the Devicetree armada-370-netgear-rn102.dts which should at least get it booting till the missing rootfs message. Serial Port should be correct, the vendor bootargs has ttyS0 and I use serial0 in the devicetree.by kbch - Debian
Got it now working. Used the uboot from http://www.readynas.com/download/beta/marvell/USB_Recovery/u-boot.bin and loaded it with the same kwboot command. Thanks for your help bodhi and koen! Just out of curiosity, I also found other threads with this issue that it hangs at the ethernet message. Did I do something wrong when changing my envs or is this an issue of this uboot build that it sometby kbch - uBoot
hmm, this is weird. I got it now working with the UART of the Raspberry Pi + kwboot from the Debian u-boot-tools package. But it looks like it afterwards boots again the old Bootloader from NAND or maybe it loads the envs from NAND. At least its also stuck at the Ethernet message again. pi@devtable:~ $ kwboot -t -B 115200 /dev/ttyS0 -b mtd0 -p Sending boot message. Please reboot the target.by kbch - uBoot
I have now built kwboot from http://ftp.denx.de/pub/u-boot/u-boot-2021.04.tar.bz2 and tried to boot mtd0. But it fails with a Protocol error. Not sure if my (presumably fake) pl2303 is causing issues or uboot tools is too new. Will try to use the supplied Raspberry Pi kwboot binary with Raspberry Pi UART tomorrow. ➜ tools sudo ./kwboot -t -B 9600 /dev/ttyUSB0 -b ~/drive/readynas/mtd0 -by kbch - uBoot
Hi bodhi It keeps stuck on this message no matter if Ethernet is connected or not. Also doesn't matter if other peripheral stuff like USB Sticks are connected.by kbch - uBoot
I'm not exactly sure how this happened. I edited and added some env's on my Readynas Duo V2 to support loading an initramfs from USB. Since then it is stuck after an Ethernet message and I can't enter UBoot anymore. It also doesn't go further with booting after this Ethernet message. Is there something I could try or do I now have a big paper weight? :) __ __by kbch - uBoot