Openmoko - User contributions [en]

MokoMakefile

2009-01-20T01:32:53Z

Chgros: /* MokoMakefile */

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

MokoMakefile does not install anything into your system (it can and should be started as normal user). MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both Om2008.8 (org.openmoko.asu.stable, openmoko-asu-image) and "Bleeding Edge" (org.openmoko.dev, openmoko-base-image) images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:

<pre>ncurses zlib (or libz) OpenSSL GTK++</pre>

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====

<pre>sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito bzip2
sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04 and and Debian testing/unstable, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo dpkg-reconfigure dash
# Select No when it asks you to install dash as /bin/sh.

# This may be needed only for ASU
sudo apt-get install libxtst-dev</pre>

===== SuSE =====
For building Openmoko on 10.3, you need

<pre>gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man</pre>

For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:

wget [http://download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm http://download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm]
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

===== Mandriva =====

<pre>urpmi git help2man diffstat texi2html texinfo</pre>

(Tested with Mandriva 2009.0. <tt>kernel-desktop-devel</tt> of the current kernel is installed in advance, which installs compilers, binutils and many other general compilation tools.)

==== For all distributions ====

As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:

<pre>ENABLE_BINARY_LOCALE_GENERATION = "0"</pre>

===== Proxy =====

Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like):

<pre>mkdir ~/moko ; cd ~/moko</pre>

If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter.
If you ever want to move your $OMDIR to another location, you must run

<pre>make clobber ; make setup</pre>

to reinitialize the environment. Yes, this will take a long time, so choose $OMDIR carefully.

=== MokoMakefile ===

Grab MokoMakefile:

wget [http://www.rwhitby.net/files/openmoko/Makefile http://www.rwhitby.net/files/openmoko/Makefile]

If that doesn't work, try

wget [http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile]

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===

If you want to make the "Bleeding Edge" (org.openmoko.dev, openmoko-base-image) image instead of the Om2008.8 image, see [[Distributions]], you need to edit your Makefile. Read the top of the Makefile for details.

Note that if you want to build FSO, you should use the FSO Makefile at http://downloads.freesmartphone.org rather than the MokoMakefile.

Set up the environment with:

<pre>make setup</pre>

If you are building for the Neo1973 GTA01, then also do this

<pre>make setup-machine-om-gta01</pre>

If you are building for the FreeRunner GTA02, then also do this

<pre>make setup-machine-om-gta02</pre>

=== Building ===

Before starting a lengthy make process, check the [[#Tips|Tips]] section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment.

<pre>make image</pre>

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/glibc/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==

For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:

<pre>make update-makefile</pre>

Be aware that any changes you previously made to the Makefile (like the git branch to use) are lost when executing ''update-makefile''.

2 - To make sure that any recent changes to the build directory structure have been applied:

<pre>make setup</pre>

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:

<pre>make update</pre>

A quick way to rebuild a new image with the latest updates:

<pre>make update-makefile && make setup update image</pre>

==Build issues==

First, make sure that the problem is reproducible after running

<pre>make update-makefile && make setup && make update</pre>

then run

<pre>make clean-package-<foo></pre>

(where you replace <foo> with the name of the package which is failing)

and finally

<pre>make image</pre>

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory. You can then [[Flashing the Neo FreeRunner|flash these]].

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it in the Openmoko development Trac at https://docs.openmoko.org/trac/wiki/NewTicket or in #openmoko on [[Development_resources#IRC|IRC]]. If bitbake has started to run, then it's almost guaranteed that the problem is in the OE build recipes, *not* in the MokoMakefile itself (which is just a convenience wrapper around the OpenEmbedded build system). Please do not report build recipe errors to the MokoMakefile author.

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.

<pre>`env | grep -Ev '^(SHELL|TERM|OLDPWD|USER|USERNAME|PATH|EDITOR|LANG|HOME|DISPLAY|_)=' \
| sed 's/^$.*$=.*/unset \1/'`</pre>

(you must include the backticks).

Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current Ubuntu/Debian unstable/testing boxes another trick is necessary. glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:

<pre>sudo sysctl -w vm.mmap_min_addr=0</pre>

Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.

To re-enable this check do the following:

<pre>sudo sysctl -w vm.mmap_min_addr=65536</pre>

See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===

==== SVN Server Certificate Errors ====

If you get an error like the following:

<pre>NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently?
svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin':
Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:

<pre>cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>"NameError: global name 'log' is not defined"</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

=== Fixes for distribution/environment-specific or isolated issues ===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==

* Make sure umask is set to 0022 before you run "make setup"
* If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
<pre>rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package></pre>
After that your build might just work again.

* For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
<pre>PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"</pre>

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
<pre>GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"</pre>

* To not build any binary locales at all, add this to local.conf:
<pre>ENABLE_BINARY_LOCALE_GENERATION = "0"</pre>

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building the whole <code>image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===

Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make image : build the full development image

; make tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-om-gta01 : setup for GTA01 version of Neo1973

; make setup-machine-om-gta02 : setup for GTA02 version of FreeRunner

; make build-package-package-index : Rebuild the package index

== Developing with MokoMakefile ==

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

<pre>cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the
# quilt series file there</pre>

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

<pre>make build-qemu
make flash-qemu-local
make run-qemu</pre>

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

<pre>cd $OMDIR/build
. ../setup-env
bitbake -c patch openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake -c compile openmoko-messages
bitbake -c build openmoko-messages</pre>

Note: The compile step is only necessary if you already had the package compiled before patching it.

Note: if you just use <tt>bitbake openmoko-messages</tt> it will remove the sources after building!

Note: You can use the '-f' switch to force a command to be run (e.g. ''bitbake -f -c compile openmoko-messages'' to force a compile run.

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:

<pre>cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb</pre>

The file should have the following content:

<pre>DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"</pre>

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do

<pre>$OMDIR/openmoko $ quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb</pre>

Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run

<pre>quilt refresh
cd ..
make update image</pre>

And if everything's alright you should now have an Openmoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

== Testimonials ==

MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", "make openmoko-devel-image :) - no magic there", and "I have never been able to get a build to complete in the pure OE environment, whereas Mokomakefile for some reason builds fine."

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Application Developer]]
[[Category:System Developers]]

MokoMakefile

2009-01-20T01:31:57Z

Chgros: /* SuSE */

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

MokoMakefile does not install anything into your system (it can and should be started as normal user). MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both Om2008.8 (org.openmoko.asu.stable, openmoko-asu-image) and "Bleeding Edge" (org.openmoko.dev, openmoko-base-image) images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:

<pre>ncurses zlib (or libz) OpenSSL GTK++</pre>

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====

<pre>sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito bzip2
sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04 and and Debian testing/unstable, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo dpkg-reconfigure dash
# Select No when it asks you to install dash as /bin/sh.

# This may be needed only for ASU
sudo apt-get install libxtst-dev</pre>

===== SuSE =====
For building Openmoko on 10.3, you need

<pre>gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man</pre>

For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:

wget [http://download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm http://download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm]
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

===== Mandriva =====

<pre>urpmi git help2man diffstat texi2html texinfo</pre>

(Tested with Mandriva 2009.0. <tt>kernel-desktop-devel</tt> of the current kernel is installed in advance, which installs compilers, binutils and many other general compilation tools.)

==== For all distributions ====

As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:

<pre>ENABLE_BINARY_LOCALE_GENERATION = "0"</pre>

===== Proxy =====

Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like):

<pre>mkdir ~/moko ; cd ~/moko</pre>

If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter.
If you ever want to move your $OMDIR to another location, you must run

<pre>make clobber ; make setup</pre>

to reinitialize the environment. Yes, this will take a long time, so choose $OMDIR carefully.

=== MokoMakefile ===

Grab MokoMakefile:

<pre>wget http://www.rwhitby.net/files/openmoko/Makefile</pre>

If that doesn't work, try

<pre>wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile</pre>

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===

If you want to make the "Bleeding Edge" (org.openmoko.dev, openmoko-base-image) image instead of the Om2008.8 image, see [[Distributions]], you need to edit your Makefile. Read the top of the Makefile for details.

Note that if you want to build FSO, you should use the FSO Makefile at http://downloads.freesmartphone.org rather than the MokoMakefile.

Set up the environment with:

<pre>make setup</pre>

If you are building for the Neo1973 GTA01, then also do this

<pre>make setup-machine-om-gta01</pre>

If you are building for the FreeRunner GTA02, then also do this

<pre>make setup-machine-om-gta02</pre>

=== Building ===

Before starting a lengthy make process, check the [[#Tips|Tips]] section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment.

<pre>make image</pre>

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/glibc/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==

For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:

<pre>make update-makefile</pre>

Be aware that any changes you previously made to the Makefile (like the git branch to use) are lost when executing ''update-makefile''.

2 - To make sure that any recent changes to the build directory structure have been applied:

<pre>make setup</pre>

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:

<pre>make update</pre>

A quick way to rebuild a new image with the latest updates:

<pre>make update-makefile && make setup update image</pre>

==Build issues==

First, make sure that the problem is reproducible after running

<pre>make update-makefile && make setup && make update</pre>

then run

<pre>make clean-package-<foo></pre>

(where you replace <foo> with the name of the package which is failing)

and finally

<pre>make image</pre>

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory. You can then [[Flashing the Neo FreeRunner|flash these]].

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it in the Openmoko development Trac at https://docs.openmoko.org/trac/wiki/NewTicket or in #openmoko on [[Development_resources#IRC|IRC]]. If bitbake has started to run, then it's almost guaranteed that the problem is in the OE build recipes, *not* in the MokoMakefile itself (which is just a convenience wrapper around the OpenEmbedded build system). Please do not report build recipe errors to the MokoMakefile author.

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.

<pre>`env | grep -Ev '^(SHELL|TERM|OLDPWD|USER|USERNAME|PATH|EDITOR|LANG|HOME|DISPLAY|_)=' \
| sed 's/^$.*$=.*/unset \1/'`</pre>

(you must include the backticks).

Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current Ubuntu/Debian unstable/testing boxes another trick is necessary. glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:

<pre>sudo sysctl -w vm.mmap_min_addr=0</pre>

Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.

To re-enable this check do the following:

<pre>sudo sysctl -w vm.mmap_min_addr=65536</pre>

See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===

==== SVN Server Certificate Errors ====

If you get an error like the following:

<pre>NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently?
svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin':
Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:

<pre>cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>"NameError: global name 'log' is not defined"</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

=== Fixes for distribution/environment-specific or isolated issues ===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==

* Make sure umask is set to 0022 before you run "make setup"
* If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
<pre>rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package></pre>
After that your build might just work again.

* For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
<pre>PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"</pre>

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
<pre>GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"</pre>

* To not build any binary locales at all, add this to local.conf:
<pre>ENABLE_BINARY_LOCALE_GENERATION = "0"</pre>

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building the whole <code>image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===

Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make image : build the full development image

; make tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-om-gta01 : setup for GTA01 version of Neo1973

; make setup-machine-om-gta02 : setup for GTA02 version of FreeRunner

; make build-package-package-index : Rebuild the package index

== Developing with MokoMakefile ==

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

<pre>cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the
# quilt series file there</pre>

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

<pre>make build-qemu
make flash-qemu-local
make run-qemu</pre>

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

<pre>cd $OMDIR/build
. ../setup-env
bitbake -c patch openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake -c compile openmoko-messages
bitbake -c build openmoko-messages</pre>

Note: The compile step is only necessary if you already had the package compiled before patching it.

Note: if you just use <tt>bitbake openmoko-messages</tt> it will remove the sources after building!

Note: You can use the '-f' switch to force a command to be run (e.g. ''bitbake -f -c compile openmoko-messages'' to force a compile run.

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:

<pre>cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb</pre>

The file should have the following content:

<pre>DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"</pre>

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do

<pre>$OMDIR/openmoko $ quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb</pre>

Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run

<pre>quilt refresh
cd ..
make update image</pre>

And if everything's alright you should now have an Openmoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

== Testimonials ==

MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", "make openmoko-devel-image :) - no magic there", and "I have never been able to get a build to complete in the pure OE environment, whereas Mokomakefile for some reason builds fine."

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Application Developer]]
[[Category:System Developers]]

Duke Nukem 3D

2008-10-25T20:08:54Z

Chgros:

Legendary First Person Shooter. Rafa shared a simple duke nukem 3d port for Neo which can be played using the accelerometer :)

* opkg install http://alasal.be/openmoko/repo/duke3d_0.1.1_armv4t.ipk
* [http://onlinedev.blogspot.com/2008/09/getting-duke-nukem-3d-on-your-neo.html HOWTO] about the package.
* Files: http://fz.hobby-site.org/om/duke-nukem-3d/
* Instructions: http://fz.hobby-site.org/om/duke-nukem-3d/readme-openmoko.txt
* Source Code released:http://fz.hobby-site.org/om/duke-nukem-3d/
* Instructions schematics: http://fz.hobby-site.org/om/duke-nukem-3d/how-to-play-duke.png
* Demo: http://www.youtube.com/watch?v=260Kpiqv9_U

Note: Game will not run if you don't have accelerometers working properly (check with 'hexdump /dev/input/event2' and 'hexdump /dev/input/event3'. Also make sure PulseAudio isn't running: '/etc/init.d/pulseaudio stop', otherwise it will cause the following error: some people have reported that it will not run resulting in the error 'Unknown multivoc error' even when PulseAudio is not installed - waiting on a workaround. To use game without sound, edit ~/.duke3d/duke3d.cfg and change FXDevice = 0 to FXDevice = 13 under [Sound Setup]

[[User:Chgros|Charles-Henri]]'s version:
* http://charles-henri.org/duke3d_1.0-r1_armv4t.opk
* http://charles-henri.org/duke3d-source.tar.gz
* http://charles-henri.org/Xglamo

The buttons are:
jump escape
prev weapon next weapon
open/accept fire

In menus, click to the left to go back.
In y/n menus, click "open" to accept / "escape" to cancel.
Saving / loading should work; to save, select a slot, use jump, prev weapon or next weapon to add a dummy name, then press accept.

The Xglamo binary fixes [http://docs.openmoko.org/trac/ticket/1244 this bug].

<onlyinclude>
{{ApplicationBox|
Name=[[Duke Nukem 3D]]|
Screenshot=Duke3d-openmoko.png|
Description=Legendary First Person Shooter.|
Homepage=http://maemo.org/downloads/product/OS2008/duke3d/|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:Gaming]]

File:Duke3d-openmoko.png

2008-10-06T18:51:38Z

Chgros: uploaded a new version of "Image:Duke3d-openmoko.png"

Screen shot of Duke Nukem 3D on Neo Freerunner

User:Chgros

2008-10-06T06:32:54Z

Chgros: New page: I'm a software engineer base in San Francisco. I've been hacking at the Duke Nukem 3D openmoko port. Comments / Questions should be sent to charles-henri.gros at m4x dot org

I'm a software engineer base in San Francisco.
I've been hacking at the [[Duke Nukem 3D]] openmoko port.

Comments / Questions should be sent to charles-henri.gros at m4x dot org

Duke Nukem 3D

2008-10-06T06:32:44Z

Chgros:

Legendary First Person Shooter. Rafa shared a simple duke nukem 3d port for Neo which can be played using the accelerometer :)

* opkg install http://alasal.be/openmoko/repo/duke3d_0.1.1_armv4t.ipk
* [http://onlinedev.blogspot.com/2008/09/getting-duke-nukem-3d-on-your-neo.html HOWTO] about the package.
* Files: http://fz.hobby-site.org/om/duke-nukem-3d/
* Instructions: http://fz.hobby-site.org/om/duke-nukem-3d/readme-openmoko.txt
* Instructions schematics: http://fz.hobby-site.org/om/duke-nukem-3d/how-to-play-duke.png
* Demo: http://www.youtube.com/watch?v=260Kpiqv9_U

Note: Game will not run if you don't have accelerometers working properly (check with 'hexdump /dev/input/event2' and 'hexdump /dev/input/event3'. Also make sure PulseAudio isn't running: '/etc/init.d/pulseaudio stop', otherwise it will cause the following error: some people have reported that it will not run resulting in the error 'Unknown multivoc error' even when PulseAudio is not installed - waiting on a workaround. To use game without sound, edit ~/.duke3d/duke3d.cfg and change FXDevice = 0 to FXDevice = 13 under [Sound Setup]

[[User:Chgros|Charles-Henri]]'s version:
* http://charles-henri.org/duke3d_1.0-r1_armv4t.opk
* http://charles-henri.org/duke3d-source.tar.gz
* http://charles-henri.org/Xglamo

The buttons are:
jump escape
prev weapon next weapon
open/accept fire

In menus, click to the left to go back.
In y/n menus, click "open" to accept / "escape" to cancel.
Saving / loading should work; to save, select a slot, use jump, prev weapon or next weapon to add a dummy name, then press accept.

The Xglamo binary fixes [http://docs.openmoko.org/trac/ticket/1244 this bug].

<onlyinclude>
{{ApplicationBox|
Name=[[Duke Nukem 3D]]|
Screenshot=Duke3d-openmoko.png|
Description=Legendary First Person Shooter.|
Homepage=http://maemo.org/downloads/product/OS2008/duke3d/|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:Gaming]]

Duke Nukem 3D

2008-10-06T00:37:14Z

Chgros:

Legendary First Person Shooter. Rafa shared a simple duke nukem 3d port for Neo which can be played using the accelerometer :)

* opkg install http://alasal.be/openmoko/repo/duke3d_0.1.1_armv4t.ipk
* [http://onlinedev.blogspot.com/2008/09/getting-duke-nukem-3d-on-your-neo.html HOWTO] about the package.
* Files: http://fz.hobby-site.org/om/duke-nukem-3d/
* Instructions: http://fz.hobby-site.org/om/duke-nukem-3d/readme-openmoko.txt
* Instructions schematics: http://fz.hobby-site.org/om/duke-nukem-3d/how-to-play-duke.png
* Demo: http://www.youtube.com/watch?v=260Kpiqv9_U

Note: Game will not run if you don't have accelerometers working properly (check with 'hexdump /dev/input/event2' and 'hexdump /dev/input/event3'. Also make sure PulseAudio isn't running: '/etc/init.d/pulseaudio stop', otherwise it will cause the following error: some people have reported that it will not run resulting in the error 'Unknown multivoc error' even when PulseAudio is not installed - waiting on a workaround. To use game without sound, edit ~/.duke3d/duke3d.cfg and change FXDevice = 0 to FXDevice = 13 under [Sound Setup]

Charles-Henri's version:
* http://charles-henri.org/duke3d
* http://charles-henri.org/duke3d.cfg
* http://charles-henri.org/Xglamo
* http://charles-henri.org/duke3d.tar.gz

The buttons are:
jump escape
prev weapon next weapon
open/accept fire

In menus, click to the left to go back.
In y/n menus, click "open" to accept / "escape" to cancel.
Saving / loading should work; to save, select a slot, use jump, prev weapon or next weapon to add a dummy name, then press accept.

The Xglamo binary fixes [http://docs.openmoko.org/trac/ticket/1244 this bug].

You'll also need to copy the provided duke3d.cfg in ~/.duke3d

<onlyinclude>
{{ApplicationBox|
Name=[[Duke Nukem 3D]]|
Screenshot=Duke3d-openmoko.png|
Description=Legendary First Person Shooter.|
Homepage=http://maemo.org/downloads/product/OS2008/duke3d/|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:Gaming]]

File:Duke3d-openmoko.png

2008-10-06T00:36:41Z

Chgros: Screen shot of Duke Nukem 3D on Neo Freerunner

Screen shot of Duke Nukem 3D on Neo Freerunner

Duke Nukem 3D

2008-10-05T23:30:08Z

Chgros:

Legendary First Person Shooter. Rafa shared a simple duke nukem 3d port for Neo which can be played using the accelerometer :)

* opkg install http://alasal.be/openmoko/repo/duke3d_0.1.1_armv4t.ipk
* [http://onlinedev.blogspot.com/2008/09/getting-duke-nukem-3d-on-your-neo.html HOWTO] about the package.
* Files: http://fz.hobby-site.org/om/duke-nukem-3d/
* Instructions: http://fz.hobby-site.org/om/duke-nukem-3d/readme-openmoko.txt
* Instructions schematics: http://fz.hobby-site.org/om/duke-nukem-3d/how-to-play-duke.png
* Demo: http://www.youtube.com/watch?v=260Kpiqv9_U

Note: Game will not run if you don't have accelerometers working properly (check with 'hexdump /dev/input/event2' and 'hexdump /dev/input/event3'. Also make sure PulseAudio isn't running: '/etc/init.d/pulseaudio stop', otherwise it will cause the following error: some people have reported that it will not run resulting in the error 'Unknown multivoc error' even when PulseAudio is not installed - waiting on a workaround. To use game without sound, edit ~/.duke3d/duke3d.cfg and change FXDevice = 0 to FXDevice = 13 under [Sound Setup]

Charles-Henri's version:
* http://charles-henri.org/duke3d
* http://charles-henri.org/duke3d.cfg
* http://charles-henri.org/Xglamo
* http://charles-henri.org/duke3d.tar.gz

The buttons are:
jump escape
prev weapon next weapon
open/accept fire

In menus, click to the left to go back.
In y/n menus, click "open" to accept / "escape" to cancel.
Saving / loading should work; to save, select a slot, use jump, prev weapon or next weapon to add a dummy name, then press accept.

The Xglamo binary fixes [http://docs.openmoko.org/trac/ticket/1244 this bug].

You'll also need to copy the provided duke3d.cfg in ~/.duke3d

<onlyinclude>
{{ApplicationBox|
Name=[[Duke Nukem 3D]]|
Screenshot=No-screenshot.png|
Description=Legendary First Person Shooter.|
Homepage=http://maemo.org/downloads/product/OS2008/duke3d/|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:Gaming]]

Duke Nukem 3D

2008-10-05T23:26:46Z

Chgros:

Legendary First Person Shooter. Rafa shared a simple duke nukem 3d port for Neo which can be played using the accelerometer :)

* opkg install http://alasal.be/openmoko/repo/duke3d_0.1.1_armv4t.ipk
* [http://onlinedev.blogspot.com/2008/09/getting-duke-nukem-3d-on-your-neo.html HOWTO] about the package.
* Files: http://fz.hobby-site.org/om/duke-nukem-3d/
* Instructions: http://fz.hobby-site.org/om/duke-nukem-3d/readme-openmoko.txt
* Instructions schematics: http://fz.hobby-site.org/om/duke-nukem-3d/how-to-play-duke.png
* Demo: http://www.youtube.com/watch?v=260Kpiqv9_U

Note: Game will not run if you don't have accelerometers working properly (check with 'hexdump /dev/input/event2' and 'hexdump /dev/input/event3'. Also make sure PulseAudio isn't running: '/etc/init.d/pulseaudio stop', otherwise it will cause the following error: some people have reported that it will not run resulting in the error 'Unknown multivoc error' even when PulseAudio is not installed - waiting on a workaround. To use game without sound, edit ~/.duke3d/duke3d.cfg and change FXDevice = 0 to FXDevice = 13 under [Sound Setup]

Charles-Henri's version:
* http://charles-henri.org/duke3d
* http://charles-henri.org/Xglamo
* http://charles-henri.org/duke3d.tar.gz

The buttons are:
jump escape
prev weapon next weapon
open/accept fire

In menus, click to the left to go back.
In y/n menus, click "open" to accept / "escape" to cancel.
Saving / loading should work; to save, select a slot, use jump, prev weapon or next weapon to add a dummy name, then press accept.

<onlyinclude>
{{ApplicationBox|
Name=[[Duke Nukem 3D]]|
Screenshot=No-screenshot.png|
Description=Legendary First Person Shooter.|
Homepage=http://maemo.org/downloads/product/OS2008/duke3d/|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:Gaming]]

MokoMakefile

2008-08-11T05:29:53Z

Chgros: /* Developing with MokoMakefile */ Build an application while keeping its sources

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

Unlike the manual process described at [[Building Openmoko from scratch]], MokoMakefile does not install anything into your system (it can and should be started as normal user).
MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both OM-2007.2 and QTopia-X11 images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:
ncurses zlib (or libz) OpenSSL GTK++

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====
sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito

sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh

# This may be needed only for ASU
sudo apt-get install libxtst-dev

===== SuSE =====
For building Openmoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

==== For all distributions ====
As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:
ENABLE_BINARY_LOCALE_GENERATION = "0"

===== Proxy =====
Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):
mkdir ~/moko ; cd ~/moko

=== MokoMakefile ===
Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===
If you want to make the ASU or FSO instead of the OM2007.2, see [[Distributions]], you need to edit your Makefile. Change OM_GIT_BRANCH to one of the following:
OM_GIT_BRANCH := org.openmoko.dev # OM2007.2 (enabled by default)
OM_GIT_BRANCH := org.openmoko.asu.dev # ASU
OM_GIT_BRANCH := org.openmoko.asu.stable # ASU stable
OM_GIT_BRANCH := org.openembedded.dev # FSO

Set up the environment with:

make setup

If you are building for the Neo1973 GTA01, then also do this
make setup-machine-neo
If you are building for the Freerunner GTA02, then also do this
make setup-machine-freerunner

=== Building ===
Before starting a lengthy make process, check the [[#Tips|Tips]] section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image
(or use "make openmoko-qtopia-x11-image" if you're building the ASU)
(or use "make fso-image" if you're building the FSO)

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To make sure that any recent changes to the build directory structure have been applied:
make setup

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:
make update

A quick way to rebuild a new image with the latest updates:
make update-makefile && make setup update openmoko-devel-image

==Build issues==
First, make sure that the problem is reproducible after running

make update-makefile && make setup && make update

then run

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

and finally

make openmoko-devel-image

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.
You can then [[Flashing openmoko|flash these]].

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [[Development_resources#IRC|IRC]].

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.
`env | grep -Ev '^(SHELL|TERM|OLDPWD|USER|USERNAME|PATH|EDITOR|LANG|HOME|DISPLAY|_)=' \
| sed 's/^$.*$=.*/unset \1/'`

(you must include the backticks).
Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current Ubuntu boxes another trick is necessary:
glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:
sudo sysctl -w vm.mmap_min_addr=0
Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.
To re-enable this check do the following:
sudo sysctl -w vm.mmap_min_addr=65536
See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===
==== SVN Server Certificate Errors ====
If you get an error like the following:
<pre>
NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin': Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)
</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:
<pre>
cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -
</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>
"NameError: global name 'log' is not defined"
</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

===Fixes for distribution/environment-specific or isolated issues===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==
*Make sure umask is set to 0022 before you run "make setup"

*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly. As of 10/16/07, this appears to be present in local.conf by default.

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"

* To not build any binary locales at all, add this to local.conf:
ENABLE_BINARY_LOCALE_GENERATION = "0"

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building <code>openmoko-devel-image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make openmoko-devel-image : build the full development image

; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make openmoko-toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-neo : setup for GTA01 version of Neo1973

; make setup-machine-freerunner : setup for GTA02 version of Freerunner

==Developing with MokoMakefile==

{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR/build
. ../setup-env
bitbake -c patch openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake -c build openmoko-messages

Note: if you just use <tt>bitbake openmoko-messages</tt> it will remove the sources after building!

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update openmoko-devel-image

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

==Testimonials==
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Openmoko]]
[[Category:Applications]]
[[Category:Application Developer]]

MokoMakefile

2008-08-10T01:39:57Z

Chgros: /* Building */

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

Unlike the manual process described at [[Building Openmoko from scratch]], MokoMakefile does not install anything into your system (it can and should be started as normal user).
MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both OM-2007.2 and QTopia-X11 images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:
ncurses zlib (or libz) OpenSSL GTK++

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====
sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito

sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh

# This may be needed only for ASU
sudo apt-get install libxtst-dev

===== SuSE =====
For building Openmoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

==== For all distributions ====
As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:
ENABLE_BINARY_LOCALE_GENERATION = "0"

===== Proxy =====
Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):
mkdir ~/moko ; cd ~/moko

=== MokoMakefile ===
Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===
If you want to make the ASU or FSO instead of the OM2007.2, see [[Distributions]], you need to edit your Makefile. Change OM_GIT_BRANCH to one of the following:
OM_GIT_BRANCH := org.openmoko.dev # OM2007.2 (enabled by default)
OM_GIT_BRANCH := org.openmoko.asu.dev # ASU
OM_GIT_BRANCH := org.openmoko.asu.stable # ASU stable
OM_GIT_BRANCH := org.openembedded.dev # FSO

Set up the environment with:

make setup

If you are building for the Neo1973 GTA01, then also do this
make setup-machine-neo
If you are building for the Freerunner GTA02, then also do this
make setup-machine-freerunner

=== Building ===
Before starting a lengthy make process, check the [[#Tips|Tips]] section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image
(or use "make openmoko-qtopia-x11-image" if you're building the ASU)
(or use "make fso-image" if you're building the FSO)

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To make sure that any recent changes to the build directory structure have been applied:
make setup

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:
make update

A quick way to rebuild a new image with the latest updates:
make update-makefile && make setup update openmoko-devel-image

==Build issues==
First, make sure that the problem is reproducible after running

make update-makefile && make setup && make update

then run

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

and finally

make openmoko-devel-image

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.
You can then [[Flashing openmoko|flash these]].

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [[Development_resources#IRC|IRC]].

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.
`env | grep -Ev '^(SHELL|TERM|OLDPWD|USER|USERNAME|PATH|EDITOR|LANG|HOME|DISPLAY|_)=' \
| sed 's/^$.*$=.*/unset \1/'`

(you must include the backticks).
Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current Ubuntu boxes another trick is necessary:
glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:
sudo sysctl -w vm.mmap_min_addr=0
Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.
To re-enable this check do the following:
sudo sysctl -w vm.mmap_min_addr=65536
See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===
==== SVN Server Certificate Errors ====
If you get an error like the following:
<pre>
NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin': Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)
</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:
<pre>
cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -
</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>
"NameError: global name 'log' is not defined"
</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

===Fixes for distribution/environment-specific or isolated issues===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==
*Make sure umask is set to 0022 before you run "make setup"

*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly. As of 10/16/07, this appears to be present in local.conf by default.

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"

* To not build any binary locales at all, add this to local.conf:
ENABLE_BINARY_LOCALE_GENERATION = "0"

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building <code>openmoko-devel-image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make openmoko-devel-image : build the full development image

; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make openmoko-toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-neo : setup for GTA01 version of Neo1973

; make setup-machine-freerunner : setup for GTA02 version of Freerunner

==Developing with MokoMakefile==

{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR/build
. ../setup-env
bitbake -c unpack openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake openmoko-messages

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update openmoko-devel-image

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

==Testimonials==
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Openmoko]]
[[Category:Applications]]
[[Category:Application Developer]]

Openmoko Local Groups: San Francisco

2008-08-08T06:04:59Z

Chgros:

Are there any other OpenMoko community members here?

{|border=1
!Name
!Skills
!Interest
!Location
!Has Device
!Has Debug Board
|-
|[http://www.asheesh.org/ Asheesh Laroia]
|Programming, sysadminning
|Whatever it takes to enjoy using it every day ;-)
|San Francisco, CA (live and work in the city)
| [[Image: Moko.jpg|center]]
|
|-
|[[User:captain_morgan|Morgan]]
|programming/some hardware
|Hardware development
|Mountain View/Oakland, CA
|
|
|-
|[[User:codyl|J.Cody]]
|programming
|Application development
|Mountain View, CA
|
|
|-
|[[User:csnellman|Carl Snellman]]
|Programming
|Application development/Location based services
|Palo Alto, CA
|
|
|-
|[[User:krid|Dirk Bergstrom]]
|programming
|"Procmail" for incoming calls/messages; GPS tracking
|Mountain View, CA
|
|
|-
|[[User:samhiatt|Sam Hiatt]]
|Application Development
|FOSS, GIS/Navigation, Cartography
|Mountain View, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:xyphus|Marco Barreno]]
|programming
|Power user/app development
|Berkeley, CA
|
|
|-
|[[User:Elektrolott|Lothar]]
|programming
|Waiting for GTA02
|Morgan Hill, CA
|
|
|-
|[[User:rabble|Rabble]]
|programming
|App Development & Geowanking
|San Francisco, CA
|
|
|-
|[[User:rtyler|R. Tyler Ballance]]
|Development
|Mobile Mono Applications
|San Francisco, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:cfl|Cfl]]
|Software/Architecture
|Mobile Applications
|San Jose, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:Pdesai|Pranav]]
|programming, linux, sysadmin.
|Applications, GPS, bluetooth
|Sunnyvale, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:Michaelshiloh|Michael Shiloh]]
|Programmer, teacher
|Developer Relations and Evangelist for OpenMoko
|San Francisco, CA (live and work in the city)
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:Maratgothix|Omar Green]]
|Architect/Technologist
|H/W, S/W, Intelligent services
|San Francisco, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:mgoff|Michael Goff]]
|Software Programmer
|Applications
|San Francisco, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:wisp|Joshua Layne]]
|Programming
|GPS/mapping/location aware apps, intelligent time/date mgmt
|Half Moon Bay, CA
|
|
|-
|[[User:GrecoJava|David Pearson]]
|Software Programmer
|Applications
|Petaluma, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:Rjt|Oldman]]
|Computer/Network Engineer
|System/Network Programming
|Half Moon Bay, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:raels|raels]]
|Programming, Management, Technologist
|Applications, Linux compatible apps -- waiting for next HW release
|Half Moon Bay, CA
|
|
|-
|[[User:jonathan.tsai|Jonathan Tsai]]
|Software Engineering Grad Student [http://west.cmu.edu/ Carnegie Mellon West]<br>Participant of class project MobileAdvisor.org [http://www.mobileadvisor.org/ Join]
|OpenMoko Evaluator
|San Jose, CA
|
|-
|[[User:yochaigal|Yochai Gal]]
|Application Testing
|Linux Admin/Technician
|San Francisco, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:wolfmanjm|Jim Morris]]
|Programming,Networks
|Ruby,remote access
|San Jose, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:Vvaidy|Vijay Vaidyanathan]]
|Programming
|Command Line Phone!
|Los Altos, CA
|Y, FreeRunner
|N
|-
|[[User:WilliamMorgan|William Morgan]]
|programming
|apps, ruby
|San Francisco, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|-
|[[User:Frang|Frang]]
|Software architect, large-scale distributed systems
|A new device to explore possibilities with.
|Palo Alto, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|-
|[[User:mmargushsf|Matthias Margush]]
|Programming
|Application programming, system testing, and documentation.
|San Francisco, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|-
|[[User:ieatlint|Jeffrey Malone]]
|Programming
|app dev
|San Francisco, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|
|-
|[[User:chgros|Charles-Henri Gros]]
|Programming (C/C++ mostly)
|Application development, phone calls
|San Francisco, CA
| [[Image: Moko.jpg|center]] (freerunner)
|

[[Category:Openmoko Local Groups]]

Building FSO

2008-08-06T04:11:10Z

Chgros: /* Mandatory Packages */ Reformat: line breaks, wiki syntax

{{Distributions|FSO}}

'''FSO is an abbreviation for FreeSmartphone.Org'''

[[Image:FSO UI main.png|right|thumb|home screen]]

See [[OpenmokoFramework]] for more information.

And [http://www.freesmartphone.org www.freesmartphone.org]

And also [http://trac.freesmartphone.org trac.freesmartphone.org]

''Note : The following is an essay in order to explain how to build FSO. Please mind the fact that it's a work in progress, done by someone fairly new to Open Embedded.''

''This information is taken as is from [http://wiki.openembedded.net/index.php/OEandYourDistro#Using_OpenEmbedded_on_Linux_systems OpenEmbedded Wiki]. Some commentaries are voluntarily stripped in order to keep this page simple, please look on OE Wiki for more information.''

= Getting Open Embedded =

== Mandatory Packages ==

=== Deb-based distributions ===

apt-get install ccache sed wget cvs subversion git-core monotone coreutils \
unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk

=== rpm-based distributions ===

urpmi python python-devel python-psyco ccache patch m4 sed bison make wget bzip2 \
cvs gawk glibc-devel gcc-c++ subversion sharutils coreutils docbook-utils openjade \
quilt pcre-devel unzip

=== SuSE (9.1/9.2) instructions ===
Install [http://linux01.gwdg.de/apt4rpm/ apt4rpm], then follow Debian instructions.

python-dev and python-spyco are not in suse apt repository. python-spyco is not mandatory, so one can ignore it.
I suppose python-devel (suse) is python-dev (debian).

=== Fedora Core 2/3 ===

yum install python patch m4 sed make docbook* openjade glibc-devel xmlto

=== Fedora Core 4 ===

Apart from the usual (native) development packages like gcc and binutils, you should check that you have the following RPM's installed:

* bison
* ccache (not required, but advised to speed up building)
* docbook* packages
* libpcre
* m4
* make
* openjade
* patch
* PyQt
* python
* python-psyco
* sed
* xmlto
* quilt (not required as OE builds it by itself, but install it if you want to use gquilt)

Use apt, synaptic, up2date or yum to automagically retrieve these packages or download and install them manually (lots of work).

=== Fedora Core 5/6 ===

Commands I used to install OE pre-requisites on FC5/6

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip \
unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl \
docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre \
pcre-devel git quilt groff linuxdoc-tools patch gcc gcc-c++ python-sqlite2 help2man"

or download the metapackage http://www.openembedded.org/dl/packages/rpm/openembedded-essential-1.1-1.noarch.rpm (may be out of date).

then do

su -c "yum localinstall openembedded-essential-1.1-1.noarch.rpm"

=== Fedora 7 ===

This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).

su -c "yum install python m4 make wget curl ftp cvs monotone subversion tar bzip2 gzip \
unzip python-psyco ccache perl texinfo texi2html diffstat openjade docbook-style-dsssl \
docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils pcre \
pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools gcc gcc-c++ help2man"

=== CentOS 4.4 / Red Hat Enterprise Linux 4 ===

yum install bison ccache coreutils cvs docbook-utils gawk git-core monotone \
python quilt rpmlib sed subversion tetex texinfo unzip wget

=== Gentoo instructions ===

emerge -n bitbake psyco ccache patch make sed dev-lang/python m4 bison cvs openjade \
quilt sgmltools-lite docbook-xml-dtd docbook-dsssl-stylesheets xmlto docbook-sgml-utils \
libpcre boost subversion monotone texi2html pysqlite diffstat

=== Ark Linux 2007.1 ===

apt-get install devel-core diffstat texi2html cvs subversion git texinfo psyco monotone \
python-devel python-encodings python-sqlite

=== Arch Linux (Duke) ===

sudo pacman -S psyco ccache patch make sed python m4 bison cvs quilt sgmltools-lite \
docbook-xml xmlto pcre boost monotone jade git texinfo

In Arch Linux the install command is in /bin/install. Since most of Linux distribution assume that install is located in /usr/bin/install, you have to create a symlink:

sudo ln -s /bin/install /usr/bin/install

You can build BitBake by using this PKGBUILD:
pkgname=bitbake
pkgver=1.8.4
pkgrel=1
pkgdesc="A simple tool for task execution derived from Gentoo's portage"
url="http://developer.berlios.de/projects/bitbake/"
arch=('i686')
license=('GPL' 'custom')
depends=('python')
source=(http://download.berlios.de/bitbake/${pkgname}-${pkgver}.tar.gz)
md5sums=('508d9a61c635d469be8facc95151158b')

build() {
cd ${startdir}/src/${pkgname}-${pkgver}
python setup.py install --root=${startdir}/pkg

# Install vim extensions
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/ftdetect/bitbake.vim \
${startdir}/pkg/usr/share/vim/ftplugin/bitbake.vim
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/syntax/bitbake.vim \
${startdir}/pkg/usr/share/vim/syntax/bitbake.vim

# Handle MIT license
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/doc/COPYING.MIT \
${startdir}/pkg/usr/share/licenses/${pkgname}/COPYING.MIT
}

= Repository Checkout =

== Bitbake ==

Go to the base directory of your [[OpenEmbedded]] environment and checkout bitbake:
<pre><nowiki>
$ cd /stuff/
$ svn co svn://svn.berlios.de/bitbake/branches/bitbake-1.8/ bitbake</nowiki></pre>
'''NOTE:''' for proxy handling, see [http://subversion.tigris.org/faq.html#proxy SVN FAQ]

== Open Embedded ==

=== Obtaining OpenEmbedded ===
Next, you'll need to obtain the actual Openembedded database. The OE database store all the OE metadata: build classes, configuration files, and packages. Then you can extract from this database the development branch(es) you want.

The Openembedded database is a [http://www.venge.net/monotone/ Monotone] database, which is the current SCM (Source Code Management) system for Openembedded. You can find monotone binaries and documentation at [http://www.venge.net/monotone/ Monotone official site].

To obtain Openembedded:
# Go to the base directory of your Openembedded environment
$ cd /stuff/
# Download and bunzip2 the OE database snapshot. '''Note: Unfortunately some monotone versions differ in database format. Check [http://www.openembedded.org/snapshots Snapshots] and download the one matching your monotone version.'''
$ wget http://www.openembedded.org/snapshots/OE.mtn.bz2
$ bunzip2 -d OE.mtn.bz2
This is the database you'll be using for all the work.

If you run into a problem at this stage, check to make sure you have version 0.32 (or newer) of monotone installed.

If you get further troubles in using monotone, there are two ways out:

* use the [http://openembedded.org/snapshots/ latest OE snapshot]
* use a static monotone image

Then you can checkout your local copy of the Openembedded tree.
$ cd /stuff
$ mtn --db=/stuff/OE.mtn checkout --branch=org.openembedded.dev
This extracts directories and files relating to the selected branch from the OE.mtn database and places them under <nowiki>/stuff/branchname</nowiki> (i.e. in <nowiki>/stuff/org.openembedded.dev</nowiki> in this guide)

IMPORTANT NOTE ! If mtn complains about an outdated database, you can migrate it using the following command :

<pre><nowiki>
mtn db migrate --db=/stuff/OE.mtn
</nowiki></pre>

You'll then have to do the checkout.
=== Create local configuration ===
It's now time to create your local configuration.
While you could copy the default local.conf.sample like that:

<pre><nowiki>
$ cd /stuff/
$ cp org.openembedded.dev/conf/local.conf.sample build/conf/local.conf
$ vi build/conf/local.conf
</nowiki></pre>

It is actually recommended to start smaller and keep local.conf.sample in the background and add entries from there step-by-step as you understand and need them. Please, do not just edit build/conf/local.conf.sample but actually READ it.

For building a .dev branch, in your <nowiki>local.conf</nowiki> file, you should have at least the following three entries. Example for the Angstrom distribution and the Openmoko gta01 machine:
<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "angstrom-2008.1"
MACHINE = "om-gta01"
</nowiki></pre>

For a Freerunner, using an openmoko distro, you'll do that :

<pre><nowiki>
BBFILES = "/stuff/org.openembedded.dev/packages/*/*.bb"
DISTRO = "openmoko"
MACHINE = "om-gta02"
</nowiki></pre>

Don't forget to include the two following files :

<pre><nowiki>
require conf/distro/include/fso-autorev.inc
require conf/distro/include/moko-autorev.inc
</nowiki></pre>

=== Setup the environment ===
One of the four command sets below will need to be run every time you open a terminal for development. (You can automate this in ~/.profile, /etc/profile, or perhaps use a script to set the necessary variables for using [[BitBake]].)

If you followed the recommendation above to use an uninstalled [[BitBake]]:
<pre><nowiki>
$ export PATH=/stuff/bitbake/bin:$PATH
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

If you installed [[BitBake]]:
<pre><nowiki>
$ export BBPATH=/stuff/build:/stuff/org.openembedded.dev
</nowiki></pre>

Alternative syntax for those using the tcsh shell (e.g FreeBSD):
<pre><nowiki>
$ setenv PATH "/stuff/bitbake/bin:"$PATH
$ setenv BBPATH "/stuff/build:/stuff/org.openembedded.dev:"$BBPATH
</nowiki></pre>

= Start building =

<pre><nowiki>
cd /stuff/build && bitbake fso-image
</nowiki></pre>
[[category:Technical]]
[[Category:Software (non openmoko)]]
[[category:FSO]]

= Configuration =

== GTK ==

Currently GTK is not well supported in the FSO build. To use GTK applications you'll most likely have to install the gtk library, and the Openmoko theme.

'''Step 1) Install the ipk-packages'''

opkg install moko-gtk-theme
opkg install openmoko-icon-theme-standard2

'''Step 2) Enable Theme'''

ln -s /usr/share/themes/Moko/gtk-2.0/gtkrc /etc/gtk-2.0/gtkrc

'''Step 3) Adjust fontsize and set icon theme'''

vi /etc/gtk-2.0/gtkrc

Add the two lines:
gtk-font-name = "Sans 5"
gtk-icon-theme-name="openmoko-standard"

(Thanks to [[User:Jtickle | Jtickle]] for pointing out how to set the font size on the [[Getting_Started_FAQ]]-Page)

MokoMakefile

2008-08-04T02:18:45Z

Chgros: /* Build issues */

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

Unlike the manual process described at [[Building Openmoko from scratch]], MokoMakefile does not install anything into your system (it can and should be started as normal user).
MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both OM-2007.2 and QTopia-X11 images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:
ncurses zlib (or libz) OpenSSL GTK++

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====
sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito

sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh

# This may be needed only for ASU
sudo apt-get install libxtst-dev

===== SuSE =====
For building Openmoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

==== For all distributions ====
As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:
ENABLE_BINARY_LOCALE_GENERATION = "0"

===== Proxy =====
Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):
mkdir ~/moko ; cd ~/moko

=== MokoMakefile ===
Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===
Set up the environment:

make setup

If you want to make the ASU or FSO instead of the OM2007.2, see [[Distributions]], you need to edit your Makefile. Change OM_GIT_BRANCH to one of the following:
OM_GIT_BRANCH := org.openmoko.dev # OM2007.2
OM_GIT_BRANCH := org.openmoko.asu.dev # ASU
OM_GIT_BRANCH := org.openmoko.asu.stable # ASU stable
OM_GIT_BRANCH := org.openembedded.dev # FSO

If you are building for the Neo1973 GTA01, then also do this
make setup-machine-neo
If you are building for the Freerunner GTA02, then also do this
make setup-machine-freerunner

=== Building ===
Before starting a lengthy make process, check the Tips section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image
(or use "make openmoko-qtopia-x11-image" if you're building the ASU)
(or use "make fso-image" if you're building the FSO)

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To make sure that any recent changes to the build directory structure have been applied:
make setup

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:
make update

A quick way to rebuild a new image with the latest updates:
make update-makefile && make setup update openmoko-devel-image

==Build issues==
First, make sure that the problem is reproducible after running

make update-makefile && make setup && make update

then run

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

and finally

make openmoko-devel-image

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.
You can then [[Flashing openmoko|flash these]].

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [[Development_resources#IRC|IRC]].

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.
`env | grep -Ev '^(SHELL|TERM|OLDPWD|USER|USERNAME|PATH|EDITOR|LANG|HOME|DISPLAY|_)=' \
| sed 's/^$.*$=.*/unset \1/'`

(you must include the backticks).
Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current Ubuntu boxes another trick is necessary:
glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:
sudo sysctl -w vm.mmap_min_addr=0
Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.
To re-enable this check do the following:
sudo sysctl -w vm.mmap_min_addr=65536
See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===
==== SVN Server Certificate Errors ====
If you get an error like the following:
<pre>
NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin': Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)
</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:
<pre>
cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -
</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>
"NameError: global name 'log' is not defined"
</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

===Fixes for distribution/environment-specific or isolated issues===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==
*Make sure umask is set to 0022 before you run "make setup"

*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly. As of 10/16/07, this appears to be present in local.conf by default.

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"

* To not build any binary locales at all, add this to local.conf:
ENABLE_BINARY_LOCALE_GENERATION = "0"

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building <code>openmoko-devel-image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make openmoko-devel-image : build the full development image

; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make openmoko-toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-neo : setup for GTA01 version of Neo1973

; make setup-machine-freerunner : setup for GTA02 version of Freerunner

==Developing with MokoMakefile==

{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR/build
. ../setup-env
bitbake -c unpack openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake openmoko-messages

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update openmoko-devel-image

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

==Testimonials==
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Openmoko]]
[[Category:Applications]]
[[Category:Application Developer]]

MokoMakefile

2008-08-04T02:18:11Z

Chgros: /* Build issues */ Minor fixes and improvements (e.g. factored regex)

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

Unlike the manual process described at [[Building Openmoko from scratch]], MokoMakefile does not install anything into your system (it can and should be started as normal user).
MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both OM-2007.2 and QTopia-X11 images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:
ncurses zlib (or libz) OpenSSL GTK++

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====
sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito

sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh

# This may be needed only for ASU
sudo apt-get install libxtst-dev

===== SuSE =====
For building Openmoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

==== For all distributions ====
As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:
ENABLE_BINARY_LOCALE_GENERATION = "0"

===== Proxy =====
Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):
mkdir ~/moko ; cd ~/moko

=== MokoMakefile ===
Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===
Set up the environment:

make setup

If you want to make the ASU or FSO instead of the OM2007.2, see [[Distributions]], you need to edit your Makefile. Change OM_GIT_BRANCH to one of the following:
OM_GIT_BRANCH := org.openmoko.dev # OM2007.2
OM_GIT_BRANCH := org.openmoko.asu.dev # ASU
OM_GIT_BRANCH := org.openmoko.asu.stable # ASU stable
OM_GIT_BRANCH := org.openembedded.dev # FSO

If you are building for the Neo1973 GTA01, then also do this
make setup-machine-neo
If you are building for the Freerunner GTA02, then also do this
make setup-machine-freerunner

=== Building ===
Before starting a lengthy make process, check the Tips section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image
(or use "make openmoko-qtopia-x11-image" if you're building the ASU)
(or use "make fso-image" if you're building the FSO)

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To make sure that any recent changes to the build directory structure have been applied:
make setup

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:
make update

A quick way to rebuild a new image with the latest updates:
make update-makefile && make setup update openmoko-devel-image

==Build issues==
First, make sure that the problem is reproducible after running

make update-makefile && make setup && make update

then run

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

and finally

make openmoko-devel-image

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.
You can then [[Flashing openmoko|flash these]].

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [[Development_resources#IRC|IRC]].

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.
`env | grep -Ev '^(SHELL|TERM|OLDPWD|USER|USERNAME|PATH|EDITOR|LANG|HOME|DISPLAY|_)=' \
| sed 's/^$.*$=.*/unset \1/'`

(you must include the backticks).
Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current Ubuntu boxes another trick is necessary:
glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:
sudo sysctl -w vm.mmap_min_addr=0
Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.
To re-enable this check do the following:
sudo sysctl -w vm.mmap_min_addr=65536
See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===
==== SVN Server Certificate Errors ====
If you get an error like the following:
<pre>
NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin': Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)
</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:
<pre>
cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -
</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>
"NameError: global name 'log' is not defined"
</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

===Fixes for distribution/environment-specific or isolated issues===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==
*Make sure umask is set to 0022 before you run "make setup"

*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly. As of 10/16/07, this appears to be present in local.conf by default.

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"

* To not build any binary locales at all, add this to local.conf:
ENABLE_BINARY_LOCALE_GENERATION = "0"

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building <code>openmoko-devel-image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make openmoko-devel-image : build the full development image

; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make openmoko-toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-neo : setup for GTA01 version of Neo1973

; make setup-machine-freerunner : setup for GTA02 version of Freerunner

==Developing with MokoMakefile==

{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR/build
. ../setup-env
bitbake -c unpack openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake openmoko-messages

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update openmoko-devel-image

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

==Testimonials==
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Openmoko]]
[[Category:Applications]]
[[Category:Application Developer]]

MokoMakefile

2008-08-04T01:58:29Z

Chgros: /* Build issues */

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

Unlike the manual process described at [[Building Openmoko from scratch]], MokoMakefile does not install anything into your system (it can and should be started as normal user).
MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both OM-2007.2 and QTopia-X11 images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:
ncurses zlib (or libz) OpenSSL GTK++

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====
sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito

sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh

# This may be needed only for ASU
sudo apt-get install libxtst-dev

===== SuSE =====
For building Openmoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

==== For all distributions ====
As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:
ENABLE_BINARY_LOCALE_GENERATION = "0"

===== Proxy =====
Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):
mkdir ~/moko ; cd ~/moko

=== MokoMakefile ===
Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===
Set up the environment:

make setup

If you want to make the ASU or FSO instead of the OM2007.2, see [[Distributions]], you need to edit your Makefile. Change OM_GIT_BRANCH to one of the following:
OM_GIT_BRANCH := org.openmoko.dev # OM2007.2
OM_GIT_BRANCH := org.openmoko.asu.dev # ASU
OM_GIT_BRANCH := org.openmoko.asu.stable # ASU stable
OM_GIT_BRANCH := org.openembedded.dev # FSO

If you are building for the Neo1973 GTA01, then also do this
make setup-machine-neo
If you are building for the Freerunner GTA02, then also do this
make setup-machine-freerunner

=== Building ===
Before starting a lengthy make process, check the Tips section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image
(or use "make openmoko-qtopia-x11-image" if you're building the ASU)
(or use "make fso-image" if you're building the FSO)

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To make sure that any recent changes to the build directory structure have been applied:
make setup

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:
make update

A quick way to rebuild a new image with the latest updates:
make update-makefile && make setup update openmoko-devel-image

==Build issues==
First, make sure that the problem is reproducible after running

make update-makefile && make setup && make update

then run

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

and finally

make openmoko-devel-image

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.
You can then [[Flashing openmoko|flash these]].

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [http://wiki.openmoko.org/wiki/Development_resources#IRC IRC].

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.
`env | grep -Ev '^SHELL=|^TERM=|^OLDPWD=|^USER=|^USERNAME=|^PATH=|^EDITOR=|^LANG=|^HOME=|^DISPLAY=|^_=' | sed 's/^$.*$=.*/unset \1/'`

(you must include the backtics).
Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current ubuntu boxes another trick is necessary:
glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:
sudo sysctl -w vm.mmap_min_addr=0
Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.
To re-enable this check do the following:
sudo sysctl -w vm.mmap_min_addr=65536
See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===
==== SVN Server Certificate Errors ====
If you get an error like the following:
<pre>
NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin': Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)
</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:
<pre>
cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -
</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>
"NameError: global name 'log' is not defined"
</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

===Fixes for distribution/environment-specific or isolated issues===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==
*Make sure umask is set to 0022 before you run "make setup"

*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly. As of 10/16/07, this appears to be present in local.conf by default.

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"

* To not build any binary locales at all, add this to local.conf:
ENABLE_BINARY_LOCALE_GENERATION = "0"

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building <code>openmoko-devel-image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make openmoko-devel-image : build the full development image

; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make openmoko-toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-neo : setup for GTA01 version of Neo1973

; make setup-machine-freerunner : setup for GTA02 version of Freerunner

==Developing with MokoMakefile==

{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR/build
. ../setup-env
bitbake -c unpack openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake openmoko-messages

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update openmoko-devel-image

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

==Testimonials==
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Openmoko]]
[[Category:Applications]]
[[Category:Application Developer]]

Keyboard Toggle

2008-07-29T07:04:31Z

Chgros: /* On the phone */ cpp-symlinks means you don't need to ln manually

The [[ASU]] and [[OM2007.2]] Openmoko [[distributions]] have been designed to bring up an on-screen keyboard which supplies keystroke information to applications. However, this requires the cooperation of the application, which is a problem for software designed with another X11 based phone stack in mind, or software which has been quickly ported from Linux desktop systems, because it will never bring up a keyboard for (possibly important) keystroke information. It is also possible that the keyboard could be brought or remain up by accident when you don't want it there, or even software specifically designed with this functionality in mind may occasionally fail or become confused when an on screen keyboard is supposed to be available.

== Alternatives ==
Alternatively, you can try connecting a [[Manually_using_Bluetooth#Being_able_to_use_HID_devices|bluetooth keyboard]] or USB keyboard (Only available with a special cable, or an extra special cable in the case of the older unpowered USB units.)

== Reactivating the keyboard toggle under ASU ==
For advanced users using the [[ASU]] [[Distributions|distribution]], it may be worth your while to change the E17 theme information which prevents the 'qwerty' link in the upper left from showing.

=== On the phone ===
Install the tools required to decompile and recompile E17 theme code.

opkg install libevas-saver-png edje-utils cpp cpp-symlinks libembryo-tests

Decompile the theme, and edit the edc file

cd /usr/share/enlightenment/data/themes
edje_decc illume.edj
cd illume
vi freerunner.edc

Search for the text 'qwerty'. This should take you to the section which defines the small 'qwerty' button in the upper left.

* Under 'part { name: "kbd";' change 'visible 0;' to 'visible 1;', and change 'relative: 1.0 1.0;' to 'relative: 0.0 1.0;'
* Under 'part { name: "kbdtext";' change 'visible 0;' to 'visible 1;'

And then recompile the .edj

sh build.sh
mv illume.edj ../illume.edj

=== Building a custom package ===
If that doesn't work, follow the instructions on [[Mokomakefile|building ASU from source]]. Unpack the source for the package 'illume-theme', edit its edc file using the same method described above, and then finish building the ipk. You should be able to install this ipk, overiding the previous configuration.

=== Upgrading ===
If you upgrade, such as with opkg upgrade, you may have to perform the modification again.

[[Category:Openmoko]]

Keyboard Toggle

2008-07-29T06:57:08Z

Chgros: /* On the phone */ Install cpp-symlinks

The [[ASU]] and [[OM2007.2]] Openmoko [[distributions]] have been designed to bring up an on-screen keyboard which supplies keystroke information to applications. However, this requires the cooperation of the application, which is a problem for software designed with another X11 based phone stack in mind, or software which has been quickly ported from Linux desktop systems, because it will never bring up a keyboard for (possibly important) keystroke information. It is also possible that the keyboard could be brought or remain up by accident when you don't want it there, or even software specifically designed with this functionality in mind may occasionally fail or become confused when an on screen keyboard is supposed to be available.

== Alternatives ==
Alternatively, you can try connecting a [[Manually_using_Bluetooth#Being_able_to_use_HID_devices|bluetooth keyboard]] or USB keyboard (Only available with a special cable, or an extra special cable in the case of the older unpowered USB units.)

== Reactivating the keyboard toggle under ASU ==
For advanced users using the [[ASU]] [[Distributions|distribution]], it may be worth your while to change the E17 theme information which prevents the 'qwerty' link in the upper left from showing.

=== On the phone ===
Install the tools required to decompile and recompile E17 theme code.

opkg install libevas-saver-png edje-utils cpp cpp-symlinks libembryo-tests
ln -s /lib/cpp /usr/bin/cpp

Decompile the theme, and edit the edc file

cd /usr/share/enlightenment/data/themes
edje_decc illume.edj
cd illume
vi freerunner.edc

Search for the text 'qwerty'. This should take you to the section which defines the small 'qwerty' button in the upper left.

* Under 'part { name: "kbd";' change 'visible 0;' to 'visible 1;', and change 'relative: 1.0 1.0;' to 'relative: 0.0 1.0;'
* Under 'part { name: "kbdtext";' change 'visible 0;' to 'visible 1;'

And then recompile the .edj

sh build.sh
mv illume.edj ../illume.edj

=== Building a custom package ===
If that doesn't work, follow the instructions on [[Mokomakefile|building ASU from source]]. Unpack the source for the package 'illume-theme', edit its edc file using the same method described above, and then finish building the ipk. You should be able to install this ipk, overiding the previous configuration.

=== Upgrading ===
If you upgrade, such as with opkg upgrade, you may have to perform the modification again.

[[Category:Openmoko]]

Main Page

2008-07-28T21:17:46Z

Chgros: Linkify Neo Freerunner

__NOTOC__
__NOEDITSECTION__
<div style="margin-top: -70px">{{Languages|Main Page}}</div>
<br>
<DIV ALIGN=center><big>'''[[Openmoko]]™ - Open. Mobile. Free.'''</big><br></DIV>

==<font color=75d806>Introduction to Openmoko</font>==

[[Image:OpenmokoFramework08.png|250px|left|Openmoko Software Stack|thumb]]

[[Openmoko]]™, born as a [http://en.wikipedia.org/wiki/Free_software Free Software] project under [[License| GPL and LGPL license]], is dedicated to delivering an open software stack on mobile platforms. [[Openmoko]] shipped its first product, the Neo 1973, on July 9 2007; and then turned into a start-up company with one aim: create great mobile products using the Openmoko stack: Open. Mobile. Free.

The [[NeoSoftwareStack|Openmoko stack]], which includes a full [[Host-based development with Xoo and Xephyr|X server]], allows users and developers to transform mobile hardware platforms into unique products. Our licence gives developers and users freedom from the "iron to the eyeballs," freedom to cosmetically customize their device or radically remix it; change the wallpaper or rebuild the entire house! It grants them the freedom, for example, to transform a phone into a medical device or point of sale device or the freedom to simply install their own favorite software. Beyond freeing the software on our devices we have also released our CAD files under Creative Commons ShareAlike. By freeing the software under GPL, we enable the community of FOSS developers to "make it new." By freeing the [http://downloads.openmoko.org/CAD/ CAD] files we give industrial designers and engineers this same opportunity.

{{mainpage}}

==<font color=75d806>Openmoko Products</font>==

[[Image:Freerunner02.gif|thumb|150px]]
The first Openmoko product, the [[Neo 1973]], sold exclusively through [http://www.openmoko.com/store.html Openmoko Online Shop]. It sold out in early February 2008.

Openmoko started selling the [[Neo FreeRunner]] (GTA02), the second generation of Neo, on July 3, 2008.
It is available through the
[http://www.openmoko.com/store.html Openmoko Online Shop]
or national distributers.
Group purchases provide a discount and extra goodies.
Find a buying group at [[GroupSales]].
If you've just received your FreeRunner, check out [[Getting Started with your Neo FreeRunner]] for tips.

<div style="clear:both">{{Bar}}</div>

==<font color=75d806>Join Openmoko development</font>==

{| class="wikitable" cellspacing="4" cellpadding="6" width=100%
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | <font color="white" >Developer Guides</font>
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |<font color="white" >Test / Emulation and share project</font>
|-
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
===<font color=white>Developer </font>===
* [[Toolchain|toolchain usage]]
* <font color=white>VMware</font>
* [[Python|python intro]]
* [[Openmoko under QEMU]]

===<font color=white>System Integration and customizing a distribution</font>===
* [[OpenEmbedded|OE-The distribution building framework]]
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]
* [[Opkg|Opkg]]
===<font color=white>Low level / system development</font>===
* <font color=white>Low-Level</font>
* [[u-boot]] <font color=white>-The bootloader we use, including docs to our modifications</font>
* [[kernel]] <font color=white>-The Linux Kernel we use, including docs to our modifications</font>
* [[gsmd]] <font color=white> -the GSM daemon managing the GSM Modem</font>
* [[agpsd]] <font color=white>-the AGPS (Assisted GPS) daemon</font>

|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
===<font color=white>Test</font>===
*[[Test Cases]]
<font color=white> ※</font> [[:Category: Test | See More About Test]]

===<font color=white>Emulation</font>===
*[[Getting Openmoko working on host with Xephyr]]

===<font color=white>Publish your project</font>===
*[[CommunityRepository|Publish Your Project]]
===<font color=white>Distributions</font>===
*[[Distributions]]
|}

==<font color=75d806>Openmoko community</font>==
Anyone can join the Openmoko project and contribute to designing open products. Join us and collaborate through any of the [[Development resources | project resources]], including this Openmoko Wiki. See the [[Help:Contents | wiki editing help]]page for information on making contributions to this wiki.

You can start by using the [[introduction]] page, photos, videos and Openmoko Wiki Official Index Page. As always, the usual [[FAQ | Frequently Asked Questions]] (FAQ), [http://lists.openmoko.org/mailman/listinfo/| mailing list] pages and [[Discussion_Forums| Discussion Forums]] are helpful.

{| class="wikitable" cellspacing="4" cellpadding="6" width=100%
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | <font color="white" >In News</font>
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |<font color="white" >Community & Events</font>
|-
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
===<font color=white>In the News</font>===
*[[Getting Started with your Neo FreeRunner]]
*[[ASU Feature Plan]]
*[[CommunityRepository|Share your project]]
*[[GroupSales]]
*[[Why Openmoko|Why Openmoko is best: A Comparative Look]]
===<font color=white>Snapshot</font>===
*<font color=white>You can always download the latest build here.</font>
** <font color=white>For FreeRunner </font>[http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
** <font color=white>For Neo 1973 the link is</font> [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
** <font color=white>Tools , like dfu-util and openocd :</font>[http://buildhost.openmoko.org/daily/tools/ http://buildhost.openmoko.org/daily/tools/]
*<font color=white>Reviews of the daily snapshot build are [[Snapshot_review|here]] and the recommended kernel and root image from the review will always be available [http://downloads.openmoko.org/recommended/ here].</font>
<font color=white>Note that the recommended set is not always the latest, but is the most stable, reliable, and functional.</font>
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |

===<font color=white> Community Update</font>===
<font color=white>For the latest status updates, see [[Community_Updates|Community Updates]]</font>

<font color=ffffff> ※</font>[[:Category:Community| See More About Community...]]

===<font color=white>Get the overview of wiki</font>===
*<font color=white>To get the overview of Openmoko Wiki, see [[Openmoko Wiki Official Index Page]].</font>
===<font color=white>Events</font>===
*[[Summer of Code 2008]]
*[[Openmoko Education/zh tw]]
*[[Events:FOSDEM 2008]]
*[[OpenLab]]

<font color=ffffff> ※</font>[[:Category:Event| See More About Event...]]

|}

[[Category:Information| ]]

Keyboard Toggle

2008-07-28T04:31:39Z

Chgros: /* On the phone */ Fixed instructions: no illume subdirectory before decompilation

The [[ASU]] and [[OM2007.2]] Openmoko [[distributions]] have been designed to bring up an on-screen keyboard which supplies keystroke information to applications. However, this requires the cooperation of the application, which is a problem for software designed with another X11 based phone stack in mind, or software which has been quickly ported from Linux desktop systems, because it will never bring up a keyboard for (possibly important) keystroke information. It is also possible that the keyboard could be brought or remain up by accident when you don't want it there, or even software specifically designed with this functionality in mind may occasionally fail or become confused when an on screen keyboard is supposed to be available.

== Alternatives ==
Alternatively, you can try connecting a [[Manually_using_Bluetooth#Being_able_to_use_HID_devices|bluetooth keyboard]] or USB keyboard (Only available with a special cable, or an extra special cable in the case of the older unpowered USB units.)

== Reactivating the keyboard toggle under ASU ==
For advanced users using the [[ASU]] [[Distributions|distribution]], it may be worth your while to change the E17 theme information which prevents the 'qwerty' link in the upper left from showing.

=== On the phone ===
Install the tools required to decompile and recompile E17 theme code.

opkg install libevas-saver-png edje-utils cpp
ln -s /lib/cpp /usr/bin/cpp

Decompile the theme, and edit the edc file

cd /usr/share/enlightenment/data/themes
edje_decc illume.edj
cd illume
vi freerunner.edc

Search for the text 'qwerty'. This should take you to the section which defines the small 'qwerty' button in the upper left, which has been disabled by the developers with a 'visible 0' entry. Comment it out, and replace it with 'visible 1'. Then rebuild the theme.

./build.sh

=== Building a custom package ===
If that doesn't work, follow the instructions on [[Mokomakefile|building ASU from source]]. Unpack the source for the package 'illume-theme', edit its edc file using the same method described above, and then finish building the ipk. You should be able to install this ipk, overiding the previous configuration.

=== Upgrading ===
If you upgrade, such as with opkg upgrade, you may have to perform the modification again.

[[Category:Openmoko]]

Flashing the Neo FreeRunner

2008-07-28T01:26:39Z

Chgros: /* Flashing the Kernel */ Short boot to NOR instructions

As Openmoko development continues, Openmoko regularly releases updated versions of the Openmoko root filesystem, the kernel, and the[[Bootloader| U-Boot]]. These may be programmed into the Flash memory of Neo FreeRunner. You can use the USB cable and Openmoko provided tool to flash Neo FreeRunner.

{{note|The Openmoko software team builds images daily. If you want to use the latest images, you can download the image from the daily build, but we recommend you download the most stable image from http://downloads.openmoko.org/releases/Freerunner/. Images here have been tested by the test team.

See [[Latest Images]] for more information about the different images available.}}
{{note|If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]], although it looks like the method on that page may not entirely work.}}

===Download the DFU-util===

==== from GNU/Linux ====

You can download the flashing tool for a GNU/Linux host from:
http://downloads.openmoko.org/releases/Freerunner/dfu-util

On the GNU/Linux host you can use the following command to download the dfu-util:
wget http://downloads.openmoko.org/releases/Freerunner/dfu-util

Afterwards you have to change the rights on the file:
chmod a+x dfu-util

==== from Windows ====

You can download the flashing tool for a Windows host from: [http://projects.openmoko.org/frs/?group_id=166&release_id=162 http://projects.openmoko.org/frs/?group_id=166&release_id=162] (see installation instructions at [[Dfu-util-windows]])

==== Using dfu-util ====

Dfu-util will be used like this, to write an image file to a (predefined) "partition name" (referred to as ''Altsetting'' in dfu-util help/manual) :

./dfu-util -a (partion name) -R -D (download image file name)

{{note| The meaning of the parameters you specified:
-a --alt alt : Specify the Altsetting of the DFU interface by name or by number<br>
-R --reset : Issue USB Reset signalling once we're finished<br>
-D --download file : Write firmware from<file> into device <br>
}}

===Flashing the Kernel===

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:0px solid #ffffff; background:#ffffff; width:100%;floating="center";font-weight: normal; "
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid #ffffff; border:1px solid #ffffff; width:75%;font-weight: normal; " |
<div align="left">
[[Image:menu15.jpg|thumb|Log into U-Boot in NOR Flash, connect your Neo with Linux Host via USB cable]]

The Neo FreeRunner needs to be at the NOR uBoot menu for flashing. For more information on booting, see [[Booting the Neo FreeRunner| booting the Neo Freerunner]] (in short: press and hold aux then power). Log into the NOR uBoot menu and just stay there, do not select or enter any item in menu. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.

'''Then''', connect your Neo to the GNU/Linux or Windows host via USB cable.

You can download the kernel from
http://downloads.openmoko.org/releases/Freerunner/

----
==== from GNU/Linux ====

Type in the following command in the terminal on a GNU/Linux host. On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

sudo ./dfu-util -a kernel -R -D uImage-2.6.24+git20080424-om-gta02.bin

==== from Windows ====

Type in the following command in the console on a Windows host:

dfu-util -a kernel -R -D uImage-2.6.24+git20080424-om-gta02.bin

----

Press Enter to execute the command.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!
</div>
|}

===Flashing the Root Filesystem ===
You can download the root filesystem from:
http://downloads.openmoko.org/releases/Freerunner/

----

==== from GNU/Linux ====

Type the following command in the terminal of a GNU/Linux host. On some systems you will need to be root.

./dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2

==== from Windows ====

Type the following command in the console of a Windows host.

dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2

----

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

=== Flashing u-boot ===
dfu-util -a u-boot -R -D uboot-gta02v5-latest.bin

[[Category:Flashing Openmoko| ]]

Latest Images

2008-07-28T01:18:08Z

Chgros: /* ASU (April|August Software Update) qtopia-based Image */ Prettier link

This page is intended to summarize in one place the various images you can try out on your Openmoko Neo FreeRunner (GTA02) or 1973 (GTA01). Note however, that some of these are works in progress and may not have even released any files yet. Nothing is guaranteed to work. Proceed at your own risk.

;See [[Distributions]] for a chart comparing the features of the various images.

Michael Lauer's blog also has an entry comparing the distributions: [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO? TMTLA!]

Instructions on flashing your FreeRunner or 1973 are provided at [[Flashing the Neo FreeRunner]] and [[Getting Started with your Neo1973]], respectively.
----
==2007.2 GTK Image==
The latest most stable release should reside here:
[http://buildhost.openmoko.org/releases/Freerunner/ http://buildhost.openmoko.org/releases/Freerunner/]

*You can download the latest daily builds here:
**For Neo FreeRunner [http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
***Look for files of the form: Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta02.rootfs.tar.gz
***and: openmoko-devel-image-om-gta02.tar.gz
**For Neo 1973 the link is [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
***Look for files of the form: openmoko-devel-image-om-gta01.tar.gz
***and: Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta01.rootfs.tar.gz
**Tools, like dfu-util and openocd [http://buildhost.openmoko.org/daily/tools/ http://buildhost.openmoko.org/daily/tools/]

Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone]
and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
=== ScaredyCat ===
Users may have heard of "ScaredyCat" images. These are usable images created by [http://blog.automated.it/category/openmoko/ Andy Powell] and are currently based on the 2007.02 software stack.

Hey, all file names are with "gta01" !
Is this an error and they are gta02 (FR) ??

scroll down a bit, or search for gta02 on the page. they're there, just not on the first page. (ozzloy)

http://buildhost.automated.it/OM2007.2/
----

==ASU (April|August Software Update) qtopia-based Image==
There has not been a recommended release of the ASU yet. You may wish to review the [[ASU_Feature_Plan|ASU feature plan]] or some [http://dos.jogger.pl/2008/06/29/asu-to-przyszlosc/ screenshots]

*You can download the latest daily builds here:
**For Neo FreeRunner [http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
***Look for files of the form: openmoko-qtopia-x11-image-om-gta02.tar.gz
***and: Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta02.rootfs.tar.gz
**For Neo 1973 the link is [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
***Look for files of the form: openmoko-qtopia-x11-image-om-gta01.tar.gz
***and: Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta01.rootfs.tar.gz
----

==FSO (FreeSmartPhone.org) Image==
Milestone 1 is here: [http://downloads.openmoko.org/framework/milestone1/ http://downloads.openmoko.org/framework/milestone1/]

[http://www.youtube.com/watch?v=toPe0S8QpJY Video of FSO Milestone 1]

Browse the source: [http://trac.freesmartphone.org:8000/trac-example/browser http://trac.freesmartphone.org:8000/trac-example/browser]

Learn more at its wiki page: [[OpenmokoFramework]]
----

==Qtopia image from qtopia.net==
[http://www.qtopia.net/modules/mydownloads/index.php Qtopia.net images] for the
*Neo FreeRunner
**[http://www.qtopia.net/modules/mydownloads/visit.php?lid=67 Freerunner flash image] (qtopia-4.3.2-gta02-flash.tgz) <-- a tarball with both a rootfs and kernel
**and the [http://www.qtopia.net/modules/mydownloads/visit.php?lid=68 root file system (ficgta02-qtopia-developer-rootfs.tgz)]
*Neo 1973
**[http://qtopia.net/downloads/neo/qtopia-4.3.2-gta01-flash.tgz Neo 1973 flash image] (qtopia-4.3.2-gta01-flash.tgz) <-- a tarball with both a rootfs and kernel
**[http://www.qtopia.net/modules/mydownloads/visit.php?lid=39 Neo 1973 root file system] (Link temporarily broken.)
**A Neo 1973 image is also available from here [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz openmoko-qtopia-image-om-gta01.tar.gz]
*[http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Alternate download page]
*You might also try [http://trolltech.com/developer/downloads/qtopia/qtopia-source-gpl ftp.trolltech.com snapshots]

Addtional packages can be added from the Trolltech feed for this image, found at
http://qtopia.net/packages/feed/4.3.2/neo/
To get to these packages, you need to add the feed as a source in the Qtopia package manager.
----

==SHR (Stable Hybrid Release) Image==
The Stable Hybrid Release (SHR) is intended to be a combination of the
FSO, some of the 2007.2 GTK software, and the ASU that provides all of
the functionality of the 2007.2 software, but with the stability of
the FSO and the new GUI toolkits provided by the ASU. It will probably
be based on an ASU build, with the FSO software and GTK end-user apps
added.

The SHR doesn't exist anywhere but in a few people's heads at the moment (2008-07-05). Hopefully, all the work in it will be integrated back into one of the other releases, and it will cease to exist. The point is to get us a release with stable calls & suspend/resume, plus access to all those other nifty apps we had on 2007.2 and the ASU.

Learn more at its wiki page: [[Stable_Hybrid_Release]]
----

==Debian==
See [[Debian]].

==Copying a jffs2 image to ext2 to boot from microSD==
If you want to copy a rootfs jffs2 to a ext2 filesystem on an microSD card, see [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) | this]].

[[category:Openmoko]]

Users Repositories

2008-07-27T18:34:12Z

Chgros: /* Unofficial builds */

Here you can find prebuilt kernels and root file systems.

=Official downloads=

==Recent/latest builds==
* Framework Testing Images
:http://downloads.openmoko.org/framework/
* OM2007.2
:http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D
* OM2007.1 (Obsolete)
:http://buildhost.openmoko.org/OM2007.1/tmp/deploy/images/?C=M;O=D

==Snapshots [http://downloads.openmoko.org/snapshots/]==
* 2007.11 - the latest (2nd Dec) snapshot ([http://lists.openmoko.org/pipermail/community/2007-December/011980.html from Mickey])
:http://downloads.openmoko.org/snapshots/2007.11/images/
* 2007.08 snapshot, as announced by Sean on August 19
:http://downloads.openmoko.org/snapshots/2007.08/images/

==Daily==
* Unstable Daily-builds
:http://buildhost.openmoko.org/daily/

==[[CommunityRepository|Community repository]]==
:http://downloads.openmoko.org/community-repository/

=Unofficial builds=

==[[User:ChooseOpen|ChooseOpen]]==
:http://chooseopen.com/openmoko/build/2007.2/?M=D
:http://chooseopen.com/openmoko/build/qtopia/?M=D (Qtopia)

==[[User:Kevin_Dean|Kevin_Dean]]==
:http://downloads.openmoko.org/recommended/
:Latest recommended [[Snapshot review|snapshot review]]

==[[User:ScaredyCat|ScaredyCat]]==
:http://buildhost.automated.it/OM2007.2/?M=D

ScaredyCat also has a ipkg repository for 2007.2 where e.g. gpe-filemanager and a lot more (e.g. ntpd) can be installed from. On the Neo do:

cd /etc/opkg
wget http://buildhost.automated.it/scaredycat.conf
opkg update
opkg install gpe-filemanager
opkg install gpe-timesheet
opkg install gpe-todo
opkg install mysql
opkg install mtpaint
opkg install sqlite
opkg install ntp
#(you get the idea)
/etc/init.d/xserver-nodm restart # to make the new applications appear in the menu

=='''mwester''' unofficial builds==
:http://moko.mwester.net/

==celtune==
:http://rabenfrost.net/celtune/?C=M;O=D
:http://rabenfrost.net/celtune/ipk/

Celtune offers Standard-Builds (.jffs2, .tar.gz, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
For more info take a look at http://rabenfrost.net/celtune/1-NEWS-WARNING-INFO
You can find images, kernels and packages for other devices too on http://rabenfrost.net/celtune/ (e.g. HTC-Blueangel, Asus730W ...)
A huge number of packages is located at http://rabenfrost.net/celtune/ipk/
Use the following line to add celtune's feed to your neo:
cd /etc/opkg && wget http://rabenfrost.net/celtune/celtune-rabenfrost.conf

If you want to add a link, it would be nice to enforce a standard format of these feeds so that they can be browsed automatically.

=== Angstrom Repository ===
If there's a package you need that is missing from the feeds listed above you can search the Angstrom repo [http://www.angstrom-distribution.org/repo/ here].

To add the unstable Angstrom feed, update your /etc/ipkg/base-feeds.conf to include a line:

src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/

[[Category:Openmoko]]

Users Repositories

2008-07-27T18:33:16Z

Chgros: /* - (2007.2) */

Users Repositories

2008-07-27T18:33:04Z

Chgros: /* ChooseOpen */ Fixed broken links

Here you can find prebuilt kernels and root file systems.

=Official downloads=

==Recent/latest builds==
* Framework Testing Images
:http://downloads.openmoko.org/framework/
* OM2007.2
:http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D
* OM2007.1 (Obsolete)
:http://buildhost.openmoko.org/OM2007.1/tmp/deploy/images/?C=M;O=D

==Snapshots [http://downloads.openmoko.org/snapshots/]==
* 2007.11 - the latest (2nd Dec) snapshot ([http://lists.openmoko.org/pipermail/community/2007-December/011980.html from Mickey])
:http://downloads.openmoko.org/snapshots/2007.11/images/
* 2007.08 snapshot, as announced by Sean on August 19
:http://downloads.openmoko.org/snapshots/2007.08/images/

==Daily==
* Unstable Daily-builds
:http://buildhost.openmoko.org/daily/

==[[CommunityRepository|Community repository]]==
:http://downloads.openmoko.org/community-repository/

=Unofficial builds=

==[[User:ChooseOpen|ChooseOpen]]==
:http://chooseopen.com/openmoko/build/2007.2/?M=D
:http://chooseopen.com/openmoko/build/qtopia/?M=D (Qtopia)

==[[User:Kevin_Dean|Kevin_Dean]]==
:http://downloads.openmoko.org/recommended/
:Latest recommended [[Snapshot review|snapshot review]]

==[[User:ScaredyCat|ScaredyCat]]==
:http://buildhost.automated.it/OM2007.2/?M=D

ScaredyCat also has a ipkg repository for 2007.2 where e.g. gpe-filemanager and a lot more (e.g. ntpd) can be installed from. On the Neo do:

cd /etc/opkg
wget http://buildhost.automated.it/scaredycat.conf
opkg update
opkg install gpe-filemanager
opkg install gpe-timesheet
opkg install gpe-todo
opkg install mysql
opkg install mtpaint
opkg install sqlite
opkg install ntp
#(you get the idea)
/etc/init.d/xserver-nodm restart # to make the new applications appear in the menu

=='''mwester''' unofficial builds==
:http://moko.mwester.net/

==- (2007.2)==
:http://www.totalueberwachung.de/~alphaone/openmoko-build/glibc/images/fic-gta01/?C=M;O=D

==celtune==
:http://rabenfrost.net/celtune/?C=M;O=D
:http://rabenfrost.net/celtune/ipk/

Celtune offers Standard-Builds (.jffs2, .tar.gz, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
For more info take a look at http://rabenfrost.net/celtune/1-NEWS-WARNING-INFO
You can find images, kernels and packages for other devices too on http://rabenfrost.net/celtune/ (e.g. HTC-Blueangel, Asus730W ...)
A huge number of packages is located at http://rabenfrost.net/celtune/ipk/
Use the following line to add celtune's feed to your neo:
cd /etc/opkg && wget http://rabenfrost.net/celtune/celtune-rabenfrost.conf

If you want to add a link, it would be nice to enforce a standard format of these feeds so that they can be browsed automatically.

=== Angstrom Repository ===
If there's a package you need that is missing from the feeds listed above you can search the Angstrom repo [http://www.angstrom-distribution.org/repo/ here].

To add the unstable Angstrom feed, update your /etc/ipkg/base-feeds.conf to include a line:

src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/

[[Category:Openmoko]]

Users Repositories

2008-07-27T18:21:35Z

Chgros: /* Official downloads */

Here you can find prebuilt kernels and root file systems.

=Official downloads=

==Recent/latest builds==
* Framework Testing Images
:http://downloads.openmoko.org/framework/
* OM2007.2
:http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D
* OM2007.1 (Obsolete)
:http://buildhost.openmoko.org/OM2007.1/tmp/deploy/images/?C=M;O=D

==Snapshots [http://downloads.openmoko.org/snapshots/]==
* 2007.11 - the latest (2nd Dec) snapshot ([http://lists.openmoko.org/pipermail/community/2007-December/011980.html from Mickey])
:http://downloads.openmoko.org/snapshots/2007.11/images/
* 2007.08 snapshot, as announced by Sean on August 19
:http://downloads.openmoko.org/snapshots/2007.08/images/

==Daily==
* Unstable Daily-builds
:http://buildhost.openmoko.org/daily/

==[[CommunityRepository|Community repository]]==
:http://downloads.openmoko.org/community-repository/

=Unofficial builds=

==[[User:ChooseOpen|ChooseOpen]]==
:http://chooseopen.com:81/openmoko/build/2007.2/?M=D
:http://chooseopen.com:81/openmoko/build/qtopia/?M=D (Qtopia)

==[[User:Kevin_Dean|Kevin_Dean]]==
:http://downloads.openmoko.org/recommended/
:Latest recommended [[Snapshot review|snapshot review]]

==[[User:ScaredyCat|ScaredyCat]]==
:http://buildhost.automated.it/OM2007.2/?M=D

ScaredyCat also has a ipkg repository for 2007.2 where e.g. gpe-filemanager and a lot more (e.g. ntpd) can be installed from. On the Neo do:

cd /etc/opkg
wget http://buildhost.automated.it/scaredycat.conf
opkg update
opkg install gpe-filemanager
opkg install gpe-timesheet
opkg install gpe-todo
opkg install mysql
opkg install mtpaint
opkg install sqlite
opkg install ntp
#(you get the idea)
/etc/init.d/xserver-nodm restart # to make the new applications appear in the menu

=='''mwester''' unofficial builds==
:http://moko.mwester.net/

==- (2007.2)==
:http://www.totalueberwachung.de/~alphaone/openmoko-build/glibc/images/fic-gta01/?C=M;O=D

==celtune==
:http://rabenfrost.net/celtune/?C=M;O=D
:http://rabenfrost.net/celtune/ipk/

Celtune offers Standard-Builds (.jffs2, .tar.gz, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
For more info take a look at http://rabenfrost.net/celtune/1-NEWS-WARNING-INFO
You can find images, kernels and packages for other devices too on http://rabenfrost.net/celtune/ (e.g. HTC-Blueangel, Asus730W ...)
A huge number of packages is located at http://rabenfrost.net/celtune/ipk/
Use the following line to add celtune's feed to your neo:
cd /etc/opkg && wget http://rabenfrost.net/celtune/celtune-rabenfrost.conf

If you want to add a link, it would be nice to enforce a standard format of these feeds so that they can be browsed automatically.

=== Angstrom Repository ===
If there's a package you need that is missing from the feeds listed above you can search the Angstrom repo [http://www.angstrom-distribution.org/repo/ here].

To add the unstable Angstrom feed, update your /etc/ipkg/base-feeds.conf to include a line:

src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/

[[Category:Openmoko]]

Users Repositories

2008-07-27T18:19:50Z

Chgros: Reformatted using headings

Here you can find prebuilt kernels and root file systems.

=Official downloads=

==Recent/latest builds==
* Framework Testing Images
:http://downloads.openmoko.org/framework/
* OM2007.2
:http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D
* OM2007.1 (Obsolete)
:http://buildhost.openmoko.org/OM2007.1/tmp/deploy/images/?C=M;O=D

==Snapshots [http://downloads.openmoko.org/snapshots/]==
* 2007.11 - the latest (2nd Dec) snapshot ([http://lists.openmoko.org/pipermail/community/2007-December/011980.html from Mickey])
:http://downloads.openmoko.org/snapshots/2007.11/images/
* 2007.08 snapshot, as announced by Sean on August 19
:http://downloads.openmoko.org/snapshots/2007.08/images/

==Daily==
* Unstable Daily-builds
:http://buildhost.openmoko.org/daily/

=Unofficial builds=

==[[User:ChooseOpen|ChooseOpen]]==
:http://chooseopen.com:81/openmoko/build/2007.2/?M=D
:http://chooseopen.com:81/openmoko/build/qtopia/?M=D (Qtopia)

==[[User:Kevin_Dean|Kevin_Dean]]==
:http://downloads.openmoko.org/recommended/
:Latest recommended [[Snapshot review|snapshot review]]

==[[User:ScaredyCat|ScaredyCat]]==
:http://buildhost.automated.it/OM2007.2/?M=D

ScaredyCat also has a ipkg repository for 2007.2 where e.g. gpe-filemanager and a lot more (e.g. ntpd) can be installed from. On the Neo do:

cd /etc/opkg
wget http://buildhost.automated.it/scaredycat.conf
opkg update
opkg install gpe-filemanager
opkg install gpe-timesheet
opkg install gpe-todo
opkg install mysql
opkg install mtpaint
opkg install sqlite
opkg install ntp
#(you get the idea)
/etc/init.d/xserver-nodm restart # to make the new applications appear in the menu

=='''mwester''' unofficial builds==
:http://moko.mwester.net/

==- (2007.2)==
:http://www.totalueberwachung.de/~alphaone/openmoko-build/glibc/images/fic-gta01/?C=M;O=D

==celtune==
:http://rabenfrost.net/celtune/?C=M;O=D
:http://rabenfrost.net/celtune/ipk/

Celtune offers Standard-Builds (.jffs2, .tar.gz, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
For more info take a look at http://rabenfrost.net/celtune/1-NEWS-WARNING-INFO
You can find images, kernels and packages for other devices too on http://rabenfrost.net/celtune/ (e.g. HTC-Blueangel, Asus730W ...)
A huge number of packages is located at http://rabenfrost.net/celtune/ipk/
Use the following line to add celtune's feed to your neo:
cd /etc/opkg && wget http://rabenfrost.net/celtune/celtune-rabenfrost.conf

If you want to add a link, it would be nice to enforce a standard format of these feeds so that they can be browsed automatically.

=== Angstrom Repository ===
If there's a package you need that is missing from the feeds listed above you can search the Angstrom repo [http://www.angstrom-distribution.org/repo/ here].

To add the unstable Angstrom feed, update your /etc/ipkg/base-feeds.conf to include a line:

src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/

[[Category:Openmoko]]

SHR Development

2008-07-22T01:46:30Z

Chgros: /* Building openmoko-dialer3 */

== Building openmoko-dialer3 ==
Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp|Bobby]] before starting one), put instructions for working on the project here!

=== Before beginning ===
You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.

The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.

You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)

=== Set up your BBPATH ===

export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/

=== Set up the CACHE ===

export CACHE=tmp/cache

=== Set up your local.conf ===
Cd to your selected build directory.

Create a directory under your current directory called 'conf'.

cp $MOKO/openembedded/conf/local.conf conf/local.conf.

Append the following lines to your local.conf:
BBFILES += "$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb"
SELECTED_OPTIMIZATION = "-Os -g"

''Note: Spaces are important in your bitbake conf files! You must have spaces before & after the = or +=''

=== Add your cross-compiler to your PATH ===

export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH

=== Run bitbake ===

bitbake openmoko-dialer3

=== To recompile, and only recompile ===

bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb

=== Troubleshooting ===

==== General ====
One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.

[[Category:Openmoko]]
[[Category:Community]]
[[Category:SHR]]
[[Category:SHR Devel]]

Change matchbox keyboard layout

2008-07-21T00:57:32Z

Chgros: /* Change matchbox keyboard layout */

{{Languages|Change_keyboard_layout}}

== Change matchbox keyboard layout ==

If you have the matchbox-keyboard installed (see [[Switching_Keyboards#Matchbox_keyboard|here]] for installation instructions) you can change the layout.
In /usr/share/matchbox-keyboard/ are the keyboard-files in xml format
just take one an copy it to your home-directory

mkdir /home/root/.matchbox
cp /usr/share/matchbox-keyboard/keyboard.xml /home/root/.matchbox/

so now you can change the layout of the keyboard by changing this file
you could add also more than one layout in that file and you can change this on-the-fly by using
this button on your keyboard [->]

for example here is my keyboard.xml with german QWERTZ layout, numblock layout and default layout
just copy it to your home directory, rename it to keyboard.xml and have fun

[[Image:Keyboard.xml]]

<?xml version="1.0" encoding="UTF-8"?>
<keyboard>
<options>
</options>
<layout id="german keyboard">
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Esc" action="escape" />
</key>
<key>
<default display="^" />
<shifted display="°" />
</key>
<key>
<default display="1" />
<shifted display="!" />
</key>
<key>
<default display="2" />
<shifted display='"' />
<mod1 display="²" />
</key>
<key>
<default display="3" />
<shifted display="§" />
<mod1 display="³" />
</key>
<key>
<default display="4" />
<shifted display="$" />
</key>
<key>
<default display="5" />
<shifted display="%" />
</key>
<key>
<default display="6" />
<shifted display="&amp;" />
</key>
<key>
<default display="7" />
<shifted display="/" />
<mod1 display="{" />
</key>
<key>
<default display="8" />
<shifted display="(" />
<mod1 display="[" />
</key>
<key>
<default display="9" />
<shifted display=")" />
<mod1 display="]" />
</key>
<key>
<default display="0" />
<shifted display="=" />
<mod1 display="}" />
</key>
<key>
<default display="?" />
<shifted display="ß" />
<mod1 display="\" />
</key>
<key>
<default display="'" />
<shifted display="" />
</key>
<key fill="true">
<default display="⌫" action="backspace"/>
</key>
<space width="500" extended="true"/>
<key width="4000" extended="true">
<default display="Home" action="home"/>
</key>
<key width="4000" extended="true">
<default display="PgUp" action="pageup"/>
</key>
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="↹" action="tab"/>
</key>
<key obey-caps='true'>
<default display="q" />
<shifted display="Q" />
<mod1 display="@" />
</key>
<key obey-caps='true'>
<default display="w" />
<shifted display="W" />
</key>
<key obey-caps='true'>
<mod1 display="€" />
<default display="e" />
<shifted display="E" />
</key>
<key obey-caps='true'>
<default display="r" />
<shifted display="R" />
</key>
<key obey-caps='true'>
<default display="t" />
<shifted display="T" />
</key>
<key obey-caps='true'>
<default display="z" />
<shifted display="Z" />
</key>
<key obey-caps='true'>
<default display="u" />
<shifted display="U" />
</key>
<key obey-caps='true'>
<default display="i" />
<shifted display="I" />
</key>
<key obey-caps='true'>
<default display="o" />
<shifted display="O" />
</key>
<key obey-caps='true'>
<default display="p" />
<shifted display="P" />
</key>
<key>
<default display="ü" />
<shifted display="Ü" />
</key>
<key>
<default display="+" />
<shifted display="*" />
<mod1 display="~" />
</key>
<key fill="true">
<default display="◀┛" action="return"/>
</key>
<space width="500" extended="true"/>
<key width="4000" extended="true">
<default display="End" action="end"/>
</key>
<key width="4000" extended="true">
<default display="PgDn" action="pagedown"/>
</key>
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Caps" action="modifier:caps"/>
</key>
<key obey-caps='true'>
<default display="a" />
<shifted display="A" />
</key>
<key obey-caps='true'>
<default display="s" />
<shifted display="S" />
</key>
<key obey-caps='true'>
<default display="d" />
<shifted display="D" />
</key>
<key obey-caps='true'>
<default display="f" />
<shifted display="F" />
</key>
<key obey-caps='true'>
<default display="g" />
<shifted display="G" />
</key>
<key obey-caps='true'>
<default display="h" />
<shifted display="H" />
</key>
<key obey-caps='true'>
<default display="j" />
<shifted display="J" />
</key>
<key obey-caps='true'>
<default display="k" />
<shifted display="K" />
</key>
<key obey-caps='true'>
<default display="l" />
<shifted display="L" />
</key>
<key>
<default display="ö" />
<shifted display="Ö" />
</key>
<key>
<default display="ä" />
<shifted display="Ä" />
</key>
<key>
<default display="#" />
<shifted display="'" />
</key>
<key fill="true">
<default display="◀┛" action="return"/>
</key>
<space width="500" extended="true"/>
<space width="4000" extended="true" />
<space width="4000" extended="true" />
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Shift" action="modifier:shift"/>
</key>
<key>
<default display="&lt;" />
<shifted display="&gt;" />
<mod1 display="|" />
</key>
<key obey-caps='true'>
<default display="y" />
<shifted display="Y" />
</key>
<key obey-caps='true'>
<default display="x" />
<shifted display="X" />
</key>
<key obey-caps='true'>
<default display="c" />
<shifted display="C" />
</key>
<key obey-caps='true'>
<default display="v" />
<shifted display="V" />
</key>
<key obey-caps='true'>
<default display="b" />
<shifted display="B" />
</key>
<key obey-caps='true'>
<default display="n" />
<shifted display="N" />
</key>
<key obey-caps='true'>
<default display="m" />
<shifted display="M" />
<mod1 display="µ" />
</key>
<key>
<default display="," />
<shifted display=";" />
</key>
<key>
<default display="." />
<shifted display=":" />
</key>
<key>
<default display="-" />
<shifted display="_" />
</key>
<key fill="true">
<default display="Shift" action="modifier:shift"/>
</key>
<space width="500" extended="true"/>
<space width="4000" extended="true" />
<space width="4000" extended="true" />
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Strg" action="modifier:ctrl"/>
</key>
<key fill="true">
<default display="[->]" action="modifier:layout"/>
</key>
<key fill="true">
<default display="Alt" action="modifier:alt"/>
</key>
<key width="9500">
<default display=" " action="space" />
</key>
<key fill="true">
<default display="Alt Gr" action="modifier:mod1"/>
</key>
<key>
<default display="↑" action="up" />
</key>
<key>
<default display="↓" action="down" />
</key>
<key>
<default display="←" action="left" />
</key>
<key>
<default display="→" action="right" />
</key>
<space width="500" extended="true"/>
<space width="4000" extended="true" />
<space width="4000" extended="true" />
<space width="500" extended="true"/>
</row>
</layout>
<layout id="numpad keyboard">
<row>
<space width="500" extended="true"/>
<key>
<default display="Num" action="modifier:caps" />
</key>
<key>
<default display="/" />
</key>
<key>
<default display="*" />
</key>
<key>
<default display="-" />
</key>
</row>
<row>
<space width="500" extended="true"/>
<key obey-caps='true'>
<default display="7" />
<shifted display="Pos 1" action="home" />
</key>
<key obey-caps='true'>
<default display="8" />
<shifted display="↑" action="up" />
</key>
<key obey-caps='true'>
<default display="9" />
<shifted display="Bild ↑" action="pageup"/>
</key>
<key>
<default display="+" />
</key>
</row>
<row>
<space width="500" extended="true"/>
<key obey-caps='true'>
<default display="4" />
<shifted display="←" action="left" />
</key>
<key>
<default display="5" />
</key>
<key obey-caps='true'>
<default display="6" />
<shifted display="→" action="right"/>
</key>
<key>
<default display="+" />
</key>
</row>
<row>
<space width="500" extended="true"/>
<key obey-caps='true'>
<default display="1" />
<shifted display="Ende" action="end" />
</key>
<key obey-caps='true'>
<default display="2" />
<shifted display="↓" action="down" />
</key>
<key obey-caps='true'>
<default display="3" />
<shifted display="Bild ↓" action="pagedown"/>
</key>
<key>
<default display="◀┛" action="return" />
</key>
</row>
<row>
<space width="500" extended="true"/>
<key obey-caps='true'>
<default display="0" />
</key>
<key obey-caps='true'>
<default display="," />
<shifted display="Entf" action="delete"/>
</key>
</row>
<row>
<key>
<default display="[->]" action="modifier:layout"/>
</key>
</row>
</layout>
<layout id="default keyboard">
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Esc" action="escape" />
</key>
<key>
<default display="`" />
</key>
<key>
<default display="1" />
<shifted display="!" />
</key>
<key>
<default display="2" />
<shifted display='"' />
<mod1 display="½" />
</key>
<key>
<default display="3" />
<shifted display="£" />
<mod1 display="¾" />
</key>
<key>
<default display="4" />
<shifted display="$" />
</key>
<key>
<default display="5" />
<shifted display="%" />
</key>
<key>
<default display="6" />
<shifted display="^" />
</key>
<key>
<default display="7" />
<shifted display="&" />
</key>
<key>
<default display="8" />
<shifted display="*" />
</key>
<key>
<default display="9" />
<shifted display="(" />
</key>
<key>
<default display="0" />
<shifted display=")" />
</key>
<key>
<default display="-" />
<shifted display="_" />
</key>
<key>
<default display="=" />
<shifted display="+" />
</key>
<key fill="true">
<default display="Bksp" action="backspace"/>
</key>
<space width="500" extended="true"/>
<key width="4000" extended="true">
<default display="Home" action="home"/>
</key>
<key width="4000" extended="true">
<default display="PgUp" action="pageup"/>
</key>
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Tab" action="tab"/>
</key>
<key obey-caps='true'>
<default display="q" />
<shifted display="Q" />
</key>
<key obey-caps='true'>
<default display="w" />
<shifted display="W" />
</key>
<key obey-caps='true'>
<mod1 display="ë" />
<default display="e" />
<shifted display="E" />
</key>
<key obey-caps='true'>
<default display="r" />
<shifted display="R" />
</key>
<key obey-caps='true'>
<default display="t" />
<shifted display="T" />
</key>
<key obey-caps='true'>
<default display="y" />
<shifted display="Y" />
</key>
<key obey-caps='true'>
<default display="u" />
<shifted display="U" />
</key>
<key obey-caps='true'>
<default display="i" />
<shifted display="I" />
</key>
<key obey-caps='true'>
<default display="o" />
<shifted display="O" />
</key>
<key obey-caps='true'>
<default display="p" />
<shifted display="P" />
</key>
<key>
<default display="{" />
<shifted display="[" />
</key>
<key>
<default display="}" />
<shifted display="]" />
</key>
<key fill="true">
<default display="\" />
<shifted display="|" />
</key>
<space width="500" extended="true"/>
<key width="4000" extended="true">
<default display="End" action="end"/>
</key>
<key width="4000" extended="true">
<default display="PgDn" action="pagedown"/>
</key>
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Caps" action="modifier:caps"/>
</key>
<key obey-caps='true'>
<default display="a" />
<shifted display="A" />
</key>
<key obey-caps='true'>
<default display="s" />
<shifted display="S" />
</key>
<key obey-caps='true'>
<default display="d" />
<shifted display="D" />
</key>
<key obey-caps='true'>
<default display="f" />
<shifted display="F" />
</key>
<key obey-caps='true'>
<default display="g" />
<shifted display="G" />
</key>
<key obey-caps='true'>
<default display="h" />
<shifted display="H" />
</key>
<key obey-caps='true'>
<default display="j" />
<shifted display="J" />
</key>
<key obey-caps='true'>
<default display="k" />
<shifted display="K" />
</key>
<key obey-caps='true'>
<default display="l" />
<shifted display="L" />
</key>
<key>
<default display=";" />
<shifted display=":" />
</key>
<key>
<default display="#" />
<shifted display="~" />
</key>
<key fill="true">
<default display="Ret" action="return"/>
</key>
<space width="500" extended="true"/>
<space width="4000" extended="true" />
<space width="4000" extended="true" />
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key fill="true">
<default display="Shift" action="modifier:shift"/>
</key>
<key obey-caps='true'>
<default display="z" />
<shifted display="Z" />
</key>
<key obey-caps='true'>
<default display="x" />
<shifted display="X" />
</key>
<key obey-caps='true'>
<default display="c" />
<shifted display="C" />
</key>
<key obey-caps='true'>
<default display="v" />
<shifted display="V" />
</key>
<key obey-caps='true'>
<default display="b" />
<shifted display="B" />
</key>
<key obey-caps='true'>
<default display="n" />
<shifted display="N" />
</key>
<key obey-caps='true'>
<default display="m" />
<shifted display="M" />
</key>
<key>
<default display="," />
<shifted display="&lt;" />
</key>
<key>
<default display="." />
<shifted display="&gt;" />
</key>
<key>
<default display="/" />
<shifted display="?" />
</key>
<key fill="true">
<default display="Shift" action="modifier:shift"/>
</key>
<space width="500" extended="true"/>
<space width="4000" extended="true" />
<space width="4000" extended="true" />
<space width="500" extended="true"/>
</row>
<row>
<space width="500" extended="true"/>
<key>
<default display="[->]" action="modifier:layout"/>
</key>
<key>
<default display="äëö" action="modifier:mod1"/>
</key>
<key fill="true">
<default display="Ctrl" action="modifier:ctrl"/>
</key>
<key>
<default display="Alt" action="modifier:alt"/>
</key>
<key width="12000">
<default display=" " action="space" />
</key>
<key>
<default display="@" />
<shifted display="'" />
</key>
<key>
<default display="↑" action="up" />
</key>
<key>
<default display="↓" action="down" />
</key>
<key>
<default display="←" action="left" />
</key>
<key>
<default display="→" action="right" />
</key>
<space width="500" extended="true"/>
<space width="4000" extended="true" />
<space width="4000" extended="true" />
<space width="500" extended="true"/>
</row>
</layout>
</keyboard>

Booting the Neo FreeRunner from SD via U-Boot

2008-07-20T05:10:05Z

Chgros: /* Partioning the SD card */

Here are the steps described to boot your system from an SD card.

{| cellspacing="5" cellpadding="0" style="padding: 2%; margin:0em 0em 1em 0em; border:1px solid #F9D163; background:#FCE9B4; width:100%"
|
Some versions of u-boot don't work properly for booting from SD card. [http://buildhost.automated.it/u-boot-good-for-sd-boot-r13_0_2632_0.bin This old one works], and a u-boot from January 2008 or later should also work. Be careful when flashing u-boot as you can brick your device.
|}

== Step 1: Change your kernel settings ==

'''''Note:''''' The default kernel config as of 2008-02-10 includes the CONFIG_MMC_S3C=y line and also includes built-in support for the ext3 filesystem. The default 2.6.22.5 kernel (and higher) may therefore be used for SD-booting as long as your card is formatted as ext3 (not ext2).

Kernel building is supposed to be done through OpenEmbedded. If you use the MokoMakefile open up $OMDIR/openmoko/trunk/oe/packages/linux/linux-gta01/defconfig-2.6.21.6-fic-gta01. If you are building OM-2007.2 open $OEDIR/openembedded/packages/linux/linux-openmoko/defconfig-2.6.22.5-fic-gta01.

'''''Note:''''' That kernel version may change in future releases.

Now find the line saying:

CONFIG_MMC_S3C=m

and change it to:

CONFIG_MMC_S3C=y

If you want to use an ext2 file system on the SD, also find the line saying:

CONFIG_EXT2_FS=m

and change it to:

CONFIG_EXT2_FS=y

If you're using MokoMakfile, you can clean out your last kernel build (forcing a new build) by running:

make clean-package-linux-openmoko

== Step 2: Acquiring a tarfile rootfs ==

There are two ways of acquiring an rootfs image as a tar archive. You can either build it on your own using the OpenEmbedded Distribution. Or download it from the openmoko buildhost.

=== Possibility 1: Downloading the rootfs tar from the Openmoko buildhost ===

The needed tar archives are automatically build during the daily creation of the new rootfs and kernel images on the Openmoko buildhost.

You need to distinguish between the Neo1973 and the Freerunner device here, because they need slightly different images and kernels.

* Freerunner
** http://buildhost.openmoko.org/daily/freerunner/
* Neo1973
** http://buildhost.openmoko.org/daily/neo1973/

=== Possibility 2: Building a tarfile distribution using OpenEmbedded ===

Another possibility to get a tar archive of your rootfs is to build it on your own with the OpenEmbedded environment.

To build OM-2007.2 you need to add "tar" to the image types in your ''local.conf'':

IMAGE_FSTYPES = "jffs2 tar"

After that build a new image by issuing:

bitbake openmoko-devel-image

or if you are using the MokoMakefile:

make openmoko-devel-image

After the process finished there will be a ''OpenMoko-....tar'' in the deploy directory, which is your newly created rootfs archive

== Step 3: Prepare the SD card ==

=== Partioning the SD card ===

Unfortunately the uboot loader can only read from FAT partitions. Therefore the kernel needs to be stored in a partition with this filesystem.
Nevertheless we want to store our rootfs in an ext3 (or ext2) filesystem. To acomplish this the sd-card needs to be partitioned into to different parts.
This example shows how to do this using the fdisk utility. Feel free to use the partitioning utility of your liking for this task.

fdisk /dev/mmcblk0

'''''Note:''''' The device file might differ on your system. If you are not sure about it, you may check your kernel message log by calling ''dmesg'' to find the correct device.

We will now create a 8 mb partition for our kernel and another one for the rootfs which will take up all the remaining space.

Command (m for help): d
Selected partition 1
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-983, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (18-983, default 18):
Using default value 18
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):
Using default value 983
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.

=== Formatting the SD card ===

As already mentioned we need the first partition to be formatted with the FAT filesystem. Just issue the following command to create this fs:

mkfs.vfat /dev/mmcblk0p1

The second partition is about to be formatted with ext3 (For ext2 to work you need to make sure you compiled the kernel with the correct configuration):

mkfs.ext3 /dev/mmcblk0p2

== Step 3: Populate SD card ==

Your sd card is now ready to be filled up with the rootfs and the needed kernel to boot.

Mount the second partition of your SD card somewhere and put the image on it:

mount /dev/mmcblk0p2 /mnt/moko
tar -C /mnt/moko/ -xvf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar

'''''Note:''''' As always in this guide the device name as well as the rootfs name needs to be adjusted to your device and filename structure

The next step is to mount the first partition of the sd card and install the kernel on it.

mount /dev/mmcblk0p1 /mnt/mokokernel
cp uImage-fic-gta01-latest.bin /mnt/mokokernel/uImage.bin

Make sure your kernel is called ''uImage.bin'' after copying it to the card.

Unmount both the rootfs partition and the kernel partition and make sure all remaining buffers are written to it:

umount /mnt/moko
umount /mnt/mokokernel
sync

== Step 4: Add uboot boot entry ==

Dependent on the revision of the phone and the partition type (ext2/ext3) you are using it might be necessary to add an entry to the bootmenu, to be able to boot the system of your sd card.
If you are using a Freerunner and have created an ext2 partition you should be able to boot from the card right out of the box, because a boot menu entry for this should already exist in the NAND boot menu.
In any other case you should at least make sure the needed entry exists in your menu before proceeding.
You will need to enter the uboot shell of the NAND boot menu for this. A description on how to connect to the uboot loader shell can be found in this article: [[Uboot#Boot_menu]]. Details on howto get into the NAND boot menu can be found in the appendix of this article [[#Entering NAND bootmenu (GTA02)]].

After you read these two references you should be connected to your NAND uboot shell right now. The first thing to do is to set the boot menu timeout to a really high value. Unfortunately if you don't do this, the boot loader will continue booting after the default timeout (60 seconds) even if you are connected to the uboot shell. Just enter the following command to the menu prompt:

setenv boot_menu_timeout 99999

This will set the timeout to 99999 seconds which should definitely enough time for us finish whatever work we want accomplish in the boot loader shell.

Now we will make sure a appropriate menu item for booting from sd exists, or create it otherwise. You can print the defined boot loader environment by issuing the command:

printenv

If it shows a line beginning with ''menu_'' followed by the commands which are just to follow in this guide, you do not need to create a new menu entry. In any other case please proceed with the following.

It is important to distinguish between ext2 and ext3 root partitions at this point. Please make sure you are using the correct configuration based on the decisions you made earlier.

'''Boot entry for ext3 partitions:'''

setenv menu_9 Boot from microSD (FAT+ext3): setenv bootargs \${bootargs_base} rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for ext2 partitions:'''

setenv menu_9 Boot from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''''Note:''''' The backslashes (\) are important for uboot to set the command as new environment variable (menu_9) instead of just executing them as soon as enter is pressed

'''''Note:''''' Copy and paste may not work. At least it did not work for me as I tried. You will have to type in the commandline manually.

You are nearly done. Just issue a

printenv

and verify that your newly created entry is correctly displayed (This time the backslashes are not displayed anyone).

If everything looks fine enter

saveenv

into the prompt and press enter. The new configuration should now be saved to the NAND.

Shutdown your neo with the following command:

neo1973 power-off

After you restarted the Neo and got back to the NAND boot menu you should be able to select your newly created menu entry and successfully boot into the rootfs from your sd card.

== Appendix ==

=== Boot from SDHC ===

As SDHC is currently not supported in u-boot you can't use the Booting from SD guide.
But there's a kind of workaround that is a good option to have at least your rootfs on the microSDHC:

First you can follow Step 1 to get an kernel-image with mmc- and ext2-support. But instead of copying the image to the rootfs you will have to flash it to the Neo's internal NAND-Flash (using [[Dfu-util]]).
Now you can continue with Step 2 (like mentioned before you do not have to copy your uImage to the rootfs) and follow the instructions to Step 3.
Instead of the setenv commands in Step 3 you have to enter the following:

GTA01Bv4 # setenv menu_5 Boot from SDHC: setenv bootargs root=/dev/mmcblk0p1 console=tty0 rootdelay=5 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

And that's it!
Now you can use the newly created menu option "Boot from SDHC" to boot the internal kernel, using the root-filesystem on the microSDHC.

=== Autoboot from SDHC ===

Maybe you want to Boot automatically from SDHC:
Set a new Bootmenu Entry for booting from NAND first

GTA01Bv4 # setenv menu_6 Boot from NAND: setenv bootargs \${bootargs_base} \${mtdparts}\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

then Power-off, and enter the Bootmenu to test the new Entry.If you can boot from NAND, shutdown, enter Boot menu, connect to bootloader and set the (auto)bootcmd for boot from SDHC:

GTA01Bv4 # setenv bootcmd setenv bootargs root=/dev/mmcblk0p1 rootdelay=10 console=tty0 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

Now you boot from SDHC everytime you press the Power-Button or reboot and if you like to boot from NAND -just use the bootmenu.

=== Fixing udev automount ===

Udev automatically mounts the SD Card in /media/mmcblk0p1/ you can disable this with

echo /dev/mmcblk >> /etc/udev/mount.blacklist

=== Entering NAND bootmenu (GTA02)===

If you want boot from NAND, please follow these steps

# Hold the Power key
# After about 1 second hold the AUX key
# Hold both keys until the menu appears
# Release both keys

=== Entering NOR bootmenu (GTA02)===

If you want boot from NOR, please follow these steps

# Hold the AUX key
# then Power Key together for power up GTA02
# Release AUX key after about 1 second

=== Remarks on Kernel Parameters ===

==== loglevel ====

Some people suggested adding:

loglevel=8

to the kernel command line. This makes the boot process extremely slow because
the framebuffer (the neo display in text mode) has to print out tons of lines of
debug messages like:

s3c2410-sdi s3c2410-sdi: ......
mmc0: ....

{{Languages|Booting_from_SD}}

[[Category:System Developers]]
[[Category:Guides]]

Booting the Neo FreeRunner from SD via U-Boot

2008-07-20T05:01:30Z

Chgros: /* Step 3: Populate SD card */

Here are the steps described to boot your system from an SD card.

{| cellspacing="5" cellpadding="0" style="padding: 2%; margin:0em 0em 1em 0em; border:1px solid #F9D163; background:#FCE9B4; width:100%"
|
Some versions of u-boot don't work properly for booting from SD card. [http://buildhost.automated.it/u-boot-good-for-sd-boot-r13_0_2632_0.bin This old one works], and a u-boot from January 2008 or later should also work. Be careful when flashing u-boot as you can brick your device.
|}

== Step 1: Change your kernel settings ==

'''''Note:''''' The default kernel config as of 2008-02-10 includes the CONFIG_MMC_S3C=y line and also includes built-in support for the ext3 filesystem. The default 2.6.22.5 kernel (and higher) may therefore be used for SD-booting as long as your card is formatted as ext3 (not ext2).

Kernel building is supposed to be done through OpenEmbedded. If you use the MokoMakefile open up $OMDIR/openmoko/trunk/oe/packages/linux/linux-gta01/defconfig-2.6.21.6-fic-gta01. If you are building OM-2007.2 open $OEDIR/openembedded/packages/linux/linux-openmoko/defconfig-2.6.22.5-fic-gta01.

'''''Note:''''' That kernel version may change in future releases.

Now find the line saying:

CONFIG_MMC_S3C=m

and change it to:

CONFIG_MMC_S3C=y

If you want to use an ext2 file system on the SD, also find the line saying:

CONFIG_EXT2_FS=m

and change it to:

CONFIG_EXT2_FS=y

If you're using MokoMakfile, you can clean out your last kernel build (forcing a new build) by running:

make clean-package-linux-openmoko

== Step 2: Acquiring a tarfile rootfs ==

There are two ways of acquiring an rootfs image as a tar archive. You can either build it on your own using the OpenEmbedded Distribution. Or download it from the openmoko buildhost.

=== Possibility 1: Downloading the rootfs tar from the Openmoko buildhost ===

The needed tar archives are automatically build during the daily creation of the new rootfs and kernel images on the Openmoko buildhost.

You need to distinguish between the Neo1973 and the Freerunner device here, because they need slightly different images and kernels.

* Freerunner
** http://buildhost.openmoko.org/daily/freerunner/
* Neo1973
** http://buildhost.openmoko.org/daily/neo1973/

=== Possibility 2: Building a tarfile distribution using OpenEmbedded ===

Another possibility to get a tar archive of your rootfs is to build it on your own with the OpenEmbedded environment.

To build OM-2007.2 you need to add "tar" to the image types in your ''local.conf'':

IMAGE_FSTYPES = "jffs2 tar"

After that build a new image by issuing:

bitbake openmoko-devel-image

or if you are using the MokoMakefile:

make openmoko-devel-image

After the process finished there will be a ''OpenMoko-....tar'' in the deploy directory, which is your newly created rootfs archive

== Step 3: Prepare the SD card ==

=== Partioning the SD card ===

Unfortunately the uboot loader can only read from FAT partitions. Therefore the kernel needs to be stored in a partition with this filesystem.
Nevertheless we want to store our rootfs in an ext3 (or ext2) filesystem. To acomplish this the sd-card needs to be partitioned into to different parts.
This example shows how to do this using the fdisk utility. Feel free to use the partitioning utitlity of your likings for this task.

fdisk /dev/mmcblk0

'''''Note:''''' The device bane might differ on your system. If you are not sure about it, you may check your kernel message log by calling ''dmesg'' to find the correct device.

We will now create a 8 mb partition for our kernel and another one for the rootfs which will take up all the remaining space.

Command (m for help): d
Selected partition 1
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-983, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (18-983, default 18):
Using default value 18
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):
Using default value 983
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.

=== Formatting the SD card ===

As already mentioned we need the first partition to be formatted with the FAT filesystem. Just issue the following command to create this fs:

mkfs.vfat /dev/mmcblk0p1

The second partition is about to be formatted with ext3 (For ext2 to work you need to make sure you compiled the kernel with the correct configuration):

mkfs.ext3 /dev/mmcblk0p2

== Step 3: Populate SD card ==

Your sd card is now ready to be filled up with the rootfs and the needed kernel to boot.

Mount the second partition of your SD card somewhere and put the image on it:

mount /dev/mmcblk0p2 /mnt/moko
tar -C /mnt/moko/ -xvf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar

'''''Note:''''' As always in this guide the device name as well as the rootfs name needs to be adjusted to your device and filename structure

The next step is to mount the first partition of the sd card and install the kernel on it.

mount /dev/mmcblk0p1 /mnt/mokokernel
cp uImage-fic-gta01-latest.bin /mnt/mokokernel/uImage.bin

Make sure your kernel is called ''uImage.bin'' after copying it to the card.

Unmount both the rootfs partition and the kernel partition and make sure all remaining buffers are written to it:

umount /mnt/moko
umount /mnt/mokokernel
sync

== Step 4: Add uboot boot entry ==

Dependent on the revision of the phone and the partition type (ext2/ext3) you are using it might be necessary to add an entry to the bootmenu, to be able to boot the system of your sd card.
If you are using a Freerunner and have created an ext2 partition you should be able to boot from the card right out of the box, because a boot menu entry for this should already exist in the NAND boot menu.
In any other case you should at least make sure the needed entry exists in your menu before proceeding.
You will need to enter the uboot shell of the NAND boot menu for this. A description on how to connect to the uboot loader shell can be found in this article: [[Uboot#Boot_menu]]. Details on howto get into the NAND boot menu can be found in the appendix of this article [[#Entering NAND bootmenu (GTA02)]].

After you read these two references you should be connected to your NAND uboot shell right now. The first thing to do is to set the boot menu timeout to a really high value. Unfortunately if you don't do this, the boot loader will continue booting after the default timeout (60 seconds) even if you are connected to the uboot shell. Just enter the following command to the menu prompt:

setenv boot_menu_timeout 99999

This will set the timeout to 99999 seconds which should definitely enough time for us finish whatever work we want accomplish in the boot loader shell.

Now we will make sure a appropriate menu item for booting from sd exists, or create it otherwise. You can print the defined boot loader environment by issuing the command:

printenv

If it shows a line beginning with ''menu_'' followed by the commands which are just to follow in this guide, you do not need to create a new menu entry. In any other case please proceed with the following.

It is important to distinguish between ext2 and ext3 root partitions at this point. Please make sure you are using the correct configuration based on the decisions you made earlier.

'''Boot entry for ext3 partitions:'''

setenv menu_9 Boot from microSD (FAT+ext3): setenv bootargs \${bootargs_base} rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for ext2 partitions:'''

setenv menu_9 Boot from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''''Note:''''' The backslashes (\) are important for uboot to set the command as new environment variable (menu_9) instead of just executing them as soon as enter is pressed

'''''Note:''''' Copy and paste may not work. At least it did not work for me as I tried. You will have to type in the commandline manually.

You are nearly done. Just issue a

printenv

and verify that your newly created entry is correctly displayed (This time the backslashes are not displayed anyone).

If everything looks fine enter

saveenv

into the prompt and press enter. The new configuration should now be saved to the NAND.

Shutdown your neo with the following command:

neo1973 power-off

After you restarted the Neo and got back to the NAND boot menu you should be able to select your newly created menu entry and successfully boot into the rootfs from your sd card.

== Appendix ==

=== Boot from SDHC ===

As SDHC is currently not supported in u-boot you can't use the Booting from SD guide.
But there's a kind of workaround that is a good option to have at least your rootfs on the microSDHC:

First you can follow Step 1 to get an kernel-image with mmc- and ext2-support. But instead of copying the image to the rootfs you will have to flash it to the Neo's internal NAND-Flash (using [[Dfu-util]]).
Now you can continue with Step 2 (like mentioned before you do not have to copy your uImage to the rootfs) and follow the instructions to Step 3.
Instead of the setenv commands in Step 3 you have to enter the following:

GTA01Bv4 # setenv menu_5 Boot from SDHC: setenv bootargs root=/dev/mmcblk0p1 console=tty0 rootdelay=5 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

And that's it!
Now you can use the newly created menu option "Boot from SDHC" to boot the internal kernel, using the root-filesystem on the microSDHC.

=== Autoboot from SDHC ===

Maybe you want to Boot automatically from SDHC:
Set a new Bootmenu Entry for booting from NAND first

GTA01Bv4 # setenv menu_6 Boot from NAND: setenv bootargs \${bootargs_base} \${mtdparts}\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

then Power-off, and enter the Bootmenu to test the new Entry.If you can boot from NAND, shutdown, enter Boot menu, connect to bootloader and set the (auto)bootcmd for boot from SDHC:

GTA01Bv4 # setenv bootcmd setenv bootargs root=/dev/mmcblk0p1 rootdelay=10 console=tty0 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

Now you boot from SDHC everytime you press the Power-Button or reboot and if you like to boot from NAND -just use the bootmenu.

=== Fixing udev automount ===

Udev automatically mounts the SD Card in /media/mmcblk0p1/ you can disable this with

echo /dev/mmcblk >> /etc/udev/mount.blacklist

=== Entering NAND bootmenu (GTA02)===

If you want boot from NAND, please follow these steps

# Hold the Power key
# After about 1 second hold the AUX key
# Hold both keys until the menu appears
# Release both keys

=== Entering NOR bootmenu (GTA02)===

If you want boot from NOR, please follow these steps

# Hold the AUX key
# then Power Key together for power up GTA02
# Release AUX key after about 1 second

=== Remarks on Kernel Parameters ===

==== loglevel ====

Some people suggested adding:

loglevel=8

to the kernel command line. This makes the boot process extremely slow because
the framebuffer (the neo display in text mode) has to print out tons of lines of
debug messages like:

s3c2410-sdi s3c2410-sdi: ......
mmc0: ....

{{Languages|Booting_from_SD}}

[[Category:System Developers]]
[[Category:Guides]]

Neo FreeRunner Wifi

2008-07-20T03:27:45Z

Chgros:

To get wlan working on your Freerunner, you can follow these steps:

1. create and edit a suitable /etc/wpa_supplicant/wpa_supplicant.conf (use your favourite search engine to find the syntax)

2. execute
ifup eth0

3. execute
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
(-B for running as daemon)

4. get a IP via dhcp:
udhcpc eth0

That's it, your wlan should now work!

==Using /etc/network/interfaces==

Another way is to use /etc/network/interfaces

For instance, for WEP:

* Using wireless tools:

iface eth0 inet dhcp
wireless-key my_wep_key
wireless-essid my_essid

* Using wpa_supplicant (this allows more authentication methods).

iface eth0 inet dhcp
wpa-wep-key0 my_wep_key
wpa-key-mgmt NONE
wpa-ssid my_essid

Using a wpa_supplicant.conf file:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Then just run:
ifup eth0

You'll get a lot of messages, like <tt>ioctl[SIOCSIWENCODEEXT]: Operation not supported</tt> and <tt>sed: unrecognized option `--quiet'</tt>, they appear to be harmless. The "--quiet" error message can be avoided by replacing "sed --quiet" with "sed -n" in /etc/wpa_supplicant/*.sh

== Known good wpa-supplicant version? ==

Is the 0.6.3-r1 broken? I don't get anything to work with these instructions via usage of wpa_supplicant, but WEP works via direct interfaces changes (wireless-essid/wireless-key settings).

== Sample wpa_supplicant.conf ==

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1

# WPA2:
network={
ssid="your ssid"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk="secret key"
priority=50
}

# WPA:
network={
ssid="your_ssid"
scan_ssid=1
psk="secret key"
priority=10
}

# WEP:
network={
ssid="your_ssid"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0="secret key"
priority=8
}

# Open:
network={
ssid="your ssid"
key_mgmt=NONE
priority=5
}

== A very ugly /etc/init.d/wlan startscript ==
#!/bin/sh
#
# wlan This shell script starts and stops wlan.
#
# processname: wlan

# Source function library.
#. /etc/rc.d/init.d/functions
# "written" by HdR

RETVAL=0
prog="wlan"

# test -f /etc/default/$prog && . /etc/default/$prog

start() {
echo -n "Starting $prog: "
ifconfig eth0 up
wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf -B
sleep 10
udhcpc eth0
RETVAL=$?
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down $prog: "
killall wpa_supplicant
ifconfig eth0 down
# killproc gpsd
RETVAL=$?
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac

exit $RETVAL

== An alternative way to automate ==
Add the wpa_supplicant details to /etc/network/interfaces:

iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Now `ifup eth0` will start up wpa_supplicant and udhcpc for you, and `ifdown eth0` will stop them, in theory at least. In practise udhcpc can time out before wpa_supplicant has finished connecting to the access point, and if udhcpc has failed to get an address ifdown exits without stopping wpa_supplicant and bringing down the interface.

== Comments ==

The alternative method seems to work reliably on the FR/ GTA02, I couldn't get the manual method to work when WPA/PSK is involved. Also you must do ifdown usb0 before the ifup eth0. Then you also need to setup the resolv.conf manually as it does not seem to get the dns server from the dhcp server. If the dhcp fails during ifup eth0, then you can run udhcpc eth0 manually it usually gets the dhcp address the second time around.

I use a script called u...
# u
ifdown usb0
ifup eth0
echo nameserver xx.xx.xx.xx >/etc/resolv.conf

This usually works

[July 19, 2008]
I've had repeated success with:
# ifconfig eth0 up
# iwconfig eth0 essid any
# iwconfig eth0 key '...'
# iwconfig eth0 essid '...'
# udhcpc eth0
# ifconfig usb0 down; ifconfig usb0 up

Hope that helps someone.

The following may be helpful in order to scan available networks :
# iwlist eth0 scan

[[Category:GTA02 Hardware]]

Getting Started with your Neo FreeRunner

2008-07-20T02:54:35Z

Chgros: Removed shell prompts, allowing copy/paste to command line

{{Languages|Getting Started with your Neo FreeRunner}}

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc; width:75% " |
<p align="left">
Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of [[Openmoko]]. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.</p>
! style="background:#fcfcfc; width:25% " |
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]
|}

== Package Contents ==

[[Image:GTA02ALL.png|left|400px|thumb|Inside the package]]
<br />
: [[Image:Circle２.gif|10px]] Neo FreeRunner
: [[Image:Circle２.gif|10px]] Stylus
: [[Image:Circle２.gif|10px]] Battery
: [[Image:Circle２.gif|10px]] Charger
: [[Image:Circle２.gif|10px]] USB Cable (A -> Mini-B 5-pole)
: [[Image:Circle２.gif|10px]] microSD Card 512MB & SD adapter

<div style="clear: both"> </div>

== Setting up the hardware, getting to know the Neo FreeRunner physically ==

===Installing the Micro-SD card, the SIM card, and the Battery ===

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|Open the case like this.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Opening !|center]]</td>
</tr>
<tr valign="top" style="background: #ffffff">
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here.|center]]</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|Finally, put in the battery.|center]]</td>
</tr></table>
</div>

# Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.
# Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.
# Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.
# Lift up on the SIM card holder.
# The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.
# Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo Freerunner.
# Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.
# Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.
# Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.
# Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.
# Replace the rear cover on the FreeRunner.

[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]

[[http://video.google.de/videoplay?docid=-8343770443102960945 A short video]] is also available. It was shot using the previous version of the Neo, but the installation procedures remains the same.

===Charging the Neo FreeRunner===

When using the Neo FreeRunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger (at 1000mA) or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.

Charging an empty battery at 100mA takes 12~15 hours, at 500mA takes 2,5~3,5 hours, and at 1000mA takes 1.5~2.5 hours. (90%~100%) [to be confirmed]

Make sure that the battery never discharges completely. This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work. Should the battery become completely discharged, your options are:
- Use external stand-alone charger (compatible with the Nokia BL-5C battery)
- Boot the FreeRunner with an alternative battery, or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
- Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.

===Buttons and connectors===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Power Button, USB and external GPS Antenna (left to right)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack (left to right)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Power'''
Tapping the power button exits the current application.

Holding the power button brings up a menu allowing you to:
* Power on and off the GPS, wifi, GSM, and bluetooth antennae
* Change power management mode to:
** Dim first then lock
** Dim only, don't lock
** Disabled
* Lock the screen
* Shutdown the device.</td>
<td></td>
<td>'''Aux'''

Holding the Aux button brings up a menu allowing you to:

* Hide and show the title bar (Fullscreen toggle)
* Alternate wide or tall display modes (Swap Orientation)
* Save the content of the screen as an image file (Screenshot)
</td>
</tr>
</table>

===Unlocking the screen===

When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.

== Making your first phone call: Menus and Applications ==

''Note:'' this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

====Today Page====

The first thing after you boot Openmoko should be the "Today" page. This is your home page. In the top row, you see icons that indicate the status of the phone. The second row are quick links to commonly-used applications such as the dialer. The main body of the screen is your home page, displaying a clock and other useful information. The bottom row consists of three tabs representing Today (the page you're viewing now), Launch Task Page, and Running Tasks Page.

See [[Today/2007.2]] for more information about the Today page and customization.<br clear=all />

====Launch Task Page====

{{stub}}

This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Current categories are [[PIM Suite]], [[Applications]], [[Games]], [[Utilities]], and All.

====Running Tasks Page====

{{stub}}

This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

====Exiting an Application====

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can switch tasks at any time by clicking the menu of tasks at the far upper-left of the screen, which will display a list of running tasks, allowing you to select one.

(''Note:'' If the task menu is not shown, use the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".)

===Adjusting the Volume===

As of this writing, there is no way to adjust the volume from the screen.

For now, run the terminal application or [[Getting_Started_with_your_Neo_FreeRunner#Connect_to_the_Neo_FreeRunner_By_USB_Networking|log in via usb]], and run the [[alsamixer]] application. The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use
alsactl -f ''path-to-statefile'' store
to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):
:gsmhandset.state
:gsmheadset.state
:gsmspeakerout.state
:headset.state
:stereoout.state

These correspond to the various Sound Profiles accessible in the Debug Tool under Applications.

One way to increase the volume of the microphone is to do the following:
# ssh into your Freerunner
# vi /usr/share/openmoko/scenarios/gsmhandset.state
# search for "Mic2"
# change to "value 3"
[[Freerunner_Hardware_Issues]]

==Getting into your new Linux box==

===Connect with and log in the Neo FreeRunner===

Connect the Neo FreeRunner to your Linux computer using the standard mini-USB to USB cable provided.

With the device connected,
modprobe usbnet
(if necessary) and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo (adjust your firewall if necessary):
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo with empty password
# ssh root@192.168.0.202

You will eventually want to setup your computer so that it automatically connects the Neo FreeRunner to the Internet when it is plugged in. This is discussed in the [[USB_Networking]] section, which you should see if the procedure above fails.

===Use the package manager===

There are three layers to the software on the FreeRunner:

* uBoot: Think of u-boot as a combination of the BIOS and Grub on a PC.
* Kernel: The Linux kernel
* Root Filesystem: The rest of the system

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intervals. There are two main methods of doing this: using the package manager opkg (discussed in this section) or [[Flashing the Neo FreeRunner|flashing the device]].

uboot, the kernel and the root filesystem can all be flashed to update them. For uboot, this is the only possibility. The advantage of flashing the kernel, rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.

Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use, so either upgrade dropbear from the FreeRunner's terminal and then upgrade the rest via ssh, or upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal. For example, go to the FreeRunner terminal and type:

# opkg install dropbear

which will upgrade it to the latest version. Then connect to the FreeRunner via ssh and type:

# opkg upgrade

If you do your first upgrade in two installments like this, it will go more smoothly.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented

=== Installing multimedia, web browsing and other applications ===

There are many applications you can install - check out the [[Repositories]] for a list of packages.

The calendar can be installed with

opkg install openmoko-dates2

For a Media Player:

opkg install openmoko-mediaplayer2
wget http://abraxa.dyndns.org:81/random/openmoko-mediaplayer-theme.tar.bz2
tar xjf openmoko-mediaplayer-theme.tar.bz2 -C /usr/share/themes/Moko/gtk-2.0
rm openmoko-mediaplayer-theme.tar.bz2

If you want a basic image viewer, have a look at the one from the gpe suite:

opkg install gpe-icons gpe-gallery

To obtain the standard web browser, use:

opkg install openmoko-browser2

An alternative browser, minimo, offers many more features.
First download and unpack it on your GNU/Linux host:

wget http://www.ginguppin.de/files/minimo.tar.bz2
tar jvxf minimo.tar.bz2

Copy it over to the FreeRunner:
scp minimo_* root@openmoko:/tmp

Then on the FreeRunner:
opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]

You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]

=== Accessing the microSD card ===

Mounted at /media/card by default.

If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc.

=== Importing contacts ===

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.

==The next steps==

Congratulations for setting up your Neo FreeRunner. There are many more ressources to help free your phone:

===Customize the interface: clock, keyboard...===

The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# /etc/init.d/xserver-nodm restart

If you rather have a regular clock instead of the digital one, do this instead:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false
# /etc/init.d/xserver-nodm restart

More information about today screen customization at [[Today/2007.2]].

With either clock, you may wish to set the correct [[Date]] and [[Timezone]].

Also, if you prefer having a full keyboard, using matchbox's qwerty keybord, see [http://www.ginguppin.de/node/15 these instructions]. Then you may also see [http://lists.openmoko.org/pipermail/community/2008-July/021296.html these], which describe a way to add an applet allowing the showing/hiding of that keyboard.

===GPS, GPRS and WLAN===

See [[GTA02 WLAN]] about wifi. See [[Manually using GPRS]].

Simple guide to get going with GPS:

# opkg install gpsd
# echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd

and restart gpsd, the gps daemon, with

# /etc/init.d/gpsd restart

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install http://www.tangogps.org/downloads/tangogps_0.9.2-r1_armv4t.ipk

More information on [[GPS]] page.

According to some [http://lists.openmoko.org/pipermail/support/2008-July/000003.html posts], GPRS might be broken currently (2007.2), though. There are also critical [[GPS Problems]]. To install the updates when they become available, you will probably want to learn about [[Booting the Neo FreeRunner]] and [[Flashing the Neo FreeRunner]].

=== The community ===
==== Mailing lists ====

There are several [[http://lists.openmoko.org/mailman/listinfo/ Mailing lists]]

There is an active community mailing list.
You may ask for help on the support mailing list : more details at https://lists.openmoko.org/mailman/listinfo/support

An excellent tool for searching all the openmoko mailing lists is http://openmoko.markmail.org/

==== The wiki ====

If you want to know more about the Neo FreeRunner then you can get more information in the following topics:

* [[GTA02 Openness]]
* [[Neo FreeRunner]]
* [[Neo FreeRunner GTA02 Hardware]]
* [[FreeRunner/Buttons and LEDs]]
* [[Latest Images]]
* [[Distributions]]

To search this wiki with Google, use the following search term:

<search term> site:http://wiki.openmoko.org/wiki/

==== Blogs ====

The [http://planet.openmoko.org/ collection of blogs on OpenMoko].

==== Other documents ====

* http://quickstart.openmoko.org/

[[Category:GTA02 Hardware]]
[[Category:Guides]]
[[Category:User Guides]]

Getting Started with your Neo FreeRunner

2008-07-20T02:53:21Z

Chgros: /* Installing multimedia, web browsing and other applications */

{{Languages|Getting Started with your Neo FreeRunner}}

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc; width:75% " |
<p align="left">
Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of [[Openmoko]]. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.</p>
! style="background:#fcfcfc; width:25% " |
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]
|}

== Package Contents ==

[[Image:GTA02ALL.png|left|400px|thumb|Inside the package]]
<br />
: [[Image:Circle２.gif|10px]] Neo FreeRunner
: [[Image:Circle２.gif|10px]] Stylus
: [[Image:Circle２.gif|10px]] Battery
: [[Image:Circle２.gif|10px]] Charger
: [[Image:Circle２.gif|10px]] USB Cable (A -> Mini-B 5-pole)
: [[Image:Circle２.gif|10px]] microSD Card 512MB & SD adapter

<div style="clear: both"> </div>

== Setting up the hardware, getting to know the Neo FreeRunner physically ==

===Installing the Micro-SD card, the SIM card, and the Battery ===

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|Open the case like this.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Opening !|center]]</td>
</tr>
<tr valign="top" style="background: #ffffff">
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here.|center]]</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|Finally, put in the battery.|center]]</td>
</tr></table>
</div>

# Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.
# Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.
# Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.
# Lift up on the SIM card holder.
# The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.
# Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo Freerunner.
# Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.
# Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.
# Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.
# Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.
# Replace the rear cover on the FreeRunner.

[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]

[[http://video.google.de/videoplay?docid=-8343770443102960945 A short video]] is also available. It was shot using the previous version of the Neo, but the installation procedures remains the same.

===Charging the Neo FreeRunner===

When using the Neo FreeRunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger (at 1000mA) or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.

Charging an empty battery at 100mA takes 12~15 hours, at 500mA takes 2,5~3,5 hours, and at 1000mA takes 1.5~2.5 hours. (90%~100%) [to be confirmed]

Make sure that the battery never discharges completely. This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work. Should the battery become completely discharged, your options are:
- Use external stand-alone charger (compatible with the Nokia BL-5C battery)
- Boot the FreeRunner with an alternative battery, or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
- Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.

===Buttons and connectors===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Power Button, USB and external GPS Antenna (left to right)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack (left to right)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Power'''
Tapping the power button exits the current application.

Holding the power button brings up a menu allowing you to:
* Power on and off the GPS, wifi, GSM, and bluetooth antennae
* Change power management mode to:
** Dim first then lock
** Dim only, don't lock
** Disabled
* Lock the screen
* Shutdown the device.</td>
<td></td>
<td>'''Aux'''

Holding the Aux button brings up a menu allowing you to:

* Hide and show the title bar (Fullscreen toggle)
* Alternate wide or tall display modes (Swap Orientation)
* Save the content of the screen as an image file (Screenshot)
</td>
</tr>
</table>

===Unlocking the screen===

When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.

== Making your first phone call: Menus and Applications ==

''Note:'' this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

====Today Page====

The first thing after you boot Openmoko should be the "Today" page. This is your home page. In the top row, you see icons that indicate the status of the phone. The second row are quick links to commonly-used applications such as the dialer. The main body of the screen is your home page, displaying a clock and other useful information. The bottom row consists of three tabs representing Today (the page you're viewing now), Launch Task Page, and Running Tasks Page.

See [[Today/2007.2]] for more information about the Today page and customization.<br clear=all />

====Launch Task Page====

{{stub}}

This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Current categories are [[PIM Suite]], [[Applications]], [[Games]], [[Utilities]], and All.

====Running Tasks Page====

{{stub}}

This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

====Exiting an Application====

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can switch tasks at any time by clicking the menu of tasks at the far upper-left of the screen, which will display a list of running tasks, allowing you to select one.

(''Note:'' If the task menu is not shown, use the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".)

===Adjusting the Volume===

As of this writing, there is no way to adjust the volume from the screen.

For now, run the terminal application or [[Getting_Started_with_your_Neo_FreeRunner#Connect_to_the_Neo_FreeRunner_By_USB_Networking|log in via usb]], and run the [[alsamixer]] application. The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use
alsactl -f ''path-to-statefile'' store
to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):
:gsmhandset.state
:gsmheadset.state
:gsmspeakerout.state
:headset.state
:stereoout.state

These correspond to the various Sound Profiles accessible in the Debug Tool under Applications.

One way to increase the volume of the microphone is to do the following:
# ssh into your Freerunner
# vi /usr/share/openmoko/scenarios/gsmhandset.state
# search for "Mic2"
# change to "value 3"
[[Freerunner_Hardware_Issues]]

==Getting into your new Linux box==

===Connect with and log in the Neo FreeRunner===

Connect the Neo FreeRunner to your Linux computer using the standard mini-USB to USB cable provided.

With the device connected,
modprobe usbnet
(if necessary) and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo (adjust your firewall if necessary):
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo with empty password
# ssh root@192.168.0.202

You will eventually want to setup your computer so that it automatically connects the Neo FreeRunner to the Internet when it is plugged in. This is discussed in the [[USB_Networking]] section, which you should see if the procedure above fails.

===Use the package manager===

There are three layers to the software on the FreeRunner:

* uBoot: Think of u-boot as a combination of the BIOS and Grub on a PC.
* Kernel: The Linux kernel
* Root Filesystem: The rest of the system

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intervals. There are two main methods of doing this: using the package manager opkg (discussed in this section) or [[Flashing the Neo FreeRunner|flashing the device]].

uboot, the kernel and the root filesystem can all be flashed to update them. For uboot, this is the only possibility. The advantage of flashing the kernel, rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.

Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use, so either upgrade dropbear from the FreeRunner's terminal and then upgrade the rest via ssh, or upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal. For example, go to the FreeRunner terminal and type:

# opkg install dropbear

which will upgrade it to the latest version. Then connect to the FreeRunner via ssh and type:

# opkg upgrade

If you do your first upgrade in two installments like this, it will go more smoothly.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented

=== Installing multimedia, web browsing and other applications ===

There are many applications you can install - check out the [[Repositories]] for a list of packages.

The calendar can be installed with

# opkg install openmoko-dates2

For a Media Player:

# opkg install openmoko-mediaplayer2
# wget http://abraxa.dyndns.org:81/random/openmoko-mediaplayer-theme.tar.bz2
# tar xjf openmoko-mediaplayer-theme.tar.bz2 -C /usr/share/themes/Moko/gtk-2.0
# rm openmoko-mediaplayer-theme.tar.bz2

If you want a basic image viewer, have a look at the one from the gpe suite:

# opkg install gpe-icons gpe-gallery

To obtain the standard web browser, use:

# opkg install openmoko-browser2

An alternative browser, minimo, offers many more features.
First download and unpack it on your GNU/Linux host:

$ wget http://www.ginguppin.de/files/minimo.tar.bz2
$ tar jvxf minimo.tar.bz2

Copy it over to the FreeRunner:
$ scp minimo_* root@openmoko:/tmp

Then on the FreeRunner:
# opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]

=== Accessing the microSD card ===

Mounted at /media/card by default.

If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc.

=== Importing contacts ===

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.

==The next steps==

Congratulations for setting up your Neo FreeRunner. There are many more ressources to help free your phone:

===Customize the interface: clock, keyboard...===

The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# /etc/init.d/xserver-nodm restart

If you rather have a regular clock instead of the digital one, do this instead:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false
# /etc/init.d/xserver-nodm restart

More information about today screen customization at [[Today/2007.2]].

With either clock, you may wish to set the correct [[Date]] and [[Timezone]].

Also, if you prefer having a full keyboard, using matchbox's qwerty keybord, see [http://www.ginguppin.de/node/15 these instructions]. Then you may also see [http://lists.openmoko.org/pipermail/community/2008-July/021296.html these], which describe a way to add an applet allowing the showing/hiding of that keyboard.

===GPS, GPRS and WLAN===

See [[GTA02 WLAN]] about wifi. See [[Manually using GPRS]].

Simple guide to get going with GPS:

# opkg install gpsd
# echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd

and restart gpsd, the gps daemon, with

# /etc/init.d/gpsd restart

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install http://www.tangogps.org/downloads/tangogps_0.9.2-r1_armv4t.ipk

More information on [[GPS]] page.

According to some [http://lists.openmoko.org/pipermail/support/2008-July/000003.html posts], GPRS might be broken currently (2007.2), though. There are also critical [[GPS Problems]]. To install the updates when they become available, you will probably want to learn about [[Booting the Neo FreeRunner]] and [[Flashing the Neo FreeRunner]].

=== The community ===
==== Mailing lists ====

There are several [[http://lists.openmoko.org/mailman/listinfo/ Mailing lists]]

There is an active community mailing list.
You may ask for help on the support mailing list : more details at https://lists.openmoko.org/mailman/listinfo/support

An excellent tool for searching all the openmoko mailing lists is http://openmoko.markmail.org/

==== The wiki ====

If you want to know more about the Neo FreeRunner then you can get more information in the following topics:

* [[GTA02 Openness]]
* [[Neo FreeRunner]]
* [[Neo FreeRunner GTA02 Hardware]]
* [[FreeRunner/Buttons and LEDs]]
* [[Latest Images]]
* [[Distributions]]

To search this wiki with Google, use the following search term:

<search term> site:http://wiki.openmoko.org/wiki/

==== Blogs ====

The [http://planet.openmoko.org/ collection of blogs on OpenMoko].

==== Other documents ====

* http://quickstart.openmoko.org/

[[Category:GTA02 Hardware]]
[[Category:Guides]]
[[Category:User Guides]]

Switching Keyboards on Om 2007.2

2008-07-20T02:49:48Z

Chgros: /* How to install it? */

==Fix Default==

To add/change the key layout on the default keypad (I added a > and a / to the 1 key), edit
/etc/multitap-pad/im-multipress.conf

[keys]
KP_0 = +;=;/;\\
KP_1 = .;,;/;>;-;?;!;@;:;(;)
KP_2 = a;b;c;2
KP_3 = d;e;f;3
KP_4 = g;h;i;4
KP_5 = j;k;l;5
KP_6 = m;n;o;6
KP_7 = p;q;r;s;7
KP_8 = t;u;v;8
KP_9 = w;x;y;z;9
KP_10 = A;B;C;2
KP_11 = D;E;F;3
KP_12 = G;H;I;4
KP_13 = J;K;L;5
KP_14 = M;N;O;6
KP_15 = P;Q;R;S;7
KP_16 = T;U;V;8
KP_17 = W;X;Y;Z;9[code]

==Matchbox keyboard==

Another keyboard is available: matchbox-keyboard. It is a full QWERTY keyboard. This howto is based on a blog entry which can be found [http://www.ginguppin.de/node/15 here]

===What does the keyboard look like?===

[[Image:Complete_QWERTY_Keyboard_On_The_Freerunner_screenshot.png|none|thumb|260px|Screenshot of the keyboard applet]]

===Considerations===

Pros:
* All keys can be generated
* Takes up less space than the keypad (multitap-pad), leaving more space for the application

Cons:
* You pretty much have to use a stylus. With difficulty you can hit keys with the corner of a fingernail.

===How to install it?===

If you use a ScaredyCat release (http://buildhost.automated.it/OM2007.2/), use the following:

opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod
opkg install matchbox-keyboard-im
opkg install matchbox-keyboard-applet

Otherwise, you'll have to download the ipk files from [http://www.ginguppin.de/files/keyboard-ipk.tar.bz2 here]. Assuming you have a working internet connection on your Freerunner, you can do the following:

cd /tmp
mkdir matchbox-keyboard
cd matchbox-keyboard
wget http://www.ginguppin.de/files/keyboard-ipk.tar.bz2
tar -jxf keyboard-ipk.tar.bz2
opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod*.ipk
opkg install matchbox-keyboard-im*.ipk
opkg install matchbox-keyboard-applet*.ipk
cd ..
rm -rf matchbox-keyboard

After that you'll have to restart the X server:
/etc/init.d/xserver-nodm restart

===How to add a keyboard toggle button===

To add a button to enable showing / hiding the keyboard, edit <tt>/etc/matchbox/session</tt>. In the list of applets after <tt>--end-applets</tt>, add <tt>keyboard</tt>, and restart your X server

===How to switch between matchbox-keyboard and multitap-pad===

If you want to keep the multitap keyboard, but also be able to start up the matchbox-keyboard, you can follow these ugly instructions:

First you must install matchbox-keyboard.
opkg install matchbox-keyboard

Do the following (from the terminal or an ssh session with DISPLAY=:0.0):
killall multitap-pad
matchbox-keyboard > /dev/null 2>&1 &

(If you type the above commands with multitap, you have to leave off the redirection of matchbox-keyboard output, since several of the keys you need are missing.)

Caveats: When you start the matchbox-keyboard, it stays up all the time. This will (among other things) prevent you from unlocking, since the keyboard covers the openmoko logo at the bottom of the lock screen. You will need to:
# nohup multitap-pad -d &
# killall matchbox-keyboard
to close it down, and at least get the matchbox keyboard going again. You should do that any time you're going to leave the neo alone for any length of time, so you can unlock it later.

To make sure you don't end up removing all your keyboard input capability, you can create a new .desktop file in /usr/share/applications/ for starting and closing the keyboard. This is pretty easy to do by copying and editing an existing .desktop file.

==Switch back to the original Openmoko keypad==

If you for whatever reason need to switch back, here are the steps:
opkg remove matchbox-keyboard-inputmethod matchbox-keyboard-im matchbox-keyboard-applet
opkg install multitap-pad

Comment or delete the following lines in /etc/gtk-2.0/gtk.immodules :
#"/usr/lib/gtk-2.0/2.10.0/immodules/libmb-im-invoker.so"
#"matchbox-im-invoker" "Virtual Keyboard" "" "" "*"

Now restart the xserver:
/etc/init.d/xserver-nodm restart

[[Category:Openmoko]]
[[Category:Technical]]

Distributions

2008-07-20T02:40:43Z

Chgros: /* Features by Distribution */

This is a skeleton to try and get the strengths and weaknesses of the various distributions available for the Neo listed in one place. See the [[Latest Images]] for information on where to find and download each distribution.

Mickey Lauer has written a good overview of the various images available, [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].

== Features by Distribution ==
{| border=1 |
| Feature || OM2007.2 || FSO || ASU || SHR || Qtopia
|-
| Description || The Openmoko 2007.2 Stack, utilizing GTK+ and assorted applications. 2007.2, since it was the 2nd iteration of the GTK+ user interface that we released in 2007. || The FSO Stack, also known as the Openmoko Framework initiative. This one is called FSO, because itýs an implementation of the freesmartphone.org APIs. You may also have seen the term Zhone which describes the framework testing user interface and is a minor part of this stack. || August Software Update. The ASU Stack, the combination of a classical smartphone stack based on Trolltech's Qtopia ported to X11 and enhanced with an EFL-based launcher and new applications. You may have seen the term Illume which is the launcher of ASU. || Stable Hybrid Release, a combination of the FSO, some of the 2007.2 GTK software, and the ASU that provides all of the functionality of the 2007.2 software, but with the stability of the FSO. || The Qtopia distribution from Trolltech, it aims to provide a ready-to use image for Openmoko devices
|-
| Availability || [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds || Now (Milestone 1) || August 2008 || No || Now
|-
| URL || ? || [http://trac.freesmartphone.org:8000/trac-example Development tracker] || [http://buildhost.openmoko.org/daily/freerunner/ Releases are labled "openmoko-qtopia-X11" ] || [[Stable Hybrid Release]] || [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]
|-
!colspan=6| Connectivity
|-
| Telephony || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes
|-
| SMS || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes
|-
| GPRS || Not through UI || Not through UI || Not through UI || N/A || Not through UI
|-
| WiFi || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || Not through UI
|-
| VoIP || ?? || ?? || ?? || ?? || ??
|-
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes
|-
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes (1) || N/A || No
|-
!colspan=6| User Interaction
|-
| Stylus friendly || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes
|-
| Finger friendly || Partly || style="background:lightgreen;" | Yes || No || N/A || style="background:lightgreen;" | Yes
|-
| Accelerometer || No || No || No || N/A || No
|-
!colspan=6| Applications
|-
| Terminal || Basic, but unusable due to lack of certain keyboard characters (unless you [[Switching_Keyboards#Matchbox_keyboard|install matchbox-keyboard]]) || No || No || N/A || style="background:lightgreen;" | Yes
|-
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes
|-
| Phonebook || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes
|-
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes
|-
!colspan=6| Application Compatibility (Toolkits / Runtimes)
|-
| GTK+ || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No
|-
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes
|-
| Java || Jalimo? || ? || ? || ? || ?
|-
| Python || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes
|-
|}

Footnotes:

(1) works, but need additional software to be installed

[[Category:Distributions]]
[[Category:Documentation]]
[[Category:FSO]]

Switching Keyboards on Om 2007.2

2008-07-20T02:36:52Z

Chgros: /* How to install it? */

==Fix Default==

To add/change the key layout on the default keypad (I added a > and a / to the 1 key), edit
/etc/multitap-pad/im-multipress.conf

[keys]
KP_0 = +;=;/;\\
KP_1 = .;,;/;>;-;?;!;@;:;(;)
KP_2 = a;b;c;2
KP_3 = d;e;f;3
KP_4 = g;h;i;4
KP_5 = j;k;l;5
KP_6 = m;n;o;6
KP_7 = p;q;r;s;7
KP_8 = t;u;v;8
KP_9 = w;x;y;z;9
KP_10 = A;B;C;2
KP_11 = D;E;F;3
KP_12 = G;H;I;4
KP_13 = J;K;L;5
KP_14 = M;N;O;6
KP_15 = P;Q;R;S;7
KP_16 = T;U;V;8
KP_17 = W;X;Y;Z;9[code]

==Matchbox keyboard==

Another keyboard is available: matchbox-keyboard. It is a full QWERTY keyboard. This howto is based on a blog entry which can be found [http://www.ginguppin.de/node/15 here]

===What does the keyboard look like?===

[[Image:Complete_QWERTY_Keyboard_On_The_Freerunner_screenshot.png|none|thumb|260px|Screenshot of the keyboard applet]]

===Considerations===

Pros:
* All keys can be generated
* Takes up less space than the keypad (multitap-pad), leaving more space for the application

Cons:
* You pretty much have to use a stylus. With difficulty you can hit keys with the corner of a fingernail.

===How to install it?===

If you use a ScaredyCat release (http://buildhost.automated.it/OM2007.2/), use the following:

opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod
opkg install matchbox-keyboard-im
opkg install matchbox-keyboard-applet

Otherwise, you'll have to download the ipk files from [http://www.ginguppin.de/files/keyboard-ipk.tar.bz2 here]. Assuming you have a working internet connection on your Freerunner, you can do the following:

cd /tmp
mkdir matchbox-keyboard
cd matchbox-keyboard
wget http://www.ginguppin.de/files/keyboard-ipk.tar.bz2
tar -jxf keyboard-ipk.tar.bz2
opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod*.ipk
opkg install matchbox-keyboard-im*.ipk
opkg install matchbox-keyboard-applet*.ipk
cd ..
rm -rf matchbox-keyboard

===How to add a keyboard toggle button===

To add a button to enable showing / hiding the keyboard, edit <tt>/etc/matchbox/session</tt>. In the list of applets after <tt>--end-applets</tt>, add <tt>keyboard</tt>, and restart your X server

===How to switch between matchbox-keyboard and multitap-pad===

If you want to keep the multitap keyboard, but also be able to start up the matchbox-keyboard, you can follow these ugly instructions:

First you must install matchbox-keyboard.
opkg install matchbox-keyboard

Do the following (from the terminal or an ssh session with DISPLAY=:0.0):
killall multitap-pad
matchbox-keyboard > /dev/null 2>&1 &

(If you type the above commands with multitap, you have to leave off the redirection of matchbox-keyboard output, since several of the keys you need are missing.)

Caveats: When you start the matchbox-keyboard, it stays up all the time. This will (among other things) prevent you from unlocking, since the keyboard covers the openmoko logo at the bottom of the lock screen. You will need to:
# nohup multitap-pad -d &
# killall matchbox-keyboard
to close it down, and at least get the matchbox keyboard going again. You should do that any time you're going to leave the neo alone for any length of time, so you can unlock it later.

To make sure you don't end up removing all your keyboard input capability, you can create a new .desktop file in /usr/share/applications/ for starting and closing the keyboard. This is pretty easy to do by copying and editing an existing .desktop file.

==Switch back to the original Openmoko keypad==

If you for whatever reason need to switch back, here are the steps:
opkg remove matchbox-keyboard-inputmethod matchbox-keyboard-im matchbox-keyboard-applet
opkg install multitap-pad

Comment or delete the following lines in /etc/gtk-2.0/gtk.immodules :
#"/usr/lib/gtk-2.0/2.10.0/immodules/libmb-im-invoker.so"
#"matchbox-im-invoker" "Virtual Keyboard" "" "" "*"

Now restart the xserver:
/etc/init.d/xserver-nodm restart

[[Category:Openmoko]]
[[Category:Technical]]

Switching Keyboards on Om 2007.2

2008-07-20T02:31:33Z

Chgros: /* Switch Keypad */

==Fix Default==

To add/change the key layout on the default keypad (I added a > and a / to the 1 key), edit
/etc/multitap-pad/im-multipress.conf

[keys]
KP_0 = +;=;/;\\
KP_1 = .;,;/;>;-;?;!;@;:;(;)
KP_2 = a;b;c;2
KP_3 = d;e;f;3
KP_4 = g;h;i;4
KP_5 = j;k;l;5
KP_6 = m;n;o;6
KP_7 = p;q;r;s;7
KP_8 = t;u;v;8
KP_9 = w;x;y;z;9
KP_10 = A;B;C;2
KP_11 = D;E;F;3
KP_12 = G;H;I;4
KP_13 = J;K;L;5
KP_14 = M;N;O;6
KP_15 = P;Q;R;S;7
KP_16 = T;U;V;8
KP_17 = W;X;Y;Z;9[code]

==Matchbox keyboard==

Another keyboard is available: matchbox-keyboard. It is a full QWERTY keyboard. This howto is based on a blog entry which can be found [http://www.ginguppin.de/node/15 here]

===What does the keyboard look like?===

[[Image:Complete_QWERTY_Keyboard_On_The_Freerunner_screenshot.png|none|thumb|260px|Screenshot of the keyboard applet]]

===Considerations===

Pros:
* All keys can be generated
* Takes up less space than the keypad (multitap-pad), leaving more space for the application

Cons:
* You pretty much have to use a stylus. With difficulty you can hit keys with the corner of a fingernail.

===How to install it?===

If you use a ScaredyCat release (http://buildhost.automated.it/OM2007.2/), use the following:

opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod
opkg install matchbox-keyboard-im
opkg install matchbox-keyboard-applet

Otherwise, you'll have to download the ipk files from [http://www.ginguppin.de/files/keyboard-ipk.tar.bz2 here]. Assuming you have a working internet connection on your Freerunner, you can do the following:

cd /tmp
mkdir matchbox-keyboard
wget http://www.ginguppin.de/files/keyboard-ipk.tar.bz2
tar -jxf keyboard-ipk.tar.bz2
opkg remove -force-depends multitap-pad
opkg install matchbox-keyboard-inputmethod*.ipk
opkg install matchbox-keyboard-im*.ipk
opkg install matchbox-keyboard-applet*.ipk
cd ..
rm -rf matchbox-keyboard

===How to add a keyboard toggle button===

To add a button to enable showing / hiding the keyboard, edit <tt>/etc/matchbox/session</tt>. In the list of applets after <tt>--end-applets</tt>, add <tt>keyboard</tt>, and restart your X server

===How to switch between matchbox-keyboard and multitap-pad===

If you want to keep the multitap keyboard, but also be able to start up the matchbox-keyboard, you can follow these ugly instructions:

First you must install matchbox-keyboard.
opkg install matchbox-keyboard

Do the following (from the terminal or an ssh session with DISPLAY=:0.0):
killall multitap-pad
matchbox-keyboard > /dev/null 2>&1 &

(If you type the above commands with multitap, you have to leave off the redirection of matchbox-keyboard output, since several of the keys you need are missing.)

Caveats: When you start the matchbox-keyboard, it stays up all the time. This will (among other things) prevent you from unlocking, since the keyboard covers the openmoko logo at the bottom of the lock screen. You will need to:
# nohup multitap-pad -d &
# killall matchbox-keyboard
to close it down, and at least get the matchbox keyboard going again. You should do that any time you're going to leave the neo alone for any length of time, so you can unlock it later.

To make sure you don't end up removing all your keyboard input capability, you can create a new .desktop file in /usr/share/applications/ for starting and closing the keyboard. This is pretty easy to do by copying and editing an existing .desktop file.

==Switch back to the original Openmoko keypad==

If you for whatever reason need to switch back, here are the steps:
opkg remove matchbox-keyboard-inputmethod matchbox-keyboard-im matchbox-keyboard-applet
opkg install multitap-pad

Comment or delete the following lines in /etc/gtk-2.0/gtk.immodules :
#"/usr/lib/gtk-2.0/2.10.0/immodules/libmb-im-invoker.so"
#"matchbox-im-invoker" "Virtual Keyboard" "" "" "*"

Now restart the xserver:
/etc/init.d/xserver-nodm restart

[[Category:Openmoko]]
[[Category:Technical]]