Openmoko - User contributions [en]

Toolchain

2009-04-04T02:09:43Z

Newkirk: /* Building a sample project */

{{Languages|Toolchain}}

= Introduction =

A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:

;(a) Developing a single application (or a kernel or a bootloader)
:For this, you should use a prebuilt toolchain from the Openmoko project. On this page you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. (You might have heard about ''OpenEmbedded'', however as an application programmer, you should '''not''' be using OpenEmbedded.)
;(b) System Integration and customizing a distribution
:For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.

=Basic toolchain usage=

==Prerequisites==

You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.

Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').

A (partial) list of required packages -- please append as necessary:

* For most Linux version you might only need to install the packages
** autoconf, automake
** binutils, gcc, gcc-c++
** libtool
** ccache
** intltool

* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev \
ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools fakeroot alien check

* For Ubuntu 8.10 the following is additionally required, install also those above:
sudo apt-get install uboot-mkimage

* For Fedora-Core the following is required, while logged in as <tt>root</tt>:
yum install gcc gcc-c++ autoconf automake binutils libtool glib2-devel \
ccache libXrender-devel intltool GConf2-devel mtools gettext-devel
Fedora-Core does not appear to have <tt>libmokoui2</tt> available.

* For Debian (Sid) do (as root):
apt-get install build-essential ccache autoconf automake autotools-dev libtool \
gettext intltool curl uboot-mkimage mtools fakeroot alien check libglib2.0-dev \
libxrender-dev libgconf2-dev

==Downloading and installing==

{{Note|If you wish to improve an existing Openmoko application and you are running Debian or Ubuntu i386 (i.e. you can install a .deb), you may wish to skip the below and instead use:
[http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html Openmoko application development in 5 minutes] by Andreas Dalsgaard. (based on the 2007.2 stack)}}

The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/developer/toolchains downloads.openmoko.org]:

* Creating a destination directory can be anywhere, but for example:

mkdir ~/sources
cd ~/sources

* Download the latest package:

wget http://downloads.openmoko.org/developer/toolchains/openmoko-i686-20090323-armv4t-linux-gnueabi-toolchain-openmoko.tar.bz2

Next, you want to extract it on your filesystem. This toolchain is ''not'' relocatable, it needs to be installed into <tt>/usr/local/openmoko/</tt>.
Now you have the following options:

* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):

cd /
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2

* On Debian-based systems (e.g. Ubuntu), you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:

bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2
gzip openmoko-*-arm-linux-gnueabi-toolchain.tar
fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz
sudo dpkg -i openmoko_*-arm-linux-gnueabi-toolchain*.deb

* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE, using [[BitBake]]:

bitbake meta-toolchain-openmoko

Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to [http://learnlinux.tsf.org.za/courses/build/shell-scripting/ch10s02.html source] it.
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need
to start "sh" or "bash" first.

. /usr/local/openmoko/arm/bin/setup-env

* At least, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make).
export PATH=$PATH:/usr/local/openmoko/arm/bin
Note: This is will only last for your current session. Add it to your shell startup scripts to make it permanent (~/.bashrc for instance).

==Installing New Libraries==

Openmoko toolchain doesn't include many libraries by default. However, it can download and install libraries that already exist in the Openmoko repository. It refers to the [http://downloads.openmoko.org/repository/testing/ Testing Repository] by default. There are wrong address in /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf. Check what you have, and modify if needed. You can check with browser what you want to use http://downloads.openmoko.org/repository/

#Some working example. /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf
src oe http://downloads.openmoko.org/repository/Om2008.8/
arch all 1
src oe-all http://downloads.openmoko.org/repository/Om2008.8/all
arch any 6
arch noarch 11
arch arm 16
arch armv4t 21
src oe-armv4t http://downloads.openmoko.org/repository/Om2008.8//armv4t
arch om-gta02 36
src oe-om-gta02 http://downloads.openmoko.org/repository/Om2008.8/om-gta02

*You need to alter some environment variables before you download libraries.
. /usr/local/openmoko/arm/environment-setup

*First, update the opkg database (Notice, you should use alias '''opkg-target''' and not '''opkg'''. If you get an "Could not obtain administrative lock" error, try to become root with "sudo su" and don't forget to rerun the scripts to set your environment variables if necessary.)
opkg-target update

*Second, select a package that you want. Let's use edje as an example. If you want to develop a project which use edje of Enlightenment, you can use '''opkg-target list''' to print out how many packages you can have. Of course, command '''grep''' will help you a lot. (Remember, you should install the -dev package and not only libedje.)
opkg-target list |grep edje-dev

*Third, install it
opkg-target install libedje-dev
*Fourth, have a cup of coffee and wait.

==Building a sample project==

To build the sample project you need to install libmokoui2-dev and gconf-dbus-dev in your opkg environment. Setup your environment like described there [http://wiki.openmoko.org/wiki/Toolchain#Installing_New_Libraries]. Now install the libraries with the following command:
opkg-target install libmokoui2-dev gconf-dbus-dev

In a chosen destination directory (in this example ~/):

* copy the downloaded sample application source:

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:

. /usr/local/openmoko/arm/bin/setup-env

* I came to the conclusion that more has to be done before the next step.

opkg-target update
opkg-target install libedje-dev
opkg-target install packagekit-dev
opkg-target install edbus-dev
opkg-target install libetk-dev
opkg-target install libts-dev

* One can chown -R <your-name>.<your-name> /usr/local/openmoko/arm, and
everything should work under the non-root account. Here is a useful link if you have problems with the command below ( https://kerneltrap.org/mailarchive/openmoko-devel/2008/9/17/3318834 )

* You need to create a build configuration for this application. This also checks if all needed libraries, tools, etc.. is available on your system. If this fails see the notes about the needed packages in the section "Prerequisites" mentioned earlier.

om-conf openmoko-sample2

* Optionally now you can modify the source code in openmoko-sample2/src. Before the next step, go into the sample directory.

cd openmoko-sample2

* If you are using an older version of the toolchain, you may have to create the makefile by running "./autogen.sh". Otherwise, to build the application from the source code just type:

make

* If there are errors (i.e. "You need to install gnome-common from the GNOME CVS") deal with them. Also see "Troubleshooting" section at the end of this page for known issues.

If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.
om-conf --prefix=/usr/local/openmoko openmoko-sample2
cd openmoko-sample2
make install

==How to create your own project from the sample project==

In order to build your own project by using openmoko-sample2 files, some changes are needed:

* copy the downloaded sample application source

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* rename the folder with the name of your project (in this example your-project-name) and delete old sample files

mv openmoko-sample2 your-project-name
cd your-project-name
cd src
rm *.c

* copy your sources (in this example your-sources) into src/

cp your-sources .
cd ..

* now in the main folder modify autogen.sh by updating the following lines

PKG_NAME="your-project-name"

* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)

AC_INIT(your-project-name, 0.0.1, http://www.openmoko.org/)
AC_CONFIG_SRCDIR(src/main.c)

* go into data/ folder and rename these files with the name of your project

cd data
mv openmoko-sample.png your-project-name.png
mv openmoko-sample.desktop your-project-name.desktop

* modify Makefile.am inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify Makefile.in inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify your-project-name.desktop by updating the following lines

Name=your-project-name
Encoding=UTF-8
Version=0.0.1
Type=Application
Exec=your-project-name

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

bin_PROGRAMS = your-project-name
your_project_name_SOURCES = \
main.c
your_project_name_LDADD = @DEPENDENCIES_LIBS@

* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names

==Packaging your application==

We have included a script to make an ipkg out of your application. Note that this is not needed to test your application on the Neo (for that you can just scp the resulting binary and data over), however it's very handy if you want to distribute your application to others.

om-make-ipkg openmoko-sample2

Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your
Neo and install it:

scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:
ssh root@192.168.0.202 opkg install openmoko-sample2_0.1_armv4t.ipk

Note that while you can redistribute the generated ipkg, be aware that this is a bare-bones ipk that contains no further information, i.e. you will lack library dependencies. See below how to fix this.

You can also supply the version number, a description, and an author / contacts string in a control file:

om-make-ipkg myapp myapp_control

A template of myapp_control:

Package: $appname
Version: 0.1
Description: package built by openmoko toolchain
Section: openmoko/applications
Priority: optional
Maintainer: $USER
Architecture: armv4t
Homepage: http://www.openmoko.org/
Depends:
Source: ${SRC}

==Where to go from here==

Using the external toolchain is an easy way to build applications for your Neo. If you are familiar with this procedure, you might also want to look into
* Using [[Qemu]] to test your applications in an emulated environment
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency
* Using [[OpenEmbedded]] to customize your Openmoko distribution image

=Advanced topics=
==Building Openmoko Kernel from git repo using Toolchain==

You may build the newest 2.6.28 kernel with these commands:

git clone git://git.openmoko.org/git/kernel.git linux-2.6
cd linux-2.6
git checkout -b mystable origin/andy-tracking
mkdir GTA02
cp arch/arm/configs/gta02-moredrivers-defconfig GTA02/.config
./build GTA02 dummy

The ''dummy'' option is required for the modules to be nicely packaged into a .tar.gz package that can be extracted on the target, in addition to flashing/installing the kernel. The "dummy" just means "some parameter given", for which there is a check in the code eventually for some reason...

You may need to edit the ./build script for the toolchain directory.

Read more information about the different branches of Openmoko's Linux kernel at: http://git.openmoko.org/?p=kernel.git;a=summary

A different approach explained in more detail can be found at [[Howto compile Openmoko kernel for Neo Freerunner]].

=== Old troubleshooting information ===

If it fails with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"

to:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"

I also had to change the 'build' script to hardcode the path to the compiler.

==Using toolchain provided libraries==
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

Sooner or later you will want to compile an application that has dependencies which can't be fulfilled by the precompiled toolchain, e.g. some obscure libraries.

In that case, feel free to request the inclusion of additional libraries into the next release of the Openmoko toolchain. Until then, here is how you enhance your already installed toolchain. Say, we want to add the library called liburiparse:

cd ~/source
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2
tar xjf uriparser-0.6.0.tar.bz2
cd uriparser-0.6.0
./configure --host=arm-angstrom-linux-gnueabi \
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr
make
make install

That's it.

==Getting your application packaged by OE==

If you have written a cool application which you want to share with others, the best way to do that is to

# upload your application source code to a public location
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

* Some Versions of the Toolchain have corrupt .la files. If you compile an application using the Toolchain and you receive a '/space/fic/openmoko-daily/neo1973/work/armv4t-angstrom-linux-gnueabi/pango-1.18.3-r0/pango-1.18.3/pango/libpangoft2-1.0.la' error, you are affected. To fix that you should go to your "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib" directory and open the affected .la files and change "/space/fic..." to "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib". You have to fix more than one .la file. For the pango error you have to change "libpangocairo-1.0.la", but there are more corrupt .la files.

Attached is a beta fix for the .la problem. Untar the .tar.bz2 as root, and execute the following bash script as root:

#!/bin/sh
DIR=/usr/local/openmoko/arm
for la in `find $DIR -iname \*.la`; do
dependency_libs=
. $la
for lib in $dependency_libs ; do
delib=`echo $lib | grep -E .la$`
if [ -z $delib ] ; then
echo -n
elif [ -f $delib ]; then
echo -n
else
basedelib=`basename $delib`
replacedelibs=`find $DIR -iname $basedelib`
found=0
for replacedelib in $replacedelibs ; do
if [ $replacedelib == $delib ]; then
found=1
fi
done
if [ $found -gt 0 ] ; then
echo -n
else
sed_delib=`echo $delib | sed 's/\//\\\\\//g'`
sed_replacedelib=`echo $replacedelib | sed 's/\//\\\\\//g'`
# A bit slow, we could chain expressions for speed. :)
cp $la $la.old
cat $la | sed "s/$sed_delib/$sed_replacedelib/g" > $la.new
mv $la.new $la
rm $la.old
fi
fi
done
done

* If you can't get the toolchain working in your distro (for example if you keep bumping into strange autotools issues), you can set up the toolchain inside a Debian chroot, which should provide reasonably standard environment. There's a guide for it: http://linux.fjfi.cvut.cz/~zub/debian-chroot-toolchain.txt
* If you get something similar:
../libtool: X--tag=CC: command not found

under Ubuntu 8.10. Try do this:

sudo apt-get remove libtool

wget http://ftp.sjtu.edu.cn/ubuntu/pool/main/libt/libtool/libtool_1.5.26-1ubuntu1_i386.deb
or
wget http://ftp.sjtu.edu.cn/ubuntu/pool/main/libt/libtool/libtool_1.5.26-1ubuntu1_amd64.deb

sudo dpkg -i libtool_1.5.26-1ubuntu1_i386.deb

The original message [http://lists.openmoko.org/pipermail/devel/2008-December/003530.html here]

* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.

[[Category:Application Developer]]

[[Category:Application Developer]]

Download

2009-02-18T02:20:40Z

Newkirk: /* SHR images (Stable Hybrid Release) */

{{Languages|Download}}
This page lists various images you can try out on your Openmoko supported smartphone and some [[#Other downloads]].

See [[Distributions]] for a more descriptive comparison. Then see [[Development Branches Policy]] when you want to know where the really bleeding edge is.

{|align=right
|__TOC__
|}

== Installation instructions ==

See [[Flashing the Neo FreeRunner]] for installation instructions. Neo 1973 users: [[Getting Started with your Neo1973]]. If you want to install a system to a microSD card, see [[Booting from SD]].

The release directories can contain up to four files:

* a Root FileSystem image. These are the files with '''rootfs''' in their name. They come both as a .jffs2 ready-to-flash image, and as a .tar.gz ready-to-cp tarball.
* a Kernel image (files with '''uimage''' in their name).
* a u-boot bootloader (file with '''u-boot''' in the name).
* a splash image file.

Also, the archive directory contains two identical versions of most files, one having the date in the filename. For those convenience ?

One usually needs only to flash the phone with the root filesystem and the kernel image. The splash image is eyecandy. The u-Boot bootloader is a critical component, you don't want to install a new version of that systematically, but there have been improvements since the one released in shipping phones.

== Openmoko Inc. driven release targets ==
=== Om 2008.12 ===
Om 2008.12 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.12/ here]

{{Main|Om 2008.12 Update}}

=== Om 2008.9 (ASU) ===

Om 2008.9 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.9/ here]

{{Main|Om 2008.9 Update}}

'''Neo FreeRunner images'''

There is no need to reflash if you have installed Om 2008.8 and used ''opkg update && opkg upgrade''.
Comment about naming scheme on the [http://lists.openmoko.org/pipermail/community/2008-September/031003.html community mailinglist]

=== The bleeding edge: Om "base / empty" images ===

The ''org.openmoko.dev'' branch does not have any applications preinstalled other than settings and installer, and it is unstable for now.

Images for ''testing'' are at:
http://downloads.openmoko.org/daily/

To get packages from ''testing'', use this ''/etc/opkg/testing.conf'' :
<pre>
src/gz testing-all http://downloads.openmoko.org/repository/testing/all
src/gz testing-arm http://downloads.openmoko.org/repository/testing/armv4t
src/gz testing-neo http://downloads.openmoko.org/repository/testing/neo1973
src/gz testing-gta02 http://downloads.openmoko.org/repository/testing/om-gta02
</pre>


''unstable'' comes from the same branch, compiled with the AUTOREV flag. There are no images, but packages are at http://downloads.openmoko.org/repository/unstable/

Reference: See [http://lists.openmoko.org/pipermail/community/2008-August/027997.html "Repository and Images" announcement] for details on other "Base image", "testing" and "unstable".

Once you have this base image, you can install the GTK+ telephony apps including gsmd, or Qtopia, or Mickey's framework. Check out the [[FDOM]] page for an idea of what to install.

=== Om 2007.2 images (GTK) ===

{{Main|Om 2007.2}}

Openmoko '''discontinued support''' for this release.
Two external developers still offer their own builds.

==== Celtune ====

Celtune offers different Images and a huge amount of packages (2007.2, pyneo, fso) for neo1973, freerunner and others. Celtune images can be found [http://rabenfrost.net/celtune/ here].

==== ScaredyCat ====

[http://blog.automated.it/category/openmoko/ Andy Powell] maintains images based on the 2007.2 software stack for the gta01 and gta02. A. Powell's ScaredyCat images can be found [http://buildhost.automated.it/OM2007.2/ here].

=== FSO images (freesmartphone.org) ===

{{Main|OpenmokoFramework}}

The file system will be in a jffs2 "summary" file. A file with the extension ".jffs2.summary" can be flashed to the FreeRunner just like an ordinary jffs2 file.

* [http://git.freesmartphone.org/ Browse the source]

* [[OpenmokoFramework/Status_Update_6|newest status update]]

* [http://downloads.freesmartphone.org/fso-stable/milestone5/ Downloads]

=== Android ===
Android now can run on Openmoko FreeRunner.
About the Image, you can check [[Android]] page , to get the detail information.
Android imagescan be found [http://people.openmoko.org/sean_mcneil/ here].

== Openmoko Community driven release targets ==

=== FDOM ===

{{Main|FDOM - a Fat and Dirty OM based distribution}}

Download images: http://compartida.net/openmoko/FDOM/

=== SHR images (Stable Hybrid Release) ===
{{Main|SHR}}
The Stable Hybrid Release (SHR) is intended to be a community driven distribution composed of the FSO and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the Openmoko2007.2 GTK software in combination with the new FSO, but things have changed.

Download images (unstable currently recommended):
* [http://shr.bearstech.com/shr-testing/images/om-gta02 Neo Freerunner testing]
* [http://shr.bearstech.com/shr-testing/images/neo1973 Neo 1973 testing]
* [http://build.shr-project.org/shr-unstable/images/om-gta02 Neo Freerunner unstable]
* [http://build.shr-project.org/shr-unstable/images/om-gta01 Neo 1973 unstable]

== Non-Openmoko distributions ==

=== Qt Extended (formerly Qtopia) images ===

:''Main article: [[Qtopia / Qt Extended on FreeRunner|Qt Extended]]''

Images are available on the [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6&orderby=dateD Qt Extended download page], make sure your browser sends referrer Header when downloading. (Note: direct linking to the files does not work.)

'''Neo FreeRunner'''

* Qt Extended flash image for FIC Neo Freerunner (gta02) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=98 here]. (The tarball contains rootfs and kernel)
* If you need to also download mwester's daily kernel (needed for previous version 4.4.1) you can find it [http://moko.mwester.net/dl.html#kernels here].

'''Neo 1973'''

* Qt Extended flash image for FIC Neo 1973 (gta01) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=99 here]. (The tarball contains rootfs and kernel)

* A alternate Neo 1973 image can be downloaded [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz here]

'''More Qtopia downloads'''

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.

=== Debian images ===

{{Main|Debian}}

=== Hackable:1 images ===

{{Main|Hackable:1}}

== Other downloads ==

=== Applications repositories ===

If you are looking for a specific application instead of a full filesystem image:
* {{Main|Community Repository}}
* {{Main|Users Repositories}}

=== CAD files ===
You can download CAD files [http://downloads.openmoko.org/developer/CAD/ here].

=== Schematics ===

You can download the schematics of [[Neo 1973]] (GTA01) and [[Neo FreeRunner]] (GTA02) [http://downloads.openmoko.org/developer/schematics/ here]

=== Press material ===

Download Neo FreeRunner photos in various sizes for print and web use [http://openmoko.com/press-press-material.html here]

=== Tiddlywiki version of wiki.openmoko.org ===
If you want to carry this wiki along with you and to use it offline, then download
it [http://om-tiddlywiki.projects.openmoko.org/openmokowiki.html here] and store it locally, then browse through the pages which you think you need to have, click "save changes", so next time you open it all articles you have fetched previously will be available to you.

[[Category:Distributions]]

Download

2009-02-18T01:46:14Z

Newkirk: /* SHR images (Stable Hybrid Release) */

{{Languages|Download}}
This page lists various images you can try out on your Openmoko supported smartphone and some [[#Other downloads]].

See [[Distributions]] for a more descriptive comparison. Then see [[Development Branches Policy]] when you want to know where the really bleeding edge is.

{|align=right
|__TOC__
|}

== Installation instructions ==

See [[Flashing the Neo FreeRunner]] for installation instructions. Neo 1973 users: [[Getting Started with your Neo1973]]. If you want to install a system to a microSD card, see [[Booting from SD]].

The release directories can contain up to four files:

* a Root FileSystem image. These are the files with '''rootfs''' in their name. They come both as a .jffs2 ready-to-flash image, and as a .tar.gz ready-to-cp tarball.
* a Kernel image (files with '''uimage''' in their name).
* a u-boot bootloader (file with '''u-boot''' in the name).
* a splash image file.

Also, the archive directory contains two identical versions of most files, one having the date in the filename. For those convenience ?

One usually needs only to flash the phone with the root filesystem and the kernel image. The splash image is eyecandy. The u-Boot bootloader is a critical component, you don't want to install a new version of that systematically, but there have been improvements since the one released in shipping phones.

== Openmoko Inc. driven release targets ==
=== Om 2008.12 ===
Om 2008.12 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.12/ here]

{{Main|Om 2008.12 Update}}

=== Om 2008.9 (ASU) ===

Om 2008.9 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.9/ here]

{{Main|Om 2008.9 Update}}

'''Neo FreeRunner images'''

There is no need to reflash if you have installed Om 2008.8 and used ''opkg update && opkg upgrade''.
Comment about naming scheme on the [http://lists.openmoko.org/pipermail/community/2008-September/031003.html community mailinglist]

=== The bleeding edge: Om "base / empty" images ===

The ''org.openmoko.dev'' branch does not have any applications preinstalled other than settings and installer, and it is unstable for now.

Images for ''testing'' are at:
http://downloads.openmoko.org/daily/

To get packages from ''testing'', use this ''/etc/opkg/testing.conf'' :
<pre>
src/gz testing-all http://downloads.openmoko.org/repository/testing/all
src/gz testing-arm http://downloads.openmoko.org/repository/testing/armv4t
src/gz testing-neo http://downloads.openmoko.org/repository/testing/neo1973
src/gz testing-gta02 http://downloads.openmoko.org/repository/testing/om-gta02
</pre>


''unstable'' comes from the same branch, compiled with the AUTOREV flag. There are no images, but packages are at http://downloads.openmoko.org/repository/unstable/

Reference: See [http://lists.openmoko.org/pipermail/community/2008-August/027997.html "Repository and Images" announcement] for details on other "Base image", "testing" and "unstable".

Once you have this base image, you can install the GTK+ telephony apps including gsmd, or Qtopia, or Mickey's framework. Check out the [[FDOM]] page for an idea of what to install.

=== Om 2007.2 images (GTK) ===

{{Main|Om 2007.2}}

Openmoko '''discontinued support''' for this release.
Two external developers still offer their own builds.

==== Celtune ====

Celtune offers different Images and a huge amount of packages (2007.2, pyneo, fso) for neo1973, freerunner and others. Celtune images can be found [http://rabenfrost.net/celtune/ here].

==== ScaredyCat ====

[http://blog.automated.it/category/openmoko/ Andy Powell] maintains images based on the 2007.2 software stack for the gta01 and gta02. A. Powell's ScaredyCat images can be found [http://buildhost.automated.it/OM2007.2/ here].

=== FSO images (freesmartphone.org) ===

{{Main|OpenmokoFramework}}

The file system will be in a jffs2 "summary" file. A file with the extension ".jffs2.summary" can be flashed to the FreeRunner just like an ordinary jffs2 file.

* [http://git.freesmartphone.org/ Browse the source]

* [[OpenmokoFramework/Status_Update_6|newest status update]]

* [http://downloads.freesmartphone.org/fso-stable/milestone5/ Downloads]

=== Android ===
Android now can run on Openmoko FreeRunner.
About the Image, you can check [[Android]] page , to get the detail information.
Android imagescan be found [http://people.openmoko.org/sean_mcneil/ here].

== Openmoko Community driven release targets ==

=== FDOM ===

{{Main|FDOM - a Fat and Dirty OM based distribution}}

Download images: http://compartida.net/openmoko/FDOM/

=== SHR images (Stable Hybrid Release) ===
{{Main|SHR}}
The Stable Hybrid Release (SHR) is intended to be a community driven distribution composed of the FSO and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the Openmoko2007.2 GTK software in combination with the new FSO, but things have changed.

Download images (unstable currently recommended):
* [http://build.shr-project.org/shr-testing/images/om-gta02/?C=M;O=D Neo Freerunner testing]
* [http://build.shr-project.org/shr-testing/images/neo1973/?C=M;O=D Neo 1973 testing]
* [http://build.shr-project.org/shr-unstable/images/om-gta02/?C=M;O=D Neo Freerunner unstable]
* [http://build.shr-project.org/shr-unstable/images/om-gta01/?C=M;O=D Neo 1973 unstable]

== Non-Openmoko distributions ==

=== Qt Extended (formerly Qtopia) images ===

:''Main article: [[Qtopia / Qt Extended on FreeRunner|Qt Extended]]''

Images are available on the [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6&orderby=dateD Qt Extended download page], make sure your browser sends referrer Header when downloading. (Note: direct linking to the files does not work.)

'''Neo FreeRunner'''

* Qt Extended flash image for FIC Neo Freerunner (gta02) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=98 here]. (The tarball contains rootfs and kernel)
* If you need to also download mwester's daily kernel (needed for previous version 4.4.1) you can find it [http://moko.mwester.net/dl.html#kernels here].

'''Neo 1973'''

* Qt Extended flash image for FIC Neo 1973 (gta01) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=99 here]. (The tarball contains rootfs and kernel)

* A alternate Neo 1973 image can be downloaded [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz here]

'''More Qtopia downloads'''

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.

=== Debian images ===

{{Main|Debian}}

=== Hackable:1 images ===

{{Main|Hackable:1}}

== Other downloads ==

=== Applications repositories ===

If you are looking for a specific application instead of a full filesystem image:
* {{Main|Community Repository}}
* {{Main|Users Repositories}}

=== CAD files ===
You can download CAD files [http://downloads.openmoko.org/developer/CAD/ here].

=== Schematics ===

You can download the schematics of [[Neo 1973]] (GTA01) and [[Neo FreeRunner]] (GTA02) [http://downloads.openmoko.org/developer/schematics/ here]

=== Press material ===

Download Neo FreeRunner photos in various sizes for print and web use [http://openmoko.com/press-press-material.html here]

=== Tiddlywiki version of wiki.openmoko.org ===
If you want to carry this wiki along with you and to use it offline, then download
it [http://om-tiddlywiki.projects.openmoko.org/openmokowiki.html here] and store it locally, then browse through the pages which you think you need to have, click "save changes", so next time you open it all articles you have fetched previously will be available to you.

[[Category:Distributions]]

Download

2009-02-18T01:44:37Z

Newkirk: /* SHR images (Stable Hybrid Release) */

{{Languages|Download}}
This page lists various images you can try out on your Openmoko supported smartphone and some [[#Other downloads]].

See [[Distributions]] for a more descriptive comparison. Then see [[Development Branches Policy]] when you want to know where the really bleeding edge is.

{|align=right
|__TOC__
|}

== Installation instructions ==

See [[Flashing the Neo FreeRunner]] for installation instructions. Neo 1973 users: [[Getting Started with your Neo1973]]. If you want to install a system to a microSD card, see [[Booting from SD]].

The release directories can contain up to four files:

* a Root FileSystem image. These are the files with '''rootfs''' in their name. They come both as a .jffs2 ready-to-flash image, and as a .tar.gz ready-to-cp tarball.
* a Kernel image (files with '''uimage''' in their name).
* a u-boot bootloader (file with '''u-boot''' in the name).
* a splash image file.

Also, the archive directory contains two identical versions of most files, one having the date in the filename. For those convenience ?

One usually needs only to flash the phone with the root filesystem and the kernel image. The splash image is eyecandy. The u-Boot bootloader is a critical component, you don't want to install a new version of that systematically, but there have been improvements since the one released in shipping phones.

== Openmoko Inc. driven release targets ==
=== Om 2008.12 ===
Om 2008.12 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.12/ here]

{{Main|Om 2008.12 Update}}

=== Om 2008.9 (ASU) ===

Om 2008.9 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.9/ here]

{{Main|Om 2008.9 Update}}

'''Neo FreeRunner images'''

There is no need to reflash if you have installed Om 2008.8 and used ''opkg update && opkg upgrade''.
Comment about naming scheme on the [http://lists.openmoko.org/pipermail/community/2008-September/031003.html community mailinglist]

=== The bleeding edge: Om "base / empty" images ===

The ''org.openmoko.dev'' branch does not have any applications preinstalled other than settings and installer, and it is unstable for now.

Images for ''testing'' are at:
http://downloads.openmoko.org/daily/

To get packages from ''testing'', use this ''/etc/opkg/testing.conf'' :
<pre>
src/gz testing-all http://downloads.openmoko.org/repository/testing/all
src/gz testing-arm http://downloads.openmoko.org/repository/testing/armv4t
src/gz testing-neo http://downloads.openmoko.org/repository/testing/neo1973
src/gz testing-gta02 http://downloads.openmoko.org/repository/testing/om-gta02
</pre>


''unstable'' comes from the same branch, compiled with the AUTOREV flag. There are no images, but packages are at http://downloads.openmoko.org/repository/unstable/

Reference: See [http://lists.openmoko.org/pipermail/community/2008-August/027997.html "Repository and Images" announcement] for details on other "Base image", "testing" and "unstable".

Once you have this base image, you can install the GTK+ telephony apps including gsmd, or Qtopia, or Mickey's framework. Check out the [[FDOM]] page for an idea of what to install.

=== Om 2007.2 images (GTK) ===

{{Main|Om 2007.2}}

Openmoko '''discontinued support''' for this release.
Two external developers still offer their own builds.

==== Celtune ====

Celtune offers different Images and a huge amount of packages (2007.2, pyneo, fso) for neo1973, freerunner and others. Celtune images can be found [http://rabenfrost.net/celtune/ here].

==== ScaredyCat ====

[http://blog.automated.it/category/openmoko/ Andy Powell] maintains images based on the 2007.2 software stack for the gta01 and gta02. A. Powell's ScaredyCat images can be found [http://buildhost.automated.it/OM2007.2/ here].

=== FSO images (freesmartphone.org) ===

{{Main|OpenmokoFramework}}

The file system will be in a jffs2 "summary" file. A file with the extension ".jffs2.summary" can be flashed to the FreeRunner just like an ordinary jffs2 file.

* [http://git.freesmartphone.org/ Browse the source]

* [[OpenmokoFramework/Status_Update_6|newest status update]]

* [http://downloads.freesmartphone.org/fso-stable/milestone5/ Downloads]

=== Android ===
Android now can run on Openmoko FreeRunner.
About the Image, you can check [[Android]] page , to get the detail information.
Android imagescan be found [http://people.openmoko.org/sean_mcneil/ here].

== Openmoko Community driven release targets ==

=== FDOM ===

{{Main|FDOM - a Fat and Dirty OM based distribution}}

Download images: http://compartida.net/openmoko/FDOM/

=== SHR images (Stable Hybrid Release) ===
{{Main|SHR}}
The Stable Hybrid Release (SHR) is intended to be a community driven distribution composed of the FSO and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the Openmoko2007.2 GTK software in combination with the new FSO, but things have changed.
Download images (unstable currently recommended):
* [http://build.shr-project.org/shr-testing/images/om-gta02/?C=M;O=D Neo Freerunner testing]
* [http://build.shr-project.org/shr-testing/images/neo1973/?C=M;O=D Neo 1973 testing]
* [http://build.shr-project.org/shr-unstable/images/om-gta02/?C=M;O=D Neo Freerunner unstable]
* [http://build.shr-project.org/shr-unstable/images/om-gta01/?C=M;O=D Neo 1973 unstable]

== Non-Openmoko distributions ==

=== Qt Extended (formerly Qtopia) images ===

:''Main article: [[Qtopia / Qt Extended on FreeRunner|Qt Extended]]''

Images are available on the [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6&orderby=dateD Qt Extended download page], make sure your browser sends referrer Header when downloading. (Note: direct linking to the files does not work.)

'''Neo FreeRunner'''

* Qt Extended flash image for FIC Neo Freerunner (gta02) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=98 here]. (The tarball contains rootfs and kernel)
* If you need to also download mwester's daily kernel (needed for previous version 4.4.1) you can find it [http://moko.mwester.net/dl.html#kernels here].

'''Neo 1973'''

* Qt Extended flash image for FIC Neo 1973 (gta01) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=99 here]. (The tarball contains rootfs and kernel)

* A alternate Neo 1973 image can be downloaded [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz here]

'''More Qtopia downloads'''

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.

=== Debian images ===

{{Main|Debian}}

=== Hackable:1 images ===

{{Main|Hackable:1}}

== Other downloads ==

=== Applications repositories ===

If you are looking for a specific application instead of a full filesystem image:
* {{Main|Community Repository}}
* {{Main|Users Repositories}}

=== CAD files ===
You can download CAD files [http://downloads.openmoko.org/developer/CAD/ here].

=== Schematics ===

You can download the schematics of [[Neo 1973]] (GTA01) and [[Neo FreeRunner]] (GTA02) [http://downloads.openmoko.org/developer/schematics/ here]

=== Press material ===

Download Neo FreeRunner photos in various sizes for print and web use [http://openmoko.com/press-press-material.html here]

=== Tiddlywiki version of wiki.openmoko.org ===
If you want to carry this wiki along with you and to use it offline, then download
it [http://om-tiddlywiki.projects.openmoko.org/openmokowiki.html here] and store it locally, then browse through the pages which you think you need to have, click "save changes", so next time you open it all articles you have fetched previously will be available to you.

[[Category:Distributions]]

Download

2009-02-18T01:42:46Z

Newkirk: /* SHR images (Stable Hybrid Release) */

{{Languages|Download}}
This page lists various images you can try out on your Openmoko supported smartphone and some [[#Other downloads]].

See [[Distributions]] for a more descriptive comparison. Then see [[Development Branches Policy]] when you want to know where the really bleeding edge is.

{|align=right
|__TOC__
|}

== Installation instructions ==

See [[Flashing the Neo FreeRunner]] for installation instructions. Neo 1973 users: [[Getting Started with your Neo1973]]. If you want to install a system to a microSD card, see [[Booting from SD]].

The release directories can contain up to four files:

* a Root FileSystem image. These are the files with '''rootfs''' in their name. They come both as a .jffs2 ready-to-flash image, and as a .tar.gz ready-to-cp tarball.
* a Kernel image (files with '''uimage''' in their name).
* a u-boot bootloader (file with '''u-boot''' in the name).
* a splash image file.

Also, the archive directory contains two identical versions of most files, one having the date in the filename. For those convenience ?

One usually needs only to flash the phone with the root filesystem and the kernel image. The splash image is eyecandy. The u-Boot bootloader is a critical component, you don't want to install a new version of that systematically, but there have been improvements since the one released in shipping phones.

== Openmoko Inc. driven release targets ==
=== Om 2008.12 ===
Om 2008.12 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.12/ here]

{{Main|Om 2008.12 Update}}

=== Om 2008.9 (ASU) ===

Om 2008.9 is an updated release of Om 2008.8.
You can download the image [http://downloads.openmoko.org/distro/releases/Om2008.9/ here]

{{Main|Om 2008.9 Update}}

'''Neo FreeRunner images'''

There is no need to reflash if you have installed Om 2008.8 and used ''opkg update && opkg upgrade''.
Comment about naming scheme on the [http://lists.openmoko.org/pipermail/community/2008-September/031003.html community mailinglist]

=== The bleeding edge: Om "base / empty" images ===

The ''org.openmoko.dev'' branch does not have any applications preinstalled other than settings and installer, and it is unstable for now.

Images for ''testing'' are at:
http://downloads.openmoko.org/daily/

To get packages from ''testing'', use this ''/etc/opkg/testing.conf'' :
<pre>
src/gz testing-all http://downloads.openmoko.org/repository/testing/all
src/gz testing-arm http://downloads.openmoko.org/repository/testing/armv4t
src/gz testing-neo http://downloads.openmoko.org/repository/testing/neo1973
src/gz testing-gta02 http://downloads.openmoko.org/repository/testing/om-gta02
</pre>


''unstable'' comes from the same branch, compiled with the AUTOREV flag. There are no images, but packages are at http://downloads.openmoko.org/repository/unstable/

Reference: See [http://lists.openmoko.org/pipermail/community/2008-August/027997.html "Repository and Images" announcement] for details on other "Base image", "testing" and "unstable".

Once you have this base image, you can install the GTK+ telephony apps including gsmd, or Qtopia, or Mickey's framework. Check out the [[FDOM]] page for an idea of what to install.

=== Om 2007.2 images (GTK) ===

{{Main|Om 2007.2}}

Openmoko '''discontinued support''' for this release.
Two external developers still offer their own builds.

==== Celtune ====

Celtune offers different Images and a huge amount of packages (2007.2, pyneo, fso) for neo1973, freerunner and others. Celtune images can be found [http://rabenfrost.net/celtune/ here].

==== ScaredyCat ====

[http://blog.automated.it/category/openmoko/ Andy Powell] maintains images based on the 2007.2 software stack for the gta01 and gta02. A. Powell's ScaredyCat images can be found [http://buildhost.automated.it/OM2007.2/ here].

=== FSO images (freesmartphone.org) ===

{{Main|OpenmokoFramework}}

The file system will be in a jffs2 "summary" file. A file with the extension ".jffs2.summary" can be flashed to the FreeRunner just like an ordinary jffs2 file.

* [http://git.freesmartphone.org/ Browse the source]

* [[OpenmokoFramework/Status_Update_6|newest status update]]

* [http://downloads.freesmartphone.org/fso-stable/milestone5/ Downloads]

=== Android ===
Android now can run on Openmoko FreeRunner.
About the Image, you can check [[Android]] page , to get the detail information.
Android imagescan be found [http://people.openmoko.org/sean_mcneil/ here].

== Openmoko Community driven release targets ==

=== FDOM ===

{{Main|FDOM - a Fat and Dirty OM based distribution}}

Download images: http://compartida.net/openmoko/FDOM/

=== SHR images (Stable Hybrid Release) ===
{{Main|SHR}}

Download images:
* [http://build.shr-project.org/shr-testing/images/om-gta02/?C=M;O=D Neo Freerunner testing]
* [http://build.shr-project.org/shr-testing/images/neo1973/?C=M;O=D Neo 1973 testing]
* [http://build.shr-project.org/shr-unstable/images/om-gta02/?C=M;O=D Neo Freerunner unstable]
* [http://build.shr-project.org/shr-unstable/images/om-gta01/?C=M;O=D Neo 1973 unstable]

== Non-Openmoko distributions ==

=== Qt Extended (formerly Qtopia) images ===

:''Main article: [[Qtopia / Qt Extended on FreeRunner|Qt Extended]]''

Images are available on the [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6&orderby=dateD Qt Extended download page], make sure your browser sends referrer Header when downloading. (Note: direct linking to the files does not work.)

'''Neo FreeRunner'''

* Qt Extended flash image for FIC Neo Freerunner (gta02) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=98 here]. (The tarball contains rootfs and kernel)
* If you need to also download mwester's daily kernel (needed for previous version 4.4.1) you can find it [http://moko.mwester.net/dl.html#kernels here].

'''Neo 1973'''

* Qt Extended flash image for FIC Neo 1973 (gta01) version 4.4.2 can be downloaded [http://qtextended.org/modules/mydownloads/visit.php?lid=99 here]. (The tarball contains rootfs and kernel)

* A alternate Neo 1973 image can be downloaded [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz here]

'''More Qtopia downloads'''

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.

=== Debian images ===

{{Main|Debian}}

=== Hackable:1 images ===

{{Main|Hackable:1}}

== Other downloads ==

=== Applications repositories ===

If you are looking for a specific application instead of a full filesystem image:
* {{Main|Community Repository}}
* {{Main|Users Repositories}}

=== CAD files ===
You can download CAD files [http://downloads.openmoko.org/developer/CAD/ here].

=== Schematics ===

You can download the schematics of [[Neo 1973]] (GTA01) and [[Neo FreeRunner]] (GTA02) [http://downloads.openmoko.org/developer/schematics/ here]

=== Press material ===

Download Neo FreeRunner photos in various sizes for print and web use [http://openmoko.com/press-press-material.html here]

=== Tiddlywiki version of wiki.openmoko.org ===
If you want to carry this wiki along with you and to use it offline, then download
it [http://om-tiddlywiki.projects.openmoko.org/openmokowiki.html here] and store it locally, then browse through the pages which you think you need to have, click "save changes", so next time you open it all articles you have fetched previously will be available to you.

[[Category:Distributions]]

GPS applications

2008-10-19T03:35:01Z

Newkirk: /* Community Applications */ add tangogps source link

{{Applications}}

== Official software ==

{{:Om 2008.8 Locations}}
'''Source code released:http://code.google.com/p/om-assassin/'''

[[Howto_Test_Your_GPS_with_agpsui|Openmoko AGPS UI project]]

== Community Applications ==

{{ApplicationBox|
Name=Cumulus|
Description=GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website.|
Screenshot=No-screenshot.png|
Homepage=http://www.kflog.org/cumulus/|
TestedOn=|
PackageName=
}}
'''Source code released: http://www.kflog.org/fileadmin/user_upload/cumulus_downloads/1.3.1/cumulus-1.3.1.src.tar.bz2'''

{{:Pyroute}}
'''Source code released: http://svn.openstreetmap.org/applications/routing/pyroute/'''

{{ApplicationBox|
Name=Gosmore|
Description=Gosmore is a routing and viewer of OSM XML data such as the planet.osm.|
Screenshot=No-screenshot.png|
Homepage=http://wiki.openstreetmap.org/index.php/Gosmore|
TestedOn=|
PackageName=
}}
'''Source Code released:http://svn.openstreetmap.org/applications/rendering/gosmore/'''

{{ApplicationBox|
Name=mumpot|
Description=mumpot as an OSM viewing, routing application. Also OSM tag editing and some live editing is possible.|
Screenshot=mumpot-screenshot.png|
Homepage=http://wiki.openstreetmap.org/index.php/Mumpot|
TestedOn=|
PackageName=
}}
'''Source Code released:http://osm.andi.de1.cc/mumpot-0.3.1.tar.gz'''

{{:GPS Sight}}
'''Source Code released:http://projects.openmoko.org/projects/gpv/'''

{{:Navit}}
'''Source code released:http://navit.svn.sourceforge.net/viewvc/navit/branches/'''

{{:Orrery}}
'''Source Code released:http://projects.openmoko.org/projects/orrery/'''

[[qpegps]] 
qtopia (arm PDA) based map viewer with gps features

'''Source Code released:Can't find.'''

[[QMapControl]] 
Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
'''Source Code released:Can't find.'''

{{:TangoGPS}}
'''Source Code released:http://www.tangogps.org/downloads/tangogps-0.9.3.tar.gz.'''

[[gpsdrive]] 
GpsDrive is a car (bike, ship, plane) navigation system. GpsDrive displays your position provided from your GPS receiver on a zoomable map. The maps are autoselected for best resolution depending of your position and can be downloaded from the Internet. Speech output is supported if the "festival" software is running. All GPS receivers supported by gpsd should be usable. more at [http://www.gpsdrive.de/ homepage]

{{ApplicationBox|
Name=RoadMap|
Description=RoadMap displays a map of the streets, tracks the position provided the GPS receiver, identifies the street matching this GPS position and announces the name of the crossing street at the next intersection. A trip feature allows RoadMap to display routes, tracks, and provide some basic navigation information (distance to the next waypoint, direction, speed, etc..). Voice messages are generated that duplicate some of the screen information.|
Screenshot=Roadmap1.png|
Homepage=http://www.linux4.be/fr/roadmap.html|
TestedOn=Qtopia|
PackageName=
}}
Source Code released:Can't find.

[[Category:GPS Applications|GPS Applications]]
[[Category:GPS|GPS]]

GSM network registration

2008-10-17T02:13:49Z

Newkirk: /* Instructions */ - add qtopia/qtextended

We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:

== Instructions ==

1. What NEO device you are using? GTA01 or GTA02

2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA

3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.

4. What is your GSM firmware version? You can get this number by an AT command. Using [[USB_Networking|SSH]] to connect to your NEO, then type these commands:
root@fic-gta02:~# [[Gsmd|libgsmd-tool]] -m atcmd
AT+CGMR
STR=`AT+CGMR'
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'

5. What is your IMEI code? Check by using this AT command like previous steps.
AT+CGSN
STR=`AT+CGSN'
RSTR=`+CGSN: 000000000000000'

6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].

(#4 and #5 Under FSO/frameworkd - use "mdbus -s org.freesmartphone.ophoned /org/freesmartphone/GSM/Device GetInfo" to retrieve both IMEI and version string at once - mdbus is provided by the package 'mickeydbus' if not already installed)

In qtopia/qtextended, go into Applications->System Info->Modem. Look for 'Revision'.

== Results table ==

{| border="1"
| Owner || Location ||| Network Provider || How/When purchased SIM card || Device || GSM firmware || IMEI || Status || GSM log
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||T-Mobile|| with phone, > 2years ||GTA01||Moko6||YES||just fine||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| with phone, 8/28/07 ||GTA01||Moko6||YES||takes several minutes to register, home network rejects, CME error 32, reregisters continuously||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| replacement for one received with phone, 3/17/08 ||GTA01||Moko6||YES||preliminary test: registers promptly to home network. Will test in various locations and report back.||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| prepaid, no phone, 3/13/08 ||GTA01||Moko6||YES||just fine in some locations, but in others it takes several minutes to register and reregisters continuously. however, always better than card that came with phone||no
|-
| [[User:SpeedEvil]] || Fife, Scotland, UK||T-Mobile||PAYG with phone 7/2007||GTA01||Moko1||YES||Just fine||no
|-
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no
|-
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the re-registering loop starts once per minute|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]
|-
| [mailto:ahvenas@gmail.com Henrik Pihl] || Kuressaare, Estonia || Elisa || || GTA01Bv4 || Moko4 || YES || Normal, can register to the network immediately, but starts reconnecting to the network in the first minutes.|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=555&action=view log]
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || Era (Heyah) || prepaid, bought in October 2007, never charged, expired || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Card expired, home network rejects it with CME Error 32 (emergency calls only), system displays "Registering..." for several minutes. || NO
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || PlusGSM || prepaid, several years old, not charged || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Registered after entering PIN. Normal work after register. || NO
|-
| [mailto:plr@udgaard.com Peter Rasmussen] || Copenhagen Denmark || DK Sonofon || Pre-paid BiBoB service since Oct. 2007 || GTA01Bv4 || Moko1 || YES || Registered immediatly after entering PIN. Works after that. No /tmp/gsm.log appears || NO
|-
| [[User:Kevin_Dean | Kevin Dean]] || Washington DC Metro Area, USA || T-Mobile || || GTA01Bv4 || Moko1 || YES || Normal, can register to the network immediately, no PIN needed|| [http://www.monochromementality.com/data/files/logs/openmoko/2008-03-17/gsm.log.edited Log (Replaced my wife's # with 9991231122)]
|-
| [[User:Dennis_Wollersheim | Dennis Wollersheim]] || Melbourne, Australia || Telstra || || GTA01Bv4 || Moko4 || Yes || Registers quickly, reregisters every 30 seconds or so|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=556&action=view gsm log]
|-
| [[User:thomasg | Thomas Gstädtner]] || Nuremberg, Germany || T-Mobile (Ericsson RBS2206, GSM900) || 2004 || GTA01Bv4 || Moko 1 || Yes || Registers nearby immediately, w/ PIN or w/o || NO
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA01Bv4 || Moko 1 || Yes || No problems || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA02 || Moko 6 || No || Does not register, pin entry works, net scan also. || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || e-plus || 200x || GTA02 (same as above) || Moko 6 || No || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Ipswich, UK || Virgin || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Lelystad, Netherlands || Virgin (Roaming on T-Mobile NL) || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Orange (Amena) || 082007 || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Vodafone || phone > 3 years || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[User:Joachim | Joachim Jaeger]] || Eschbach, Germany || O2 || Fonic prepaid card, 01/2008 || GTA01Bv4 || Moko 4 || YES || Registers immediately after entering PIN. Normal work after register. || NO
|-
| [[user:liuxf|liuxf]] || Beijing, China || CU-GSM || 2006 || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[user:ismo|ismo]] || Zurich, Switzerland || sunrise || 2007 || GTA01Bv4 || Moko1 || YES || No problems || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone || 200x || GTA02 || Moko 7 || Yes || No problems || No
|-
| [[User:homyx | homyx]] || Ingolstadt, Germany || o2 || 2005, 2007 || GTA01 || Moko 1 || yes || No Problems || No
|-
| [[User:BasilK | basilk]] || Moskow, Russia || MegaFon || 2008 || GTA01Bv4 || Moko 4 || YES || No Problems || No
|-
| [[User:ibb | Ib Bentzen]] || Copenhagen, Denmark || TDC Mobil (Telmore) || 4 yrs || GTA01Bv4 || Moko4 || YES || OK || No
|-
| [[User:Zrich | zrich]] || Cambridge, MA, USA || Cingular || > 3 Years || GTA02 || Moko7 || Yes || No Problems || No
|-
| [[User:Infoport | William Vidrine]] || Greensboro, NC, USA || AT&T || replaced SIM sold with service Jul-18-08; model 71234 O 4022 || GTA02 || Moko8 || Yes || doesn't try to register on boot; sometimes takes switching on/off to register; re-registers with Home network frequently || No
|-
| [[User:robolange | Robert Lange]] || Philadelphia, PA, USA || AT&T || obtained with AT&T prepaid phone in July 2008; model 71234 O 4022 || GTA02Bv5 || Moko8 || Yes || With probability about 0.1, will register immediately upon boot. Can register manually with `libgsmd-tool -m shell` using commands `O` then `r`. Antenna power-up (command `O`) fails often, but try repeatedly and it will succeed; afterwards, registration (command `r`) works. Phone re-registers with network frequently, which interrupts suspend if you have power management on. || File not found
|-
| KB || Denmark || TDC || From TDC business in 2007 (64K43) didn't work, got new card for free (64K23) and that worked! || GTA02Bv5 || Moko8 || ¿What? || Works with new card || File not found
|-
| clare johnstone||Perth, Australia ||Vodafone AU || Prepaid 10 days||GTA02bv5 ||Moko8||YES ||no service briefly 2 min intervals for 10 hours today||MDBUS listing
|-
| [[User:gercamjr | Gerardo Camorlinga]]||Amarillo, TX, USA ||ATT || Prepaid $15 Motorola phone, pay as you go plan ||GTA02 ||Moko8||YES ||works great, used the gui script from [http://wiki.openmoko.org/wiki/Manually_using_GPRS Manually using GPRS]||No
|-

== See also ==
* [[FreeRunner unable to work with 3G SIM cards]]

[[Category:Community]]
[[Category:GSM]]

GSM network registration

2008-10-13T20:52:29Z

Newkirk: /* Instructions */ - add FSO/Frameworkd method to retrieve IMEI & firmware version via dbus since libgsm-tools not applicable

We'd like to know the real network registration status by our NEO devices in the world. Please provide some information about your NEO status! The question list as below:

== Instructions ==

1. What NEO device you are using? GTA01 or GTA02

2. Where is your location and what is your network provider? eg. T-Mobile, San Francisco in USA

3. When you boot the NEO, how long it takes to register the network? eg. in normal case, it should be able to register to a network in 1~2 minutes immediately.

4. What is your GSM firmware version? You can get this number by an AT command. Using [[USB_Networking|SSH]] to connect to your NEO, then type these commands:
root@fic-gta02:~# [[Gsmd|libgsmd-tool]] -m atcmd
AT+CGMR
STR=`AT+CGMR'
RSTR=`+CGMR: "HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko6"'

5. What is your IMEI code? Check by using this AT command like previous steps.
AT+CGSN
STR=`AT+CGSN'
RSTR=`+CGSN: 000000000000000'

6. if NEO takes over 3 minutes to register to the network or it just re-register to the network again and again. Please attach your gsm log file ('/tmp/gsm.log') to our bugzilla, we already created a bug for [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 this issue].

(#4 and #5 Under FSO/frameworkd - use "mdbus -s org.freesmartphone.ophoned /org/freesmartphone/GSM/Device GetInfo" to retrieve both IMEI and version string at once - mdbus is provided by the package 'mickeydbus' if not already installed)

== Results table ==

{| border="1"
| Owner || Location ||| Network Provider || How/When purchased SIM card || Device || GSM firmware || IMEI || Status || GSM log
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||T-Mobile|| with phone, > 2years ||GTA01||Moko6||YES||just fine||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| with phone, 8/28/07 ||GTA01||Moko6||YES||takes several minutes to register, home network rejects, CME error 32, reregisters continuously||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| replacement for one received with phone, 3/17/08 ||GTA01||Moko6||YES||preliminary test: registers promptly to home network. Will test in various locations and report back.||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| prepaid, no phone, 3/13/08 ||GTA01||Moko6||YES||just fine in some locations, but in others it takes several minutes to register and reregisters continuously. however, always better than card that came with phone||no
|-
| [[User:SpeedEvil]] || Fife, Scotland, UK||T-Mobile||PAYG with phone 7/2007||GTA01||Moko1||YES||Just fine||no
|-
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no
|-
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the re-registering loop starts once per minute|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]
|-
| [mailto:ahvenas@gmail.com Henrik Pihl] || Kuressaare, Estonia || Elisa || || GTA01Bv4 || Moko4 || YES || Normal, can register to the network immediately, but starts reconnecting to the network in the first minutes.|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=555&action=view log]
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || Era (Heyah) || prepaid, bought in October 2007, never charged, expired || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Card expired, home network rejects it with CME Error 32 (emergency calls only), system displays "Registering..." for several minutes. || NO
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || PlusGSM || prepaid, several years old, not charged || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Registered after entering PIN. Normal work after register. || NO
|-
| [mailto:plr@udgaard.com Peter Rasmussen] || Copenhagen Denmark || DK Sonofon || Pre-paid BiBoB service since Oct. 2007 || GTA01Bv4 || Moko1 || YES || Registered immediatly after entering PIN. Works after that. No /tmp/gsm.log appears || NO
|-
| [[User:Kevin_Dean | Kevin Dean]] || Washington DC Metro Area, USA || T-Mobile || || GTA01Bv4 || Moko1 || YES || Normal, can register to the network immediately, no PIN needed|| [http://www.monochromementality.com/data/files/logs/openmoko/2008-03-17/gsm.log.edited Log (Replaced my wife's # with 9991231122)]
|-
| [[User:Dennis_Wollersheim | Dennis Wollersheim]] || Melbourne, Australia || Telstra || || GTA01Bv4 || Moko4 || Yes || Registers quickly, reregisters every 30 seconds or so|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=556&action=view gsm log]
|-
| [[User:thomasg | Thomas Gstädtner]] || Nuremberg, Germany || T-Mobile (Ericsson RBS2206, GSM900) || 2004 || GTA01Bv4 || Moko 1 || Yes || Registers nearby immediately, w/ PIN or w/o || NO
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA01Bv4 || Moko 1 || Yes || No problems || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA02 || Moko 6 || No || Does not register, pin entry works, net scan also. || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || e-plus || 200x || GTA02 (same as above) || Moko 6 || No || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Ipswich, UK || Virgin || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Lelystad, Netherlands || Virgin (Roaming on T-Mobile NL) || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Orange (Amena) || 082007 || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Vodafone || phone > 3 years || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[User:Joachim | Joachim Jaeger]] || Eschbach, Germany || O2 || Fonic prepaid card, 01/2008 || GTA01Bv4 || Moko 4 || YES || Registers immediately after entering PIN. Normal work after register. || NO
|-
| [[user:liuxf|liuxf]] || Beijing, China || CU-GSM || 2006 || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[user:ismo|ismo]] || Zurich, Switzerland || sunrise || 2007 || GTA01Bv4 || Moko1 || YES || No problems || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone || 200x || GTA02 || Moko 7 || Yes || No problems || No
|-
| [[User:homyx | homyx]] || Ingolstadt, Germany || o2 || 2005, 2007 || GTA01 || Moko 1 || yes || No Problems || No
|-
| [[User:BasilK | basilk]] || Moskow, Russia || MegaFon || 2008 || GTA01Bv4 || Moko 4 || YES || No Problems || No
|-
| [[User:ibb | Ib Bentzen]] || Copenhagen, Denmark || TDC Mobil (Telmore) || 4 yrs || GTA01Bv4 || Moko4 || YES || OK || No
|-
| [[User:Zrich | zrich]] || Cambridge, MA, USA || Cingular || > 3 Years || GTA02 || Moko7 || Yes || No Problems || No
|-
| [[User:Infoport | William Vidrine]] || Greensboro, NC, USA || AT&T || replaced SIM sold with service Jul-18-08; model 71234 O 4022 || GTA02 || Moko8 || Yes || doesn't try to register on boot; sometimes takes switching on/off to register; re-registers with Home network frequently || No
|-
| [[User:robolange | Robert Lange]] || Philadelphia, PA, USA || AT&T || obtained with AT&T prepaid phone in July 2008; model 71234 O 4022 || GTA02Bv5 || Moko8 || Yes || With probability about 0.1, will register immediately upon boot. Can register manually with `libgsmd-tool -m shell` using commands `O` then `r`. Antenna power-up (command `O`) fails often, but try repeatedly and it will succeed; afterwards, registration (command `r`) works. Phone re-registers with network frequently, which interrupts suspend if you have power management on. || File not found
|-
| KB || Denmark || TDC || From TDC business in 2007 (64K43) didn't work, got new card for free (64K23) and that worked! || GTA02Bv5 || Moko8 || ¿What? || Works with new card || File not found
|-
| clare johnstone||Perth, Australia ||Vodafone AU || Prepaid 10 days||GTA02bv5 ||Moko8||YES ||no service briefly 2 min intervals for 10 hours today||MDBUS listing
|-
| [[User:gercamjr | Gerardo Camorlinga]]||Amarillo, TX, USA ||ATT || Prepaid $15 Motorola phone, pay as you go plan ||GTA02 ||Moko8||YES ||works great, used the gui script from [http://wiki.openmoko.org/wiki/Manually_using_GPRS Manually using GPRS]||No
|-

== See also ==
* [[FreeRunner unable to work with 3G SIM cards]]

[[Category:Community]]
[[Category:GSM]]

Manually using GPRS

2008-10-01T13:54:35Z

Newkirk: /* Option 1: With GSM multiplexing and with a GUI */ add new mokoscripts package link

The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator. Once a GPRS connection is made, it is possible to [[#Sharing_the_GPRS_connection_with_a_computer|share that connection with a connected computer]], allowing that computer to access the internet through the phone!

= Option 1: With GSM multiplexing and with a GUI =

{{note|The following does not appear to work if you have a SIM PIN. The dialog to enter your SIM PIN never pops up and the GSM multiplexing daemon continuous loops and runs into a SIM PIN error.}}

GSM multiplexing allows both a GPRS connection and a phone call to be handled at the same time. By default, [[Om 2008.8]] does not multiplex the GSM device. The [[FSO]] distribution, however, introduces GSM multiplexing with a new service and a DBus API to that service. The instructions to modify the OM2008.8 distribution to make use of GSM multiplexing and allow you to start GPRS from a GUI can be found here: http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295 ('''Note:''' Script package seems to be no longer be available, but a later post in the thread links to a version at [http://fyp-archiv.relei.de/ http://fyp-archiv.relei.de/].)

== gsm0710muxd from Angstrom Repositories ==

However, using those instructions, you will encounter a few hurdles. Do not use the gsm0710muxd that is found in the OM2008.8 repository. It will not work, instead, use the one from the Angstrom Repositories (see [[Repositories]]).

Alternatively, if you simply want to download all the packages, you can get them from here:

http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/gsm0710muxd_0.9.1+r0-gitr3ff86b129640b647ccba3d86eb243d864671b039-r0_armv4t.ipk

and the dependencies from here:

http://www.angstrom-distribution.org/repo/?action=details&pnm=gsm0710muxd

Make sure that you install the armv4t versions of all packages.

The [[#Some APN names for reference|APN Reference]] table may come in handy when you are looking for the required network specific information.

Once you follow through with all the instructions, you will notice that the "Services" GUI will crash. This has to do with this bug: http://docs.openmoko.org/trac/ticket/1718

The fix is to change the "init()" call on line 82 of /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_init_.py to "_init()" (add an underscore).

You may also have to modify your /etc/resolv.conf file and add the nameserver (DNS Server) of your service provider if you have DNS resolution problems.

Then, hopefully, you should be up in running with GPRS and a GUI to turn it on and off.

= Option 2: With GSM multiplexing and without a GUI =

You will have to get gsm0710muxd the same way as detailed in Option 1.

'''1) In /etc/rc5.d start gsm0710muxd before gsmd:'''
* S34gsm0710muxd -> ../init.d/gsm0710muxd
* S35gsmd -> ../init.d/gsmd

'''2) Modify S35gsmd so it can start either with or without gsm0710muxd:'''
<pre>
...
case "$1" in
start)
if [ "$(pidof gsm0710muxd)" ] ; then
id=$(date +%s)
GSM_DEV=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2)
else
[ -n "$GSM_POW" ] && ( echo "0" >$GSM_POW; sleep 1 )
[ -n "$GSM_POW" ] && ( echo "1" >$GSM_POW; sleep 1 )
[ -n "$GSM_RES" ] && ( echo "1" >$GSM_RES; sleep 1 )
[ -n "$GSM_RES" ] && ( echo "0" >$GSM_RES; sleep 2 )
fi

if [ ! "$GSM_DEV" ] ; then
echo "GSM_DEV was not set"
exit 1
fi

echo -n "Starting GSM daemon: "
start-stop-daemon -S -x /usr/sbin/gsmd -- gsmd -p $GSM_DEV $GSMD_OPTS -d -l /var/log/gsmd

if [ $? = 0 ]; then
echo "gsmd."
else
echo "(failed.)"
fi
;;
stop)
if [ ! "$(pidof gsm0710muxd)" ] ; then
[ -n "$GSM_POW" ] && echo "0" >$GSM_POW
fi

echo -n "Stopping GSM daemon: "
...
</pre>

'''3) Remove the tty from /etc/ppp/peers/simyo''' (replace simyo with your provider).

'''4) Use a ppp start script like this:'''
<pre>
$ cat /usr/local/bin/ppp-start
#!/bin/sh

id=$(date +%s)
TTY=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id | grep string | cut -d \" -f 2)
logger -t ppp-start "using tty $TTY"
pppd $TTY call simyo
</pre>

'''5) Use "killall pppd" to terminate the PPP connection.'''

[[:Image:Gsmmuxd.trace.txt|Here]] is some strace information from gsm0710muxd, showing how the daemon responds when receiving a call when GPRS is up.

= Option 3: Without GSM multiplexing and without a GUI =

[Important Note: It has been pointed out that this is only for 2007.2 and not for the 2008.8 images. If someone can confirm this and update this comment with more detail it would help out this page. Thanks]

The program that implements PPP on Linux is [[pppd]], which we need to configure and run to get a connection. When that is working, we can configure pppd to wait until it's needed before it connects, and to disconnect if the connection becomes idle. Further, we can start pppd in the background during the boot process.

== Configuring pppd for manual connections ==

You'll need /etc/ppp/peers/gprs:
<pre>
# Uncomment the following if you want some debug.
#debug
#logfile /var/volatile/log/pppd.log
lock
/dev/ttySAC0 115200
crtscts
connect /etc/ppp/gprs-connect-chat
disconnect /etc/ppp/gprs-disconnect-chat
hide-password
usepeerdns
ipcp-accept-local
noauth
noipdefault
novj
novjccomp
defaultroute
replacedefaultroute
# Reopen the connection if it fails, pausing for a while.
persist
holdoff 15
# Check the line every 20 seconds and presume
# the peer is gone if no replay for 4 times.
lcp-echo-interval 20
lcp-echo-failure 4
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. In /etc/ppp/pap-secrets you can add the following default line for "password-less" connections:

<pre>
# client server secret IP addresses
* * "" *
</pre>

For CHAP, lines in /etc/ppp/chap-secrets are used. For PAP, the lines are in /etc/ppp/pap-secrets. The client should match the "user" option in pppd the config file (below). You can use * to mean any here, but the option user "" doesn't mean empty!

For example:

<pre>
# Secrets for authentication using CHAP
# client server secret IP addresses
"user" * "password" *
</pre>

For this you need the following options in /etc/ppp/peers/gprs:

<pre>
# username to use for authentication, should match "client" in /etc/ppp/{chap,pap}-secrets
user "user"
</pre>

== gprs-connect-chat, version 1 ==

You'll also need /etc/ppp/gprs-connect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
exec chat -v -S -s\
TIMEOUT 15\
"" "\K\K\K\d+++ATH"\
OK-AT-OK ATZ\
OK ATE1\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 60\
OK AT+CFUN=1\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT /n/d
</pre>

Note: In the 3rd last line, replace the word internet by your provider's APN (listed below).

(08/18/08) Note: I needed to add the command "AT+CMOD=2" (formatted as "OK AT+CMOD=2\" without the quotes) in order to get GPRS working with the above script (otherwise it would ERROR on the CFUN, COPS, or the ATD if the other two were removed). I have T-Mobile (US) with the $5.99 "tzones" addon, which works with Minimo as it supports HTTP proxy setups.

== gprs-connect-chat, version 2 ==

Update: On my freerunner the first AT+CFUN=1 always generated ERROR. I managed to get gprs work by using the following script from http://lists.openmoko.org/pipermail/community/2008-July/023246.html:

<pre>
#!/bin/sh -e
exec /usr/sbin/chat -v \
TIMEOUT 10 \
OK-AT-'' ''\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 30 \
'' ATZ\
OK ATE1\
OK AT+CFUN=1\
ERROR AT+CPIN=\"XXXX\"\ << USE YOUR OWN
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK 'ATDT*99***1#'\
CONNECT ''
</pre>

The error seems to vary a bit, sometimes it's before AT+COPS, sometimes as above. I have two versions of the gprs-connect-chat, which I vary between depending on which is needed. Or is there a way to specify two acceptable answers like {OK,ERROR}?

You will need to adjust the APN name "internet" in at+cgdcont line and possibly the phone number in the ATD line to match what your network operator provides. See below in the table "Some APN names for reference" for the right settings for your operator.

== gprs-disconnect-chat ==

Also good to have is /etc/ppp/gprs-disconnect-chat (needs "chmod +x"):

<pre>
#!/bin/sh -e
/usr/sbin/chat -v\
ABORT OK\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO CARRIER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 12\
"" "\K\K\K\d+++ATH"\
"NO CARRIER-AT-OK" "\c"
</pre>

== Starting PPP connection ==

The following script can be used to start the ppp connection. First it stops gsmd because gsmd may put the phone in a unknown state. It then turns on the power to the phone, modifies the ownership, and then creates a tty connection. Finally it starts [[pppd]] with the gprs settings.

<pre>
/etc/init.d/gsmd stop
echo "1" > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
chown uucp.uucp /dev/ttySAC0
stty -F /dev/ttySAC0 crtscts
pppd call gprs
</pre>

If you are having problems connecting ensure you have a good GSM signal and replace the last line with the below line. This will allow you to see the details of the connection on the console.

<pre>
pppd debug nodetach call gprs
</pre>

The config above will establish a persistant link over gprs. The battery will run low in less than an hour. See an example for an on-demand config below.

=== Resolve.conf issues ===

The latest build seems to have solved the following issue, it should be automatically updated by pppd.

If you expeience DNS issues after connecting to DNS you may need a proper /etc/resolv.conf:

<pre>
ln -sf /var/run/resolv.conf /etc
</pre>

If needed put your nameserver for usb-net into /var/run/resolv.conf, not in /etc.

The image does not set a correct resolv.conf. i do so with an

<pre>
echo nameserver 192.168.0.201 > /var/run/resolv.conf
</pre>

in the right place. because a post-up in /etc/network/interfaces is not supported i do that in /etc/network/if-up.d/08setupdns

another problem is pppd's /etc/ppp/ip-down.d/92removedns which does not properly remove the link when shuting down ppp. my fix is this script:

<pre>
#!/bin/sh
ACTUALCONF=/var/run/resolv.conf
PPPCONF=/var/run/ppp/resolv.conf
if [ -f $PPPCONF ] ; then
if [ -f $ACTUALCONF ] ; then
if [ ! -h $ACTUALCONF -o ! "`readlink $ACTUALCONF 2>&1`" = "$PPPCONF" ] ; then
mv $ACTUALCONF $ACTUALCONF.ppporig
fi
fi

ln -sf $PPPCONF $ACTUALCONF
fi
</pre>

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN/Phone
! user/password if required
! Working pppd scripts
|-
| Australia || Virgin || Any || VirginInternet || ||
|-
| Australia || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || use pap authetication
proxy address 205.151.011.011:8080

mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
org.freesmartphone.GSM.PDP.ActivateContext internet.fido.ca fido
fido
|-
| Canada || Rogers || Any, behind NAT || internet.com || wapuser1/wap || nameserver 207.181.101.4
|-
| Canada || Rogers || $7 unlimited browsing || goam.com || wapuser1/wap || Must use a proxy server 10.128.1.69:80 (or 172.25.0.107:80 or 208.200.67.150:8080)
|-
| Czech Republic || Vodafone || any postpaid || internet || must be empty || [[GPRS_FSO|Works with FSO]] Behind NAT.
|-
| Czech Republic || Vodafone || prepaid || ointernet || must be empty || [[GPRS_FSO|Works with FSO]] Behind NAT.
|-
| Denmark || Telmore || || wap || must be empty ||
|-
| Denmark || Unotel || || internet || must be empty || Note: APN not tested
|-
| Estonia || Elisa || Any, behind NAT || internet || ||
|-
| Estonia || EMT || Any, behind NAT || internet.emt.ee || ||
|-
| Finland || Saunalahti || Any || internet.saunalahti || ||
|-
| Finland || Sonera || Any, behind NAT || internet || ||
|-
| Finland || Sonera || Any, public IP || prointernet || ||
|-
| France || SFR || 10.x.x.x? || websfr || || under tests
|-
| France || SFR || 10.x.x.x? || wapsfr[1]|| || under tests
|-
| France || Orange || ??? || orange.fr || || under tests
|-
| France || Bouyges Telecom || Web & Mail || mmsbouygtel.com || || Work great under FSO. Just follow instructions at http://wiki.openmoko.org/wiki/GPRS_FSO. Proxy: 62.201.129.225:8080. For emails, only ports 25 (smtp) and 110 (pop) are allowed. (They use a transparent proxy ...)
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs || [[Base pppd scripts]]
|-
| Germany || E-Plus || Simyo || internet.eplus.de || simyo simyo || [[simyo pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| Hungary || T-Mobile || Any || internet / *99***1# || must be empty || must disable chap auth: refuse-chap, refuse-mschap, refuse-mschap-v2
|-
| India || AirTel || MobileOffice || airtelgprs.com || ||
|-
| Italy || Wind || Superinternet, public IP || internet.wind / *99# || wind/wind (any string) || [[Wind pppd scripts]]
|-
| Netherlands || Vodafone || Any || live.vodafone.com / *99***1#|| || [[Vodafone pppd scripts]]
|-
| New Zealand || Vodafone || Any || live.vodafone.com / *99***2#|| ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Norway || OneCall || Any || internet || ||
|-
| Norway || Telenor || Any || telenor || ||
|-
| Spain || Simyo || Any || gprs-service.com / *99# || ||
|-
| Sweden || Parlino || || internet.parlino.se || || [[GPRS_FSO|Works with FSO]]
|-
| Sweden || Telia || || online.telia.se || || [[GPRS_FSO|Works with FSO]]
|-
| Switzerland || Swisscom || e.g. Natel Basic Liberty, behind NAT || gprs.swisscom.ch || ||
|-
| UK || T-Mobile|| || general.t-mobile.uk || ||
|-
| UK || Virgin || || goto.virginmobile.uk || user ||
|-
| UK || [http://www.filesaveas.com/gprs.html other providers] || || || ||
|-
| USA || AT&T || Unlimited data plan (attached to pay-as-you-go voice plan) || wap.cingular / *99***1# || WAP@CINGULARGPRS.COM/CINGULAR1 ||
|-
| USA || Cincinnati Bell Wireless || || wap.gocbw.com || cbw ||
|-
| USA || Cingular (AT&T) || Less than full internet || wap.cingular / may require *99***1# || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || || Need to set proxy to 216.155.165.50 T-Mobile docs say "216.155.165.050". 050 octal = 40 decimal and will *not* work. I think port is 8080 or 9100. No luck w/ pppd scripts. GPRS_FSO directions work under FSO though.
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
| Venezuela || Digitel || Pre- y post-pago || gprsweb.digitel.ve || ||
|-
|}

[1] connected through a WAP proxy (slower, but the only way to access Vodafone live! and SFR portal)

[2] Unless stated otherwise the phone number to call is "*99#"

Also see Ross Barkman's page for a detailed list of more [http://www.taniwha.org.uk/gprs.html global GPRS providers APN details]

== Starting pppd automatically ==

Once you have finished debugging your gprs-connect-chat and gprs options files, you may wish to automatically connect whenever needed and hang up when finished. Make sure you understand the impact of this change to your carrier plan billing. This is not recommended unless you have a large-use or unlimited data plan. These scripts do NOT prompt you before connecting.

=== On-demand connection settings ===

Additional settings are needed if you want the actual connection to be up only while there is traffic. In the 'gprs' file above, insert the following, making sure 'nodetach' is commented out. If 'nodetach' is on, the boot process will stop when it starts pppd. Also remove the option 'persist' mentioned above.

<pre>

# Wait until needed before connecting
demand

# Disconnect if idle for given amount of seconds
idle 20

</pre>

=== Start on boot (method 1) ===

Add the following definition to /etc/network/interfaces:
<pre>
auto ppp0
iface ppp0 inet ppp
provider gprs
</pre>

That should be it. Now you can use 'ifup ppp0' and 'ifdown ppp0' manually too.

=== Start on boot (method 2) ===

Create the following file as /etc/ppp/ppp_on_boot (needs chmod +x). The /etc/init.d/ppp script will call it to set up the daemon.
<pre>
#!/bin/sh
#
# Rename this file to ppp_on_boot and pppd will be fired up as
# soon as the system comes up, connecting to `provider'.
#
# If you also make this file executable, and replace the first line
# with just "#!/bin/sh", the commands below will be executed instead.
#

# The location of the ppp daemon itself (shouldn't need to be changed)
PPPD=/usr/sbin/pppd

# The default provider to connect to
$PPPD call gprs

# Additional connections, which would just use settings from
# /etc/ppp/options.<tty>
#$PPPD ttyS0
#$PPPD ttyS1
#$PPPD ttyS2
#$PPPD ttyS3
</pre>

Finally, you need to add the /etc/init.d/ppp script to the init process by creating symbolic links from the appropriate directories. I chose the following:

<pre>
/etc/rc0.d/K25ppp
/etc/rc1.d/K45ppp
/etc/rc2.d/S45ppp
/etc/rc3.d/S45ppp
/etc/rc4.d/S45ppp
/etc/rc5.d/S45ppp
/etc/rc6.d/K25ppp
</pre>

= Sharing the GPRS connection with a computer =

See [[Tethering]]

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]
* [[GPRS FSO]]
{{Languages|Manually_using_GPRS}}

[[Category:Application Developer]]
[[Category:Networking]]
[[Category:GSM]]

Using the Neo as an USB Mass storage device

2008-09-26T05:35:25Z

Newkirk: Restructured from Q&A format to sections

==Make the Neo FreeRunner act as a mass storage device==

To access the microSD card in the Freerunner from the host computer as if it were a USB key or memory stick, the following script can be used:

#!/bin/sh
ifdown usb0
umount /media/card
rmmod g_ether
modprobe g_file_storage file=/dev/mmcblk0p1
Reference: [http://lists.openmoko.org/pipermail/community/2008-September/029261.html Petr Vanek's "usb mass media storage" message on the community mailing list]

The card is not accessible from the Freerunner in this mode.

==Make the Neo FreeRunner revert to USB networking==

The following script can be used:

#!/bin/sh
rmmod g_file_storage
mount /dev/mmcblk0p1 /media/card
modprobe g_ether
ifup usb0
Be sure to properly unmount on the host computer first, just as you would with any other USB storage.

==Is it possible to pretend to be a USB hub, providing both g_ether and g_file_storage?==

Not yet. At the moment it's one gadget driver at a time, but there is a project under way to allow use of multiple gadget drivers together. See [http://blog.felipebalbi.com/?p=44 this blog posting called 'USB Composite Gadget Framework'] or [http://www.linux-usb.org/gadget/ Linux-USB Gadget API Framework]

[[Category:USB]]

Using the Neo as an USB Mass storage device

2008-09-26T05:22:41Z

Newkirk: Added umount and mount commands to protect from conflicts

Q: How to make the Neo FreeRunner act as a mass storage device (memory stick, USB key, portable drive...)

A: The following script can be used

#!/bin/sh
ifdown usb0
umount /media/card
rmmod g_ether
modprobe g_file_storage file=/dev/mmcblk0p1
Reference: [http://lists.openmoko.org/pipermail/community/2008-September/029261.html Petr Vanek's "usb mass media storage" message on the community mailing list]

Q: How to make the Neo FreeRunner revert to USB networking?

A: The following script can be used (Keep in mind that you need to properly unmount on the host computer FIRST or risk corruption)

#!/bin/sh
rmmod g_file_storage
mount /dev/mmcblk0p1 /media/card
modprobe g_ether
ifup usb0

Q: Is it possible to pretend to be a USB hub, providing both g_ether and g_file_storage ?

A: Not yet. At the moment it's one gadget driver at a time, but there is a project under way to allow use of multiple gadget drivers together. See [http://blog.felipebalbi.com/?p=44 this blog posting called 'USB Composite Gadget Framework'] or [http://www.linux-usb.org/gadget/ Linux-USB Gadget API Framework]

[[Category:USB]]

Using the Neo as an USB Mass storage device

2008-09-26T05:12:33Z

Newkirk:

Q: How to make the Neo FreeRunner act as a mass storage device (memory stick, USB key, portable drive...)

A: The following script can be used

#!/bin/sh
ifdown usb0
rmmod g_ether
modprobe g_file_storage file=/dev/mmcblk0p1
Reference: [http://lists.openmoko.org/pipermail/community/2008-September/029261.html Petr Vanek's "usb mass media storage" message on the community mailing list]

Q: How to make the Neo FreeRunner revert to USB networking?

A: The following script can be used (Keep in mind that you need to properly unmount on the host computer FIRST or risk corruption)

#!/bin/sh
rmmod g_file_storage
modprobe g_ether
ifup usb0

Q: Is it possible to pretend to be a USB hub, providing both g_ether and g_file_storage ?

A: Not yet. At the moment it's one gadget driver at a time, but there is a project under way to allow use of multiple gadget drivers together. See [http://blog.felipebalbi.com/?p=44 this blog posting called 'USB Composite Gadget Framework'] or [http://www.linux-usb.org/gadget/ Linux-USB Gadget API Framework]

[[Category:USB]]

Using the Neo as an USB Mass storage device

2008-09-26T05:11:33Z

Newkirk: added 'revert to networking'

Q: How to make the Neo FreeRunner act as a mass storage device (memory stick, USB key, portable drive...)

A: The following script can be used

#!/bin/sh
ifdown usb0
rmmod g_ether
modprobe g_file_storage file=/dev/mmcblk0p1

Q: How to make the Neo FreeRunner revert to USB networking?

A: The following script can be used (Keep in mind that you need to properly unmount on the host computer FIRST or risk corruption)

#!/bin/sh
rmmod g_file_storage
modprobe g_ether
ifup usb0

Reference: [http://lists.openmoko.org/pipermail/community/2008-September/029261.html Petr Vanek's "usb mass media storage" message on the community mailing list]

Q: Is it possible to pretend to be a USB hub, providing both g_ether and g_file_storage ?

A: Not yet. At the moment it's one gadget driver at a time, but there is a project under way to allow use of multiple gadget drivers together. See [http://blog.felipebalbi.com/?p=44 this blog posting called 'USB Composite Gadget Framework'] or [http://www.linux-usb.org/gadget/ Linux-USB Gadget API Framework]

[[Category:USB]]

File transfer

2008-09-26T04:59:18Z

Newkirk: Clarified SFTP with user:password URI and corrected 'USB mass storage unsupported' with link to wiki page offering info.

The Openmoko hardware and software offer several ways to transfer files to and from the system.

== SCP ==
client (find host pc ip-adress: scp <hostLoginName>@<hostIP>:/file .)

server (on host pc: 'scp <file> root@192.168.0.202:/tmp/')

== TFTP ==
client ('tftp')

server?

== NFS ==
client (on Neo: 'mount -t nfs ...' or edit /etc/fstab and '/etc/init.d/mountnfs.sh start')

server?

== HTTP ==
client (on Neo: 'wget',web browser)

== MicroSD ==
It is possible to write data to micro SD on a desktop machine with the suitable writer and then have it accessible from inside the Openmoko after the card is inserted into that device. To get this working, the micro SD must be formatted in some filesystem that both Openmoko and host understand (ext2, for instance).

The problem with this approach is that micro SD is difficult to access in the Neo. Both battery and even SIM card must be removed to reach it.

== SFTP ==
SFTP can be an excellent way to transfer files as it is supported by many possible clients on the desktop machine. After USB network is set up, it is possible to try to open sftp connection by entering sftp://192.168.0.202 or sftp://{username}:{password}@192.168.0.202 into the address bar of the browser that supports sftp.

You can also use the sftp console client under Linux or something like psftp.exe, the sftp client that goes with PuTTY for Windows.

== FTP ==
FTP is currently considered insecure. There is no any reason to use FTP, SFTP should be used instead.

== USB Mass Storage ==
The Freerunner can be configured to appear as a USB mass storage device to the desktop. see [[Using the Neo as a Mass storage device]].

== Common methods not supported ==
*Bluetooth (except via other network methods)

[[Category:Advanced End User]]

File transfer

2008-09-26T04:48:31Z

Newkirk: /* SFTP */

The Openmoko hardware and software offer several ways to transfer files to and from the system.

== SCP ==
client (find host pc ip-adress: scp <hostLoginName>@<hostIP>:/file .)

server (on host pc: 'scp <file> root@192.168.0.202:/tmp/')

== TFTP ==
client ('tftp')

server?

== NFS ==
client (on Neo: 'mount -t nfs ...' or edit /etc/fstab and '/etc/init.d/mountnfs.sh start')

server?

== HTTP ==
client (on Neo: 'wget',web browser)

== MicroSD ==
It is possible to write data to micro SD on a desktop machine with the suitable writer and then have it accessible from inside the Openmoko after the card is inserted into that device. To get this working, the micro SD must be formatted in some filesystem that both Openmoko and host understand (ext2, for instance).

The problem with this approach is that micro SD is difficult to access in the Neo. Both battery and even SIM card must be removed to reach it.

== SFTP ==
SFTP can be an excellent way to transfer files as it is supported by many possible clients on the desktop machine. After USB network is set up, it is possible to try to open sftp connection by entering sftp://192.168.0.202 or sftp://{username}:{password}@192.168.0.202 into the address bar of the browser that supports sftp.

You can also use the sftp console client under Linux or something like psftp.exe, the sftp client that goes with PuTTY for Windows.

== FTP ==
FTP is currently considered insecure. There is no any reason to use FTP, SFTP should be used instead.

== Common methods not supported ==
*Bluetooth (except via other network methods)
*USB (appearing as a mass storage device on the other device).

[[Category:Advanced End User]]

Wiki statistic numbers

2008-09-02T22:43:39Z

Newkirk: /* August, 2008 */

Openmoko uses Google Analytics to get visitor's information. On this page, you can find every kind of wiki statistic numbers.
==August, 2008==
Period :1 August, 2008~31 August, 2008

*[[Media:Analytics wiki-1-.openmoko.org 200808 (ExitsReport).pdf|Exit Page]]
*[[Media:Analytics wiki-1-.openmoko.org 200808 (TopContentReport).pdf|Top 250 contents]]
*[[Media:Analytics wiki-1-.openmoko.org 200808 (KeywordsReport).pdf|Keyword Report]]
*[[Media:Analytics wiki-1-.openmoko.org 200808 (GeoMapReport).pdf|Mapoverlay]]
*[[Media:Analytics wiki-1-.openmoko.org 200808 (ExitsReport).pdf|Exit page report]]

==July, 2008==
Period :1 July, 2008~31 July, 2008
*[[Media:Top250content.pdf|Top 250 contents]]
*[[Media:Keyword.pdf|Search Keyword]]
*[[Media:Exitpage.pdf|Top leaving pages]]

[[Category:Community]]

Edje

2008-08-22T04:14:56Z

Newkirk: fix link to edge api docs (it's a PDF in the parent of the original link's target dir, which doesn't exist)

= Edje =
Is a configuration-file format which origins of [http://www.enlightenment.org/ Enlightenment 17]. It is used by Openmoko and Illume for configuring a lot of the look of OpenMoko and its applications.

Edje uses *.edj Files as binary-configuration files and *.edc as the source of such an *.edj file.

For compiling an *.edc file to an *.edj file you need: edje_cc
For decompiling an *.edj file to an *.edc file you need: edje_decc (you might want to do this to learn about how such a file has to look like)

= Installation =
You can install edje_cc and edje_decc for Ubuntu by adding this source to your /etc/apt/sources.lst:
deb http://e17.dunnewind.net/ubuntu hardy e17
or
deb http://e17.dunnewind.net/ubuntu gutsy e17
or
deb http://e17.dunnewind.net/ubuntu feisty e17
After that you can install the needed tools with:
sudo apt-get update && sudo apt-get install libedje-bin

= Links =
* [http://docs.enlightenment.org/api/edje/edje-reference.pdf docs.enlightenment.org] - offical edje documentation
* [http://52grad.de/.stuff/freerunner/ 52grad.de] - example on using edj files

USB Networking

2008-08-20T03:07:49Z

Newkirk: change 'allow-hotplug' to 'auto' in Ubuntu example code and explanation

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

If Desktop/Laptop has a DNS server or is proxying DNS:
nameserver 192.168.0.200
or just put in another DNS Server - for example:
nameserver 212.147.10.10

Some Linux and Windows systems have DNS servers, especially those configured as servers, but in general they do not. You can install packages such as ''bind9'' or ''dnsmasq'' to run your own DNS server. If you have a DNS server then Test Your Connection. Otherwise you may want to proxy DNS from your Desktop/Laptop.

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from http://www.tapor.com/udpf/ - use it with the command"

udpf-elf -p=53-f=`cat /etc/resolv.conf|awk '$1 == "nameserver"{print $2; exit(0);}'`:53

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

== Hostnames ==

If you become tired of remembering and typing in the ip address of the Neo (for scp, telnet, SSH, SMB, or whatever), you can give it an easy to remember hostname.

Open and enter the following line in your desktop's /etc/hosts:
192.168.0.202 openmoko
Now instead of typing the full ip address in commands like:
ssh root@192.168.0.202
You can replace the full ip with the hostname like:
ssh root@openmoko

It may also be helpful to some to edit the Neo's /etc/hosts to use "desktop" or "laptop" instead of 192.168.0.200

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= OS or Distro Specific & Automatic Configuration =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.
These instructions should keep you from having to run the Simple Manual Linux Configuration every time you plug in and want to connect to an Openmoko device. One run and then you're done!

If the Simple Manual Linux Configuration does not work for your OS or Distro (MacOS X, MS Windows, etc) there may be instructions here that work for you.

== MacOS X ==
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].

== Windows ==
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &

</pre>

This is more sophisticated than the manual setup. The 'auto usb' stanza ties into the Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

Another possible configuration that adds DNS forward and removes
the iptables changes after unplugging:

in /etc/network/interfaces add
<pre>
# freerunner
auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

LABEL="net_end"

ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

The bug is that the LABEL="net_end" is at the wrong position

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

# scp ~/.ssh/id_rsa.pub phone:.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

User:Newkirk

2008-08-16T19:59:31Z

Newkirk: New page: Joel Newkirk ('j') is a network administrator at an all-linux wireless ISP, and a web app developer. Homepage at [http://newkirk.us] and blog at [http://jthinks.com] j

Joel Newkirk ('j') is a network administrator at an all-linux wireless ISP, and a web app developer. Homepage at [http://newkirk.us] and blog at [http://jthinks.com]

j

Neo FreeRunner Hardware

2008-08-16T19:52:45Z

Newkirk: Added links to schematic and board layout PDFs

{{Languages|Neo FreeRunner GTA02 Hardware}}
{{gta02menu}}

This is the detailed list of the hardware components used in Neo FreeRunner (development codename GTA02), Openmoko Inc.'s second smartphone. Differences between various GTA02 revisions is also described.

If you are looking for general hardware overview please look at the [[Neo FreeRunner]] page.

Board layout [http://downloads.openmoko.org/schematics/GTA02/Component-placement_Freerunner-GTA02-MB-A6.pdf] and schematics [http://downloads.openmoko.org/schematics/GTA02/Schematics_Freerunner-GTA02_A5-A7cumulative_public_RC0.pdf] for GTA02 have been published, PDF format.

See also the [[Neo FreeRunner GTA02 Hardware Requirements]] used in making these component selections.

== Photos ==

<gallery>
Image:Gta02a5 pcba cs.JPG|component (back) side NOTE: GTA02 A5 PCBA Component Side photo
Image:Gta02a5 pcba ps.JPG|display (top) side NOTE: GTA02 A5 PCBA Print Side photo
Image:GTA02 A5 PCB CS.jpg|component (back) side NOTE: GTA02 A5 PCB Component Side photo
Image:GTA02 A5 PCB PS.jpg|display (top) side NOTE: GTA02 A5 PCB Print Side photo
Image:SimpleComponentDiagram.jpg|Simplified Hardware Component Diagram
</gallery>

=== PCB layout ===

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #ffffff; background:#ffffff; width:100%;"
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:33% " |
<div align=center>
[[Image:Gta02a5 pcba cs1.png]]
</div>
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:33% " |
<div align=left>
1. NOR Flash 
2. SDRAM 
3. GPS 
4. CPU/NAND Flash 
5. GPU 
6. PMU 
7. Audio Codec
</div>
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:34% " |

<div align="left">
8. Audio Amplifier 
9. USB Host Power 
10. Analog Baseband 
11. Digital Baseband 
12. GSM SRAM/Flash 
13. GSM RF TRanceiver 
14. RF AMP
</div>
|}

= GTA02 Hardware Component Selection =

== Physical Dimensions ==
* 120.7 x 62 x 18.5 mm (4.75 x 2.44 x 0.728 inch)
* 110 +/- 5 g (4 ounces) without battery 

== Main components ==
=== Processor ===
The main Processor (CPU) is a [[Samsung S3C2442B B54]] (running at 400 MHz)

GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt

{{:Samsung S3C2442B B54}}

=== Power Management ===
A NXP PCF50633 04 N3 is used for [[Neo1973_Power_Management|power management]].

* NXP PMU index: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page] 
* Product Datasheet: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf NXP PCF50633 Product Data Sheet] 
* Product User manual: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633UM_6.pdf NXP PCF50633 User Manual] 
**Special thanks NXP provide full user manual and support openness for all developer
**Datasheet/User manual usage [http://lists.openmoko.org/pipermail/community/2008-March/013898.html was legally authorized by NXP]
* Connected to: S3C2442 via I2C, client address is 0x08. 
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch 

=== Flash ===
==== NAND Flash ====
256MB integrated Samsung NAND flash inside the 2442 multi-chip package, attached to the S3C2442 NAND controller

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 S3C2442]
* Data Sheet: S3C2442 B54 comes with 256 MB NAND MCP package
* Connected to: S3C2442 NAND controller 

==== NOR Flash ====

16MBit ST M58WR016KB706E NOR flash for 'unbrickable emergency boot' feature.

* Product Homepage: [http://www.st.com/stonline/products/families/memories/fl_nor_mob/index.htm ST Mobile Flash NOR/Mobile Terminal]
* Data Sheet: [http://www.st.com/stonline/products/literature/ds/13023/m58wr032qb.pdf M58WR016]
* Connected to: S3C2442 NAND controller 

=== SDRAM ===
128MB SDRAM (64MB inside 2442 MCP, 1x Samsung K4M51323PC) attached to S3C2442 SDRAM controller
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M51323PC Samsung K4M51323PC]
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M51323PC/ds_k4m51323pc.pdf Samsung K4M51323PC]
* Connected to: S3C2442 

== GSM/GPRS ==
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.

* Connected to: S3C2442 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch
* [[External GSM Antenna|Accessible GSM/GPRS antenna jack]] (if battery cover is removed) - MURATA MM8430-2610RB3 SMD RF TEST PORT. FOr compatible adapter see Murata part no. MXHS83QE3000 

=== CALYPSO ASIC digital baseband ===
Unfortunately we cannot provide many details on the GSM chipset due to very tight [http://en.wikipedia.org/wiki/Non-disclosure_agreement NDA]s. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2442. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.

The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.
The legality of reading these files may vary according to your local laws, as may generating code from them.

*Calypso D751992AZHH 
*The firmware within GTA02 should be moko6 or later (internal code name)

=== TI TWL3025BZGMR analog baseband ===
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014] 

=== TI TRF6151 (GSM/PCS) RF Transceiver ===
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] 
GPRS Class12/CS4 

== AGPS ==
[[u-blox ANTARIS 4 ATR0635]] chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
{{:u-blox ANTARIS 4 ATR0635}}

== Accelerometers ==
Two ST LIS302DL
* Homepage: http://www.st.com/stonline/products/literature/ds/12726/lis302dl.htm
* Datasheet: http://www.st.com/stonline/products/literature/ds/12726.pdf
* Connected to: S3C2442 via SPI interface
* S3C2442 SPI EINT interrupt inputs 

== Graphics/3D Acceleration ==

Smedia Glamo 3362.
* Homepage: http://www.smediatech.com/product3362.htm
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC). There is hope that the glamo chip features may be usable even without a NDA, see [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ the hack here]
* Connected to: S3C2442 Address/Data bus 

=== microSD ===
The GTA02 has one microSD aka Transflash slot. Using the Glamo 3362 MMC/SD controller

*It should support SDHC, and 4GB card has been tested. Anyone with 8GB card? MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].
* Connected to: Glamo 3362 MMC/SD controller
* Driver: Check svn for the SMedia driver with SD implementation
* [[Supported microSD cards]]
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]
* SANDISK 128 MB/512 MB and some 4G SDHC card been verified could work on GTA02 

== LCD Module (LCM) ==
Toppoly (tpo) 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 TD028TTEC1 module, using a Toshiba JBT6K74 TFT
LCD Driver Chipset. 
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]
* Specification: http://www.cip.physik.uni-muenchen.de/~Wolfgang.Draxinger/stuff/openmoko/TD028TTEC1.pdf
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch
* Connected to: Glamo3362 LCM interface and Glamo3362 SPI Interface 

==== Touch Screen ====
* Connected to: S3C2442 TS controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_touchscreen.patch

== Bluetooth Module==
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4

* Data Sheet: [http://www.delta.com.tw/product/cp/vco/BT/download/pdf/CS/2.DFBM-CS320.pdf 2.DFBM-CS320.pdf]
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]
* Driver: Stock Linux Kernel BlueZ
* Connected to: S3C2442 USB Host controller (OHCI)
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch 

=== Bluetooth Audio ===
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec. 

== WiFi Module==

Accton (WLAN 802.11b/g SiP-M WM3236AQ(Flash Ver:2.0 Atheros AR6001GZ)
* Connected to: S3C2442 SDIO Host controller 
* Datasheet: [http://www.accton.com/products/Datasheet/WM3236A.AQ.pdf Accton 3236AQ datasheet] 
* Driver: http://svn.openmoko.org/developers/sameo/patches/ 

== Vibrator ==
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch
* Connected to: S3C2442 GPIO

== USB Host ==
The USB Host controller is inside the S3C2442
* Driver: Stock Linux kernel ohci_hcd
* USB version 1.1
* Supply USB 5v in Host mode using usb power switch AAT1275IRN-5.0-T1
** http://www.analogictech.com/products/digitalfiles/AAT1275.pdf
* A net EN_USBHOST is controlled by PMU GPIO "GPO", this one signal when asserted (high)
** enables generation of 5V for external device using a charge pump
** enables connection of 15K pulldowns to D+ and D- to allow device insertion and removal detection for host mode
** DISABLES the path for USB power to charge the battery

It should also be possible to use host mode with externally-provided power. This will allow the FreeRunner to be connected to a USB device and be powered and charging the battery if present at the same time.

* Connect 0V, d+, d-, +5 to your USB device
* Connect a 15k ohm resistor between d+ and ground
* Connect a 15k ohm resistor between d- and ground
* Connect 0V, +5 to your >1A power source
** If your power source was not the Openmoko 1A charger, additionally connect a 47K ohm 5% resistor between the ID pin and ground to pretend to be the 1A charger.

In addition you need to make sure EN_USBHOST signal that enables the physical Host mode power generation and disables the USB -> PMU charging path is deasserted. This may be taken care of automatically shortly by detection of the 48K resistor on a USB insertion leading to forcing EN_USBHOST deasserted. The charge pump that generates the 5V in host mode doesn't seem to mind getting external 5V given to it, but the real issue is that the battery will not be charged at all if we leave EN_USBHOST asserted since one of its jobs is to stop that happening.

== USB Device ==
The USB Device controller is inside the S3C2442
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use
* 1200mAh lithium battery charges when connected to powered host.
* Mini-AB connector similar to [http://www.cypressindustries.com/shoponline/proddetail.asp?prod=CCMUSBAB-32005-700&cat=34 this one].

== I2C Devices ==
I2C is a simple communication standard intended to move small amounts of data a few inches between chips.
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973. 

== Audio ==
See also: [[Neo1973 Audio Subsystem]]

=== Wolfson Codec ===
There's a [[WM8753]] Wolfson Microelectronics CODEC (This is not a 'smart' codec that can interpret MP3/... it is a simple dumb 'sound card'.)
* Product Homepage: http://www.wolfsonmicro.com/products/WM8753/
* Data Sheet: [http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf WM8753.pdf]
* Connected to: S3C2442 IIS interface (PCM data), S3C2442 I2C (Control)
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/asoc.patch

=== Mono Amplifier ===
There's a National Semiconductor [[LM4853]] Mono Amplifier at the analog audio output of the WM8753

* Product Homepage: [http://www.national.com/pf/LM/LM4853.html LM4853.html]
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4853.pdf LM4853.pdf]
* Connects to (LM4853 pin):
** S3C2442 GPIO: HP_IN, AMP_SHUT (shutdown);
** Wolfson WM8753: LOUTL (LEFTIN), LOUTR (RIGHTIN);
** speaker4102: (LEFTOUT/BLTOUT-, BLTOUT+);
** headset-jack: ring 2 (RIGHTOUT), ring 3 (LEFTOUT/BLTOUT-) via 1uF-33R each

=== Analog wired Headset ===
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.

The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration.

ring 
1(base): GND 
2: right out 
3: left out 
4(tip): mic + HOLD-button(press:short to GND)

=== Buttons ===
The Neo1973 GTA02 features two buttons:
* [[Neo1973 Power Button|The Power Button]]
* [[Neo1973 AUX Button|The "Aux" button]]

== Case ==
The case for the FreeRunner is all black, as seen on the front page of the wiki.

Openmoko has released the CAD files for the case schematics for the Openmoko [[Neo1973]] (GTA01) and Neo FreeRunner. These are available in the original Pro/E (.asm/.prt) format and alternative formats created from the originals.

We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.

* [http://downloads.openmoko.org/CAD/NeoFreerunner_ProE.zip The original Pro/E (.asm/.prt) format]

[http://downloads.openmoko.org/CAD/ Browse CAD directory]

=Accessory=

== Stylus ==

Using 4 in 1 laser pen
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]
*GTA02 standard setup comes with [http://www.quarton.com.tw/laser_pen_infiniter_xp_2.html QUARTON XPII 4 in 1 laser pen]

== Battery ==
The [[Neo FreeRunner (GTA02) Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility with a Nokia BL6C battery.
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.

* GTA02 using the smart battery based on TI bq27000 chipset
* SANYO UF653450S 1200mAh cell. 
* Battery schematics: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf GTA02 Smart Battery Schematics]

== microSD Card ==

GTA02 should come with one of following microSD card

* [http://www.transcendusa.com/ Transcend] 512MB microSD card
* [http://www.sandisk.com/ SanDisk] 512MB microSD card 

== Charger ==

AKII Technology Charger

*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]
*Input: 100-240v~ /0.3A
*Output: +5v up to 2.0A
*Add 47.5k 1% resistor between ID pin and ground for openmoko charger identification 

= Hardware revisions =

{{Main|GTA02 revisions}}

= Debug Board =

{{Main|Debug_Board_v3}}

= Distinguishing hardware revisions =
== Inside the [[Bootloader]] ==
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)

== Inside the [[Kernel]] ==
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.

== From Userspace ==
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.

= Certification =

== FCC ==
*For US Import
** 850/1800/1900 Band, FCC ID: EUNGTA02
** 900/1800/1900 Band, FCC ID: EUNGTA02E
** [http://people.openmoko.org/openmoko/certificate/gta/gta02/certificate/EUNGTA02_850_1800_1900/ FCC test report(GTA02)]
** [http://people.openmoko.org/openmoko/certificate/gta/gta02/certificate/EUNGTA02E_900_1800_1900/ FCC test report(GTA02E)]

== CE ==
*For Europe
**Registration number: M528583V-EO
**[http://people.openmoko.org/openmoko/certificate/gta/gta02/certificate/CE CE report and certificate]

== NCC ==
*For Taiwan Import
**NCC certification number: CCAF08DG0080T0
**[http://people.openmoko.org/openmoko/certificate/gta/gta02/certificate/NCC NCC report and certificate]

[[Category:GTA02 Hardware]]

Neo FreeRunner Battery

2008-08-12T06:02:01Z

Newkirk: /* Compatible Replacement Batteries */

{{Gta02menu}}
=== GTA02 1200 mAh Smart Battery ===

*Using SANYO 1200mAh cell
*Battery Technical information: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf Detailed Battery Information]

* 1200mAh Smart Battery with Coulomb-counter and protection circuit
* The Smart Battery keeps track of maximum and current capacity for precise prediction of remaining battery power and time until shutdown, based on actual power dissipation.

For more information, see the GTA01 battery info at [[Neo1973 Battery]]

=== Notes about expected battery life ===
Battery life is a work in progress. The power saving software is in a very rudimentary state. At the moment 12h is about the most (note though a [http://lists.openmoko.org/pipermail/community/2008-July/020339.html recent result of at least 21h], mostly in suspend, with multiple short wakeups, on the predecessor device GTA01). A week standby and 6 hours talk, 20 hours mp3 might be attainable when power saving software is complete.

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.
(If you have the newest kernel images, you should be safe due to a software fix.)
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.

=== Compatible Replacement Batteries ===

Other known FreeRunner-compatible batteries include the BL-series (BL-4X, BL-5X) from Nokia, and their third-party equivalents.
These may not work to revive a device and may not report charge information.
It is probably a good idea to check that your battery is not greater than the stock battery's voltage of 3.7V (the above suggests that 4.5VDC should be fine) unless you know what you are doing.

{| border="1" cellpadding="4" cellspacing="0"
!Battery Model
!Capacity (mAh)
!Charge info reported
!Notes
|-
|NOKIA BL-4
|
|no
|
|-
|NOKIA BL-4C
|750
|
|
|-
|NOKIA BL-5B
|
|
|
|-
|NOKIA BL-5C
|
|no
|
|-
|NOKIA BL-6C
|1200
|no
|
|}

[[Category:GTA02 Hardware]]

Neo FreeRunner Hardware

2008-07-29T01:08:23Z

Newkirk: correct photo captions

{{Languages|Neo FreeRunner GTA02 Hardware}}
__NOTOC__
__NOEDITSECTION__
{{gta02menu}}
[[Openmoko]] is a software distribution stack that sits on top of a [[hardware]] platform. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of Openmoko. You can find specifications of the hardware by reviewing this introduction page and the pages in the category as shown at the bottom of this page.



=Summary=
Openmoko, Inc. is building a Linux based smart phone with full GPL compatible firmware source code for Openmoko, project code named GTA02 (Neo FreeRunner).

Detailed hardware component selection can be found below. See also the [[Neo FreeRunner GTA02 Hardware Requirements]] used in making these component selections.

<gallery>
Image:Gta02a5 pcba cs.JPG|component (back) side NOTE: GTA02 A5 PCBA Component Side photo
Image:Gta02a5 pcba ps.JPG|display (top) side NOTE: GTA02 A5 PCBA Print Side photo
Image:GTA02 A5 PCB CS.jpg|component (back) side NOTE: GTA02 A5 PCB Component Side photo
Image:GTA02 A5 PCB PS.jpg|display (top) side NOTE: GTA02 A5 PCB Print Side photo
Image:SimpleComponentDiagram.jpg|Simplified Hardware Component Diagram
</gallery>

= GTA02 Hardware Component Selection =

== Physical Dimensions ==
* 120.7 x 62 x 18.5 mm (4.75 x 2.44 x 0.728 inch)
* 110 +/- 5 g (4 ounces) without battery 

== Main components ==
=== Processor ===
The main Processor (CPU) is a [[Samsung S3C2442B B54]] (running at 400 MHz)

GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt

{{:Samsung S3C2442B B54}}

=== Power Management ===
A NXP PCF50633 04 N3 is used for [[Neo1973_Power_Management|power management]].

* NXP PMU index: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page] 
* Product Datasheet: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf NXP PCF50633 Product Data Sheet] 
* Product User manual: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633UM_6.pdf NXP PCF50633 User Manual] 
**Special thanks NXP provide full user manual and support openness for all developer
**Datasheet/User manual usage [http://lists.openmoko.org/pipermail/community/2008-March/013898.html was legally authorized by NXP]
* Connected to: S3C2442 via I2C, client address is 0x08. 
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch 

=== Flash ===
==== NAND Flash ====
256MB integrated Samsung NAND flash inside the 2442 multi-chip package, attached to the S3C2442 NAND controller

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 S3C2442]
* Data Sheet: S3C2442 B54 comes with 256 MB NAND MCP package
* Connected to: S3C2442 NAND controller 

==== NOR Flash ====

16MBit ST M58WR016KB706E NOR flash for 'unbrickable emergency boot' feature.

* Product Homepage: [http://www.st.com/stonline/products/families/memories/fl_nor_mob/index.htm ST Mobile Flash NOR/Mobile Terminal]
* Data Sheet: [http://www.st.com/stonline/products/literature/ds/13023/m58wr032qb.pdf M58WR016]
* Connected to: S3C2442 NAND controller 

=== SDRAM ===
128MB SDRAM (64MB inside 2442 MCP, 1x Samsung K4M51323PC) attached to S3C2442 SDRAM controller
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M51323PC Samsung K4M51323PC]
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M51323PC/ds_k4m51323pc.pdf Samsung K4M51323PC]
* Connected to: S3C2442 

== GSM/GPRS ==
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.

* Connected to: S3C2442 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch
* Accessible GSM/GPRS antenna jack (if battery cover is removed) 

=== CALYPSO ASIC digital baseband ===
Unfortunately we cannot provide many details on the GSM chipset due to very tight [http://en.wikipedia.org/wiki/Non-disclosure_agreement NDA]s. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2442. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.

The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.
The legality of reading these files may vary according to your local laws, as may generating code from them.

*Calypso D751992AZHH 
*The firmware within GTA02 should be moko6 or later (internal code name)

=== TI TWL3025BZGMR analog baseband ===
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014] 

=== TI TRF6151 (GSM/PCS) RF Transceiver ===
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] 
GPRS Class12/CS4 

== AGPS ==
[[u-blox ANTARIS 4 ATR0635]] chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
{{:u-blox ANTARIS 4 ATR0635}}

== Accelerometers ==
Two ST LIS302DL
* Homepage: http://www.st.com/stonline/products/literature/ds/12726/lis302dl.htm
* Datasheet: http://www.st.com/stonline/products/literature/ds/12726.pdf
* Connected to: S3C2442 via SPI interface
* S3C2442 SPI EINT interrupt inputs 

== Graphics/3D Acceleration ==

Smedia Glamo 3362.
* Homepage: http://www.smediatech.com/product3362.htm
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC). There is hope that the glamo chip features may be usable even without a NDA, see [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ the hack here]
* Connected to: S3C2442 Address/Data bus 

=== microSD ===
The GTA02 has one microSD aka Transflash slot. Using the Glamo 3362 MMC/SD controller

*It should support SDHC, and 4GB card has been tested. Anyone with 8GB card? MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].
* Connected to: Glamo 3362 MMC/SD controller
* Driver: Check svn for the SMedia driver with SD implementation
* [[Supported microSD cards]]
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]
* SANDISK 128 MB/512 MB and some 4G SDHC card been verified could work on GTA02 

== LCD Module (LCM) ==
Toppoly (tpo) 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 TD028TTEC1 module, using a Toshiba JBT6K74 TFT
LCD Driver Chipset. 
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]
* Specification: http://www.cip.physik.uni-muenchen.de/~Wolfgang.Draxinger/stuff/openmoko/TD028TTEC1.pdf
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch
* Connected to: Glamo3362 LCM interface and Glamo3362 SPI Interface 

==== Touch Screen ====
* Connected to: S3C2442 TS controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_touchscreen.patch

== Bluetooth Module==
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4

* Data Sheet: [http://www.delta.com.tw/product/cp/vco/BT/download/pdf/CS/2.DFBM-CS320.pdf 2.DFBM-CS320.pdf]
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]
* Driver: Stock Linux Kernel BlueZ
* Connected to: S3C2442 USB Host controller (OHCI)
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch 

=== Bluetooth Audio ===
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec. 

== WiFi Module==

Accton (WLAN 802.11b/g SiP-M WM3236AQ(Flash Ver:2.0 Atheros AR6001GZ)
* Connected to: S3C2442 SDIO Host controller 
* Datasheet: [http://www.accton.com/products/Datasheet/WM3236A.AQ.pdf Accton 3236AQ datasheet] 
* Driver: http://svn.openmoko.org/developers/sameo/patches/ 

== Vibrator ==
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch
* Connected to: S3C2442 GPIO

== USB Host ==
The USB Host controller is inside the S3C2442
* Driver: Stock Linux kernel ohci_hcd
* USB version 1.1
* Supply USB 5v in Host mode using usb power switch AAT1275IRN-5.0-T1
** http://www.analogictech.com/products/digitalfiles/AAT1275.pdf
* A net EN_USBHOST is controlled by PMU GPIO "GPO", this one signal when asserted (high)
** enables generation of 5V for external device using a charge pump
** enables connection of 15K pulldowns to D+ and D- to allow device insertion and removal detection for host mode
** DISABLES the path for USB power to charge the battery

It should also be possible to use host mode with externally-provided power. This will allow the FreeRunner to be connected to a USB device and be powered and charging the battery if present at the same time.

* Connect 0V, d+, d-, +5 to your USB device
* Connect a 15k ohm resistor between d+ and ground
* Connect a 15k ohm resistor between d- and ground
* Connect 0V, +5 to your >1A power source
** If your power source was not the Openmoko 1A charger, additionally connect a 47K ohm 5% resistor between the ID pin and ground to pretend to be the 1A charger.

In addition you need to make sure EN_USBHOST signal that enables the physical Host mode power generation and disables the USB -> PMU charging path is deasserted. This may be taken care of automatically shortly by detection of the 48K resistor on a USB insertion leading to forcing EN_USBHOST deasserted. The charge pump that generates the 5V in host mode doesn't seem to mind getting external 5V given to it, but the real issue is that the battery will not be charged at all if we leave EN_USBHOST asserted since one of its jobs is to stop that happening.

== USB Device ==
The USB Device controller is inside the S3C2442
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use
* 1200mAh lithium battery charges when connected to powered host.
* Mini-AB connector similar to [http://www.cypressindustries.com/shoponline/proddetail.asp?prod=CCMUSBAB-32005-700&cat=34 this one].

== I2C Devices ==
I2C is a simple communication standard intended to move small amounts of data a few inches between chips.
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973. 

== Audio ==
See also: [[Neo1973 Audio Subsystem]]

=== Wolfson Codec ===
There's a [[WM8753]] Wolfson Microelectronics CODEC (This is not a 'smart' codec that can interpret MP3/... it is a simple dumb 'sound card'.)
* Product Homepage: http://www.wolfsonmicro.com/products/WM8753/
* Data Sheet: [http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf WM8753.pdf]
* Connected to: S3C2442 IIS interface (PCM data), S3C2442 I2C (Control)
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/asoc.patch

=== Mono Amplifier ===
There's a National Semiconductor [[LM4853]] Mono Amplifier at the analog audio output of the WM8753

* Product Homepage: [http://www.national.com/pf/LM/LM4853.html LM4853.html]
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4853.pdf LM4853.pdf]
* Connects to (LM4853 pin):
** S3C2442 GPIO: HP_IN, AMP_SHUT (shutdown);
** Wolfson WM8753: LOUTL (LEFTIN), LOUTR (RIGHTIN);
** speaker4102: (LEFTOUT/BLTOUT-, BLTOUT+);
** headset-jack: ring 2 (RIGHTOUT), ring 3 (LEFTOUT/BLTOUT-) via 1uF-33R each

=== Analog wired Headset ===
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.

The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration.

ring 
1(base): GND 
2: right out 
3: left out 
4(tip): mic + HOLD-button(press:short to GND)

=== Buttons ===
The Neo1973 GTA02 features two buttons:
* [[Neo1973 Power Button|The Power Button]]
* [[Neo1973 AUX Button|The "Aux" button]]

== Case ==
The case for the FreeRunner is all black, as seen on the front page of the wiki.

Openmoko has released the CAD files for the case schematics for the Openmoko [[Neo1973]] (GTA01) and Neo FreeRunner. These are available in the original Pro/E (.asm/.prt) format and alternative formats created from the originals.

We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.

* [http://downloads.openmoko.org/CAD/NeoFreerunner_ProE.zip The original Pro/E (.asm/.prt) format]

[http://downloads.openmoko.org/CAD/ Browse CAD directory]

=Accessory=

== Stylus ==

Using 4 in 1 laser pen
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]
*GTA02 standard setup comes with [http://www.quarton.com.tw/laser_pen_infiniter_xp_2.html QUARTON XPII 4 in 1 laser pen]

== Battery ==
The [[Neo FreeRunner (GTA02) Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility with a Nokia BL6C battery.
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.

* GTA02 using the smart battery based on TI bq27000 chipset
* SANYO UF653450S 1200mAh cell. 
* Battery schematics: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf GTA02 Smart Battery Schematics]

== microSD Card ==

GTA02 should come with one of following microSD card

* [http://www.transcendusa.com/ Transcend] 512MB microSD card
* [http://www.sandisk.com/ SanDisk] 512MB microSD card 

== Charger ==

AKII Technology Charger

*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]
*Input: 100-240v~ /0.3A
*Output: +5v up to 2.0A
*Add 47.5k 1% resistor between ID pin and ground for openmoko charger identification 

= History =

== GTA02v1 ==
First generation of prototypes that was given to internal Openmoko software developers. Total 30 pcs fabricated.

*It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash
*Using the PCF50633 05 N3 due to 04 N3 not available, re-work power for basic schematics verification
*Using GTA01 SIM socket
*Add external debug port
*Still using Global locate A-GPS
* ATAG_REVISION: 0310

== GTA02v2 ==
Second generation of prototypes, Total 50 pcs run at Taipei SMT factory MOUNT

*Ideal is have 256 MB NAND on Samsung package, Due to chip availability Start using S3C2442 B43
*Using correct PMU PCF50633 04 N3
*Change new SIM socket
*Change to u-blox A-GPS
*Change LCM power from 3.3v to 1.8v
*USB power switch layout/pin assignment mistake, could not verify USB host supply 5v function
*GPS function verified ok with good sensitivity
* ATAG_REVISION: 0320

== GTA02v3 ==
Production verification version, 2007/10/11 28 pcs fabricate at FIC SuZhou

*Still using S3C2442 B43 for hardware verification
*Using control pilot run to verify S3C2442 B54 chips 
* ATAG_REVISION: 0330

== GTA02v4 ==
Mass production release candidate version 1

2 weeks after v3 gerber out, release the v4 gerber, and 2007/10/20 20 pcs fabricate at FIC SuZhou

*Change LCM power from 1.8v to 3.3v for display stability issue
*fabricate another 200 pcs for yield rate/production verification
*fabricate 50 pcs with S3C2442 B43 (128 MB NAND) for quality comparsion
*USB host power chip have some output voltage stability issues with Vb/Vcc comes from different power source, need layout change to fix the issue
*Battery Coulomb design not working on A4
* ATAG_REVISION: 0340

== GTA02v5 ==
Mass production candidate version 2/Mass production version

* First batch fabricate 2008/1/14 at FIC SuZhou
* Mass production A5 trial run start from 2008 March, including some resistor/capacitor change compare with inital 100 pcs prototypes A5, and prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]
* Coulomb counter issue fixed
* USB host power switch fixed
* Need add capacitor for PMU Vbat input for stability issue, this could be done by direct SMT or hand rework
* Need rework (still using SMT in production) add capacitor for PMU Vbat input for PMU stability issue.
* Need manual rework GSM IR UART path a 100k pull down for better GSM deep sleep
* ATAG_REVISION: 0350

===GTA02 mass Production version change list===
*PMU's LED power error: PMU potential damage issue
*NOR FLASH enable WP: User can write data into NOR FLASH.
*CE CS/RS fine tune: Audio's background noise too high
*I2C pull high resistor: The resistor is too high and signal is distorted
*GSM leakage current: TX_MODEM has a pull high resistor on IO_3V3
*Power consumption: Disable keep active function
*SDIO clock and esd protect resistor
*Refer to Datasheet: R1526 to 33K
*GSM modem on pin: The R1018 is too small and has some leakage current
*LED driving transistor: When GPIO is on, the transistor will be draw more current on LED. This is component change fix, do not need change PCB or re-work.

== GTA02v6 ==
Mass production candidate version 3/Mass production version 

A6 will be fine tune version of A5, only minor schematic change for better product quality and version control. Capacitor and resistor change A6 also on mass production A5 

*First 100 pcs start from 2008 mid April, and factory make component placement mistake on GSM, second 100 pcs PCB arrive time TBD.
*Add capacitor space for Vbat, reduce the SMT effort
*Add GSM IR resistor for better GSM deep sleep
*Reserve 3 GPIO for hardware version control
*Fixed LEDs power usage (from about 150mW of v5 to about 25mW)
* ATAG_REVISION: 0360

=== GTA02 A5 to A6 changes ===
*Power Glitch on VB_SYS: Add capacitor on layout, Mass production A5 also apply this change.
*G-sensor separate these interrupt pins: At A5, each accelerometer INT1/INT2 connected to same line, at A6 only INT1 was connected.
*GSM_modem power source Reduce power's ripple when the phone is talking
*Keep active Disable keep active function, just fine tune
*GPIO for version control
*GSM RX_IR has some noise Add resistor and reduce GSM RX_IR noise and gsm can't enter suspend mode easily, apply on mass production A5.
*LED driving transistor apply on mass production A5.
*LCM's VDDIO We can totally power off LCM's power, save about extra 1mA.

= Debug Board =

== Debug Board Connector definition ==

This is the connector used to connect the [[Debug Board]] and possibly other hardware.

Connections are:
* 39 - GND
* 38 - STDI
* 37 - _RESET
* 36 - STMS
* 35 - STCK
* 34 - STDO
* 33 - GSM_EN
* 29 - _STRST
* 19 - X_I2C_SCL (H-TP4703)
* 18 - X_I2C_SDA (H-TP4704)
* 17 - SPI_CLK0
* 16 - SPI_MOSI0
* 15 - SPI-MISO0
* 14 - SS0
* 13 - EINT3 (H-TP4705)
* 3 - CONSOLE_TXD (H-TP4701)
* 2 - CONSOLE_RXD (H-TP4702)

Information from [http://people.openmoko.org/roh/Debugport_GTA01bv4.png].

= Distinguishing hardware revisions =
== Inside the [[Bootloader]] ==
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)

== Inside the [[Kernel]] ==
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.

== From Userspace ==
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.

= Certification =

== FCC ==
*For US Import
** 850/1800/1900 Band, FCC ID: EUNGTA02
** 900/1800/1900 Band, FCC ID: EUNGTA02E
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02_850_1800_1900/ FCC test report(GTA02)]
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02E_900_1800_1900/ FCC test report(GTA02E)]

== CE ==
*For Europe
**Registration number: M528583V-EO
**[http://people.openmoko.org/tony_tu/GTA02/certificate/CE/ CE report and certificate]

== NCC ==
*For Taiwan Import
**NCC certification number: CCAF08DG0080T0
**[http://people.openmoko.org/tony_tu/GTA02/certificate/NCC NCC report and certificate]

[[Category:GTA02 Hardware]]

Automatic emulation in Ubuntu

2008-07-20T20:37:18Z

Newkirk: /* Problems */

[[Image:Qemu-ubuntu1.png|thumb|emulation of [[Openmoko]] running on Ubuntu]]

This is a tutorial for getting an emulation environment on an Ubuntu system. For other systems see the [[Installation guide]]

== Installation ==

You have to know that there is a great tool to get it running on a linux system, namely the [[MokoMakefile]]. This is a sort of wrapper round several instructions, so it is easy to set up and maintain a development environment. If you build the whole [[MokoMakefile]], you will need approximately 12GB, a swap+ram memory of about 1GB and minimum 5 hours time. But we will only build it for Qemu (the emulator that I will use) and that needs (on my system) only 890mb and a 15 min of your time.

To get it running, you will have to tweak your ubuntu a little bit (This will not damage other programs, everything will work as before).
* Configure your sources (System -> Administration -> Software Sources) to include:
** Canonical-supported Open Source software (main)
** Community-maintained Open Source software (universe)
* Open your terminal (Applications -> Accessories -> Terminal).
* Enter following command and select NO when it asks to install dash as /bin/sh (You will have to enter your password)
sudo dpkg-reconfigure dash
* Install the needed programs on Hardy Heron 8.04 (You will have to enter your password):
sudo apt-get install monotone git-core git-svn git-email \
git-cvs git-arch gitk python-dev ccache m4 sed bison make cvs gawk \
libc6-dev g++ subversion sharutils docbook openjade quilt libmpfr-dev \
libpcre3-dev texinfo texi2html libboost-date-time-dev libboost-filesystem-dev \
libboost-regex-dev libboost-test-dev libboost-dev zlib1g-dev build-essential \
dh-make debhelper devscripts gcc-3.4 lynx netpbm libsdl1.2-dev dosfstools \
help2man python-psyco lynx

*For older versions (git-svn git-email git-cvs git-arch gitk are replaced by cogito)
sudo apt-get install monotone git-core cogito python-dev ccache m4 sed bison \
make cvs gawk libc6-dev g++ subversion sharutils docbook openjade quilt \
libmpfr-dev libpcre3-dev texinfo texi2html libboost-date-time-dev \
libboost-filesystem-dev libboost-regex-dev libboost-test-dev libboost-dev \
zlib1g-dev build-essential dh-make debhelper devscripts gcc-3.4 netpbm \
libsdl1.2-dev dosfstools help2man python-psyco lynx

Voila your system is ready to get the install Openmoko.

Now we will install Openmoko in a directory by downloading the MokoMakefile in it and build it.
* Create a directory and go into the directory:
mkdir openmoko
cd openmoko
* Get the MokoMakefile (Currently down due to fires in California. Use the link below instead):
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

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

* Make the MokoMakefile and tell it, you want to install it for qemu:
make qemu

This will download the necessary files of the latest release and build them following the MokoMakefile. After that it will start into the emulator for the first time. Voila you have now successfully installed openmoko onto your ubuntu system.

===Creating a menu item for Openmoko (optional)===

You can create a menu item for starting Openmoko by doing the following:

*Open the terminal (Applications->Accessories->Terminal)

*Go to the openmoko directory:

cd ~/openmoko

*open the file moko.sh with '''gedit''':

gedit moko.sh

*insert the following text into the file:

#!/bin/bash
cd ~/openmoko
make run-qemu

*Press "save" and close gedit

*then run the following commands:
chmod +x moko.sh
alacarte

*and add a menu item with these values:
**Name: Openmoko
**Command: ~/openmoko/moko.sh

**If you want to you can add an appropriate icon by clicking on the image on the top left. You can download some useful images here:
***[http://wiki.openmoko.org/wiki/Artwork Artwork in the Openmoko wiki]
***[http://openclipart.org/media/tags/openmoko Openmoko at the Open Clip Art Library]

==Help with running Openmoko in Qemu==

If you have created a menu item you can start Openmoko through the applications menu of Ubuntu. If you have not, you can start it by:

* Open your terminal (Applications->Accessories->Terminal).
* Go to the directory:
cd openmoko
* starting with the MokoMakefile
make run-qemu

The first screen of Openmoko will show a nice picture of the Openmoko logo which will be followed
almost immediately by the BOOT MENU, this is done by the bootloader.

In the BOOT MENU you can choose different options. To select an option you have to press enter (=aux) and to execute it, hit space (=power). The default selection will boot Openmoko.
Thus if the BOOT MENU shows, you just have to hit the space bar and the phone software will load.

While booting Openmoko the progress will be shown in text mode. Depending on your computer's performance it might take a while (some minutes even) to complete the boot. When complete you will see the graphical interface as will be shown on the phone itself (but slightly larger due to the larger pixelsize of your screen).

A few pointers on using Openmoko:
* You can select the icon that looks like "+" for a list of applications you can run.
* You can select the icon that looks like "three gears" for a list of applications that are running now. Here you can also terminate unwanted applications when you are unable to do so from within the application itself.
* You can select the icon that looks like a "house" to get back to the first home screen.
* The statusbar at the top is always shown and by clicking on the top-left corner you can switch to another application that is already running. The "Home" application is always running and clicking on it will bring you back to the home screen.

See [[Qemu]] for more advanced information on running Openmoko in Qemu.

==Installing ipk packages==
First you need a xxx.ipk package, see [[toolchain]] on how to compile an application for the ARM CPU and create the package.

Note that if at this point you have the Openmoko Qemu running, it is probably wise to terminate it first.
Then you can install the xxx.ipk package for access by the Qemu emulator with:

cd openmoko
mkdir -p build/tmp/deploy/glibc/ipk/a
cp xxx.ipk build/tmp/deploy/glibc/ipk/a/xxx_a.ipk
make qemu-copy-package-xxx

''Note: for some reason qemu-copy-package-xxx looks for above source file.
Maybe this part can be improved, or a different command can overcome the problem of creating this directory.''

When above make command was succesful the next time you start Openmoko Qemu,
you still need to make the installed application available in the application list.
For this you can select from within Openmoko the terminal application
(Select icon that looks like "+" for the list of available applicaitons, select "Applications" and select the "Terminal").
In this terminal double-click, so you can type in the commands:
opkg install /media/mmcblk0/xxx_a.ipk
exit
After the "exit" command you should return to the Task list, in which the newly
added application should be listed under a name which was choosen when building the ipk package.

== Updating Openmoko==
* Open your terminal (Applications->Accessories->Terminal).
* Go to the directory:
cd openmoko
* Update with the MokoMakefile
make qemu

== Problems ==
If you have any problems, just add it here

After issuing the command 'make qemu' in Gutsy, the installation eventually borks with

make[2]: Leaving directory `/usr/local/src/openmoko/build/qemu/arm-softmmu'
make[1]: Leaving directory `/usr/local/src/openmoko/build/qemu'
[ -e images/openmoko ] || mkdir -p images/openmoko
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )
Retrieving available builds list...
Kernel is... not found
make: *** [download-images] Error 255

[[User:BioGeek|BioGeek]] 02:03, 27 March 2008 (CET)

Do you still have the problem?

[[User:Dolfje|Dolfje]] 20:54, 9 April 2008 (CEST)

I tested this today (uImage-2.6.24+svnr4301-r4251-r5-om-gta01.bin) on '''hardy'''. Qemu doesn't compile with gcc4 you need:
sudo aptitude install gcc-3.4
After the init process started, became the emulation extremely slow. It takes more than 15 minutes
to boot the GUI on 2GHz CPU and you have to klick & hold the mouse several seconds to see
any visual response. It would be great if there was a easy way to get a shell,
i.e. why the serial port (ctrl+shift-3) doesn't have a getty & co attached? 
Can anybody confirm this?
--[[User:Captn|Captn]] 12:29, 18 April 2008 (CEST)

Hi, just to tell that the ''Install ipkg package'' part is not effective since there is no room to install the .ipk on the QEmu (say ROM image) device.

Have any idea on how to get over it or to enable the automatic memory allocation on QEmu if allowed?

--[[User:VdeGrandpré|VdeGrandpré]] 17:37, 12 mai 2008 (EST)

I have compiled the Qemu source just fine on Ubuntu Hardy, but when the emulator started it showed up with an unusual QT theme. After the nice picture with the two boots there appeared a message line "No network" in the middle of the screen and 4 icons (cellphone, Q, star and lock). The buttons below the icons are unresponsive. They show a change in the background color when I click them with the mouse, but then nothing happens. Even if I press them for several seconds as noted above. Has the Openmoko theme been accidentally replaced by a non-working QT theme or did I configure something wrong on my end?

Thomas

--[[User:Xaos|Xaos]] 15:06, July 7th, 2008 (CST)

Thomas, I got the same thing when I tried. On the #openmoko IRC channel, lindi and I (with help) got this to work:

1. After building qemu with "make qemu", close the emulator and:

2. modify the file: build/qemu/openmoko/env as follows (you may need to adjust these values as time goes by for different images):
# rootfs_wildcard="Open?oko-openmoko-*image*-om-gta01.rootfs.jffs2"
rootfs_wildcard="Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080706-om-gta01.rootfs.jffs2"
#download_dir="http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/"
download_dir="http://buildhost.openmoko.org/daily/neo1973/200807/20080706/"

3. Download the above .jffs2 file (build the URL with the download_dir and the rootfs_wildcard values) to images/openmoko/

4. run "make flash-qemu-official"

5. run "make run-qemu-snapshot" or "make run-qemu"

--[[User:Schafdog|schafdog]] 15:10, July 1th 2008 (CST)

Built succesfully on a Fedora Linux 9. Trying to run on the linux box but with the XServer on OS X. It doesn't react to any keypress. Now tried it locally. The keypress works, but stil having some issues to get openmoko up.

Ubuntu 8.04 Hardy Heron, it was also necessary to "apt-get install libgnutls-dev".
--[[User:Newkirk|Newkirk]] 20:37, 20 July 2008 (UTC)
{{Languages|Automatic emulation in Ubuntu}}

[[Category:Technical]]
[[Category:Documentation]]