Yes it looks like one of the images on the NAND may have been corrputed. You can find documentation on how to reflash the device from: http://www.gumstix.org/how-to/70-writing-images-to-flash.html

It has the instructions on writing the images you can download from: http://cumulus.gumstix.org/images/angstrom/factory/  to the device's NAND.


On Thu, Mar 24, 2011 at 12:21 PM, Ben Johnson <myalphabetfamily@gmail.com> wrote:
Hello All,
  So I don't recommend this, but I have been gluing in my SD cards so that there is not possible chance that they will come out.  I mostly have no trouble with it, except for the other day.  The file system on my SD card became corrupted and I can no longer get it to mount. I have an overo water so I didn't think it was going to be that big of a deal.  I would just boot from nand and then fix my file system. However when I went to boot from nand I got the following message.

Overo # run nandboot
Booting from nand ...

NAND read: device 0 offset 0x280000, size 0x400000
 4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Has any one seen this?  I searched for some docs on reflashing the nand but the ones that I have found involve a bootable SD card which is not an option.  Does anyone have any good docs on using a NFS or using tftpboot to reflash the nand?


Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
gumstix-users mailing list