[oe] Doubts regarding the final Image file

[Stephen Arnold]

I'm not the TI guru-dude, but the beaglebone machines (white or black)
don't seem to use the image bbclass, but should at least produce the rootfs
tarballs and kernel/u-boot files to make a card (in your deploy
directory).  The TI sdcard and u-boot stuff is documented all over, but
essentially you format the sdcard as a vfat boot partition and ext* root
partition, copy MLO first, then the u-boot.bin file to the boot partition,
then untar (with -p) the rootfs to the root partition.  The kernel image
could go either place, depending on the u-boot config (but is probably in
the rootfs under /boot).  If the root part is ext2/3 then u-boot should be
able to load kernel image from there with the right config.  This way is
the "old" way and unfortunately has many variations depending on versions
of u-boot and vendor.  There should be some TI people listening who know
more, but if you just try it and it fails, you could try a serial console
to get a u-boot prompt.  Then you can display the u-boot environment and
see how it's configured.

Steve


On Tue, Aug 12, 2014 at 4:07 PM, Amey Patil <amey.patil at sjsu.edu> wrote:

> Hi,
> I am a beginner in this Yocto stuff.
>
> My objective: Angstrom operating system with built in Qt5 libraries on
> Beaglebone Black.
> My source:
>
> http://www.ics.com/blog/beaglebone-black-low-cost-embedded-platform-part-3#.U-lfAv7fEew
>
> I was expecting when I do "bitbake" (the final step), I will get a image
> file which I will copy to a memory card and flash the on board eMMC of
> Beaglebone black with it.
> But I dont see an image. :(
>
> Please guide.
>
> Sincere Regards,
> Amey Patil
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>