Openmoko - User contributions [en]

Wiki Maintainers

2008-07-27T02:07:32Z

Cheetah100: /* Members */

== Goals ==

* Maintain integrity and correctness of information
* Organize and maintain page content and layout
* Clean up and consolidate pages and categories
* Reduce clutter and confusion for users
* Work with OpenMoko to maintain an offline-capable version

== Members ==

* [[User:Nuclear_Eclipse|John Reese (Nuclear_Eclipse)]]
* [[User:Tingo|Torfinn Ingolfsen]]
* [[User:Iandouglas|Ian Douglas]]
* Jay Vaughan
* Ken Young
* [[User:Vvaidy|Vijay Vaidyanathan]]
* Ken Restivo
* Josh Monson (westcoastmonson)
* Matt Joyce
* [[User:MicRenda|Michele Renda]] (Italian version)
* [[User:stryderjzw|Justin Wong]]
* [[User:Kempelen|Ferenc Veres]]
* [[User:Cheetah100|Peter Harrison]]

== Tools ==

* [[Openmoko_Wiki_Editing_Guidelines]]
* [[Wiki_Issues]]
* [[Wiki_maintain_agenda]]
* [[Openmoko_Wiki_Official_Index_Page]]
* [[:Category:Candidates_for_speedy_deletion]]
* [[Special:Categories]]
* [[:Category:Categories]]
* [[:Category:Templates]]

[[Category:Community]]

Talk:Wiki Maintainers

2008-07-21T03:31:49Z

Cheetah100:

Feedback and advice is always welcome!

* Will volunteer to help maintain this in anyway, shape, or form. Would like to see direction come from Brenda, if not someone designated by her. I think as a group we can make a huge impact on this wiki, but in order for us to come up w/ some process, organization, and editing rules I feel that OM needs to endorse this. -westcoastmonson

* I won't put my name down yet, but I'll probably end up involved in Wiki editing once I get my Freerunner and start wanting to find information... Consider me an interested party. [[User:Darksatanic|Darksatanic]] 21:28, 15 July 2008 (UTC)

* I'd love to take a crack at a better Getting Started for Brand New OpenMoko Developers - from after you have unwrapped your phone to "Hello World". The confusion over which Distro to use, and the constant references in the Wiki to the Neo 1973 sure dont help :-) - [[User:Vvaidy|Vijay]]
** I agree. I think where there is commonality between various Openmoko products, pages should be shared, but the distinctions should be teased out. If that means editing some 1973 pages, so be it. - Matt

* biggest issue is reorganizing the pages into something that makes more sense, and keeping Brenda involved since she's in charge of the wiki as an OpenMoko employee. Secondary concern is that everyone who signs up understands wiki syntax - [[User:Iandouglas|Ian Douglas]]

* I agree - we want to have Brenda in on this (be it as leader, advisor or both). As for understanding Wiki syntax, I'll settle for peope that are willing to learn it. [[User:Tingo|Tingo]] 05:40, 16 July 2008 (UTC)

* I'm also not willing to be an official maintainer, but expect to contribute lots of edits. I don't really understand why references to the Neo 1973 are confusing. The company has two very similar devices and it's simply more efficient to discuss the same topic with respect to each in the same place. If someone really wants to duplicate such similar content in two separate places, go for it, but that's a lot of work for little payback, when we could instead educate wiki users that there are two devices out there. The main thing I think the maintainers should focus on initially is getting a very organized front page and better search functionality in place. Those two things prevent people from finding what they are looking for. The search is just abysmal and I can't even find pages I know I've edited in the past using the search. The front page cannot link to everything, but it should try to hit the main things people are looking for and also provide a prominent link to a more comprehensive index that can be used when the front page doesn't have what you're looking for. We might ask OpenMoko if they'd be willing to give us some website stats on the wiki so that we know which pages ARE most-visited and then could be sure to include those on the front page. - [[User:Brianwc|Brianwc]]

*I would like to spend time helping out with maintaining the Wiki. I feel that the future of the OpenMoko project will be determined by the community around it, not by advanced technology. We need to aim for involvement with many vertical market specialists, and they will need to be comfortable with the support infrastructure. The Wiki and other community tools will be central to this effort. I look forward to contributing. [[User:Cheetah100|Cheetah100]]

** The navigation menu has a link to the Wiki Index Page, and Brenda mails monthly stats to the community mailing list. - [[User:Nuclear_Eclipse|John Reese]]

User:Cheetah100

2008-06-28T11:06:26Z

Cheetah100: New page: == Peter Harrison == == In Open Source: == Peter Harrison was the founder of the New Zealand Open Source Society, and was President of the society from 2002 to 2007. During this time he ...

== Peter Harrison ==

== In Open Source: ==

Peter Harrison was the founder of the New Zealand Open Source Society, and was President of the society from 2002 to 2007. During this time he was involved with oppositions to Microsoft patents, and presented submissions before parliamentary committees considering copyright law. He has been a contributor to various open source projects, and wrote a book about Tomcat the open source Java web server in 2002.

== Involvement with Openmoko ==

Peter became interested in the Openmoko project in 2007 as it provided an excellent platform for his robotic boat project. Most of the boat was completed before he acquired the Neo itself. The software and hardware interfaces were tested before the Neo 1973 was purchased. After the Neo was obtained off eBay the required OS modifications were made to support host USB, the required packages installed to run python, and scripts written to enable GPS and GPRS.

== Openmoko Contributions ==

Peter has contributed some documentation modifications on the OpenMoko Wiki around configuring GPRS.

Openmoko Local Groups: Auckland

2008-06-28T10:44:35Z

Cheetah100:

{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
|-
|[[User:Myfanwy|Myfanwy]]
|Hardware engineering, design and manufacture
|User, possibly developer later
|Auckland city
|
|
|-
|[[User:BlueLightning|BlueLightning]]
|Software development
|Developer (nothing contributed yet)
|North Shore
|
|[[Image: Moko.jpg|center]]
|-
|[[User:Cheetah100|Cheetah100]]
|Software development, Robotics
|Would like to contribute
|North Shore
|
|[[Image: Moko.jpg|center]]
|-
|
|
|
|
|
|
|}

[[Category:Community]]
[[Category: OpenMoko Local Groups| ]]

Toolchain

2008-03-22T22:17:54Z

Cheetah100: /* Prerequisites */

= Introduction =

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

== Developing a single application ==

For this, you should use a prebuilt toolchain from the OpenMoko project. Here you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. You might have heard about [[OpenEmbedded]], however as an application programmer, you should '''not''' be using [[OpenEmbedded]].

== System Integration and customizing a distribution ==

For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.

=Basic toolchain usage=

==Prerequisites==

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

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

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

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

* For ubuntu (7.10) the following is required:
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev ccache libxrender-dev intltool

==Downloading and installing==

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

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

mkdir ~/sources
cd ~/sources

* Depending on your CPU type (x86_64 or i686) download the proper package:

wget http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
or
wget http://downloads.openmoko.org/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2

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

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

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

* On Debian-based systems, you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2 (install with dpkg -i <package.deb>):

bunzip2 openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
gzip openmoko-x86_64-arm-linux-gnueabi-toolchain.tar
fakeroot alien -d openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.gz

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

bitbake meta-toolchain-openmoko

Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to source it.
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need
to start "sh" or "bash" first.

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

==Building a sample project==

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

* copy the downloaded sample application source:

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

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

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

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

om-conf openmoko-sample2

* Optionally now you can modify the source code in openmoko-sample2/src

* To build the application from the source code you only need to use "make":

cd openmoko-sample2
make

If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.

om-conf --prefix=/usr/local/openmoko openmoko-sample2
cd openmoko-sample2
make install

==How to modify the sample project==

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

* copy the downloaded sample application source

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

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

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

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

cp your-sources .
cd ..

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

PKG_NAME="your-project-name"

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

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

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

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

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

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

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

dist_desktop_DATA = smart-search.desktop
dist_appicon_DATA = smart-search.png

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

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

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

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

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

==Packaging your application==

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

om-make-ipkg openmoko-sample2

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

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

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

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

om-make-ipkg myapp myapp_control

A template of myapp_control:

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

==Where to go from here==

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

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

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

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

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

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

That's it.

==Getting your application packaged by OE==

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

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

See also [[Customizing your OpenMoko distribution]].

==Troubleshooting==

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

{{Languages|Toolchain}}
[[Category:Software ]]
[[Category:Application Developer]]
[[Category:Openmoko]]

Gllin

2008-03-21T00:55:28Z

Cheetah100:

gllin is an userpsace driver for a hammerhead [[GPS]] chip. It was distributed on phase1 openmokos.

Thanks to a tremendous amount of hard work by many people, we have ready
a release of gllin, the GPS drives. Here is how you can get it:

http://3rdparty.downloads.openmoko.org/gllin/

Instructions, how to use the driver, are given at:

http://lists.openmoko.org/pipermail/community/2007-November/011916.html.

The similar instructions are described in more details at [[getting GPS console output with gllin]].

Unfortunately, gllin expects paths such as /sys/bus/platform/devices/gta01-pm-gps.0/pwron ... and 2.6.24 kernel provides neo1973-pm-gps.0 instead :-(.

-- The following steps seem to be not necessary (anymore?). -- [[User:Homyx|homyx]] Mar 08, 2008

<pre>
root@fic-gta01:/media/card/home/root/gllin# cat gllin.real | grep /sys/bus/platform/devices/
/sys/bus/platform/devices/gta01-pm-gps.0/reset
...

root@fic-gta01:/sys/bus/platform/devices# ls -l gta01-pm-gps.0
lrwxrwxrwx 1 root root 0 Mar 8 11:01 gta01-pm-gps.0 -> ../../../devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/neo1973-pm-gps.0
root@fic-gta01:/sys/bus/platform/devices# ls -l neo1973-pm-gps.0
lrwxrwxrwx 1 root root 0 Mar 8 11:01 neo1973-pm-gps.0 -> ../../../devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/neo1973-pm-gps.0
root@fic-gta01:/sys/bus/platform/devices# uname -a
Linux fic-gta01 2.6.24 #1 PREEMPT Wed Mar 5 00:16:31 UTC 2008 armv4tl unknown
</pre>

Fortunately, you can do evil hack:

<pre>
cat gllin.real | sed 's-/sys/-/s/s/-g' > gllin.real2
mkdir -p /s/s/bus/platform/devices/
ln -s /sys/bus/platform/devices/neo1973-pm-gps.0/ /s/s/bus/platform/devices/gta01-pm-gps.0
</pre>

''WARNING:The first step above should not be executed on the phone itself, as BusyBox's sed will corrupt the binary file. It worked for me when run on my host (thanks balrog-kun!)
''
<pre>
# gllin.real2 was produced by BusyBox sed
lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real2 -low 5
/home/root/gllin/gllin.real2: error while loading shared libraries: /home/root/gllin/gllin.real2: ELF file version does not match current one

# gllin.real3 was produced by GNU sed version 4.1.5
$ lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real3 -low 5
GPSpwr "1" > /s/s/bus/platform/devices/gta01-pm-gps.0/power_lp_io_3v3
GPSpwr "1" > /s/s/bus/platform/devices/gta01-pm-gps.0/power_lp_io_3v3
...
</pre>

-- I didn't do the above steps; instead I just linked the old directory to the new one. No sed black magic was required. See below. -- [[User:Wurp]] Mar 12, 2008

-- The below link appears not to work - giving a "No such file or directory" error when trying to create any file in this directory. This is with the 20 Feb build. -- [[User:Cheetah100]] Mar 21, 2008

<pre>
cd /sys/bus/platform/devices/
ln -s neo1973-pm-gps.0 gta01-pm-gps.0
</pre>

== gllin options ==

The /home/root/gllin/gllin file installed by the new (legitimate!) .ipk package is really just a shell script. You can modify the options passed to gllin.real by editing that script. Here are the options:
<pre>
Usage:

-help Help
-board <type> Defines board type Ex: '-board matchbox'
supported: matchbox, trident
-com <com port> GPS com port; Ex: '-com com6'
-baud <baud rate> Set baud rate; Ex: '-baud 115200'
-rft <RF type> Set RF type; Ex: '-rft RF_LN22OUT'
-freq <freq plan> | ? set frequency plan for GPS or show the list of all available plans
Ex: '-freq FRQ_PLAN_OCXO_10000'
Ex: '-freq ?' -- Show all available plans
-g <URL> SUPL Server URL or IP address;
Ex: '-g 216.15.9.46'
-p <port> SUPL Server port number;
Ex: '-p 9118'
-udp <port> Local UDP port to send NMEA to.
'-udp 6000' [default]
-gsm_cell <cell ID> set GSM Cell ID information
cell ID has the following format: '<MCC>.<MNC>.<LAC>.<CI>'
Where:
MCC - Mobile Country Code
MNC - Mobile Network Code
LAC - Location Area Code
CI - Cell Identification
Ex: '-gsm_cell 310.170.367.25732'
-set_assisted_off disable SET assisted capability
-set_based_off disable SET based capability
-msisdn <MSISDN> set value for MSISDN (international phone number) as SET id
Ex: '-msisdn 14081234567'
-nai <nai> specify Network Access Identifier as SET id
Ex: '-nai 12345@mywebsite.com'
-periodic <s> make periodic request every s second (-1 to 64)
-1 single shot: perform one fix, then quit
0 native: perform fixes as fast as possible
<s> timed: report a position every <s> seconds
where <s> is 1 to 64
-recover recover GLLIN after signaled exit
-low [<count>] low level test. Default <count> is 1
-low_debug Low level debug ON
+low_debug Low level debug OFF
-train <count> Send train data <count> times
+pty | -pty Enable or disable NMEA output to pty "/tmp/nmeaPTY"
Default is off [-pty]
+np | -np Enable or disable NMEA output to named pipe "/tmp/nmeaNP"
Default is on [-np]
+nmea | -nmea Enable or disable NMEA output to log file
Default is off [-nmea]
+daemon | -daemon Become a daemon (or not)
Default is -daemon
-a2 | -a3 | -a0 Select a GTA01 board revision. Default is a3
-batch <st> <n> <fix> perform batch test of <n> starts of type <st>
<st> is hot, warm, cold, or SNR.
Each start has <fix> fixes.
-i start GLLIN command line
+pnd optimize for PND
-pnd look for low signal strength signals
+sim using simulator so don't use almanac
-sim not using simulator
SNR manufacturing SNR test mode
hot hot start [default]
warm warm start
cold cold start
-v[n] Report GLLIN version string.
n is 1234 to report selected versions.
version 1.1.7
</pre>

== Using gpsd with gllin ==

edit /etc/default/gpsd and set the GPS_DEV to /tmp/nmeaNP start gpsd before gllin.

== Some notes: ==

The listed defaults don't seem to be correct. By default it DOES generate NMEA data in log files. These log files are on your flash (/home/root/gllin/log/*) and are written to once every second. Ridiculous!

To stop this, add the option "-nmea" to the second of the two gllin.real commands in the startup script.

But note further that the startup script also spawns a command to 'cat' the output of the /tmp/nmeaNP named pipe to a gzipped file in /home/root. If you want this to stop, you can do one of two things:

* cat to /dev/null instead of | gzip >> file

* add "-np" to the second gllin.real command

You can't just take the 'cat' command out of the script, because with the named pipe activated, gllin will QUIT if it doesn't see anybody taking the output from the pipe. To keep it going, either open that pipe or turn it off.

You can use this [http://obri.sygroup.ch/gllin gllin initscript] to start and stop gllin.

Another option:
#!/bin/sh
echo "Starting gllin..."

killall cat
killall gllin.real

mknod /tmp/nmeaNP p
cat /tmp/nmeaNP > /dev/null &
cd /home/root/gllin
lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real -low 5
lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real -periodic 1 -nmea

== More Initscripts ==

The gllin package doesn't come with a very good set of initscripts, and gpsd is flexible enough to use gllin or some other source of GPS coordinates.

For gpsd and gllin to run together well, upon boot, the following scripts have worked well for me:

/etc/init.d/gpsd:
<pre>
#!/bin/sh
#
# gpsd This shell script starts and stops gpsd.
#
# chkconfig: 345 90 40
# description: Gpsd manages access to a serial- or USB-connected GPS
# processname: gpsd

# Source function library.
#. /etc/rc.d/init.d/functions

RETVAL=0
prog="gpsd"

test -f /etc/default/${prog} && . /etc/default/${prog}

start() {
# Start daemons.
echo -n "Starting ${prog}: "
# We don't use the daemon function here because of a known bug
# in initlog -- it spuriously returns a nonzero status when
# starting daemons that fork themselves. See
# http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130629
# for discussion. Fortunately:
#
# 1. gpsd startup can't fail, or at least not in the absence of
# much larger resource-exhaustion problems that would be very obvious.
#
# 2. We don't need all the logging crud that daemon/initlog sets
# up -- gpsd does its own syslog calls.
#

if [ -e "${GPS_DEV}" ]
then
${prog} -n ${GPSD_OPTS} ${GPS_DEV}
RETVAL=$?
echo "success"
else
# User needs to symlink ${GPS_DEV} to the right thing
# Do it automatically if the name contains "NP"
if echo ${GPS_DEV} | grep -q NP
then
mknod ${GPS_DEV} p
${prog} -n ${GPSD_OPTS} ${GPS_DEV}
RETVAL=$?
echo "success"
else
RETVAL=$?
echo "No ${GPS_DEV} GPS device, aborting gpsd startup. Check /etc/default/${prog}"
fi
fi
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/gpsd
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down ${prog}: "
killall ${prog}
RETVAL=$?
echo
if [ $RETVAL -eq 0 ]
then
test -e /var/lock/subsys/gpsd && rm -f /var/lock/subsys/gpsd;
fi
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
condrestart)
if [ -f /var/lock/subsys/gpsd ]; then
stop
start
RETVAL=$?
fi
;;
status)
# status gpsd
# RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac

exit $RETVAL
</pre>

/etc/init.d/gllin:
<pre>
#!/bin/sh
#
# This shell script starts and stops gllin.
#

RETVAL=0
prog="gllin"
GLLIN_PATH=/home/root/gllin

test -f /etc/default/${prog} && . /etc/default/${prog}

start() {
# Make fifo if it doesn't already exist
if [ ! -p /tmp/nmeaNP ]
then
mknod /tmp/nmeaNP p
fi

# Check for gpsd ready (max 5 seconds)
echo -n "Waiting for gpsd . . . "
sleep 1
if [ ! "$(pidof gpsd)" ]
then
sleep 4
if [ ! "$(pidof gpsd)" ]
then
RETVAL=1
echo "failure."
return $RETVAL
fi
fi

# Start daemons.
echo -n "starting ${prog}: "
cd $GLLIN_PATH
sleep 1
if [ -e $GLLIN_PATH/${prog}.real ]
then
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog}.real -low 5 > /dev/null
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog}.real -periodic 1 +daemon
else
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog} -low 5 > /dev/null
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog} -periodic 1 +daemon
fi
echo "success."
RETVAL=$?
echo
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down ${prog}: "
pkill ld-linux.so.2
RETVAL=$?
echo "success."
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
status)
# RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac

exit $RETVAL
</pre>

These scripts allow you (or init, if you have them numbered in rcX.d appropriately) to start gpsd *before* gllin. This way, gpsd starts listening on /tmp/nmeaNP immediately, and gllin doesn't need to send output to /dev/null in order to stay alive.

This version of the gpsd script will create the named pipe (if the device name includes "NP" in the filename) if it doesn't exist.

Gllin

2008-03-21T00:53:51Z

Cheetah100:

gllin is an userpsace driver for a hammerhead [[GPS]] chip. It was distributed on phase1 openmokos.

Thanks to a tremendous amount of hard work by many people, we have ready
a release of gllin, the GPS drives. Here is how you can get it:

http://3rdparty.downloads.openmoko.org/gllin/

Instructions, how to use the driver, are given at:

http://lists.openmoko.org/pipermail/community/2007-November/011916.html.

The similar instructions are described in more details at [[getting GPS console output with gllin]].

Unfortunately, gllin expects paths such as /sys/bus/platform/devices/gta01-pm-gps.0/pwron ... and 2.6.24 kernel provides neo1973-pm-gps.0 instead :-(.

-- The following steps seem to be not necessary (anymore?). -- [[User:Homyx|homyx]] Mar 08, 2008

<pre>
root@fic-gta01:/media/card/home/root/gllin# cat gllin.real | grep /sys/bus/platform/devices/
/sys/bus/platform/devices/gta01-pm-gps.0/reset
...

root@fic-gta01:/sys/bus/platform/devices# ls -l gta01-pm-gps.0
lrwxrwxrwx 1 root root 0 Mar 8 11:01 gta01-pm-gps.0 -> ../../../devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/neo1973-pm-gps.0
root@fic-gta01:/sys/bus/platform/devices# ls -l neo1973-pm-gps.0
lrwxrwxrwx 1 root root 0 Mar 8 11:01 neo1973-pm-gps.0 -> ../../../devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/neo1973-pm-gps.0
root@fic-gta01:/sys/bus/platform/devices# uname -a
Linux fic-gta01 2.6.24 #1 PREEMPT Wed Mar 5 00:16:31 UTC 2008 armv4tl unknown
</pre>

Fortunately, you can do evil hack:

<pre>
cat gllin.real | sed 's-/sys/-/s/s/-g' > gllin.real2
mkdir -p /s/s/bus/platform/devices/
ln -s /sys/bus/platform/devices/neo1973-pm-gps.0/ /s/s/bus/platform/devices/gta01-pm-gps.0
</pre>

''WARNING:The first step above should not be executed on the phone itself, as BusyBox's sed will corrupt the binary file. It worked for me when run on my host (thanks balrog-kun!)
''
<pre>
# gllin.real2 was produced by BusyBox sed
lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real2 -low 5
/home/root/gllin/gllin.real2: error while loading shared libraries: /home/root/gllin/gllin.real2: ELF file version does not match current one

# gllin.real3 was produced by GNU sed version 4.1.5
$ lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real3 -low 5
GPSpwr "1" > /s/s/bus/platform/devices/gta01-pm-gps.0/power_lp_io_3v3
GPSpwr "1" > /s/s/bus/platform/devices/gta01-pm-gps.0/power_lp_io_3v3
...
</pre>

-- I didn't do the above steps; instead I just linked the old directory to the new one. No sed black magic was required. See below. -- [[User:Wurp]] Mar 12, 2008
-- The below link appears not to work - giving a "No such file or directory" error when trying to create any file in this directory. -- [[User:Cheetah100]]
<pre>
cd /sys/bus/platform/devices/
ln -s neo1973-pm-gps.0 gta01-pm-gps.0
</pre>

== gllin options ==

The /home/root/gllin/gllin file installed by the new (legitimate!) .ipk package is really just a shell script. You can modify the options passed to gllin.real by editing that script. Here are the options:
<pre>
Usage:

-help Help
-board <type> Defines board type Ex: '-board matchbox'
supported: matchbox, trident
-com <com port> GPS com port; Ex: '-com com6'
-baud <baud rate> Set baud rate; Ex: '-baud 115200'
-rft <RF type> Set RF type; Ex: '-rft RF_LN22OUT'
-freq <freq plan> | ? set frequency plan for GPS or show the list of all available plans
Ex: '-freq FRQ_PLAN_OCXO_10000'
Ex: '-freq ?' -- Show all available plans
-g <URL> SUPL Server URL or IP address;
Ex: '-g 216.15.9.46'
-p <port> SUPL Server port number;
Ex: '-p 9118'
-udp <port> Local UDP port to send NMEA to.
'-udp 6000' [default]
-gsm_cell <cell ID> set GSM Cell ID information
cell ID has the following format: '<MCC>.<MNC>.<LAC>.<CI>'
Where:
MCC - Mobile Country Code
MNC - Mobile Network Code
LAC - Location Area Code
CI - Cell Identification
Ex: '-gsm_cell 310.170.367.25732'
-set_assisted_off disable SET assisted capability
-set_based_off disable SET based capability
-msisdn <MSISDN> set value for MSISDN (international phone number) as SET id
Ex: '-msisdn 14081234567'
-nai <nai> specify Network Access Identifier as SET id
Ex: '-nai 12345@mywebsite.com'
-periodic <s> make periodic request every s second (-1 to 64)
-1 single shot: perform one fix, then quit
0 native: perform fixes as fast as possible
<s> timed: report a position every <s> seconds
where <s> is 1 to 64
-recover recover GLLIN after signaled exit
-low [<count>] low level test. Default <count> is 1
-low_debug Low level debug ON
+low_debug Low level debug OFF
-train <count> Send train data <count> times
+pty | -pty Enable or disable NMEA output to pty "/tmp/nmeaPTY"
Default is off [-pty]
+np | -np Enable or disable NMEA output to named pipe "/tmp/nmeaNP"
Default is on [-np]
+nmea | -nmea Enable or disable NMEA output to log file
Default is off [-nmea]
+daemon | -daemon Become a daemon (or not)
Default is -daemon
-a2 | -a3 | -a0 Select a GTA01 board revision. Default is a3
-batch <st> <n> <fix> perform batch test of <n> starts of type <st>
<st> is hot, warm, cold, or SNR.
Each start has <fix> fixes.
-i start GLLIN command line
+pnd optimize for PND
-pnd look for low signal strength signals
+sim using simulator so don't use almanac
-sim not using simulator
SNR manufacturing SNR test mode
hot hot start [default]
warm warm start
cold cold start
-v[n] Report GLLIN version string.
n is 1234 to report selected versions.
version 1.1.7
</pre>

== Using gpsd with gllin ==

edit /etc/default/gpsd and set the GPS_DEV to /tmp/nmeaNP start gpsd before gllin.

== Some notes: ==

The listed defaults don't seem to be correct. By default it DOES generate NMEA data in log files. These log files are on your flash (/home/root/gllin/log/*) and are written to once every second. Ridiculous!

To stop this, add the option "-nmea" to the second of the two gllin.real commands in the startup script.

But note further that the startup script also spawns a command to 'cat' the output of the /tmp/nmeaNP named pipe to a gzipped file in /home/root. If you want this to stop, you can do one of two things:

* cat to /dev/null instead of | gzip >> file

* add "-np" to the second gllin.real command

You can't just take the 'cat' command out of the script, because with the named pipe activated, gllin will QUIT if it doesn't see anybody taking the output from the pipe. To keep it going, either open that pipe or turn it off.

You can use this [http://obri.sygroup.ch/gllin gllin initscript] to start and stop gllin.

Another option:
#!/bin/sh
echo "Starting gllin..."

killall cat
killall gllin.real

mknod /tmp/nmeaNP p
cat /tmp/nmeaNP > /dev/null &
cd /home/root/gllin
lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real -low 5
lib/ld-linux.so.2 --library-path /home/root/gllin/lib:/home/root/gllin/usr/lib /home/root/gllin/gllin.real -periodic 1 -nmea

== More Initscripts ==

The gllin package doesn't come with a very good set of initscripts, and gpsd is flexible enough to use gllin or some other source of GPS coordinates.

For gpsd and gllin to run together well, upon boot, the following scripts have worked well for me:

/etc/init.d/gpsd:
<pre>
#!/bin/sh
#
# gpsd This shell script starts and stops gpsd.
#
# chkconfig: 345 90 40
# description: Gpsd manages access to a serial- or USB-connected GPS
# processname: gpsd

# Source function library.
#. /etc/rc.d/init.d/functions

RETVAL=0
prog="gpsd"

test -f /etc/default/${prog} && . /etc/default/${prog}

start() {
# Start daemons.
echo -n "Starting ${prog}: "
# We don't use the daemon function here because of a known bug
# in initlog -- it spuriously returns a nonzero status when
# starting daemons that fork themselves. See
# http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130629
# for discussion. Fortunately:
#
# 1. gpsd startup can't fail, or at least not in the absence of
# much larger resource-exhaustion problems that would be very obvious.
#
# 2. We don't need all the logging crud that daemon/initlog sets
# up -- gpsd does its own syslog calls.
#

if [ -e "${GPS_DEV}" ]
then
${prog} -n ${GPSD_OPTS} ${GPS_DEV}
RETVAL=$?
echo "success"
else
# User needs to symlink ${GPS_DEV} to the right thing
# Do it automatically if the name contains "NP"
if echo ${GPS_DEV} | grep -q NP
then
mknod ${GPS_DEV} p
${prog} -n ${GPSD_OPTS} ${GPS_DEV}
RETVAL=$?
echo "success"
else
RETVAL=$?
echo "No ${GPS_DEV} GPS device, aborting gpsd startup. Check /etc/default/${prog}"
fi
fi
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/gpsd
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down ${prog}: "
killall ${prog}
RETVAL=$?
echo
if [ $RETVAL -eq 0 ]
then
test -e /var/lock/subsys/gpsd && rm -f /var/lock/subsys/gpsd;
fi
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
condrestart)
if [ -f /var/lock/subsys/gpsd ]; then
stop
start
RETVAL=$?
fi
;;
status)
# status gpsd
# RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac

exit $RETVAL
</pre>

/etc/init.d/gllin:
<pre>
#!/bin/sh
#
# This shell script starts and stops gllin.
#

RETVAL=0
prog="gllin"
GLLIN_PATH=/home/root/gllin

test -f /etc/default/${prog} && . /etc/default/${prog}

start() {
# Make fifo if it doesn't already exist
if [ ! -p /tmp/nmeaNP ]
then
mknod /tmp/nmeaNP p
fi

# Check for gpsd ready (max 5 seconds)
echo -n "Waiting for gpsd . . . "
sleep 1
if [ ! "$(pidof gpsd)" ]
then
sleep 4
if [ ! "$(pidof gpsd)" ]
then
RETVAL=1
echo "failure."
return $RETVAL
fi
fi

# Start daemons.
echo -n "starting ${prog}: "
cd $GLLIN_PATH
sleep 1
if [ -e $GLLIN_PATH/${prog}.real ]
then
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog}.real -low 5 > /dev/null
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog}.real -periodic 1 +daemon
else
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog} -low 5 > /dev/null
$GLLIN_PATH/lib/ld-linux.so.2 --library-path $GLLIN_PATH/lib $GLLIN_PATH/${prog} -periodic 1 +daemon
fi
echo "success."
RETVAL=$?
echo
return $RETVAL
}

stop() {
# Stop daemons.
echo -n "Shutting down ${prog}: "
pkill ld-linux.so.2
RETVAL=$?
echo "success."
return $RETVAL
}

# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
RETVAL=$?
;;
status)
# RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac

exit $RETVAL
</pre>

These scripts allow you (or init, if you have them numbered in rcX.d appropriately) to start gpsd *before* gllin. This way, gpsd starts listening on /tmp/nmeaNP immediately, and gllin doesn't need to send output to /dev/null in order to stay alive.

This version of the gpsd script will create the named pipe (if the device name includes "NP" in the filename) if it doesn't exist.

Manually using GPRS

2008-03-12T09:09:16Z

Cheetah100:

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>
/dev/ttySAC0 115200
connect /etc/ppp/gprs-connect-chat
crtscts
lock
hide-password
defaultroute
usepeerdns
disconnect /etc/ppp/gprs-disconnect-chat
holdoff 3
ipcp-accept-local
lcp-echo-failure 8
lcp-echo-interval 3
noauth
noipdefault
novj
novjccomp
replacedefaultroute
persist
lcp-echo-interval 3
lcp-echo-failure 12
</pre>

This options where mentioned before with that strange comment. Mine worked fine for me without those.

<pre>
# very long timeouts (unwise?)
lcp-echo-interval 300
lcp-echo-failure 40000
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. 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>

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

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

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.

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" ""
</pre>

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/gta01-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 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
|-
| 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
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs ||
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| New Zealand || Vodafone || Any || live.vodafone.com / *99***2#|| ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Norway || Telenor || Any || telenor || ||
|-
| 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 || Cingular (AT&T) || Less than full internet || wap.cingular || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || ||
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
|}

[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#"

== 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:Developer software]]

[[Category:Guides]]

Manually using GPRS

2008-03-12T03:35:51Z

Cheetah100: /* Some APN names for reference */

You need to have [[GSM]] parts already initialized, with modem logged in to the network, for this to work. It is best to test it by doing test call. 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>
/dev/ttySAC0 115200
connect /etc/ppp/gprs-connect-chat
crtscts
lock
hide-password
defaultroute
usepeerdns
disconnect /etc/ppp/gprs-disconnect-chat
holdoff 3
ipcp-accept-local
lcp-echo-failure 8
lcp-echo-interval 3
noauth
noipdefault
novj
novjccomp
replacedefaultroute
persist
lcp-echo-interval 3
lcp-echo-failure 12
</pre>

This options where mentioned before with that strange comment. Mine worked fine for me without those.

<pre>
# very long timeouts (unwise?)
lcp-echo-interval 300
lcp-echo-failure 40000
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. 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>

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

<pre>
#!/bin/sh -e
exec chat -v\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 3\
"" ATZ\
OK-\\k\\k\\k\\d+++ATH-OK ATE1\
OK AT+CFUN=0\
OK \\dAT+CFUN=1\
ERROR AT+CPIN\?\
"+CPIN: READY-AT+CPIN=\"2222\"-OK" AT\
TIMEOUT 60\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT \d\c
</pre>

You will need to adjust the APN name "internet" in at+cgdcont 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.

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" ""
</pre>

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

=== Required fixes ===

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>

=== Starting pppd ===

Then, after initializing GSM, you should be able to initialize GPRS by `pppd call gprs`. Good luck!

To dial in - and get verbose output on the terminal - use pppd
<pre>
pppd debug nodetach call gprs
</pre>

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

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN
! user/password if required
! Working pppd scripts
|-
| 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
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs ||
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| New Zealand || Vodafone || Any || live.vodafone.com || ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Norway || Telenor || Any || telenor || ||
|-
| 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 || Cingular (AT&T) || Less than full internet || wap.cingular || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || ||
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
|}

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

== 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:Developer software]]

[[Category:Guides]]

Manually using GPRS

2008-03-12T03:34:25Z

Cheetah100:

You need to have [[GSM]] parts already initialized, with modem logged in to the network, for this to work. It is best to test it by doing test call. 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>
/dev/ttySAC0 115200
connect /etc/ppp/gprs-connect-chat
crtscts
lock
hide-password
defaultroute
usepeerdns
disconnect /etc/ppp/gprs-disconnect-chat
holdoff 3
ipcp-accept-local
lcp-echo-failure 8
lcp-echo-interval 3
noauth
noipdefault
novj
novjccomp
replacedefaultroute
persist
lcp-echo-interval 3
lcp-echo-failure 12
</pre>

This options where mentioned before with that strange comment. Mine worked fine for me without those.

<pre>
# very long timeouts (unwise?)
lcp-echo-interval 300
lcp-echo-failure 40000
</pre>

Depending on the APN, you may need password authentication using CHAP or PAP. 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>

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

<pre>
#!/bin/sh -e
exec chat -v\
ABORT BUSY\
ABORT DELAYED\
ABORT "NO ANSWER"\
ABORT "NO DIALTONE"\
ABORT VOICE\
ABORT ERROR\
ABORT RINGING\
TIMEOUT 3\
"" ATZ\
OK-\\k\\k\\k\\d+++ATH-OK ATE1\
OK AT+CFUN=0\
OK \\dAT+CFUN=1\
ERROR AT+CPIN\?\
"+CPIN: READY-AT+CPIN=\"2222\"-OK" AT\
TIMEOUT 60\
OK AT+COPS\
OK AT+CGDCONT=1,\"IP\",\"internet\"\
OK ATD*99#\
CONNECT \d\c
</pre>

You will need to adjust the APN name "internet" in at+cgdcont 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.

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" ""
</pre>

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

=== Required fixes ===

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>

=== Starting pppd ===

Then, after initializing GSM, you should be able to initialize GPRS by `pppd call gprs`. Good luck!

To dial in - and get verbose output on the terminal - use pppd
<pre>
pppd debug nodetach call gprs
</pre>

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

=== Some APN names for reference ===

{| border="1"
! Country
! Carrier
! Plan
! APN
! user/password if required
! Working pppd scripts
|-
| 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
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs ||
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| New Zealand || Vodafone || Any || live.vodafone.com || phone number = *99***2# ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Norway || Telenor || Any || telenor || ||
|-
| 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 || Cingular (AT&T) || Less than full internet || wap.cingular || ||
|-
| USA || T-mobile || Anything less than full internet || wap.voicestream.com || ||
|-
| USA || T-mobile || Regular internet plan || internet2.voicestream.com || || [[T-Mobile pppd scripts]]
|-
| USA || T-mobile || "VPN" internet plan || internet3.voicestream.com || ||
|-
|}

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

== 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:Developer software]]

[[Category:Guides]]