Hello all, I have successfully built several versions of kernels using the OE environment from Angstrom.  http://www.angstrom-distribution.org/building-angstrom.  As far as I know, they work great and include exactly the modules I want, and none of the modules I don't, but neither the Overo FE-storm nor the Overo Water will boot on a Tobi :(...  As far as I can tell, this is a common problem, but I don't know how to begin troubleshooting it- and that is my question. How do I troubleshoot failure-to-boot problems? Is there a guide on that?

It looks like a lot of people have a problem where their console spits out on the wrong ttyS* port, I set mine to ttyS2.
Overo # echo $bootargs

This is the result:

Texas Instruments X-Loader 1.4.4ss (Jan 28 2011 - 20:54:56)
Board revision: 1
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.12 (Jan 31 2011 - 08:33:29)

OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Gumstix Overo board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Board revision: 1
Tranceiver detected on mmc2
No EEPROM on expansion board
Die ID #414a00229ff80000016858020901e022
Net:   smc911x-0
Hit any key to stop autoboot:  0
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

4537976 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Angstrom/3.2.19/overo
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4537912 Bytes = 4.3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.