Unable to boot from SD-Card

Hi all together,
first of all, excuse my english, it’s not my fathers language.
Since I received my first 2 BBB I try to boot BBB from SD-Cards.
I plan to use Starterware from TI, so I loaded Starterware and CCS 5.4 an installed it on Windows 7 Computer.
In the dir “AM335X\binary\armv7a\ct_css\am335x\beaglebone\bootloader” I found “MLO” and in
“AM335X\binary\armv7a\ct_css\am335x\beaglebone\demo” I found “app”.
I loadet the tool “HP USB Disk Storage Format Tool” and format the SD.
After that I copied the 2 files with Drag & Drop to the SD-Card.
After inserting the Card to BBB and connecting terminal to J1 (RS232) the terminal reports:

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img

U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
** Unable to read file uEnv.txt **
gpio: pin 55 (gpio 55) value is 1
** Invalid partition 2 **
U-Boot#

My next step was to hold down S2 while powering BBB.
Result: Exact the same.

Next step: Loading “TI_SDCard_boot_utility_v1_9.exe” and execute it.
With this newly formatted Cart I tried to boot BBB again.
Result: Exact the same.
So, now I’m at a point needing your help, I have no idea what I have to do.
BTW Angström is correct booting, no problems.

Thank you all

Matthias

Did you look here? http://circuitco.com/support/index.php?title=Updating_The_Software#Image_For_Booting_From_microSD

Gerald

Hello Gerald,

thank you for reply.

" To force a boot from the microSD card, delete the MLO file in the FAT partition of the eMMC.

 You can access this when the board is connected over the USB cable and it appears as a thumbdrive. "

Do that mean, that booting from SD-Card is only possible if MLO on eMMC is deleted?

Matthias

I got this one Gerald J

Just rename MLO to MOO or something and you are good to go.

That way you can change it back if need be.

You can always just push the button. Look at the System Reference Manual and it explains about the boot order of the processor. eMMC–>uSD. Push button and it is uSD–<eMMC.

http://circuitco.com/support/index.php?title=BeagleBoneBlack

If the eMMC is bootable, then it boots. Remove MLO and it is no longer bootable.

Gerald

I would argue that deleting MLO, or even renaming would be bad form. I feel the proper way to do this would be to setup a proper uEnv.txt file to boot from whichever media you wish. Renaming the file is probably less of a problem though( can be reversed rather easily ).

Granted learning boot parameters for uboot / uEnv.txt can take some time, but it is well worth it in the end. This does also nearly necessitate having a way to read the serial debug output( read: having a serial debug cable / module / device ).

Works for me!

Gerald