Re: BBB + uboot 2014.07 - not booting

["Peter A. Bigot" <pab@pabigot.com>]

I am seeing the same behavior with an SD card with u-boot from current 
meta-ti master (MLO-beaglebone-2014.07-r1+gitrAUTOINC+8bd803d2c5)

I partition the cards and create the boot/root partitions with:

sudo dd if=/dev/zero of=${MMC} bs=1024 count=1024
( echo ,9,0x0C,* ; echo ,,,- ) \
   | sudo sfdisk -D -H 255 -S 63 ${MMC}

${SUDO} mkfs.vfat -F 16 -n boot ${MMC}1
${SUDO} mkfs -t ${FSTYPE} -L rootfs ${MMC}2

${SUDO} cp -p MLO u-boot.img ${MPROOT}/boot

This process works with poky master and yocto-bsp on beaglebone.

I recall from long ago that some TI systems were picky about the 
partitioning of the boot media.  Would somebody with an SD card image 
that boots the current meta-ti master provide the output of fdisk -lu 
from it, or a pointer to instructions for doing the formatting?  For 
reference, what doesn't work is:

llc[325]$ sudo fdisk -lu /dev/sdh

Disk /dev/sdh: 7892 MB, 7892631552 bytes
255 heads, 63 sectors/track, 959 cylinders, total 15415296 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/sdh1   *          63      144584       72261    c  W95 FAT32 (LBA)
/dev/sdh2          144585    15406334     7630875   83  Linux

Thanks.

Peter


On 08/19/2014 04:29 AM, Maciej Borzecki wrote:
> Hi all,
>
> There seems to be a problem booting BBB from SD card with uboot 2014.07 from
> meta-ti, 2013.07 from yocto seems to work.
> The card is partitioned as follows:
>
> Device         Boot     Start       End Blocks  Id System
> /dev/mmcblk0p1 *         2048     22527  10240   c W95 FAT32 (LBA)
> /dev/mmcblk0p2          22528    227327 102400  83 Linux
>
> I've already tried different cards.
>
> This is all I get on the serial console:
>
> U-Boot SPL 2014.07 (Aug 19 2014 - 10:45:01)
> 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 ###
>