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 # 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