Hi Steve!

Gumstix booting is a multi-stage process.  The X-Loader does some configuration and calls U-Boot which does some configuration and calls the kernel which does some configuration and starts the userspace.

You may have to configure, but not modify, u-boot and the kernel to get the DSP working properly.  I can't seem to immediately find a guide to setup the DSP properly so hopefully somebody can come up with that soon.

On Wed, Mar 14, 2012 at 2:54 PM, Steve Haviland <havi0019@umn.edu> wrote:

First post here.

I have succeeded in getting the standard "bitbake omap3-console-image" built and now have moved on towards more customizable images. My end goal is to have a working system with an enabled DSP. I have been following multiple tutorials(pixhawk, etc) and have run into an area that I have not found much info on.

? When are modifications needed to be done to the x-load, kernel and u-boot?

 If I'm building a custom image say for instance:

this is a test-console-image.bb
# Personal test console image

require recipes/images/omap3-console-image.bb

IMAGE_INSTALL += "   opencv   gsl   pkgconfig   grep   dropbear   git   ncurses   boost   nano   screen  "

export IMAGE_BASENAME = "test-console-image"

and I do the bitbake on it, it builds with no errors. Do I need to change anything on how I build the x-load, kernel and u-boot? If I don't great but can any one link me to more on what each of those files do?


Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
gumstix-users mailing list