Openmoko - User contributions [en]

User talk:ScaredyCat

2008-06-04T16:18:32Z

ScaredyCat: /* GSM AT Command Reference */

=== GSM AT Command Reference ===

[http://buildhost.automated.it/ My Stuff] and [http://blog.automated.it/ My blog]

<pre>
'1.1 - Oct.2001
'
'According to ITU-T V.25ter (07/97):
'only the commands which effect GSM/UMTS 6.1.8 ISO system global object identification

AT+GOI
ERROR

'6.1.9 Overall capabilities of TA
AT+GCAP
+GCAP: +FCLASS, +CGSM, +DS

'6.1.10 Selects the country of installation
AT+GCI=?
ERROR

'6.2.10 Fixed TE data rate
AT+IPR=?
+IPR: (0,300,1200,2400,4800,9600,14400,19200,28800,38400,57600,115200,230400,460800)

AT+IPR?
+IPR: 0

'6.2.11 Character framing
AT+ICF=?
+ICF: (0-6),(0-3)

AT+ICF?
+ICF: 3,3

'6.2.12 Flow control
AT+IFC=?
+IFC: (0-3),(0-2)

AT+IFC?
+IFC: 2,2

'6.2.13 Data rate
AT+ILRR=?
+ILRR: (0,1)

AT+ILRR?
+ILRR: 0

'
'According to TIA IS-101:
'only one command which effect GSM/UMTS used here
'C.2.1 Select mode
AT+FCLASS=?
0,1,2

'
'According to PCCA STD-101:
'Select wireless network
AT+WS46=?
+WS46: (12,240)

AT+WS46?
+WS46: 12

'
'According to 3GPP TS 27.007 version 4.2.0:
'5.1 Request manufacturer identification
AT+GMI
Ericsson

AT+CGMI
ERICSSON

'5.2 Request model identification
AT+GMM
T39

AT+CGMM
1130102-BVT39m

'5.3 Request revision identification
AT+GMR
R2M prgCXC125147_TAE

AT+CGMR
R2M CXC125268

'5.4 Request product serial number identification
'not used here, for privacy reasons
AT+CGSN=?
OK

'5.5 Select TE character set
AT+CSCS=?
+CSCS: ("GSM","IRA","8859-1","ERICSSON","UTF-8")

AT+CSCS?
+CSCS: "GSM"

'5.6 Request international mobile subscriber identity
'not used here, for privacy reasons
AT+CIMI=?
OK

'5.7 Multiplexing mode
AT+CMUX=?
+CMUX: (0),(0),(1-7),(31),(10),(3),(30),(10),(1-7)

AT+CMUX?
+CMUX: 0,0,1,31,10,3,30,10,2

'6.1 Select type of address
AT+CSTA=?
ERROR

AT+CSTA?
ERROR

'6.4 Call mode
AT+CMOD=?
+CMOD: (0-1)

AT+CMOD?
+CMOD: 0

'6.5 Hangup call
AT+CHUP=?
OK

'6.7 Select bearer service type
AT+CBST=?
+CBST: (0,4,6-7,12,14-16,68,70-71,75,79-83),(0),(1)

AT+CBST?
+CBST: 0,0,1

'6.8 Radio link protocol
AT+CRLP=?
+CRLP: (0-61),(0-61),(38-100),(0-255),(0,1)
+CRLP: (0-496),(0-496),(38-100),(0-255),(2),(3-10)

AT+CRLP?
+CRLP: 61,61,48,6,0
+CRLP: 120,120,48,6,2,3

'6.9 Service reporting control
AT+CR=?
+CR: (0,1)

AT+CR?
+CR: 0

'6.10 Extended error report
AT+CEER=?
OK

'6.11 Cellular result codes
AT+CRC=?
+CRC: (0,1)

AT+CRC?
+CRC: 0

'6.12 HSCSD device parameters
AT+CHSD=?
OK

AT+CHSD
+CHSD: 2,2,1,3,12

'6.13 HSCSD transparent call configuration
AT+CHST=?
ERROR

AT+CHST?
ERROR

'6.14 HSCSD non-transparent call configuration
AT+CHSN=?
+CHSN: (0-4),(0-2),(0-2),(4,8,12)

AT+CHSN?
+CHSN: 1,1,0,4

'6.15 HSCSD current call parameters
AT+CHSC=?
OK

AT+CHSC?
ERROR

'6.16 HSCSD parameters report
AT+CHSR=?
+CHSR: (0,1)

AT+CHSR?
+CHSR: 0

'6.17 HSCSD automatic user initiated upgrading
AT+CHSU=?
+CHSU: (0,1)

AT+CHSU?
+CHSU: 0

'6.18 HSCSD non-transparent asymmetry configuration
AT+CHSA=?
ERROR

AT+CHSA?
ERROR

'6.19 Single numbering scheme
AT+CSNS=?
ERROR

AT+CSNS?
ERROR

'6.20 Voice Hangup Control
AT+CVHU=?
+CVHU: (0-2)

AT+CVHU?
+CVHU: 2

'6.21 V.120 rate adaption protocol
AT+CV120=?
ERROR

AT+CV120?
ERROR

'6.22 Settings date format
AT+CSDF=?
ERROR

AT+CSDF?
ERROR

'6.23 Silence Command
AT+CSIL=?
ERROR

AT+CSIL?
ERROR

'6.24 Settings time format
AT+CSTF=?
ERROR

AT+CSTF?
ERROR

'7.1 Subscriber number
'not used here, for privacy reasons
AT+CNUM=?
OK

'7.2 Network registration
'not used here, for privacy reasons
AT+CREG=?
+CREG: (0-1)

'7.3 Operator selection
'not used here, for speed reasons
AT+COPS?
+COPS: 0,0,"E-PLUS"

'7.4 Facility lock
AT+CLCK=?
+CLCK: ("CS","PS","SC","P2","AO","OI","OX","AI","IR","AB","AG","AC")

'7.5 Change password
AT+CPWD=?
+CPWD: ("PS",8),("SC",8),("P2",8),("AO",8),("OI",8),("OX",8),("AI",8),("IR",8),("AB",8),("AG",8),("AC",8)

'7.6 Calling line identification presentation
AT+CLIP=?
+CLIP: (0-1)

'7.7 Calling line identification restriction
AT+CLIR=?
+CLIR: (0-2)

'7.8 Connected line identification presentation
AT+COLP=?
ERROR

'7.9 Called line identification presentation
AT+CDIP=?
ERROR

'7.10 Closed user group
AT+CCUG=?
ERROR

'7.11 Call forwarding number and conditions
AT+CCFC=?
+CCFC: (0-5)

'7.12 Call waiting
AT+CCWA=?
+CCWA: (0-1)

AT+CCWA?
+CCWA: 0

'7.13 Call related supplementary services
AT+CHLD=?
+CHLD: (0-4,11-16,21-26)

'7.14 Call deflection
AT+CTFR=?
ERROR

'7.15 Unstructured supplementary service data
AT+CUSD=?
+CUSD: (0-1)

AT+CUSD?
+CUSD: 0

'7.16 Advice of Charge
AT+CAOC=?
+CAOC: (0)

AT+CAOC?
+CME ERROR: 4

'7.17 Supplementary service notifications
AT+CSSN=?
+CSSN: (0-1),(0-1)

AT+CSSN?
+CSSN: 0,0

'7.18 List current calls
'not used here, for privacy reasons
AT+CLCC=?
ERROR

'7.19 Preferred operator list
'not used here, for privacy reasons
AT+CPOL=?
ERROR

'7.20 Selection of preferred operator list
AT+CPLS=?
ERROR

AT+CPLS?
ERROR

'7.21 Read operator names
'not used here, for privacy reasons
AT+COPN=?
ERROR

'7.22 eMLPP Priority Registration and Interrogation
'not used here, for privacy reasons
AT+CAEMLPP=?
ERROR

'7.23 eMLPP subscriptions
AT+CPPS=?
ERROR

'7.24 Fast call setup conditions
'not used here, for privacy reasons
AT+CFCS=?
ERROR

'7.25 Automatic answer for eMLPP Service
'not used here, for privacy reasons
AT+CAAP=?
ERROR

'7.26 User to User Signalling Service 1
AT+CUUS1=?
ERROR

AT+CUUS1?
ERROR

'8.1 Phone activity status
AT+CPAS=?
+CPAS: (0,3,4,129,130,131)

'8.2 Set phone functionality
AT+CFUN=?
+CFUN: (0-1)

AT+CFUN?
+CFUN: 1

'8.3 Enter PIN
AT+CPIN?
+CPIN: READY

'8.4 Battery charge
AT+CBC=?
+CBC: (0-2),(0-100)

'8.5 Signal quality
AT+CSQ=?
+CSQ: (0-31,99),(0-7,99)

'8.6 Mobile Equipment control mode
AT+CMEC=?
ERROR

AT+CMEC?
ERROR

'8.7 Keypad control
AT+CKPD=?
OK

'8.8 Display control
AT+CDIS=?
ERROR

'8.9 Indicator control
AT+CIND=?
+CIND: ("battchg",(0-5)),("signal",(0-5)),("batterywarning",(0-1)),("chargerconnected",(0-1)),("service",(0-1)),("sounder",(0-1)),("message",(0-1)),("call",(0-1)),("roam",(0-1)),("smsfull",(0-1))

'8.10 Mobile Equipment event reporting
AT+CMER=?
+CMER: (0,3),(0,2),0,(0-1),0

AT+CMER?
+CMER: 0,0,0,0,0

'8.11 Select phonebook memory storage
AT+CPBS=?
+CPBS: ("ME","SM","DC","FD","MC","MV","RC","HP","BC")

AT+CPBS?
+CPBS: "SM"

'8.12 Read phonebook entries
AT+CPBR=?
+CPBR: (1-100),80,17

AT+CPBR?
ERROR

'8.13 Find phonebook entries
AT+CPBF=?
+CPBF: 80,17

'8.14 Write phonebook entry
AT+CPBW=?
+CPBW: (1-100),80,(128-255),17

'8.15 Clock
AT+CCLK=?
OK

AT+CCLK?
+CCLK: "01/10/27,16:00:45+04"

'8.16 Alarm
AT+CALA=?
+CALA: (1-2),(),(),(13),()

AT+CALA?
OK

'8.17 Generic SIM access
AT+CSIM=?
ERROR

'8.18 Restricted SIM access
AT+CRSM=?
ERROR

'8.19 Secure control command
AT+CSCC=?
+CSCC: (1-2),(199)

'8.20 Alert sound mode
AT+CALM=?
ERROR

AT+CALM?
ERROR

'8.21 Ringer sound level
AT+CRSL=?
ERROR

'8.22 Vibrator mode
AT+CVIB=?
+CVIB: (0-1,16)

'8.23 Loudspeaker volume level
AT+CLVL=?
ERROR

'8.24 Mute control
AT+CMUT=?
ERROR

'8.25 Accumulated call meter
AT+CACM=?
OK

'8.26 Accumulated call meter maximum
AT+CAMM=?
OK

'8.27 Price per unit and currency table
AT+CPUC=?
OK

'8.28 Call Meter maximum event
AT+CCWE=?
ERROR

'8.29 Power class
AT+CPWC=?
ERROR

AT+CPWC?
ERROR

'8.30 Set Language
AT+CLAN=?
+CLAN: "de","en","fr","it","AUTO"

'8.31 Language Event
AT+CLAE=?
ERROR

AT+CLAE?
ERROR

'8.32 Set Greeting Text
AT+CSGT=?
ERROR

'8.33 Set Voice Mail Number
AT+CSVM=?
ERROR

'8.34 Ring Melody Playback
AT+CRMP=?
ERROR

'8.35 Master Reset
AT+CMAR=?
ERROR

'8.36 List all available AT commands
AT+CLAC
&F
*
*EACS
*EAID
*EALR
*EALS
*EAM
*EAMS
*EAPM
*EAPN
*EAPP
*EAPS
*EARS
*EASM
*EASY
*EBCA
*ECAM
*ECAR
*ECAS
*ECAW
*ECBP
*ECMW
*ECSP
*ECUR
*EDIF
*EDIS
*EDST
*EENL
*EFOS
*EGIR
*EINA
*EIPS
*EKSE
*EKSP
*EKSR
*ELAM
*ELAN
*ELIN
*EMAR
*EMIC
*EMIR
*EMLR
*EMWS
*ENAD
*EPED
*EPEE
*EPEW
*EPHD
*EPNR
*EPNW
*EPRR
*EPRW
*EQVL
*ERIL
*ERIN
*ERIP
*ESAG
*ESAM
*ESBL
*ESCG
*ESCN
*ESDF
*ESDG
*ESDI
*ESGR
*ESIL
*ESKL
*ESKS
*ESLN
*ESMA
*ESMM
*ESNU
*ESOM
*ESTF
*ESTL
*ESVM
*ESZS
*ETCH
*ETXT
*EVA
*EVAA
*EVD
*EVH
*EWBA
*EWBR
*EWCG
*EWCT
*EWDT
*EWHP
*EWIL
*EWLI
*EWPB
*EWPN
*EWPR
*EWSA
*EWSG
*EXVC
*EYDO
*EYPI
*EYRE
*EYRR
*EYRV
+CACM
+CALA
+CALD
+CAMM
+CAOC
+CAPD
+CBC
+CBST
+CCFC
+CCLK
+CCWA
+CFUN
+CGMI
+CGMM
+CGMR
+CGSMS
+CGSN
+CHLD
+CHSC
+CHSD
+CHSN
+CHUP
+CIMI
+CIND
+CKPD
+CLAC
+CLAN
+CLCK
+CLIP
+CLIR
+CMEE
+CMER
+CMGC
+CMGD
+CMGF
+CMGL
+CMGR
+CMGS
+CMGW
+CMOD
+CMSS
+CNMI
+CNUM
+COPS
+CPAS
+CPBF
+CPBR
+CPBS
+CPBW
+CPIN
+CPMS
+CPUC
+CPWD
+CRC
+CREG
+CRES
+CSAS
+CSCA
+CSCB
+CSCC
+CSCS
+CSMS
+CSQ
+CSSN
+CTZU
+CUSD
+CVIB
+VTS
+WS46
A
D
H
L
Q
S3
S4
S5
V
Z
/
&C
&D
&F
&W
*
*EINA
*EOBEX
*ESIR
+CEER
+CGACT
+CGATT
+CGDATA
+CGDATA
+CGDCONT
+CGEREP
+CGPADDR
+CGPADDR
+CGQMIN
+CGQREQ
+CGREG
+CHSR
+CHSU
+CHUP
+CHUP
+CLAC
+CMEE
+CMUX
+CR
+CRC
+CRLP
+CVHU
+DR
+DS
+FAA
+FBADLIN
+FBADMUL
+FBOR
+FBUG
+FCIG
+FCLASS
+FCQ
+FCR
+FDCC
+FDFFC
+FDIS
+FDR
+FDT
+FDT
+FECM
+FET
+FK
+FLID
+FLNFC
+FLPL
+FMDL?
+FMFR?
+FMI?
+FMINSP
+FMM?
+FMR?
+FPHCTO
+FPTS
+FRBC
+FREL
+FREV?
+FRH
+FRH
+FRM
+FRM
+FRS
+FRS
+FSPL
+FTBC
+FTH
+FTH
+FTM
+FTM
+FTS
+FTS
+FVRFC
+FWDFC
+GCAP
+GMI
+GMM
+GMR
+ICF
+IFC
+ILRR
+IPR
A
D
E
H
I
L
M
O
P
Q
S0
S10
S2
S3
S4
S5
S6
S7
S8
T
V
X
Z

'8.37 Delete alarm
AT+CALD=?
+CALD: (1-2)

'8.38 Postpone or dismiss an alarm
AT+CAPD=?
+CAPD: (0,540)

'8.39 Automatic Time Zone Update
AT+CTZU=?
+CTZU: (0-1)

AT+CTZU?
+CTZU: 0

'8.40 Time Zone Reporting
AT+CTZR=?
ERROR

AT+CTZR?
ERROR

'8.41 Enter protocol mode
AT+CPROT=?
ERROR

'9.1 Report Mobile Equipment error
AT+CMEE=?
+CMEE: (0-2)

'10.1.1 Define PDP Context
AT+CGDCONT=?
+CGDCONT:(1-10),("IP"),,,(0-1),(0-1)

'10.1.2 Define Secondary PDP Context
AT+CGDSCONT=?
ERROR

'10.1.3 Traffic Flow Template
AT+CGTFT=?
ERROR

'10.1.4 Quality of Service Profile (Requested)
AT+CGQREQ=?
+CGQREQ: (1-10),(0-3),(0-4),(0-5),(0-5),(0-18,31)

'10.1.5 Quality of Service Profile (Minimum acceptable)
AT+CGQMIN=?
+CGQMIN: (1-10),(0-3),(0-4),(0-5),(0-5),(0-18,31)

'10.1.6 3G Quality of Service Profile (Requested)
AT+CGEQREQ=?
ERROR

'10.1.7 3G Quality of Service Profile (Minimum acceptable)
AT+CGEQMIN=?
ERROR

'10.1.8 3G Quality of Service Profile (Negotiated)
AT+CGEQNEG=?
ERROR

'10.1.9 PS attach or detach
AT+CGATT=?
+CGATT: (0,1)

'10.1.10 PDP context activate or deactivate
AT+CGACT=?
+CGACT: (0,1)

'10.1.11 PDP Context Modify
AT+CGCMOD=?
ERROR

'10.1.12 Enter data state
AT+CGDATA=?
+CGDATA:("PPP")

'10.1.13 Configure local Octet Stream PAD parameters
AT+CGCLOSP=?
ERROR

'10.1.14 Show PDP address
AT+CGPADDR=?
+CGPADDR: (1,2)

'10.1.15 Automatic response to a network request for PDP context activation
AT+CGAUTO=?
ERROR

'10.1.16 Manual response to a network request for PDP context activation
AT+CGANS=?
ERROR

'10.1.17 GPRS mobile station class
AT+CGCLASS=?
ERROR

AT+CGCLASS?
ERROR

'10.1.12 Configure local triple-X PAD parameters
AT+CGCLPAD=?
ERROR

'10.1.18 Packet Domain event reporting
AT+CGEREP=?
+CGEREP: (0,1),(0)

'10.1.19 GPRS network registration status
AT+CGREG=?
+CGREG: (0-2)

'10.1.20 Select service for MO SMS messages
AT+CGSMS=?
+CGSMS: (2,3)

'11.1.1 Accept an incoming Voice Group or Voice Broadcast Call
AT+CAJOIN=?
ERROR

'11.1.2 Reject an incoming Voice Group or Voice Broadcast Call
AT+CAREJ=?
ERROR

'11.1.3 Leave an ongoing Voice Group or Voice Broadcast Call
AT+CAHLD=?
ERROR

'11.1.4 Talker Access for Voice Group Call
AT+CAPTT=?
ERROR

'11.1.5 Voice Group Call Uplink Status Presentation
AT+CAULEV=?
ERROR

'11.1.6 List current Voice Group and Voice Broadcast Calls
AT+CALCC=?
ERROR

'11.1.7 Voice Group or Voice Broadcast Call State Attribute Presentation
AT+CACSP=?
ERROR

'11.1.8 NCH Support Indication
AT+CANCHEV=?
ERROR

'11.1.9 Originator to Dispatcher Information
AT+COTDI=?
ERROR

AT+COTDI?
ERROR

'11.3.1 VGCS subscriptions and GId status
AT+CGCS=?
ERROR

AT+CGCS?
ERROR

'11.3.2 VBS subscriptions and GId status
AT+CBCS=?
+CBC: 0,69
ERROR

AT+CBCS?
+CBC: 0,69
ERROR

'
'According to 3GPP TS 27.005 version 4.0.0:
'3.2.1 Select Message Service
AT+CSMS=?
+CSMS: (0)

AT+CSMS?
+CSMS: 0, 1, 1, 1

'3.2.2 Preferred Message Storage
AT+CPMS=?
+CPMS: ("ME","SM"),("ME","SM"),("ME")

AT+CPMS?
+CPMS: "SM",0,12,"SM",0,12,"ME",9,40

'3.2.3 Message Format
AT+CMGF=?
+CMGF: (0)

AT+CMGF?
+CMGF: 0

'3.2.4 Enter SMS Block Mode Protocol
AT+CESP=?
ERROR

'3.3.1 Service Centre Address
AT+CSCA=?
OK

'3.3.2 Set Text Mode Parameters
AT+CSMP=?
ERROR

AT+CSMP?
ERROR

'3.3.3 Show Text Mode Parameters
AT+CSDH=?
ERROR

AT+CSDH?
ERROR

'3.3.4 Select Cell Broadcast Message Types
AT+CSCB=?
+CSCB: (0)

AT+CSCB?
+CSCB: 0,""

'3.3.5 Save Settings
AT+CSAS=?
+CSAS: (0-4)

'3.3.6 Restore Settings
AT+CRES=?
+CRES: (0-4)

'3.4.1 New Message Indications to TE
AT+CNMI=?
+CNMI: (3),(0,1,3),(0,2),(0),(0)

AT+CNMI?
+CNMI: 3,0,0,0,0

'3.5.4 Delete Message
AT+CMGD=?
OK

'3.5.6 More Messages to Send
AT+CMMS=?
ERROR

'
'SMS Text mode
AT+CMGF=1
+CMS ERROR: 303

'3.4.2 List Messages
AT+CMGL=?
AT +CMGF=1
+CMS ERROR: 303

'3.4.3 Read Message
AT+CMGR=?
OK

'3.4.4 New Message Acknowledgement to ME/TA
AT+CNMA=?
ERROR

'3.5.1 Send Message
AT+CMGS=?
OK

'3.5.2 Send Message from Storage
AT+CMSS=?
OK

'3.5.3 Write Message to Memory
AT+CMGW=?
OK

'3.5.5 Send Command
AT+CMGC=?
OK

'
'SMS PDU mode
AT+CMGF=0
OK

'4.1 List Messages
AT+CMGL=?
+CMGL: (0-4)

'4.2 Read Message
AT+CMGR=?
OK

'4.3 Send Message
AT+CMGS=?
OK

'4.4 Write Message to Memory
AT+CMGW=?
OK

'4.5 Send Command
AT+CMGC=?
OK

'4.6 New Message Acknowledgement to ME/TA
AT+CNMA=?
ERROR

'4.7 Send Message from Storage
AT+CMSS=?
OK

</pre>

Group sales

2008-04-20T14:15:16Z

ScaredyCat: /* [http://wiki.openmoko.org/wiki/Talk:GroupSales#The_Netherlands The Netherlands] */

<div style='float:right'>__TOC__</div>

== Australia ==
=== Western Australia ===
==== Perth ====

* Fred Janon mailto:fjanon@yahoo.com

=== Victoria ===
==== Melbourne ====
Status: 4/10

* 4x Dennis Wollersheim, mailto: dewoller (at) gmail (dot) com

=== ACT ===
==== Canberra ====
Status: 1/10

* J Dinale [http://wiki.openmoko.org/wiki/Special:Emailuser/Noledil Contact me here]

=== Queensland ===
==== Brisbane ====
Status: 2/10 (possibly 20)

* Nick Devereaux [http://wiki.openmoko.org/wiki/Special:Emailuser/Monkeypanic Contact me here]
* Matt Gallagher [http://wiki.openmoko.org/wiki/Special:Emailuser/mattg Contact me here]

== Austria ==
I don't think that we reach the 10 phones in a city, so maybe we can handle it like the Italians. Order the phones in the most requested city and ship it to the other ones from there.

=== Salzburg ===
Status: 1/10

* D. Kepplinger [http://wiki.openmoko.org/wiki/Special:Emailuser/Wedge Contact me here]
=== Wien ===
Status: 1/10
* M. Greifeneder [http://wiki.openmoko.org/wiki/Special:Emailuser/mikegr Contact me here]
=== Styria ===
==== Graz ====
Status: 1/10

* F Hackenberger [http://wiki.openmoko.org/wiki/Special:Emailuser/Deadman66 Contact me here]

== Belgium ==
=== Flanders ===
==== Brussel/Aalst/Gent/Brugge ====
Status 4/10
* Yorick, mailto: yorick DOT matthys AT gmail DOT com
* 2x Dolfje [http://wiki.openmoko.org/wiki/Special:Emailuser/Dolfje Contact me here]
* XVens, mailto: xavier DOT vens AT gmail DOT com
ps: Dolfje can bring freerunners to Brugge if needed

==== Antwerp ====
Status 4/10

* michielv [http://wiki.openmoko.org/wiki/Special:Emailuser/Michielv Contact me here]
* Peter N [http://wiki.openmoko.org/wiki/Special:Emailuser/Bubsy Contact me here]
* Ivo [http://wiki.openmoko.org/wiki/Special:Emailuser/Ivo Contact me here]
* Peter Leemans, mailto: peter AT x-tend DOT be

== Bulgaria ==
=== Sofia ===
==== Sofia ====
Status : 2/10

* Dimitar Staykov, mailto:meditache@gmail.com
* Vernim, [http://wiki.openmoko.org/wiki/Special:Emailuser/Vernim Contact]

== Canada ==
=== Ontario/Quebec ===
==== GTA (Toronto) ====
Status : 2/10

* Gerald A [http://wiki.openmoko.org/wiki/Special:Emailuser/Historybuff Contact me here]
* MattC, mailto: quirkz AT gmail

== Denmark ==
If we do not reach a total large enough, Denmark **is** a very small place - surely we could figure out a way of getting them to find their way 'round the country :)

=== Jutland ===
==== Aalborg ====
Status: 2/10

* Dan Leinir Turthra Jensen mailto:admin@leinir.dk [[User:Leinir]]
* Fabian Olesen mailto:firewalkerx@gmail.com

=== Fyn ===
Status: 1/10

* [[User:EsbenDamgaard]]

=== Sjælland ===
==== Copenhagen ====
Status: 2/10

* [[User:Fursund]]
* [[User:Rasmusjensen]]

== Finland ==
=== Uusimaa ===
==== Helsinki (Full)====
Status : 10/10

* Mikko Rauhala x2 [mailto:mjr@iki.fi mjr@iki.fi]
* Aleksi Hankalahti [mailto:aleksi.hankalahti@iki.fi aleksi.hankalahti@iki.fi]
* Seppo Hätönen [mailto:karrde@iki.fi karrde@iki.fi]
* Arttu Sund [mailto:thearttu@gmail.com thearttu@gmail.com]
* Ville-Pekka Vainio vpivaini AT cs.helsinki.fi
* Heikki Hallamaa [mailto:heikki.hallamaa@iki.fi heikki.hallamaa@iki.fi]
* Tomi Jylhä-Ollila tomi.jylha-ollila@helsinki.fi
* Richard Braakman
* Timo Jyrinki [mailto:timo.jyrinki@iki.fi timo.jyrinki@iki.fi]

==== Helsinki ====
Status : 4/10

* |[[User:Piksi]]
* Risto H. Kurppa risto AT kurppa DOT fi
* Aapo Rantalainen aapo DOT rantalainen AT gmail DOT com
* Matti Laakso matti DOT laakso AT kotiposti DOT net

=== Varsinais-Suomi ===
==== Turku ====
Status : 1/10

* Teemu Välimäki [mailto:teemu.valimaki@iki.fi teemu.valimaki@iki.fi]

== France ==
=== Bretagne ===
==== Brest ====
Status : 1/10

* StevenLeRoux [mailto:steven@pourri.fr steven@pourri.fr] Jabber_Id:Steven@jabber.fr
* Acheteur potentiel #2

==== Rennes ====
Status : 2/10

* Cédric DUFOUIL (openmoko at tsleg point com)
* Acheteur potentiel #2
* Yves MAHE (ymahe at zindep dot com)

=== Ile de france ===
==== Paris ====
Status : 8/10

* StevenLeRoux
* [[User:Phyce|Phyce]]
* Yann SLADEK
* [[User:Wilk|Wilk]] [http://wiki.openmoko.org/wiki/Special:Emailuser/Wilk Contact me here]
* Jonathan Magano (jonathanmm[AT]free[DOT]fr)
* Benjamin Renard (bn8[AT]zionetrix.net)
* [[User:OlivierBerger|OlivierBerger]]
* [[User:BartGS|BartGS]] [http://wiki.openmoko.org/wiki/Special:Emailuser/BartGS Contact me here]

You may also see :
http://bearstech.com/openmoko/register

=== Pays de la Loire ===
==== La Roche sur Yon ====
Status : 1/10

* [http://wiki.openmoko.org/wiki/Special:Emailuser/Vtouchar Vincent Touchard] (I may soon move to Bretagne/Brest)

== Germany ==
=== Sachsen-Anhalt ===
==== Stendal (evtl. Magdeburg) ====
Status 1/10

* Fabian Off [http://wiki.openmoko.org/wiki/Special:Emailuser/Fabian2de Contact me here]

=== Hamburg ===
==== Hamburg ====
Status 2/10

* Jan [http://wiki.openmoko.org/wiki/Special:Emailuser/Jan07 Contact me here]
* Varacanero [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here]

=== NRW ===
==== Bielefeld ====
Status 3/10

* David, infos on my [[User:Raven|user page]], or you can [[Special:Emailuser/Raven|contact me here]]
* Sebastian, infos on my [[User:Seppi|user page]], or you can [[Special:Emailuser/Seppi|contact me here]]
* Dackel, infos on my [[User:Killerdackel|user page]], or you can [[Special:Emailuser/Killerdackel|contact me here]]

==== Aachen ====
Status 1/10
* Henrik, infos on my [[User:Henrikz|user page]], or you can [[Special:Emailuser/Henrikz|contact me here]]

=== Baden-Württemberg ===
==== Karlsruhe ====

Status 2/10

* 2 for André (one for me and one for a friend), you can [[Special:Emailuser/Spacemarine|contact me here]]

== Italy ==
If we don't reach the 10 phones limit in each city, maybe we could place an order in the "most requested city", and from shipping to other buyers. We'll have anyway a good discount although the "double-shipping". ([http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/10937/focus=10981 Read here for reference]).

=== Toscana ===
==== Firenze ====
Status 2/10

* [[User:Treviño|Marco Trevisan (Treviño)]] - [http://blog.3v1n0.net/contatti-trevino/ Contacts here]
* [[User:Niccolo|Niccolo Rigacci]] - ''niccolo [AT] rigacci.org''

=== Lombardia ===

==== Milano ====
Status 5/10

* Marco Crociani - [http://wiki.openmoko.org/wiki/Special:Emailuser/Tyrael Contacts here]
* Marcello Gorla
* Maxxer [mailto:maxxer@yetopen.it maxxer@yetopen.it] (Lecco)
* Pietro Montorfano [mailto:monto84@gmail.com monto84@gmail.com] (from como)
* Gianluigi Belli - [http://wiki.openmoko.org/wiki/Special:Emailuser/Pulciux Contacts here]

=== Trentino-Alto Adige ===
==== Trento (Padova too :)) ====
Status 1/10

* Andrea Debortoli (debortoland AT gmail DOT com)

=== Veneto ===
==== Verona ====

* Persegat [mailto:persegat@alice.it persegat@alice.it] [[User:Pecce|Pecce]]

=== Puglia ===
==== Lecce ====
Status : 1/10

* [[User:Morpheus90|Morpheus90]] [mailto:ugopiemontese@rudiaelinux.com ugopiemontese@rudiaelinux.com]
==== Bari ====
Status : 2/10

* [[User:Fradeve11|Fradeve11]] [mailto:fradeve@ubuntu-it.org fradeve@ubuntu-it.org]

== [http://wiki.openmoko.org/wiki/Talk:GroupSales#The_Netherlands The Netherlands] ==
(Discuss this group sale on the [http://wiki.openmoko.org/wiki/Talk:GroupSales#The_Netherlands talk page])

* Christ van Willegen 1/10 [[User:ChristW]]
* Marijn Kruisselbrink 1 [[Special:Emailuser/User:mkruisselbrink|Contact]]
* Andy Powell 1/10 [[Special:Emailuser/User:ScaredyCat|Contact]]
* Arjan Veenstra 1/10 [[User:AVee]] [[Special:Emailuser/User:AVee|Contact]]
* Jan de Haan 1/10 [[User:Jan de Haan]] [[Special:Emailuser/User:Jan de Haan|Contact]]
* Eric Smith 1/10 [[User:Eric Smith]]
* André Disselhorst 1/10 [[User:A.dre]] [[Special:Emailuser/User:A.dre|Contact]]
=== Noord-Brabant ===

==== Bergen op Zoom ====
* [[User:Madjo|Marcel de Jong]] 1/10 [[Special:Emailuser/User:Madjo|Contact]]

=== Overijssel ===

==== Hengelo ====
* Sander Hoentjen 1/10 [[Special:Emailuser/User:Tjikkun|Contact]]

=== Utrecht ===

==== Utrecht ====
* Eric Spierings 1/10 [[Special:Emailuser/User:ericsp|Contact]]
* Peter van de Werken 1/10 [[Special:Emailuser/User:PWerken|Contact]]

=== Status ===
11/10

== New Zealand ==
=== Auckland ===
==== Auckland ====

* Rob Paulson 1/10 [[User:Myfanwy]] Simon Wells [[User:Swel024]]

== Norway ==
=== Nordland ===
==== Bodø ====
Status 2/10

* [[User:AlecTBM|Alexander Frøyseth]] [mailto:alexander.froyseth@gmail.com alexander.froyseth@gmail.com]
* Ole Marius
* Stian Vading
=== Rogaland ===
Status 1/10

*[[User:Dalaker|Tore Dalaker]] [mailto:tore@dalaker.com tore@dalaker.com]

=== Sør-Trøndelag ===
==== Trondheim ====
Status 8/10

*[[User:andy000|Andreas Kalvå]] [mailto:andy@samfundet.no andy@samfundet.no]
Send mail om du er interessert.

=== Østlandet ===
==== Oslo, Akershus, Buskerud, Vestfold ====
Status 16/20

* [[User:Ixian|Heikki Sørum]] [mailto:heikkis@matnat.uio.no] Interessert? mail meg.
* [[User:Bobkare|Knut Arne Bjørndal]] [mailto:bob@cakebox.net]

== Poland ==
=== dolnośląskie ===
==== Wrocław ====

* Special group buy site: https://www.kumulator.pl/show/group/35

== Portugal ==
=== Aveiro ===
==== Aveiro ====
Status : 2/10

* [[User:Ruben|Ruben Mendes]]
* [[User:kuyky|Tiago Saraiva]] [mailto:destructhor88@gmail.pt]

== Sweden ==
If insufficient number of people, orders could be merged and remailed perhaps

=== Svealand ===
==== Stockholm ====
Status : 2/10

* Erland Lewin mailto:erland@lewin.nu
* Simon Kågström mailto:simon.kagstrom@gmail.com
* Ingvaldur Sigurjonsson mailto:ingi@ultimalabor.se

==== Örebro ====
Status : 1/10

* Anders Petersson [mailto:demitar@worldforge.org demitar@worldforge.org]

=== Norrland ===
==== Umeå ====
Status : 1/10

* [[User:Zash|Zash]] [[Special:Emailuser/Zash|Contact]]

== Switzerland ==
==== Zurich ====
Status : 9/10

* Simon Wenner [http://wiki.openmoko.org/wiki/Special:Emailuser/Nowic Contact]
* Simon Schreiber [http://wiki.openmoko.org/wiki/Special:Emailuser/Magbeat Contact]
* Markus Huggler [http://wiki.openmoko.org/wiki/Special:Emailuser/Magbeat Contact]
* Andre Timmermann [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Raffael Schmid [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Pascal Weller [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Nick Zbinden [mailto:nickik@gmx.ch]
* Marcel Wirth [http://wiki.openmoko.org/wiki/Special:Emailuser/Skarhand Contact]
* Marcel Lütolf [http://wiki.openmoko.org/wiki/Special:Emailuser/NeRo Contact]

== Spain ==
=== Madrid ===
==== Madrid ====
Status : 1/10

* Rafael Campos [http://wiki.openmoko.org/wiki/Special:Emailuser/Methril Contact]

=== Zaragoza ===
==== Zaragoza ====
Status : 1/10

* Alejandro R. Mosteo alejandro AT mosteo · com

=== Barcelona ===
==== Barcelona ====
Status : 1/10

* José Luis Pérez [[Special:Emailuser/jluis|Contact]]

== USA ==
=== Colorado ===
==== Denver ====
Status: 7/10
* Shawn Sullivan [[mailto:shelbydz87@yahoo.com shelbydz87@yahoo.com]]
* Peter Abplanalp [http://wiki.openmoko.org/wiki/Special:Emailuser/alderion Contact]

=== Southern California ===
==== Los Angeles ====
Status: 2/10

* Ian Douglas [http://wiki.openmoko.org/wiki/Special:Emailuser/Iandouglas Contact me here]
* Matthew [http://wiki.openmoko.org/wiki/Special:Emailuser/Wetmoko Contact]

=== Texas ===
==== Austin ====
* Dale Schumacher [[Special:Emailuser/dalnefre|Contact]]

=== Mid-Atlantic ===
==== Virginia====
===== Richmond (1/10)=====
* Philippe Gerard [[Special:Emailuser/feydreva|Contact]]

==== New York ====
Status: 2/10

* Bert Hartmann [http://wiki.openmoko.org/wiki/Special:Emailuser/BertHartm Contact me here]
* Michael Cole mailto:mjcole137@gmail.com 

== UK ==
=== London ===
==== London ====
Status : 5/10

* Juergen Schinker mailto:ba1020@homie.homelinux.net
* Tim Coggins (actually in Oxford) [http://wiki.openmoko.org/wiki/Special:Emailuser/Sonicated Contact]
* David Pottage (actually in Reading) [http://wiki.openmoko.org/wiki/Special:Emailuser/chrestomanci Contact]
* aled [http://wiki.openmoko.org/wiki/Special:Emailuser/aled Contact]
* Bin Zong (actually in Birmingham) [mailto:hunter_00zb@hotmail.com]

== Latvia ==
=== Riga ===
==== Riga ====
Status : 1/10
* [[User:VRGhost]]
[[Category:Information| ]]
[[Category:community| ]]

Group sales

2008-04-18T14:22:41Z

ScaredyCat: /* The Netherlands */

== Australia ==
=== Western Australia ===
==== Perth ====

* Fred Janon mailto:fjanon@yahoo.com

=== Victoria ===
==== Melbourne ====
Status: 4/10

* Dennis Wollersheim dewoller (at) gmail (dot) com 4x

=== ACT ===
==== Canberra ====
Status: 1/10

* J Dinale [http://wiki.openmoko.org/wiki/Special:Emailuser/Noledil Contact me here]

=== Queensland ===
==== Brisbane ====
Status: 2/10 (possibly 20)

* Nick Devereaux [http://wiki.openmoko.org/wiki/Special:Emailuser/Monkeypanic Contact me here]

== Austria ==
=== Wien ===
* M. Greifeneder [http://wiki.openmoko.org/wiki/Special:Emailuser/mikegr Contact me here]
=== Styria ===
==== Graz ====
Status: 2/10

* F Hackenberger [http://wiki.openmoko.org/wiki/Special:Emailuser/Deadman66 Contact me here]
* D. Kepplinger [http://wiki.openmoko.org/wiki/Special:Emailuser/Wedge Contact me here]

== Belgium ==
=== Flanders ===
==== Brussel/Aalst/Gent/Brugge ====
Status 3/10 ps:Dolfje can bring freerunners to Brugge if needed

* Yorick mailto: yorick DOT matthys AT gmail DOT com
* 2x Dolfje [http://wiki.openmoko.org/wiki/Special:Emailuser/Dolfje Contact me here]

==== Antwerp ====
Status 4/10

* michielv [http://wiki.openmoko.org/wiki/Special:Emailuser/Michielv Contact me here]
* Peter N [http://wiki.openmoko.org/wiki/Special:Emailuser/Bubsy Contact me here]
* Ivo [http://wiki.openmoko.org/wiki/Special:Emailuser/Ivo Contact me here]
* Peter Leemans mailto: peter AT x-tend DOT be

== Bulgaria ==
=== Sofia ===
==== Sofia ====
Status : 2/10

* Dimitar Staykov meditache@gmail.com
* Vernim [http://wiki.openmoko.org/wiki/Special:Emailuser/Vernim Contact]

== Canada ==
=== Ontario/Quebec ===
==== GTA (Toronto) ====
Status : 2/10

* Gerald A [http://wiki.openmoko.org/wiki/Special:Emailuser/Historybuff Contact me here]
* MattC quirkz AT gmail

== Denmark ==
If we do not reach a total large enough, Denmark **is** a very small place - surely we could figure out a way of getting them to find their way 'round the country :)

=== Jutland ===
==== Aalborg ====
Status: 2/10

* Dan Leinir Turthra Jensen mailto:admin@leinir.dk [[User:Leinir]]
* Fabian Olesen mailto:firewalkerx@gmail.com

=== Fyn ===
Status: 1/10

* [[User:EsbenDamgaard]]

=== Sjælland ===
==== Copenhagen ====
Status: 1/10

* [[User:Fursund]]

== Finland ==
=== Uusimaa ===
==== Helsinki (Full)====
Status : 10/10

* Mikko Rauhala x2 [mailto:mjr@iki.fi mjr@iki.fi]
* Aleksi Hankalahti [mailto:aleksi.hankalahti@iki.fi aleksi.hankalahti@iki.fi]
* Seppo Hätönen [mailto:karrde@iki.fi karrde@iki.fi]
* Arttu Sund [mailto:thearttu@gmail.com thearttu@gmail.com]
* Ville-Pekka Vainio vpivaini AT cs.helsinki.fi
* Heikki Hallamaa [mailto:heikki.hallamaa@iki.fi heikki.hallamaa@iki.fi]
* Tomi Jylhä-Ollila tomi.jylha-ollila@helsinki.fi
* Richard Braakman
* Timo Jyrinki [mailto:timo.jyrinki@iki.fi timo.jyrinki@iki.fi]

==== Helsinki ====
Status : 4/10

* |[[User:Piksi]]
* Risto H. Kurppa risto AT kurppa DOT fi
* Aapo Rantalainen aapo DOT rantalainen AT gmail DOT com
* Matti Laakso matti DOT laakso AT kotiposti DOT net

=== Varsinais-Suomi ===
==== Turku ====
Status : 1/10

* Teemu Välimäki [mailto:teemu.valimaki@iki.fi teemu.valimaki@iki.fi]

== France ==
=== Bretagne ===
==== Brest ====
Status : 1/10

* StevenLeRoux [mailto:steven@pourri.fr steven@pourri.fr] Jabber_Id:Steven@jabber.fr
* Acheteur potentiel #2

==== Rennes ====
Status : 1/10

* Cédric DUFOUIL (openmoko at tsleg point com)
* Acheteur potentiel #2

=== Ile de france ===
==== Paris ====
Status : 9/10

* StevenLeRoux
* [[User:Phyce|Phyce]]
* Yann SLADEK
* [[User:Wilk|Wilk]] [http://wiki.openmoko.org/wiki/Special:Emailuser/Wilk Contact me here]
* Charles Clément (caratorn at gmail dot com)
* Jonathan Magano (jonathanmm[AT]free[DOT]fr)
* Benjamin Renard (bn8[AT]zionetrix.net)
* [[User:OlivierBerger|OlivierBerger]]
* [[User:BartGS|BartGS]] [http://wiki.openmoko.org/wiki/Special:Emailuser/BartGS Contact me here]

You may also see :
http://bearstech.com/openmoko/register

=== Pays de la Loire ===
==== La Roche sur Yon ====
Status : 1/10

* [http://wiki.openmoko.org/wiki/Special:Emailuser/Vtouchar Vincent Touchard] (I may soon move to Bretagne/Brest)

== Germany ==
=== Sachsen-Anhalt ===
==== Stendal (evtl. Magdeburg) ====
Status 1/10

* Fabian Off [http://wiki.openmoko.org/wiki/Special:Emailuser/Fabian2de Contact me here]

=== Hamburg ===
==== Hamburg ====
Status 1/10

* Jan [http://wiki.openmoko.org/wiki/Special:Emailuser/Jan07 Contact me here]

=== NRW ===
==== Bielefeld ====
Status 3/10

* David, infos on my [[User:Raven|user page]], or you can [[Special:Emailuser/Raven|contact me here]]
* Sebastian, infos on my [[User:Seppi|user page]], or you can [[Special:Emailuser/Seppi|contact me here]]
* Dackel, infos on my [[User:Killerdackel|user page]], or you can [[Special:Emailuser/Killerdackel|contact me here]]

== Italy ==
If we don't reach the 10 phones in each city, maybe we could place an order in the "most requested city", and from shipping to other buyers. We'll have anyway a good discount although the "double-shipping". ([http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/10937/focus=10981 Read here for reference]).

=== Toscana ===
==== Firenze ====
Status 2/10

* Marco Trevisan [http://blog.3v1n0.net/contatti-trevino/ Contacts here]
* [[User:Niccolo|Niccolo]] 11:13, 18 April 2008 (CEST)

=== Lombardia ===

==== Milano ====
Status 5/10

* Marco Crociani [http://wiki.openmoko.org/wiki/Special:Emailuser/Tyrael Contacts here]
* Marcello Gorla
* Maxxer [mailto:maxxer@yetopen.it maxxer@yetopen.it] (Lecco)
* Pietro Montorfano [mailto:monto84@gmail.com monto84@gmail.com] (from como)
* Gianluigi Belli [http://wiki.openmoko.org/wiki/Special:Emailuser/Pulciux Contacts here]

=== Trentino-Alto Adige ===
==== Trento (Padova too :)) ====
Status 1/10

* Andrea Debortoli (debortoland AT gmail DOT com)

=== Veneto ===
==== Verona ====

* Persegat [mailto:persegat@alice.it persegat@alice.it] [[User:Pecce|Pecce]]

=== Puglia ===
==== Lecce ====
Status : 1/10

* [[User:Morpheus90|Morpheus90]] [mailto:ugopiemontese@rudiaelinux.com ugopiemontese@rudiaelinux.com]
==== Bari ====
Status : 2/10

* [[User:Fradeve11|Fradeve11]] [mailto:fradeve@ubuntu-it.org fradeve@ubuntu-it.org]

== The Netherlands ==

* Marcel de Jong 1/10 [[User:madjo]]
* Christ van Willegen 1/10 [[User:ChristW]]
* Peter van de Werken 3/10 [[Special:Emailuser/User:PWerken|Contact]]
* Marijn Kruisselbrink 1 [[Special:Emailuser/User:mkruisselbrink|Contact]]
* Eric Spierings 1/10 [[User:ericsp]]
* Andy Powell 1/10 [[User:ScaredyCat]]
=== Overijssel ===
==== Hengelo ====
* Sander Hoentjen 4/10 [[Special:Emailuser/User:Tjikkun|Contact]]
==== Status ====
12/20

== New Zealand ==
=== Auckland ===
==== Auckland ====

* Rob Paulson 1/10 [[User:Myfanwy]]

== Norway ==
=== Nordland ===
==== Bodø ====
Status 3/10

* [[User:AlecTBM|Alexander Frøyseth]] [mailto:alexander.froyseth@gmail.com alexander.froyseth@gmail.com]
* Ole Marius
* Marius Andersen

=== Østlandet ===
==== Oslo&Akershus ====
Status 11/20

* [[User:Ixian|Heikki Sørum]] [mailto:heikkis@matnat.uio.no] Interessert? mail meg.
* [[User:Bobkare|Knut Arne Bjørndal]] [mailto:bob@cakebox.net]

== Poland ==
=== dolnośląskie ===
==== Wrocław ====

* Special group buy site: https://www.kumulator.pl/show/group/35

== Portugal ==
=== Aveiro ===
==== Aveiro ====
Status : 2/10

* Ruben Mendes
* [[User:kuyky|Tiago Saraiva]] [mailto:destructhor88@gmail.pt]

== Sweden ==
If insufficient number of people, orders could be merged and remailed perhaps

=== Svealand ===
==== Stockholm ====
Status : 2/10

* Erland Lewin mailto:erland@lewin.nu
* Simon Kågström mailto:simon.kagstrom@gmail.com

==== Örebro ====
Status : 1/10

* Anders Petersson [mailto:demitar@worldforge.org demitar@worldforge.org]

=== Norrland ===
==== Umeå ====
Status : 1/10

* [[User:Zash|Zash]] [[Special:Emailuser/Zash|Contact]]

== Switzerland ==
=== Zurich ===
==== Zurich ====
Status : 7/10

* Simon Wenner [http://wiki.openmoko.org/wiki/Special:Emailuser/Nowic Contact]
* Simon Schreiber [http://wiki.openmoko.org/wiki/Special:Emailuser/Magbeat Contact]
* Markus Huggler [http://wiki.openmoko.org/wiki/Special:Emailuser/Magbeat Contact]
* Andre Timmermann [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Raffael Schmid [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Pascal Weller [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Nick Zbinden [mailto:nickik@gmx.ch]

== Spain ==
=== Madrid ===
==== Madrid ====
Status : 1/10

* Rafael Campos [http://wiki.openmoko.org/wiki/Special:Emailuser/Methril Contact]

=== Zaragoza ===
==== Zaragoza ====
Status : 1/10

* Alejandro R. Mosteo alejandro AT mosteo · com

=== Barcelona ===
==== Barcelona ====
Status : 1/10

* José Luis Pérez [[Special:Emailuser/jluis|Contact]]

== USA ==
=== Colorado ===
==== Denver ====
Status: 7/10
* Shawn Sullivan [[mailto:shelbydz87@yahoo.com shelbydz87@yahoo.com]]
* Peter Abplanalp [http://wiki.openmoko.org/wiki/Special:Emailuser/alderion Contact]

=== Southern California ===
==== Los Angeles ====
Status: 2/10

* Ian Douglas [http://wiki.openmoko.org/wiki/Special:Emailuser/Iandouglas Contact me here]
* Matthew [http://wiki.openmoko.org/wiki/Special:Emailuser/Wetmoko Contact]

=== Mid-Atlantic ===
==== Virginia====
===== Richmond =====
* Philippe Gerard [[Special:Emailuser/feydreva|Contact]]
==== New York ====
Status: 1/10

* Bert Hartmann [http://wiki.openmoko.org/wiki/Special:Emailuser/BertHartm Contact me here]

== UK ==
=== London ===
==== London ====
Status : 5/10

* Juergen Schinker mailto:ba1020@homie.homelinux.net
* Tim Coggins (actually in Oxford) [http://wiki.openmoko.org/wiki/Special:Emailuser/Sonicated Contact]
* David Pottage (actually in Reading) [http://wiki.openmoko.org/wiki/Special:Emailuser/chrestomanci Contact]
* aled [http://wiki.openmoko.org/wiki/Special:Emailuser/aled Contact]
* Bin Zong (actually in Birmingham) [mailto:hunter_00zb@hotmail.com]

== Latvia ==
=== Riga ===
==== Riga ====
* [[User:VRGhost]]
[[Category:Information| ]]
[[Category:community| ]]

Main Page

2008-04-16T13:53:05Z

ScaredyCat: /* minor phrase mod */

{{Languages|Main_Page}}
__NOTOC__
__NOEDITSECTION__
__NOTOC__
{| cellspacing="4" cellpadding="0" style="padding: 2%; margin:0em 0em 1em 0em; border:1px solid #c8bbbf; background:#ECE5B6; width:100%"
| <big>'''Welcome to the [[Openmoko]]™ public Wiki'''</big> 
|}

[[Image:GTA02.gif |200px|right|frontside]]
Openmoko™ is an [http://en.wikipedia.org/wiki/Open_source Open Source] project under[[License| GPL and LGPL license]]. The aim of Openmoko is to build the world's first free mobile platform which runs a full X server and can therefore run most X applications. You can install any [[Openmoko]] software over the whole range of [[OpenMoko-supported hardware|supported phones]], and if you upgrade your phone, you won't lose that software. Bugs fixed on any phone are fixed on all.

The [[Neo1973 | Neo 1973 (GTA01)]] from [[FIC]] is the first of many phones that Openmoko may be used on. It has now sold out (Feb 08) as you can see at the [https://direct.openmoko.com/ Openmoko Online Shop]. [[Neo FreeRunner | Neo FreeRunner (GTA02)]] the new generation Openmoko mobile phone is not yet available - press [[Neo FreeRunner GTA02 Hardware| here]] to get more hardware information. Otherwise, scroll down this page for info on the development status , or you can add your nickname to those interested buying the Neo FreeRunner at [[Buying_Interest_List|Buying Interest List]].
The [[Openmoko]] project is a community that anyone can join, to help design their ideal phone. Please join us in collaborating on the Openmoko project through any of the [[Development resources | project resources]] including this Openmoko wiki. Please see the [[Help:Contents | wiki editing help]] page for information on making contributions to this wiki. A [[Meet the Core Team | core team]] of developers funded by FIC, Inc. leads the project.

To the novice, can start by use [[introduction]] page , [[Introduction#Photos|photos]], [[Introduction#Videos|videos]] and [[Openmoko Wiki Official Index Page]], to take the overview of Openmoko and wiki. Moreover, the usual [[FAQ | Frequently Asked Questions]] (FAQ) and [http://lists.openmoko.org/mailman/listinfo/| mailing list] pages might be helpful. Developers may find the [[ChangeLog | change log]] an important resource.

{{warning|'''The Openmoko GUI applications are not suitable for end users yet.''' They are still in beta. Do not expect to always and reliably make and receive calls from the Openmoko GUI. Thanks to the openness of the FIC Neo1973 hardware, there is also an alternative to the Openmoko GUI: Qtopia 4.3.x is released under GPL and is at the edge of being usable for daily phone use.}}

{| class="wikitable" cellspacing="0" cellpadding="5" width=100%
! width=100% colspan="2" style="background:#C8B560;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Latest status
|-
|valign="TOP" width="50%" style="background:#FAF8CC;border-left:5px solid white;border-bottom:5px solid white;" |
* The latest Qtopia snapshot can now be successfully used to make and receive calls, to send and receive SMS and use Contacts for both. However, if you do not enable suspend, one battery will only last 3-5 hours, but in suspend, incoming calls do not wake up Qtopia! See [[Qtopia on Neo 1973]] for instructions.
|valign="TOP" width="50%" style="background:#FAF8CC;border-right:5px solid white;border-bottom:5px solid white;" |
* The [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/ latest build] can make and receive calls most of the time. Power management (suspend, standby time) are still experiencing problems. Reviews of the daily snapshot build are [[Snapshot_review|here]] and the recommended kernel and root image from the review will always be available [http://downloads.openmoko.org/recommended/ here]. Note that the recommended set is not always the latest, but is the most stable, reliable, and functional.
* For the latest status updates, see [[Community_Updates|Community Updates]]
* To get the overview of Openmoko Wiki, see [[Openmoko Wiki Official Index Page]].
|}

{| class="wikitable" cellspacing="0" cellpadding="5" width=100%
! width=100% colspan="2" style="background:#ADA96E;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | What's Your Interest?
|-
|valign="TOP" width="50%" style="background:#FAF8CC;border-left:5px solid white;border-bottom:5px solid white;" |
* [[Basic End-user]] - Information for end users who want basic functionality and no surprises
* [[Advanced End-user]] - Information for advanced end-users who want advanced and experimental functionality but who are not programmers
* [[Business Development]] - Exchange of commercial opportunities for promoting widespread end-user acceptance.
|valign="TOP" width="50%" style="background:#FAF8CC;border-right:5px solid white;border-bottom:5px solid white;" |
* [[Application Developer]] - Information for application developers, including ideas and specifications for applications, and tools to build them
* [[System Developer]] - Information for system developers, including bootloader, kernel, and libraries
* [[Hardware Developer]] - Information for hardware developers, including hardware specs and debug board
|}

{| class="wikitable" cellspacing="0" cellpadding="5" width=100%
! width=100% colspan="2" style="background:#C9BE62;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | System Specs
|-
|valign="TOP" width="50%" style="background:#FAF8CC;border-left:5px solid white;border-bottom:5px solid white;" |
* [[Neo1973_hardware|Neo 1973 (GTA01)]] - Specs of original Neo 1973 (GTA01) Hardware
* [[Neo_FreeRunner_GTA02_Hardware|Neo FreeRunner (GTA02)]] - Specs of Neo FreeRunner (GTA02) Hardware
|valign="TOP" width="50%" style="background:#FAF8CC;border-right:5px solid white;border-bottom:5px solid white;" |
* [[Openmoko Core Applications]] - Applications included in the core build of Openmoko
* [[Openmoko Community Applications]] - Featured downloadable applications from the Openmoko community
|}

{| class="wikitable" cellspacing="0" cellpadding="5" width=100%
! width=33% style="background:#ff9900;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | General
! width=33% style="background:#ff6633;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Developer Guides
! width=33% style="background:#cc3333;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Developer Reference Documentation
|-
|valign="TOP" style="background:#F4F4F4;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |
* [[Development resources | Project Resources]] - Provides a centralized location of all resources such as [[Development resources#Mailing_Lists|mailing lists]], [[Development resources#IRC | IRC]], and other software development oriented resources.

* [[Current events]] - Information on both past and future events where FIC or Openmoko had or will have a presence.
* [http://forums.makeopensource.com/ Unofficial Openmoko Forums] - Everyone is invited to collaborate with Openmoko users and developers on the forums.
* Most of the documentation and Wiki assumes you are using Linux; here are some notes for users of [[Other OSes]].
* [[MacOS_X|Mac OS X]] - Information specific for those who use Mac OS X
* [[OpenLab]] - A physical area where Openmoko can interact with FOSS community

'''Administrative + Organizational'''
* [[Shipping Notes]] - Information to help FIC figure out how to ship products to you, and how much it might cost.
* [[My Account]] - Ideas for what sort of account-based services FIC should provide with the phone.
* [[Hear Me FIC]] - Information to help FIC know what the community wants.
* [[Listen Up Community]] - Community's To-Do-List
* [[Wiki Issues]] - problems/requests regarding this Wiki

|valign="TOP" style="background:#F4F4F4;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |
* [[Getting Started with your Neo1973]]
* [[installation_guide|A guide for flashing and emulating the openmoko software]]
** [[Flashing_openmoko|Flashing Neo1973 with the kernel, the root filesystem and optionally u-boot.]]
** [[MokoMakefile|Building Openmoko using the MokoMakefile]]
** [[Application Development Crash Course]] -A very basic how-to for the new people.
** [[OpenMoko2007.2|Building Openmoko 2007.2]]
** [[Building Openmoko 2007.1 from scratch]]
*** [[Building a hello world application]]
*** Old [[Building Openmoko from scratch (pre-BBT)|Building Openmoko from scratch (pre-BBT)]]
** [[Running Openmoko on PC]]
*** [[Host-based development with Xoo and Xephyr|Getting Openmoko working on host with Xoo]]
*** [[Getting OpenMoko working on host with Xephyr|Getting Openmoko working on host with Xephyr]]
*** [[How to run OpenMoko Apps on PC|How to run Openmoko Apps on PC]]
*** [[Openmoko under QEMU]]
*** [[Test Openmoko Emulation with chroot image|Test Openmoko Emulation with a Prebuilt chroot Image]]
* [[Migration to bad block tolerant builds]]
* [[Booting from SD]]
* [[DailyBuiltImages|Getting daily built images]]

|valign="TOP" style="background:#F4F4F4;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;"|
'''Hardware Reference Documentation'''
* All [[:Category:Hardware|Hardware]] related documentation and specifications are found on the [[:Category:Hardware|Hardware page]].
* The [[Neo1973 Hardware]] page provides an overview of the hardware components used by the [[:Category:Neo1973 Hardware|Neo1973 hardware platform]]. PCB photographs are also included. A [[Disassembling Neo1973 | photo disassembly story]] may be an interesting starting place.
* [[:Category:Neo1973 Hardware Debugging | Neo1973 Hardware Debugging]] is assisted with the [[Debug Board | Neo1973 debug board]]. A page discussing [[Connecting Neo1973 with Debug Board v2 | debug board and Neo1973 configurations]] is also provided.

'''Software Reference Documentation'''
* Architectural
** [[OpenmokoFramework]] - The Openmoko Application Framework
* [[Neo1973 host software]]
* Device Software
** Low-Level
*** [[u-boot]] - The bootloader we use, including documentation for our modifications
*** [[kernel]] - The Linux kernel we use, including documentation for our modifications
** Userspace
*** [[binary compatibility]]
*** [[gsmd]] - the GSM daemon managing the GSM Modem
*** [[gpsd]] - the AGPS (Assisted GPS) daemon
|}

{| class="wikitable" cellspacing="0" cellpadding="5" width=100%
! width=33% style="background:#99ccff;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Openmoko-specific Development
! width=33% style="background:#B3DDF4;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Openmoko Miscellaneous Development
! width=33% style="background:#00ccff;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Miscellaneous
|-
|valign="TOP" style="background:#F4f4f4;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |
* [[Roadmap]] - Roadmap for further Openmoko development
* [[OpenEmbedded]] - The distribution-building framework
* [[Toolchain]] - The toolchain we use for compilation
* [[Openmoko]] - The Openmoko distribution
** [[Openmoko2007]] - The first intended release of it
** [[Openmoko2007.2]] - An improved release with more formalized style guidelines.
** [[Userspace root image]]
* [[Test Plans]] - How we test our phones
* [[Prototypes]] - Tracking prototypes
* [[GSM network registration]] - Tracking network registration status in the world

'''User Interface Related'''
* [[GUI Style Guidelines]] -- New for [[Openmoko2007.2]]
* [[Look & Feel]]
** [[Artwork]]
* [[Applications|Application Roadmap]]
* [[Widgets]]
** [[Widget Inheritance Graph]]
* [[Application UI Design Recommendations]]

|valign="TOP" style="background:#F4f4f4;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |
* [[Thesis work]]
* [[Freshman todo]]
* [[Templates]]
* [[PIM Storage]]
* [[Coding Guidelines]]
* [[OpenMoko#Setting_up_an_OpenMoko_SDK|How to setup the Openmoko SDK]]
* Alternative distributions for [[Neo1973]] GTA01: [[Angstrom on Neo1973]], [http://pokylinux.org Poky] [http://www.usome.com](instructions needed!)
* [[License]] - How we license our code
* [[Development resources]] - Describes resources for developers (lists, svn, ...)
* [[Neo1973 Phase 0]] - Information for Phase 0 device owners
* [[Wishlist:Neo1973 P0 Review]] - Impressions of the Phase 0 hardware device, also the Phase 0 FAQ
* [[Neo1973 Phase 1]] - Information for Phase 1 device owners
* [[Wishlist:Neo1973 P1 Review]] - Impressions of the Phase 1 hardware device
* [[External Feeds]] - List of feeds from people blogging about Openmoko

|valign="TOP" style="background:#F4f4f4;border-left:5px solid white;border-right:5px solid white;border-bottom:5px solid white;" |
* [[WiFi support in Openmoko]]
* [[Neo1973 and Windows]]
* [[Press Coverage]] - What the press says about the Openmoko project
* [[mFAQ]] - The Openmoko Misinformation FAQ ('''mFAQ''') - What the press '''''incorrectly''''' says about the Openmoko project
* [[Openmoko Core Applications]] - Applications (GUI based) currently included in the main/core build of Openmoko
* [[Wish List]]s: [[Wish List - Hardware|Hardware]], [[Wishlist:BuiltInScriptingLanguage|Scripting Languages]], [[Wish List - OpenMoko Ringtones and Sounds|ringtones and sounds]]
* [[Media Content]] - What types of media on the device can we use (that is non-software)?
* [[Testimonials]] - How did you get to Openmoko?
* [[Buying Interest List]] - (Not official and not a pre-order page) Have you put money aside for Neo1973? Put your nick here.
* Comparison with the [[iPhone]]
* [[Translation]] of Openmoko
* Project applications for Google's [[Summer of code]]
* Purchase Openmoko [[SWAG]] T-Shirts!
* The Openmoko [[Trademark Policy]]
|}

The members of the Openmoko community would like to thank FIC Inc. for their continued leadership of the Openmoko project.



[[Category:Information| ]]
[[Category:Categories| ]]

Users Repositories

2008-03-19T20:42:24Z

ScaredyCat: /* fix wrong dir for scaredycat.conf */

=== Repositories ===
here you can find prebuilt kernels and root file systems.

* '''Official downloads'''
:* Recent/latest builds
::* OM2007.2
:::http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D
::* OM2007.1 (Obsolete)
:::http://buildhost.openmoko.org/OM2007.1/tmp/deploy/images/?C=M;O=D

:* Snapshots [http://downloads.openmoko.org/snapshots/]
::* 2007.11 - the latest (2nd Dec) snapshot ([http://lists.openmoko.org/pipermail/community/2007-December/011980.html from Mickey])
:::http://downloads.openmoko.org/snapshots/2007.11/images/
::* 2007.08 snapshot, as announced by Sean on August 19
:::http://downloads.openmoko.org/snapshots/2007.08/images/

:* Daily
::* Unstable Daily-builds
:::http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/?C=M;O=D
* '''Unofficial builds'''
:* '''[[User:ChooseOpen|ChooseOpen]]'''
::http://chooseopen.com:81/openmoko/build/2007.2/?M=D
::http://chooseopen.com:81/openmoko/build/qtopia/?M=D (Qtopia)

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

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

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

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

:* - (2007.2)
::http://www.totalueberwachung.de/~alphaone/openmoko-build/glibc/images/fic-gta01/?C=M;O=D

:* '''celtune''' unofficial builds
::http://celtune.morb-design.com/images/fic-gta01/?C=M;O=D
::http://celtune.morb-design.com/ipk/
::Celtune offers Standard-Builds (.jffs2, .tar, .bin, .ipk) and several special-images with additional packages (e.g. monster-images,navigation-images,...)
::For more info take a look at http://celtune.morb-design.com/images/fic-gta01/1-NEWS-WARNING-INFO

cd /etc/ipkg && wget http://celtune.morb-design.com/celtune.conf

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

=== Angstrom Repository ===
If there's a package you need that is missing from the feeds listed above you can search the Angstrom repo [http://www.angstrom-distribution.org/repo/ here].

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

src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/

[[Category:OpenMoko]]

GSM network registration

2008-03-18T10:36:14Z

ScaredyCat: /* Results table */

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

== Instructions ==

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

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

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

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

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

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

== Results table ==

{| border="1"
| Owner || Location ||| Network Provider || How/When purchased SIM card || Device || GSM firmware || IMEI || Status || GSM log
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||T-Mobile|| with phone, > 2years ||GTA01||Moko6||YES||just fine||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| with phone, 8/28/07 ||GTA01||Moko6||YES||takes several minutes to register, home network rejects, CME error 32, reregisters continuously||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| replacement for one received with phone, 3/17/08 ||GTA01||Moko6||YES||preliminary test: registers promptly to home network. Will test in various locations and report back.||no
|-
| [[User:MichaelShiloh]] || San Francisco, CA, USA ||AT&T|| prepaid, no phone, 3/13/08 ||GTA01||Moko6||YES||just fine in some locations, but in others it takes several minutes to register and reregisters continuously. however, always better than card that came with phone||no
|-
| [[User:SpeedEvil]] || Fife, Scotland, UK||T-Mobile|| ||GTA01||Moko1||YES||Just fine||no
|-
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no
|-
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the re-registering loop starts once per minute|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]
|-
| [mailto:ahvenas@gmail.com Henrik Pihl] || Kuressaare, Estonia || Elisa || || GTA01Bv4 || Moko4 || YES || Normal, can register to the network immediately, but starts reconnecting to the network in the first minutes.|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=555&action=view log]
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || Era (Heyah) || prepaid, bought in October 2007, never charged, expired || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Card expired, home network rejects it with CME Error 32 (emergency calls only), system displays "Registering..." for several minutes. || NO
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || PlusGSM || prepaid, several years old, not charged || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Registered after entering PIN. Normal work after register. || NO
|-
| [mailto:plr@udgaard.com Peter Rasmussen] || Copenhagen Denmark || DK Sonofon || || GTA01Bv4 || Moko1 || YES || Registered immediatly after entering PIN. Works after that. No /tmp/gsm.log appears || NO
|-
| [[User:Kevin_Dean | Kevin Dean]] || Washington DC Metro Area, USA || T-Mobile || || GTA01Bv4 || Moko1 || YES || Normal, can register to the network immediately, no PIN needed|| [http://www.monochromementality.com/data/files/logs/openmoko/2008-03-17/gsm.log.edited Log (Replaced my wife's # with 9991231122)]
|-
| [[User:Dennis_Wollersheim | Dennis Wollersheim]] || Melbourne, Australia || Telstra || || GTA01Bv4 || Moko4 || Yes || Registers quickly, reregisters every 30 seconds or so|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=556&action=view gsm log]
|-
| [[User:thomasg | Thomas Gstädtner]] || Nuremberg, Germany || T-Mobile (Ericsson RBS2206, GSM900) || 2004 || GTA01Bv4 || Moko 1 || Yes || Registers nearby immediately, w/ PIN or w/o || NO
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA01Bv4 || Moko 1 || Yes || No problems || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA02 || Moko 6 || No || Does not register, pin entry works, net scan also. || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || e-plus || 200x || GTA02 (same as above) || Moko 6 || No || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Ipswich, UK || Virgin || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Lelystad, Netherlands || Virgin (Roaming on T-Mobile NL) || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|}

[[Category:Hardware]]
[[Category:GSM]]

Manually using GPRS

2008-03-08T14:51:33Z

ScaredyCat: /* 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 || 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 || ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| 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-08T14:50:27Z

ScaredyCat: /* added Virgin APN */

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 || 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 || ||
|-
| Norway || Netcom || Any || internet.netcom.no || ||
|-
| Switzerland || Swisscom || e.g. Natel Basic Liberty, behind NAT || gprs.swisscom.ch || ||
|-
| UK || T-Mobile|| || general.t-mobile.uk || ||
|-
| UK || Virgin || || goto.virginmobile.uk || ||
|-
| 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]]

Java

2008-02-29T17:16:18Z

ScaredyCat: /* Typical Java programmers, can't even count... */

== Introduction ==
There are three main types of Java platforms that can be made available on OpenMoko devices such as the Neo1973.
* Java Standard Edition (J2SE)
* Java Micro Edition (J2ME)
* Hybrid Solutions

=== Java Standard Edition (J2SE) ===

This is the incarnation of the desktop version of Sun's Java platform. The majority of its codebase was recently opensourced under the GPL+exception license; the closed bits are quickly being replaced by unencumbered alternatives.

When people talk of Java applications, they're usually referring to software targetted to this platform. Application memory footprints on desktop applications usually include the VM and base libraries into account, rather than just the application itself (this isn't the case in J2ME).

=== Java Micro Edition (J2ME) ===

This is the 'lite' edition of the Java platform. Modular and optimised for embedded devices, this platform provides a much more restricted set of language and library features.

J2ME applications are usually referred to as MIDlets (Sun's name for these applications).

When talking about games, and mobile phone games in general, people are normally referring to this platform. J2ME games and applications are expected to function within the strict memory capabilities of the corresponding platform (application descriptors allow the runtime environment to know for which they are intended).

Memory footprints of MIDlets written for J2ME are typically quoted exclusive of the VM or base libraries - this is because they are often delivered to Java-enabled devices over the network. Footprint sizes average 10-64KB, with recent devices supporting up to 1MB MIDlets.

MIDlet are delivered as two files:
* a .jad MIDlet metadata descriptor
* a .jar MIDlet container, containing executable bytecode and any required resources

=== Hybrid Solutions ===

Other approaches include mixing and matching J2SE and J2ME in various ways. Standard methods include providing a compatibility layer on top of J2SE (like [http://www.microemu.org/ microemu]) to allow it to run J2ME and expanding J2ME to provide more J2SE features.

Another possible approach would be to have every application compiled to native with gcj when installed and then run without a JVM, with a much faster startup. This may be risky and needs a specialized installer.

== Implementations ==

=== J2SE implementations ===
* [http://www.cacaojvm.org/ Cacao] is a Java Virtual Machine (JVM) which uses Just-In-Time (JIT) compilation to execute Java methods natively.
* [http://jamvm.sourceforge.net/ JamVM] is a JVM with a very small footprint (<160k).
* [http://en.wikipedia.org/wiki/Icedtea Icedtea] is basically OpenJDK with some improvements

=== J2ME implementations ===
* [https://phoneme.dev.java.net/ PhoneME] is basically the code base of Sun's commercial Java ME implementation without those components that Sun can't --or won't-- release to the open source community. It is licensed under GPL2. There are actually two versions of PhoneME:
*;PhoneME Feature: is an implementation of the CLDC (Connected Limited Device Configuration) and MIDP2 (Mobile Information Device Profile) as is common on feature phones (e.g. 'normal', non-smart phones).
*;PhoneME Advanced: is an implementation of the more complex CDC (Connected Device Configuration), designed for more advanced handsets.
* [http://midpath.thenesis.org MIDPath] is a Java library which provides a MIDP2 implementation and can be used together with the CLDC version of the Cacao to provide an alternative implementation of CLDC/MIDP.
* [http://www.microemu.org/ Microemu]: a J2ME emulator that runs on top of J2SE. If the overhead is small enough, it should be the 'cheapest' solution.

== Status on OpenMoko ==
[http://java-pkg.projects.openmoko.org/ Java-pkg] is a [http://projects.openmoko.org/ projects.openmoko.org] [http://projects.openmoko.org/projects/java-pkg/ project] whose aim it is to "Get Java going on OpenMoko, and once it's running, maintain it. There are two sub-projects, one for JME and one for JSE. Priority is currently given to JME CDC profile." There is currently a work-in-progress recipe for PhoneME Advanced in their SVN, which doesn't fully build, as well as a working recipe for PhoneME Feature, which only works directly on the Neo1973 framebuffer (e.g. you'll have to stop Xfbdev).

[http://www.jalimo.org Jalimo] is a project, to feature the integration of free Java-like implementations for free platforms. They already have [http://www.jalimo.org/wiki/doku.php?id=packages#openmoko_2007.2 packages for Openmoko 2007.2], covering Cacao, GNU Classpath (with Swing support), SWT and the java-gnome bindings, which allows writing GTK+ applications in Java. Build recipes are part of OpenEmbedded and maintained therein.

== Licensing ==

=== VM Licensing ===

=== MIDlet Licensing ===

== Links ==

Google should be your first port of call for most things Java as it would be impossible to give a comprehensive list of all the useful information out there. That being said, below is a selected list of further information resources.

=== J2SE Links ===

In 2006/7 Sun [http://www.deviceforge.com/news/NS9280947932.html acquired the assets of Savaje], which included a port of J2SE to ARM Linux. This was used to build the "JavaFX" modules and, in fact, it runs on the Neo1973 already. They used it to show JavaFX at the JavaOne 2007: http://java.sun.com/javaone/sf/media_shell.jsp?id=193609 See also http://blogs.sun.com/jonathan/entry/when_not_where

=== J2ME Links ===

[[Category:Software]]
[[Category:Applications]]
[[Category:Developer software]]
[[Category:Unimplemented]]

Building a hello world application

2008-02-09T08:17:53Z

ScaredyCat: /* corrected export line - make it match what is used in the compile */

=== Preparation ===
This guide assumes that you have performed the steps in [[Building_OpenMoko_from_scratch]]

=== The commandline program ===
Store the following more or less standard hello world code in hello.c

#include <stdio.h>

int main()
{
printf ("Hello World\n");
return 0;
}

=== Compiling it the ''wrong'' / easy way ===
Assuming your current working directory is '''/home/moko''', and that you stored the code in '''/home/moko/hello.c''' it should now be possible to compile the application using
./build/tmp/cross/arm-linux/bin/gcc -o hello hello.c

==== Testing it ====
Assuming you have followed [[OpenMoko_under_QEMU#Setting_up_USB_connection|Setting up USB connection]] and you have a working network connection to either a qemu Neo or a real Neo.
scp hello root@192.168.0.202:/tmp/
ssh root@192.168.0.202 /tmp/hello
This sequence of commands ought to give you a nice ''Hello World'', btw. the default root password is blank, just press return.

=== GDK the Wrong / Easy Way ===
Building a GDK application the wrong way is slightly more complex, but is still fun to try. It requires using pkg-config to specify including and linking with the ARM header files and libraries.

Given the following program as main.c:

#include <gtk/gtk.h>

gchar *hello = "Howdy";
gchar *world = "World";
GtkWidget *label;
gchar *labeltext;

void buttoncb(GtkWidget *widget, gpointer data)
{
if (labeltext == hello)
{
labeltext = world;
gtk_label_set_text(GTK_LABEL(label), labeltext);
}
else if (labeltext == world)
gtk_main_quit();
}

int main(int argc, char *argv[])
{
GtkWidget *window;
GtkWidget *button;

gtk_init(&argc, &argv);
window = gtk_window_new(GTK_WINDOW_TOPLEVEL);
button = gtk_button_new();
labeltext = hello;
label = gtk_label_new(labeltext);
gtk_container_add(GTK_CONTAINER(button), label);
g_signal_connect(G_OBJECT(button), "clicked", G_CALLBACK(buttoncb), NULL);
gtk_container_add(GTK_CONTAINER(window), button);
gtk_widget_show_all(window);
gtk_main();

return 0;
}

You must first point pkg-config to the proper directory:

export PKG_CONFIG_PATH=/home/username/moko/build/tmp/staging/arm-linux/lib/pkgconfig

And set up an environment variable to make things easier:

export OMDIR=/home/username/moko

The compile/link line is rather long - you will only want to do this once before you decide to create a shell script or make file:

$OMDIR/build/tmp/cross/arm-angstrom-linux-gnueabi/bin/gcc -L $OMDIR/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/ \
-Wl, rpath-link, $OMDIR/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/ -Wl, -O1 -g -o hw main.c \
'$OMDIR/build/tmp/staging/i686-linux/bin/pkg-config --cflags --libs openmoko-libs gtk+-2.0'

Then copy and run as in the original hello world command line program above.

===== Why was it the ''wrong'' way? =====
OpenMoko uses [[http://www.openembedded.org/ OpenEmbedded]] and they use bitbake when building stuff, but at least you now know that you can cross compile for OpenMoko.

=== Compiling it using bitbake ===
If you set your enviroment (I created a small script to do this, you could also add it to you .bashrc)
export OMDIR=/home/username/moko
export BBPATH=$OMDIR/build:$OMDIR/openmoko/trunk/oe:$OMDIR/openembedded
You should be capable of
cd $OMDIR/build
bitbake nano
This should auto-magically fetch the recipe for baking nano and baking it. This results in some ipk packages being created in $OMDIR/build/tmp/deploy/ipk/armv4t/
''According to [[http://www.openembedded.org/wiki/UsefulTargets UsefulTargets | OpenEmbedded]] there is a helloworld target, however on my machine it fails with 'ERROR: Nothing provides dependency helloworld' '' 
While this hasn't brought us closer to actually baking a helloworld it demonstrates what we should eventually be capable of doing for our new and revolutionary software for OpenMoko.
==== An OpenEmbedded guide to creating a hello world ====
OpenEmbedded has a nice [[http://www.openembedded.org/user-manual&dpage=recipes_examples Wiki page]] on creating a hello world, I highly recommend it.

==== Creating an ipk package ====
To be written ''(Perhaps this is done by the do_install() function)''

{{Languages|Building_a_hello_world_application}}
[[Category:Software]]
[[Category:Guides]]

Talk:Problems of typical "closed" phones

2008-02-03T20:33:46Z

ScaredyCat: /* Clarification please */

Can you clarify please, many of the points you make are carrier issues not handset issues. Are you speaking from a US perspective, your initial reasons suggest this. If so please bear in mind that this is a worldwide device.

Many carrier will forbid the use of voip software regardless of wether you can run it on your phone or not, if they catch you using it they'll cut you off - the GTA01/02 are not going to help you there at all.

Problems of typical "closed" phones

2008-02-03T20:22:28Z

ScaredyCat: /* Removed 'unlocking is illegal' - it might be where you are from but not round here and most other countries */

This page is a list of "locked" features on "closed" mobile phones listed by members of the Openmoko community. Buying an [[Openmoko]] phone will free you from these problems!

{| border="1"
!Manufacturer / Model / Operating System / Operator
!Locked feature
!Comments
|-
|Many / Many / Many / Many
|Handset will only operate with SIM registered to a particular operator
|Can be "unlocked" but takes some effort or a small fee to someone providing this service.
|-
|O2 / Orbit / Windows Mobile 6 / O2
|Handset includes GPS but I bought the cheaper tarrif and this does not come with gps software. GPS capability has been locked by the operator and i cannot use it even with free applications like Google Maps for mobile which can use cell tower interpolation or GPS to provide location info
| O2 orbit = HTC Touch (i think)
|-
|Many / Many / Many / Many
|Operators do not allow an Internet Messaging application to be installed that could use GPRS (for those with cheap data plans) or Wifi to communicate with others. This is presumably because they are scared of losing SMS revenue.
|
|-
|Many / Many / Many / Many
|VOIP software to allow phone calls over the IP network is not allowed onto "closed" phones by most operators.
|Cheap phone calls to other VOIP enabled people are denied to you at locations where you have WiFi available
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|Please add your example here
|Your locked feature here
|Your comments here
|-
|}

{{Languages|Neo1973: GTA01Bv4 versus GTA02 comparison}}

[[Category:Neo1973 Phase 1 related]]
[[Category:Neo1973 Phase 2 related]]
[[Category:Information]]

Booting the Neo FreeRunner from SD via U-Boot

2007-11-12T09:03:42Z

ScaredyCat: /* note about bad uboots */

Here are the steps described to boot your system from an SD card.

{| cellspacing="5" cellpadding="0" style="padding: 2%; margin:0em 0em 1em 0em; border:1px solid #F9D163; background:#FCE9B4; width:100%"
|
Newer versions of u-boot don't work properly for booting from SD card. [http://buildhost.automated.it/u-boot-good-for-sd-boot-r13_0_2632_0.bin This one works], but as ever be careful when flashing u-boot as you can brick your device.
|}

=== Step 1: Change your kernel settings ===

Kernel building is supposed to be done through OpenEmbedded. If you use the MokoMakefile open up $OMDIR/openmoko/trunk/oe/packages/linux/linux-gta01/defconfig-2.6.21.6-fic-gta01. If you are building OM-2007.2 open $OEDIR/openembedded/packages/linux/linux-openmoko/defconfig-2.6.22.5-fic-gta01. (''Note that the kernel version may change in future versions.'')

Now find the line saying:

CONFIG_MMC_S3C=m

and change it to:

CONFIG_MMC_S3C=y

If you want to use an ext2 file system on the SD, also find the line saying:

CONFIG_EXT2_FS=m

and change it to:

CONFIG_EXT2_FS=y

If you're using MokoMakfile, you can clean out your last kernel build (forcing a new build) by running:

make clean-package-linux-openmoko

=== Step 2: Building a tarfile distribution ===

If you are building OM-2007.2 you need to add "tar" to the image types in your ''local.conf'':

IMAGE_FSTYPES = "jffs2 tar"

After building a new image by issuing ''bitbake openmoko-devel-image'' (or ''make openmoko-devel-image'' if you are using MokoMakefile) there will be a ''OpenMoko-....tar'' in the deploy directory.

=== Step 3: Populate SD card ===

Format partition 1 as ext3 (or better ext2 if enabled, see above). Mount your SD card somewhere and put your image on it:

mount /dev/sda1 /mnt/moko
tar -C /mnt/moko/ -xvf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar

Now we also want the kernel on there. In OM-2007.2 the last built kernel gets a special soft-link. Therefore you can copy it by doing:
cp uImage-fic-gta01-latest.bin /mnt/moko/boot/uImage

=== Step 3: Add uboot boot entry ===

On my Phase-1 Neo the boot menu entry existed already. If yours is missing it follow those instructions: Start uboot in bootmenu mode (= hold AUX while powering on) and add the following entry via serial console: (See [[Bootloader]] section on how to access an bootloader).

GTA01Bv4 # setenv menu_4 Boot from SD: setenv bootargs root=/dev/mmcblk0p1 rootdelay=5 console=ttySAC0,115200 console=tty0 loglevel=8 \${mtdparts}\; mmcinit\; ext2load mmc 0 0x32000000 /boot/\${sd_image_name}\; bootm 0x32000000
GTA01Bv4 # setenv sd_image_name uImage
GTA01Bv4 # saveenv

You can now easily boot a different kernel by changing the variable sd_image_name to the new name.

=== Step 4: Boot into the new system ===

Power off your device, insert the SD card and boot into the boot menu. You should have an entry called "Boot from SD" which does exactly that. :-)

== Installing without removing your SD card ==

Being the lazy person that I am, at one point I tried copying an image over to the micro SD card while still in my phone. This didn't work so well, primarily due to [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug 677].

Now that this bug has been resolved, the process becomes relatively simple:

* Boot to your internal flash partition (not the SD card.) Make sure you're running a release that includes the fix to bug 677!
* Plug in your USB and set up [USB Networking].
* Clean off your currently installed microSD card and install the new image:
ssh root@192.168.0.202 "rm -rf /media/card/*"
cat openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar | ssh root@192.168.0.202 tar -C /media/card -xv
scp uImage-fic-gta01-latest.bin root@192.168.0.202:/media/card/boot/uImage

== Boot from SDHC ==

As SDHC is currently not supported in u-boot you can't use the Booting from SD guide.
But there's a kind of workaround that is a good option to have at least your rootfs on the microSDHC:

First you can follow Step 1 to get an kernel-image with mmc- and ext2-support. But instead of copying the image to the rootfs you will have to flash it to the Neo's internal NAND-Flash (using [[Dfu-util]]).
Now you can continue with Step 2 (like mentioned before you do not have to copy your uImage to the rootfs) and follow the instructions to Step 3.
Instead of the setenv commands in Step 3 you have to enter the following:

GTA01Bv4 # setenv menu_5 Boot from SDHC: setenv bootargs root=/dev/mmcblk0p1 console=tty0 loglevel=8 rootdelay=5 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

And that's it!
Now you can use the newly created menu option "Boot from SDHC" to boot the internal kernel, using the root-filesystem on the microSDHC.

=== Autoboot from SDHC ===

Maybe you want to Boot automatically from SDHC:
Set a new Bootmenu Entry for booting from NAND first

GTA01Bv4 # setenv menu_6 Boot from NAND: setenv bootargs ${bootargs_base} \${mtdparts}\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

then Power-off, and enter the Bootmenu to test the new Entry.If you can boot from NAND, shutdown, enter Boot menu, connect to bootloader and set the (auto)bootcmd for boot from SDHC:

GTA01Bv4 # setenv bootcmd setenv bootargs root=/dev/mmcblk0p1 rootdelay=10 console=tty0 loglevel=8 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

Now you boot from SDHC everytime you press the Power-Button or reboot and if you like to boot from NAND -just use the bootmenu.

{{Languages|Booting_from_SD}}
[[Category:Software]]
[[Category:Guides]]

MokoMakefile

2007-11-07T10:53:17Z

ScaredyCat: /* correct typo in blond moment */

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

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

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

The MokoMakefile is able to build either OM-2007.1 or OM-2007.2 images. The core team chooses the default, but you can select one or the other at the top of the Makefile.

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

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

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

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

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

=== Required software ===
The version control system used by OpenEmbedded is [http://monotone.ca monotone], it is not downloaded and installed by MokoMakefile. If your distribution does not provide a package, you can download and install a static binary from http://monotone.ca

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

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

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

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

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

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

===== Debian / Ubuntu =====
apt-get install subversion monotone build-essential help2man
diffstat texi2html texinfo cvs gawk
apt-get install libncurses5-dev libz-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
apt-get install ca-certificates
# For OpenMoko 2007.2 using BitBake-1.8.8:
apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
apt-get install quilt python-psyco
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
apt-get install gcc-3.4 g++-3.4

===== SuSE =====
For building OpenMoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion texinfo help2man [http://download.opensuse.org/repositories/devel:/tools:/scm/openSUSE_Factory/repodata/repoview/Development.Tools.group.html monotone]
10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel. Use monotone for [http://download.opensuse.org/repositories/devel:/tools:/scm/openSUSE_10.2/repodata/repoview/Development.Tools.group.html 10.2] or [http://download.opensuse.org/repositories/devel:/tools:/scm/SUSE_Linux_10.1/repodata/repoview/Development.Tools.group.html 10.1]

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

== Building OpenMoko with MokoMakefile ==

1 - Create your $OMDIR directory (note that you can change ~/moko to any directory you like):
mkdir ~/moko ; cd ~/moko
2 - Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.nslu2-linux.org/svnroot/mokomakefile/trunk/Makefile

note: If you want to compile for the old version 2007.1 instead of the new
version edit the top of the Makefile. Edit the lines at the top to
look like this:
OPENMOKO_GENERATION = 2007.1
#OPENMOKO_GENERATION = 2007.2

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

3 - Set up the environment:
make setup
4 - Start building. Before starting a lengthy make process, check the Tips section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image

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

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

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

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

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

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

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

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

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

then run

make clean-package-<foo>

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

and finally

make openmoko-devel-image

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

===Known MokoMakefile errors ===
If you experience the following after changing from OM-2007.1 to OM-2007.2:

Patch bitbake-1.6.6-om3.patch does not apply (enforce with -f)

then type "make clobber-patches" to fix it. There was a period of 24 hours when there was a bug in the MokoMakefile which causes this problem. Once the patches have been clobbered, they will re-download and the problem will not reoccur.

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

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

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

*If you an encounter an error with monotone similar to the following:
mtn: misuse: database /home/''username''/moko/OE.mtn is laid out according to an old schema
Then you need to upgrade OE.mtn Use the following command while in ~/moko:
# mtn --db OE.mtn db migrate

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

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

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

*For amd64 host users you need the patch from http://bugs.openembedded.org/show_bug.cgi?id=1765 to build db3-native

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

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

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

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

==Developing with MokoMakefile==

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

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

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

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

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

To build the changes and have them used by qemu:

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

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

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

Then continue with MokoMakefile usage.

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

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

inherit autotools

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

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

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

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

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

=== Hello World application ===

There is a [http://wiki.openmoko.org/wiki/Building_a_hello_world_application Hello World!] tutorial available too.

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

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

{{Languages|MokoMakefile}}

[[Category:Developer]]
[[Category:Guides]]

Host OS Tips

2007-10-19T09:03:12Z

ScaredyCat: /* Start a page for OS specific stuff */

With a variety of linux distributions come a myriad of differences. Below are some quirks you may find when building, flashing or talking to your neo 1973

== OpenSuSE 10.2 ==

=== u-boot ===

When booting the new1973 in u-boot mode '''/dev/ttyACM0''' may not appear automatically. You may have to:

# modprobe cdc_acm

before hand. Conversely cdc_ether seems to work automatically without any issues.

USB Networking

2007-10-16T20:24:05Z

ScaredyCat: /* removed 'see above' - doesn't make sense, example is imediately below */

= Neo1973 side =

== Name resolution ==

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

A better aproach is to symlink

ln -s /var/run/resolv.conf /etc/resolv.conf

and fill the file at bootup with a script /etc/network/if-up.d/08setupdns containing:

#!/bin/sh -e
echo nameserver 192.168.0.200 > /var/run/resolv.conf

this way the file is correctly handled from ppp package when dialing into gprs.

== Routing ==

You need a additional route for traffic to the internet. This traffic can be routed through your pc (see below) if the pc is the default route destination. you can achieve this by adding

gateway 10.10.10.21

to your /etc/network/interfaces in the usb0 section.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

'''For Ubuntu Feisty:'''
Edit /etc/network/interfaces file ():
<pre>
auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu feisty appears to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once
after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:
<pre>
SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

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

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

== Proxying DNS requests ==

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my Neo /etc/resolv.conf only contains:

nameserver 192.168.0.200

and my laptop will proxy all dns requests based on it's own /etc/resolv.conf

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

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

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

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

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

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

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

Qtopia on Neo1973

2007-09-28T13:48:03Z

ScaredyCat: /* Where to get it source code */

== Where to get it ==
You can get everything you need [http://www.qtopia.net/modules/devices/openmoko.php from here]. Currently the flash tarball has the 2.6.21 openmoko kernel and a Qtopia phone edition jffs2 flash
image cross-compiled for the Neo.

If you want to build qtopia for yourself you can download the [ftp://ftp.trolltech.com/qtopia/tech-preview/ technical preview] or [ftp://ftp.trolltech.com/qtopia/snapshots/ snapshots]

It appears you must clear the flash chunks first (if you have not updated your uboot. If you have, you may skip this step). Get into uboot console [http://wiki.openmoko.org/wiki/Uboot#Accessing_the_bootloader_prompt] and enter

# nand erase kernel
# nand erase rootfs

Download and use dfu-util as normal [http://wiki.openmoko.org/wiki/Flashing_openmoko] and the ip address and cidr are the same as the openmoko build (192.168.0.202/24) :D - Simple, Eh?

Most things seem to work out of the box, however you may need to use the following command to get audio:

# alsactl -f /etc/alsa/gsmhandset.state restore
Or put this command in /etc/init.d/qpe line 64

Do not switch themes. Only the default theme is usable. For example, once you switch themes, the lock feature continues to work, but only if you unlock using the smallest # keypad in the world.

Suspend support is very flaky. The neo often shuts off from a suspend state. It will not wake from suspend for an incoming call or text message (someone try setting an alarm and report results here). To turn suspend off (this will of course use the batteries very quickly), hit the down arrow next to the suspend setting in the power management until it says "Off".

When using the virtual keyboard, do a quick flick up or down over the keyboard to access numbers/symbols/capitals.

In summary, Qtopia on the Neo1973 is much closer to being ready than OpenMoko as of this writing. However, sound and suspend support prevent it from being at all useful as a cell phone (as a landline that doesn't ring but instead vibrates, it works ok).

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]]

[[Image:Qtopia002.png]]

[[Image:Qtopia003.png]]

[[Image:Qtopia004.png]]

[[Image:Qtopia005.png]]

[[Image:Qtopia006.png]]

== Videos ==

http://www.youtube.com/watch?v=YW5q8SpY7t4
http://www.youtube.com/watch?v=iOG_mtSEMgs

For full size videos, 346 MiB:

http://linuxtracker.org/download.php?id=4613&name=qt_on_neo1973_videos.torrent

Neo1973 compatible cellphone providers

2007-09-20T19:31:09Z

ScaredyCat: /* United Kingdom - Virgin mobile*/

{|align=right
|__TOC__
|}
The Neo1973 uses quad-band [[GSM]] (850/900/1800/1900 MHz) so any GSM provider in the world should be compatible. In general, when you are looking for a mobile solution in your region, you would need to be aware of:
* the ''network coverage'' of available providers
* different ''tariffs'' of these providers
and choose the one that is right for you. If you haven't had any experience with GSM coverage in your area, you may want to inquire locally from the available providers and people you know that may already have experienced GSM at your location. You may also want to subscribe to our mailing list. If you have doubts about the coverage for your area, you may want to borrow a GSM phone or buy an inexpensive one so that you can get a feel for how the Neo1973 will work in your area. You can help keep your cost down by using a prepaid card for your testing.

Here is some information on Prepaid GSM cards:
* [http://www.prepaidgsm.net/ PrePaidGSM - worldwide overview about GSM prepaid offers]
Think twice before choosing a tariff with long duration contracts (more than 12 months), because prices for the GPRS data tariffs are ''likely'' to lower in many countries. Also, long duration contracts are mostly combined with hardware (ie: free or steeply discounted phone with a 24 or 36 month contract). It will be worth your while to shop around for competing offers from the different providers in your area.

We chose the GSM network format for the Neo1973 because GSM is in use by more countries than any other mobile phone standard. As a result, you will have better coverage with the Neo1973, and we felt that it was the best choice for our OpenMoko devices. When the Neo1973 is successful, and we believe that it will be, we will be developing new devices that we will be bringing to market. They will be running OpenMoko and supporting additional mobile phone network standards as well. So if GSM is not available in your area (ie: some areas in the USA), OpenMoko will be bringing other options to market in the future.

Below is a list of Neo1973-compatible providers around the world. Please help by filling this out ''alphabetically'':

There is also a [[Carriers]] page that should be merged with this section.

==Argentina==
* [http://www.movistar.com.ar/ Movistar]
* [http://www.personal.com.ar/ Personal]
* [http://www.cti.com.ar/ CTI]

== Belgium ==
* [http://www.proximus.be/ Proximus]
* [http://www.base.be/ Base]
* [http://www.mobistar.be/LanguageIndex.html Mobistar]

== Canada ==
* [http://www.fido.ca/ Fido]
* [http://www.icewireless.ca/ IceWireless]
* [http://www.rogers.ca/ Rogers]
* [http://www.yak.ca/ Yak Communications]

== China ==
* China Mobile
* China Unicom (CHINA UNICOM GSM)

== Czech Republic ==

* [http://www.vodafone.cz/ Vodafone]
* [http://www.cz.o2.com/ o2]
* [http://www.t-mobile.cz/ T-mobile]

== Denmark ==
* Sonofon ([http://www.sonofon.dk/english/index.shtml English] - [http://www.sonofon.dk/ Danish])
* TDC A/S ([http://tdc.com English] - [http://privat.tdc.dk/mobil/ Danish])
* Telia DK ([http://telia.dk/privat/produkter/mobil/ Danish])

== Estonia ==

* [http://www.emt.ee/ EMT]
* [http://www.tele2.ee/ Tele2] - Very low rates for GPRS. You can get 3GB of bandwidth for 675EEK(~43€) per month.
* [http://www.elisa.ee/ Elisa] - With M-internet plan you get free access to Elisa wifi hotspots

== Finland ==

* [http://www.cubio.fi Cubio]
* [http://www.dnafinland.fi Dna] - Also a roaming network operator (Network operated under the name Dna Networks Ltd)
* [http://www.elisa.fi Elisa] - Also a roaming network operator.
* [http://www.go.fi Go mobile]
* [http://www.hesburger.fi/heseliittyma/ Hesburger] - Do you want sim card(s) with that?
* [http://www.kolumbus.fi Kolumbus] - Strangely they don't offer their website in English, but they're a part of the Elisa.
* [http://www.teliasonera.com Teliasonera] - Also a roaming network operator.
* [http://www.tele.fi Telefinland] - They haven't got an English site, but they're part of the Teliasonera.
* [http://www.gsm.aland.fi/ Ålands Mobiltelefon] - Only in the Åland Islands in the southwestern Finland. Also a roaming network operator.

== France ==

All:
* [http://www.sfr.fr SFR]
* [http://www.bouyguestelecom.fr/ Bouygues]
* [http://www.orange.fr Orange]

== Germany ==
All:
* [http://www.vodafone.de/ Vodafone]
* [http://www.o2online.de/ o2]
* [http://www.eplus.de/ E-Plus]
* [http://www.t-mobile.de/ T-mobile]
== India ==
All GSM:
* [http://www.airtel.in/ Airtel]
* Vodafone
* [http://www.ideacellular.com/ Idea]
* Reliance GSM
* BPL Mobile
* Spice
* [http://www.bsnl.co.in/ BSNL]
* [http://www.hutch.in/ Hutch]

== Japan ==

According to the [http://www.gsmworld.com/roaming/gsminfo/cou_jp.shtml GSM-Association] there is no GSM in Japan, except for UMTS.

== Latvia ==
* [http://www.lmt.lv/ LMT]
* [http://www.bite.lv/ Bitė]
* [http://www.tele2.lv/ Tele2]

== Lithuania ==
* [http://www.omnitel.lt/ Omnitel]
* [http://www.bite.lt/ Bitė]
* [http://www.tele2.lt/ Tele2]

== Netherlands ==
All.
* [http://www.vodafone.nl/ Vodafone]
* [http://www.telfort.nl/ Telfort]
* [http://www.orange.nl/ Orange]
* [http://www.t-mobile.nl/ T-mobile]
* [http://www.kpn.com/mobiel KPN]
* [http://www.hi.nl/ Hi]
(There are more)

For a breakdown of SIM-only plans, go to [http://www.bellen.com/mobiel_overzicht/default.asp?taal=nl&land=nl&prgr=4 Bellen.com]

== New Zealand ==
* [http://www.vodafone.co.nz/ Vodafone]

== Norway ==
* [http://www.netcom.no/ NetCom] (GSM900/1800 & UMTS)
* [http://www.networknorway.no/ Network Norway] (GSM900)
* [http://www.telenormobil.no/ Telenor] (GSM900/1800 & UMTS)

== Poland ==

* [http://www.eragsm.pl/ Era]
* [http://www.plusgsm.pl/ Plus]
* [http://www.orange.pl/ Orange] - europe wide provider
* [http://www.playmobile.pl/ Play]

== Romania ==

* [http://www.vodafone.ro Vodafone] (226-01; GSM900)
* [http://www.orange.ro Orange] (226-10; GSM900)
* [http://www.cosmote.com Cosmote] (226-06; GSM1800)

* [http://www.zapp.ro/ Zapp] is running CDMA (Qualcomm style) and as such it is incompatible with [[Neo1973]].

== Russia ==
=== global ===
* [http://www.beeline.ru/ Билайн]/BeeLine (GSM900/1800)
* [http://megafon.ru/ МегаФон]/MegaFon (GSM900/1800)
* [http://www.mts.ru МТС]/MTS (GSM900/1800)
=== regional ===
* [http://www.smarts.ru/ СМАРТС]/SMARTS (GSM900/1800)
* [http://www.tele2.ru TELE2] (GSM900/1800)
* [http://www.u-tel.ru/ Ютел]/Utel (GSM900/1800)
* [http://www2.sibirtelecom.ru/857 Сибирьтелеком]/Sibirtelecom (GSM-900/1800)
* [http://www.ncc.nnov.ru/ НСС]/NSS (GSM900/1800)
* [http://www.bwc.ru/ Байкалвестком]/Baykalvestcom (GSM900/1800)

== Slovak Republic ==
All:
* [http://www.orange.sk/ Orange]
* [http://www.sk.o2.com/ o2]
* [http://www.t-mobile.sk/ T-mobile]

== South Africa ==

* [http://www.vodacom.co.za/ Vodacom]
* [http://www.mtn.co.za/ MTN]
* [http://www.cellc.co.za/ Cell C]

== Spain ==

* [http://www.vodafone.es/ Vodafone]
* [http://www.movistar.es/ Movistar]

== Sweden ==

Operators with their own physical networks:
* [http://comviq.se/ Comviq/Tele2]
* [http://www.telia.se/ Telia]
* [http://www.tre.se/ 3]
* [http://www.telenor.se Telenor]

Virtual Operators:
* [http://www.tangomini.se TangoMini]
* [http://www.halebop.se Halebop]
* [http://www.djuice.se Djuice]

== Switzerland ==
(all)
* [http://www.swisscom-mobile.ch/ Swisscom Mobile]
* [http://www.sunrise.ch/ Sunrise]
* [http://www.orange.ch/ Orange]

== Taiwan ==

* Chunghwa Telecom
* Far EasTone Telecommunications Co Ltd
* KG Telecom
* MobiTai
* Taiwan Mobile Co.Ltd

== Ukraine ==
* [http://www.umc.ua/ UMC] (including virtual [http://www.jeans.com.ua/ Jeans], [http://www.ekotel.com.ua/ Ecotel])
* [http://www.kyivstar.net/ Kyivstar] (including virtual [http://www.djuice.com.ua/ DJUICE], [http://mobilych.com.ua/ Mobilych])
* [http://www.life.com.ua/ life:)]
* [http://www.beeline.ua/ Beeline]
* [http://gsm.goldentele.com/ Golden Telecom]
* [http://www.privatmobile.com.ua/ PrivatMobile]

== United Kingdom ==
* [http://www.virginmobile.com/vm/home.do Virgin Mobile]
* [http://www.vodafone.co.uk/ Vodafone]
* [http://www.o2.co.uk/ O2]
* [http://www.orange.co.uk/ Orange]
* [http://www.t-mobile.co.uk/ T-mobile]
* [http://www.three.co.uk/ 3] ''There is a rumour that 3 use technology that blocks detect phones that are not capable of 3G from their 2G network. If this rumour is true, then 3 would not really be compatible with the GSM-only Neo1973

== United States ==

* [[Carriers/ATT|AT&T]] - (Was Cingular)
* [[Carriers/CellularOne|Cellular One/Dobson Cellular]] - Their Prepaid Cellular page says it works with any GSM phone. However according to Wikipedia [http://en.wikipedia.org/wiki/Dobson_Cellular] they are possibly being acquired by AT&T, so it's unknown whether they will stay GSM or not.
* [[Carriers/TMobile|T-Mobile]] - Works with Neo1973 using manual GSM commands w/prepaid SIM.
* Other (more local) GSM-network providers can be found at [http://www.gsmworld.com/roaming/gsminfo/cou_us.shtml GSMworld.com]
* [http://www.unicel.com/ UNICEL] - Has just been purchased by Verizon Wireless (Aug/1/07), they are planning on take down their GSM Network except to support roaming GSM customers. GSM customers will be transition to CDMA. :(
* Wikipedia has a list of providers and technologies [http://en.wikipedia.org/wiki/List_of_United_States_mobile_phone_companies here]. Only GSM networks are compatible with the Neo1973.
* [http://www.prepaidgsm.net/en/usa.html PrepaidGSM.net information about GSM prepaid cards in the USA]

== Uruguay ==

* [http://www.ancel.com.uy/ Ancel] -

== Venezuela ==

* [http://www.digitel.com.ve/ Digitel] - This works on the 900Mhz band.
* [http://www.movistar.com.ve/ Movistar] - Previously named Telcel. It is moving from CDMA to GSM, but currently all its new phones are GSM. They work on the 850 Mhz band.

== Rest of World (Africa, Asia, Australia, Europe, South America) ==

* almost all use GSM thus they are compatible

(More info available at: [http://www.gsmworld.com/roaming/gsminfo/index.shtml GSMworld.com])
{{Languages|Neo1973_compatible_cellphone_providers}}

[[Category:Information]]

Qtopia on Neo1973

2007-09-18T15:01:29Z

ScaredyCat: /* alsactl */

== Where to get it ==

You can get everything you need [http://www.qtopia.net/modules/devices/openmoko.php from here] download and use dfu-util as normal :D - Simple, Eh?

Most things seem to work out of the box, however you may need to use the following command to get audio:

# alsactl -f /etc/alsa/gsmhandset.state restore

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]]

[[Image:Qtopia002.png]]

[[Image:Qtopia003.png]]

[[Image:Qtopia004.png]]

[[Image:Qtopia005.png]]

[[Image:Qtopia006.png]]

== Videos ==

http://www.youtube.com/watch?v=YW5q8SpY7t4
http://www.youtube.com/watch?v=iOG_mtSEMgs

Qtopia on Neo1973

2007-09-18T14:28:14Z

ScaredyCat: /* Where to find the files */

== Where to get it ==

You can get everything you need [http://www.qtopia.net/modules/devices/openmoko.php from here] download and use dfu-util as normal :D - Simple, Eh?

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]]

[[Image:Qtopia002.png]]

[[Image:Qtopia003.png]]

[[Image:Qtopia004.png]]

[[Image:Qtopia005.png]]

[[Image:Qtopia006.png]]

== Videos ==

http://www.youtube.com/watch?v=YW5q8SpY7t4
http://www.youtube.com/watch?v=iOG_mtSEMgs

Qtopia on Neo1973

2007-09-18T10:13:37Z

ScaredyCat: /* Screenshots */

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]]

[[Image:Qtopia002.png]]

[[Image:Qtopia003.png]]

[[Image:Qtopia004.png]]

[[Image:Qtopia005.png]]

[[Image:Qtopia006.png]]

Qtopia on Neo1973

2007-09-18T10:09:16Z

ScaredyCat:

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]][[Image:Qtopia002.png]][[Image:Qtopia003.png]][[Image:Qtopia004.png]][[Image:Qtopia005.png]][[Image:Qtopia006.png]]

File:Qtopia006.png

2007-09-18T10:09:04Z

ScaredyCat:

File:Qtopia005.png

2007-09-18T10:08:37Z

ScaredyCat:

File:Qtopia004.png

2007-09-18T10:07:55Z

ScaredyCat:

Qtopia on Neo1973

2007-09-18T10:07:10Z

ScaredyCat:

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

[[Image:Qtopia001.png]][[Image:Qtopia002.png]][[Image:Qtopia003.png]]

File:Qtopia003.png

2007-09-18T10:06:47Z

ScaredyCat:

File:Qtopia002.png

2007-09-18T10:06:13Z

ScaredyCat:

File:Qtopia001.png

2007-09-18T10:04:05Z

ScaredyCat:

Qtopia on Neo1973

2007-09-18T10:03:22Z

ScaredyCat: /* qtopia on neo */

== Screenshots ==

Here are some screenshots of Qtopia runing on a Neo 1973. Personally I find it very impressive...

Customizing the Openmoko Distribution

2007-09-02T13:55:48Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp build/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

IMAGE_INSTALL += "task-openmoko-debug"

</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and beyond the standard image. This example includes '''[http://wiki.openmoko.org/wiki/Scummvm scummvm]''' and '''[http://www.handhelds.org/moin/moin.cgi/kbdd kbdd]'''. If you modify this file, make sure you update the '''PR''' by incrementing the number each time.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
kbdd \
"

</pre>

==== Actually building your image ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T21:41:30Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and beyond the standard image. This example includes '''[http://wiki.openmoko.org/wiki/Scummvm scummvm]''' and '''[http://www.handhelds.org/moin/moin.cgi/kbdd kbdd]'''. If you modify this file, make sure you update the '''PR''' by incrementing the number each time.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
kbdd \
"

</pre>

==== Actually building your image ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T21:34:09Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and beyond the standard image. This example includes '''[http://wiki.openmoko.org/wiki/Scummvm scummvm]'''. If you modify this file, make sure you update the '''PR''' by incrementing the number each time.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

==== Actually building your image ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T19:58:04Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image. This example includes '''scummvm'''. If you modify this file, make sure you update the '''PR''' by incrementing the number each time.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

==== Actually building your image ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T19:56:57Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image. This example includes '''scummvm'''. If you modify this file, make sure you update the '''PR''' by incrementing the number.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

==== Building it ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:47:20Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image. This example includes '''scummvm'''

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

==== Building it ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:46:15Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

==== Building it ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:43:40Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something yo identify your images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

==== Building it ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:40:45Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see ''scaredycat'' replace this with something yo identify your images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:39:50Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see 'scaredycat' replace this with something yo identify your images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:39:15Z

ScaredyCat: /* Creating your own images */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them so suit. Where you see 'scaredycat' replace this with something yo identify your images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

export PACKAGE_INSTALL += "\
task-openmoko-debug \
"
</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export PACKAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

DEPENDS = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko \
"

RDEPENDS = "${PACKAGE_INSTALL}"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and behond the standard image.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
"

</pre>

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:30:03Z

ScaredyCat: /* Setting Up a Local Overlay */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the local/conf/site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Customizing the Openmoko Distribution

2007-08-29T17:28:46Z

ScaredyCat: /* Setting Up a Local Overlay */

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages local/packages/images local/packages/tasks

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

USB Networking

2007-08-27T20:26:26Z

ScaredyCat: /* Proxying DNS requests */

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu feisty appears to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once
after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, adding a last line:
<pre>
SUBSYSTEM=="net", ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>
and remove the similar remove like earlier.

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

== Proxying DNS requests ==

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my Neo /etc/resolv.conf only contains

nameserver 192.168.0.200

and my laptop will proxy all dns requests based on it's own /etc/resolv.conf

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

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

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

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

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

Boot sound

2007-08-27T15:14:37Z

ScaredyCat: /* The Boot Sound */

= The Boot Sound =

Annoying isn't it. To stop the boot sound playing simply edit '''/etc/pulse/session'''. Look near the bottom of the file, you should see something like:

# Load samples
load-sample startup /usr/share/openmoko/sounds/startup_openmoko.wav
load-sample touchscreen /usr/share/openmoko/sounds/touchscreen_click.wav

To disable the boot sound and/or the touchscreen tap sound simply place a # at the start of the line, ie:

# Load samples
#load-sample startup /usr/share/openmoko/sounds/startup_openmoko.wav
#load-sample touchscreen /usr/share/openmoko/sounds/touchscreen_click.wav

If you want to change the sound, simply change the .wav file name to something else.

Boot sound

2007-08-27T15:13:46Z

ScaredyCat: /* How to remove annoying boot sound */

= The Boot Sound =

Annoying isn't it. To stop the boot sound playing simply edit '''/etc/pulse/session'''. Look neat the bottom of the file, you should see something like:

# Load samples
load-sample startup /usr/share/openmoko/sounds/startup_openmoko.wav
load-sample touchscreen /usr/share/openmoko/sounds/touchscreen_click.wav

To disable the boot sound and/or the touchscreen tap sound simply place a # at the start of the line, ie:

# Load samples
#load-sample startup /usr/share/openmoko/sounds/startup_openmoko.wav
#load-sample touchscreen /usr/share/openmoko/sounds/touchscreen_click.wav

If you want to change the sound, simply change the .wav file name to something else.

USB Networking

2007-08-27T11:50:33Z

ScaredyCat: /* Proxying DNS requests */

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu feisty appears to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once
after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, adding a last line:
<pre>
SUBSYSTEM=="net", ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>
and remove the similar remove like earlier.

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

== Proxying DNS requests ==

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my /etc/resolv.conf only contains

nameserver 192.168.0.200

and my laptop will proxy all dns requests based on it's own /etc/resolv.conf

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

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

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

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

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

USB Networking

2007-08-27T11:45:56Z

ScaredyCat: /* Proxying DNS requests */

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu feisty appears to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once
after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, adding a last line:
<pre>
SUBSYSTEM=="net", ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>
and remove the similar remove like earlier.

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

== Proxying DNS requests ==

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my resolv.conf only contains

nameserver 192.168.0.200

and my laptop will proxy all dns requests.

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

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

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

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

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

USB Networking

2007-08-27T11:40:59Z

ScaredyCat: /* Proxying DNS requests */

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu feisty appears to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once
after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, adding a last line:
<pre>
SUBSYSTEM=="net", ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>
and remove the similar remove like earlier.

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

== Proxying DNS requests ==

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my resolv.conf only contains

nameserver 192.168.0.200

and my laptop will proxy all dns requests.

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

The script is designed to use dnrd as the dns proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available from my site.

The script also performs the initial setup of the connection as per the sections above.

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

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

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

USB Networking

2007-08-27T11:38:43Z

ScaredyCat: /* Mobile development */

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu feisty appears to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once
after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, adding a last line:
<pre>
SUBSYSTEM=="net", ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>
and remove the similar remove like earlier.

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

== Proxying DNS requests ==

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my resolv.conf only contains

nameserver 192.168.0.200

and my laptop will proxy all dns requests.

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

The script is designed to use dnrd as the dns proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available from my site.

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

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

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

USB Networking

2007-08-27T11:36:49Z

ScaredyCat: /* how to proxy dns requests */

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

On the Neo, if you want to reach out to the internets using full qualified hostnames, you need to define your DNS server. Create a file /etc/resolv.conf with at least one line saying

nameserver xxx.xxx.xxx.xxx

e.g. nameserver 192.168.1.1

Then you can also easily update your 2007.2 OpenMoko packages with "ipkg update && ipkg upgrade" on the Neo.

= Desktop side =

== Manual method ==

With the device connected, modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

Took from [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] post by Marcin 'Hrw' Juszkiewicz.

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

If you are doing the echo 1 > /proc/... command manually, sudo may not be enough, then you will have to execute it from a sudo bash.

Ubuntu feisty appears to have a bug where ifdown is not run when the interface is unplugged, meaning this only works once
after the system is booted.
One can patch /etc/udev/rules.d/85-ifupdown.rules, adding a last line:
<pre>
SUBSYSTEM=="net", ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"
</pre>
and remove the similar remove like earlier.

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Mobile development =

If, like me, you move about quite a lot, connecting to various networks as you go and getting your ip via dhcp, you'll probably be annoyed at having to constantly update your resolv.conf on the Neo 1973.

To get round this, as part of my setup script, I run a proxy dns on the ip address the neo comes in on at the usb0 port. This means that my resolv.conf only contains

nameserver 192.168.0.200

and my laptop will proxy all dns requests.

'''note that we only run the dns proxy on the usb0 interface so that we don't break any other networking'''

The script is designed to use dnrd as the dns proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available from my site.

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

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

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===
====From host to phone====

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

====From phone to host====
Generate the key

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

This works for me. I ripped off these instructions from: [[http://forum.openwrt.org/viewtopic.php?pid=53705]]

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]