bitbake problems when testing pre-built images
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,
Signature · 1 line
Pedro
Quoted 10 lines · 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.
Quoted 7 lines
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
Please download yocto-image-minimal-qemuarm-0.9.rootfs.ext3
Quoted 11 lines
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-gnueabiThe 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
The command should be
$poky-qemu qemuarm zImage-2.6.34-qemuarm-0.9.bin
yocto-image-minimal-qemuarm-0.9.rootfs.ext3 ext3
Hope this should get you going...
- Jessica
Thank you Jessica, it worked.
May I suggest to update the wiki? As written, the instructions there do not work, at least for the section "Using Pre-Built Binaries and QEMU".
Thanks again,
Signature · 1 line
Pedro
Quoted 40 lines · Jessica
Quoted 10 lines · 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.Quoted 7 lines
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.bz2Please download yocto-image-minimal-qemuarm-0.9.rootfs.ext3
Quoted 11 lines
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-gnueabiThe 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.tarThe command should be
$poky-qemu qemuarm zImage-2.6.34-qemuarm-0.9.bin
yocto-image-minimal-qemuarm-0.9.rootfs.ext3 ext3Hope this should get you going...
- Jessica
I second the point about updating the instructions. The whole point of the quick start instructions is to let one quickly get their feet on the ground. When the documentation is in error, it costs people time and frustration. I spent a couple hours working in the dark since this is new to me, until I finally found a work-around, when the exercise should have taken minutes.
My suggestion would be that you dry-run documentation such as this, using people that have *no* yocto or openembedded background. After all, that's the target audience for a 'quick start' page.
Thanks,
Ron
Quoted 6 lines
Thank you Jessica, it worked.
May I suggest to update the wiki? As written, the instructions there do not work, at least for the section "Using Pre-Built Binaries and QEMU".
Thanks again,
Quoted 6 lines · Ron Olson
I second the point about updating the instructions. The whole point of the quick start instructions is to let one quickly get their feet on the ground. When the documentation is in error, it costs people time and frustration. I spent a couple hours working in the dark since this is new to me, until I finally found a work-around, when the exercise should have taken minutes.
Hi Ron,
I'm sorry to hear that this took up your time in this way, and wanted to let you know that I'm working with our documentation person to get the change made to our web site. Unfortunately the person who has access to make changes on our production server is at a conference this week, so we're hoping he will be able to make the change in a free moment.
Quoted 3 lines
My suggestion would be that you dry-run documentation such as this, using people that have *no* yocto or openembedded background. After all, that's the target audience for a 'quick start' page.
Point taken. As a matter of fact, we did do this, but the renaming of the final images happened literally within a day or two of our public release, and the bug in the poky-qemu script is due to this renaming. It just goes to show that even "simple" last-minute changes still need to be tested. :(
Scott
Signature · 2 lines
Scott Garman Embedded Linux Distro Engineer - Yocto Project