Openmoko under QEMU/zh cn - Revision history

Liusong: /* Manual setup */

2009-02-23T17:01:49Z

‎Manual setup

Liusong: /* 使用 MokoMakefile */

2009-02-19T14:35:20Z

‎使用 MokoMakefile

Kempelen: -Guides

2008-09-12T22:01:59Z

-Guides

DolfjeBot1: Replacing '\[\[Openmoko\]\]' with 'Openmoko'

2008-08-23T10:53:55Z

Replacing '\[\[Openmoko\]\]' with 'Openmoko'

DolfjeBot1: Replacing 'OpenMoko' with 'Openmoko'

2008-08-23T09:04:46Z

Replacing 'OpenMoko' with 'Openmoko'

Dolfje at 22:15, 20 August 2008

2008-08-20T22:15:59Z

Glenn: catchg

2008-07-16T07:22:19Z

catchg

Glenn: case

2008-07-09T10:19:34Z

case

Glenn: OpenMoko under QEMU/zh cn moved to Openmoko under QEMU/zh cn: case

2008-07-09T06:44:47Z

OpenMoko under QEMU/zh cn moved to Openmoko under QEMU/zh cn: case

BSCH at 03:04, 13 May 2008

2008-05-13T03:04:54Z

@@ Line 130: / Line 130: @@
 To obtain the latest source code for the emulator, you will want to do something like the following:
 <pre>
 $ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973
@@ Line 135: / Line 136: @@
 </pre>
 Now, we're going to configure and build the emulator (Note [[#Requirements|Requirements]] below):
 <pre>
 $ ./configure --target-list=arm-softmmu  # GCC 3.x will be required, see --cc=
@@ Line 141: / Line 143: @@
 See other available options for the configure script by appending "--help".
-Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run Openmoko you will also need to somehow install Openmoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First run
+Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run
 <pre>$ openmoko/download.sh</pre>
 which will look up the list of latest available Openmoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the flash.sh script. First make sure you have the netpbm package installed for some graphics conversion utilities. On Ubuntu this can be done by:

@@ Line 121: / Line 121: @@
 This is arguably the easiest way of building qemu-neo1973 since you won't need to deal with the compiling and flashing processes yourself. See [[Using_QEMU_with_MokoMakefile|MokoMakefile]] for details.
+这是可以证明的最简单的搭建QEMU-neo1973的办法，因为你不需要
 If you *just* build QEMU and use the official images by typing "make qemu" only (as opposed to setting up monotone and openembedded and building an entire new image for yourself with MokoMakefile), then the build takes less time than the manual instructions below (since it's all done automatically).
 === Manual setup ===

← Older revision		Revision as of 22:01, 12 September 2008
Line 454:		Line 454:

	[[Category:Emulation/zh cn]]		[[Category:Emulation/zh cn]]
−	~~[[Category:Guides/zh cn]]~~

@@ Line 1: / Line 1: @@
-QEMU can be used in at least three ways to run [[Openmoko]]. Depending on the purpose that you are going to use the emulator for, you should decide on the target platform.
+QEMU can be used in at least three ways to run Openmoko. Depending on the purpose that you are going to use the emulator for, you should decide on the target platform.
-QEMU 至少有三种方式来运行[[Openmoko]].根据你的虚拟机使用目的，你应该决定要使用目标平台。
+QEMU 至少有三种方式来运行Openmoko.根据你的虚拟机使用目的，你应该决定要使用目标平台。
-*''PC'' - Openmoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get Openmoko running if you want to get an impression of how it looks.  In this scenario QEMU would only serve for isolating your [[Openmoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].
+*''PC'' - Openmoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get Openmoko running if you want to get an impression of how it looks.  In this scenario QEMU would only serve for isolating your Openmoko installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].
-*''个人计算机'' - Openmoko 可以运行在兼容i386的硬件上，32位或64位，并且，他可能是运行Openmoko最快的方式了，如果你想对Openmoko有个整体印象的话。在这种方案中，QEMU在你的正常系统中独立的安装[[Openmoko]]。如果你用的是非UNIX系统，QEMU会提供个非侵入方式（non-intrusive way）快速运行Linux。更多的资料可以在[[FAQ]]中和[[Getting Openmoko working on host with Xoo|here]]找到
+*''个人计算机'' - Openmoko 可以运行在兼容i386的硬件上，32位或64位，并且，他可能是运行Openmoko最快的方式了，如果你想对Openmoko有个整体印象的话。在这种方案中，QEMU在你的正常系统中独立的安装Openmoko。如果你用的是非UNIX系统，QEMU会提供个非侵入方式（non-intrusive way）快速运行Linux。更多的资料可以在[[FAQ]]中和[[Getting Openmoko working on host with Xoo|here]]找到
 *''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original Openmoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_Openmoko.3F|FAQ]].

@@ Line 2: / Line 2: @@
 QEMU 至少有三种方式来运行[[Openmoko]].根据你的虚拟机使用目的，你应该决定要使用目标平台。
-*''PC'' - Openmoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get OpenMoko running if you want to get an impression of how it looks.  In this scenario QEMU would only serve for isolating your [[OpenMoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].
+*''PC'' - Openmoko can be built to run on regular i386 hardware, 32- or 64-bit and this is probably the fastest way to get Openmoko running if you want to get an impression of how it looks.  In this scenario QEMU would only serve for isolating your [[Openmoko]] installation from your normal system, or, if you're not on a UNIX system, QEMU provides a non-intrusive way to get Linux up quickly. More information can be found in the [[FAQ]] and [[Getting Openmoko working on host with Xoo|here]].
-*''个人计算机'' - Openmoko 可以运行在兼容i386的硬件上，32位或64位，并且，他可能是运行OpenMoko最快的方式了，如果你想对OpenMoko有个整体印象的话。在这种方案中，QEMU在你的正常系统中独立的安装[[OpenMoko]]。如果你用的是非UNIX系统，QEMU会提供个非侵入方式（non-intrusive way）快速运行Linux。更多的资料可以在[[FAQ]]中和[[Getting Openmoko working on host with Xoo|here]]找到
+*''个人计算机'' - Openmoko 可以运行在兼容i386的硬件上，32位或64位，并且，他可能是运行Openmoko最快的方式了，如果你想对Openmoko有个整体印象的话。在这种方案中，QEMU在你的正常系统中独立的安装[[Openmoko]]。如果你用的是非UNIX系统，QEMU会提供个非侵入方式（non-intrusive way）快速运行Linux。更多的资料可以在[[FAQ]]中和[[Getting Openmoko working on host with Xoo|here]]找到
-*''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F|FAQ]].
+*''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original Openmoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_Openmoko.3F|FAQ]].
-*''Integrator/CP'' - 这是默认的QEMU模拟的基于ARM的机器。它的QEMU用参数MACHINE="qemuarm"编译的，并且他完全能运行原始的OpenMoko根镜像，除了特定的CPU核，它不能完全模拟[[:Category:Neo1973 Hardware | Neo1973 Hardware]]。想知道更多的资料，可以读[[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F|FAQ]]。
+*''Integrator/CP'' - 这是默认的QEMU模拟的基于ARM的机器。它的QEMU用参数MACHINE="qemuarm"编译的，并且他完全能运行原始的Openmoko根镜像，除了特定的CPU核，它不能完全模拟[[:Category:Neo1973 Hardware | Neo1973 Hardware]]。想知道更多的资料，可以读[[FAQ#Q:_Is_there_an_emulator_available_for_Openmoko.3F|FAQ]]。
-*''Neo1973'' - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] (GTA01) hardware, although not all of it. Additionally, Neo FreeRunner emulation is a work-in-progress. When all of the emulator parts are more mature our code is going to be submitted and merged to the main QEMU development tree.
+*''Neo1973'' - the QEMU tree available from Openmoko repositories is also capable of emulating most of the actual [[Neo1973]] (GTA01) hardware, although not all of it. Additionally, Neo FreeRunner emulation is a work-in-progress. When all of the emulator parts are more mature our code is going to be submitted and merged to the main QEMU development tree.
 == Neo1973 emulation ==
-This target will (obviously) run original OpenMoko rootfs images, but then it should also be able to run the original u-boot and kernel images, the same ones that a real Neo1973 (GTA01) uses. Among other differences you will notice between this approach and the Integrator/CP target is you also get correct screen resolution, some (fake) battery readings, and other goodness. Currently missing parts of the GTA01 emulator are: [[Hardware:AGPS|AGPS]] and [[Bluetooth]] - these things will still be worked on, as well as general usability. Even with these things missing, QEMU should provide substantial help in debugging kernel and u-boot issues to developers.
+This target will (obviously) run original Openmoko rootfs images, but then it should also be able to run the original u-boot and kernel images, the same ones that a real Neo1973 (GTA01) uses. Among other differences you will notice between this approach and the Integrator/CP target is you also get correct screen resolution, some (fake) battery readings, and other goodness. Currently missing parts of the GTA01 emulator are: [[Hardware:AGPS|AGPS]] and [[Bluetooth]] - these things will still be worked on, as well as general usability. Even with these things missing, QEMU should provide substantial help in debugging kernel and u-boot issues to developers.
-What QEMU can '''*not*''' be used for, and probably no other emulator can, is speed measures and getting the general feel of OpenMoko performance. Code running in qemu runs with the maximum speed your host computer can provide with an overhead of translating target code to host code, and this overhead is not uniform across different instructions. This means that even if your virtual Neo reports near 100 BogoMIPS (which is the speed of a real Neo), different actions performed in the emulator will not run with the same speed. On most PCs you will notice the virtual Neo running faster than a real one (Audio related operations may be one of the exceptions).
+What QEMU can '''*not*''' be used for, and probably no other emulator can, is speed measures and getting the general feel of Openmoko performance. Code running in qemu runs with the maximum speed your host computer can provide with an overhead of translating target code to host code, and this overhead is not uniform across different instructions. This means that even if your virtual Neo reports near 100 BogoMIPS (which is the speed of a real Neo), different actions performed in the emulator will not run with the same speed. On most PCs you will notice the virtual Neo running faster than a real one (Audio related operations may be one of the exceptions).
 === What hardware is supported ===
@@ Line 78: / Line 78: @@
 == Neo FreeRunner emulation ==
-The second line of OpenMoko phones, the Neo FreeRunner (GTA02) saw various hardware changes and improvements since Neo1973 (GTA01).  QEMU has fullest support for the GTA01 (the first model), but partial GTA02 emulation is also planned.  This will only include the hardware components which were added in GTA02 and were not present in GTA01:
+The second line of Openmoko phones, the Neo FreeRunner (GTA02) saw various hardware changes and improvements since Neo1973 (GTA01).  QEMU has fullest support for the GTA01 (the first model), but partial GTA02 emulation is also planned.  This will only include the hardware components which were added in GTA02 and were not present in GTA01:
 * The u-blox GPS chip (i.e. raw NMEA protocol).
@@ Line 139: / Line 139: @@
 See other available options for the configure script by appending "--help".
-Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run OpenMoko you will also need to somehow install OpenMoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First run
+Now you should have a working emulator under the name "arm-softmmu/qemu-system-arm". To run Openmoko you will also need to somehow install Openmoko on your virtual phone, which is totally clean of any software at this moment. There are several block devices to choose from, the best option is probably to do exactly what the Neo1973 manufacturer does before it ships the device to the final user. This process is described in [[Bootloader]], [[Kernel]], [[NAND bad blocks]] and [[Devirginator]] but you don't need to know all the details. Two scripts are provided to generate a firmware for your phone, as realistic as possible. First run
 <pre>$ openmoko/download.sh</pre>
-which will look up the list of latest available OpenMoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the flash.sh script. First make sure you have the netpbm package installed for some graphics conversion utilities. On Ubuntu this can be done by:
+which will look up the list of latest available Openmoko snapshot builds from buildhost.openmoko.org and choose the most recent [[u-boot]], Kernel, and root filesystem images, and download the images (unless they are already found in the openmoko/ directory). These binaries will be used by the flash.sh script. First make sure you have the netpbm package installed for some graphics conversion utilities. On Ubuntu this can be done by:
 <pre>sudo apt-get install netpbm</pre>
 Then run:
@@ Line 159: / Line 159: @@
 The kernel supporting GTA02 emulator is obtained by applying the ''openmoko/linux-gta02-pseudo.patch'' patch found in qemu-neo1973 sources, to the 2.6.24 openmoko kernel (vanilla linux-2.6.24 + the openmoko patchset from http://svn.openmoko.org/branches/src/target/kernel/2.6.24.x/patches/).  Since the GTA02 kernel support is still under heavy development, please refer to the openmoko/README file contained in qemu-neo1973 sources for the latest instructions on building the kernel.
-If a normal OpenMoko kernel is used under Neo FreeRunner emulator, it will simply run as if the machine was a GTA01 and not detect any of the new peripherals.
+If a normal Openmoko kernel is used under Neo FreeRunner emulator, it will simply run as if the machine was a GTA01 and not detect any of the new peripherals.
 == Convenient Scripts ==
@@ Line 169: / Line 169: @@
 * openmoko/qemu-upload.sh <filename>
-produces a SD card image with one partition with the given file(s) on it (you can pass a list of files) and inserts it into the phone. The OpenMoko kernel should detect the event and the automounter should mount the partition. openmoko/qemu-auto.sh must be running already. If you pass no parameters, it ejects the media (the OM kernel is too dumb to detect this unfortunately). This will only work with gta01 emulation because gta02 has no SD.
+produces a SD card image with one partition with the given file(s) on it (you can pass a list of files) and inserts it into the phone. The Openmoko kernel should detect the event and the automounter should mount the partition. openmoko/qemu-auto.sh must be running already. If you pass no parameters, it ejects the media (the OM kernel is too dumb to detect this unfortunately). This will only work with gta01 emulation because gta02 has no SD.
 * openmoko/qemu-quit.sh
@@ Line 248: / Line 248: @@
 == Setting up USB connection ==
-It is possible (although not very straight forward, probably about the complexity of tun-tap networking) to connect the virtual, emulated Neo1973 to the Linux PC on which the emulator is running, and work with it as if a real Neo1973 was plugged into the computer's USB port, but no twiddling with cables is needed. If you're testing your applications on the Neo, it may be worth setting up this kind of connection because it lets you enable normal [[USB_Networking|networking between the PC and the phone and ssh into it]] (which is much more comfortable than typing commands into the OpenMoko's terminal emulator via on-screen keyboard). Here's what you will need in order to get this working:
+It is possible (although not very straight forward, probably about the complexity of tun-tap networking) to connect the virtual, emulated Neo1973 to the Linux PC on which the emulator is running, and work with it as if a real Neo1973 was plugged into the computer's USB port, but no twiddling with cables is needed. If you're testing your applications on the Neo, it may be worth setting up this kind of connection because it lets you enable normal [[USB_Networking|networking between the PC and the phone and ssh into it]] (which is much more comfortable than typing commands into the Openmoko's terminal emulator via on-screen keyboard). Here's what you will need in order to get this working:
 A Linux host with a 2.6 series kernel. The following drivers compiled-in or in modules: dummy_hcd, gadgetfs, usbnet, cdc_ether. [[Building Gadget USB Module|A detailed guide to building the necessary modules is available (primarily Ubuntu focused).]] Generic instructions follow.
@@ Line 280: / Line 280: @@
 After that the rest of the procedure can be performed from your regular user account. Mounting gadgetfs is done with:
 <pre> $ mount /dev/gadget</pre>
-The "default_uid" parameter changes the ownership on all files under /dev/gadget to your own and since the files there are created and destroyed dynamically, there's no easy way to have that performed by ''udev''. Now running qemu as you usually do but appending "-usb -usbgadget" (in the current version of the [[MokoMakefile]] this is not included) should enable the USB Slave functionality. The qemu monitor commands "info usbslave" and "usb_add gadget" will be useful. The former instruction asks the OS running under the emulator (OpenMoko) to describe its slave features (that's what ''lsusb'' does after a Neo1973 is connected to a PC). You can see the available USB configurations in this command's output. Since gadgetfs allows only one configuration, we will need to choose the desired configuration - most device have only one such configuration, in which case you can use just "usb_add gadget" to connect to host; CDC ethernet devices however usually include a second configuration for RNDIS networking (i.e. Ms Windows compatibility) and so does OpenMoko when using the g_ether driver. Hence, to get this right, wait for OpenMoko to fully boot up and execute the following in QEMU monitor:
+The "default_uid" parameter changes the ownership on all files under /dev/gadget to your own and since the files there are created and destroyed dynamically, there's no easy way to have that performed by ''udev''. Now running qemu as you usually do but appending "-usb -usbgadget" (in the current version of the [[MokoMakefile]] this is not included) should enable the USB Slave functionality. The qemu monitor commands "info usbslave" and "usb_add gadget" will be useful. The former instruction asks the OS running under the emulator (Openmoko) to describe its slave features (that's what ''lsusb'' does after a Neo1973 is connected to a PC). You can see the available USB configurations in this command's output. Since gadgetfs allows only one configuration, we will need to choose the desired configuration - most device have only one such configuration, in which case you can use just "usb_add gadget" to connect to host; CDC ethernet devices however usually include a second configuration for RNDIS networking (i.e. Ms Windows compatibility) and so does Openmoko when using the g_ether driver. Hence, to get this right, wait for Openmoko to fully boot up and execute the following in QEMU monitor:
 <pre>
 QEMU 0.9.0 monitor - type 'help' for more information
@@ Line 294: / Line 294: @@
 If qemu gives "couldn't add device gadget:1", double-check that it was built against gadgetfs - the file config-host.h must contain the line "#define CONFIG_GADGETFS 1".
-The "1" in "usb_add gadget:N" is the number of the USB configuration that we want to use. If everything went correctly - you can check that in dmesg - you should now have a new network interface called ''usb0'' on the PC, through which you can talk to the OpenMoko running in QEMU:
+The "1" in "usb_add gadget:N" is the number of the USB configuration that we want to use. If everything went correctly - you can check that in dmesg - you should now have a new network interface called ''usb0'' on the PC, through which you can talk to the Openmoko running in QEMU:
 <pre>
   $ dmesg | tail
@@ Line 448: / Line 448: @@
 == See also ==
 *[[Building Gadget USB Module]] - Helpful guide
-*[[Xephyr]] - OpenMoko on i386
+*[[Xephyr]] - Openmoko on i386
-*[[Xoo]] - OpenMoko on i386
+*[[Xoo]] - Openmoko on i386
 {{Languages|Openmoko_under_QEMU}}

@@ Line 453: / Line 453: @@
 {{Languages|Openmoko_under_QEMU}}
-[[Category:Emulation]]
+[[Category:Emulation/zh cn]]
-[[Category:Guides]]
+[[Category:Guides/zh cn]]

← Older revision		Revision as of 03:04, 13 May 2008
Line 6:		Line 6:

	*''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware \| Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F\|FAQ]].		*''Integrator/CP'' - this is the default ARM-based machine that QEMU knows about. This target is used with MACHINE="qemuarm" and it is sufficient to run the original OpenMoko rootfs image, although it doesn't emulate any of the [[:Category:Neo1973 Hardware \| Neo1973 Hardware]] except the very CPU core. Read more in the [[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F\|FAQ]].
		+	*''Integrator/CP'' - 这是默认的QEMU模拟的基于ARM的机器。它的QEMU用参数MACHINE="qemuarm"编译的，并且他完全能运行原始的OpenMoko根镜像，除了特定的CPU核，它不能完全模拟[[:Category:Neo1973 Hardware \| Neo1973 Hardware]]。想知道更多的资料，可以读[[FAQ#Q:_Is_there_an_emulator_available_for_OpenMoko.3F\|FAQ]]。
		+

	*''Neo1973'' - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] (GTA01) hardware, although not all of it. Additionally, Neo FreeRunner emulation is a work-in-progress. When all of the emulator parts are more mature our code is going to be submitted and merged to the main QEMU development tree.		*''Neo1973'' - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] (GTA01) hardware, although not all of it. Additionally, Neo FreeRunner emulation is a work-in-progress. When all of the emulator parts are more mature our code is going to be submitted and merged to the main QEMU development tree.