From: Craig H. <cr...@gu...> - 2007-09-19 17:23:59
|
On Sep 19, 2007, at 8:41 AM, Jesse Lund wrote: > Then I load the new Filesystem (JFFS2) and Kernel (uImage). Then, > katinstall 100000 and katload 100000, then bootm. Works fine (BUT > ONLY THIS TIME). Log into Gumstix as root. Poke around. reboot. > BAD MAGIC NUMBER > > It seems like U-boot's bootcmd sequence is somehow corrupting the > kernel image in the katload / bootm that it does -- but the console > output suggests it's doing the same thing as the commands I manually > entered when flashing. > > Anyone know how to engage the Gumstix support guys directly?? Almost certainly, the rootfs thinks it's supposed to be able to write to the top of flash where your kernel uImage is. Did you load an older rootfs which thinks there are only 2 regions of flash {u-boot, rootfs} rather than three {u-boot, rootfs, uImage}? Can you re-load the uImage and rootfs, restore them to the flash, then boot again, and this time save the boot log. I'm particularly interested in the part where it's talking about flash partitions. Thanks C |