3.3.1. Getting the Images

To get the kernel and filesystem images, you either have to build them or download pre-built versions. For an example of how to build these images, see the "Buiding Images" section of the Yocto Project Quick Start. For an example of downloading pre-build versions, see the "Example Using Pre-Built Binaries and QEMU" section.

The Yocto Project ships basic kernel and filesystem images for several architectures (x86, x86-64, mips, powerpc, and arm) that you can use unaltered in the QEMU emulator. These kernel images reside in the release area - http://downloads.yoctoproject.org/releases/yocto/yocto-1.9/machines and are ideal for experimentation using Yocto Project. For information on the image types you can build using the OpenEmbedded build system, see the "Images" chapter in the Yocto Project Reference Manual.

If you are planning on developing against your image and you are not building or using one of the Yocto Project development images (e.g. core-image-*-dev), you must be sure to include the development packages as part of your image recipe.

If you plan on remotely deploying and debugging your application from within the Eclipse IDE, you must have an image that contains the Yocto Target Communication Framework (TCF) agent (tcf-agent). You can do this by including the eclipse-debug image feature.

Note

See the "Image Features" section in the Yocto Project Reference Manual for information on image features.

To include the eclipse-debug image feature, modify your local.conf file in the Build Directory so that the EXTRA_IMAGE_FEATURES variable includes the "eclipse-debug" feature. After modifying the configuration file, you can rebuild the image. Once the image is rebuilt, the tcf-agent will be included in the image and is launched automatically after the boot.