[yocto] bitbake problems when testing pre-built images

[Pedro I. Sanchez]

Hello,

I'm starting to play with Yocto and the first thing I want to do is to 
run pre-built images to get a feeling for the system. Unfortunately I'm 
getting errors when running the poky-qemu command. My host machine is 
Ubuntu 10.04.

I'm following the Wiki instructions at 
http://www.yoctoproject.org/docs/yocto-quick-start/yocto-project-qs.html.

The section "Using Pre-Built Binaries and QEMU" lists three steps to 
follow in order to test pre-built images, steps which I'm executing as 
follows after downloading the following arm-target files:

yocto-eglibc-i586-arm-toolchain-sdk-0.9.tar.bz2
zImage-2.6.34-qemuarm-0.9.bin
yocto-image-minimal-qemuarm-0.9.rootfs.tar.bz2

and installing the toolchain with:

$ sudo tar xjf yocto-eglibc-i586-arm-toolchain-sdk-0.9.tar.bz2 -C /
$ source /opt/poky/environment-setup-armv5te-poky-linux-gnueabi

The final step is supposed to be to run the poky-emu command but I get 
the following error:

$ poky-qemu zImage-2.6.34-qemuarm-0.9.bin 
yocto-image-minimal-qemuarm-0.9.rootfs.tar
Set MACHINE to [qemuarm-0] based on kernel [zImage-2.6.34-qemuarm-0.9.bin]
In order for this script to dynamically infer paths
to kernels or filesystem images, you either need
bitbake in your PATH or to source poky-init-build-env
before running this script

Up to this point it is either I or the wiki docs missing something.

I then tried downloading poky and installing it as follows:

$ wget http://www.yoctoproject.org/downloads/poky/poky-laverne-4.0.tar.bz2
$ tar xjf poky-laverne-4.0.tar.bz2
$ source poky-laverne-4.0/poky-init-build-env poky-4.0-build

But running poky-qemu gives me this:

$ poky-qemu zImage-2.6.34-qemuarm-0.9.bin 
yocto-image-minimal-qemuarm-0.9.rootfs.tar
Set MACHINE to [qemuarm-0] based on kernel [zImage-2.6.34-qemuarm-0.9.bin]
Note: Unable to determine filesystem extension for 
yocto-image-minimal-qemuarm-0.9.rootfs.tar
We will use the default FSTYPE for qemuarm-0
Error: Unable to determine default fstype for MACHINE [qemuarm-0]


Any suggestions would be appreciated.


Thanks,

-- 
Pedro