Openmoko - User contributions [en]

Manually using GPRS

2009-01-02T17:19:40Z

Dewey: /* From OM2008.8 repositories */

{{note| These instructions are for OM2008.8 . If you are using the FSO stack, see [[GPRS_FSO]].}}

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 ==

There are two sources, where you can find gsm0710muxd.

=== From OM2008.8 repositories ===

Good news, working gsm0710muxd can be installed just by typing "opkg install gsm0710muxd"

NOTE: ASU2008.12 boots in 45s and gsm0710muxd has probably not enough time to initialize GSM modem (gsm0710muxd is unable to provide working tty device to qtopia => qpe fails to open GSM modem and quits)
==> Some kind of delay may be needed in /etc/X11/Xsession.d/89qtopia

==> It has also been suggested on the mailing lists that an "update-rc.d gsm0710muxd defaults 11" be issued to get this to start earlier in the boot process to give the modem a chance to initialize before QPE starts.

=== From Angstrom Repositories ===

If the gsm0710muxd that is found in the OM2008.8 repository refuses to work, you can use the one from the Angstrom Repositories (see [[Repositories]]) instead.

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

I don't know if the package got renamed but that one wasn't in there the one i downloaded was

http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/gsm0710muxd_0.9.2+gitr79e10fe8ad0828e5be9a5c087ac9ee04956674c1-r0.1_armv4t.ipk

haven't gotten past this step yet well see how / if it works. :)

This link was working for me on 11.12.2008 (I've successfully muxed GSM device and sent command for echo reduction - http://lists.openmoko.org/pipermail/community/2008-August/028495.html)

http://shr.bearstech.com/shr-testing/ipk/armv4t/gsm0710muxd-dbg_0.9.2+gitr12+d8b36b923ef69a64cb5a2d3bca799d772b9c73c3-r0.1_armv4t.ipk

and the dependencies from here:

http://www.angstrom-distribution.org/repo/?pkgname=gsm0710muxd

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

=== Common part ===

The most important step after installing gsm0710muxd is to tell QPE to use the MUX instead of the device directly. If you follow the instructions in the link above, there is a step that replaces the 89qtopia init script with one from their script package. The key difference is the addition of the following lines that tells QPE to use the MUX:

in /etc/X11/Xsession.d/89qtopia

<code>
identvar=$(date +%s) 
ptsvar=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer
org.freesmartphone.GSM.MUX.AllocChannel string:$identvar | grep string | awk -F '"' '{ print $2 }')
 

export QTOPIA_PHONE_DEVICE=$ptsvar
 
</code>

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

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. Note that you can use the command line scripts "gprson" and "gprsoff" in place of the GUI if you need to do some debugging.

= 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.

[http://www.teaparty.net/technotes/openmoko-2.html#GPRS Here] is Tom's documentation on how he got it working (under 2008.08), with config files and example output.

= 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>

Comment by Vasco: I also had to include this in order to survive a "'''IPCP: timeout sending Config-Requests'''" sporadic error that dropped my connection right in the beginning:
<pre>
ipcp-restart 10
</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 || Telstra || Any || telstra.internet || || use CHAP auth with "" secret ||
|-
| Australia || Virgin || Any || VirginInternet || ||
|-
| Australia || Vodafone || Any || vfinternet.au || ||
|-
| Austria|| Orange/One|| Any || web.one.at || web/web || works with gsm0710d under om2008.9: [http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295 howto] - complete /etc/ppp/ directory with settings can be found here: [http://www.true-binary.com/wp-content/uploads/2008/11/orange_ppp.tar.gz orange_ppp.tar.gz]
|-
| 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.
|-
| Czech Republic || 02 || Unlimited data plan || internet || must be empty || [[http://wiki.openmoko.org/index.php?title=Manually_using_GPRS&action=submit#Option_3:_Without_GSM_multiplexing_and_without_a_GUI Works with OM2008.9]].
|-

| 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 || ||
|-
| Fiji || Digicel || Any || wap.digicelpacific.com || || nameserver 10.150.123.41 10.150.102.240 Must use a proxy server 10.150.122.12:8080
|-
| 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 || orange orange|| Work under OM2008.9 FDOM with UI ( gsm0710muxd )
|-
| 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 || ||
|-
| Ireland || Vodafone || || isp.vodafone.ie || vodafone/vodafone ||
|-
| Ireland || O2 || || open.internet || gprs/gprs ||
|-
| 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 || ||
|-
| Russia || MTS || Any || internet.mts.ru / *99***1# || mts/mts ||
|-
| Russia || Megafon || Any || internet || ||
|-
| Spain || Masmovil || Any || internetmas || ||
|-
| Spain || Simyo || Any || gprs-service.com / *99# || ||
|-
| Spain || Yoigo || Any || internet / *99***1 || must be empty || [[Yoigo pppd scripts]]
|-
| Sweden || Parlino || || internet.parlino.se || || [[GPRS_FSO|Works with FSO]]
|-
| Sweden || Telia || || online.telia.se || || [[GPRS_FSO|Works with FSO]]
|-
| Switzerland || Sunrise || || internet || ||
|-
| Switzerland || Sunrise || MMS || mms.sunrise.ch || ||
|-
| 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>

= Qt Extended =
If password/username is not mandotory for your provider, input anything e.g. x. Works fine with 4.4.2.

= 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]]

Dfu-util-windows

2008-11-12T03:26:28Z

Dewey: /* Apply patch to compile with MinGW */

== dfu-util for Win32 ==

{{Note|This has been reported to work on Windows 2000, Windows XP and Windows Vista with the Neo FreeRunner. No reports have been received on whether it works with other versions of Windows or with the Neo 1973. There are some reports that image downloads and uploads are extremely slow for some people. The exact cause of this has not yet been pinpointed.}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. Theoretically, a USB standard-compliant DFU class driver should work, unfortunately, Windows does not come bundled with one. If you do not have a DFU class driver (ie. Windows does not recognize the device in U-Boot mode and pops up the New Device Wizard), the LibUSB-Win32 driver and accompanying INF file for the Neo FreeRunner can be used, this driver can be found in OpenmokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH=" /c/msys/1.0/lib/pkgconfig"

ensuring that the path is accessible from the MSYS shell and points to the pkgconfig files.

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4759)
+++ main.c (working copy)
@@ -35,6 +35,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +583,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n",
@@ -712,13 +730,19 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n",
usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4759)
+++ sam7dfu.c (working copy)
@@ -22,6 +22,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4759)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

check your PKG_CONFIG_PATH (see above) to make sure it is correct, otherwise, you can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: Openmoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Android

2008-11-09T18:54:58Z

Dewey: /* Current State */

{{Languages|Android}}
{{Distributions|Android}}

= Updates =

* 20081104 The first Android-image has been successfully created by Sean McNeil! You can try on your own: [http://people.openmoko.org/sean_mcneil/ android image and kernel] - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']
* 20081029 [[User:Cfriedt]] [http://benno.id.au Benno] has modified Android's build system so that it will output a JFFS2 image instead of YAFFS . Unlike JFFS2, which [http://64.233.169.104/search?q=cache:e8czlAdKTn0J:gentoo-wiki.com/JFFS2/Mounting+gentoo+jffs2&hl=en&ct=clnk&cd=1&gl=ca&client=firefox-a can be mounted read-only from an image], mounting a YAFFS image is not possible unless it's already been written to flash (it complains about the block device being of type '1' and not 'NAND'). JFFS2 also has the benefit that it's a standard OpenMoko image format (See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]])
* 20081023 [[User:Bricode]] To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw
* 20081022 [[User:Cfriedt]] I was able to 'trivially' compile all of the Android source code without error for the ARMv4T architecture by removing v5TE instructions. Although it will definitely not run anything predictably, at least now that I know the build system will work with a few simple substitutions in build/core/combo/arm-linux.mk. At this point I am able to go ahead and re-implement v5TE instructions as v4T instruction sequences instead (or re-implement entire sections of assembly with hand-optimized v4T instructions).
* 20081021 [[User:Cfriedt]] Android -> FreeRunner updates on my [http://perpetual-notion.blogspot.com/search/label/android blog]
* 20081021 Google released the majority [http://source.android.com/download source code] for the phone under Apache free and open-source [http://source.android.com/license license], with portions covered by other existing licenses, such as the Linux kernel under GPLv2.
* 200810?? [http://www.koolu.com Koolu.com] has announced that they will be '''selling the OpenMoko Freerunner with Android pre-installed''' beginning in November 2008, as well as offering '''free downloads of the Freerunner port of Android''' to existing Freerunner owners. Well-known open-source advocate [http://koolu.com/The-Koolu-Team/maddog.html Jon "maddog" Hall] is CTO and Ambassador for Koolu.

= Introduction =
This page is dedicated to porting the [http://www.android.com Android OS] to the [[Neo 1973]] and [[Neo FreeRunner]] handsets. Since the Android OS was [http://source.android.com/posts/opensource publically released] on 20081021, [http://benno.id.au/blog/2007/11/21/android-neo1973 work] [http://perpetual-notion.blogspot.com/search/label/android is] [http://groups.google.com/group/android-porting currently underway] to port Android to the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

== Goals ==
# Systematically introduce patches for ARMv4T in the Android codebase
# Provide Neo1973 and Neo FreeRunner hardware-dependent patches in the Android codebase, leveraging the work already done by the Openmoko developers, without forcing Android-specific changes upstream
# Provide a useable Android filesystem and kernel on the [[Distributions]] page that conform to current Openmoko installation routines

== Early Attempts ==
As [http://benno.id.au Ben Leslie] had pointed out on his [http://benno.id.au/blog/2007/11/21/android-neo1973 blog] far before the source code was released, [http://www.android.com Android] was originally designed to work with the ARMv5TE [http://en.wikipedia.org/wiki/Instruction_set_architecture instruction set architecture] (ISA), which allows for [http://en.wikipedia.org/wiki/ARM_architecture#DSP_Enhancement_Instructions DSP enhanced instructions]. Contrary to the ARMv5TE ISA, the Neo1973 and FreeRunner handsets both feature an arm920t core, which comply to the ARMv4T ISA.

Before the source code was released, kernel trap handlers were implemented to 'emulate' the ARMv5TE ISA. Although the results worked in many cases, trapping is costly and performance suffered as a result. Moreover, without explicitly knowing which conditions were set by various instructions, such as Thumb Mode execution, the result became nondeterministic.

== Current State ==

With the release of the Android [http://source.android.com source code], the Open Source community is no longer limited to dealing with a binary-only product. The Open Handset Alliance (OHA) has let their source code become their product for everyone enrich and benefit from.

Currently, porting efforts are underway in many circles. Patches should be submitted via the [http://source.android.com/submit-patches official Android channels].

To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw [[User:Bricode]]

[[User:Seanmcneil3|Sean McNeil]] said that he was able to get Androind running (including telephony) in his Freerunner [http://3v1n0.tuxfamily.org/tumblelog/post/368 source].

Ben Leslie mentioned on the android-porting list that he was able to get the 'Android' logo to appear on his Neo 1973.

=== Windows Connectivity ===

It is possible to get Windows to at least recognize the Android "Ethernet Gadget" and charge the FreeRunner using the Android USB Windows driver (http://dl.google.com/android/android_usb_windows.zip) by modifying the android_usb.inf file in that package before attempting to install the driver. The following modifications are required:

Add the following to the [Google.NTx86] section of the android_usb.inf file:

<pre>
; Neo FreeRunner
%USB\VID_1457&PID_5117.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117
%USB\VID_1457&PID_5117&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117&MI_01
</pre>

and add the following to the to the [Strings] section of the android_usb.inf file:

<pre>
USB\VID_1457&PID_5117.DeviceDescRelease="Neo FreeRunner"
USB\VID_1457&PID_5117&MI_01.DeviceDescRelease="Neo FreeRunner Composite ADB Interface"
</pre>

The Windows version of adb does not appear to recognize the connected device yet but at least the FreeRunner charges and the device driver indicates that "This device is working properly."

= How to Help =

== Getting Started ==

You can start by following the instructions to download and build the Android source from scratch. Please see [http://source.android.com/download http://source.android.com/download] and follow the instructions for your architecture.

== Publicize Your Efforts ==

It's generally a good idea to make your efforts known via wiki systems, public mailing lists, forums, and publically open version control systems.

Always take credit for your work but please don't do it in the form of comments. Some code is already hard enough to read without comments polluting the text. The best thing to do is to create a patch and put a header with your information at the top. Collaboration systems such as git might already do this for you (??).

If you create something new and have the ability to designate the license for it, please consider license compatibility issues.

== Porting Strategy ==

* Analysis and leverage of the existing build system
** buid/core/combo/arm-linux.mk
*** -D__ARCH_ARM_4__ -D__ARCH_ARM_4T__
*** -march=armv4t -mcpu=arm920t
** fix various static references to 'armv5'
* Isolating ARMv5TE ISA dependent code
** e.g. grep -n -R -i "${armv5te_isa_pattern}" ~/android
* Abstracting
** ( C/C++ )
*** Use inlined functions / #ifdef statments to implement functions in a portable manner
*** For inlined assembler calls, it's acceptable for now to use generic C code instead, so long as later on we optimize it by hand.
** ( ASM )
*** Proprocessor statements based on ISA / architecture, e.g. #ifdef __ARCH_ARM_5__ ... #endif #ifdef __ARCH_ARM_4__ ... #endif
*** It's highly suggested that preprocessor statements should not be nested (i.e. make them mutually exclusive)
*** Some people have suggested that we should not do #ifdef's based on ARCH or ISA, but rather based on an AndroidConfig.h which would define macros like PLD(...) #ifdef HAVE_ARM_PLD pld #else ... #endif .

For each ARMv5TE instruction, one could potentially
* Implement the instruction using general registers instead of DSP calls (i.e. eabi / softfloat)
* If that is a) nondeterministic, or b) slow, then sections of code need to be analyzed and hand-optimized for the ARMv4T isa

== List of Unsupported Instructions ==

This is a list of opcodes, extracted from the Android source, that are unsupported for ARMv4T compliant processors (specifically the arm920t). The opcodes represent instructions available for ARMv5, ARMv5T, and ARMv5TE architectures, which are not present in the ARMv4T ISA. The list was obtained by exhaustively editing the recompiling the Android source code until it compiled without error.

Please keep in mind, that in some cases, translating these instructions into a sequence of ARMv4T instructions will be impossible and / or result in nondeterministic execution because of
* the requirement of additional context
* the tendencies of certain opcodes to change condition registers that may or may not be present in the arm920t core

=== Opcodes ===

{{scroll box|height=480px|text=
<TABLE BORDER="1">
<TR>
<TH>Opcode</TH>
<TH>Desription</TH>
<TH>[[http://www.arm.com/miscPDFs/14128.pdf PDF]] Page Number</TH>
<TH>C</TH>
<TH>ASM</TH>
</TR>
<TR>
<TH VALIGN="TOP">BLX(1)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>166</TD>
<TD>N/A (Unused in Android)</TD>
<TD>N/A (Unused in Android)</TD>
</TR>
<TR>
<TH VALIGN="TOP">BLX(2)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>168</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_BLX
... (inline asm) ...
#else
... (inline asm with equivalent blx code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_BLX
#define BLX(a) \
blx a
#else
#define BLX(a) \
mov pc,lr \
bx a
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">CLZ</TH>
<TD>Count Leading Zeros</TD>
<TD>175</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_CLZ
... (inline asm) ...
#else
... (inline asm with equivalent clz code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081029
<pre>
#ifdef HAVE_CLZ
#define CLZ(Rd,Rm) \
clz Rd,Rm
#else
#define CLZ(Rd,Rm) \
...
#endif
...
CLZ(Rd,Rm)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">LDRD</TH>
<TD>Load Registers Doubleword</TD>
<TD>200</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_LDRD
... (inline asm) ...
#else
... (inline asm with ldrd substituted) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_LDRD
#define LDRD(a,b) \
ldrd a,b
#else
#define LDRD(a,b) \
...
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">PLD</TH>
<TD>Preload Data</TD>
<TD>240</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_PLD
... (inline asm) ...
#else
... (inline asm with pld removed) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove or substitute with a macro reference such as
<pre>
#ifdef HAVE_PLD
#define PLD(a,b) \
pld a,b
#else
#define PLD(a,b)
#endif
...
PLD(r0,#0)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLA<x><y></TH>
<TD>Signed Multiply-Accumulate</TD>
<TD>291</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAL<x><y></TH>
<TD>Signed Multiply Accumulate Long</TD>
<TD>298</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAW<y></TH>
<TD>Signed Multiply-Accumulate Word</TD>
<TD>302</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMUL<x><y></TH>
<TD>Signed Multiply</TD>
<TD>316</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULW<y></TH>
<TD>Signed Multiply Word</TD>
<TD>320</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QADD</TH>
<TD>Saturating Add</TD>
<TD>242</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDADD</TH>
<TD>Saturating Double and Add</TD>
<TD>249</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDSUB</TH>
<TD>Saturating Double and Subtract</TD>
<TD>251</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QSUB</TH>
<TD>Saturating Subtract</TD>
<TD>253</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">STRD</TH>
<TD>Store Registers Doubleword</TD>
<TD>349</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_STRD
... (inline asm) ...
#else
... (inline asm without strd) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_STRD
#define STRD(a,b) \
strd a,b
#else
#define STRD(a,b) \
...
#endif
</pre>

</TD>
</TR>
</TABLE>
}}

=== Scanning for Files That Use the ARMv5TE ISA ===

Using the above list of opcodes, one can scan the Android source code for ARMv4T-incompatible instruction sequences.

'''Code:'''
{{scroll box|height=240px|text=
<pre>
#!/bin/sh

# $1 is the android directory

if [ $# -ne 1 ]; then
exit -1
fi

cd "${1}"

opcodes="blx clz ldrd pld smlabb smlabt smlatt
smlal smlawb smlawt smulbb smulbt smultt smulwb
smulwt qadd qdadd qdsub qsub strd"

for op in ${opcodes}; do

echo "* ${op} ====================================="

if [ ! -e .files.${op} ]; then

files="$(grep -R -i "${op} " * 2>/dev/null)"
files="$(echo $files | grep -v "^Binary file" | sed -e 's/:.*//')"
files="$(echo $files| grep -v "CREDIT\|README\|^$kernel/\|.git/$\|$\.txt$$" | sort -u)"

echo "${files}" > .files.${op}

else
files="$(cat .files.${op})"
fi

for fil in ${files}; do
lines="$(grep -n -i "${op} " ${fil} | sed -e 's/:.*//g' )"
lines="$(echo $lines | sed -e 's/ /,/g')"
echo "** ${fil}: lines {${lines}}"
done
done
</pre>
}}

=== Source Files in Android that Use the ARMv5TE ISA ===

The list of files below may or may not be complete. There might also be some assembly code that is generated with a python script (verification?).

{{scroll box|height=150px|text=
* blx =====================================
** bionic/libc/tools/gensyscalls.py: lines {168,186}
** bootloader/legacy/nandwrite/init.S: lines {77}
** bootloader/legacy/usbloader/init.S: lines {95}
** dalvik/vm/arch/arm/CallEABI.S: lines {239}
** dalvik/vm/arch/arm/CallOldABI.S: lines {145}
** development/emulator/qtools/thumbdis.cpp: lines {187,265}
** external/qemu/target-arm/translate.c: lines {1151,1971,2444}
** external/qemu/trace.c: lines {774,1353,1358}
** system/core/libpixelflinger/codeflinger/disassem.c: lines {416}
* clz =====================================
** development/emulator/qtools/armdis.cpp: lines {654}
** external/opencore/codecs_v2/audio/aac/dec/src/pv_normalize.h: lines {67,84}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/norm_l.h: lines {137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/normalize_amr_wb.h: lines {78,95}
** external/opencore/codecs_v2/audio/mp3/dec/src/pvmp3_normalize.h: lines {67,84}
** external/opencore/codecs_v2/video/avc_h264/dec/src/vlc.cpp: lines {23}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/vlc_encode_inline.h: lines {125,162,168,204,218}
** external/qemu/target-arm/translate.c: lines {1247}
** external/skia/libcorecg/Sk64.cpp: lines {340,341,343}
** external/skia/libcorecg/SkMatrix.cpp: lines {500,501}
** external/skia/libsgl/effects/SkColorMatrixFilter.cpp: lines {135}
** external/skia/libsgl/sgl/SkBitmap.cpp: lines {945,946,947}
** external/skia/libsgl/sgl/SkBitmapShader.cpp: lines {32,33,34}
** external/skia/libsgl/sgl/SkGraphics.cpp: lines {429,437}
* ldrd =====================================
** dalvik/vm/mterp/armv5/OP_AGET_WIDE.S: lines {28}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE.S: lines {37}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE_QUICK.S: lines {10}
** dalvik/vm/mterp/armv5/OP_SGET_WIDE.S: lines {17}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2653,7464,8318,8390}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {40,41,42,43}
* pld =====================================
** bionic/libc/arch-arm/bionic/memcmp.S: lines {37,44,45,56,57,107,108,195,196}
** bionic/libc/arch-arm/bionic/memcmp16.S: lines {37,44,45,67,68,116,117,198,199}
** bionic/libc/arch-arm/bionic/memcpy.S: lines {55,56,57,145,266,293,320}
** bionic/libc/arch-arm/bionic/strlen.c: lines {59,65}
** bionic/libc/kernel/arch-arm/asm/arch/irqs.h: lines {162}
** external/elfutils/src/Makefile: lines {243}
** external/elfutils/src/Makefile.am: lines {32}
** external/elfutils/src/Makefile.in: lines {243}
** external/jpeg/jidctfst.S: lines {69,235,247}
** external/qemu/target-arm/translate.c: lines {1149}
** system/core/libpixelflinger/codeflinger/ARMAssembler.cpp: lines {368}
** system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp: lines {104,108,117}
** system/core/libpixelflinger/t32cb16blend.S: lines {111,112,134,143}
* smlabb =====================================
** external/jpeg/jidctfst.S: lines {110,115,155,156}
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {584,589}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {147,166}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {120,129}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {514,533}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {418,429}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {202}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {250}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {119,155,167,278,326,341}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {178,225,437,517}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {405,436}
* smlabt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {184}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {138}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {131,143,294,310}
* smlatt =====================================
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {585,590}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {157}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {441}
* smlal =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4.h: lines {179,223,236,257,267}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4_gcc.h: lines {264,341}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {178,188,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9.s: lines {84,90,96,101,109,114,116,118,121,132,138,150,163,165,167,174,176,178}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9_gcc.s: lines {73,79,86,90,98,103,105,107,110,121,127,139,152,154,156,163,165,167}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.asm: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.s: lines {145,164,180,190,194,201,209,219,227,233,239,243,246}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18_gcc.s: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.asm: lines {62,63,66,72,76,77,81,82,85,90,94,97,99,100,103,108,113,114,118,119,122,129,136,137,176,179,183,187,190,193}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.s: lines {67,68,71,77,81,82,86,87,90,95,99,102,104,105,108,113,118,119,123,124,127,134,141,142,181,184,188,192,195,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window_gcc.s: lines {65,66,69,75,79,80,84,85,88,93,97,100,102,103,106,111,116,117,121,122,125,132,139,140,179,182,186,190,193,196}
** external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm.h: lines {148}
** external/qemu/trace.c: lines {813}
** frameworks/base/opengl/libagl/iterators.S: lines {66,67}
** frameworks/base/opengl/libagl/matrix.h: lines {67,68,96,126,127,282,283,314,315,316}
* smlawb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {203,259}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {166,416}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {93,109}
** frameworks/base/opengl/libagl/matrix.h: lines {163,203}
* smlawt =====================================
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {114}
** frameworks/base/opengl/libagl/matrix.h: lines {162,202,243,244}
* smulbb =====================================
** external/jpeg/jidctfst.S: lines {109,114,151,153}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {79}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {71,81}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {207,251,297,348,361,375,427,440,487}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {199,234,274,314,316,326,367,369,404}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {121,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {123,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {122,140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {132,134,138,164,177,191}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {127,129,150,163}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mult.h: lines {121,141}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {115,139,151,163,189,190,212}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {112,113,164,183,201,218,265}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {250,457,531}
** external/skia/include/corecg/SkMath.h: lines {170}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {420,462}
** system/core/libpixelflinger/t32cb16blend.S: lines {39,66,74,82}
* smulbt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {115}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {109}
** system/core/libpixelflinger/codeflinger/texturing.cpp: lines {1091}
** system/core/libpixelflinger/t32cb16blend.S: lines {47,55}
* smultt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {131}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {100}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {467}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {73}
* smulwb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {221}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {373}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {222}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {283}
** external/opencore/codecs_v2/audio/sbc/enc/src/sbcenc_filter.h: lines {33}
** frameworks/base/opengl/libagl/matrix.h: lines {161,201,242}
* smulwt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {202,240}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {385,415}
* qadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {64}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {60}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {130,256}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {128,235}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_add.h: lines {122,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {123,145}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {71,102,152,176,192}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {91,115,148,202,234}
** external/openssl/crypto/bn/bn_prime.c: lines {454,455}
* qdadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/calc_sbr_synfilterbank.cpp: lines {116,162}
** external/opencore/codecs_v2/audio/aac/dec/src/trans4m_freq_2_time_fxp.cpp: lines {472,494}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {212,356,370,385,435,449}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {200,315,321,331,368,371}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {122,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {133,136,140,172,186,201}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {128,131,158,172}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {116}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {184}
* qdsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {302}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {275}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {124,147}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {165}
* qsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {167}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {162}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_sub.h: lines {121,138}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {88,127}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {70,133}
* strd =====================================
** dalvik/vm/mterp/armv5/OP_APUT_WIDE.S: lines {31}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE.S: lines {39}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE_QUICK.S: lines {14}
** dalvik/vm/mterp/armv5/OP_SPUT_WIDE.S: lines {21}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2834,7530,8331,8542}
** dalvik/vm/oo/Object.h: lines {589}
** external/opencore/fileformats/avi/parser/include/pv_avifile_streamlist.h: lines {179}
** external/opencore/fileformats/avi/parser/src/pv_avifile_streamlist.cpp: lines {153}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {47,52,56,60}
}}

=== Discussion ===
=== Notes ===
The file
<pre>
system/core/libpixelflinger/codeflinger/ARMAssembler.cpp
</pre>

will need special attention. It's responsible for dynamic generation of DSP code.

== Suggestions ==
* [[User:Cfriedt]] 20081024 I'm not sure how feasible this is, given that the [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#SMedia_3362_Documentation_.26_OpenGL_ES_Drivers SMedia 3362 is heavily NDA'd]. However, since the arm920t lacks a floating-point unit / DSP core, is it possible to use the SMedia chip for general-purpose math? This would help in the Android platform, at least, for things like audio and video codecs. Aside from an OpenGL ES driver, OpenMoko documentation for the SMedia would be highly appreciated.

= Important Links =
(Please Update Me)

== Documentation ==
* [http://source.android.com/documentation Android Documentation]
* [http://www.arm.com/documentation/ ARM Documentation], (keywords: armv4t, armv5t, armv5te, arm920t, arm926ej-s)
* [http://www.arm.com/miscPDFs/9658.pdf ARM Assembly Language Programming]
* [http://www.cse.unsw.edu.au/~cs3221/labs/assembler-intro.pdf An Introduction to the GNU Assembler]
* [http://www.heyrick.co.uk/assembler/apcsintro.html ARM Procedure Call Standard], [http://en.wikipedia.org/wiki/Calling_convention#ARM ARM Calling Conventions]

== Instruction Set References ==
* [http://www.arm.com/miscPDFs/14128.pdf ARM Architecture Reference Manual], The definitive ISA documentation
* [http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf ARM Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001l/QRC0001_UAL.pdf ARM and Thumb -2 Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0025b/DVI0025.pdf ARMv4T] (See section 1.4.13)
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0014a/DVI0014A_ARM10T_PO.pdf ARMv5T] (See section 4.16)
* [http://www.arm.com/pdfs/ARM-DSP.pdf ARM DSP Enhanced Instruction Set]
* [http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042c/IHI0042C_aapcs.pdf Procedure Call Standard for the ARM Architecture]

== Hardware Reference ==

* [[Neo1973 Hardware]]
* [[Neo FreeRunner GTA02 Hardware]]

== Communities ==
* [http://source.android.com/discuss Android Public Mailing Lists]
** Specifically, [http://groups.google.com/group/android-porting android-porting]
* [http://lists.openmoko.org/mailman/listinfo OpenMoko Mailing Lists]
** Specifically, [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel openmoko-kernel]
* [http://forum.koolu.org/viewforum.php?f=10 Android on FreeRunner] at KoolU.com
* [[Openmoko Local Groups]]
* [[Openmoko:Community_Portal]]

= See also =

* [[Debug_Board]]

= External Links =
== Youtube video /Andorid on FreeRunner ==

[http://tw.youtube.com/watch?v=m4NbsLmF9j0 Video 1]

[http://tw.youtube.com/watch?v=r6Op-7tNTiw Video 2]

== Headline text ==

[[Category:Distributions]]

Manually using GPRS

2008-10-01T18:21:56Z

Dewey: /* gsm0710muxd from Angstrom Repositories */

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/?pkgname=gsm0710muxd

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

The most important step after installing gsm0710muxd is to tell QPE to use the MUX instead of the device directly. If you follow the instructions in the link above, there is a step that replaces the 89qtopia init script with one from their script package. The key difference is the addition of the following lines that tells QPE to use the MUX:

in /etc/X11/Xsession.d/89qtopia

identvar=$(date +%s)
ptsvar=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer
org.freesmartphone.GSM.MUX.AllocChannel string:$identvar | grep
string | awk -F '"' '{ print $2 }')
export QTOPIA_PHONE_DEVICE=$ptsvar

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

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. Note that you can use the command line scripts "gprson" and "gprsoff" in place of the GUI if you need to do some debugging.

= 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]]

Manually using GPRS

2008-10-01T18:15:40Z

Dewey: /* gsm0710muxd from Angstrom Repositories */

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/?pkgname=gsm0710muxd

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

The most important step after installing gsm0710muxd is to tell QPE to use the MUX instead of the device directly. If you follow the instructions in the link above, there is a step that replaces the 89qtopia init script with one from their script package. The key difference is the addition of the following lines that tells QPE to use the MUX:

in /etc/X11/Xsession.d/89qtopia

identvar=$(date +%s)
ptsvar=$(dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer
org.freesmartphone.GSM.MUX.AllocChannel string:$identvar | grep
string | awk -F '"' '{ print $2 }')
export QTOPIA_PHONE_DEVICE=$ptsvar

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

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]]

Manually using GPRS

2008-10-01T16:39:37Z

Dewey: /* gsm0710muxd from Angstrom Repositories */

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/?pkgname=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]]

VoIP

2008-09-27T06:28:57Z

Dewey: Redirect to Linphone page for now until other options are available

#REDIRECT [[Linphone]]

Qtopia / Qt Extended on FreeRunner

2008-09-26T17:24:12Z

Dewey: /* Installing Qtopia */

{{Languages|Qtopia_on_FreeRunner}}

This page provides instructions on how to install Qtopia (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==
On 29 August 2008, Trolltech released the [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=79 Qtopia flash image for the FIC Neo FreeRunner (gta02)] containing the Qtopia 4.3.2 release (Version: 4.3.2-290808) (GPL version).
See [http://doc.trolltech.com/qtopia4.3/release-4-3-2.html Release-Notes]

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does not, however, have a web browser or a GPS application. There are however at least two third-party GPS applications available:
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps here]
* [http://www.linux4.be/fr/roadmap.html RoadMap(experimental) here]

On 2nd of September 2008 Trolltech also released a 4.3.3-snapshot which fixes a number issues (sms messages not retrieved after resume; Qtopia getting confused between two calls; Make default call volume down and mic up; Added echo fix.)

You can find all the Qtopia images [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 here]

=== What to expect in the next release (Qtopia 4.4)? ===
There is no schedule about the release, but it will be [http://n2.nabble.com/qtopia-update-tp832851p832862.html soon] (a few weeks, it's said to be [http://lists.openmoko.org/nabble.html#nabble-tt1120455|a1120476 around the corner]).
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]
* GPS api
* usb net/storage switching
* Gtalk support

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:

mount /dev/mmcblk0p1 /media/card
mkdir /media/card/boot

mkdir /media/mmcblk0p2
mount /dev/mmcblk0p2 /media/mmcblk0p2

This will set you up properly for the installation of the root filesystem and the kernel in the steps below.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia image from qtopia.net]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".

==== Creating a compressed tarball ====

Next, tar up the root filesystem:

# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.

mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/

==== Pointing Qtopia to the SD Card ====

Lorn Potter on the mailing lists pointed this out:

Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.

You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd
/dev node, to be able to run it this way"

Another user's solution to this is the following:

Edit this file: " /opt/Qtopia/etc/default/Trolltech/Storage.conf
And change the [MountPoint0] section so it resembles this:
-[
[MountPoint0]
Name[] = SD Card
Path=/dev/mmcblk0p1
Removable = 0
Applications = 0
Documents = 0
ContentDatabase = 0

== Option 3: updating from source ==

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)
cd /
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz
* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/
* once dowloaded untar it
tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz
* make a "build" dir
mkdir build
cd build
* configure and make:
../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01
make
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:

make install

will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

== Booting into Qtopia ==

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

== Internationalization ==

Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.

Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].

[[Category:Qtopia]]

== Suspend /Resume ==
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.

== Bugs ==

See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).

Bug reports should be sent to qt-bugs@trolltech.com.

=== in 4.3.2 release ===

* Voice notes seem not to work, only record a 44 bytes file, containing no voice

Distributions

2008-09-09T22:34:59Z

Dewey: /* Applications */

{{Languages|Distributions}}

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[OpenmokoFramework|FSO]]
* Community
** [[SHR]]
* Other
** [[Qtopia]]
** [[Debian]]
** [[Gentoo]]
</div>
|-
|}
Openmoko distributions are designed to run on various mobile devices, with the primary aim of Openmoko Inc.'s [[Neo 1973]] and [[Neo FreeRunner]] phones. They are similar to Linux distributions; complete operating systems with user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed.

While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below).

For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].

== About distributions ==

To be technically precise, 2007.2, 2008.8, FSO and SHR of these are not directly independent distributions, but different 'release targets'. They are built out of different branches of the [[OpenEmbedded]] metadistribution source tree, e.g. 2007.2 and 2008.8 are to each other like Ubuntu Gutsy is to Kubuntu Hardy. A [http://docs.openmoko.org/trac/roadmap roadmap] showing the number of remaining active tickets (in other words, bugs) is available on the bug [http://docs.openmoko.org/trac/ trac]king system (also accessible with the DOCS link at the top of every page).

One should only use feeds from packages of the same source-branch, else 'stuff will break', similar to like using .debs from Hardy on a Gutsy base system. Also note that there is NO supported upgrade path between these at the moment, thus updating by changing the feeds will most likely end in broken packages or even a unbootable system. Thus please always use [[dfu-util]] to switch between the different 'distributions' for now or install them in a dual-boot setup (e.g. via sdcard or NFS).

== Openmoko Inc. driven release targets ==

=== Om 2008.8 (ASU, April/August Software Update) ===

Om 2008.8 has been started to integrate the [http://trolltech.com/products/qtopia Qtopia] stack - on X11 - with a new set of graphically pleasing applications based on the Enlightenment Foundation Libraries. ASU is the internal name and is known as Om 2008.8 upon its release on August 8, 2008. Qtopia is a more mature product than the GNOME Mobile stack and you can expect all the standard feature phone applications to work in a solid way. It uses the Qtopia phone server. Since - contrary to standard Qtopia - it does not directly use the framebuffer, non-Qt applications can safely share the screen with Qt applications.

Om 2008.8 is maintained as "'''ASU-stable'''" with continuous updates.

* [[Om2008.8|Om 2008.8]]
* [[Downloads#Om_2008.8_images_.28ASU.29|Download > Om 2008.8 images (ASU)]]

=== Om 2007.2 (GTK) ===

[[Om 2007.2]] is for people who are familiar with the [http://www.gnome.org/mobile/ GNOME Mobile] initiative and who want to write applications that run on multiple devices running (parts of) GNOME Mobile. This includes Maemo, which runs on the Nokia Internet Tablets. The strength of the GTK+ stack is a UI and programming environment similar to what you run on your Linux desktop, if you’re into GNOME. The GTK+ has PIM applications based on the Evolution Data Server and runs the gsmd phone server. Although you can use them, the applications are still pretty rough und unfinished. Some people have problems with the stability of the phone server.

* [[Om 2007.2]]
* Availabilty: [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds
* [[Downloads#Openmoko_2007.2_images_.28GTK.29|Download]]
* Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone] and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
This is the base-system which is installed on FreeRunner when it leaves the factory.

2007.2 development driven by openmoko inc. has basically stopped and resources are allocated in favor of 2008.8, while the community currently does the effort to 'rescue' the 2007.2 telephony apps and pull them to the future middleware from FSO (see SHR).
thus patches are still welcome, especially if they help development of SHR.

=== FSO - freesmartphone.org ===

FSO has been started to overcome the deficiencies both of the 2007.2 and the 2008.8 stack, namely to come up with an extensible framework that gives developers the infrastructure they need to create solid and exciting software products based on the Openmoko platform. An infrastructure that supports competing UIs while we can collaborate on developing services, making the framework strong . Here, the focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. People report that despite its infancy, e.g. the phone server part in FSO is already more solid than anywhere else.

It is not really intended as future release-target, but used as a 'vessel' or 'container' for the development and testing of the new, future middleware.

The applications installed are intended as test-tools for the new middleware and not as fully featured, end user oriented applications. (even if it looks that way sometimes)

In the words of Mickey, project manager:

:"FSO is only a distro because "we can" (thanks to OpenEmbedded). Zhone is an independent UI application based on the FSO framework to facilitate testing. If you want to build own UIs or custom applications on the forthcoming Openmoko dbus service framework, then the FSO-image is a good starting point.

* [[FSO]]
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]
* [http://downloads.openmoko.org/framework/milestone2/ Download milestone 2]
* [http://freesmartphone.org freesmartphone.org]
* [http://shr.bearstech.com/ fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

== Openmoko Community driven release targets ==

=== SHR - Stable Hybrid Release ===

Stable Hybrid Release is a combination of the middleware from FSO, some of the 2007.2 GTK software (telephony-ui, pim), and Om2008.8 that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.

* [[Stable Hybrid Release]]

== Non-Openmoko distributions ==

These are not Openmoko (and OE) based distributions. These are an alternatives you can run on your Openmoko phones.

=== Qtopia ===

The Qtopia distribution from [http://www.trolltech.com Trolltech], it aims to provide a ready-to use image for Openmoko devices.

* [[Qtopia]]
* Download: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]

=== Debian ===

In the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team:

:It’s not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the Stable Hybrid Release software in our archive.

:So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)

* [[Debian]]

=== Gentoo ===

* [[Gentoo]]
== Features by distribution/release target ==

=== Connectivity ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Telephony || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| SMS || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| [[GPRS]] || Not through UI || Not through UI || Not through UI || N/A || {{No}} (3) || {{Yes}} (1)
|-
| WiFi || {{Yes}} || Not through UI || {{Yes}} (*) || N/A || {{Yes}} || {{Yes}}
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || {{Yes}}
|-
| Bluetooth || {{Yes}} || {{No}} || {{Yes}} || N/A || {{Yes}} || {{Yes}}
|-
| GPS || {{Yes}} (1) || {{Yes}} || {{Yes}} (1) || N/A || {{No}} || {{Yes}} (1)
|-
|}

=== User Interaction ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Stylus friendly || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}}
|-
| Finger friendly || Partially || Partially || Partially || N/A || {{Yes}} || {{No}}
|-
| Accelerometer || {{No}}|| {{No}} || {{Yes}} [[Gestures|(1)]] || N/A || {{No}} || {{No}}
|-
|}

=== Applications ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Terminal || Basic (2) || {{Yes}} || {{Yes}} (1) || N/A || {{Yes}} || {{Yes}}
|-
| PIM || {{Yes}} || {{No}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| Phonebook || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| Dialer || {{Yes}} || {{Yes}} || {{Yes}} || N/A || {{Yes}} || {{Yes}} (1)
|-
| Web Browser || {{Yes}} (1) || ? || {{Yes}} (1) || ? || {{No}} || {{Yes}} (midori)
|-
| Mail Client || ? || ? || {{Yes}} || ? || {{Yes}} || {{Yes}} (1)
|-
| XMPP Client || {{Yes}} (1) || ? || {{Yes}} [[Instant Messaging|(1)]] || ? || {{No}} || {{Yes}} (1)
|-
| Media Player || {{Yes}} || ? || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} (1)
|-
|}

=== Toolkits / Runtimes ===
{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| GTK+ || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}}
|-
| QT/Qtopia || No || {{Yes}}? || {{Yes}} || {{Yes}}? || {{Yes}} || {{Yes}}
|-
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || freesmartphone.org
|-
| [[Java]] || Jalimo || Jalimo || Jalimo || ? || ? || {{Yes}} (CacaoVM, JamVM)
|-
| [[Python]] || {{Yes}} || {{Yes}} || {{Yes}} || ? || {{Yes}} || {{Yes}}
|-
| [[Mono]] || {{Yes}} (1) || ? || {{Yes}} (1) || ? || ? || {{Yes}} (1)
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters. [[Switching_Keyboards#Matchbox_keyboard|Various fixes available.]]

(3) there is a UI but it crashes the device when used.

(*) unstable

== External links ==

Original distribution descriptions are from Mickey Lauer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].

[[Category:Distributions| ]]
[[Category:Documentation]]

Talk:Rotate

2008-09-08T02:43:47Z

Dewey:

This is a pretty neat little application.

Too bad the screen doesn't recalibrate properly yet. :(

-- Techiem2

It stops working for me after a while. Also, for the freerunner-rotate init script, it might make more sense to put it under the X init scripts (/etc/X11/Xsession.d) instead.

-- Dewey

Dfu-util-windows

2008-09-06T05:58:15Z

Dewey: /* dfu-util for Win32 */

== dfu-util for Win32 ==

{{Note|This has been reported to work on Windows 2000, Windows XP and Windows Vista with the Neo FreeRunner. No reports have been received on whether it works with other versions of Windows or with the Neo 1973. There are some reports that image downloads and uploads are extremely slow for some people. The exact cause of this has not yet been pinpointed.}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. Theoretically, a USB standard-compliant DFU class driver should work, unfortunately, Windows does not come bundled with one. If you do not have a DFU class driver (ie. Windows does not recognize the device in U-Boot mode and pops up the New Device Wizard), the LibUSB-Win32 driver and accompanying INF file for the Neo FreeRunner can be used, this driver can be found in OpenmokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH=" /c/msys/1.0/lib/pkgconfig"

ensuring that the path is accessible from the MSYS shell and points to the pkgconfig files.

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4553)
+++ main.c (working copy)
@@ -26,8 +26,10 @@
#include <getopt.h>
#include <usb.h>
#include <errno.h>
+#ifndef __MINGW32__
#include <byteswap.h>
#include <endian.h>
+#endif

#include "dfu.h"
#include "usb_dfu.h"
@@ -37,6 +39,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +585,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n", usb_strerror());
@@ -700,12 +720,18 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4553)
+++ sam7dfu.c (working copy)
@@ -20,6 +20,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4553)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

check your PKG_CONFIG_PATH (see above) to make sure it is correct, otherwise, you can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: Openmoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Manually using GPRS

2008-08-31T09:12:23Z

Dewey: /* Option 2: With GSM multiplexing and without a GUI */

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

== 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+gitr6fecc78198dd821bbe29efd096bd8fecd855179d-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.'''

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

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>

(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 || 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
|-
| Denmark || Telmore || || wap || must be empty ||
|-
| 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 || ||
|-
| 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]]
|-
| 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:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Manually using GPRS

2008-08-29T23:03:24Z

Dewey: /* Option 1: With GSM multiplexing and with a GUI */

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

== 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+gitr6fecc78198dd821bbe29efd096bd8fecd855179d-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 =

'''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.'''

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

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>

(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 || 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
|-
| Denmark || Telmore || || wap || must be empty ||
|-
| 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 || ||
|-
| 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]]
|-
| 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:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Pidgin

2008-08-29T22:31:48Z

Dewey:

[http://pidgin.im/ Pidgin] can be installed from the Angstrom Repositories (see [[Repositories]]).

opkg install pidgin

There are various plugins for pidgin provided by libpurple that can be installed to connect to MSN (libpurple-protocol-msn), Yahoo (libpurple-protocol-yahoo), etc.

Do a

opkg list | grep libpurple-protocol

to see a full list.

You can have instant messaging on the go through [[GPRS]].

Pidgin

2008-08-29T22:18:45Z

Dewey: New page: [http://pidgin.im/ Pidgin] can be installed from the Angstrom Repositories (see Repositories). opkg install pidgin There are various plugins for pidgin provided by libpurple that c...

Tethering

2008-08-29T18:54:50Z

Dewey:

Once you successfully connect to your network operator (see [[Manually_using_GPRS]]), you can start sharing your data plan with your computer through USB or Bluetooth networking. The following describes how you can do so through USB networking.

== Setting up your computer's network settings ==

I find it useful to have my computer automatically acquire it's network address, mask, gateway, and DNS servers from the FreeRunner instead of manually setting these up. In order to this, I installed busybox-udhcpd from the Angstrom repositories onto my FreeRunner (see [[Repositories]])

opkg install busybox-udhcpd

Once it is installed, it needs to be configured. Edit the /etc/udhcpd.conf file. Mine looks like this:

<pre>
# Sample udhcpd configuration file (/etc/udhcpd.conf)

# The start and end of the IP lease block

start 192.168.0.200 #default: 192.168.0.20
end 192.168.0.200 #default: 192.168.0.254

# The interface that udhcpd will use

interface usb0 #default: eth0

# The maximim number of leases (includes addressesd reserved
# by OFFER's, DECLINE's, and ARP conficts

#max_leases 254 #default: 254

# If remaining is true (default), udhcpd will store the time
# remaining for each lease in the udhcpd leases file. This is
# for embedded systems that cannot keep time between reboots.
# If you set remaining to no, the absolute time that the lease
# expires at will be stored in the dhcpd.leases file.

#remaining yes #default: yes

# The time period at which udhcpd will write out a dhcpd.leases
# file. If this is 0, udhcpd will never automatically write a
# lease file. (specified in seconds)

#auto_time 7200 #default: 7200 (2 hours)

# The amount of time that an IP will be reserved (leased) for if a
# DHCP decline message is received (seconds).

#decline_time 3600 #default: 3600 (1 hour)

# The amount of time that an IP will be reserved (leased) for if an
# ARP conflct occurs. (seconds

#conflict_time 3600 #default: 3600 (1 hour)

# How long an offered address is reserved (leased) in seconds

#offer_time 60 #default: 60 (1 minute)

# If a lease to be given is below this value, the full lease time is
# instead used (seconds).

#min_lease 60 #defult: 60

# The location of the leases file

#lease_file /var/lib/misc/udhcpd.leases #defualt: /var/lib/misc/udhcpd.
leases

# The location of the pid file
#pidfile /var/run/udhcpd.pid #default: /var/run/udhcpd.pid

# Everytime udhcpd writes a leases file, the below script will be called.
# Useful for writing the lease file to flash every few hours.

#notify_file #default: (no script)

#notify_file dumpleases # <--- usefull for debugging

# The following are bootp specific options, setable by udhcpd.

#siaddr 192.168.0.22 #default: 0.0.0.0

#sname zorak #default: (none)

#boot_file /var/nfs_root #default: (none)

# The remainer of options are DHCP options and can be specifed with the
# keyword 'opt' or 'option'. If an option can take multiple items, such
# as the dns option, they can be listed on the same line, or multiple
# lines. The only option with a default is 'lease'.

#Examles
opt dns 192.168.0.202 <your APN's DNS server>
option subnet 255.255.255.0
opt router 192.168.0.202
opt wins 192.168.0.202
#option dns 129.219.13.81 # appened to above DNS servers for a total of 3
option domain local
option lease 864000 # 10 days of seconds

# Currently supported options, for more info, see options.c
#subnet
#timezone
#router
#timesvr
#namesvr
#dns
#logsvr
#cookiesvr
#lprsvr
#bootsize
#domain
#swapsvr
#rootpath
#ipttl
#mtu
#broadcast
#wins
#lease
#ntpsrv
#tftp
#bootfile
</pre>

Notice that I set the start and end of the IP lease block to 192.168.0.200. If you follow the instructions at [[USB Networking]], this is the address that it assumes the host to be and the /etc/resolv.conf file points to this address to allow name resolution from your phone.

The interface in this case is usb0. This will have to be set differently if you are using Bluetooth.

The dns is set to the FreeRunner's address, as well as my network operator's DNS server address. You don't have to use your network operator's DNS address if you can find a caching nameserver for the FreeRunner.

The router is set to the FreeRunner.

== Turning your FreeRunner into a Network Address Translation (NAT) gateway ==

I set up my FreeRunner so that it acts as a NAT gateway so that all traffic that goes to my network operator appears to originate from the phone. I installed iptables to accomplish this:

opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat

Once that is installed, I have the following script named firewall.sh that I use to set up the NAT once connected to the GPRS network:

<pre>
#!/bin/sh
IPTABLES='/usr/sbin/iptables'

# Set interface values
EXTIF='ppp0'
INTIF='usb0'

# enable ip forwarding in the kernel
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

# flush rules and delete chains
$IPTABLES -F
$IPTABLES -X

#Enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

#Forward LAN traffic from LAN $INTIF to Internet $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

#Allowing access to the SSH server"
#$IPTABLES -A INPUT --protocol tcp --dport 22 -j ACCEPT

#Allowing access to the HTTP server"
#$IPTABLES -A INPUT --protocol tcp --dport 80 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP
</pre>

so once connected through GPRS, I run:

./firewall.sh

and then you should be able to connect to the internet from your computer!

Of course this also works when sharing your WLAN connection. Just set EXTIF to eth0.

== See also ==
* [[Manually_using_GPRS]]

[[Category:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Manually using GPRS

2008-08-29T18:50:45Z

Dewey: /* Sharing the GPRS connection with a computer */

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

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 found here:

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

In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found 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 =

'''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.'''

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

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>

(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 || 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
|-
| Denmark || Telmore || || wap || must be empty ||
|-
| 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 || ||
|-
| 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]]
|-
| 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:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Tethering

2008-08-29T18:50:37Z

Dewey: New page: = Tethering = Once you successfully connect to your network operator (see Manually_using_GPRS), you can start sharing your data plan with your computer through USB or Bluetooth networ...

= Tethering =

Once you successfully connect to your network operator (see [[Manually_using_GPRS]]), you can start sharing your data plan with your computer through USB or Bluetooth networking. The following describes how you can do so through USB networking.

== Setting up your computer's network settings ==

I find it useful to have my computer automatically acquire it's network address, mask, gateway, and DNS servers from the FreeRunner instead of manually setting these up. In order to this, I installed busybox-udhcpd from the Angstrom repositories onto my FreeRunner (see [[Repositories]])

opkg install busybox-udhcpd

Once it is installed, it needs to be configured. Edit the /etc/udhcpd.conf file. Mine looks like this:

<pre>
# Sample udhcpd configuration file (/etc/udhcpd.conf)

# The start and end of the IP lease block

start 192.168.0.200 #default: 192.168.0.20
end 192.168.0.200 #default: 192.168.0.254

# The interface that udhcpd will use

interface usb0 #default: eth0

# The maximim number of leases (includes addressesd reserved
# by OFFER's, DECLINE's, and ARP conficts

#max_leases 254 #default: 254

# If remaining is true (default), udhcpd will store the time
# remaining for each lease in the udhcpd leases file. This is
# for embedded systems that cannot keep time between reboots.
# If you set remaining to no, the absolute time that the lease
# expires at will be stored in the dhcpd.leases file.

#remaining yes #default: yes

# The time period at which udhcpd will write out a dhcpd.leases
# file. If this is 0, udhcpd will never automatically write a
# lease file. (specified in seconds)

#auto_time 7200 #default: 7200 (2 hours)

# The amount of time that an IP will be reserved (leased) for if a
# DHCP decline message is received (seconds).

#decline_time 3600 #default: 3600 (1 hour)

# The amount of time that an IP will be reserved (leased) for if an
# ARP conflct occurs. (seconds

#conflict_time 3600 #default: 3600 (1 hour)

# How long an offered address is reserved (leased) in seconds

#offer_time 60 #default: 60 (1 minute)

# If a lease to be given is below this value, the full lease time is
# instead used (seconds).

#min_lease 60 #defult: 60

# The location of the leases file

#lease_file /var/lib/misc/udhcpd.leases #defualt: /var/lib/misc/udhcpd.
leases

# The location of the pid file
#pidfile /var/run/udhcpd.pid #default: /var/run/udhcpd.pid

# Everytime udhcpd writes a leases file, the below script will be called.
# Useful for writing the lease file to flash every few hours.

#notify_file #default: (no script)

#notify_file dumpleases # <--- usefull for debugging

# The following are bootp specific options, setable by udhcpd.

#siaddr 192.168.0.22 #default: 0.0.0.0

#sname zorak #default: (none)

#boot_file /var/nfs_root #default: (none)

# The remainer of options are DHCP options and can be specifed with the
# keyword 'opt' or 'option'. If an option can take multiple items, such
# as the dns option, they can be listed on the same line, or multiple
# lines. The only option with a default is 'lease'.

#Examles
opt dns 192.168.0.202 <your APN's DNS server>
option subnet 255.255.255.0
opt router 192.168.0.202
opt wins 192.168.0.202
#option dns 129.219.13.81 # appened to above DNS servers for a total of 3
option domain local
option lease 864000 # 10 days of seconds

# Currently supported options, for more info, see options.c
#subnet
#timezone
#router
#timesvr
#namesvr
#dns
#logsvr
#cookiesvr
#lprsvr
#bootsize
#domain
#swapsvr
#rootpath
#ipttl
#mtu
#broadcast
#wins
#lease
#ntpsrv
#tftp
#bootfile
</pre>

Notice that I set the start and end of the IP lease block to 192.168.0.200. If you follow the instructions at [[USB Networking]], this is the address that it assumes the host to be and the /etc/resolv.conf file points to this address to allow name resolution from your phone.

The interface in this case is usb0. This will have to be set differently if you are using Bluetooth.

The dns is set to the FreeRunner's address, as well as my network operator's DNS server address. You don't have to use your network operator's DNS address if you can find a caching nameserver for the FreeRunner.

The router is set to the FreeRunner.

== Turning your FreeRunner into a Network Address Translation (NAT) gateway ==

I set up my FreeRunner so that it acts as a NAT gateway so that all traffic that goes to my network operator appears to originate from the phone. I installed iptables to accomplish this:

opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat

Once that is installed, I have the following script named firewall.sh that I use to set up the NAT once connected to the GPRS network:

<pre>
#!/bin/sh
IPTABLES='/usr/sbin/iptables'

# Set interface values
EXTIF='ppp0'
INTIF='usb0'

# enable ip forwarding in the kernel
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

# flush rules and delete chains
$IPTABLES -F
$IPTABLES -X

#Enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

#Forward LAN traffic from LAN $INTIF to Internet $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

#Allowing access to the SSH server"
#$IPTABLES -A INPUT --protocol tcp --dport 22 -j ACCEPT

#Allowing access to the HTTP server"
#$IPTABLES -A INPUT --protocol tcp --dport 80 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP
</pre>

so once connected through GPRS, I run:

./firewall.sh

and then you should be able to connect to the internet from your computer!

Of course this also works when sharing your WLAN connection. Just set EXTIF to eth0.

== See also ==
* [[Manually_using_GPRS]]

[[Category:Documentation]]
[[Category:Application Developer]]
[[Category:Guides]]
[[Category:Networking]]

Distributions

2008-08-19T16:11:46Z

Dewey: /* Applications */

{{Languages|Distributions}}

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[Om 2007.1]]
** [[OpenmokoFramework|FSO]]
* Community
** [[SHR]]
* Other
** [[Qtopia]]
** [[Debian]]
</div>
|-
|}<noinclude>[[Category:Templates]]</noinclude>

Openmoko distributions are designed to run on various mobile devices, with the primary aim of Openmoko Inc.'s [[Neo 1973]] and [[Neo FreeRunner]] phones. They are similar to Linux distributions; complete operating systems with user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed.

While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below).

For downloads see [[Latest Images]], for installation instructions see [[Flashing the Neo FreeRunner]].

== About distributions ==

To be technically precise, 2007.2, 2008.8, FSO and SHR of these are not directly independent distributions, but different 'release targets'. They are built out of different branches of the [[OpenEmbedded]] metadistribution source tree, e.g. 2007.2 and 2008.8 are to each other like Ubuntu Gutsy is to Kubuntu Hardy.

One should only use feeds from packages of the same source-branch, else 'stuff will break', similar to like using .debs from Hardy on a Gutsy base system. Also note that there is NO supported upgrade path between these at the moment, thus updating by changing the feeds will most likely end in broken packages or even a unbootable system. Thus please always use [[dfu-util]] to switch between the different 'distributions' for now or install them in a dual-boot setup (e.g. via sdcard or NFS).

== Openmoko Inc. driven release targets ==

=== Om 2007.2 (GTK) ===

[[Om 2007.2]] is for people who are familiar with the [http://www.gnome.org/mobile/ GNOME Mobile] initiative and who want to write applications that run on multiple devices running (parts of) GNOME Mobile. This includes Maemo, which runs on the Nokia Internet Tablets. The strength of the GTK+ stack is a UI and programming environment similar to what you run on your Linux desktop, if you’re into GNOME. The GTK+ has PIM applications based on the Evolution Data Server and runs the gsmd phone server. Although you can use them, the applications are still pretty rough und unfinished. Some people have problems with the stability of the phone server.

* [[Om 2007.2]]
* Availabilty: [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds
* [[Downloads#Openmoko_2007.2_images_.28GTK.29|Download]]
* Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone] and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
This is the base-system which is installed on Freerunner when it leaves the factory.

2007.2 development driven by openmoko inc. has basically stopped and resources are allocated in favor of 2008.8, while the community currently does the effort to 'rescue' the 2007.2 telephony apps and pull them to the future middleware from FSO (see SHR).
thus patches are still welcome, especially if they help development of SHR.

=== Om 2008.8 (ASU, April/August Software Update) ===

Om 2008.8 has been started to integrate the [http://trolltech.com/products/qtopia Qtopia] stack - on X11 - with a new set of graphically pleasing applications based on the Enlightenment Foundation Libraries. ASU is the internal name and is known as Om 2008.8 upon its release on August 8, 2008. Qtopia is a more mature product than the GNOME Mobile stack and you can expect all the standard feature phone applications to work in a solid way. It uses the Qtopia phone server. Since - contrary to standard Qtopia - it does not directly use the framebuffer, non-Qt applications can safely share the screen with Qt applications.

* [[Om2008.8|Om 2008.8]]
* [[Downloads#Openmoko_2008.8_images_.28ASU.29|Download]]

=== FSO - freesmartphone.org ===

FSO has been started to overcome the deficiencies both of the 2007.2 and the 2008.8 stack, namely to come up with an extensible framework that gives developers the infrastructure they need to create solid and exciting software products based on the Openmoko platform. An infrastructure that supports competing UIs while we can collaborate on developing services, making the framework strong . Here, the focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. People report that despite its infancy, e.g. the phone server part in FSO is already more solid than anywhere else.

It is not really intended as future release-target, but used as a 'vessel' or 'container' for the development and testing of the new, future middleware. 
The applications installed are intended as test-tools for the new middleware and not as fully featured, end user oriented applications. (even if it looks that way sometimes)

* [[FSO]]
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]
* [http://downloads.openmoko.org/framework/milestone2/ Download milestone 2]
* [http://freesmartphone.org freesmartphone.org]
* [http://shr.bearstech.com/ fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

== Openmoko Community driven release targets ==

=== SHR - Stable Hybrid Release ===

Stable Hybrid Release is a combination of the middleware from FSO, some of the 2007.2 GTK software (telephony-ui, pim), and Om2008.8 that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.

* [[Stable Hybrid Release]]

== Non-Openmoko distributions ==

These are not Openmoko (and OE) based distributions. These are an alternatives you can run on your Openmoko phones.

=== Qtopia ===

The Qtopia distribution from [http://www.trolltech.com Trolltech], it aims to provide a ready-to use image for Openmoko devices.

* [[Qtopia]]
* Download: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]

=== Debian ===

Debian Linux, the whole distribution, on a mobile phone.

* [[Debian]]

== Features by distribution/release target ==

=== Connectivity ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Telephony || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| SMS || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[GPRS]] || Not through UI || Not through UI || Not through UI || N/A || No (3) || style="background:lightgreen;" | Yes
|-
| WiFi || style="background:lightgreen;" | Yes || Not through UI || style="background:lightgreen;" | Yes (*) || N/A || style="background:lightgreen;" | Yes ||style="background:lightgreen;" | Yes
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || style="background:lightgreen;" | Yes
|-
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || No || style="background:lightgreen;" | Yes
|-
|}

=== User Interaction ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Stylus friendly || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Finger friendly || Partially || Partially || Partially || N/A || style="background:lightgreen;" | Yes || No
|-
| Accelerometer || No || No || style="background:lightgreen;" | Yes[[Gestures|(1)]] || N/A || No || No
|-
|}

=== Applications ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Terminal || Basic (2) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Phonebook || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Web Browser || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes (1) || ? || No || style="background:lightgreen;" | Yes
|-
| Mail Client || ? || ? || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| XMPP Client || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes [[IM#Implementation_Recommendations|(1)]] || ? || No || style="background:lightgreen;" | Yes
|-
| Media Player || ? || ? || ? || ? || ? || ?
|-
|}

=== Toolkits / Runtimes ===
{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| GTK+ || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes
|-
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || freesmartphone.org
|-
| [[Java]] || Jalimo || Jalimo || Jalimo || ? || ? || No
|-
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[Mono]] || style="background:lightgreen;" | Yes(1) || ? || style="background:lightgreen;" | Yes(1) || ? || ? || ?
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters (unless you [[Switching_Keyboards#Matchbox_keyboard|install matchbox-keyboard]])

(3) there is a UI but it crashes the device when used.

(*) unstable

== External links ==

Original distribution descriptions are from Mickey Lauer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].

[[Category:Distributions| ]]
[[Category:Documentation]]

Distributions

2008-08-19T16:06:56Z

Dewey: /* Connectivity */

{{Languages|Distributions}}

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[Om 2007.1]]
** [[OpenmokoFramework|FSO]]
* Community
** [[SHR]]
* Other
** [[Qtopia]]
** [[Debian]]
</div>
|-
|}<noinclude>[[Category:Templates]]</noinclude>

Openmoko distributions are designed to run on various mobile devices, with the primary aim of Openmoko Inc.'s [[Neo 1973]] and [[Neo FreeRunner]] phones. They are similar to Linux distributions; complete operating systems with user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed.

While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below).

For downloads see [[Latest Images]], for installation instructions see [[Flashing the Neo FreeRunner]].

== About distributions ==

To be technically precise, 2007.2, 2008.8, FSO and SHR of these are not directly independent distributions, but different 'release targets'. They are built out of different branches of the [[OpenEmbedded]] metadistribution source tree, e.g. 2007.2 and 2008.8 are to each other like Ubuntu Gutsy is to Kubuntu Hardy.

One should only use feeds from packages of the same source-branch, else 'stuff will break', similar to like using .debs from Hardy on a Gutsy base system. Also note that there is NO supported upgrade path between these at the moment, thus updating by changing the feeds will most likely end in broken packages or even a unbootable system. Thus please always use [[dfu-util]] to switch between the different 'distributions' for now or install them in a dual-boot setup (e.g. via sdcard or NFS).

== Openmoko Inc. driven release targets ==

=== Om 2007.2 (GTK) ===

[[Om 2007.2]] is for people who are familiar with the [http://www.gnome.org/mobile/ GNOME Mobile] initiative and who want to write applications that run on multiple devices running (parts of) GNOME Mobile. This includes Maemo, which runs on the Nokia Internet Tablets. The strength of the GTK+ stack is a UI and programming environment similar to what you run on your Linux desktop, if you’re into GNOME. The GTK+ has PIM applications based on the Evolution Data Server and runs the gsmd phone server. Although you can use them, the applications are still pretty rough und unfinished. Some people have problems with the stability of the phone server.

* [[Om 2007.2]]
* Availabilty: [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds
* [[Downloads#Openmoko_2007.2_images_.28GTK.29|Download]]
* Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone] and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
This is the base-system which is installed on Freerunner when it leaves the factory.

2007.2 development driven by openmoko inc. has basically stopped and resources are allocated in favor of 2008.8, while the community currently does the effort to 'rescue' the 2007.2 telephony apps and pull them to the future middleware from FSO (see SHR).
thus patches are still welcome, especially if they help development of SHR.

=== Om 2008.8 (ASU, April/August Software Update) ===

Om 2008.8 has been started to integrate the [http://trolltech.com/products/qtopia Qtopia] stack - on X11 - with a new set of graphically pleasing applications based on the Enlightenment Foundation Libraries. ASU is the internal name and is known as Om 2008.8 upon its release on August 8, 2008. Qtopia is a more mature product than the GNOME Mobile stack and you can expect all the standard feature phone applications to work in a solid way. It uses the Qtopia phone server. Since - contrary to standard Qtopia - it does not directly use the framebuffer, non-Qt applications can safely share the screen with Qt applications.

* [[Om2008.8|Om 2008.8]]
* [[Downloads#Openmoko_2008.8_images_.28ASU.29|Download]]

=== FSO - freesmartphone.org ===

FSO has been started to overcome the deficiencies both of the 2007.2 and the 2008.8 stack, namely to come up with an extensible framework that gives developers the infrastructure they need to create solid and exciting software products based on the Openmoko platform. An infrastructure that supports competing UIs while we can collaborate on developing services, making the framework strong . Here, the focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. People report that despite its infancy, e.g. the phone server part in FSO is already more solid than anywhere else.

It is not really intended as future release-target, but used as a 'vessel' or 'container' for the development and testing of the new, future middleware. 
The applications installed are intended as test-tools for the new middleware and not as fully featured, end user oriented applications. (even if it looks that way sometimes)

* [[FSO]]
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]
* [http://downloads.openmoko.org/framework/milestone2/ Download milestone 2]
* [http://freesmartphone.org freesmartphone.org]
* [http://shr.bearstech.com/ fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

== Openmoko Community driven release targets ==

=== SHR - Stable Hybrid Release ===

Stable Hybrid Release is a combination of the middleware from FSO, some of the 2007.2 GTK software (telephony-ui, pim), and Om2008.8 that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.

* [[Stable Hybrid Release]]

== Non-Openmoko distributions ==

These are not Openmoko (and OE) based distributions. These are an alternatives you can run on your Openmoko phones.

=== Qtopia ===

The Qtopia distribution from [http://www.trolltech.com Trolltech], it aims to provide a ready-to use image for Openmoko devices.

* [[Qtopia]]
* Download: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]

=== Debian ===

Debian Linux, the whole distribution, on a mobile phone.

* [[Debian]]

== Features by distribution/release target ==

=== Connectivity ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Telephony || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| SMS || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[GPRS]] || Not through UI || Not through UI || Not through UI || N/A || No (3) || style="background:lightgreen;" | Yes
|-
| WiFi || style="background:lightgreen;" | Yes || Not through UI || style="background:lightgreen;" | Yes (*) || N/A || style="background:lightgreen;" | Yes ||style="background:lightgreen;" | Yes
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || style="background:lightgreen;" | Yes
|-
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || No || style="background:lightgreen;" | Yes
|-
|}

=== User Interaction ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Stylus friendly || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Finger friendly || Partially || Partially || Partially || N/A || style="background:lightgreen;" | Yes || No
|-
| Accelerometer || No || No || style="background:lightgreen;" | Yes[[Gestures|(1)]] || N/A || No || No
|-
|}

=== Applications ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Terminal || Basic (2) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Phonebook || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Web Browser || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes (1) || ? || No || style="background:lightgreen;" | Yes
|-
| Mail Client || ? || ? || ? || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| XMPP Client || style="background:lightgreen;" | Yes (1) || ? || ? || ? || No || style="background:lightgreen;" | Yes
|-
| Media Player || ? || ? || ? || ? || ? || ?
|-
|}

=== Toolkits / Runtimes ===
{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| GTK+ || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes
|-
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || freesmartphone.org
|-
| [[Java]] || Jalimo || Jalimo || Jalimo || ? || ? || No
|-
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[Mono]] || style="background:lightgreen;" | Yes(1) || ? || style="background:lightgreen;" | Yes(1) || ? || ? || ?
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters (unless you [[Switching_Keyboards#Matchbox_keyboard|install matchbox-keyboard]])

(3) there is a UI but it crashes the device when used.

(*) unstable

== External links ==

Original distribution descriptions are from Mickey Lauer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].

[[Category:Distributions| ]]
[[Category:Documentation]]

Distributions

2008-08-19T16:05:55Z

Dewey: /* User Interaction */

{{Languages|Distributions}}

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[Om 2007.1]]
** [[OpenmokoFramework|FSO]]
* Community
** [[SHR]]
* Other
** [[Qtopia]]
** [[Debian]]
</div>
|-
|}<noinclude>[[Category:Templates]]</noinclude>

Openmoko distributions are designed to run on various mobile devices, with the primary aim of Openmoko Inc.'s [[Neo 1973]] and [[Neo FreeRunner]] phones. They are similar to Linux distributions; complete operating systems with user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed.

While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below).

For downloads see [[Latest Images]], for installation instructions see [[Flashing the Neo FreeRunner]].

== About distributions ==

To be technically precise, 2007.2, 2008.8, FSO and SHR of these are not directly independent distributions, but different 'release targets'. They are built out of different branches of the [[OpenEmbedded]] metadistribution source tree, e.g. 2007.2 and 2008.8 are to each other like Ubuntu Gutsy is to Kubuntu Hardy.

One should only use feeds from packages of the same source-branch, else 'stuff will break', similar to like using .debs from Hardy on a Gutsy base system. Also note that there is NO supported upgrade path between these at the moment, thus updating by changing the feeds will most likely end in broken packages or even a unbootable system. Thus please always use [[dfu-util]] to switch between the different 'distributions' for now or install them in a dual-boot setup (e.g. via sdcard or NFS).

== Openmoko Inc. driven release targets ==

=== Om 2007.2 (GTK) ===

[[Om 2007.2]] is for people who are familiar with the [http://www.gnome.org/mobile/ GNOME Mobile] initiative and who want to write applications that run on multiple devices running (parts of) GNOME Mobile. This includes Maemo, which runs on the Nokia Internet Tablets. The strength of the GTK+ stack is a UI and programming environment similar to what you run on your Linux desktop, if you’re into GNOME. The GTK+ has PIM applications based on the Evolution Data Server and runs the gsmd phone server. Although you can use them, the applications are still pretty rough und unfinished. Some people have problems with the stability of the phone server.

* [[Om 2007.2]]
* Availabilty: [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds
* [[Downloads#Openmoko_2007.2_images_.28GTK.29|Download]]
* Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone] and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
This is the base-system which is installed on Freerunner when it leaves the factory.

2007.2 development driven by openmoko inc. has basically stopped and resources are allocated in favor of 2008.8, while the community currently does the effort to 'rescue' the 2007.2 telephony apps and pull them to the future middleware from FSO (see SHR).
thus patches are still welcome, especially if they help development of SHR.

=== Om 2008.8 (ASU, April/August Software Update) ===

Om 2008.8 has been started to integrate the [http://trolltech.com/products/qtopia Qtopia] stack - on X11 - with a new set of graphically pleasing applications based on the Enlightenment Foundation Libraries. ASU is the internal name and is known as Om 2008.8 upon its release on August 8, 2008. Qtopia is a more mature product than the GNOME Mobile stack and you can expect all the standard feature phone applications to work in a solid way. It uses the Qtopia phone server. Since - contrary to standard Qtopia - it does not directly use the framebuffer, non-Qt applications can safely share the screen with Qt applications.

* [[Om2008.8|Om 2008.8]]
* [[Downloads#Openmoko_2008.8_images_.28ASU.29|Download]]

=== FSO - freesmartphone.org ===

FSO has been started to overcome the deficiencies both of the 2007.2 and the 2008.8 stack, namely to come up with an extensible framework that gives developers the infrastructure they need to create solid and exciting software products based on the Openmoko platform. An infrastructure that supports competing UIs while we can collaborate on developing services, making the framework strong . Here, the focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. People report that despite its infancy, e.g. the phone server part in FSO is already more solid than anywhere else.

It is not really intended as future release-target, but used as a 'vessel' or 'container' for the development and testing of the new, future middleware. 
The applications installed are intended as test-tools for the new middleware and not as fully featured, end user oriented applications. (even if it looks that way sometimes)

* [[FSO]]
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]
* [http://downloads.openmoko.org/framework/milestone2/ Download milestone 2]
* [http://freesmartphone.org freesmartphone.org]
* [http://shr.bearstech.com/ fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

== Openmoko Community driven release targets ==

=== SHR - Stable Hybrid Release ===

Stable Hybrid Release is a combination of the middleware from FSO, some of the 2007.2 GTK software (telephony-ui, pim), and Om2008.8 that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.

* [[Stable Hybrid Release]]

== Non-Openmoko distributions ==

These are not Openmoko (and OE) based distributions. These are an alternatives you can run on your Openmoko phones.

=== Qtopia ===

The Qtopia distribution from [http://www.trolltech.com Trolltech], it aims to provide a ready-to use image for Openmoko devices.

* [[Qtopia]]
* Download: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]

=== Debian ===

Debian Linux, the whole distribution, on a mobile phone.

* [[Debian]]

== Features by distribution/release target ==

=== Connectivity ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Telephony || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| SMS || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| GPRS || Not through UI || Not through UI || Not through UI || N/A || No (3) || style="background:lightgreen;" | Yes
|-
| WiFi || style="background:lightgreen;" | Yes || Not through UI || style="background:lightgreen;" | Yes (*) || N/A || style="background:lightgreen;" | Yes ||style="background:lightgreen;" | Yes
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || style="background:lightgreen;" | Yes
|-
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || No || style="background:lightgreen;" | Yes
|-
|}

=== User Interaction ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Stylus friendly || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Finger friendly || Partially || Partially || Partially || N/A || style="background:lightgreen;" | Yes || No
|-
| Accelerometer || No || No || style="background:lightgreen;" | Yes[[Gestures|(1)]] || N/A || No || No
|-
|}

=== Applications ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Terminal || Basic (2) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Phonebook || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Web Browser || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes (1) || ? || No || style="background:lightgreen;" | Yes
|-
| Mail Client || ? || ? || ? || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| XMPP Client || style="background:lightgreen;" | Yes (1) || ? || ? || ? || No || style="background:lightgreen;" | Yes
|-
| Media Player || ? || ? || ? || ? || ? || ?
|-
|}

=== Toolkits / Runtimes ===
{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| GTK+ || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes
|-
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || freesmartphone.org
|-
| [[Java]] || Jalimo || Jalimo || Jalimo || ? || ? || No
|-
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[Mono]] || style="background:lightgreen;" | Yes(1) || ? || style="background:lightgreen;" | Yes(1) || ? || ? || ?
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters (unless you [[Switching_Keyboards#Matchbox_keyboard|install matchbox-keyboard]])

(3) there is a UI but it crashes the device when used.

(*) unstable

== External links ==

Original distribution descriptions are from Mickey Lauer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].

[[Category:Distributions| ]]
[[Category:Documentation]]

Distributions

2008-08-19T16:04:22Z

Dewey: /* Toolkits / Runtimes */

{{Languages|Distributions}}

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[Om 2007.1]]
** [[OpenmokoFramework|FSO]]
* Community
** [[SHR]]
* Other
** [[Qtopia]]
** [[Debian]]
</div>
|-
|}<noinclude>[[Category:Templates]]</noinclude>

Openmoko distributions are designed to run on various mobile devices, with the primary aim of Openmoko Inc.'s [[Neo 1973]] and [[Neo FreeRunner]] phones. They are similar to Linux distributions; complete operating systems with user applications. You can install any of them on your phone or even have a multiboot system with two distributions installed.

While the Openmoko distributions will run on [[Supported devices|other mobile devices]] too, some other software distributions will also run on the Openmoko Inc. phones (see below).

For downloads see [[Latest Images]], for installation instructions see [[Flashing the Neo FreeRunner]].

== About distributions ==

To be technically precise, 2007.2, 2008.8, FSO and SHR of these are not directly independent distributions, but different 'release targets'. They are built out of different branches of the [[OpenEmbedded]] metadistribution source tree, e.g. 2007.2 and 2008.8 are to each other like Ubuntu Gutsy is to Kubuntu Hardy.

One should only use feeds from packages of the same source-branch, else 'stuff will break', similar to like using .debs from Hardy on a Gutsy base system. Also note that there is NO supported upgrade path between these at the moment, thus updating by changing the feeds will most likely end in broken packages or even a unbootable system. Thus please always use [[dfu-util]] to switch between the different 'distributions' for now or install them in a dual-boot setup (e.g. via sdcard or NFS).

== Openmoko Inc. driven release targets ==

=== Om 2007.2 (GTK) ===

[[Om 2007.2]] is for people who are familiar with the [http://www.gnome.org/mobile/ GNOME Mobile] initiative and who want to write applications that run on multiple devices running (parts of) GNOME Mobile. This includes Maemo, which runs on the Nokia Internet Tablets. The strength of the GTK+ stack is a UI and programming environment similar to what you run on your Linux desktop, if you’re into GNOME. The GTK+ has PIM applications based on the Evolution Data Server and runs the gsmd phone server. Although you can use them, the applications are still pretty rough und unfinished. Some people have problems with the stability of the phone server.

* [[Om 2007.2]]
* Availabilty: [http://buildhost.openmoko.org/daily/ Official Buildhost] and [[MokoMakefile]] support for development builds
* [[Downloads#Openmoko_2007.2_images_.28GTK.29|Download]]
* Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone] and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
This is the base-system which is installed on Freerunner when it leaves the factory.

2007.2 development driven by openmoko inc. has basically stopped and resources are allocated in favor of 2008.8, while the community currently does the effort to 'rescue' the 2007.2 telephony apps and pull them to the future middleware from FSO (see SHR).
thus patches are still welcome, especially if they help development of SHR.

=== Om 2008.8 (ASU, April/August Software Update) ===

Om 2008.8 has been started to integrate the [http://trolltech.com/products/qtopia Qtopia] stack - on X11 - with a new set of graphically pleasing applications based on the Enlightenment Foundation Libraries. ASU is the internal name and is known as Om 2008.8 upon its release on August 8, 2008. Qtopia is a more mature product than the GNOME Mobile stack and you can expect all the standard feature phone applications to work in a solid way. It uses the Qtopia phone server. Since - contrary to standard Qtopia - it does not directly use the framebuffer, non-Qt applications can safely share the screen with Qt applications.

* [[Om2008.8|Om 2008.8]]
* [[Downloads#Openmoko_2008.8_images_.28ASU.29|Download]]

=== FSO - freesmartphone.org ===

FSO has been started to overcome the deficiencies both of the 2007.2 and the 2008.8 stack, namely to come up with an extensible framework that gives developers the infrastructure they need to create solid and exciting software products based on the Openmoko platform. An infrastructure that supports competing UIs while we can collaborate on developing services, making the framework strong . Here, the focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. People report that despite its infancy, e.g. the phone server part in FSO is already more solid than anywhere else.

It is not really intended as future release-target, but used as a 'vessel' or 'container' for the development and testing of the new, future middleware. 
The applications installed are intended as test-tools for the new middleware and not as fully featured, end user oriented applications. (even if it looks that way sometimes)

* [[FSO]]
* [http://trac.freesmartphone.org:8000/trac-example Development tracker]
* [http://downloads.openmoko.org/framework/milestone2/ Download milestone 2]
* [http://freesmartphone.org freesmartphone.org]
* [http://shr.bearstech.com/ fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

== Openmoko Community driven release targets ==

=== SHR - Stable Hybrid Release ===

Stable Hybrid Release is a combination of the middleware from FSO, some of the 2007.2 GTK software (telephony-ui, pim), and Om2008.8 that provides all of the functionality of the 2007.2 software, but with the stability of the FSO.

* [[Stable Hybrid Release]]

== Non-Openmoko distributions ==

These are not Openmoko (and OE) based distributions. These are an alternatives you can run on your Openmoko phones.

=== Qtopia ===

The Qtopia distribution from [http://www.trolltech.com Trolltech], it aims to provide a ready-to use image for Openmoko devices.

* [[Qtopia]]
* Download: [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Qtopia.net]

=== Debian ===

Debian Linux, the whole distribution, on a mobile phone.

* [[Debian]]

== Features by distribution/release target ==

=== Connectivity ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Telephony || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| SMS || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| GPRS || Not through UI || Not through UI || Not through UI || N/A || No (3) || style="background:lightgreen;" | Yes
|-
| WiFi || style="background:lightgreen;" | Yes || Not through UI || style="background:lightgreen;" | Yes (*) || N/A || style="background:lightgreen;" | Yes ||style="background:lightgreen;" | Yes
|-
| VoIP || ?? || ?? || ?? || ?? || ?? || style="background:lightgreen;" | Yes
|-
| Bluetooth || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| GPS || style="background:lightgreen;" | Yes (1) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || No || style="background:lightgreen;" | Yes
|-
|}

=== User Interaction ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Stylus friendly || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Finger friendly || Partially || Partially || Partially || N/A || style="background:lightgreen;" | Yes || No
|-
| Accelerometer || No || No || No || N/A || No || No
|-
|}

=== Applications ===

{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| Terminal || Basic (2) || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes (1) || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| PIM || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Phonebook || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Dialer || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || N/A || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Web Browser || style="background:lightgreen;" | Yes (1) || ? || style="background:lightgreen;" | Yes (1) || ? || No || style="background:lightgreen;" | Yes
|-
| Mail Client || ? || ? || ? || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| XMPP Client || style="background:lightgreen;" | Yes (1) || ? || ? || ? || No || style="background:lightgreen;" | Yes
|-
| Media Player || ? || ? || ? || ? || ? || ?
|-
|}

=== Toolkits / Runtimes ===
{| border=1 width=100% |
| width=14%| || width=14%|2007.2 || width=14%|FSO || width=14%|Om2008.8 || width=14%|SHR || width=14%|Qtopia || Debian
|-
| GTK+ || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || No || style="background:lightgreen;" | Yes
|-
| QT/Qtopia || No || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| Middleware || gsmd/neod || freesmartphone.org || qtopia-x11 || freesmartphone.org || qtopia || freesmartphone.org
|-
| [[Java]] || Jalimo || Jalimo || Jalimo || ? || ? || No
|-
| [[Python]] || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes || ? || style="background:lightgreen;" | Yes || style="background:lightgreen;" | Yes
|-
| [[Mono]] || style="background:lightgreen;" | Yes(1) || ? || style="background:lightgreen;" | Yes(1) || ? || ? || ?
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters (unless you [[Switching_Keyboards#Matchbox_keyboard|install matchbox-keyboard]])

(3) there is a UI but it crashes the device when used.

(*) unstable

== External links ==

Original distribution descriptions are from Mickey Lauer's [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!].

[[Category:Distributions| ]]
[[Category:Documentation]]

Om 2008 Guide

2008-08-19T06:37:08Z

Dewey: /* Things to know */

This documents quickly some key useability bits about [[Om 2008.8]] and initial setup.

=== Interface ===

'''New Keyboard'''

Sliding your finger left is backspace.

Sliding your finger right is space.

Sliding your finger up/down changes between lowercase/uppercase/numbers/special characters.

Hovering over a letter for more than 2 seconds activates [[Om2008.8_Keyboard#Keyboard_Zoom|zoom mode]], allowing you to type specific letters without prediction.

More details at : [[Om2008.8 Keyboard]]

'''Installer'''

The button to run the Installer is now on the bottom of the homescreen.
The plus signs are placeholders for the graphical buttons to be added later.

'''Top Menu'''

The top menu is now your task switcher and is activated by touching the down arrow.
Press "remove" to close currently focused application.

=== Things to know ===

''' Commands '''

*'''"ifconfig"''' - Displays network information.

*'''"opkg update"''' - Updates list of available software.

*'''"opkg install"''' - Install software.

*'''"opkg upgrade"''' - Updates your software.

*'''"killall packagekitd"''' - Quits any package manager which could be running. (Run this command if you get the "Could not obtain administrative lock" error message while running opkg commands)

*'''"shutdown -r now"''' or '''"reboot"'''- Reboots your phone.

''' Configuring Om 2008.8 '''

Follow this [[http://support.microsoft.com/kb/306126 guide (Windows Users)]]to share your internet with your phone.

To share your internet connection on a Linux host follow this [[USB_Networking|Guide]]

*If you are also behind a router you may have to change your LAN IP range in your router to avoid using 192.168.0.* as this is the same IP range as what your phone and ICS uses. (If you don't there will be an IP conflict)

After you install and run [[http://wiki.openmoko.org/wiki/Om2008.8#Download Om 2008.8 ]] for the first time you have to restart to get the USB working. Once you have done that you have to ssh into your phone (192.168.0.202) to edit your /etc/network/interfaces so you can access the internet through USB to install software and updates.

Edit the USB section to look like this:

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
auto usb0
iface usb0 inet static
address 192.168.0.202
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.1
up echo nameserver 208.67.222.222 >/etc/resolv.conf
up echo nameserver 208.67.220.220 >/etc/resolv.conf
#up echo nameserver 192.168.0.200 >/etc/resolv.conf

Now edit the Multiverse repository (/etc/opkg/Multiverse-feed.conf) to fix a typo: Remove the duplicate "/" before Multiverse.

Create a file named zecke.conf and paste this into it to get the latest unofficial updates. (Temporary Repository)

src/gz zecke-all http://people.openmoko.org/~zecke/om2008.8-dev/all
src/gz zecke-arm http://people.openmoko.org/~zecke/om2008.8-dev/armv4t
src/gz zecke-i686 http://people.openmoko.org/~zecke/om2008.8-dev/i686
src/gz zecke-neo http://people.openmoko.org/~zecke/om2008.8-dev/neo1973
src/gz zecke-gta02 http://people.openmoko.org/~zecke/om2008.8-dev/om-gta02

(Restart your phone)

Now that you are able to install software, It is a good time to install "illume-config" to can gain access to more advanced power management features and to change the look of the GUI through the wrench that will now appear in the top bar. (Restart your phone)

The Media Player is basically useless due to the default theme. To install with a better theme run:

opkg install openmoko-mediaplayer2
wget http://abraxa.dyndns.org:81/random/openmoko-mediaplayer-theme.tar.bz2
tar xjf openmoko-mediaplayer-theme.tar.bz2 -C /usr/share/themes/Moko/gtk-2.0
rm openmoko-mediaplayer-theme.tar.bz2

''' Bugs/Fixes '''

*The Media Player is basically unusable because of the skin. And is also very buggy.
*Battery meter always says its charging. Installing a terminal and running "apm" will display the proper battery status.

*Your phone will go into standby after 30 seconds EVEN when connected to your computer or wall charger. (Disable this under the settings menu)

*The wifi doesn't work too well right now.

*Accelerometers have alpha support via [[Gestures]]

*If you let the battery completely drain you will have problems booting it up. Plug it into the wall charger for a few hours and then plug it into your computer and press power.

*Your have to install "illume-config" to have more control over power management, scrolling speeds, keyboard options, and to change how the interface looks.

*Some software that you install by command-line may appear in in the settings menu (wrench) that you unlock after installing "illume-config".

[[Category:Om 2008.8]]

Manually using GPRS

2008-08-19T04:14:52Z

Dewey:

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

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 found here:

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

In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found 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: Without GSM multiplexing and without a GUI =

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>

(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 || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || 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
|-
| 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 pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| 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 || ||
|-
| Sweden || Parlino || || internet.parlino.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 =

Once you successfully connect to your network operator, you can start sharing your data plan with your computer through USB or Bluetooth networking. The following describes how you can do so through USB networking.

== Setting up your computer's network settings ==

I find it useful to have my computer automatically acquire it's network address, mask, gateway, and DNS servers from the FreeRunner instead of manually setting these up. In order to this, I installed busybox-udhcpd from the Angstrom repositories (see [[Repositories]])

opkg install busybox-udhcpd

Once it is installed, it needs to be configured. Edit the /etc/udhcpd.conf file. Mine looks like this:

<pre>
# Sample udhcpd configuration file (/etc/udhcpd.conf)

# The start and end of the IP lease block

start 192.168.0.200 #default: 192.168.0.20
end 192.168.0.200 #default: 192.168.0.254

# The interface that udhcpd will use

interface usb0 #default: eth0

# The maximim number of leases (includes addressesd reserved
# by OFFER's, DECLINE's, and ARP conficts

#max_leases 254 #default: 254

# If remaining is true (default), udhcpd will store the time
# remaining for each lease in the udhcpd leases file. This is
# for embedded systems that cannot keep time between reboots.
# If you set remaining to no, the absolute time that the lease
# expires at will be stored in the dhcpd.leases file.

#remaining yes #default: yes

# The time period at which udhcpd will write out a dhcpd.leases
# file. If this is 0, udhcpd will never automatically write a
# lease file. (specified in seconds)

#auto_time 7200 #default: 7200 (2 hours)

# The amount of time that an IP will be reserved (leased) for if a
# DHCP decline message is received (seconds).

#decline_time 3600 #default: 3600 (1 hour)

# The amount of time that an IP will be reserved (leased) for if an
# ARP conflct occurs. (seconds

#conflict_time 3600 #default: 3600 (1 hour)

# How long an offered address is reserved (leased) in seconds

#offer_time 60 #default: 60 (1 minute)

# If a lease to be given is below this value, the full lease time is
# instead used (seconds).

#min_lease 60 #defult: 60

# The location of the leases file

#lease_file /var/lib/misc/udhcpd.leases #defualt: /var/lib/misc/udhcpd.
leases

# The location of the pid file
#pidfile /var/run/udhcpd.pid #default: /var/run/udhcpd.pid

# Everytime udhcpd writes a leases file, the below script will be called.
# Useful for writing the lease file to flash every few hours.

#notify_file #default: (no script)

#notify_file dumpleases # <--- usefull for debugging

# The following are bootp specific options, setable by udhcpd.

#siaddr 192.168.0.22 #default: 0.0.0.0

#sname zorak #default: (none)

#boot_file /var/nfs_root #default: (none)

# The remainer of options are DHCP options and can be specifed with the
# keyword 'opt' or 'option'. If an option can take multiple items, such
# as the dns option, they can be listed on the same line, or multiple
# lines. The only option with a default is 'lease'.

#Examles
opt dns 192.168.0.202 <your APN's DNS server>
option subnet 255.255.255.0
opt router 192.168.0.202
opt wins 192.168.0.202
#option dns 129.219.13.81 # appened to above DNS servers for a total of 3
option domain local
option lease 864000 # 10 days of seconds

# Currently supported options, for more info, see options.c
#subnet
#timezone
#router
#timesvr
#namesvr
#dns
#logsvr
#cookiesvr
#lprsvr
#bootsize
#domain
#swapsvr
#rootpath
#ipttl
#mtu
#broadcast
#wins
#lease
#ntpsrv
#tftp
#bootfile
</pre>

Notice that I set the start and end of the IP lease block to 192.168.0.200. If you follow the instructions at [[USB Networking]], this is the address that it assumes the host to be and the /etc/resolv.conf file points to this address to allow name resolution from your phone.

The interface in this case is usb0. This will have to be set differently if you are using Bluetooth.

The dns is set to the FreeRunner's address, as well as my network operator's DNS server address. You don't have to use your network operator's DNS address if you can find a caching nameserver for the FreeRunner.

The router is set to the FreeRunner.

== Turning your FreeRunner into a Network Address Translation (NAT) gateway ==

I set up my FreeRunner so that it acts as a NAT gateway so that all traffic that goes to my network operator appears to originate from the phone. I installed iptables to accomplish this:

opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat

Once that is installed, I have the following script named firewall.sh that I use to set up the NAT once connected to the GPRS network:

<pre>
#!/bin/sh
IPTABLES='/usr/sbin/iptables'

# Set interface values
EXTIF='ppp0'
INTIF='usb0'

# enable ip forwarding in the kernel
/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

# flush rules and delete chains
$IPTABLES -F
$IPTABLES -X

#Enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

#Forward LAN traffic from LAN $INTIF to Internet $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

#Allowing access to the SSH server"
#$IPTABLES -A INPUT --protocol tcp --dport 22 -j ACCEPT

#Allowing access to the HTTP server"
#$IPTABLES -A INPUT --protocol tcp --dport 80 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP
</pre>

so once connected through GPRS, I run:

./firewall.sh

and then you should be able to connect to the internet from your computer!

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]

{{Languages|Manually_using_GPRS}}
[[Category:Documentation]]
[[Category:Application Developer]]

[[Category:Guides]]

Navit

2008-08-18T16:16:52Z

Dewey: /* Route > Destination */

As described on the [http://navit.sourceforge.net/ Navit home page],

"Navit is a car navigation system with routing engine.

It's modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time.

The GTK+ or SDL user interfaces are designed to work well with touch screen displays. Points of Interest of various formats are displayed on the map.

The current vehicle position is either read from gpsd or directly from NMEA GPS sensors."

Some people say Navit is also a good choice for pedestrian and bicycle navigation.

[[Image:Screenshot-3.png|thumb|Navit-0.0.4+cvs]]

== Acknowledgment ==

Thanks to [[User:Alessandro | Alessandro]], stefan_schmidt, cp15 and all Navit developers I have done a small ("not really working") preview of Navit on Neo1973 at [http://www.telemobilityforum.com/eng/ Telemobility Forum 2007]. Thanks to [http://gfoss.it GFoss] guys to invite me.
''[[User:Tyrael | Tyrael]]''

==Setting up Navit==

I got navit set up and configured to the point where it follows me on the map. It doesn't have street names or any other information, just the map and the cursor showing the location and direction. Here's what I did:
* Install navit ipkg on NEO
opkg install http://www.mikeasoft.com/~mike/ipk/armv4t/navit_0.0.4-r0_armv4t.ipk
* Or roll your own from svn using the toolchain (having checked out trunk in the navit directory, and assuming you have written navit_control):
. /usr/local/openmoko/arm/setup-env
om-conf navit --disable-samplemap
om-make-ipkg navit navit_control
* Set up your local maps
** Openstreetmap - follow directions at http://wiki.navit-project.org/index.php/OpenStreetMaps
** Here's an example of what I did to get the maps for the area around Seattle, Wa where I live:
*** figured out map coordinates using http://informationfreeway.org/?lat=47.520270037501454&lon=-122.20130713167327&zoom=9&layers=B000F000
*** Downloaded 4 regions from openstreetmaps ([[Navit#Script_to_download_OSM_maps|see below]] for a script to do this for you automatically for largish areas)
wget -O map1.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.5,-122,47.7
wget -O map2.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.5,-122.2,47.7
wget -O map3.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.3,-122.2,47.5
wget -O map4.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.3,-122,47.5
*** Made a navit binary map file using the osm2navit binary that comes with the navit package on my linux box (it is also installing to the target from the .ipk)
cat *.osm | osm2navit --dedupe-ways mymap.bin

http://downloads.cloudmade.com/ also has up-to-date maps from OpenStreetMap by country.

*** Copied the map to the NEO
scp mymap.bin root@neo:/home/root/card/map
*** Change the navit.xml file on the NEO to use the new map
cp /usr/share/navit/navit.xml ~/.navit/navit.xml
vi ~/.navit/navit.xml
<map type="binfile" enabled="yes" data="/home/root/card/map/mymap.bin" />
* Run navit
** Start gllin (for GTA01)
** Start gpsd ( gpsd /tmp/nmeaNP )
** Start navit

* The version of osm2navit with which you build the maps should match the version of navit you have. If in doubt, build the maps on the OpenMoko.

== News ==

=== Street names ===
They are now displayed on OpenMoko using the CVS version of Navit (20071217).

=== Point selection by pen ===
Easier using the CVS version (20071217).

=== Route > Destination ===
The Route > Destination menu item crashes the software (20071217 and 0.04).

A current fix is to set the LANG variable before calling navit. For example:

LANG=fr_FR.UTF-8 navit

Note that a short syntax (e.g. LANG=fr) would not work.

If you put an "export LANG=fr_FR.UTF-8" into your /etc/.profile file, it will automatically set this environment variable every time you boot up. This way, you can launch Navit from the Icon in Illume.

http://trac.navit-project.org/ticket/51

=== Speech ===
Navit can speak if you install eSpeak + speech-dispatcher and updates your navit.xml file.

For adventurous people, one way to do this:

* mokoTTS aims to integrate these packages in OM:
http://projects.openmoko.org/projects/mokotts/

install espeak, dotconf, and then speech-dispatcher.
note: running 2008.8 updating from zecke's "testing" repo does not require "dotconf"

* change the speech tag in navit.xml:
<speech type="cmdline" data="spd-say '%s'" />

or "spd-say -l fr '%s'" for using the French voice for example.

=== Script to download OSM maps ===
[[User:Wurp|Wurp]] wrote a little python script to download all OSM maps within a lat/long rectangle. Just copy the script to a file called dlOSM.sh, chmod +x it, and run it like
dlOSM.sh <minimum latitude> <maximum latitude> <minimum longitude> <maximum longitude>

It takes a long time for large maps. I could optimize it some by having it try to get a big section at once, then if it fails, break it into smaller pieces and recurse. I'm not sure when/if I'll get around to that...

dlOSM.sh:
<pre>
#!/usr/bin/python

import os
import sys
#import math

def doIt(cmd):
os.system(cmd)

def getOsms(basename, minLat, maxLat, minLon, maxLon):
'''basename - base name of map, maps are named {basename}{count}.osm
minLat - latitude of the west side of the map
maxLat - latitude of the east side of the map
minLon - longitude of the north side of the map
maxLon - longitude of the south side of the map'''

wgetCmdTemplate = 'wget -O %s%s.osm http://api.openstreetmap.org/api/0.5/map?bbox=%s,%s,%s,%s'

currLat = minLat
mapCount = 0
while currLat < maxLat:
nextLat = min(currLat + 0.1, maxLat)

currLon = minLon
while currLon < maxLon:
nextLon = min(currLon + 0.1, maxLon)

doIt(wgetCmdTemplate % (basename, mapCount, currLon, currLat, nextLon, nextLat))

currLon = nextLon
mapCount = mapCount + 1

currLat = nextLat

(minLat, maxLat, minLon, maxLon) = map(float, sys.argv[1:])
getOsms('map', minLat, maxLat, minLon, maxLon)
</pre>

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

Navit

2008-08-18T16:16:25Z

Dewey: /* Route > Destination */

As described on the [http://navit.sourceforge.net/ Navit home page],

"Navit is a car navigation system with routing engine.

It's modular design is capable of using vector maps of various formats for routing and rendering of the displayed map. It's even possible to use multiple maps at a time.

The GTK+ or SDL user interfaces are designed to work well with touch screen displays. Points of Interest of various formats are displayed on the map.

The current vehicle position is either read from gpsd or directly from NMEA GPS sensors."

Some people say Navit is also a good choice for pedestrian and bicycle navigation.

[[Image:Screenshot-3.png|thumb|Navit-0.0.4+cvs]]

== Acknowledgment ==

Thanks to [[User:Alessandro | Alessandro]], stefan_schmidt, cp15 and all Navit developers I have done a small ("not really working") preview of Navit on Neo1973 at [http://www.telemobilityforum.com/eng/ Telemobility Forum 2007]. Thanks to [http://gfoss.it GFoss] guys to invite me.
''[[User:Tyrael | Tyrael]]''

==Setting up Navit==

I got navit set up and configured to the point where it follows me on the map. It doesn't have street names or any other information, just the map and the cursor showing the location and direction. Here's what I did:
* Install navit ipkg on NEO
opkg install http://www.mikeasoft.com/~mike/ipk/armv4t/navit_0.0.4-r0_armv4t.ipk
* Or roll your own from svn using the toolchain (having checked out trunk in the navit directory, and assuming you have written navit_control):
. /usr/local/openmoko/arm/setup-env
om-conf navit --disable-samplemap
om-make-ipkg navit navit_control
* Set up your local maps
** Openstreetmap - follow directions at http://wiki.navit-project.org/index.php/OpenStreetMaps
** Here's an example of what I did to get the maps for the area around Seattle, Wa where I live:
*** figured out map coordinates using http://informationfreeway.org/?lat=47.520270037501454&lon=-122.20130713167327&zoom=9&layers=B000F000
*** Downloaded 4 regions from openstreetmaps ([[Navit#Script_to_download_OSM_maps|see below]] for a script to do this for you automatically for largish areas)
wget -O map1.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.5,-122,47.7
wget -O map2.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.5,-122.2,47.7
wget -O map3.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.4,47.3,-122.2,47.5
wget -O map4.osm http://www.openstreetmap.org/api/0.5/map?bbox=-122.2,47.3,-122,47.5
*** Made a navit binary map file using the osm2navit binary that comes with the navit package on my linux box (it is also installing to the target from the .ipk)
cat *.osm | osm2navit --dedupe-ways mymap.bin

http://downloads.cloudmade.com/ also has up-to-date maps from OpenStreetMap by country.

*** Copied the map to the NEO
scp mymap.bin root@neo:/home/root/card/map
*** Change the navit.xml file on the NEO to use the new map
cp /usr/share/navit/navit.xml ~/.navit/navit.xml
vi ~/.navit/navit.xml
<map type="binfile" enabled="yes" data="/home/root/card/map/mymap.bin" />
* Run navit
** Start gllin (for GTA01)
** Start gpsd ( gpsd /tmp/nmeaNP )
** Start navit

* The version of osm2navit with which you build the maps should match the version of navit you have. If in doubt, build the maps on the OpenMoko.

== News ==

=== Street names ===
They are now displayed on OpenMoko using the CVS version of Navit (20071217).

=== Point selection by pen ===
Easier using the CVS version (20071217).

=== Route > Destination ===
The Route > Destination menu item crashes the software (20071217 and 0.04).

A current fix is to set the LANG variable before calling navit. For example:

LANG=fr_FR.UTF-8 navit

Note that a short syntax (e.g. LANG=fr) would not work.

If you put an "export LANG=fr_FR.UTF-8" into your /etc/.profile file, it will automatically be set this environment variable every time you boot up. This way, you can launch Navit from the Icon in Illume.

http://trac.navit-project.org/ticket/51

=== Speech ===
Navit can speak if you install eSpeak + speech-dispatcher and updates your navit.xml file.

For adventurous people, one way to do this:

* mokoTTS aims to integrate these packages in OM:
http://projects.openmoko.org/projects/mokotts/

install espeak, dotconf, and then speech-dispatcher.
note: running 2008.8 updating from zecke's "testing" repo does not require "dotconf"

* change the speech tag in navit.xml:
<speech type="cmdline" data="spd-say '%s'" />

or "spd-say -l fr '%s'" for using the French voice for example.

=== Script to download OSM maps ===
[[User:Wurp|Wurp]] wrote a little python script to download all OSM maps within a lat/long rectangle. Just copy the script to a file called dlOSM.sh, chmod +x it, and run it like
dlOSM.sh <minimum latitude> <maximum latitude> <minimum longitude> <maximum longitude>

It takes a long time for large maps. I could optimize it some by having it try to get a big section at once, then if it fails, break it into smaller pieces and recurse. I'm not sure when/if I'll get around to that...

dlOSM.sh:
<pre>
#!/usr/bin/python

import os
import sys
#import math

def doIt(cmd):
os.system(cmd)

def getOsms(basename, minLat, maxLat, minLon, maxLon):
'''basename - base name of map, maps are named {basename}{count}.osm
minLat - latitude of the west side of the map
maxLat - latitude of the east side of the map
minLon - longitude of the north side of the map
maxLon - longitude of the south side of the map'''

wgetCmdTemplate = 'wget -O %s%s.osm http://api.openstreetmap.org/api/0.5/map?bbox=%s,%s,%s,%s'

currLat = minLat
mapCount = 0
while currLat < maxLat:
nextLat = min(currLat + 0.1, maxLat)

currLon = minLon
while currLon < maxLon:
nextLon = min(currLon + 0.1, maxLon)

doIt(wgetCmdTemplate % (basename, mapCount, currLon, currLat, nextLon, nextLat))

currLon = nextLon
mapCount = mapCount + 1

currLat = nextLat

(minLat, maxLat, minLon, maxLon) = map(float, sys.argv[1:])
getOsms('map', minLat, maxLat, minLon, maxLon)
</pre>

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

Users Repositories

2008-08-16T19:11:43Z

Dewey: /* Angstrom Repository */

For information about the official downloads and distributions, see [[Downloads]]

=== Angstrom Repository ===

Angstrong is the base distribution of OpenMoko Linux distribution. It contains the basic set of Linux applications and they should be compatible with OpenMoko. [http://www.angstrom-distribution.org/repo/ The repository package listing].

To add the unstable Angstrom feed, update your ''/etc/opkg/base-feeds.conf'' to include a line:

<pre>
src/gz base http://www.angstrom-distribution.org/feeds/2007/ipk/glibc/armv4t/base/
</pre>

==== Om 2008.8 ====

On Om 2008.8, run the following commands from the Neo:

echo "arch base 50" > /etc/opkg/angstrom-feed.conf
echo "src/gz base http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/" >> /etc/opkg/angstrom-feed.conf

This repository contains the following useful packages:

* Pidgin - Instant Messaging. Can connect to MSN, Google Talk, Yahoo, ICQ with additional plugins
* [[Minimo]] - Web Browsing. AJAX capable, based on the Gecko rendering engine
* [[Navit]] - Car Navigation with Routing Engine

===[[User:ChooseOpen|ChooseOpen]]===
:http://chooseopen.com/openmoko/build/2007.2/?M=D (2007.2)
:http://chooseopen.com/openmoko/build/qtopia/?M=D (Qtopia)

===[[User:Kevin_Dean|Kevin_Dean]]===
:http://downloads.openmoko.org/recommended/ (only gta01)
:Latest recommended [[Snapshot review|snapshot review]]

===[[User:ScaredyCat|ScaredyCat]]===
:http://buildhost.automated.it/OM2007.2/?M=D

ScaredyCat also has a opkg repository for 2007.2 where e.g. gpe-filemanager and a lot more (e.g. ntpd) can be installed from. On the Neo do:

cd /etc/opkg
wget http://buildhost.automated.it/scaredycat.conf
opkg update
opkg install gpe-filemanager
opkg install gpe-timesheet
opkg install gpe-todo
opkg install mysql
opkg install mtpaint
opkg install sqlite
opkg install ntp
#(you get the idea)
/etc/init.d/xserver-nodm restart # to make the new applications appear in the menu

==='''mwester''' unofficial builds===
:http://moko.mwester.net/

===celtune===
:http://rabenfrost.net/celtune/?C=M;O=D
:http://rabenfrost.net/celtune/ipk/

Celtune offers Standard-Builds (.jffs2, .tar.gz, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
For more info take a look at http://rabenfrost.net/celtune/1-NEWS-WARNING-INFO
You can find images, kernels and packages for other devices too on http://rabenfrost.net/celtune/ (e.g. HTC-Blueangel, Asus730W ...)
A huge number of packages is located at http://rabenfrost.net/celtune/ipk/
Use the following line to add celtune's feed to your neo:
cd /etc/opkg && wget http://rabenfrost.net/celtune/celtune-rabenfrost.conf

===FSO===
Daily builds of the freesmartphone.org distribution can be found at: 
http://totalueberwachung.de/~alphaone/openembedded-build/glibc/images/neo1973/ 

===Note===
If you want to add a link, it would be nice to enforce a standard format of these feeds so that they can be browsed automatically.

[[Category:Openmoko]]

Om 2008 Installer

2008-08-16T17:36:59Z

Dewey: Undo revision 46950 by Dewey (Talk)

{{Om 2008.8}}

==Introduction==
The OpenMoko Installer (Codename: [http://code.google.com/p/om-assassin/ Assassin]) is a tool for ''installing'', ''updating'' and ''uninstalling'' programs on your Neo.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Install.png|200px|thumb|catogory]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Install1.png|200px|thumb|choose program]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Installer4.png|200px|thumb|install application]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Om2008 installer2.png|200px|thumb|install application]]
|}
==Install an Application ==
'''Installer''' needs an internet connection to install applications for the repositories. This can be done via WiFi (currently unstable), [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB], [[GPRS]] or [[How_to_use_bluetooth_to_transfer_data_between_Neo_and_Desk-top|Bluetooth]].

===Instructions===

'''[1]''' Make sure you are connected to the internet and launch '''Installer'''.

'''[2]''' At launch, '''Installer''' will initially refresh a list of installable programs. After refresh is complete, press the '''INSTALL''' button from the bottom bar to view a list of Categories. This is also the default page of the Installer application.

'''[3]''' Select a Category from the category list, then select a package to install.

'''[4]''' In the package information page, press the image box and confirm to begin.

'''[5]''' Once the progress bar shows '''Done''', you will return to the Installer default page. Installation is then complete.

* To ''update'' or ''uninstall'' packages, simply replace step '''[2]''' with the desired function '''UPDATE''' or '''UNINSTALL''' and repeat steps '''[3]''' through '''[5]'''.

==Sharing Applications==
Sharing applications is done by uploading packages to the [http://downloads.openmoko.org/repository/Multiverse/ Community Repository], which is a similar concept to the Multiverse repository in Ubuntu. [[CommunityRepository|Anyone can upload applications]] or even their own repository to share with fellow Neo owners.

===How to add a package to Openmoko Repository===

You can release your package with ipk file.

* [[Create package on projects.openmoko.org and upload]]
* '''Create ipk files'''
** Using OE
** [[Toolchain|Meta-toolchain]]

==== Package Tags ====
Packages in '''Installer''' are displayed according to '''Package Tags'''.
To display a package through [[Om2008.8_Installer |Installer]], add the appropriate tag message.
{| class="wikitable" border:1px ;
! Category !! Tag
|-
| Communication || group::communication
|-
| Development || group::programming
|-
| Games || group::games
|-
| Maps || group::maps
|-
| Miscellaneous || group::unknown
|-
| Network || group::network
|-
|Repos || group::repos
|}

* For OpenEmbedded users, add a Tag by adding one line in your bb file
:For [http://code.google.com/p/comic-reader/source/browse/trunk/data/comic-reader_svn.bb example]:
PKG_TAGS_${PN} = "group::games"

==== Add a Repository ====
===== Add repositories by installing repository packages =====
* The community-repository is installed by default in [[Om2008.8 | Om 2008.8]].

===== Add repository manually =====
* Create a file, here we call it community-repos.conf
> echo "arch community-repos 50" > community-repos.conf
> echo "src community-repos http://downloads.openmoko.org/repository/Multiverse/" >> community-repos.conf
* Connect to your Neo with USB
> sudo ifconfig usb0 192.168.0.200
> scp community-repos.conf root@192.168.0.202:/etc/opkg/
* Let your Neo connect to the Internet
** For USB users:
> echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward
> sudo iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
> scp /etc/resolv.conf root@192.168.0.202:/etc/
** For geek users:
> ssh root@192.168.0.202
> iwlist eth0 scan
Find a usable AP lets say OpenMind (Support it's an open AP)
> iwconfig eth0 essid OpenMind
> udhcpc eth0
Then pray, if successfull, remove default gw *twice*.
> route -n # to see your gateway of eth0 say 192.168.1.1
> route del default
> route del default
> route add default gw 192.168.1.1 eth0
Then you can ping wiki.openmoko.org for testing :)
** For GUI WiFi user:
Click Settings
Click WiFi
Select an AP
Input password if needed

* Refresh the opkg metadata database
after connecting to Neo
> opkg update

== Technical Features ==
* '''Installer''' is a specialized GUI front-end of [http://packagekit.org/ Packagekit] over DBus interface.

* Please run '''Installer''' under stable network conditions and enough power supply. Once '''Installer''' is launched, it will actually try to detect repositories you installed. This will take some time if your network condition is not stable.
** If you do not have access to WiFi, a [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB] connection is recommended.
* The default Packagekit backend on Neo is [[opkg]], but is not restricted to opkg.

* '''Installer''' refreshes the package meta-data every 2 days.

* While running '''Installer''', it will also launch packagekitd automatically, in which it will lock the libopkg for synchronization issues. If you want to use opkg, you may terminate '''Installer''' and killall packagekitd.

* You can also talk with Packagekit through DBus.

For more information, refer to the reference section below.

== Reference ==
[1] Installer project - http://code.google.com/p/om-assassin/

[2] Packagekit project - http://packagekit.org/

[3] Opkg package management - http://wiki.openmoko.org/wiki/Opkg

[[Category:Applications]]
[[Category:Om 2008.8]]

Om 2008 Installer

2008-08-16T17:34:23Z

Dewey: /* Install an Application */

{{Om 2008.8}}

==Introduction==
The OpenMoko Installer (Codename: [http://code.google.com/p/om-assassin/ Assassin]) is a tool for ''installing'', ''updating'' and ''uninstalling'' programs on your Neo.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Install.png|200px|thumb|catogory]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Install1.png|200px|thumb|choose program]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Installer4.png|200px|thumb|install application]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |
[[Image:Om2008 installer2.png|200px|thumb|install application]]
|}
==Install an Application ==

There are two ways to install an application:

=== 1. Using the Graphical Installer ===

'''Installer''' needs an internet connection to install applications for the repositories. This can be done via WiFi (currently unstable), [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB], [[GPRS]] or [[How_to_use_bluetooth_to_transfer_data_between_Neo_and_Desk-top|Bluetooth]].

====Instructions====

'''[1]''' Make sure you are connected to the internet and launch '''Installer'''.

'''[2]''' At launch, '''Installer''' will initially refresh a list of installable programs. After refresh is complete, press the '''INSTALL''' button from the bottom bar to view a list of Categories. This is also the default page of the Installer application.

'''[3]''' Select a Category from the category list, then select a package to install.

'''[4]''' In the package information page, press the image box and confirm to begin.

'''[5]''' Once the progress bar shows '''Done''', you will return to the Installer default page. Installation is then complete.

* To ''update'' or ''uninstall'' packages, simply replace step '''[2]''' with the desired function '''UPDATE''' or '''UNINSTALL''' and repeat steps '''[3]''' through '''[5]'''.

=== 2. Using opkg from the command line ===

opkg install <package name from repository, filename, or url to package>

This method is most useful for installing packages that are not in any of the repositories. You may have to kill the packagekit service if opkg compalins about:

* Could not obtain administrative lock

Issue a

pkill packagekit

==Sharing Applications==
Sharing applications is done by uploading packages to the [http://downloads.openmoko.org/repository/Multiverse/ Community Repository], which is a similar concept to the Multiverse repository in Ubuntu. [[CommunityRepository|Anyone can upload applications]] or even their own repository to share with fellow Neo owners.

===How to add a package to Openmoko Repository===

You can release your package with ipk file.

* [[Create package on projects.openmoko.org and upload]]
* '''Create ipk files'''
** Using OE
** [[Toolchain|Meta-toolchain]]

==== Package Tags ====
Packages in '''Installer''' are displayed according to '''Package Tags'''.
To display a package through [[Om2008.8_Installer |Installer]], add the appropriate tag message.
{| class="wikitable" border:1px ;
! Category !! Tag
|-
| Communication || group::communication
|-
| Development || group::programming
|-
| Games || group::games
|-
| Maps || group::maps
|-
| Miscellaneous || group::unknown
|-
| Network || group::network
|-
|Repos || group::repos
|}

* For OpenEmbedded users, add a Tag by adding one line in your bb file
:For [http://code.google.com/p/comic-reader/source/browse/trunk/data/comic-reader_svn.bb example]:
PKG_TAGS_${PN} = "group::games"

==== Add a Repository ====
===== Add repositories by installing repository packages =====
* The community-repository is installed by default in [[Om2008.8 | Om 2008.8]].

===== Add repository manually =====
* Create a file, here we call it community-repos.conf
> echo "arch community-repos 50" > community-repos.conf
> echo "src community-repos http://downloads.openmoko.org/repository/Multiverse/" >> community-repos.conf
* Connect to your Neo with USB
> sudo ifconfig usb0 192.168.0.200
> scp community-repos.conf root@192.168.0.202:/etc/opkg/
* Let your Neo connect to the Internet
** For USB users:
> echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward
> sudo iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
> scp /etc/resolv.conf root@192.168.0.202:/etc/
** For geek users:
> ssh root@192.168.0.202
> iwlist eth0 scan
Find a usable AP lets say OpenMind (Support it's an open AP)
> iwconfig eth0 essid OpenMind
> udhcpc eth0
Then pray, if successfull, remove default gw *twice*.
> route -n # to see your gateway of eth0 say 192.168.1.1
> route del default
> route del default
> route add default gw 192.168.1.1 eth0
Then you can ping wiki.openmoko.org for testing :)
** For GUI WiFi user:
Click Settings
Click WiFi
Select an AP
Input password if needed

* Refresh the opkg metadata database
after connecting to Neo
> opkg update

== Technical Features ==
* '''Installer''' is a specialized GUI front-end of [http://packagekit.org/ Packagekit] over DBus interface.

* Please run '''Installer''' under stable network conditions and enough power supply. Once '''Installer''' is launched, it will actually try to detect repositories you installed. This will take some time if your network condition is not stable.
** If you do not have access to WiFi, a [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB] connection is recommended.
* The default Packagekit backend on Neo is [[opkg]], but is not restricted to opkg.

* '''Installer''' refreshes the package meta-data every 2 days.

* While running '''Installer''', it will also launch packagekitd automatically, in which it will lock the libopkg for synchronization issues. If you want to use opkg, you may terminate '''Installer''' and killall packagekitd.

* You can also talk with Packagekit through DBus.

For more information, refer to the reference section below.

== Reference ==
[1] Installer project - http://code.google.com/p/om-assassin/

[2] Packagekit project - http://packagekit.org/

[3] Opkg package management - http://wiki.openmoko.org/wiki/Opkg

[[Category:Applications]]
[[Category:Om 2008.8]]

Om 2008 Installer

2008-08-16T16:54:09Z

Dewey: /* Install an Application */

Minimo

2008-08-16T16:07:20Z

Dewey: /* Installing Minimo web browser */

{{Languages|Minimo}}

[[Image:Minimo-slashdot.jpeg|thumb|minimo in QEMU displaying it.slashdot.org]]
[[Image:GTA01-minimo.JPG|thumb|minimo on GTA01 displaying www.heise.de]]

= Installing Minimo web browser =

[http://www.mozilla.org/projects/minimo/develop.html Minimo] is a Mozilla based web browser. It features full [http://en.wikipedia.org/wiki/Ajax_%28programming%29 AJAX] support and other goodies. Currently stock Openmoko build doesn't include Minimo.

== Running on Om2008.8 ==

From the Neo, download the minimo package:

wget http://www.ginguppin.de/files/minimo.tar.bz2

Then install it:

opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

If you get the following error:

* ERROR: Cannot satisfy the following dependencies for minimo:
* libfreetype6 (>= 2.3.6) *

First try:

opkg install libfreetype6

If this does not install a libfreetype6 version > 2.3.6, you can download a newer libfreetype6 from the Angstrom repository at this location: http://www.angstrom-distribution.org/repo/?action=details&pnm=libfreetype6

Ex:

wget http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libfreetype6_2.3.6-r0_armv4t.ipk
opkg install minimo_0.02\+cvs20070626-r0_armv4t.ipk

Using Minimo with the stock Om2008.8 gets annoying because the keyboard always takes up half the screen. I recommend reactivating the [[Keyboard_Toggle#Reactivating_the_keyboard_toggle_under_Om2008.8|Keyboard Toggle]] so that you can hide the keyboard while browsing.

I also highly recommend getting [[GPRS]] going so that you can browse on the go!

== Running in Xephyr PC environment ==

Here are instructions on how to run minimo in Xephyr PC environment and how to use other third party packages too.

* [http://bec-systems.com/web/content/view/79/9/ Instructions for including new OpenEmbedded packages to your project]

These instructions should be updated to use a custom image rather than DISTRO_EXTRA_RDEPENDS -- see link above.

Alternatively, a binary ipkg was posted here[[http://www.ginguppin.de/files/minimo.tar.bz2]]

=== Setup build environment ===

If you have built your Openmoko using MokoMakefile some of these steps might not be familiar to you.

Assume your Openmoko root is at ~/workspace/moko

First setup build environment variables:
<pre>
moo@hacker:~/workspace/moko/build$ . ../setup-env
</pre>

Then checkout minimo from OpenEmbedded repository:
<pre>
moo@hacker:~/workspace/moko/build$ bitbake minimo
</pre>

Edit local.conf and add minimo to build dependencies list.

<pre>
MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "minimo"
</pre>

After local.conf has added new packages, one must refresh bitbake tasks.

<pre>
bitbake task-base -crebuild
</pre>

Now, you should be able to rebuild root fs using MokoMakefile.

<pre>
make openmoko-devel-image
</pre>

=== Tips ===

The default Openmoko distribution lacks ''/etc/resolv.conf'' file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

<pre>
moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf
</pre>

If build fails with

<pre>
/usr/bin/ld: skipping incompatible $OMDIR/local/tmp/staging/arm-angstrom-linux-gnueabi/lib/libIDL-2.a when searching for -lIDL-2
</pre>
(here minimo is installed in a [http://wiki.openmoko.org/wiki/Application_Development_Crash_Course#Setting_Up_a_Local_Overlay Local Overlay], so your path will perhaps differ) try installing the libidl-dev package on the buildhost:

<pre>
sudo aptitude install libidl-dev
</pre>

=== In chroot'ed environment ===

Following instructions in [[Getting Openmoko working on host with Xephyr]] to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start Openmoko session, minimo can run as is.

<pre>
/ $ minimo
</pre>

[[Category:Applications]]
[[Category:Guides]]

Minimo

2008-08-16T15:57:21Z

Dewey:

{{Languages|Minimo}}

[[Image:Minimo-slashdot.jpeg|thumb|minimo in QEMU displaying it.slashdot.org]]
[[Image:GTA01-minimo.JPG|thumb|minimo on GTA01 displaying www.heise.de]]

= Installing Minimo web browser =

[http://www.mozilla.org/projects/minimo/develop.html Minimo] is a Mozilla based web browser. It features full [http://en.wikipedia.org/wiki/Ajax_%28programming%29 AJAX] support and other goodies. Currently stock Openmoko build doesn't include Minimo.

== Running on Om2008.8 ==

From the Neo, download the minimo package:

wget http://www.ginguppin.de/files/minimo.tar.bz2

Then install it:

opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

If you get the following error:

* ERROR: Cannot satisfy the following dependencies for minimo:
* libfreetype6 (>= 2.3.6) *

First try:

opkg install libfreetype6

If this does not install a libfreetype6 version > 2.3.6, you can download a newer libfreetype6 from the Angstrom repository at this location: http://www.angstrom-distribution.org/repo/?action=details&pnm=libfreetype6

Ex:

wget http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/libfreetype6_2.3.6-r0_armv4t.ipk
opkg install minimo_0.02\+cvs20070626-r0_armv4t.ipk

Using Minimo with the stock Om2008.8 gets annoying because the keyboard always takes up half the screen. I recommend reactivating the [[Keyboard_Toggle#Reactivating_the_keyboard_toggle_under_Om2008.8|Keyboard Toggle]] so that you can hide the keyboard while browsing.

== Running in Xephyr PC environment ==

Here are instructions on how to run minimo in Xephyr PC environment and how to use other third party packages too.

* [http://bec-systems.com/web/content/view/79/9/ Instructions for including new OpenEmbedded packages to your project]

These instructions should be updated to use a custom image rather than DISTRO_EXTRA_RDEPENDS -- see link above.

Alternatively, a binary ipkg was posted here[[http://www.ginguppin.de/files/minimo.tar.bz2]]

=== Setup build environment ===

If you have built your Openmoko using MokoMakefile some of these steps might not be familiar to you.

Assume your Openmoko root is at ~/workspace/moko

First setup build environment variables:
<pre>
moo@hacker:~/workspace/moko/build$ . ../setup-env
</pre>

Then checkout minimo from OpenEmbedded repository:
<pre>
moo@hacker:~/workspace/moko/build$ bitbake minimo
</pre>

Edit local.conf and add minimo to build dependencies list.

<pre>
MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "minimo"
</pre>

After local.conf has added new packages, one must refresh bitbake tasks.

<pre>
bitbake task-base -crebuild
</pre>

Now, you should be able to rebuild root fs using MokoMakefile.

<pre>
make openmoko-devel-image
</pre>

=== Tips ===

The default Openmoko distribution lacks ''/etc/resolv.conf'' file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

<pre>
moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf
</pre>

If build fails with

<pre>
/usr/bin/ld: skipping incompatible $OMDIR/local/tmp/staging/arm-angstrom-linux-gnueabi/lib/libIDL-2.a when searching for -lIDL-2
</pre>
(here minimo is installed in a [http://wiki.openmoko.org/wiki/Application_Development_Crash_Course#Setting_Up_a_Local_Overlay Local Overlay], so your path will perhaps differ) try installing the libidl-dev package on the buildhost:

<pre>
sudo aptitude install libidl-dev
</pre>

=== In chroot'ed environment ===

Following instructions in [[Getting Openmoko working on host with Xephyr]] to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start Openmoko session, minimo can run as is.

<pre>
/ $ minimo
</pre>

[[Category:Applications]]
[[Category:Guides]]

TangoGPS

2008-08-16T15:25:31Z

Dewey: /* Running tangoGPS on OM2008.8 */

{{Languages|TangoGPS}}
TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.

Website: http://www.tangogps.org

== Running tangoGPS on OM2008.8 ==

{{note|There may be other steps because I remember it took a while before my TangoGPS started working, but these are the only things I remember installing}}

From the freerunner connected to the internet:

opkg install gpsd
opkg install tangogps

If opkg complains about not being able to acquire a lock, try:

pkill packagekit

I think TangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]

There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!

[[Category:GPS]]

TangoGPS

2008-08-16T15:19:31Z

Dewey: /* Running tangoGPS on OM2008.8 */

Manually using GPRS

2008-08-15T02:02:17Z

Dewey: Modified section titles

The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator.

= 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

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 found here:

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

In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found 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: Without GSM multiplexing and without a GUI =

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>

== 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 || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || 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
|-
| 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 pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| 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 || Telenor || Any || telenor || ||
|-
| Sweden || Parlino || || internet.parlino.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>

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]

{{Languages|Manually_using_GPRS}}
[[Category:Documentation]]
[[Category:Application Developer]]

[[Category:Guides]]

Manually using GPRS

2008-08-15T01:57:43Z

Dewey:

The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator.

= Option 1: With GSM Multiplexing =

{{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

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 found here:

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

In order to install that version of gsm0710muxd, however, you will also have to install a bunch of missing dependencies. Those can be found by clicking on the dependencies found 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: Without GSM Multiplexing =

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>

== 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 || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || 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
|-
| 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 pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| 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 || Telenor || Any || telenor || ||
|-
| Sweden || Parlino || || internet.parlino.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>

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]

{{Languages|Manually_using_GPRS}}
[[Category:Documentation]]
[[Category:Application Developer]]

[[Category:Guides]]

Manually using GPRS

2008-08-15T00:43:15Z

Dewey: /* Some APN names for reference */

The GPRS connection is made using the PPP protocol to a server identified by an "APN" at the network operator.

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>

== 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 || Vodafone || Any || vfinternet.au || ||
|-
| Canada || Fido || Any, behind NAT || internet.fido.ca || fido/fido || 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
|-
| 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 pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| 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 || Telenor || Any || telenor || ||
|-
| Sweden || Parlino || || internet.parlino.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>

== See also ==
* [[pppd]]
* [[Manually using GSM]]
* [[Manually using Bluetooth]]

{{Languages|Manually_using_GPRS}}
[[Category:Documentation]]
[[Category:Application Developer]]

[[Category:Guides]]

Flashing the Neo FreeRunner

2008-08-07T18:45:53Z

Dewey: /* Boot the FreeRunner from NOR Flash */

Openmoko regularly releases updated versions of the Openmoko root filesystem, the [[kernel]], and the [[Bootloader| U-Boot]] as binary images. These may be programmed into the Flash memory (NAND) of Neo FreeRunner. For that, you can use the USB cable and another computer which will run an Openmoko provided tool to flash the Neo FreeRunner "through" USB.

{{note|The Openmoko software team builds images daily. If you want to use the latest images, you can download the image from the daily build, but we recommend you '''use the most stable image from http://downloads.openmoko.org/releases/Freerunner/.''' Images here have been tested by the test team.}}

== Overview ==
All the components of the software in the FreeRunner are bundled together into binary images.

The '''bootloader''' is a small program that runs first when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from NOR or NAND is booted).
The '''kernel''' is the central component in the Linux operating system.
The '''root filesystem''' contains all the files that make up the commands and applications that you can run.

On a desktop computer when you want to replace the operating system, you would boot it from a CD-ROM drive, then copy files from the CD to the internal hard drive.

The FreeRunner does not have a CD-ROM drive but it does have two kinds of internal program storage: NOR flash and NAND flash. The NOR flash is small and stores only a special boot program used when you need to re-write the contents of the NAND flash. NAND flash acts more like a hard drive.

The NAND Flash is divided into 3 partitions so that you can flash each component separately.
For example if you are trying to install a better kernel, you only have to follow the steps to flash the kernel image.

The FreeRunner can also boot from an image in its micro SD card but that option is not covered here. See [[Booting from SD]] for more information.

'''Before you start: Erasing the root filesystem or flashing the uboot are radical measures. Take the time to ponder the necessity. Sometimes problems can be fixed by updating only the kernel.'''

The steps to reflash NAND are

# Collect everything you need together on your desktop computer. This includes the dfu-util program and the images you will load into the FreeRunner and a USB cable.
# Boot the FreeRunner from NOR Flash.
# Connect the FreeRunner to the desktop computer via the USB cable.
# Use dfu-util to backup the current contents of the FreeRunner.
# Use dfu-util to copy the images from the desktop into the FreeRunner.
# Boot the FreeRunner from NAND Flash to use the new image(s).

== Collect the things you need ==

=== Download the DFU-util program ===

You will download that program on your preferred desktop computer. It will allow you to connect to the FreeRunner through the USB cable and control its bootloader. That connection uses a special protocol which addresses the bootloader's interface, and differs from USB networking.

There are versions of dfu-util for both Linux and Windows. It works the same way on both platforms.
There is a separate page to describe it in more detail: [[dfu-util]]

'''MacOS X'''

There is also a graphical dfu-util based flashing utility for MacOS X which is described here: [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

'''Linux'''
You can download the flashing tool for a GNU/Linux host from:
http://downloads.openmoko.org/releases/Freerunner/dfu-util

Make sure it is executable by setting the permissions with this command: chmod a+x dfu-util

'''Windows'''
You can download the flashing tool for a Windows host from:
[http://projects.openmoko.org/frs/?group_id=166&release_id=162 http://projects.openmoko.org/frs/?group_id=166&release_id=162]

See additional driver installation instructions for Windows at [[Dfu-util-windows]]

=== Download the image files that you will need ===

Exactly what files you need depends on what you are trying to install. Here are some pages you can refer to for more information.

''Edit request -- Some comments on why you'd want to replace each component could go here. For example you probably don't want to replace the bootloader unless there are bug fixes you really need.''

[[Bootloader]] : TBD

[[Kernel]] : You can download kernels from http://downloads.openmoko.org/releases/Freerunner/

You can download the standard Openmoko root filesystem from
http://downloads.openmoko.org/releases/Freerunner/
or you can see more options at [[Distributions]] and [[Latest_Images]]

If you download a '''Qtopia''' image, you will get a tarball file containing both the Qtopia root filesystem and a matching kernel. You can unpack them with the tar command, for example: tar xzvf ''qtopia.tgz''

If you download an '''FSO''' image, 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.

== Boot the FreeRunner from NOR Flash ==

[[Image:menu15.jpg|thumb|Booting from NOR Flash]]

The Neo FreeRunner needs to be at the NOR uBoot menu for flashing. To get there. 1. press and hold ''aux'' button down, and then 2. press ''power button'' until the boot process starts. (For more information on booting, see [[Booting the Neo FreeRunner| booting the Neo Freerunner]])

Once you see the NOR uBoot menu (labelled '''*** BOOT MENU (NOR) ***''') just stay there, you do not need to select or enter any item in menu. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.

We often hear this comment: '''The screen goes dark before I do anything!!''' The FreeRunner only stays at the NOR boot prompt for about 30 seconds and then shuts off unless you do something. Be sure you are ready to enter commands on your desktop once you have booted.

Once the FreeRunner is at the NOR boot menu, then you can connect your Neo to the GNU/Linux or Windows host via a USB cable. If you have to boot back into NOR at this point (because you did not type fast enough!), pull the USB cable out first. Otherwise you will end up booting into the regular FreeRunner operating system. Got that? This is the routine:

# boot into NOR
# connect usb
# type dfu-util commands


Note that the dfu-util connection does '''not''' use Ethernet over USB - that is, you should not attempt to set up a usb0 network interface on your GNU/Linux host desktop (on Windows, you need a DFU class driver, or you can use the LibUSB-Win32 driver described on the [[Dfu-util-windows]] page). The dfu-util utility sets up its own connection to the FreeRunner. In fact, you will not be able to make an Ethernet-over-USB connection to the FreeRunner when it is at the uBoot menu; this type of connection is only available when the FreeRunner has booted fully.

After connecting the FreeRunner to your host via USB cable, you can test whether dfu-util "sees" the FreeRunner by executing:

dfu-util -l

Sometimes I get error messages from the dfu-util command; I just try again. Often they work on the second try. Sometimes I have to boot into NOR again before things work. Once a connection has been made everything seems to work fine.
 

== Do a backup ==

If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]], although it looks like the method on that page may not entirely work.

''Is this still true? 7/31/08??''

== Using dfu-util ==

dfu-util can be used to read flash memory, write memory, and get information from the device.

This is the general command format to write an image file to a (predefined) "partition name" (referred to as ''altsetting'' in dfu-util help/manual) :

dfu-util -a ''altsetting'' -R -D ''file_name''

where: 
-a ''altsetting'' : Specify the altsetting of the DFU interface by name or by number 
-R : Issue USB Reset signalling once we're finished 
-D ''file_name'' : Write firmware from ''file_name'' into device

On Linux, you run dfu-util from a command shell prompt. If you have not put it somewhere on your command path you probably need to prefix it with a "./" like this '''./dfu-util'''.
On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

On Windows, you need to open a command window and run from a command line. Use Start-Run Program and type "cmd" to open a Window.

== Flashing the Kernel ==

The command format is

dfu-util -a kernel -R -D ''/path/to/uImage''

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the Root Filesystem ==

The root filesystem has to be an image in jffs2 format. If the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a rootfs -R -D ''rootfs_filename.jffs2''

where ''rootfs_filename.jffs2'' is the name of the file containing the root filesystem.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the boot loader to the NAND==

The boot loader (U-boot) file should have a .bin extension. As with the root filesystem, if the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a u-boot -R -D ''uboot.bin''

where ''uboot.bin'' is the name of the boot loader binary image file.

''Reminder'': You should have [[Flashing_the_Neo_FreeRunner#Boot_the_FreeRunner_from_NOR_Flash|rebooted from NOR first]], in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates.


(Optional) After an upgrade, you may wish to check that the u-boot version matches the one you have just flashed. You can use 'grep Bootloader /dev/mtdblock1' from a shell on the FreeRunner (and possibly the 1973 as well) to get the '''NAND''' u-boot version, like this:
root@om-gta02:~# grep Bootloader /dev/mtdblock1
Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb

You can grep for the same string in /dev/mtdblock0 to retrieve the '''NOR''' u-boot version:
root@om-gta02:~# grep Bootloader /dev/mtdblock0
Neo1973 Bootloader U-Boot 1.3.2-moko12



== Reboot the FreeRunner from NAND ==

You should now be able to boot into the new images.

Pay attention '''to booting from the NAND flash this time''', in particular if you upgraded the boot-loader (in short: 1. press and hold ''power button'' down, and then 2. press ''aux button'')

The boot menu should be labelled '''*** BOOT MENU (NAND) ***''' this time (see [[Booting#Log_into_U-Boot_in_the_NAND_Flash|booting from NAND]] for more detailed instructions).

[[Category:Flashing Openmoko| ]]

Dfu-util-windows

2008-08-07T18:45:23Z

Dewey: /* dfu-util for Win32 */

== dfu-util for Win32 ==

{{Note|This has been reported to work on Windows XP and Windows Vista with the Neo FreeRunner. No reports have been received on whether it works with other versions of Windows or with the Neo 1973}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. Theoretically, a USB standard-compliant DFU class driver should work, unfortunately, Windows does not come bundled with one. If you do not have a DFU class driver (ie. Windows does not recognize the device in U-Boot mode and pops up the New Device Wizard), the LibUSB-Win32 driver and accompanying INF file for the Neo FreeRunner can be used, this driver can be found in OpenMokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH=" /c/msys/1.0/lib/pkgconfig"

ensuring that the path is accessible from the MSYS shell and points to the pkgconfig files.

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4553)
+++ main.c (working copy)
@@ -26,8 +26,10 @@
#include <getopt.h>
#include <usb.h>
#include <errno.h>
+#ifndef __MINGW32__
#include <byteswap.h>
#include <endian.h>
+#endif

#include "dfu.h"
#include "usb_dfu.h"
@@ -37,6 +39,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +585,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n", usb_strerror());
@@ -700,12 +720,18 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4553)
+++ sam7dfu.c (working copy)
@@ -20,6 +20,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4553)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

check your PKG_CONFIG_PATH (see above) to make sure it is correct, otherwise, you can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: OpenMoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Flashing the Neo FreeRunner

2008-08-07T18:38:10Z

Dewey: /* Download the DFU-util program */

Openmoko regularly releases updated versions of the Openmoko root filesystem, the [[kernel]], and the [[Bootloader| U-Boot]] as binary images. These may be programmed into the Flash memory (NAND) of Neo FreeRunner. For that, you can use the USB cable and another computer which will run an Openmoko provided tool to flash the Neo FreeRunner "through" USB.

{{note|The Openmoko software team builds images daily. If you want to use the latest images, you can download the image from the daily build, but we recommend you '''use the most stable image from http://downloads.openmoko.org/releases/Freerunner/.''' Images here have been tested by the test team.}}

== Overview ==
All the components of the software in the FreeRunner are bundled together into binary images.

The '''bootloader''' is a small program that runs first when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from NOR or NAND is booted).
The '''kernel''' is the central component in the Linux operating system.
The '''root filesystem''' contains all the files that make up the commands and applications that you can run.

On a desktop computer when you want to replace the operating system, you would boot it from a CD-ROM drive, then copy files from the CD to the internal hard drive.

The FreeRunner does not have a CD-ROM drive but it does have two kinds of internal program storage: NOR flash and NAND flash. The NOR flash is small and stores only a special boot program used when you need to re-write the contents of the NAND flash. NAND flash acts more like a hard drive.

The NAND Flash is divided into 3 partitions so that you can flash each component separately.
For example if you are trying to install a better kernel, you only have to follow the steps to flash the kernel image.

The FreeRunner can also boot from an image in its micro SD card but that option is not covered here. See [[Booting from SD]] for more information.

'''Before you start: Erasing the root filesystem or flashing the uboot are radical measures. Take the time to ponder the necessity. Sometimes problems can be fixed by updating only the kernel.'''

The steps to reflash NAND are

# Collect everything you need together on your desktop computer. This includes the dfu-util program and the images you will load into the FreeRunner and a USB cable.
# Boot the FreeRunner from NOR Flash.
# Connect the FreeRunner to the desktop computer via the USB cable.
# Use dfu-util to backup the current contents of the FreeRunner.
# Use dfu-util to copy the images from the desktop into the FreeRunner.
# Boot the FreeRunner from NAND Flash to use the new image(s).

== Collect the things you need ==

=== Download the DFU-util program ===

You will download that program on your preferred desktop computer. It will allow you to connect to the FreeRunner through the USB cable and control its bootloader. That connection uses a special protocol which addresses the bootloader's interface, and differs from USB networking.

There are versions of dfu-util for both Linux and Windows. It works the same way on both platforms.
There is a separate page to describe it in more detail: [[dfu-util]]

'''MacOS X'''

There is also a graphical dfu-util based flashing utility for MacOS X which is described here: [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

'''Linux'''
You can download the flashing tool for a GNU/Linux host from:
http://downloads.openmoko.org/releases/Freerunner/dfu-util

Make sure it is executable by setting the permissions with this command: chmod a+x dfu-util

'''Windows'''
You can download the flashing tool for a Windows host from:
[http://projects.openmoko.org/frs/?group_id=166&release_id=162 http://projects.openmoko.org/frs/?group_id=166&release_id=162]

See additional driver installation instructions for Windows at [[Dfu-util-windows]]

=== Download the image files that you will need ===

Exactly what files you need depends on what you are trying to install. Here are some pages you can refer to for more information.

''Edit request -- Some comments on why you'd want to replace each component could go here. For example you probably don't want to replace the bootloader unless there are bug fixes you really need.''

[[Bootloader]] : TBD

[[Kernel]] : You can download kernels from http://downloads.openmoko.org/releases/Freerunner/

You can download the standard Openmoko root filesystem from
http://downloads.openmoko.org/releases/Freerunner/
or you can see more options at [[Distributions]] and [[Latest_Images]]

If you download a '''Qtopia''' image, you will get a tarball file containing both the Qtopia root filesystem and a matching kernel. You can unpack them with the tar command, for example: tar xzvf ''qtopia.tgz''

If you download an '''FSO''' image, 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.

== Boot the FreeRunner from NOR Flash ==

[[Image:menu15.jpg|thumb|Booting from NOR Flash]]

The Neo FreeRunner needs to be at the NOR uBoot menu for flashing. To get there. 1. press and hold ''aux'' button down, and then 2. press ''power button'' until the boot process starts. (For more information on booting, see [[Booting the Neo FreeRunner| booting the Neo Freerunner]])

Once you see the NOR uBoot menu (labelled '''*** BOOT MENU (NOR) ***''') just stay there, you do not need to select or enter any item in menu. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.

We often hear this comment: '''The screen goes dark before I do anything!!''' The FreeRunner only stays at the NOR boot prompt for about 30 seconds and then shuts off unless you do something. Be sure you are ready to enter commands on your desktop once you have booted.

Once the FreeRunner is at the NOR boot menu, then you can connect your Neo to the GNU/Linux or Windows host via a USB cable. If you have to boot back into NOR at this point (because you did not type fast enough!), pull the USB cable out first. Otherwise you will end up booting into the regular FreeRunner operating system. Got that? This is the routine:

# boot into NOR
# connect usb
# type dfu-util commands


Note that the dfu-util connection does '''not''' use Ethernet over USB - that is, you should not attempt to set up a usb0 network interface on your GNU/Linux host desktop (or the equivalent on Windows). The dfu-util utility sets up its own connection to the FreeRunner. In fact, you will not be able to make an Ethernet-over-USB connection to the FreeRunner when it is at the uBoot menu; this type of connection is only available when the FreeRunner has booted fully.

After connecting the FreeRunner to your host via USB cable, you can test whether dfu-util "sees" the FreeRunner by executing:

dfu-util -l

Sometimes I get error messages from the dfu-util command; I just try again. Often they work on the second try. Sometimes I have to boot into NOR again before things work. Once a connection has been made everything seems to work fine.
 

== Do a backup ==

If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]], although it looks like the method on that page may not entirely work.

''Is this still true? 7/31/08??''

== Using dfu-util ==

dfu-util can be used to read flash memory, write memory, and get information from the device.

This is the general command format to write an image file to a (predefined) "partition name" (referred to as ''altsetting'' in dfu-util help/manual) :

dfu-util -a ''altsetting'' -R -D ''file_name''

where: 
-a ''altsetting'' : Specify the altsetting of the DFU interface by name or by number 
-R : Issue USB Reset signalling once we're finished 
-D ''file_name'' : Write firmware from ''file_name'' into device

On Linux, you run dfu-util from a command shell prompt. If you have not put it somewhere on your command path you probably need to prefix it with a "./" like this '''./dfu-util'''.
On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

On Windows, you need to open a command window and run from a command line. Use Start-Run Program and type "cmd" to open a Window.

== Flashing the Kernel ==

The command format is

dfu-util -a kernel -R -D ''/path/to/uImage''

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the Root Filesystem ==

The root filesystem has to be an image in jffs2 format. If the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a rootfs -R -D ''rootfs_filename.jffs2''

where ''rootfs_filename.jffs2'' is the name of the file containing the root filesystem.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the boot loader to the NAND==

The boot loader (U-boot) file should have a .bin extension. As with the root filesystem, if the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a u-boot -R -D ''uboot.bin''

where ''uboot.bin'' is the name of the boot loader binary image file.

''Reminder'': You should have [[Flashing_the_Neo_FreeRunner#Boot_the_FreeRunner_from_NOR_Flash|rebooted from NOR first]], in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates.


(Optional) After an upgrade, you may wish to check that the u-boot version matches the one you have just flashed. You can use 'grep Bootloader /dev/mtdblock1' from a shell on the FreeRunner (and possibly the 1973 as well) to get the '''NAND''' u-boot version, like this:
root@om-gta02:~# grep Bootloader /dev/mtdblock1
Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb

You can grep for the same string in /dev/mtdblock0 to retrieve the '''NOR''' u-boot version:
root@om-gta02:~# grep Bootloader /dev/mtdblock0
Neo1973 Bootloader U-Boot 1.3.2-moko12



== Reboot the FreeRunner from NAND ==

You should now be able to boot into the new images.

Pay attention '''to booting from the NAND flash this time''', in particular if you upgraded the boot-loader (in short: 1. press and hold ''power button'' down, and then 2. press ''aux button'')

The boot menu should be labelled '''*** BOOT MENU (NAND) ***''' this time (see [[Booting#Log_into_U-Boot_in_the_NAND_Flash|booting from NAND]] for more detailed instructions).

[[Category:Flashing Openmoko| ]]

Qtopia / Qt Extended on FreeRunner

2008-08-07T18:31:49Z

Dewey: /* Installing Kernel */

This page provides instructions on how to install Qtopia (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (Freerunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==
On 18 July 2008, Qtopia released the [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=72 latest flash image for the FIC Neo Freerunner (gta02)] containing the Qtopia 4.3.2 snapshot of 17 July 2008 (GPL version).

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does not, however, have a web browser or a GPS application.

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia image from qtopia.net]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-*.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now extract the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]].

Now, tar up the root filesystem:

tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin to uImage.bin and copy it to the boot/ on the first partition of the MicroSD card.

{{note|There are reports that the kernel image sometimes does not work from the /boot directory. If this is the case for you, try moving the kernel image into the root of the microSD card, ie: /media/card instead of /media/card/boot. This is probably dependent on the version of U-Boot installed. It also doesn't hurt, seeing as there is room on the first partition, to simply have uImage.bin in both locations.}}

mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/
scp uImage.bin root@192.168.0.202:/media/card/

=== Option 3: updating from source ===

{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:

* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38
* unzip it on your PC in / (as root)
* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/
* once dowloaded untar it
tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080804.tar.gz
* make a "build" dir
mkdir build
cd build
* configure and make:
../qtopia-opensource-src-4.3.2-snapshot-20080804/configure -device ficgta01
make
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:

make install

will make a root directory into build directory. That directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.

=== Booting into Qtopia ===

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NOR Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.

[[Category:Distributions]]
[[Category:Qtopia]]

Dfu-util-windows

2008-08-01T17:23:42Z

Dewey: /* dfu-util for Win32 */

== dfu-util for Win32 ==

{{Note|This has been reported to work on Windows XP and Windows Vista with the Neo FreeRunner. No reports have been received on whether it works with other versions of Windows or with the Neo 1973}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. The LibUSB-Win32 driver and accompanying INF file for the OpenMoko can be found in OpenMokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH=" /c/msys/1.0/lib/pkgconfig"

ensuring that the path is accessible from the MSYS shell and points to the pkgconfig files.

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4553)
+++ main.c (working copy)
@@ -26,8 +26,10 @@
#include <getopt.h>
#include <usb.h>
#include <errno.h>
+#ifndef __MINGW32__
#include <byteswap.h>
#include <endian.h>
+#endif

#include "dfu.h"
#include "usb_dfu.h"
@@ -37,6 +39,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +585,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n", usb_strerror());
@@ -700,12 +720,18 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4553)
+++ sam7dfu.c (working copy)
@@ -20,6 +20,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4553)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

check your PKG_CONFIG_PATH (see above) to make sure it is correct, otherwise, you can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: OpenMoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Dfu-util-windows

2008-07-29T19:02:14Z

Dewey: /* Build dfu-util */

== dfu-util for Win32 ==

{{Note|This has only been tested on the developer's box and with the FreeRunner.}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. The LibUSB-Win32 driver and accompanying INF file for the OpenMoko can be found in OpenMokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH=" /c/msys/1.0/lib/pkgconfig"

ensuring that the path is accessible from the MSYS shell and points to the pkgconfig files.

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4553)
+++ main.c (working copy)
@@ -26,8 +26,10 @@
#include <getopt.h>
#include <usb.h>
#include <errno.h>
+#ifndef __MINGW32__
#include <byteswap.h>
#include <endian.h>
+#endif

#include "dfu.h"
#include "usb_dfu.h"
@@ -37,6 +39,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +585,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n", usb_strerror());
@@ -700,12 +720,18 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4553)
+++ sam7dfu.c (working copy)
@@ -20,6 +20,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4553)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

check your PKG_CONFIG_PATH (see above) to make sure it is correct, otherwise, you can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: OpenMoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Dfu-util-windows

2008-07-29T19:01:22Z

Dewey: /* MinGW/MSYS port */

== dfu-util for Win32 ==

{{Note|This has only been tested on the developer's box and with the FreeRunner.}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. The LibUSB-Win32 driver and accompanying INF file for the OpenMoko can be found in OpenMokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH=" /c/msys/1.0/lib/pkgconfig"

ensuring that the path is accessible from the MSYS shell and points to the pkgconfig files.

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4553)
+++ main.c (working copy)
@@ -26,8 +26,10 @@
#include <getopt.h>
#include <usb.h>
#include <errno.h>
+#ifndef __MINGW32__
#include <byteswap.h>
#include <endian.h>
+#endif

#include "dfu.h"
#include "usb_dfu.h"
@@ -37,6 +39,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +585,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n", usb_strerror());
@@ -700,12 +720,18 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4553)
+++ sam7dfu.c (working copy)
@@ -20,6 +20,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4553)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

You can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: OpenMoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Dfu-util-windows

2008-07-29T18:59:42Z

Dewey: Undo revision 42941 by Dewey (Talk)

== dfu-util for Win32 ==

{{Note|This has only been tested on the developer's box and with the FreeRunner.}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. The LibUSB-Win32 driver and accompanying INF file for the OpenMoko can be found in OpenMokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH="/msys/1.0/lib/pkgconfig"

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4553)
+++ main.c (working copy)
@@ -26,8 +26,10 @@
#include <getopt.h>
#include <usb.h>
#include <errno.h>
+#ifndef __MINGW32__
#include <byteswap.h>
#include <endian.h>
+#endif

#include "dfu.h"
#include "usb_dfu.h"
@@ -37,6 +39,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +585,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n", usb_strerror());
@@ -700,12 +720,18 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4553)
+++ sam7dfu.c (working copy)
@@ -20,6 +20,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4553)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

You can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: OpenMoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Dfu-util-windows

2008-07-29T18:43:20Z

Dewey: /* Build dfu-util */

== dfu-util for Win32 ==

{{Note|This has only been tested on the developer's box and with the FreeRunner.}}

In order to use dfu-util for Win32, you need to install a Windows driver when the device is in U-Boot. The LibUSB-Win32 driver and accompanying INF file for the OpenMoko can be found in OpenMokoDFU.zip at the link below. When the Windows New Device Wizard pops up, use this driver.

Once the driver is installed, then you can proceed and use the instructions found at the main [[dfu-util]] page.

The above mentioned files can be downloaded at: [http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

The information below is for developers who would like to know how to compile dfu-util for Win32.

== Porting dfu-util to Windows ==

{{Note|This is entirely work in progress. Nevertheless hopefully the information on this page will serve as a starting point for anyone who find the time to take this further. After all, as many people still use Windows PCs as their every day computers, having a convenient way to re-flash a Neo from Windows would probably open up the user base.}}

=== Potential Approaches ===

* Cygwin
: Not very attactive as Cygwin binaries require Cygwin in order to run. You will not get a simple, native dfu-util.exe which can be downloaded and used on any Windows machine that way.

* MinGW/MSYS
: MinGW (Minimalist GNU for Windows) seems to be the platform of choice.

* LibUSB-Win32
: Will only be able to be built on a Windows box

=== MinGW/MSYS port ===

The preferred order of installation is:

# Install MinGW (the core installation should be sufficient)
# Install MSYS (Note: make comes with MSYS while GCC comes with MinGW)

Here is step-by-step howto:

1. Download MinGW-5.1.4.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=240780&release_id=529741 and execute the installer. It will download additional files required and install MinGW.
: {{Note|It has often been a good idea to install into a directory that has no spaces in the filename.}}
2. Download MSYS-1.0.10.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=24963 and install.
: {{Note|Make sure to open the "Current Version: 1.0.10" folder as the newer version 1.0.11 does not have an installer yet.}}
You will need to enter the path where you installed MinGW. It's a good idea to install MinGW and MSYS next to each other, i.e. C:\SOMEDIR\MinGW and C:\SOMEDIR\MSYS.
: {{Note|For example if MinGW is installed in C:\MinGW enter 'C:/MinGW.' including the period.}}

3. Download msysDTK-1.0.1.exe from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044, which contains the autotools. Install into the same directory into which you installed MSYS itself. The installer might not automatically suggest the right directory.

That should give you an Icon in your Start menu in MinGW->MSYS with the name of msys. Open that one, and you will find yourself in a bourne compatible shell on your native Windows system.

You can try to execute some commends such as gcc, make, etc. to make sure you installed everything correctly.

4. Download autoconf 2.59 from http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=67879&release_id=131044. All you need to do to install it is to use a utility like [http://www.7-zip.org/ 7-Zip] to extract the files into your msys installation directory.

5. You will also need pkg-config. According to [http://www.mingw.org/MinGWiki/index.php/pkg-config http://www.mingw.org/MinGWiki/index.php/pkg-config], you need the following packages:

glib
glib-dev
libiconv
gettext
pkg-config

You can get all of these from the GTK+ for Windows page at: [http://www.gtk.org/download-windows.html http://www.gtk.org/download-windows.html]. Unzip them to your msys\1.0 directory.

6. Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH="/msys/1.0/lib/pkgconfig"

7. Download libusb-win32-device-bin-0.1.12.1.tar.gz from http://sourceforge.net/project/showfiles.php?group_id=78138&package_id=79216&release_id=495011. Then, copy the libusb.a file from the LibUSB-Win32\lib\gcc directory into the MinGW\lib directory and the usb.h file from LibUSB-Win32\include into MinGW\include (or you can copy it into your dfu-util\src directory).

8. Then you will need to create a libusb.pc file in the msys\1.0\lib\pkgconfig directory. I created the following:

prefix=c:/msys/1.0
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: LibUSB
Description: USB for Win32
Requires:
Version: 0.1.12.1
Libs: -L${libdir} -lusb
Cflags: -I${includedir}

=== Getting dfu-util sources ===

Use your favorite Subversion client to check out the dfu-util sources. The dfu-util sources can be checked out from [https://svn.openmoko.org/trunk/src/host/dfu-util/ https://svn.openmoko.org/trunk/src/host/dfu-util/].

=== Apply patch to compile with MinGW ===

Apply the following patch to the source code:

<pre>
Index: main.c
===================================================================
--- main.c (revision 4553)
+++ main.c (working copy)
@@ -26,8 +26,10 @@
#include <getopt.h>
#include <usb.h>
#include <errno.h>
+#ifndef __MINGW32__
#include <byteswap.h>
#include <endian.h>
+#endif

#include "dfu.h"
#include "usb_dfu.h"
@@ -37,6 +39,10 @@
#include "config.h"
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#endif
+
#ifdef HAVE_USBPATH_H
#include <usbpath.h>
#endif
@@ -579,6 +585,20 @@

/* FIXME: check if the selected device really has only one */

+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
+ printf("Setting Configuration %u...\n", dif->configuration);
+ if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
+ fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
+ exit(1);
+ }
+ dif->configuration = configuration;
+#endif
+
printf("Claiming USB DFU Runtime Interface...\n");
if (usb_claim_interface(_rt_dif.dev_handle, _rt_dif.interface) < 0) {
fprintf(stderr, "Cannot claim interface: %s\n", usb_strerror());
@@ -700,12 +720,18 @@
exit(1);
}

-#if 0
+#ifdef __MINGW32__
+ int configuration = dif->configuration;
+
+ if (configuration == 0) {
+ dif->configuration = 1;
+ }
printf("Setting Configuration %u...\n", dif->configuration);
if (usb_set_configuration(dif->dev_handle, dif->configuration) < 0) {
fprintf(stderr, "Cannot set configuration: %s\n", usb_strerror());
exit(1);
}
+ dif->configuration = configuration;
#endif
printf("Claiming USB DFU Interface...\n");
if (usb_claim_interface(dif->dev_handle, dif->interface) < 0) {
Index: sam7dfu.c
===================================================================
--- sam7dfu.c (revision 4553)
+++ sam7dfu.c (working copy)
@@ -20,6 +20,11 @@
#define O_BINARY 0
#endif

+#ifdef __MINGW32__
+#define sleep(seconds) Sleep((seconds)*1000)
+#define usleep(microseconds) Sleep((microseconds)/1000)
+#endif
+
int sam7dfu_do_upload(struct usb_dev_handle *usb_handle, int interface,
int xfer_size, const char *fname)
{
Index: usb_dfu.h
===================================================================
--- usb_dfu.h (revision 4553)
+++ usb_dfu.h (working copy)
@@ -12,6 +12,13 @@

#include <sys/types.h>

+#ifdef __MINGW32__
+#include <stdint.h>
+#define u_int8_t uint8_t
+#define u_int16_t uint16_t
+#define u_int32_t uint32_t
+#endif
+
#define USB_DT_DFU 0x21

struct usb_dfu_func_descriptor {
</pre>

=== Build dfu-util ===

In the Msys shell inside the dfu-util directory, run the following command:

./autogen.sh
./configure
make

dfu-util should successfully compile and you should have the .exe files in the src directory. In case you get the following error

checking for USB... configure: error: *** Required libusb >= 0.1.4 not installed ***

It means that it could not find the libusb.pc file mentioned earlier. Your PKG_CONFIG_PATH may not be set up properly. Try the following:

Open the file /etc/profile (C:\msys\1.0\etc\profile) with your favorite editor (make sure it uses LF line endings) and add:

PKG_CONFIG_PATH="/c/msys/lib/pkgconfig"

as described here: http://www.mingw.org/node/18 (modify the path to point to your pkgconfig directory of course), and restart your MSYS shell.

If that doesn't work, you can try running the following command (if you are sure that libusb is correctly installed):

./configure USB_CFLAGS=-Iinclude USB_LIBS=-lusb

=== Preparing to use dfu-util ===

A Windows driver needs to be installed when the device is in U-Boot and connected through the USB. Windows does not come with a DFU class driver and Jungo seems to be the only one that has created a DFU class driver, but it is non-free. You can use LibUSB-Win32 as the driver for the device by creating an INF file for it for this device. Use inf-wizard.exe, which is a part of the LibUSB-Win32 binaries distribution. Run the wizard, select the following device:

Vendor ID Product ID Description
0x1D50 0x5119 USB Device

Insert the Manufacturer name: OpenMoko, or FIC?

Insert device description: Device Firmware Upgrade

Then save the INF file along with the auto generated CAT files.

When you get the New Device Wizard when plugging in the device in U-Boot mode into Windows, select this newly generated INF file.

=== Running dfu-util ===

Once the Windows driver is successfully installed, you can try some commands:

dfu-util --list

and you should be able to list the device. Example:

Found Runtime: [0x1d50:0x5119] devnum=7, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"

=== Binary ===

[http://projects.openmoko.org/projects/dfu-util-win32/ http://projects.openmoko.org/projects/dfu-util-win32/]

=== Outstanding issues ===

Had to call usb_set_configuration() with configuration set to 1 before attempting to claim the device instead of using configuration 0 that the device returns. It sounds like DFU implementation in U-Boot might not be compliant with USB spec. A similar issue and discussion can be found here: [http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554 http://thread.gmane.org/gmane.comp.lib.libusb.devel.windows/1546/focus=1554]

[[Category:Flashing Openmoko]]

Flashing the Neo FreeRunner

2008-07-25T22:53:13Z

Dewey: /* Windows */ replaced https link with http link.

As Openmoko development continues, Openmoko regularly releases updated versions of the Openmoko root filesystem, the kernel, and the[[Bootloader| U-Boot]]. These may be programmed into the Flash memory of Neo FreeRunner. You can use the USB cable and Openmoko provided tool to flash Neo FreeRunner.

{{note|The Openmoko software team builds images daily. If you want to use the latest images, you can download the image from the daily build, but we recommend you download the most stable image from http://downloads.openmoko.org/releases/Freerunner/. Images here have been tested by the test team.

See [[Latest Images]] for more information about the different images available.}}
{{note|If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]], although it looks like the method on that page may not entirely work.}}

===Step 1. Download the DFU-util===

==== GNU/Linux ====

You can download the flashing tool for a GNU/Linux host from:
http://downloads.openmoko.org/releases/Freerunner/dfu-util

On the GNU/Linux host you can use the following command to download the dfu-util:
wget http://downloads.openmoko.org/releases/Freerunner/dfu-util

Afterwards you have to change the rights on the file:
chmod a+x dfu-util

==== Windows ====

You can download the flashing tool for a Windows host from: [http://projects.openmoko.org/frs/?group_id=166&release_id=162 http://projects.openmoko.org/frs/?group_id=166&release_id=162] (see installation instructions at [[Dfu-util-windows]])

===Step 2. Flashing the Kernel===

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:0px solid #ffffff; background:#ffffff; width:100%;floating="center";font-weight: normal; "
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid #ffffff; border:1px solid #ffffff; width:75%;font-weight: normal; " |
<div align="left">
[[Image:menu15.jpg|thumb|Log into U-Boot in NOR Flash, connect your Neo with Linux Host via USB cable]]

The Neo FreeRunner needs to be at the NOR uBoot menu for flashing. For more information on booting, see [[Booting the Neo FreeRunner| booting the Neo Freerunner]]. Log into the NOR uBoot menu and select Set console to USB. ''/Just stay in NOR uBoot menu to be able to connect via dfu-util. If selected and entered "Set console to USB", then dfu-util was unable to connect./'' Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.

'''Then''', connect your Neo to the GNU/Linux or Windows host via USB cable.

You can download the kernel from
http://downloads.openmoko.org/releases/Freerunner/

----
==== GNU/Linux ====

Type in the following command in the terminal on a GNU/Linux host. On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

./dfu-util -a (partion name) -R -D (download image file name)

or:

sudo ./dfu-util -a kernel -R -D uImage-2.6.24+git20080424-om-gta02.bin

==== Windows ====

Type in the following command in the console on a Windows host:

dfu-util -a kernel -R -D uImage-2.6.24+git20080424-om-gta02.bin

----

Press Enter to execute the command.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!
</div>
|}

{{note| The meaning of the parameters you specified:
-a --alt alt Specify the altsetting of the DFU interface by name or by number 
-R --reset Issue USB Reset signalling once we're finished 
-D --download file Write firmware from<file> into device 
}}

===Step 3. Flashing the Root Filesystem ===
You can download the root filesystem from:
http://downloads.openmoko.org/releases/Freerunner/

----

==== GNU/Linux ====

Type the following command in the terminal of a GNU/Linux host. On some systems you will need to be root.

./dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2

==== Windows ====

Type the following command in the console of a Windows host.

dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2

----

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

[[Category:Flashing Openmoko| ]]

Qtopia / Qt Extended on FreeRunner

2008-07-25T19:38:47Z

Dewey: /* Current status */

This page provides instructions on how to install Qtopia (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (Freerunner) phone. It is similar to the [[Qtopia on Neo1973]] page.

{|align=right
|__TOC__
|}

== Current status ==
On 18 July 2008, Qtopia released the [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=72 latest flash image for the FIC Neo Freerunner (gta02)] containing the Qtopia 4.3.2 snapshot of 17 July 2008 (GPL version).

This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does not, however, have a web browser or a GPS application.

== Option 1: Flashing Qtopia to FreeRunner ==

Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]

== Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==

Installation Requirements:

# SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)

=== Preparing the SD card ===

See the [[Booting from SD#Preparing the SD Card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions.

=== Installing Qtopia ===

==== Unpacking the Qtopia Root Filesystem Image ====

Download the Qtopia FLASH image from [[Latest Images#Qtopia image from qtopia.net]] to your Linux box and extract its contents:

tar xzf qtopia-4.3.2-gta02-flash-07172049.tgz

You should now have two files:
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2
Now extract the root file system from the jffs2 using the commands found at [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]].

Now, tar up the root filesystem:

tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .

Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted.

==== Installing Root Filesystem ====

Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:

scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/

Log in to your FreeRunner and unpack the root filesystem:

cd /media/mmcblk0p2
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz
rm -f /media/mmcblk0p2/boot/*

'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.

==== Installing Kernel ====

From your Linux box, rename uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin to uImage.bin and copy it to the boot/ on the first partition of the MicroSD card.

mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin
scp uImage.bin root@192.168.0.202:/media/card/boot/

=== Booting into Qtopia ===

Now shutdown the FreeRunner

shutdown -h now

Log into U-Boot in the NOR Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])

* Press and hold Power button
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.
* A boot menu will appear.
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.

Qtopia should now boot.

'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run

umount /dev/mmcblk0p2
fsck.ext3.e2fsprogs /dev/mmcblk0p2

This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.
[[category:Technical ]]
[[category:GTA02 Hardware]]

Backup

2008-07-25T19:35:02Z

Dewey:

You will need the [[Dfu-util]] to make a backup of your existing image.

As when [[Flashing_the_Neo_FreeRunner|flashing]], you will need to be in [[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|U-Boot in the NOR Flash]]. Log into the NOR uBoot menu and select ''Set console to USB''. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with [[Dfu-util|dfu-util]].

{{note|On a Windows host, omit the "./" or "sudo ./" that precedes the commands listed on this page}}

THIS WILL TAKE AWHILE. The rootfs will take significantly longer than the kernel.

<pre>
./dfu-util -a kernel -R -U good-kernel.bin
./dfu-util -a rootfs -R -U good-rootfs.jffs2
</pre>

Here is what my successful output looked like...

on the host PC:
<pre>
$ sudo ./dfu-util -a kernel -R -U good-kernel.img
dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=12, cfg=0, intf=0, alt=3, name="kernel"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
Resetting USB to switch back to runtime mode
$ sudo ./dfu-util -a rootfs -R -U good-rootfs.jffs2
dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Found Runtime: [0x1d50:0x5119] devnum=16, cfg=0, intf=0, alt=6, name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuERROR, status = 14
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
Resetting USB to switch back to runtime mode
</pre>

Despite the fact that there was a device status with state=dfuERROR, everything seems to have worked.

on the FreeRunner:
<pre>
DFU: Switching to DFU Mode
DEVICE_CONFIGURED: 1
Starting DFU Upload of partition 'kernel'
DEVICE_CONFIGURED: 1
Starting DFU Upload of partition 'rootfs'
</pre>

I could backup the kernel of my GTA02 but trying to use this method to backup the rootfs failed several times....
dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=20, cfg=0, intf=0, alt=6, name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
dfu_upload error -110

In demsg I get this error
usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110

I have not been able to backup rootfs using this method.
[[category:Software]]
[[category:Technical]]

Flashing the Neo FreeRunner

2008-07-25T19:27:04Z

Dewey: Added instructions for a Windows host.

As Openmoko development continues, Openmoko regularly releases updated versions of the Openmoko root filesystem, the kernel, and the[[Bootloader| U-Boot]]. These may be programmed into the Flash memory of Neo FreeRunner. You can use the USB cable and Openmoko provided tool to flash Neo FreeRunner.

{{note|The Openmoko software team builds images daily. If you want to use the latest images, you can download the image from the daily build, but we recommend you download the most stable image from http://downloads.openmoko.org/releases/Freerunner/. Images here have been tested by the test team.

See [[Latest Images]] for more information about the different images available.}}
{{note|If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]], although it looks like the method on that page may not entirely work.}}

===Step 1. Download the DFU-util===

==== GNU/Linux ====

You can download the flashing tool for a GNU/Linux host from:
http://downloads.openmoko.org/releases/Freerunner/dfu-util

On the GNU/Linux host you can use the following command to download the dfu-util:
wget http://downloads.openmoko.org/releases/Freerunner/dfu-util

Afterwards you have to change the rights on the file:
chmod a+x dfu-util

==== Windows ====

You can download the flashing tool for a Windows host from: https://projects.openmoko.org/frs/?group_id=166 (see installation instructions at [[Dfu-util-windows]])

===Step 2. Flashing the Kernel===

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:0px solid #ffffff; background:#ffffff; width:100%;floating="center";font-weight: normal; "
! style="background:#ffffff;border-left:1px solid #ffffff;border-right:1px ; border-top:2px solid #ffffff; border:1px solid #ffffff; width:75%;font-weight: normal; " |
<div align="left">
[[Image:menu15.jpg|thumb|Log into U-Boot in NOR Flash, connect your Neo with Linux Host via USB cable]]

The Neo FreeRunner needs to be at the NOR uBoot menu for flashing. For more information on booting, see [[Booting the Neo FreeRunner| booting the Neo Freerunner]]. Log into the NOR uBoot menu and select Set console to USB. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.

'''Then''', connect your Neo to the GNU/Linux or Windows host via USB cable.

You can download the kernel from
http://downloads.openmoko.org/releases/Freerunner/

----
==== GNU/Linux ====

Type in the following command in the terminal on a GNU/Linux host. On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

./dfu-util -a (partion name) -R -D (download image file name)

or:

sudo ./dfu-util -a kernel -R -D uImage-2.6.24+git20080424-om-gta02.bin

==== Windows ====

Type in the following command in the console on a Windows host:

dfu-util -a kernel -R -D uImage-2.6.24+git20080424-om-gta02.bin

----

Press Enter to execute the command.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!
</div>
|}

{{note| The meaning of the parameters you specified:
-a --alt alt Specify the altsetting of the DFU interface by name or by number 
-R --reset Issue USB Reset signalling once we're finished 
-D --download file Write firmware from<file> into device 
}}

===Step 3. Flashing the Root Filesystem ===
You can download the root filesystem from:
http://downloads.openmoko.org/releases/Freerunner/

----

==== GNU/Linux ====

Type the following command in the terminal of a GNU/Linux host. On some systems you will need to be root.

./dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2

==== Windows ====

Type the following command in the console of a Windows host.

dfu-util -a rootfs -R -D openmoko-devel-image-fic-gta02.jffs2

----

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

[[Category:Flashing Openmoko| ]]

Qtopia / Qt Extended on FreeRunner

2008-07-25T19:16:10Z

Dewey: Added option to flash the freerunner instead of dual-booting