User's Manual

www.openmoko.com
29
QEMU has *tons* of commandline switches and things that can be
configured. You can look them up in QEMU user docs. You will probably
want to use the "-snapshot" switch, among other ones. Saving and
restoring emulation state at any point (unrelated to "-snapshot") should
work as per QEMU user docs too. In addition the monitor commands "help"
and "info" are of great help. The monitor usually sits in second virtual
console, thus ctrl-alt-2 and ctrl-alt-1 switch to monitor and back.
Pre-built binaries
Win32 binaries shipped with firmware can be downloaded from
openmoko-emulator-win32-bin-20070625.zip (or a mirror here). Tested
on MS Windows XP and Vista Business.
Requirements
This QEMU tree has only been tested on GNU/Linux. To get graphical (not
counting VNC) and/or audio output from the emulator you will need either
SDL or Cocoa installed on your computer. To enable audio, see the
available switches to the ./configure script.
The scripts that sit in openmoko/ require lynx, wget, python, netpbm and
most GNU base utilities installed in standard locations. The netpbm
package contains tools necessary for bootsplash image conversion.
All of the build-time and run-time requirements listed in QEMU
documentation apply. This includes zlib, etc. On distributions that use
binary packages, remember that you need the packages ending in -dev or
-devel.
QEMU and GNU debugger
QEMU lets you debug operating system kernels and bootloaders like you
debug all other programs. To do this you will need a debugger that
speaks the GDB remote debugging protocol - GDB is the obvious choice.