I believe there needs to be a space between mmc and init.  I'm running Gumstix Overo, and I've found if my bootargs variable does not have a space, the SD card fails to boot.  For example:

Before: ------------------

overo# printenv
bootargs = if mmcinit;....
<other environment variables>

Add a space:

overo# setenv bootargs="if mmc init;..."
overo# printenv
<other environment variables>
bootargs = if mmc init;......
overo# boot

This should then boot from the SD card if it's inserted, at least in my experience.  Note:  I put "..." at the end of bootargs since there is much more text, but don't have my Gumstix available at the moment to capture that text.  Just get that from 'printenv'

On Fri, Mar 19, 2010 at 10:21 AM, mlq <mark.l.quilling@lmco.com> wrote:


I have the 2.6.31 OE kernel up and running on the verdex board (thanks to
all who made this hapen!!!).  I have a gumstix-factory script in the
partition with the uimage.  When I power up sometimes the verdex boots from
the flash and others it boots from the microSD.  I am using the latest
u-boot for the verdex.  Is there a way to ensure the microSD is always
booted?  It seems like the microSD isnt mounting fast enough and/or the
mmcinit is failing (although I think its the later becuase i dont see the
u-boot message stating that it found the script).

View this message in context: http://old.nabble.com/Booting-from-microSD-on-the-verdex-tp27950970p27950970.html
Sent from the Gumstix mailing list archive at Nabble.com.

Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
gumstix-users mailing list