On Sun, Sep 25, 2011 at 2:06 PM, Don Quixote de la Mancha <quixote@dulcineatech.com> wrote:
$ bitbake -k omap3-console-image

At the completion of the build I have the following files:

31536 Angstrom-omap3-console-image-glibc-ipk-2011.03-overo.rootfs.tar.bz2
53120 Angstrom-omap3-console-image-glibc-ipk-2011.03-overo.rootfs.ubi
   4 Angstrom-omap3-console-image-glibc-ipk-2011.03-overo-testlab/
52040 Angstrom-omap3-console-image-glibc-ipk-2011.03-overo.ubifs.img
 4220 modules-2.6.39-r102-overo.tgz
   4 omap3-console-image-overo.tar.bz2@
   4 omap3-console-image-overo.ubi@
   4 ubinize.cfg
 232 u-boot-overo-2010.12+r75+gitr261733408a27d14590cf3ec6b596461808050e32-r75.bin*
   4 u-boot-overo.bin@
 2848 uImage-2.6.39-r102-overo.bin
   0 uImage-overo.bin@

There are no files with "MLO" or "mlo" in their filename.  Was it not
built, is it not used anymore, or is it named something different.

Pardon me for being such a newbie.  When I get up to speed I should
have something to contribute!!

I usually do "bitbake x-load;bitbake u-boot;bitbake omap3-XX-image" in order to get MLO, U-Boot, uImage and rootfs-tarball generated.