Linux/ARM – DreamPlug to 3.14-rc1
Just updated the DreamPlug to Kernel 3.14-rc1, and everything seems to work OK… Still getting a few mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0000 pio=0 messages at boot time, but none after the system has booted…
Fedora release 18 (Spherical Cow) Kernel 3.14.0-rc1 on an armv5tel (ttyS0) # uname -a Linux rgdreamplug 3.14.0-rc1 #1 PREEMPT Mon Feb 3 10:02:34 GMT 2014 armv5tel armv5tel armv5tel GNU/Linux
It is a shame that this device is a bit ‘old’ now, as it is the only ARM system I have that can use the standard kernel.org source tree… The others have their own ‘forked’ kernel source trees on GitHub.. Hopefully that will change over time..
Robert Gadsdon. February 3, 2014
Are you running a DTB kernel?
Do you have a Dreamplug revision with SD8787 that uses mwifiex?
I’m trying to track down an issue where the SD8787 seems to be losing interrupts, and it seems like on a DTB kernel, the “unhandled interrupt” messages from mvsdio are for interrupts that should have gone to mwifiex.
I’m using the ‘appended’ kernel image:
# cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-dreamplug.dtb > arch/arm/boot/zImage_w_dtb
# mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n “linux-dreamplug” -d arch/arm/boot/zImage_w_dtb ../uImage314rc1
Tried to update the old UBoot to a newer version, but repeated attempts to use the JTAG connection failed, with IO errors, and I didn’t want to run the risk of bricking it with a flash update..
I haven’t used the wifi hardware for some time now, so don’t have any info on the problem you mentioned..
RG.
Dear sir,
I’m trying to compile a kernel for Dreamplug under Archlinux, as it seems the usb-drivers and internal SD-card drivers are not built in, at least I can’t get the stock Archlinux-kernel to boot. Is there a place I can get your .config for the kernel, so I can have a look what devices you have built in?
Thanks
I have a working 3.12 .config for the Dreamplug at http://pastebin.com/Vr3Y7Gg3
Hope that is useful..
RG.
Thanks – I also found the .config of the 3.12.6 of Archlinux, but still no luck – now it breaks when mounting the rootfs and proposes the mtdblocks as partitions, but that’s not useful, neither 🙁 Did you compile and boot on a Dreamplug from 3.15, too?
Arch Linux has linux-kirkwood-dt and linux-kirkwood in the repositories; both have been updated to 3.15. The -dt kernel requires a U-Boot upgrade from the stock firmware.
Is there something missing in these as well?
I have put my .config for a working DreamPlug 3.15-rc1 at http://pastebin.com/hn8RWYWy
I did try to update the U-Boot, but the jtag connection was extremely unreliable, and I didn’t want to risk bricking the unit, and not being able to recover the firmware..
I used the device tree config with the ‘old’ U-Boot, by creating a uImage, as follows:
# cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-dreamplug.dtb > arch/arm/boot/zImage_w_dtb
# mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n “linux-dreamplug” -d arch/arm/boot/zImage_w_dtb ../uImage315rc1
This was all using the kernel.org source code..
RG
Great – I’ll try that today. I have an updated u-boot from the debian-repositories, IIRC, from october 2013. As the kernel starts to boot, I guess it’s not too bad. From Archlinuxarm I tried both linux-kirkwood and linux-kirkwood-dt, but both fail to recognize any root-filesystem…
That’s… odd.
I’m currently running linux-kirkwood-dt with a U-Boot I built myself, and I didn’t have any issues.
Hmm, which kernel-version is that? Here I tried dt-3.15-4 and 3.15.1 (no dt for the latter)…
Would you mind to share your u-boot, so I can try if the problem lies there? As I said, mine comes from Debian and is dated October 2013.
I just started *make zImage* with your config-file, but on an Archlinuxarm-kirkwood-dt-patched kernel. I hope that will work, even though I’m scared at the search of the flag that needs to be added to the Archlinuxarm-kernel…
OK, the build is finished, last line I see is
bootconsole [earlycon0] disabled
I’ll try to compile without the dtb – perhaps I’ll have more luck.
No – still no luck. I think I’ll bug the people at ArchLinux to know whether they have some ideas, I’m running low on them (and having to wait for 3 hours of compilation between the ideas does not help, neither).
Another question: when you do the
cat zImage dreamplug.dtb > zImage_with_dtb
where do you take the dtb from? I’m using the one I found on the Archlinux-installation…
Are you running linux-kirkwood-dt from Archlinux with 3.15.1? Or what version?
I just tried to compile the 3.15-kernel with your config, without all the patches from Archlinux. But upon mounting the root-filesystem, it only sees the mtdblock-devices, which doesn’t help…
Now I’m eager to get a kernel compiling, seems the radio-issue with Dreamplug has been fixed:
https://bugzilla.kernel.org/show_bug.cgi?id=70191