From: Anthony G. <gar...@gm...> - 2012-06-29 15:05:57
|
Hi, I'm working on a recovery tool for overo that allows an overo to boot all the way to Linux over USB OTG. This idea is similar to the beagle-board usb recovery process. The motivation is so that 'fat fingered' maintenance chaps don't keep losing microSD cards (http://comments.gmane.org/gmane.linux.distributions.gumstix.general/52077) My current problem is that when the kernel loads the ramdisk as the rootfs it throws a segmentation fault or kernel panic. This error is very inconsistent in that sometimes I can boot all the way to Angstrom, and sometimes I get a kernel panic, but never the same things twice in a row. This behaviour is really strange since I'm loading the exact same ramdisk rootfs into memory every time I power on the overo. Any ideas on why it inconsistently fails or partially succeeds while booting? In bitbake I'm running. bitbake virtual/kernel bitbake min bitbake u-boot and I made my own x-loader so that I could add usb. Attached is min.bb and a script that I use to cut out udev and some other stuff at the beginning to make it boot faster. I was sort of following Scott Ellis' instructions here: http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=65:gumstix-quick-boot&catid=35:gumstix&Itemid=67 Also attached are 3 error logs. All 3 came from trying to boot the exact same rootfs and kernel, and yet they all fail at different locations. Thanks for the help! Anthony G. |