Openmoko - User contributions [en]

User talk:Vortex

2008-08-23T13:36:19Z

Vortex:

Currently generating OM2008.2, OM2008.8 & FSO builds on the Neo Freerunner from OE (bitbake - portage from first principles!). Painful & time consuming. I'll be sharing the pain here for the pleasure of others.

Generating openmoko environments on a venerable headless, X Windows-less Gentoo box. Last sync'ed on 20080823.

20080823: Starting with Rod Whitby's Mokomakefile, after a few informal & unsuccessful attempts at bitbaking and reading around, I've changed OM_GIT_BRANCH to ASU testing:

Makefile:

-OM_GIT_BRANCH := org.openmoko.dev
+OM_GIT_BRANCH := org.openmoko.asu.testing # ASU testing

Hopefully this will bring some stability to the chaos.

1st issue: make openmoko-qtopia-x11-image fails at /openembedded/packages/qtopia-phone/qtopia-phone-x11_git.bb, do_compile package qtopia-phone-x11-4.3.2+git0+dfc2b2c070c0b5feeeb073f1751f3cab8b8fc9a7-r39.1 appears to want a local, native libXtst available.

Not sure why. Perhaps for local qemu. emerge'd libXtst locally & cranked the bitbake handle again. This time for sure ...

make openmoko-qtopia-x11-image
...
NOTE: build 200808230805: completed
[ -d stamps ] || mkdir stamps
touch stamps/openmoko-qtopia-x11-image

Success!

make openmoko-devel-image
...
NOTE: build 200808231356: completed
[ -d stamps ] || mkdir stamps
touch stamps/openmoko-devel-image

Success

#make fso-image
( cd build && . ../setup-env && bitbake fso-image )
NOTE: Removed the following variables from the environment:LESS,LESSOPEN,SSH_CLIENT,CVS_RSH,MAKEFLAGS,INFOPATH,JDK_HOME,SHLVL,CONFIG_PROTECT_MASK,WINDOW,EDITOR,MANPATH,OMDIR,JAVA_HOME,MFLAGS,PYTHONPATH,CLASSPATH,GCC_SPECS,STY,TERMCAP,SSH_CONNECTION,JAVAC,SSH_TTY,OLDPWD,CONFIG_PROTECT,MAKELEVEL,MAIL,LS_COLORS,PAGER
NOTE: Handling BitBake files: | (5431/5431) [100 %]
NOTE: Parsing finished. 5196 cached, 0 parsed, 235 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200808231343: started

OE Build Configuration:
BB_VERSION = "1.8.11"
OE_REVISION = "f17808591dd22fb8c254f6ab52190198a14e7930"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "om-gta02"
DISTRO = "openmoko"
DISTRO_VERSION = "P1-Snapshot-20080823"
TARGET_FPU = "soft"

ERROR: Nothing PROVIDES 'fso-image' (but '[]' DEPENDS on or otherwise requires it)
make: *** [fso-image] Error 1

I suspect that's not working cause I changed the OM_GIT_BRANCH above to ASU testing :-/

User talk:Vortex

2008-08-23T12:56:06Z

Vortex:

Currently generating OM2008.2, OM2008.8 & FSO builds on the Neo Freerunner from OE (bitbake - portage from first principles!). Painful & time consuming. I'll be sharing the pain here for the pleasure of others.

Generating openmoko environments on a venerable headless, X Windows-less Gentoo box. Last sync'ed on 20080823.

20080823: Starting with Rod Whitby's Mokomakefile, after a few informal & unsuccessful attempts at bitbaking and reading around, I've changed OM_GIT_BRANCH to ASU testing:

Makefile:

-OM_GIT_BRANCH := org.openmoko.dev
+OM_GIT_BRANCH := org.openmoko.asu.testing # ASU testing

Hopefully this will bring some stability to the chaos.

1st issue: make openmoko-qtopia-x11-image fails at /openembedded/packages/qtopia-phone/qtopia-phone-x11_git.bb, do_compile package qtopia-phone-x11-4.3.2+git0+dfc2b2c070c0b5feeeb073f1751f3cab8b8fc9a7-r39.1 appears to want a local, native libXtst available.

Not sure why. Perhaps for local qemu. emerge'd libXtst locally & cranked the bitbake handle again. This time for sure ...

make openmoko-qtopia-x11-image
...
NOTE: build 200808230805: completed
[ -d stamps ] || mkdir stamps
touch stamps/openmoko-qtopia-x11-image

Success!

#make fso-image
( cd build && . ../setup-env && bitbake fso-image )
NOTE: Removed the following variables from the environment:LESS,LESSOPEN,SSH_CLIENT,CVS_RSH,MAKEFLAGS,INFOPATH,JDK_HOME,SHLVL,CONFIG_PROTECT_MASK,WINDOW,EDITOR,MANPATH,OMDIR,JAVA_HOME,MFLAGS,PYTHONPATH,CLASSPATH,GCC_SPECS,STY,TERMCAP,SSH_CONNECTION,JAVAC,SSH_TTY,OLDPWD,CONFIG_PROTECT,MAKELEVEL,MAIL,LS_COLORS,PAGER
NOTE: Handling BitBake files: | (5431/5431) [100 %]
NOTE: Parsing finished. 5196 cached, 0 parsed, 235 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200808231343: started

OE Build Configuration:
BB_VERSION = "1.8.11"
OE_REVISION = "f17808591dd22fb8c254f6ab52190198a14e7930"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "om-gta02"
DISTRO = "openmoko"
DISTRO_VERSION = "P1-Snapshot-20080823"
TARGET_FPU = "soft"

ERROR: Nothing PROVIDES 'fso-image' (but '[]' DEPENDS on or otherwise requires it)
make: *** [fso-image] Error 1

I suspect that's not working cause I changed the OM_GIT_BRANCH above to ASU testing :-/

User talk:Vortex

2008-08-23T12:54:28Z

Vortex:

Currently generating OM2008.2, OM2008.8 & FSO builds on the Neo Freerunner from OE (bitbake - portage from first principles!). Painful & time consuming. I'll be sharing the pain here for the pleasure of others.

Generating openmoko environments on a venerable headless, X Windows-less Gentoo box. Last sync'ed on 20080823.

20080823: Starting with Rod Whitby's Mokomakefile, after a few informal & unsuccessful attempts at bitbaking and reading around, I've changed OM_GIT_BRANCH to ASU testing:

Makefile:

-OM_GIT_BRANCH := org.openmoko.dev
+OM_GIT_BRANCH := org.openmoko.asu.testing # ASU testing

Hopefully this will bring some stability to the chaos.

1st issue: make openmoko-qtopia-x11-image fails at /openembedded/packages/qtopia-phone/qtopia-phone-x11_git.bb, do_compile package qtopia-phone-x11-4.3.2+git0+dfc2b2c070c0b5feeeb073f1751f3cab8b8fc9a7-r39.1 appears to want a local, native libXtst available.

Not sure why. Perhaps for local qemu. emerge'd libXtst locally & cranked the bitbake handle again. This time for sure ...

make openmoko-qtopia-x11-image
...
NOTE: build 200808230805: completed
[ -d stamps ] || mkdir stamps
touch stamps/openmoko-qtopia-x11-image

Success!

#make fso-image
( cd build && . ../setup-env && bitbake fso-image )
NOTE: Removed the following variables from the environment:LESS,LESSOPEN,SSH_CLIENT,CVS_RSH,MAKEFLAGS,INFOPATH,JDK_HOME,SHLVL,CONFIG_PROTECT_MASK,WINDOW,EDITOR,MANPATH,OMDIR,JAVA_HOME,MFLAGS,PYTHONPATH,CLASSPATH,GCC_SPECS,STY,TERMCAP,SSH_CONNECTION,JAVAC,SSH_TTY,OLDPWD,CONFIG_PROTECT,MAKELEVEL,MAIL,LS_COLORS,PAGER
NOTE: Handling BitBake files: | (5431/5431) [100 %]
NOTE: Parsing finished. 5196 cached, 0 parsed, 235 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200808231343: started

OE Build Configuration:
BB_VERSION = "1.8.11"
OE_REVISION = "f17808591dd22fb8c254f6ab52190198a14e7930"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "om-gta02"
DISTRO = "openmoko"
DISTRO_VERSION = "P1-Snapshot-20080823"
TARGET_FPU = "soft"

ERROR: Nothing PROVIDES 'fso-image' (but '[]' DEPENDS on or otherwise requires it)
make: *** [fso-image] Error 1

User talk:Vortex

2008-08-23T12:53:33Z

Vortex:

Currently generating OM2008.2, OM2008.8 & FSO builds on the Neo Freerunner from OE (bitbake - portage from first principles!). Painful & time consuming. I'll be sharing the pain here for the pleasure of others.

Generating openmoko environments on a venerable headless, X Windows-less Gentoo box. Last sync'ed on 20080823.

20080823: Starting with Rod Whitby's Mokomakefile, after a few informal & unsuccessful attempts at bitbaking and reading around, I've changed OM_GIT_BRANCH to ASU testing:

Makefile:

-OM_GIT_BRANCH := org.openmoko.dev
+OM_GIT_BRANCH := org.openmoko.asu.testing # ASU testing

Hopefully this will bring some stability to the chaos.

1st issue: make openmoko-qtopia-x11-image fails at /openembedded/packages/qtopia-phone/qtopia-phone-x11_git.bb, do_compile package qtopia-phone-x11-4.3.2+git0+dfc2b2c070c0b5feeeb073f1751f3cab8b8fc9a7-r39.1 appears to want a local, native libXtst available.

Not sure why. Perhaps for local qemu. emerge'd libXtst locally & cranked the bitbake handle again. This time for sure ...

...
NOTE: build 200808230805: completed
[ -d stamps ] || mkdir stamps
touch stamps/openmoko-qtopia-x11-image

Success!

#make fso-image
( cd build && . ../setup-env && bitbake fso-image )
NOTE: Removed the following variables from the environment:LESS,LESSOPEN,SSH_CLIENT,CVS_RSH,MAKEFLAGS,INFOPATH,JDK_HOME,SHLVL,CONFIG_PROTECT_MASK,WINDOW,EDITOR,MANPATH,OMDIR,JAVA_HOME,MFLAGS,PYTHONPATH,CLASSPATH,GCC_SPECS,STY,TERMCAP,SSH_CONNECTION,JAVAC,SSH_TTY,OLDPWD,CONFIG_PROTECT,MAKELEVEL,MAIL,LS_COLORS,PAGER
NOTE: Handling BitBake files: | (5431/5431) [100 %]
NOTE: Parsing finished. 5196 cached, 0 parsed, 235 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200808231343: started

OE Build Configuration:
BB_VERSION = "1.8.11"
OE_REVISION = "f17808591dd22fb8c254f6ab52190198a14e7930"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "om-gta02"
DISTRO = "openmoko"
DISTRO_VERSION = "P1-Snapshot-20080823"
TARGET_FPU = "soft"

ERROR: Nothing PROVIDES 'fso-image' (but '[]' DEPENDS on or otherwise requires it)
make: *** [fso-image] Error 1

User talk:Vortex

2008-08-23T12:53:11Z

Vortex:

Currently generating OM2008.2, OM2008.8 & FSO builds on the Neo Freerunner from OE (bitbake - portage from first principles!). Painful & time consuming. I'll be sharing the pain here for the pleasure of others.

Generating openmoko environments on a venerable headless, X Windows-less Gentoo box. Last sync'ed on 20080823.

20080823: Starting with Rod Whitby's Mokomakefile, after a few informal & unsuccessful attempts at bitbaking and reading around, I've changed OM_GIT_BRANCH to ASU testing:

Makefile:

-OM_GIT_BRANCH := org.openmoko.dev
+OM_GIT_BRANCH := org.openmoko.asu.testing # ASU testing

Hopefully this will bring some stability to the chaos.

1st issue: make openmoko-qtopia-x11-image fails at /openembedded/packages/qtopia-phone/qtopia-phone-x11_git.bb, do_compile package qtopia-phone-x11-4.3.2+git0+dfc2b2c070c0b5feeeb073f1751f3cab8b8fc9a7-r39.1 appears to want a local, native libXtst available.

Not sure why. Perhaps for local qemu. emerge'd libXtst locally & cranked the bitbake handle again. This time for sure ...

...
NOTE: build 200808230805: completed
[ -d stamps ] || mkdir stamps
touch stamps/openmoko-qtopia-x11-image

Success!

$make fso-image
( cd build && . ../setup-env && bitbake fso-image )
NOTE: Removed the following variables from the environment:LESS,LESSOPEN,SSH_CLIENT,CVS_RSH,MAKEFLAGS,INFOPATH,JDK_HOME,SHLVL,CONFIG_PROTECT_MASK,WINDOW,EDITOR,MANPATH,OMDIR,JAVA_HOME,MFLAGS,PYTHONPATH,CLASSPATH,GCC_SPECS,STY,TERMCAP,SSH_CONNECTION,JAVAC,SSH_TTY,OLDPWD,CONFIG_PROTECT,MAKELEVEL,MAIL,LS_COLORS,PAGER
NOTE: Handling BitBake files: | (5431/5431) [100 %]
NOTE: Parsing finished. 5196 cached, 0 parsed, 235 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200808231343: started

OE Build Configuration:
BB_VERSION = "1.8.11"
OE_REVISION = "f17808591dd22fb8c254f6ab52190198a14e7930"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "om-gta02"
DISTRO = "openmoko"
DISTRO_VERSION = "P1-Snapshot-20080823"
TARGET_FPU = "soft"

ERROR: Nothing PROVIDES 'fso-image' (but '[]' DEPENDS on or otherwise requires it)
make: *** [fso-image] Error 1

User talk:Vortex

2008-08-23T12:51:44Z

Vortex:

Currently generating OM2008.2, OM2008.8 & FSO builds on the Neo Freerunner from OE (bitbake - portage from first principles!). Painful & time consuming. I'll be sharing the pain here for the pleasure of others.

Generating openmoko environments on a venerable headless, X Windows-less Gentoo box. Last sync'ed on 20080823.

20080823: Starting with Rod Whitby's Mokomakefile, after a few informal & unsuccessful attempts at bitbaking and reading around, I've changed OM_GIT_BRANCH to ASU testing:

Makefile:

-OM_GIT_BRANCH := org.openmoko.dev
+OM_GIT_BRANCH := org.openmoko.asu.testing # ASU testing

Hopefully this will bring some stability to the chaos.

1st issue: make openmoko-qtopia-x11-image fails at /openembedded/packages/qtopia-phone/qtopia-phone-x11_git.bb, do_compile package qtopia-phone-x11-4.3.2+git0+dfc2b2c070c0b5feeeb073f1751f3cab8b8fc9a7-r39.1 appears to want a local, native libXtst available.

Not sure why. Perhaps for local qemu. emerge'd libXtst locally & cranked the bitbake handle again. This time for sure ...

...
NOTE: build 200808230805: completed
[ -d stamps ] || mkdir stamps
touch stamps/openmoko-qtopia-x11-image

Success!

make fso-image

( cd build && . ../setup-env && bitbake fso-image )
NOTE: Removed the following variables from the environment:LESS,LESSOPEN,SSH_CLIENT,CVS_RSH,MAKEFLAGS,INFOPATH,JDK_HOME,SHLVL,CONFIG_PROTECT_MASK,WINDOW,EDITOR,MANPATH,OMDIR,JAVA_HOME,MFLAGS,PYTHONPATH,CLASSPATH,GCC_SPECS,STY,TERMCAP,SSH_CONNECTION,JAVAC,SSH_TTY,OLDPWD,CONFIG_PROTECT,MAKELEVEL,MAIL,LS_COLORS,PAGER
NOTE: Handling BitBake files: | (5431/5431) [100 %]
NOTE: Parsing finished. 5196 cached, 0 parsed, 235 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200808231343: started

OE Build Configuration:
BB_VERSION = "1.8.11"
OE_REVISION = "f17808591dd22fb8c254f6ab52190198a14e7930"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "om-gta02"
DISTRO = "openmoko"
DISTRO_VERSION = "P1-Snapshot-20080823"
TARGET_FPU = "soft"

ERROR: Nothing PROVIDES 'fso-image' (but '[]' DEPENDS on or otherwise requires it)
make: *** [fso-image] Error 1

User talk:Vortex

2008-08-23T12:42:02Z

Vortex:

User talk:Vortex

2008-08-23T12:40:56Z

Vortex:

User talk:Vortex

2008-08-23T10:00:07Z

Vortex:

User talk:Vortex

2008-08-23T09:59:47Z

Vortex:

User talk:Vortex

2008-08-23T09:59:26Z

Vortex:

User talk:Vortex

2008-08-23T09:50:32Z

Vortex:

User talk:Vortex

2008-08-23T09:49:24Z

Vortex: Openmoko OE local builds

User:Vortex

2008-08-19T16:07:45Z

Vortex: New page: Contact me at vortex (at) free2air . net

Contact me at vortex (at) free2air . net

Openmoko Local Groups: London

2008-08-19T16:05:11Z

Vortex:

Welcome to OpenMoko London!

Beer and Neo anyone?

{|border=1
!Name (IRC nick)
!Skills
!Interest
!Location
!Device owned
|-
|[[User:jptmoore|John Moore]] (zedstar)
|C/Scheme
|Application development
|Pinner
|[[Image: Moko.jpg|center]]
|-
|Alex
|Java,Perl,Python
|User & developer
|Hampshire
|
|-
|[[User:Phlash|Phil Ashby]]
|C/C++/Java /Embedded/Hardware
|Kernel & Application development
|Felixstowe
|[[Image: Moko.jpg|center]]
|-
|John Cass
|Java,C
|User & developer
|London
|[[Image: Moko.jpg|center]]
|-
|[[User:TonyGarnockJones|Tony Garnock-Jones]] (tonyg)
|C, assembly, Erlang, Scheme, ML, Haskell, Smalltalk, ...
|User & developer
|London
|[[Image: Moko.jpg|center]]
|-
|[[User:ThomasWood|Thomas Wood/OpenedHand]]
|C, GTK+ developer
|User & developer
|London
|[[Image: Moko.jpg|center]] [[Image: MokoBox.jpg|center]] + GTA02 (FreeRunner Prototype)
|-
|[[User:Stephmw|Steph Meslin-Weber]]
|Java (J2ME), C, User Experience, Interface prototyping
|User, developer and general busybody
|London
|-
|[[User:WebJames|James Olney]]
|General experience
|User
|Oxford
|Wanted Freerunner perhaps get into a 10pack group]
|-
|[[User:chrestomanci|David Pottage]]
|Perl, Java (J2se), C
|User & developer
|Reading
|Freerunner
|-
|[[User:vermoos|Michael Nandris]]
|Python/Plone ethusiast, interest in DPA (1998)
|User, developer
|London, Camden
|Wanted Freerunner perhaps get into a 10pack group]
|-
|[[User:Weiss|Weiss]]
|C, GTK+, ARM Assembly, Perl, TCL
|User, developer
|Cambridge
|Wanted Freerunner [perhaps get into a 10pack group]
|-
|[[User:TimW|TimW]]
|C++
|User, developer
|Pinner
|Freerunner
|-
|[[User:Menno|Menno Smits]]
|Python, C, GTK+
|User, apps development
|London
|Freerunner
|-
|[[User:David_Hicks|Dave]]
|C, SSL/TLS, POSIX threading
|User, apps development
|London
|Freerunner
|-
|Tina
|User, Sys Admin
|User (can compile, maybe port)
|Oxford
|Freerunner
|-
|[[User:gnublade|Andy Kilner]]
|Python, C, GTK+
|User, Developer
|London
|Freerunner
|-
|[[User:Vortex|Vortex]]
|C, toolchains, distributions
| mesh networking, service discovery, wifi, bluetooth, scanning, gps
|London
|Freerunner
|-
|}
Key:
[[Image: Moko.jpg]] = GTA01
[[Image: MokoBox.jpg]] = Debug board

See [[Talk:OpenMoko_Local_Groups:_London|discussion]]

[[Category:Openmoko Local Groups]]

How to use bluetooth to transfer data between Neo and Desk-top

2008-08-18T12:28:49Z

Vortex: /* Start to transfer date */

This page , we will introduce about , how to active your Neo bluetooth device via host. You can follow these step to learn how to transfer date between Neo and PC.

==configure your setting of host ==
First you should modify this bluetooth setting file in your desk-top computer:

> sudo vi /etc/default/bluetooth

then search for the keyword "/pand" to find " PAND_ENABLED=0 "

And now you should change the 0 into 1

("PAND_ENABLED=1")

After you modify the setting, use this command to restart bluetooth device.

> sudo /etc/init.d/bluetooth restart

After restarting the bluetooth, you will see Bluetooth PAN daemon information.

That means you wake up the '''PAN''' daemon suscessfully :P

After that,you should pass the argument to let PAN daemon know what it should do now.

> sudo pand -s

this command let desk-top computer be a Server to listen the other linux-based devices

which is connecting it through the bluetooth.

==On the Neo side==
In the Neo:

> echo "1" > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
> echo "0" > /sys/bus/platform/devices/neo1973-pm-bt.0/reset

this command will search nearly bluetooth device.

> hcitool scan

Put the wanted bluetooth's Mac (Address) in this line

> export PC_BT_ID=(bluetooth's Mac)
> pand -c $PC_BT_ID --service NAP --autozap

> ifconfig bnep0 10.0.0.2 netmask 255.255.255.0

Switch back to the Desk-top computer :

>sudo ifconfig bnep0 10.0.0.1 netmask 255.255.255.0

This means that desk-top computer will set up environment for connectiog the Neo.

Then, you can use the "ping" command to check whether the connection is build sucessfully or not.

> ping 10.0.0.2

// send the testing data to the Neo

If it works ,you will receive following message:

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=xx.x ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=xx.x ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=xx.x ms

........

==Start to transfer data==
Also,you can copy datas to the Neo.

> scp XXX.X root@10.0.0.2:

That's all.
Enjoy:)

[[Category:Networking]]

How to use bluetooth to transfer data between Neo and Desk-top

2008-08-18T12:28:31Z

Vortex: /* On the Neo site */

This page , we will introduce about , how to active your Neo bluetooth device via host. You can follow these step to learn how to transfer date between Neo and PC.

==configure your setting of host ==
First you should modify this bluetooth setting file in your desk-top computer:

> sudo vi /etc/default/bluetooth

then search for the keyword "/pand" to find " PAND_ENABLED=0 "

And now you should change the 0 into 1

("PAND_ENABLED=1")

After you modify the setting, use this command to restart bluetooth device.

> sudo /etc/init.d/bluetooth restart

After restarting the bluetooth, you will see Bluetooth PAN daemon information.

That means you wake up the '''PAN''' daemon suscessfully :P

After that,you should pass the argument to let PAN daemon know what it should do now.

> sudo pand -s

this command let desk-top computer be a Server to listen the other linux-based devices

which is connecting it through the bluetooth.

==On the Neo side==
In the Neo:

> echo "1" > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
> echo "0" > /sys/bus/platform/devices/neo1973-pm-bt.0/reset

this command will search nearly bluetooth device.

> hcitool scan

Put the wanted bluetooth's Mac (Address) in this line

> export PC_BT_ID=(bluetooth's Mac)
> pand -c $PC_BT_ID --service NAP --autozap

> ifconfig bnep0 10.0.0.2 netmask 255.255.255.0

Switch back to the Desk-top computer :

>sudo ifconfig bnep0 10.0.0.1 netmask 255.255.255.0

This means that desk-top computer will set up environment for connectiog the Neo.

Then, you can use the "ping" command to check whether the connection is build sucessfully or not.

> ping 10.0.0.2

// send the testing data to the Neo

If it works ,you will receive following message:

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=xx.x ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=xx.x ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=xx.x ms

........

==Start to transfer date==
Also,you can copy datas to the Neo.

> scp XXX.X root@10.0.0.2:

That's all.
Enjoy:)

[[Category:Networking]]

Manually using GPRS

2008-08-06T16:08:51Z

Vortex:

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>

And you'll 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>

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>

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" "\c"
</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/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
|-
| Canada || Rogers || Any, behind NAT || internet.com || ||
|-
| 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<sup>[1]</sup>|| || under tests
|-
| France || Orange || ??? || orange.fr || || under tests
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs || [[Base pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| 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 || ||
|-
| 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 || Cingular (AT&T) || Less than full internet || wap.cingular / may require *99***1# || ||
|-
| 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 || ||
|-
| Venezuela || Digitel || Pre- y post-pago || gprsweb.digitel.ve || ||
|-
| India || AirTel || MobileOffice || airtelgprs.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#"

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-06T08:14:06Z

Vortex: /* 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>

And you'll 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>

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>

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" "\c"
</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/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
|-
| Canada || Rogers || Any, behind NAT || internet.com || ||
|-
| 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<sup>[1]</sup>|| || under tests
|-
| France || Orange || ??? || orange.fr || || under tests
|-
| Germany || E-Plus || BASE (and others?) || internet.eplus.de || eplus gprs || [[Base pppd scripts]]
|-
| Germany || T-Mobile || || internet.t-mobile || ||
|-
| Germany || Vodafone || Any, behind NAT || web.vodafone.de || ||
|-
| 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 || ||
|-
| 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 || Cingular (AT&T) || Less than full internet || wap.cingular / may require *99***1# || ||
|-
| 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 || ||
|-
| Venezuela || Digitel || Pre- y post-pago || gprsweb.digitel.ve || ||
|-
| India || AirTel || MobileOffice || airtelgprs.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#"

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

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