OpenMoko under QEMU - Revision history

Coolcat at 07:43, 24 March 2008

2008-03-24T07:43:39Z

Show changes

Coolcat at 07:41, 24 March 2008

2008-03-24T07:41:27Z

John at 08:37, 20 March 2008

2008-03-20T08:37:29Z

Seppi: /* Simple network connection with pppd */

2008-03-14T12:32:20Z

‎Simple network connection with pppd

Dread: /* Using MokoMakefile */ chinging link to the right page for using qemu with moko makefile

2008-02-09T12:22:24Z

‎Using MokoMakefile: chinging link to the right page for using qemu with moko makefile

Galadh: /* Using MokoMakefile */ removed doubled link

2008-02-06T17:07:30Z

‎Using MokoMakefile: removed doubled link

Balrog: /* Neo1973 emulation */ Speed obviously depends on the host specs but let's revert to figures backed by an actual test. + spelling

2008-01-11T19:56:32Z

‎Neo1973 emulation: Speed obviously depends on the host specs but let's revert to figures backed by an actual test. + spelling

Gshadow: /* Simple network connection with pppd */

2008-01-01T20:20:29Z

‎Simple network connection with pppd

Denis std: /* Neo1973 emulation */

2007-11-27T20:46:34Z

‎Neo1973 emulation

TuukkaH: /* Simple network connection with pppd */ link pppd

2007-11-25T18:48:06Z

‎Simple network connection with pppd: link pppd

@@ Line 1: / Line 1: @@
-QEMU can basically be used in 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 basically be used in 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.
-*''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]].
 *''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]].
-*''Neo1973'' - the QEMU tree available from OpenMoko repositories is also capable of emulating most of the actual [[Neo1973]] hardware, although not all of it at this moment. It is a work-in-progress and when it's more mature it is going to be submitted for merging to the main QEMU development tree.
+*''Neo1973'' - the QEMU tree available from Openmoko repositories is also capable of emulating most of the actual [[Neo1973]] hardware, although not all of it at this moment. It is a work-in-progress and when it's more mature it is going to be submitted for merging 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 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 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 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 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 ===

← Older revision		Revision as of 08:37, 20 March 2008
Line 106:		Line 106:

	Win32 binaries shipped with firmware can be downloaded from [http://mdk.linux.org.tw/~jserv/openmoko/openmoko-emulator-win32-bin-20070625.zip openmoko-emulator-win32-bin-20070625.zip] ([http://snakesoftruth.com/openmoko-emulator-win32-bin-20070625.zip or a mirror here]). Tested on MS Windows XP and Vista Business.		Win32 binaries shipped with firmware can be downloaded from [http://mdk.linux.org.tw/~jserv/openmoko/openmoko-emulator-win32-bin-20070625.zip openmoko-emulator-win32-bin-20070625.zip] ([http://snakesoftruth.com/openmoko-emulator-win32-bin-20070625.zip or a mirror here]). Tested on MS Windows XP and Vista Business.
		+
		+	== Convenient Scripts ==
		+
		+	* openmoko/qemu-auto.sh
		+
		+	launches qemu and opens a unix socket for communication. All additional parameters are passed to qemu. (e.g. openmoko/qemu-auto.sh -nographic launches the virtual machine with no graphics etc.).
		+
		+	* 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.
		+
		+	* openmoko/qemu-quit.sh
		+
		+	powers the VM down cleanly.
		+
		+	* openmoko/qemu-gadget.sh
		+
		+	attempts to connect target's S3C USB slave to host's dummy HCD (if present and gadgetfs is mounted).

	== Requirements ==		== Requirements ==

← Older revision		Revision as of 12:32, 14 March 2008
Line 130:		Line 130:

	Now on the host computer side, you should be able to "ping 192.168.68.2" and "ssh root@192.168.68.2".		Now on the host computer side, you should be able to "ping 192.168.68.2" and "ssh root@192.168.68.2".
		+
		+	==Setting up Internet connection for your qemu neo:==
		+
		+	(I assume that your local ip-adress is 192.168.0.100 and your router is 192.168.0.1)
		+
		+	In qemu terminal (or via ssh) type:
		+
		+	<pre>
		+	$ ifdown usb0
		+	$ route add default gw 192.168.68.1
		+	</pre>
		+
		+	Edit /etc/resolv.conf:
		+	nameserver 192.168.0.1
		+
		+	On the host-computer type:
		+
		+	<pre>
		+	$ echo 1 >> /proc/sys/net/ipv4/ip_forward
		+	$ echo 1 >> /proc/sys/net/ipv4/ip_dynaddr
		+
		+	$ modprobe ip_tables
		+	$ modprobe iptable_nat
		+	$ modprobe ipt_MASQUERADE
		+
		+	$ iptables -t filter -F
		+	$ iptables -t nat -F
		+
		+	$ iptables -t filter -P INPUT ACCEPT
		+	$ iptables -t filter -P FORWARD ACCEPT
		+	$ iptables -t filter -P OUTPUT ACCEPT
		+	$ iptables -t nat -P PREROUTING ACCEPT
		+	$ iptables -t nat -P POSTROUTING ACCEPT
		+
		+	$ iptables -t nat -A POSTROUTING -o eth0 -s 192.168.68.0/24 -j MASQUERADE
		+	</pre>
		+
		+	(Where eth0 is your network interface connected to the router)
		+
		+	Thats it - now you can enjoy internet in qemu.

	== Setting up USB connection ==		== Setting up USB connection ==

@@ Line 76: / Line 76: @@
 === Using MokoMakefile ===
-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 [[MokoMakefile#QEMU|MokoMakefile]] for details.
+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.
 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).

@@ Line 76: / Line 76: @@
 === Using MokoMakefile ===
-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 [[MokoMakefile#QEMU|MokoMakefile]] for details. ([[MokoMakefile#QEMU|Installation instructions]])
+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 [[MokoMakefile#QEMU|MokoMakefile]] for details.
 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).

@@ Line 123: / Line 123: @@
 == Simple network connection with pppd ==
-One simple way to get a network connection from the emulated Neo is via an emulated serial port and [[pppd]]. Add ''-serial vc -serial pty'' to the QEMU command line, and QEMU prints a device name on a line like "char device redirected to /dev/pts/12".
+One simple way to get a network connection from the emulated Neo is via an emulated serial port and [[pppd]]. Add ''-serial vc -serial pty'' to the [[QEMU command line]], and QEMU prints a device name on a line like "char device redirected to /dev/pts/12".
 On the Neo side, open a terminal and run the command "pppd nodetach debug /dev/ttySAC1".