Poky kernel image and file system

Last post address the build process of Poky ARM SDK and how to configure Anjunta to use the toolchain for cross development; once you start building an application you  are going to need to deploy it to an target system and here is where Qemu comes to play, as you might know Qemu is an processor emulator that can be used as target platform.

The ingredients that you need are a kernel image and root file system that can be bitbaked:

source poky-init-build-env
bitbake poky-image-sato

if you are an Ubuntu hardy user like me you are going to see the next error:

ERROR:  Poky’s config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

/proc/sys/vm/mmap_min_addr is not 0. This will cause problems with qemu so please fix the value   (as root).

I find an bug report about it, by I lost the reference, anywise you only need to set mmap_min_addr to 0:

sudo sysctl -w vm.mmap_min_addr=0

After a successful build the image and files system will be place on
[poky root path]/build/tmp/deploy/images/

the kernel image zImage-qemuarm.bin and
the file system poky-image-sato-qemuarm.ext2

However the building process my take a long time so you may prefer to download the kernel image and the root file system from http://pokylinux.org/releases/

In Anjuta poky plug-in preferences add the path for the root file system and kernel image:

You can find a screen cast on how to launch quemu, deploy your application and debug at   poky-anjuta-screencast.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s