I just made a new 16 Gb SD card that has MLO, u-boot.bin, and uImage.bin (formatted with mkfs.vfat.) This is a Transcend brand class 6 SDHC card. I put the card into the card reader on the Beagle and then plug in the power. For this SD card, I'm trying to run the console image, not the X image. Here is what I get in a minicom terminal:
Welcome to minicom 2.3
OPTIONS: I18n
Compiled on Jul 26 2009, 22:02:23.
Port /dev/ttyUSB0
Press CTRL-A Z for help on special keys
40W
That is what the processor’s internal ROM prints out on power up. If it stops there it means that it cannot find any suitable boot source to boot from, NAND or MMC. In this case I think it means that the MMC card is either not formatted correctly or the MLO file was not the first file copied to the card before any other files were copied. I usually format the cards as FAT. I have seem some cards when formatted to FAT32, they can have issues.
Gerald
Thanks a lot, I'll try again in the morning with FAT.
Bob
I was following the validation steps for my Beagleboard RevC and ran
the erase NAND test and now when I power the board on it shows 40W and
that is all.
I have a 512MB card formatted as FAT16 as mentioned above with MLO and
the rest of the files copied in the correct order but it is not
proceeding past the processor power on notification.
How do you fix this?
What did you use to format the card? Worst case, you must use the HP format tool that is called out on the validation page. There are other tools used in Linux that wil work as well.
Gerald
There must be some issue with my Transcend brand class 6 SDHC card that the Beagle dislikes. I created and then formatted the first partition on the card as FAT12 and the Beagle still doesn't boot off it. I'm going to see if my wife has a different SD card...and try that. I'm also going to see what the local CVS has.
Bob
I used mkfs.vfat -F16 /dev/sdc1 in Kubuntu 9.10.
I'll download the HP tool and try that.
I have a feeling I know what the issue is with the Transcend card. I forgot to make the first partition bootable.
Bob
What happened to 40U?
Philip
Hi Philip,
40T, 40U, 40W all depend on the actual information send out by the ROM-code
during boot.
Most likely the character come from the ROM-code- and/or chip-revision (or
the CRC of the complete message I can't remember)
=> You shouldn't depend on exactly 40U, but more on something like 40[T-Z]
depending the exact chip revision...
More info to be found in chapter 26 (page 3472) of the OMAP35xx TRM
(spruf98c.pdf) describing the boot process...
Hope this clarified/answered you question?
Søren
Hi Philip,
40T, 40U, 40W all depend on the actual information send out by the ROM-code
during boot.
Most likely the character come from the ROM-code- and/or chip-revision (or
the CRC of the complete message I can't remember)
=> You shouldn't depend on exactly 40U, but more on something like 40[T-Z]
depending the exact chip revision...More info to be found in chapter 26 (page 3472) of the OMAP35xx TRM
(spruf98c.pdf) describing the boot process...Hope this clarified/answered you question?
Not really, I've personally seen 40T and 40W and heard off 40V, but I
wonder what happened to 40 U 
Philip
OK - Now I got your question 
My best guess is that you can consider 40U an internal never
produced/official released chip version then
Søren
Behalf Of Philip Balister
S�ren Steen Christensen wrote:
OK - Now I got your question
My best guess is that you can consider 40U an internal never
produced/official released chip version then
what do you estimate it will be worth on the OMAP3 collectors market?
> OK - Now I got your question
>
> My best guess is that you can consider 40U an internal never
> produced/official released chip version thenwhat do you estimate it will be worth on the OMAP3 collectors market?
I think it will pretty much depend on which "special features" were
introduced in the U-version - Do you have one?
Søren