<small>(If you have trouble with cut-and-paste of the lines above, go to edit mode and copy from there)</small>

+

+

Not all packages exist, but you can (or at least I could) safely ignore this.

+

+

You also need to install gcc3.x, which was neither found by yum nor by rpmseek/rpmfind. But Fedora 7 has the rpm, so go to any site which archives Fedora packages (e.g. http://sunsite.rwth-aachen.de) and grab e.g. <tt>compat-gcc-34-3.4.6-7.x86_64.rpm</tt> (adapt to your architecture, any 3.x.y version should do). Then do a <tt>yum localinstall</tt>.

== Compilation and use ==

== Compilation and use ==

Line 76:

Line 88:

rootfs_wildcard="Open?oko-*image*-om-gta01.rootfs.jffs2"

rootfs_wildcard="Open?oko-*image*-om-gta01.rootfs.jffs2"

Or change the downloaded images filename to match '''Open?oko-openmoko-*image*-om-gta01.rootfs.jffs2'''.

Or change the downloaded images filename to match '''Open?oko-openmoko-*image*-om-gta01.rootfs.jffs2'''.

−

−

Read [[Snapshot review]] to download better working images.

[[Category:Emulation]]

[[Category:Emulation]]

Latest revision as of 13:14, 9 December 2009

MokoMakefile has support for automatically building, flashing, and running Openmoko under QEMU using qemu-neo1973, a fork of qemu which adds simulation of almost all Neo1973 devices in order allow testing Openmoko images in a virtual environment.

For this, it's not required to download and run a complete Openmoko build (which takes several hours to even days and needs lots of disk space and RAM), because if you only need to test pre-compiled images, it is enough to build qemu-neo1973 and to set it up to run these images. This is what this article deals with and to describe how MokoMakefile makes this easy.

Note: The talk page of MokoMakefile may also contain some valuable hints regarding compiling and using QEMU for Openmoko, including distribution specific issues and workarounds.

Gentoo will usually have some version of gcc-3 installed by default. You don't need to use gcc-config to switch the default compiler to gcc-3 - Qemu should find there right version if it's installed.

GCC 3.4 is known to be broken on 32-bit Gentoo. If your 32-bit i386 system has a 3.4 GCC installed from portage you will need to downgrade to 3.3.6.(Note: GCC 3.3 is currently broken and masked in Gentoo, consider disabling QEMU if you are running gentoo)

Some Gentoo users who have multiple GCC versions installed have had to modify the Makefile (by adding --cc=gcc-3.4.6 to the qemu-configure call, after --target-list=arm-softmmu) otherwise the compilation fails during compilation of softmmu_template.h see this link for more details.

Gentoo users will need to install sys-fs/dosfstools for the mkdosfs command then create a link in /sbin:
ln -s /usr/sbin/mkdosfs /sbin/mkdosfs.

(If you have trouble with cut-and-paste of the lines above, go to edit mode and copy from there)

Not all packages exist, but you can (or at least I could) safely ignore this.

You also need to install gcc3.x, which was neither found by yum nor by rpmseek/rpmfind. But Fedora 7 has the rpm, so go to any site which archives Fedora packages (e.g. http://sunsite.rwth-aachen.de) and grab e.g. compat-gcc-34-3.4.6-7.x86_64.rpm (adapt to your architecture, any 3.x.y version should do). Then do a yum localinstall.

“make qemu” will build qemu-neo1973, download the latest official Openmoko images, flash the images into the virtual NAND flash, create an empty virtual SD card, and run the emulator (you still need to install the makefile as mentioned above, however).

make run-qemu - restarts qemu with the currently flashed Openmoko images and current virtual SD card.

make run-qemu-snapshot - does the same but starts qemu with -snapshot which causes QEMU to write all changes to temporary files instead of flash and disk image files.This is beneficial in that the virtual Neo1973 is not changed. Also all changes that make run-qemu-snapshot creates occur in parallel. This allows you to run multiple instances without creating incoherent flash and SD card state. You can, however, force the write back by pressing C-a s in the QEMU window. This may be useful to update the flash and disk images in the last qemu instance that is running to preserve the changes.

You may also use:

make download-images - to download the latest official images

make flash-qemu-official - to flash those images

make flash-qemu-local - to flash your latest locally built images, which can then be followed by

make qemu-copy-package-foo - copies foo.ipk to the virtual SD card, which allows you to use ipkg install /media/mmcblk0/file inside the running Openmoko to install the package.

The process described above will download the latest daily build, which may be broken or non-working in many cases. If you delete the images downloaded into the images/openmoko directory, you can add another set of the 3 files there and flash them into QEmu by make flash-qemu-official.

To be able to flash FSO images you must change the file search pattern in build/qemu/openmoko/env to match the:

rootfs_wildcard="Open?oko-*image*-om-gta01.rootfs.jffs2"

Or change the downloaded images filename to match Open?oko-openmoko-*image*-om-gta01.rootfs.jffs2.

Views

Personal tools

MokoMakefile has support for automatically building, flashing, and running Openmoko under QEMU using qemu-neo1973, a fork of qemu which adds simulation of almost all Neo1973 devices in order allow testing Openmoko images in a virtual environment.

For this, it's not required to download and run a complete Openmoko build (which takes several hours to even days and needs lots of disk space and RAM), because if you only need to test pre-compiled images, it is enough to build qemu-neo1973 and to set it up to run these images. This is what this article deals with and to describe how MokoMakefile makes this easy.

Note: The talk page of MokoMakefile may also contain some valuable hints regarding compiling and using QEMU for Openmoko, including distribution specific issues and workarounds.

Build requirements

gcc 3.4 or 3.3: You need gcc-3.x for building qemu. If you have no precompiled gcc-3.x packages, you need to compile it. [1]

Gentoo

Gentoo will usually have some version of gcc-3 installed by default. You don't need to use gcc-config to switch the default compiler to gcc-3 - Qemu should find there right version if it's installed.

GCC 3.4 is known to be broken on 32-bit Gentoo. If your 32-bit i386 system has a 3.4 GCC installed from portage you will need to downgrade to 3.3.6.(Note: GCC 3.3 is currently broken and masked in Gentoo, consider disabling QEMU if you are running gentoo)

Some Gentoo users who have multiple GCC versions installed have had to modify the Makefile (by adding --cc=gcc-3.4.6 to the qemu-configure call, after --target-list=arm-softmmu) otherwise the compilation fails during compilation of softmmu_template.h see this link for more details.

Gentoo users will need to install sys-fs/dosfstools for the mkdosfs command then create a link in /sbin:
ln -s /usr/sbin/mkdosfs /sbin/mkdosfs.

“make qemu” will build qemu-neo1973, download the latest official Openmoko images, flash the images into the virtual NAND flash, create an empty virtual SD card, and run the emulator (you still need to install the makefile as mentioned above, however).

make run-qemu - restarts qemu with the currently flashed Openmoko images and current virtual SD card.

make run-qemu-snapshot - does the same but starts qemu with -snapshot which causes QEMU to write all changes to temporary files instead of flash and disk image files.This is beneficial in that the virtual Neo1973 is not changed. Also all changes that make run-qemu-snapshot creates occur in parallel. This allows you to run multiple instances without creating incoherent flash and SD card state. You can, however, force the write back by pressing C-a s in the QEMU window. This may be useful to update the flash and disk images in the last qemu instance that is running to preserve the changes.

You may also use:

make download-images - to download the latest official images

make flash-qemu-official - to flash those images

make flash-qemu-local - to flash your latest locally built images, which can then be followed by

make qemu-copy-package-foo - copies foo.ipk to the virtual SD card, which allows you to use ipkg install /media/mmcblk0/file inside the running Openmoko to install the package.

Using tested and recommended images

The process described above will download the latest daily build, which may be broken or non-working in many cases. If you delete the images downloaded into the images/openmoko directory, you can add another set of the 3 files there and flash them into QEmu by make flash-qemu-official.

To be able to flash FSO images you must change the file search pattern in build/qemu/openmoko/env to match the:

rootfs_wildcard="Open?oko-*image*-om-gta01.rootfs.jffs2"

Or change the downloaded images filename to match Open?oko-openmoko-*image*-om-gta01.rootfs.jffs2.