[beagleboard] Unable to use mmc 0:1 for fatls

Hi,

I've got a REV C2 Beagleboard that I haven't fiddled for a while and
decided to get back up and running the latest Angstrom Demo. I'm
using a 4GB SD card that worked before.

I'm following the various guides on getting Angstrom running but I
seem to be stuck on some sort of problem might be related to my mmc.

Here is what I see at boot (holding the user button):

Texas Instruments X-Loader 1.4.4ss (Apr 1 2010 - 07:01:03)
Beagle Rev C1/C2/C3
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.03-rc1 (Apr 01 2010 - 06:56:39)

OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
timed out in wait_for_bb: I2C_STAT=1000
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Beagle Rev C1/C2/C3
Die ID #690000030000000004013f8a17015010
Hit any key to stop autoboot: 0

When I try to list the files on the MMC card I get this:

OMAP3 beagleboard.org # fatls mmc 0:1

** Unable to use mmc 0:1 for fatls **

Any advice on how to proceed?

Much obliged.

Mike

Did you do 'mmc init' before the fatls?

regards,

Koen

Nope.

OMAP3 beagleboard.org # mmc init
mmc1 is available
OMAP3 beagleboard.org # fatls mmc 0:1
    23976 mlo
    23976 x-load.bin.ift
   205364 u-boot.bin

3 file(s), 0 dir(s)

Thanks! Do I need to issue an mmc init command each time I power up?

Mike

nevermind. dumb question. I see I can do a set bootcmd.

Thanks for your help.

mike

I am confused. I've followed the steps but the command "mmcinit" does
not appear to be a valid command. "mmc init" is valid. I tried
changing the boot command to include the space but it seems to be
entering an interactive mmc command.

Is there an updated newbie guide that reflects these changes or I am
doing something wrong?

Thanks.

Mike

Texas Instruments X-Loader 1.4.4ss (Apr 13 2010 - 22:36:28)
Beagle Rev C1/C2/C3
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.03-rc1 (Apr 01 2010 - 06:56:39)

OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
timed out in wait_for_bb: I2C_STAT=1000
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Beagle Rev C1/C2/C3
Die ID #690000030000000004013f8a17015010
Hit any key to stop autoboot: 0
Unknown command 'mmcinit' - try 'help'

** Unable to use mmc 0:1 for fatload **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OMAP3 beagleboard.org # mmcinit
Unknown command 'mmcinit' - try 'help'
OMAP3 beagleboard.org # mmc init
mmc1 is available
OMAP3 beagleboard.org # setenv bootcmd 'mmc init;fatload mmc 0
0x80300000 uImage; bootm 0x80300000'
OMAP3 beagleboard.org # savenv
Unknown command 'savenv' - try 'help'
OMAP3 beagleboard.org # saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x260000 -- 100% complete.
Writing to Nand... done
OMAP3 beagleboard.org #

Texas Instruments X-Loader 1.4.4ss (Apr 13 2010 - 22:36:28)
Beagle Rev C1/C2/C3
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.03-rc1 (Apr 01 2010 - 06:56:39)

OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Beagle Rev C1/C2/C3
Die ID #690000030000000004013f8a17015010
Hit any key to stop autoboot: 0
Unknown command 'mmcinit' - try 'help'

** Unable to use mmc 0:1 for fatload **
bootm - boot application image from memory

Usage:
bootm [addr [arg ...]]
    - boot application image stored in memory
        passing arguments 'arg ...'; when booting a Linux kernel,
        'arg' can be the address of an initrd image

Sub-commands to do part of the bootm sequence. The sub-commands must
be
issued in the order below (it's ok to not issue all sub-commands):
        start [addr [arg ...]]
        loados - load OS image
        cmdline - OS specific command line processing/setup
        bdt - OS specific bd_t processing
        prep - OS specific prep before relocation or go
        go - start OS

mmcinit is the *old* form of the command. in newer versions of
u-boot, it's now "mmc init".

rday

I did a printenv and noticed a typo in my bootcmd variable. I fixed it
and it seems to initialize the mmc correctly but now it won't load the
Angstrom image:

Any newbie-type mistakes that would lead to this?

thanks.

Texas Instruments X-Loader 1.4.4ss (Apr 13 2010 - 22:36:28)
Beagle Rev C1/C2/C3
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.03-rc1 (Apr 01 2010 - 06:56:39)

OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Beagle Rev C1/C2/C3
Die ID #690000030000000004013f8a17015010
Hit any key to stop autoboot: 0
mmc1 is available
reading uImage

** Unable to read "uImage" from mmc 0:1 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

I got it working. My boot partition had a copy of u-boot.bin from the
setup_boot.sh script that I experimented with. I copied over the u-
boot.bin that I downloaded with the Angstrom root file tar ball. I
also noticed I didn't have uImage on the boot partition (small
problem). I also copied that over and rebooted the BeagleBoard and
its working.

Thanks for the help and sorry for cluttering up the group with my
stumblings...

Mike

I will stumble just as much and like you, I need to get back to fiddling with my Revision C4 Beagleboard. So I feel a little like I'm back to learning how to read myself. I'm planning to order the Trainer board this week and the Beagleboard XM when it becomes available.

Bob Cochran