I have an Overo Fire running on a Tobi board. I just recently received two - one would not boot properly from the start (and has been RMA'ed) but the second seemed fine. I booted it several times to the prompt and was able to login fine. However, the first time I had it running more than 5 minutes, It locked up at the login prompt . I cycled power, and now the Overo won't start up (I get the ECC error for u-boot.bin). I have spent the last two days trying to create a bootable MMC card, without success. However, I get a slightly different error than others with the problem. The output with the MCC inserted is: Texas Instruments X-Loader 1.4.4ss (Oct 20 2010 - 10:10:28) OMAP3530-GP ES3.1 Board revision: 2 Reading boot sector not there Loading u-boot.bin from nand ECC Failed, page 0x00080200 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 I have gone through many posts of building the MMC, and verified the partitions are exactly as shown in the posts, and have tried both FAT-16 and FAT-32. Looking through the x-loader code, the error "not there" can only occur when the trying to load a file (not a directory) and the filename being requested is NULL. Also, it doesn't appear that any change to the MLO on my MMC changes the X-Loader in use. I assume that the posting which indicated the Overo must have the NAND flash zeroed in order to load MLO from MMC was indicating that a corrupted flash could create a situation where one cannot boot, even from the MMC. here is info on my MMC: Disk /dev/sdc: 2002 MB, 2002780160 bytes 255 heads, 63 sectors/track, 243 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0003b57a Device Boot Start End Blocks Id System /dev/sdc1 * 1 5 40131 6 FAT16 /dev/sdc2 6 243 1911735 83 Linux ~$ ls -al /media/gum-uimage/ total 3324 drwx------ 2 dmwheel1 root 16384 1969-12-31 17:00 . drwxr-xr-x 6 root root 4096 2011-08-11 15:26 .. -rwx------ 1 dmwheel1 root 24220 2011-08-11 14:34 mlo -rwx------ 1 dmwheel1 root 195984 2011-08-11 14:34 u-boot.bin -rwx------ 1 dmwheel1 root 3160132 2011-08-11 14:34 uimage I am assuming that the Overo is using the X-Loader on the NAND first, before using the MMC, since changes to the X-Loader (MLO) does nothing. Is there a GPIO that I can toggle to force the Overo to load the X-Loader from the MMC "first" before trying the one on the NAND? Any ideas, or does this Overo need to be RMA'ed also? Thanks.

View this message in context: Overo Fire no longer boots
Sent from the Gumstix mailing list archive at Nabble.com.