Peter,
On Mon, Sep 1, 2014 at 6:10 PM, Peter A. Bigot <pab@pabigot.com> wrote:
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.
This is not true for recent Sitara SoCs:
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/dev/sdh1 * 63 144584 72261 c W95 FAT32 (LBA)
Device Boot Start End Blocks Id System
/dev/sdh2 144585 15406334 7630875 83 Linux
I'm using the following partition layout (both working on eMMC and sdcard with u-boot_2014.07.bb):
# fdisk -lu /dev/mmcblk0
Disk /dev/mmcblk0: 1920 MB, 1920991232 bytes, 3751936 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisk label type: dosDisk identifier: 0x00000000
Device Boot Start End Blocks Id System/dev/mmcblk0p1 * 63 80324 40131 c W95 FAT32 (LBA)