Unable to read from mmc device

Hi Guys

I just received my BeagleBoard today, but I am unable to boot the
device properly yet.

I have serial connection to the device and the bootloader seems to be
operating properly, however when I issue the commands:

mmcinit
fatload mmc 0 0x8030000 uImage

the device hangs with no more output on the console. The mmc device
(1G in size, not sure if that is a problem?) has been formatted
FAT32. It also hangs when attempting the command fatinfo mmc 0.

Am I doing something wrong? Is there something wrong with my
BeagleBoard.

For information, I have U-Boot 1.3.3-00035-gab55ea5-dirty (Jun 16 2008
- 17:35:22).

Cheers

Matt

Make sure the MMC is inserted all the way in. I had the same symptoms
when I got started, and in my case I simply had not inserted my SD
card (same size as MMC) far enough in.

The MMC socket is designed to take several different kinds of Flash
cards. When I first got my BeagleBoard, the socket was very stiff and
I assumed I should only insert my SD card to the tip of the gold
contacts on the top surface. However, it turned out I had to push the
MMC all the way into the socket so that the SD card pushed the gold
contacts aside. Properly inserted, the SD card sticks out 1.8cm and
is about 1mm from the black plastic body of the socket.

Look inside the socket from the edge of the board and see where the 9
contacts are that must mate with the SD. (MMC has fewer, but at the
same depth.) This tells you how far the insert the card. As always,
be careful and don't force. However, following that advice myself I
didn't force hard enough :slight_smile:

I hope this helps.

What happens if you first is issue a coninfo
before the mmcinit. Do you still have no output?

greetings

I think you are giving a ZERO less, it should be 0x80300000 what you have is 0x8030000.

You can try fatls mmc 0

Regards,
Khasim
http://khasim.blogspot.com

Thanks everyone for the feedback.

JohnB -> I can confirm that the card is fully inserted as if I upload
the kernel/initrd over ymodem and flash them, I am able to mount and
read the mmc card no problem.

KJ -> I still get the same problem
# coninfo
List of available devices:
serial 800000007 SIO stdin stdout stderr
# mmcinit
# fatload mmc 0 0x80300000 uImage

Syed -> I think this was a typo in the my original posting, there the
address was 0x08300000, but thanks for pointing that out.

For your information, I have also upgraded U-Boot to version: U-Boot
1.3.3 (Jul 10 2008 - 16:33:09) as given on the beagleboard website.

Cheers

Matt

For your information, I have also upgraded U-Boot to version: U-Boot
1.3.3 (Jul 10 2008 - 16:33:09) as given on the beagleboard website.

I'm using MLO and U-Boot from Koen's Ångström demo at
http://www.angstrom-distribution.org/beagleboard-demo-image-available.
When I downloaded it, this U-Boot was:
U-Boot 1.3.4-rc2 (Aug 2 2008 - 15:30:02)

On my B-4 board, fatload also also works with the U-Boot that came
with it from Digi-Key:
U-Boot 1.3.3-00035-gab55ae5-dirty (Jun 16 2008 - 17:35:22)

One quirk of my board is that it sometimes fails to use the MMC U-Boot
even though I have the USER button pressed. A proper MMC U-Boot
should say:

Texas Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector

152880 Bytes Read from MMC
Starting OS Bootloader from MMC...

U-Boot 1.3.4-rc2 (Aug 2 2008 - 15:30:02)

But sometimes it says "Starting on with MMC" but doesn't read U-Boot
from MMC:

Texas Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector
Starting OS Bootloader...

U-Boot 1.3.3-00035-gab55ae5-dirty (Jun 16 2008 - 17:35:22)

This usually fixes itself after a few reboots, so I haven't tried to
track it down yet.

John

Could you try http://ewi546.ewi.utwente.nl/~koen/MLO-beagleboard-1.42+r7+git73eb0caf065b3b3f407d8af5c4836624e5cc7b69-r7
as MLO? Steve has fixed numerous issues[1] in that version.

regards,

Koen

[1] http://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary