[meta-ti] BBB + uboot 2014.07 - not booting

[Maciej Borzecki]

On Monday 01 of September 2014 18:28:14 Peter A. Bigot wrote:
> On 09/01/2014 04:53 PM, Diego Sueiro wrote:
> > Peter,
> > 
> > On Mon, Sep 1, 2014 at 6:10 PM, Peter A. Bigot <pab at pabigot.com
> > 
> > <mailto:pab at 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:
> > http://permalink.gmane.org/gmane.comp.handhelds.openembedded/64088
> > 
> >     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
> > 
> > I'm using the following partition layout (both working on eMMC and
> > 
> > sdcard with u-boot_2014.07.bb <http://u-boot_2014.07.bb>):
> >     # fdisk -lu /dev/mmcblk0
> >     
> >     Disk /dev/mmcblk0: 1920 MB, 1920991232 bytes, 3751936 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 label type: dos
> >     Disk identifier: 0x00000000
> >     
> >             Device Boot      Start     End      Blocks   Id  System
> >     
> >     /dev/mmcblk0p1   *          63   80324       40131    c  W95 FAT32
> >     (LBA)
> 
> Thanks.  That does appear to be an eMMC partition, which probably
> shouldn't matter, but I replicated the configuration on a 2GB class 4
> uSD card, and an 8GB class 6, and it doesn't work on either one.
> 
> llc[77]$ sudo fdisk -lu /dev/sdh
> 
> Disk /dev/sdh: 3965 MB, 3965190144 bytes
> 255 heads, 63 sectors/track, 482 cylinders, total 7744512 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       80324       40131    c  W95 FAT32 (LBA)
> /dev/sdh2           80325     7743329     3831502+  83  Linux
> 
> Anybody got a uSD partition layout that works?  I'm suspecting an issue
> with the heads/sectors/cylinders configuration.

Try looking here:
http://article.gmane.org/gmane.linux.embedded.yocto.meta-ti/4371

Although I could not confirm this, it seems that the first partition on SD 
needs to have an even block count (not sure about eMMC though, but I'm 
guessing the same rules apply).

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.