This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MMC: block number 0x100 exceeds max(0x0)

After building a few images with Yocto I decided to try and use just OE Core and meta-ti.  After building core-image-base I was unable to boot from the same SD card I have been using.  I notice the version of uboot is much newer in meta-ti.    When I hold the user button my BeagleBone Black to boot off the SD card I get the following on the console:

U-Boot SPL 2014.07 (Aug 29 2014 - 13:15:48)
MMC: block number 0x100 exceeds max(0x0)
MMC: block number 0x200 exceeds max(0x0)
*** Error - No Valid Environment Area found
Using default environment

MMC: block number 0x1 exceeds max(0x0)
** Can't read partition table on 0:0 **
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
### ERROR ### Please RESET the board ###

The card partition is as follows:

Disk /dev/mmcblk0: 31.7 GB, 31691112448 bytes
4 heads, 16 sectors/track, 967136 cylinders, total 61896704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 63 144584 72261 c W95 FAT32 (LBA)
/dev/mmcblk0p2 147456 7127039 3489792 83 Linux

My boot partition has MLO and u-boot.img.  This was enough with Yocto but using this new u-boot do I need more there?  I am not using a uEnv.txt file.

  • Looks like another person ran into the same issue.  Like him I can boot SD card when using u-boot 2014.07, just not u-boot-ti-staging.

    http://comments.gmane.org/gmane.linux.embedded.yocto.meta-ti/4358

  • Hi Adam,

    There obviously is a bug with this version of U-Boot. Did you try the U-Boot from the commit id suggested at the bottom of the link you posted?

    My suggestion is to use a known stable version of the U-Boot bootloader.

    Best regards,
    Miroslav

  • I was able to switch over to 2014.07 after my last post once I realized that machine.conf was processed after my local.conf.  I'm a little surprised that the repository used the staging versions of the kernel and u-boot by default but am past that now.  I can boot core-image-base and get to the console.  On to HDMI output now.

    Also, the staging version out there now is the same as the last person in the other post.