Openmoko - User contributions [en]

Server:WebProxy

2009-07-21T13:31:34Z

Speedevil: /* Related software */

{{wishlist}}

* This is an outline of a proxy to reduces data transfer - for use on devices with a reasonable amount of persistant storage, and very limited bandwidth.
** Some aspects could later be included in browsers or webservers.

Once, each page linked to a subpage of contents, which remained static, and could be easily refreshed if it changed based on dates in the HTTP headers.

Now, this is the case in the minority of popular sites.

Most sites now have a substantial fraction of pages with some non-static contents.

As an example of this, for example consider http://www.ebay.com/index.html.

Over a 15 minute period, the size was constant at around 66K, and it was different most times it was loaded.

Simply compressing this page using advanced compression techniques provides a useful compression - taking the page to 15K.

(Zipproxy, is an example of software implementing this type of compression.)

A very simple test, using diff and gzip however, revealed that the variation between pages is quite small.

This means that if the user clicks 'reload', if the proxy simply compresses the page, the user needs to download 15K.

If, however, the user-agent and the proxy act in concert, this can be reduced to under 0.5K. (split on "<", count the compressed differences).

This is done by the user-agent caching the pages it downloads, then informing the proxy of which version of the page it has.

The proxy then simply sends the compressed differences between the previous and current version.

Other optimisations.

* Comparing pages, and ensuring that any page has in fact changed before downloading, as many servers misreport pages changed when they have not.

* Convert all jpegs to progressive, and initially only download the first 'scan' of the image, which is 1/8th the size or so. Allow the user to download the remainder of the file for full resolution by clicking on it.

* If the proxy knows the exact state of the clients cache - for example if it's the only proxy the client uses - it does not need to negotiate it with the client, it can simply send only the compressed differences.

* If the user visits a new page on a site - the proxy can compare the hashes of parts of the newly downloaded page, with others the client has cached, and instead of sending the whole file, send only the (compressed) differences.

** For example - ebay - auction pages share a large amount of common text - all the in-page javascript, footers, headers, and navigation bar.

* The proxy can automatically download and include required elements if the user wishes them - for example automatically including images and javascript, without another round-trip to the server.

* Converting images to lower resolution forms. For example - convert all jpegs to progressive jpeg, and serve up only the first 1/8th of a file.

==Related software==
* rproxy - rsync for wepbages. Failed due potential patent problems. http://ozlabs.org/~rusty/rproxy.html

* Zipproxy - http://ziproxy.sourceforgehttp://ziproxy.sourceforge.net/.net/ is a related application, but does not implement the core of this proposal, which is compressing webpages based on the known contents of the users cache.

=Q&A=

* How does this differ from rproxy? (http://ozlabs.org/~rusty/rproxy.html)
** It differs primarily in that it does not require webservers to support anything. Only that a user desiring to run it has somewhere to put their personal proxy.
** It also differs in that it has perfect knowledge of the state of the cache on the mobile device.
** It differs significantly from rsync/rproxy, as the core of those programs - negotiating file differences over a remote link - is not done.
** it does not require any negotiation over the (potentially very slow) link, and also enables the proxy to potentially send other changed pages that are referred in the changes.

Server:WebProxy

2009-07-21T13:28:57Z

Speedevil: rework

{{wishlist}}

* This is an outline of a proxy to reduces data transfer - for use on devices with a reasonable amount of persistant storage, and very limited bandwidth.
** Some aspects could later be included in browsers or webservers.

Once, each page linked to a subpage of contents, which remained static, and could be easily refreshed if it changed based on dates in the HTTP headers.

Now, this is the case in the minority of popular sites.

Most sites now have a substantial fraction of pages with some non-static contents.

As an example of this, for example consider http://www.ebay.com/index.html.

Over a 15 minute period, the size was constant at around 66K, and it was different most times it was loaded.

Simply compressing this page using advanced compression techniques provides a useful compression - taking the page to 15K.

(Zipproxy, is an example of software implementing this type of compression.)

A very simple test, using diff and gzip however, revealed that the variation between pages is quite small.

This means that if the user clicks 'reload', if the proxy simply compresses the page, the user needs to download 15K.

If, however, the user-agent and the proxy act in concert, this can be reduced to under 0.5K. (split on "<", count the compressed differences).

This is done by the user-agent caching the pages it downloads, then informing the proxy of which version of the page it has.

The proxy then simply sends the compressed differences between the previous and current version.

Other optimisations.

* Comparing pages, and ensuring that any page has in fact changed before downloading, as many servers misreport pages changed when they have not.

* Convert all jpegs to progressive, and initially only download the first 'scan' of the image, which is 1/8th the size or so. Allow the user to download the remainder of the file for full resolution by clicking on it.

* If the proxy knows the exact state of the clients cache - for example if it's the only proxy the client uses - it does not need to negotiate it with the client, it can simply send only the compressed differences.

* If the user visits a new page on a site - the proxy can compare the hashes of parts of the newly downloaded page, with others the client has cached, and instead of sending the whole file, send only the (compressed) differences.

** For example - ebay - auction pages share a large amount of common text - all the in-page javascript, footers, headers, and navigation bar.

* The proxy can automatically download and include required elements if the user wishes them - for example automatically including images and javascript, without another round-trip to the server.

* Converting images to lower resolution forms. For example - convert all jpegs to progressive jpeg, and serve up only the first 1/8th of a file.

==Related software==
* rproxy - rsync for wepbages. Failed due to lack of uptake. http://ozlabs.org/~rusty/rproxy.html

* Zipproxy - http://ziproxy.sourceforgehttp://ziproxy.sourceforge.net/.net/ is a related application, but does not implement the core of this proposal, which is compressing webpages based on the known contents of the users cache.

=Q&A=

* How does this differ from rproxy? (http://ozlabs.org/~rusty/rproxy.html)
** It differs primarily in that it does not require webservers to support anything. Only that a user desiring to run it has somewhere to put their personal proxy.
** It also differs in that it has perfect knowledge of the state of the cache on the mobile device.
** It differs significantly from rsync/rproxy, as the core of those programs - negotiating file differences over a remote link - is not done.
** it does not require any negotiation over the (potentially very slow) link, and also enables the proxy to potentially send other changed pages that are referred in the changes.

Wishlist/Unlikely

2008-12-20T02:30:50Z

Speedevil: /* V12 Embedded power source */

These are ideas that are unlikely to be implemented in the neo1973. Some are impossible for any device,
some may be possible if technology improves in the future, when patents expire, or in othere models.

== Storage Devices / Peripherals ==
=== Floppy Disk Drive ===
For people stuck in the past who just can't let go of that last 3 and a half inches.

At least the initial devices will be phones. In a phone this is a bad idea.
There may be future devices that it would be appropriate in.

===LASER keyboard (can be a full QWERTY keyboard)===
*On the hardware side, this would require a $5 laser diode, a $3 (in bulk) custom diffraction grating, and probably a couple of cubic centimetres volume inside the phone.
*This requires a camera pointable to the front.
*It requires an integrated stand for the phone.
*To practically use this, you've got to be 40cm or so away from the phone, which means under 25*20 of text resolution.
*In software, it's relatively easy to parse the camera output, to find changes in the known laser field.

There are major problems.
*Patent issues.
*No tactile response at all, which slows typing.
*An extra 2cc/6g.

There are existing Bluetooth devices that do this. [http://www.thinkgeek.com/computing/input/8193/ For example, this one from thinkgeek]. --[[User:Alx|Alx]] 02:28, 29 March 2007 (CEST)

==Power Sources==

===Zero Point Energy Generator===
Why bother with solar panels and fuel cells if you can have the real thing?

===Air Breathing Micro Fusion Generator===
In case the above is not available in small enough sizes

===Radioisotope Battery===
We could have the first mobile with a 100 year standby endurance. Can the shielding, We can all use a little tan.

===V12 Embedded power source===

We'll need something beefy to power the next Neos for the above gadgets, I propose the use of a [http://www.ultimatestupidity.com/pics/1/diesel/ Embeddable Power Source], that with some miniturisation and a bit of design work should be workable as a possible solution.

[http://uk.youtube.com/watch?v=mutb7KgA9NM] Is almost an appropriate device.

=== Flux Capacitor ===
The device needs a [http://en.wikipedia.org/wiki/Flux_capacitor flux capacitor] instead of a battery ;)

=== Power over WiFi ===
Using PoWiFi openmoko-devices could be powered by your pc-wifi-card or wifi-router.
Charge your mobile at every wlan-ap with no plug-in required.

Another implementation might be power-over-bluetooth.

=== Human body's kinetic power ===
With any of [http://wiki.laptop.org/go/Freecharge_portable_charger these devices], especially those [http://wiki.laptop.org/go/Freecharge_portable_charger#Balancing_Musculoskeletal_System using human energy], happy Openmoko user will at once become noticeably more mobile. Unlimited travel far avay from casual power sources, this is what it gives.

== Miscellaneous ==
=== Disinfection UV-Light ===
I had read about it in an Article on http://www.americanairandwater.com/UV-news/. But Motorola patents it.
Yes - finally a way to stop the billions of annual deaths due to cellphone infections! --[[User:Speedevil|Speedevil]] 14:04, 16 February 2007 (CET)
It´s just something that flying in my head... It´s not the first "unreal" or "useless" idea. Just for fun! --[[User:MookiE|MookiE]] 14:51, 16 February 2007 (CET)

More seriously - UV of the required frequency is inherently eye-damaging.
Also, as I understand it, there are actually no UV LEDs that will reliably produce 'germicidal' UV.
The most expensive - and they are very expensive - ones produce UV of a sort that may kill very susceptible bacteria, but comparatively few.
IIRC the LEDs are $20 per.
--[[User:Speedevil|Speedevil]] 15:11, 16 February 2007 (CET)

The most efficient germicidal wavelength is at around 260 nm. LEDs at these wavelengths are already available for purchasing, e.g. here: http://www.s-et.com/products.htm - however the cost at this moment is rather high (above $200 per piece; much less in large amounts). The output power is also quite low. However this is likely to improve with time.
--[[User:Shaddack|Shaddack]] 00:54, 16 July 2007 (CEST)

===FPGA add-on board===
Expose the system bus signals to allow easy-ish addition of a daughter board with an FPGA chip. This will allow to leverage a set of projects available at e.g. http://www.opencores.org/ and easily add a wide range of functionality, from high-speed memory-mapped analog inputs (e.g. GNU-Radio, camera (possibly with a hardware MPEG encoder in the FPGA), portable oscilloscope or logic analyzer or multichannel data acquisition unit), to outputs (eg. display drivers for e-paper, framebuffers for TV-out or external monitors - important for e.g. wearable augmented-reality displays), Ethernet controller, mini-PCI card controller, advanced signal processing, cryptographic accelerators, and essentially anything within the limits of the available number of gates in the FPGA chip and available amount of electricity to feed the chip.

This is very unlikely - for several reasons.
*Requires a '''large''', relatively expensive connector, able to pass signals at very high speeds.
*Requires routing from the core logic of the phone to the connector, which makes the PCB more complicated to fabricate.
*There is no convenient memory bus on the phone.
--[[User:Speedevil|Speedevil]] 13:58, 15 July 2007 (CEST)

It is not impossible on very different hardware, but will certainly not appear on a commodity phone.

Let's consider another way then. What we want here is not necessarily a direct access to the system bus (not seeing the schematics I mistakenly assumed it would be the simplest way) but any kind of high-speed I/O. E.g. MMC card interface in 8 bit mode at 52 MHz seems to be able to achieve data transfer rate of 52 MB/s, CompactFlash maximum data transfer rate can reportedly go up to 133 MB/s (if I read the standards correctly) - more than enough for most applications listed above. Possible?
--[[User:Shaddack|Shaddack]] 00:54, 16 July 2007 (CEST)

=== Teleportation ===
Implementing a beaming-device to the Neo would make it the first phone enabling teleportation.
See: [http://news.bbc.co.uk/1/hi/sci/tech/3811785.stm]
Possible implementation difficulties might be the lacking teleportation-support in the GSM standard as well as uncooperative mobile service providers that feel uneasy towards innovative technologies...
''

(Please get serious. You would obviously need more bandwidth to make this practical. Wifi would be better or at least 3G. maybe you could use Bluetooth with the right compression algorithms.)''

(Are you serious? Bluetooth? Please, there's no way that will work. We need at least WiMax or even better, that upcoming Wireless USB standard. l2teleport, please.)

(Also cant say i would be too keen about once i am teleported far away my phone is left sitting on the sidewalk.)

=== All band compatibility ===

*Is it possible to make the phone so it can work on any cell network including the Veriz** network in the USA. Unfortunately, the FCC has allowed network providers to have proprietary phones etc... The way the US system works tends to cheapen the phone itself because there is more money in the selling of service, this tends to foster semi-disposable phones. Don't lose focus, you are in business to make money selling phones, make really good solid phones and they will be appreciated. My ideal is to be able to go purchase a phone, purchase a service separately, and be able to change services when necessary.

** Unfortunately, this would add significant cost, volume, and weight. And be useless for the majority of worldwide users. In some carriers cases, you simply can't do this anyway, as they won't supply information on their networks, or let you connect to them with your own handset. Different phones for different markets is probably the way to go. Hopefully eventually the carriers will bring out Openmoko phones.
--[[User:Speedevil|Speedevil]] 15:45, 6 May 2007 (CEST)

===SDR Radio===
* Advantages
** Removes the need for ANY other wireless radio in the device
*** GSM Radio
*** Wifi Radio
*** Bluetooth Radio
*** RFID Radio (may still need a microwave power pump)
*** FRS Radio
*** DECT Radio
*** Etc...
** Reduce battery consumption by an enormous amount
** Allows connection to new types of networks with only a software upgrade
* Disadvantages
** Experimental?
** Only one type of wireless network would be accessible at any given time
*** Solution: Include 2 SDR radios (this would alleviate radio contention)
** All protocols would need to be coded in software
*** Solution: Upgrade primary cpu if necessary (additional power costs for a faster cpu are far outweighed by reduction of radios)

<hr>
Unfortunately, much of this is incorrect.
A wideband software radio eats _enormous_ amounts of power in very fast A/Ds and D/As, as well as fast CPUs.
It's also much more expensive in many cases, due to the large amount of CPU power needed, and the expensive chips and wideband RF devices needed.
It trades flexibility for hardware signal processing.

One little filter chip can do billions of operations per second, entirely due to the physics.

Also - there is no open-source GSM stack, and this would in fact be illegal to sell in many countries.
--[[User:Speedevil|Speedevil]] 20:43, 9 July 2007 (CEST)

== Beverage Aids ==

===Beer Cooling===

Either Rod's filled with liquid nitrogen pop out the bottom or heatpipes attached to a peltier device. for those hot days when your cold one is just a one.

==Hardware enhancements==

Some small hardware enhancement could be cheap, but very useful. Please add your ideas/wishes here:
 

'''Made Hardware Extension/Expansion for the Base Product''' 
Market this device like a fully customizable PC; 
- create a base device, (which you already did) 
- add wifi and bluetooth(absolutely neccesary for any mobile device) 
- make expansion hardware, that user can connect to the base hardware, (e.g camera & hdd; gamepad...etc) 
- just like a PC the user will choose customizations that sue their needs. 
- most important, the expansion hardware should NOT be a peripheral that has ridiculously long cables, it should fit snuggly to the device making it a little thicker than the base device. 
- This mobile entertainment generation wants an all-in-one device. They want their cellphone, mp3 player, pda, digital camera(which takes good quality and sized pictures), video player to all fit in their pocket. 
- That's why the ipod's hot, but that is why this is hotter, the user can get all those things and upload software to make it better it even better to their personalities. 

If the hardware is made as customizable as the software, everyone will have one of these device, from the smallest child to a CEO of a corporation, because it can be made exactly to what the user wants. Market the expansion hardware, no-one will mind paying for the parts as they need them, but they will be very upset about not being able to do want they really want to do with it. No one will even think about looking at other devices. If the "regular joe/jill" has to buy a new part instead of a whole new device, which do you think he/she will choose?

- Modular, able to open and upgrade/add hardware while keeping a micro form factor.
----

The neo1973 is a phone, to be marketed as a phone. Future devices may be marketed in other ways. The shape and number of buttons is fixed for this device. Minor modifications may happen before it ships in September.

See [[Expansion Back]] for expansion thoughts. Extendable devices otherwise simply aren't really possible, unless you make the phone larger than needed.

The connectors take up volume, add unreliability, need mechanical fixings, and modules have to be larger than required to allow slight increases in size. --[[User:Speedevil|Speedevil]] 14:47, 17 April 2007 (CEST)

[[Category:Hardware ideas|Unlikely]]

Server:WebProxy

2008-08-11T18:58:20Z

Speedevil: /* Q&A */

{{wishlist}}
This is a brief page describing a web proxy optimised for use on devices with a reasonable amount of persistant storage, and very limited bandwidth.

Once, each page linked to a subpage of contents, which remained static, and could be easily refreshed if it changed based on dates in the HTTP headers.

Now, this is the case in the minority of popular sites.
Most sites now have a substantial fraction of pages with some non-static contents.

As an example of this, for example consider http://www.ebay.com/index.html.

Over a 15 minute period, the size was constant at around 66K, and it was different most times it was loaded.

Simply compressing this page using advanced compression techniques provides a useful compression - taking the page to 15K.

A very simple test, using diff and gzip however, revealed that the variation between pages is quite small.

This means that if the user clicks 'reload', if the proxy simply compresses the page, the user needs to download 15K.

If, however, the user-agent and the proxy act in concert, this can be reduced to under 0.5K. (split on "<", count the compressed differences).

This is done by the user-agent caching the pages it downloads, then informing the proxy of which version of the page it has.

The proxy then simply sends the compressed differences between the previous and current version.

=Q&A=
* Would be better NOT to modify the client, but instead have a 'reassembly proxy' on the client, so that all http clients/user agents benefit without hacks.
** This is a simple option initially.

* How does this differ from rproxy? (http://ozlabs.org/~rusty/rproxy.html)
** It differs primarily in that it does not require webservers to support anything. Only that a user desiring to run it has somewhere to put their personal proxy.
** It also differs in that it has perfect knowledge of the state of the cache on the mobile device.
** It differs significantly from rsync/rproxy, as the core of those programs - negotiating file differences over a remote link - is not done.
** it does not require any negotiation over the (potentially very slow) link, and also enables the proxy to potentially send other changed pages that are referred in the changes.

Other optimisations:
* Comparing pages, and ensuring that any page has in fact changed before downloading, as many servers misreport pages changed when they have not.
* Convert all jpegs to progressive, and initially only download the first 'scan' of the image, which is 1/8th the size or so. Allow the user to download the remainder of the file for full resolution by clicking on it.
* Probably 'Ziproxy' (http://ziproxy.sourceforge.net/) could be extended to provide this functionality.

Extended usage scenarios:
* Different profiles, depending on how the Freerunner is connected (Wifi vs. USB vs. GPRS).
* Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) or in areas with limited data-consumption, like on commercial wifi-aps on airports and such.

[[Category:Server]]

User talk:Borgcube

2008-08-11T18:55:17Z

Speedevil: New page: rewrapped your comments about rproxy on Server:WebProxy into a Q&A section - do the answers seem logical? --~~~~

rewrapped your comments about rproxy on [[Server:WebProxy]] into a Q&A section - do the answers seem logical?
--[[User:Speedevil|Speedevil]] 18:55, 11 August 2008 (UTC)

Server:WebProxy

2008-08-11T18:53:52Z

Speedevil: add Q&A section

{{wishlist}}
This is a brief page describing a web proxy optimised for use on devices with a reasonable amount of persistant storage, and very limited bandwidth.

Once, each page linked to a subpage of contents, which remained static, and could be easily refreshed if it changed based on dates in the HTTP headers.

Now, this is the case in the minority of popular sites.
Most sites now have a substantial fraction of pages with some non-static contents.

As an example of this, for example consider http://www.ebay.com/index.html.

Over a 15 minute period, the size was constant at around 66K, and it was different most times it was loaded.

Simply compressing this page using advanced compression techniques provides a useful compression - taking the page to 15K.

A very simple test, using diff and gzip however, revealed that the variation between pages is quite small.

This means that if the user clicks 'reload', if the proxy simply compresses the page, the user needs to download 15K.

If, however, the user-agent and the proxy act in concert, this can be reduced to under 0.5K. (split on "<", count the compressed differences).

This is done by the user-agent caching the pages it downloads, then informing the proxy of which version of the page it has.

The proxy then simply sends the compressed differences between the previous and current version.

=Q&A=
* Would be better NOT to modify the client, but instead have a 'reassembly proxy' on the client, so that all http clients/user agents benefit without hacks.
** This is a simple option initially.

* How does this differ from rproxy? (http://ozlabs.org/~rusty/rproxy.html)
** It differs primarily in that it does not require webservers to support anything. Only that a user desiring to run it has somewhere to put their personal proxy.
** It also differs in that it has perfect knowledge of the state of the cache on the mobile device.
** It differs significantly from rsync/rproxy, as the core of those programs - negotiating file differences over a remote link - is not done.
** it does not require any negotiation over the (potentially very slow) link.

Other optimisations:
* Comparing pages, and ensuring that any page has in fact changed before downloading, as many servers misreport pages changed when they have not.
* Convert all jpegs to progressive, and initially only download the first 'scan' of the image, which is 1/8th the size or so. Allow the user to download the remainder of the file for full resolution by clicking on it.
* Probably 'Ziproxy' (http://ziproxy.sourceforge.net/) could be extended to provide this functionality.

Extended usage scenarios:
* Different profiles, depending on how the Freerunner is connected (Wifi vs. USB vs. GPRS).
* Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) or in areas with limited data-consumption, like on commercial wifi-aps on airports and such.

[[Category:Server]]

MokoForesight

2008-08-11T17:47:18Z

Speedevil: /* Chip Scouting */ typo

=Purpose=
MokoForesight is an independent hardware lab inside Openmoko to scout, analyze, and write proof-of-concept drivers for new open source chips/modules. It will accept tasks from Openmoko product teams or from the community, and maintain its own priorities.

[[Image:MokoForesight_1.jpg|500px|center]]

=People=
* Matt Hsu (Software)
* Shawn Lin (Hardware)

=Gear=
* R&S CMU 200 x 3
* R&S Audio Analyzer
* R&S Vector Signal Generator SMU200A
* R&S FSP Spectrum Analyzer
* Tektronix TDS 7254 Digital Phosphor Oscilloscope
* Anechoic Test Chamber
* Agilent E5071B Network Analyzer
* Agilent E4440A Spectrum Analyzer
* HP 16702A Logic Analysis System

=Current Tasks=

* U-boot porting to GTA03EVB (Matt) '''ONGOING'''
* SIMCOM 3G MODEM Research (Shawn) '''ONGOING'''
*
* GTA03EVB Hardware Verification (Matt & Shawn) '''NOT STARTED'''
** Starts when GTA03EVB is in office (AUG.11.2008)
** voltage, power consumption, RF characteristics (finished by end of AUG.22.2008)
*** Siemens MC 75i EDGE MODEM
*** u-blox 5 Antaris GPS
*** CSR BT
*** Accton/Atheros AR6001 Wi-Fi module
*
* Implement touchpanel driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* Implement LCD driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* GPS: Ublox5 & AGPS (On-line and Off-line Mode) (Shawn & Matt) '''NOT STARTED'''
* Implement Camera driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* Hardware Verification of BT module with new firmware (Matt & Shawn) '''NOT STARTED'''
* Marvell8686 WiFi module (Matt & Shawn) '''NOT STARTED'''

=Chip Scouting=

{|border=1 cellspacing=0
! Chip/Module !!Freedom Requirements !! Bussiness Requirements !! Technical Requirements !! Specs
|-
||SIMCOM5210V || All docs not open, even AT commands. Requested answer from SIMCOMM Aug 8. || Teenie says it's OK. || Good (Shawn Aug.7.2008)||NA
|-
| WiFi and BT Combo Module (AR6002+BC6) ||Not Checked || Not Checked || Good (Shawn Aug.7.2008)||NA
|-
| Wavecom WMP100 || AT docs open, ability to program new AT commands for everyone with a "free"(ly available) SDK. || Order quantity? || Component is fine, but only supports Class10 GPRS unfortunately|| No idea, see [http://www.wavecom.com/modules/movie/scenes/products/index.php?fuseAction=wirelessCPU&productName=WMP100 wavecom.com] ([http://www.wavecom.com/modules/movie/scenes/products/index.php?fuseAction=downloads&productName=WMP100 sort of])
|-
| NA ||NA || NA || NA || NA
|-
|}

=Publications=
* [http://downloads.openmoko.org/foresight/Publications/Digging_HTC_Touch.pdf Digging HTC Touch ]
* [http://downloads.openmoko.org/foresight/Publications/iPhone_3G_Disassembly.pdf iPhone 3G Disassembly ]
** See also [http://www.eetimes.com/showArticle.jhtml;jsessionid=3EVLVGY31FQQCQSNDLOSKH0CJUNN2JVN?articleID=209000014 this teardown] which was published in EEtimes (not in-house)
* [http://downloads.openmoko.org/foresight/Publications/Reveal_ETEN_Glofiish_X650.pdf Reveal ETEN Glofiish X650 ]
* [http://downloads.openmoko.org/foresight/Publications/Reveal_Gsmart_MS800.pdf Reveal Gsmart MS800 ]

[[Category:Openmoko]]

MokoForesight

2008-08-11T13:48:40Z

Speedevil: /* Publications */ caveat

=Purpose=
MokoForesight is an independent hardware lab inside Openmoko to scout, analyze, and write proof-of-concept drivers for new open source chips/modules. It will accept tasks from Openmoko product teams or from the community, and maintain its own priorities.

[[Image:MokoForesight_1.jpg|500px|center]]

=People=
* Matt Hsu (Software)
* Shawn Lin (Hardware)

=Gear=
* R&S CMU 200 x 3
* R&S Audio Analyzer
* R&S Vector Signal Generator SMU200A
* R&S FSP Spectrum Analyzer
* Tektronix TDS 7254 Digital Phosphor Oscilloscope
* Anechoic Test Chamber
* Agilent E5071B Network Analyzer
* Agilent E4440A Spectrum Analyzer
* HP 16702A Logic Analysis System

=Current Tasks=

* U-boot porting to GTA03EVB (Matt) '''ONGOING'''
* SIMCOM 3G MODEM Research (Shawn) '''ONGOING'''
*
* GTA03EVB Hardware Verification (Matt & Shawn) '''NOT STARTED'''
** Starts when GTA03EVB is in office (AUG.11.2008)
** voltage, power consumption, RF characteristics (finished by end of AUG.22.2008)
*** Siemens MC 75i EDGE MODEM
*** u-blox 5 Antaris GPS
*** CSR BT
*** Accton/Atheros AR6001 Wi-Fi module
*
* Implement touchpanel driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* Implement LCD driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* GPS: Ublox5 & AGPS (On-line and Off-line Mode) (Shawn & Matt) '''NOT STARTED'''
* Implement Camera driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* Hardware Verification of BT module with new firmware (Matt & Shawn) '''NOT STARTED'''
* Marvell8686 WiFi module (Matt & Shawn) '''NOT STARTED'''

=Chip Scouting=

{|border=1 cellspacing=0
! Chip/Module !!Freedom Requirements !! Bussiness Requirements !! Technical Requirements !! Specs
|-
||SIMCOM5210V || All docs not open, even AT commands. Requested answer from SIMCOMM Aug 8. || Teenie says it's OK. || Good (Shawn Aug.7.2008)||NA
|-
| WiFi and BT Combo Module (AR6002+BC6) ||Not Checked || Not Checked || Good (Shawn Aug.7.2008)||NA
|-
| Wavecom WMP100 || AT docs open, ability to program new AT commands for everywone with a "free"(ly available) SDK. || Order quantity? || package size too big? ~25x25x3mm BGA module, needs an additional 8x10mm flash/sram EDGE? 3G?|| No idea, see [http://www.wavecom.com/modules/movie/scenes/products/index.php?fuseAction=wirelessCPU&productName=WMP100 wavecom.com] ([http://www.wavecom.com/modules/movie/scenes/products/index.php?fuseAction=downloads&productName=WMP100 sort of])
|-
| NA ||NA || NA || NA || NA
|-
|}

=Publications=
* [http://downloads.openmoko.org/foresight/Publications/Digging_HTC_Touch.pdf Digging HTC Touch ]
* [http://downloads.openmoko.org/foresight/Publications/iPhone_3G_Disassembly.pdf iPhone 3G Disassembly ]
** See also [http://www.eetimes.com/showArticle.jhtml;jsessionid=3EVLVGY31FQQCQSNDLOSKH0CJUNN2JVN?articleID=209000014 this teardown] which was published in EEtimes (not in-house)
* [http://downloads.openmoko.org/foresight/Publications/Reveal_ETEN_Glofiish_X650.pdf Reveal ETEN Glofiish X650 ]
* [http://downloads.openmoko.org/foresight/Publications/Reveal_Gsmart_MS800.pdf Reveal Gsmart MS800 ]

[[Category:Openmoko]]

MokoForesight

2008-08-11T12:55:28Z

Speedevil: /* Publications */ add link to eetimes

=Purpose=
MokoForesight is an independent hardware lab inside Openmoko to scout, analyze, and write proof-of-concept drivers for new open source chips/modules. It will accept tasks from Openmoko product teams or from the community, and maintain its own priorities.

[[Image:MokoForesight_1.jpg|500px|center]]

=People=
* Matt Hsu (Software)
* Shawn Lin (Hardware)

=Gear=
* R&S CMU 200 x 3
* R&S Audio Analyzer
* R&S Vector Signal Generator SMU200A
* R&S FSP Spectrum Analyzer
* Tektronix TDS 7254 Digital Phosphor Oscilloscope
* Anechoic Test Chamber
* Agilent E5071B Network Analyzer
* Agilent E4440A Spectrum Analyzer
* HP 16702A Logic Analysis System

=Current Tasks=

* U-boot porting to GTA03EVB (Matt) '''ONGOING'''
* SIMCOM 3G MODEM Research (Shawn) '''ONGOING'''
*
* GTA03EVB Hardware Verification (Matt & Shawn) '''NOT STARTED'''
** Starts when GTA03EVB is in office (AUG.11.2008)
** voltage, power consumption, RF characteristics (finished by end of AUG.22.2008)
*** Siemens MC 75i EDGE MODEM
*** u-blox 5 Antaris GPS
*** CSR BT
*** Accton/Atheros AR6001 Wi-Fi module
*
* Implement touchpanel driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* Implement LCD driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* GPS: Ublox5 & AGPS (On-line and Off-line Mode) (Shawn & Matt) '''NOT STARTED'''
* Implement Camera driver for [[GTA|GTA03]] (Matt) '''NOT STARTED'''
* Hardware Verification of BT module with new firmware (Matt & Shawn) '''NOT STARTED'''
* Marvell8686 WiFi module (Matt & Shawn) '''NOT STARTED'''

=Chip Scouting=

{|border=1 cellspacing=0
! Chip/Module !!Freedom Requirements !! Bussiness Requirements !! Technical Requirements !! Specs
|-
||SIMCOM5210V || All docs not open, even AT commands. Requested answer from SIMCOMM Aug 8. || Teenie says it's OK. || Good (Shawn Aug.7.2008)||NA
|-
| WiFi and BT Combo Module (AR6002+BC6) ||Not Checked || Not Checked || Good (Shawn Aug.7.2008)||NA
|-
| NA ||NA || NA || NA || NA
|-
|}

=Publications=
* [http://downloads.openmoko.org/foresight/Publications/Digging_HTC_Touch.pdf Digging HTC Touch ]
* [http://downloads.openmoko.org/foresight/Publications/iPhone_3G_Disassembly.pdf iPhone 3G Disassembly ]
** See also [http://www.eetimes.com/showArticle.jhtml;jsessionid=3EVLVGY31FQQCQSNDLOSKH0CJUNN2JVN?articleID=209000014 this teardown] which was published in EEtimes]
* [http://downloads.openmoko.org/foresight/Publications/Reveal_ETEN_Glofiish_X650.pdf Reveal ETEN Glofiish X650 ]
* [http://downloads.openmoko.org/foresight/Publications/Reveal_Gsmart_MS800.pdf Reveal Gsmart MS800 ]

[[Category:Openmoko]]

Nand erase

2008-07-22T19:46:11Z

Speedevil: add caveat

To make a NAND erase, you need to connect to your device while in uboot using minicom or cu. The device will usually be called /dev/ttyACM0. You might need to

sudo chown uucp.uucp /dev/ttyACM0

to get the necessary right (even as root). Using cu, you can then access the Neo:

cu -l /dev/ttyACM0

After connecting, you should get a prompt where you can tell u-boot to clean certain parts of the NAND memory.

{{warning|Before you hit enter on one of the following commands, make sure that you are *not* issuing a plain "nand erase" command - always make sure you tell it which partition to erase. If you forget this you'll brick the Neo1973 and you'll need a debug board to recover it. For Freerunner, you can recover using the NOR flash.}}

nand erase rootfs
nand erase kernel

To exit cu you need to type:

~.
[[Category:Technical]]
[[Category:Software (non openmoko)]]
[[Category:Documentation]]

GPS Problems

2008-07-21T02:36:51Z

Speedevil: /* Solutions */ link shops

See [[GPS]] for details on how to evaluate the Freerunner GPS with command line utilities.

=== Problem: it takes a long time (10min+) before the Freerunner gets first GPS data ===

It was found that the OpenMoko FreeRunner GPS has a long Time To First Fix (TTFF) with the SD card in the phone. [http://lists.openmoko.org/pipermail/community/2008-July/021774.html This thread] indicates that there is interference from the SD card slot, as without the SD card inserted it the TTFF are much shorter.

::More specific: the GPS signal level drops by -20dBm, i.e. factor 100. Signal strength of a GPS satellite above your head is around -127dBm. Needed strength for a first fix is -145dBm with a minimum of three satellites. Once the GPS chip has a fix, it can operate at signal levels of -157dBm, thus making it possible to operate while there is data transfer from/to the SD card.
::''(From http://lists.openmoko.org/pipermail/community/2008-July/022202.html )''

=== Solutions ===

The people of OpenMoko know about the problem and are working on it. A [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003777.html software workaround] is under testing. It turns off the SD card clock when the SD card is not being used. One will be able to use the SD card at the same time as the GPS except for the first approximately 30 seconds.

Users report that the GPS works when there is no SD card in the Neo. But this is not a practical option, inserting/removing the card requires non-trivial manipulations.

OpenMoko is also examining a hardware solution: [http://www.openmoko.org/wiki/Image:Gta02_gps_10pf_rework_sop.pdf soldering a 10 pf capacitor between SD card pin 5 (clk) and pin 6 (Vss)]. This effectively restores GPS performance to the levels obtained without the SD card inside. The rework is not suggested to end users without hardware soldering technique and equipment.
==== Hardware mod related ====

See:
* [[Shop:Speedevil|Speedevil's Shop]] for a UK service to perform this operation on your freerunner, or globally shipped 10pF capacitor.

* [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=490-1278-1-ND Digikey] for the capacitor.

=== Discussion ===

The following is based on [http://lists.openmoko.org/pipermail/community/2008-July/022180.html Alasal's post] to the community mailing list.

;What is TTFF?
:TTFF means Time To First Fix of the GPS. This is the time the GPS needs to get the first clue on where you are on planet earth. So you have to do this only once. After you have a FF (first fix), you can get more fixes without any problems with the SD card in the phone.

;So if we have a first fix, the SD card doesn't block the GPS anymore?
:Yes, the SD card doesn't block the GPS if we have a first fix. (Some people even claim it's more stable)

;Why do we need a first fix?
: According to [http://lists.openmoko.org/pipermail/community/2008-July/020705.html Al Johnson], the Antares4 chip on the GTA02 doesn't have the memory needed to store almanac and ephemeris, last known position or time. This means that every start is a true cold start. It [http://lists.openmoko.org/pipermail/community/2008-July/020772.html is possible] to save location, almanac and ephemeris at GPS shut down, and restore these information at the next startup, but that does not seem implemented yet.

;Does the lower signal also affect accuracy?
:It is a good deal more jittery. However, if you drive around in a city you will get a lot more error from signal reflections than from the jitter.
:''(From http://lists.openmoko.org/pipermail/community/2008-July/022209.html )''

;Do they have a solution?
:Yes. There is already a highly alpha software workaround. The software just turns off the SD card clock when the SD card is not being used. They are also examining a hardware solution.
::The software fix is still in testing. Expect first results this noon (''Thursday, 17th July 2008'') (Taipeh time).
::Also, the hardware fix needed is rather easy. No need to open the shielding or housing. We are working on a document which gives you detailed instructions.
::''(From http://lists.openmoko.org/pipermail/community/2008-July/022242.html )''

;Do we have to return our FreeRunners to OpenMoko?
:Probably not, because the software workaround should work too.

;But we can't read from the SD card when the GPS is on?
:Wrong, you will be able to read the SD card when the GPS is on. The clock for the SD card used to run constantly. Now the kernel turns it off when the SD card is not in use. As long as you are not constantly reading from the SD card, you should see much better first fix times. Obtaining a GPS fix does not affect SD performance.

;Did Openmoko test the GPS with a SD card in it?
:Yes.

;Why didn't they find it while testing the Freerunner?
:Because they have to do the tests with a fake GPS signal and with that signal it worked (In a fab you don't have a decent GPS signal). They have already modified the test, so it corresponds to the GPS signal better.

== Information about faulty antennas ==

* If removing the SD card doesn't help and you suspect your antenna, try unplugging and replugging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this may differ on freerunner, pictures appreciated)
Also note that there is a trac ticket for this issue: [http://docs.openmoko.org/trac/ticket/1542 #1542]

[[FreeRunner_GPS_antenna_repair_SOP]] Indicates that some (rare?) units may have bad soldering, and includes a guide to fix. This will presumably void your warranty.

[[Category:GPS]]

Neo 1973 GPS

2008-07-18T13:16:51Z

Speedevil: add iphone /* GTA01 GPS driver (gllin) */

The [[Neo 1973]] device contains an integrated '''GPS'''. The particular device is marketed as an AGPS, and there is some [[Hardware:AGPS | discussion]] available as to what significance that "A" might have.

The external antenna for the GPS is an MMCX connector. It is located inside the battery compartment, to the left of the battery, and directly above the SD card.

Note that the [[GTA02 GPS]] device contains u-blox ANTARIS 4 solution, you could find more hardware related information before GTA02 hardware page.

A critical problem with early (current) GTA02s is that they can take a long time (10min+) to get first GPS data. This problem has been traced to interference with the SD card, see [[GPS Problems | this page]] for more discussion and suggested fixes.

Assisted GPS performance requirement also defined in GSM/GPRS 3GPP TS 25.171, CDMA 3GPP2 C.S0036-0 

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.
The Iphone 3G also uses the same GPS chip. It's not inconcievable that this might lead to further effort.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

For detailed GTA02 u-blox 4 GPS information, please check here: [[GTA02 GPS]]

To turn on the GPS, echo 1 to the file /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

gpspipe -r 127.0.0.1 2947

gpspipe is in package gps-utils

{{Note|
cat /dev/ttySAC1
Produces the unknown msg*58 this doesn't happen with gpspipe}}

Before getting a fix, the GPS spits out lots of "$GPTXT,01,01,01,NMEA unknown msg*58", though these stop once a fix is obtained.

A position without a fix looks like:
* $GPGGA,235946.99,,,,,00,00,5.0,,M,0.0001999,M,0.0020199,*57
One with a fix:
* $GPGGA,065852.00,5613.022527,N,00306.725890,W,1,05,0.5,158.0,M,0.277000,M,-0.010
0515,*7A

(central Scotland)

--[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

If you are having GPS problems with your freerunner, please document these on the page [[GPS Problems]].
[[FreeRunner_GPS_antenna_repair_SOP]] documents a possible solution.

In Openmoko projects, you could find a GPS test program that could provide graphical and text dump of GPS information. This project called [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
:* [http://wiki.openstreetmap.org/index.php/Rana Raná] is the new version of pyroute
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].
* [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].
* [[GPS Sight]], a popular Openmoko project under LGPL.
* [[Orrery]], an unpopular Openmoko project for displaying the night sky.
* [http://wiki.openstreetmap.org/index.php/Gosmore Gosmore] is a routing and viewer of OSM XML data such as the planet.osm.

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

=== GTA01 ===
*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

=== GTA02 ===
*Power up the bluetooth radio
*Ensure [http://wiki.openmoko.org/wiki/Gpsd#GPS_on_GTA02 gpsd] is running and the gps-utils package is installed
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "gpspipe -r >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

Howto Test Your GPS with agpsui

2008-07-14T16:03:53Z

Speedevil: /* howto */ add

= How to test AGPS on the Neo Freerunner =
==Overview==
Some Freerunner GPSs appear to be insensitive, taking a long time, or not obtaining a fix at all, even in ideal condtions.

Time to first fix (TTFix) should be well under 15 minutes in all cases when the Freerunner has a view of the sky, however some appear to have bad solder joints between the GPS antenna
connector and the Freerunner main PCB.

===Why do I need to test?===
This guide outlines how to gather data to help fix this problem.
It's important for both those with working GPS, and those with not-working GPS to perform this test.

There may be some with marginal GPSs that appear to work, but are drastically less sensitive than the norm.

This guide assumes that you've managed to configure your Freerunner so that you can install opkg packages from buildhost.openmoko.org/daily-feed/ , either directly through wifi or usb networking, or by downloading them to a desktop and transferring them with scp.

===Aims===
We need to find the average reported signal strength of phones in a similar condition.

This should be outside, with no obstructions too near the horizon.
A location with nothing within 30 degrees of the horizon is adequate. The occasional sticking up building or tree is not a big issue.

The phone should be placed upright, with the screen upright in order to make the antenna (at the top of the phone) most sensitive - if placed flat on a table, it will have very poor sensitivity to half the satellites in the sky.

Could you report the following numbers.
*Serial number, this number is printed on both the black box packaging and under the battery of your freerunner. It's 9 digits and begins 8A86<xxxxx>
* Number of satelites your phone managed to detect and a estimate of the average signal strength in dBm for those satelites. (We don't need to know the average for each satelite, just the average for all satelites.)

== Howto ==

*1. Assuming you have a fresh-from-the-factory freerunner, first get some
basic networking configured. this is beyond the scope of this howto.
*2. ssh to the freerunner :
ssh root@192.168.0.202
*3a. If you have a working wifi or usb network:
opkg update
( Ignore all warnings about missing signature files, the
openmoko repository haven't got any at the moment.)
*3b. Or if your doing this the basic way, download openmoko-agpsui and
then transfer to your freerunner:
wget http://buildhost.openmoko.org/daily-feed/armv4t/openmoko-agpsui_*.ipk
scp openmoko-agpsui_*.ipk root@192.168.0.202:/home/root/.
*4. Install the package openmoko-agpsui:
opkg install openmoko-agpsui
or
opkg install openmoko-agpsui_*.ipk
*5. After having completed all these steps sucessfully your ready to
test your freerunner.
Charge your battery to full capacity (can't hurt), wait for a clear
weather and then check out places you can visit. The ideal place is
Charlie's midle of nowhere, but the next best thing is a area with
clear view of the sky and no towering foliage or buildings nearby.
Nice weather is a must have because you don't want your shiny
freerunner to get soaked do you?
*6. Find a place where your freerunner can sit on a stable surface or
at least 30 minutes without being molested, fondled or even touched.
Leave the freerunner with the screen facing upwards, preferably with
the top of the freerunner facing northish. (Not a requirement, just
trying to be scientific. ;) )
*7. on the freerunner Graphical User Interface you should find a program
called "Openmoko AGPS UI". Run this program.
The program has several interesting features. on the top left side of
it's UI you can find the tabs:
'''"Run" "SS" "AZ" "plot" "Log"'''
:"Run" is the current picture, here you start and stop the GPS
:: testing software. Everything with the word "Reset" reset's the
:: sampling and/or the chipset. "Power on"/"Power off" powers up
:: (or down) the GPS chipset and starts logging. "One Fix" starts
:: the logging but powers automatically down after having managed
:: to get FFix from a single satelite.
:"SS" gives you signalstrength, calculates average
:: signalstrength, identifies the differnt satelites by number and
:: of course lets you count the number of satelites _IF_ it can
:: manage to find at least 1 satelite.
:"AZ" gives you the position of the different satelites _after_ it
:: get's a FFIX. Otherwise a satelite is "defaulted" to being
:: somewhere over the northpole. (on a _very_ thight polar orbital
:: indeed. ;) )
:"Plot" gives a estimate on where the different satelites say _you_ are,
:: usually with a margin of +-5 meters. (10 meters in difference.)
:"Log" gives you the NEMA output from the GPS chipset. Interesting for
:: those who can read NEMAish, not so interesting for the rest of
:: us.
*8. Now press "Power on" and then "SS", then leave the Freerunner in a vertical position for _at least 30 minutes without moving or
touching it_. (a large mug works well as a stand) Do not stand over it either, your blocking those precious
satelite signals! ( GPS runs at ~ 1,2-1,5 Ghz, this is a weak signal
with a wavelength of 20cm, now imagine
godzilla (you) smashing them. )
*9. After having spent twidling your thumbs or reading a good book for
30 minutes you get to press the "dBm" button to translate those nasty
dB.Hz into goodness dBm signals. If you've gotten FFix some of the blue
blue bars has a nice black thing on the bottom. And on top of screen
above each bar there are two numbers, the top denoting the maximum
signal you got from each satelite and the lower number the average
signalstrength.
*10. If you haven't managed to get a FFIX your either doing something
wrong or your one of those unlucky guys (gals) with a bad solder or
something else that probably requires shipping the phone back to your
supplier/openmoko.
If you got only 3-4 satelites and had a lousy reception (say -150 to
-160 dBm) you /might/ have a faulty freerunner but you should try again
somewhere else at another time of the day just to make sure. If you had
a lousy reception but did get a FFix, try again somewhere else to se if
you can improve your record. If you on the other hand found several
satelites( +5) and had quite a good reception (maybe > -145 dBm ? )
the you probably has a working phone.
Now, I'm not a radio or wireless engineer, so any numbers in dBm should
be taken with a grain of salt. But the main thing is that you followed
the basic instruction and did a thorough scientific test! You did
Science!
*11. Now report any anomalities to the apropriate mailinglists or the guys that told
you to read this howto.

== Recommended Reading ==
http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner
http://wiki.openmoko.org/wiki/FreeRunner_GPS_antenna_repair_SOP
http://wiki.openmoko.org/wiki/USB_Networking
http://en.wikipedia.org/wiki/Global_Positioning_System

[[category:GPS]]
[[category:GTA02 Hardware]]
[[Category:Hardware]]

Howto Test Your GPS with agpsui

2008-07-14T16:00:12Z

Speedevil: /* Aims */ more

= How to test AGPS on the Neo Freerunner =
==Overview==
Some Freerunner GPSs appear to be insensitive, taking a long time, or not obtaining a fix at all, even in ideal condtions.

Time to first fix (TTFix) should be well under 15 minutes in all cases when the Freerunner has a view of the sky, however some appear to have bad solder joints between the GPS antenna
connector and the Freerunner main PCB.

===Why do I need to test?===
This guide outlines how to gather data to help fix this problem.
It's important for both those with working GPS, and those with not-working GPS to perform this test.

There may be some with marginal GPSs that appear to work, but are drastically less sensitive than the norm.

This guide assumes that you've managed to configure your Freerunner so that you can install opkg packages from buildhost.openmoko.org/daily-feed/ , either directly through wifi or usb networking, or by downloading them to a desktop and transferring them with scp.

===Aims===
We need to find the average reported signal strength of phones in a similar condition.

This should be outside, with no obstructions too near the horizon.
A location with nothing within 30 degrees of the horizon is adequate. The occasional sticking up building or tree is not a big issue.

The phone should be placed upright, with the screen upright in order to make the antenna (at the top of the phone) most sensitive - if placed flat on a table, it will have very poor sensitivity to half the satellites in the sky.

Could you report the following numbers.
*Serial number, this number is printed on both the black box packaging and under the battery of your freerunner. It's 9 digits and begins 8A86<xxxxx>
* Number of satelites your phone managed to detect and a estimate of the average signal strength in dBm for those satelites. (We don't need to know the average for each satelite, just the average for all satelites.)

== howto ==

*1. Assuming you have a fresh-from-the-factory freerunner, first get some
basic networking configured. this is beyond the scope of this howto.
*2. ssh to the freerunner :
ssh root@192.168.0.202
*3a. If you have a working wifi or usb network:
opkg update
( Ignore all warnings about missing signature files, the
openmoko repository haven't got any at the moment.)
*3b. Or if your doing this the basic way, download openmoko-agpsui and
then transfer to your freerunner:
wget http://buildhost.openmoko.org/daily-feed/armv4t/openmoko-agpsui_*.ipk
scp openmoko-agpsui_*.ipk root@192.168.0.202:/home/root/.
*4. Install the package openmoko-agpsui:
opkg install openmoko-agpsui
or
opkg install openmoko-agpsui_*.ipk
*5. After having completed all these steps sucessfully your ready to
test your freerunner.
Charge your battery to full capacity (can't hurt), wait for a clear
weather and then check out places you can visit. The ideal place is
Charlie's midle of nowhere, but the next best thing is a area with
clear view of the sky and no towering foliage or buildings nearby.
Nice weather is a must have because you don't want your shiny
freerunner to get soaked do you?
*6. Find a place where your freerunner can sit on a stable surface or
at least 30 minutes without being molested, fondled or even touched.
Leave the freerunner with the screen facing upwards, preferably with
the top of the freerunner facing northish. (Not a requirement, just
trying to be scientific. ;) )
*7. on the freerunner Graphical User Interface you should find a program
called "Openmoko AGPS UI". Run this program.
The program has several interesting features. on the top left side of
it's UI you can find the tabs:
'''"Run" "SS" "AZ" "plot" "Log"'''
:"Run" is the current picture, here you start and stop the GPS
:: testing software. Everything with the word "Reset" reset's the
:: sampling and/or the chipset. "Power on"/"Power off" powers up
:: (or down) the GPS chipset and starts logging. "One Fix" starts
:: the logging but powers automatically down after having managed
:: to get FFix from a single satelite.
:"SS" gives you signalstrength, calculates average
:: signalstrength, identifies the differnt satelites by number and
:: of course lets you count the number of satelites _IF_ it can
:: manage to find at least 1 satelite.
:"AZ" gives you the position of the different satelites _after_ it
:: get's a FFIX. Otherwise a satelite is "defaulted" to being
:: somewhere over the northpole. (on a _very_ thight polar orbital
:: indeed. ;) )
:"Plot" gives a estimate on where the different satelites say _you_ are,
:: usually with a margin of +-5 meters. (10 meters in difference.)
:"Log" gives you the NEMA output from the GPS chipset. Interesting for
:: those who can read NEMAish, not so interesting for the rest of
:: us.
*8. Now press "Power on" and then "SS", then leave the darn freerunner on
the safe and flat surface for _at least 30 minutes without moving or
touching it_. Do not stand over it either, your blocking those precious
satelite signals! ( GPS runs at ~ 1,2-1,5 Ghz, this is a weak signal
with a wavelength between millimeters and centimeters, now imagine
godzilla (you) smashing them. )
*9. After having spent twidling your thumbs or reading a good book for
30 minutes you get to press the "dBm" button to translate those nasty
dB.Hz into goodness dBm signals. If you've gotten FFix some of the blue
blue bars has a nice black thing on the bottom. And on top of screen
above each bar there are two numbers, the top denoting the maximum
signal you got from each satelite and the lower number the average
signalstrength.
*10. If you haven't managed to get a FFIX your either doing something
wrong or your one of those unlucky guys (gals) with a bad solder or
something else that probably requires shipping the phone back to your
supplier/openmoko.
If you got only 3-4 satelites and had a lousy reception (say -150 to
-160 dBm) you /might/ have a faulty freerunner but you should try again
somewhere else at another time of the day just to make sure. If you had
a lousy reception but did get a FFix, try again somewhere else to se if
you can improve your record. If you on the other hand found several
satelites( +5) and had quite a good reception (maybe > -145 dBm ? )
the you probably has a working phone.
Now, I'm not a radio or wireless engineer, so any numbers in dBm should
be taken with a grain of salt. But the main thing is that you followed
the basic instruction and did a thorough scientific test! You did
Science!
*11. Now report any anomalities to the apropriate mailinglists or the guys that told
you to read this howto.

== Recommended Reading ==
http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner
http://wiki.openmoko.org/wiki/FreeRunner_GPS_antenna_repair_SOP
http://wiki.openmoko.org/wiki/USB_Networking
http://en.wikipedia.org/wiki/Global_Positioning_System

[[category:GPS]]
[[category:GTA02 Hardware]]
[[Category:Hardware]]

Howto Test Your GPS with agpsui

2008-07-14T15:58:05Z

Speedevil: /* Overview */ typo

= How to test AGPS on the Neo Freerunner =
==Overview==
Some Freerunner GPSs appear to be insensitive, taking a long time, or not obtaining a fix at all, even in ideal condtions.

Time to first fix (TTFix) should be well under 15 minutes in all cases when the Freerunner has a view of the sky, however some appear to have bad solder joints between the GPS antenna
connector and the Freerunner main PCB.

===Why do I need to test?===
This guide outlines how to gather data to help fix this problem.
It's important for both those with working GPS, and those with not-working GPS to perform this test.

There may be some with marginal GPSs that appear to work, but are drastically less sensitive than the norm.

This guide assumes that you've managed to configure your Freerunner so that you can install opkg packages from buildhost.openmoko.org/daily-feed/ , either directly through wifi or usb networking, or by downloading them to a desktop and transferring them with scp.

===Aims===
We need to find the average reported signal strength of phones in a similar condition.

This should be outside, with no obstructions too near the horizon.
A location with nothing within 30 degrees of the horizon is adequate. The occasional sticking up building or tree is not a big issue.

The phone should be placed upright, with the screen upright in order to make the antenna (at the top of the phone) most sensitive - if placed flat on a table, it will have very poor sensitivity to half the satellites in the sky.

Could you report the following numbers.
*Serial number, this number is printed on both the black
box packaging and under the battery of your freerunner. It's
9 digits and begins 8A86<xxxxx>
* Number of satelites your phone managed to detect and a estimate of the average signal strength in dBm for those satelites. (We don't need to know the average for each satelite, just the average for all satelites.)

== howto ==

*1. Assuming you have a fresh-from-the-factory freerunner, first get some
basic networking configured. this is beyond the scope of this howto.
*2. ssh to the freerunner :
ssh root@192.168.0.202
*3a. If you have a working wifi or usb network:
opkg update
( Ignore all warnings about missing signature files, the
openmoko repository haven't got any at the moment.)
*3b. Or if your doing this the basic way, download openmoko-agpsui and
then transfer to your freerunner:
wget http://buildhost.openmoko.org/daily-feed/armv4t/openmoko-agpsui_*.ipk
scp openmoko-agpsui_*.ipk root@192.168.0.202:/home/root/.
*4. Install the package openmoko-agpsui:
opkg install openmoko-agpsui
or
opkg install openmoko-agpsui_*.ipk
*5. After having completed all these steps sucessfully your ready to
test your freerunner.
Charge your battery to full capacity (can't hurt), wait for a clear
weather and then check out places you can visit. The ideal place is
Charlie's midle of nowhere, but the next best thing is a area with
clear view of the sky and no towering foliage or buildings nearby.
Nice weather is a must have because you don't want your shiny
freerunner to get soaked do you?
*6. Find a place where your freerunner can sit on a stable surface or
at least 30 minutes without being molested, fondled or even touched.
Leave the freerunner with the screen facing upwards, preferably with
the top of the freerunner facing northish. (Not a requirement, just
trying to be scientific. ;) )
*7. on the freerunner Graphical User Interface you should find a program
called "Openmoko AGPS UI". Run this program.
The program has several interesting features. on the top left side of
it's UI you can find the tabs:
'''"Run" "SS" "AZ" "plot" "Log"'''
:"Run" is the current picture, here you start and stop the GPS
:: testing software. Everything with the word "Reset" reset's the
:: sampling and/or the chipset. "Power on"/"Power off" powers up
:: (or down) the GPS chipset and starts logging. "One Fix" starts
:: the logging but powers automatically down after having managed
:: to get FFix from a single satelite.
:"SS" gives you signalstrength, calculates average
:: signalstrength, identifies the differnt satelites by number and
:: of course lets you count the number of satelites _IF_ it can
:: manage to find at least 1 satelite.
:"AZ" gives you the position of the different satelites _after_ it
:: get's a FFIX. Otherwise a satelite is "defaulted" to being
:: somewhere over the northpole. (on a _very_ thight polar orbital
:: indeed. ;) )
:"Plot" gives a estimate on where the different satelites say _you_ are,
:: usually with a margin of +-5 meters. (10 meters in difference.)
:"Log" gives you the NEMA output from the GPS chipset. Interesting for
:: those who can read NEMAish, not so interesting for the rest of
:: us.
*8. Now press "Power on" and then "SS", then leave the darn freerunner on
the safe and flat surface for _at least 30 minutes without moving or
touching it_. Do not stand over it either, your blocking those precious
satelite signals! ( GPS runs at ~ 1,2-1,5 Ghz, this is a weak signal
with a wavelength between millimeters and centimeters, now imagine
godzilla (you) smashing them. )
*9. After having spent twidling your thumbs or reading a good book for
30 minutes you get to press the "dBm" button to translate those nasty
dB.Hz into goodness dBm signals. If you've gotten FFix some of the blue
blue bars has a nice black thing on the bottom. And on top of screen
above each bar there are two numbers, the top denoting the maximum
signal you got from each satelite and the lower number the average
signalstrength.
*10. If you haven't managed to get a FFIX your either doing something
wrong or your one of those unlucky guys (gals) with a bad solder or
something else that probably requires shipping the phone back to your
supplier/openmoko.
If you got only 3-4 satelites and had a lousy reception (say -150 to
-160 dBm) you /might/ have a faulty freerunner but you should try again
somewhere else at another time of the day just to make sure. If you had
a lousy reception but did get a FFix, try again somewhere else to se if
you can improve your record. If you on the other hand found several
satelites( +5) and had quite a good reception (maybe > -145 dBm ? )
the you probably has a working phone.
Now, I'm not a radio or wireless engineer, so any numbers in dBm should
be taken with a grain of salt. But the main thing is that you followed
the basic instruction and did a thorough scientific test! You did
Science!
*11. Now report any anomalities to the apropriate mailinglists or the guys that told
you to read this howto.

== Recommended Reading ==
http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner
http://wiki.openmoko.org/wiki/FreeRunner_GPS_antenna_repair_SOP
http://wiki.openmoko.org/wiki/USB_Networking
http://en.wikipedia.org/wiki/Global_Positioning_System

[[category:GPS]]
[[category:GTA02 Hardware]]
[[Category:Hardware]]

Howto Test Your GPS with agpsui

2008-07-14T15:56:36Z

Speedevil: /* How to test AGPS on the Neo Freerunner */ copy edit, add position

= How to test AGPS on the Neo Freerunner =
==Overview==
Some Freerunner GPSs appear to be insensitive, taking a long time, or not obtaining a fix at all, even in ideal condtions.

Time to first fix (TTFix) should be well under 15 minutes in all cases when the Freerunner has a view of the sky, however some appear to have bad solder joints between the GPS antenna
connector and the Freerunner main PCB.

===Why do I need to test?===T
his guide outlines how to gather data to help fix this problem.
It's important for both those with working GPS, and those with not-working GPS to perform this test.

There may be some with marginal GPSs that appear to work, but are drastically less sensitive than the norm.

This guide assumes that you've managed to configure your Freerunner so that you can install opkg packages from buildhost.openmoko.org/daily-feed/ , either directly through wifi or usb networking, or by downloading them to a desktop and transferring them with scp.

===Aims===
We need to find the average reported signal strength of phones in a similar condition.

This should be outside, with no obstructions too near the horizon.
A location with nothing within 30 degrees of the horizon is adequate. The occasional sticking up building or tree is not a big issue.

The phone should be placed upright, with the screen upright in order to make the antenna (at the top of the phone) most sensitive - if placed flat on a table, it will have very poor sensitivity to half the satellites in the sky.

Could you report the following numbers.
*Serial number, this number is printed on both the black
box packaging and under the battery of your freerunner. It's
9 digits and begins 8A86<xxxxx>
* Number of satelites your phone managed to detect and a estimate of the average signal strength in dBm for those satelites. (We don't need to know the
average for each satelite, just the average for all satelites.)

== howto ==

*1. Assuming you have a fresh-from-the-factory freerunner, first get some
basic networking configured. this is beyond the scope of this howto.
*2. ssh to the freerunner :
ssh root@192.168.0.202
*3a. If you have a working wifi or usb network:
opkg update
( Ignore all warnings about missing signature files, the
openmoko repository haven't got any at the moment.)
*3b. Or if your doing this the basic way, download openmoko-agpsui and
then transfer to your freerunner:
wget http://buildhost.openmoko.org/daily-feed/armv4t/openmoko-agpsui_*.ipk
scp openmoko-agpsui_*.ipk root@192.168.0.202:/home/root/.
*4. Install the package openmoko-agpsui:
opkg install openmoko-agpsui
or
opkg install openmoko-agpsui_*.ipk
*5. After having completed all these steps sucessfully your ready to
test your freerunner.
Charge your battery to full capacity (can't hurt), wait for a clear
weather and then check out places you can visit. The ideal place is
Charlie's midle of nowhere, but the next best thing is a area with
clear view of the sky and no towering foliage or buildings nearby.
Nice weather is a must have because you don't want your shiny
freerunner to get soaked do you?
*6. Find a place where your freerunner can sit on a stable surface or
at least 30 minutes without being molested, fondled or even touched.
Leave the freerunner with the screen facing upwards, preferably with
the top of the freerunner facing northish. (Not a requirement, just
trying to be scientific. ;) )
*7. on the freerunner Graphical User Interface you should find a program
called "Openmoko AGPS UI". Run this program.
The program has several interesting features. on the top left side of
it's UI you can find the tabs:
'''"Run" "SS" "AZ" "plot" "Log"'''
:"Run" is the current picture, here you start and stop the GPS
:: testing software. Everything with the word "Reset" reset's the
:: sampling and/or the chipset. "Power on"/"Power off" powers up
:: (or down) the GPS chipset and starts logging. "One Fix" starts
:: the logging but powers automatically down after having managed
:: to get FFix from a single satelite.
:"SS" gives you signalstrength, calculates average
:: signalstrength, identifies the differnt satelites by number and
:: of course lets you count the number of satelites _IF_ it can
:: manage to find at least 1 satelite.
:"AZ" gives you the position of the different satelites _after_ it
:: get's a FFIX. Otherwise a satelite is "defaulted" to being
:: somewhere over the northpole. (on a _very_ thight polar orbital
:: indeed. ;) )
:"Plot" gives a estimate on where the different satelites say _you_ are,
:: usually with a margin of +-5 meters. (10 meters in difference.)
:"Log" gives you the NEMA output from the GPS chipset. Interesting for
:: those who can read NEMAish, not so interesting for the rest of
:: us.
*8. Now press "Power on" and then "SS", then leave the darn freerunner on
the safe and flat surface for _at least 30 minutes without moving or
touching it_. Do not stand over it either, your blocking those precious
satelite signals! ( GPS runs at ~ 1,2-1,5 Ghz, this is a weak signal
with a wavelength between millimeters and centimeters, now imagine
godzilla (you) smashing them. )
*9. After having spent twidling your thumbs or reading a good book for
30 minutes you get to press the "dBm" button to translate those nasty
dB.Hz into goodness dBm signals. If you've gotten FFix some of the blue
blue bars has a nice black thing on the bottom. And on top of screen
above each bar there are two numbers, the top denoting the maximum
signal you got from each satelite and the lower number the average
signalstrength.
*10. If you haven't managed to get a FFIX your either doing something
wrong or your one of those unlucky guys (gals) with a bad solder or
something else that probably requires shipping the phone back to your
supplier/openmoko.
If you got only 3-4 satelites and had a lousy reception (say -150 to
-160 dBm) you /might/ have a faulty freerunner but you should try again
somewhere else at another time of the day just to make sure. If you had
a lousy reception but did get a FFix, try again somewhere else to se if
you can improve your record. If you on the other hand found several
satelites( +5) and had quite a good reception (maybe > -145 dBm ? )
the you probably has a working phone.
Now, I'm not a radio or wireless engineer, so any numbers in dBm should
be taken with a grain of salt. But the main thing is that you followed
the basic instruction and did a thorough scientific test! You did
Science!
*11. Now report any anomalities to the apropriate mailinglists or the guys that told
you to read this howto.

== Recommended Reading ==
http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner
http://wiki.openmoko.org/wiki/FreeRunner_GPS_antenna_repair_SOP
http://wiki.openmoko.org/wiki/USB_Networking
http://en.wikipedia.org/wiki/Global_Positioning_System

[[category:GPS]]
[[category:GTA02 Hardware]]
[[Category:Hardware]]

Howto Test Your GPS with agpsui

2008-07-14T15:36:09Z

Speedevil: /* How to test AGPS on the Neo Freerunner */ copy edit

== How to test AGPS on the Neo Freerunner ==

Some Freerunner GPSs appear to be insensitive, taking a long time, or not obtaining a fix at all, even in ideal condtions.

Time to first fix (TTFix) should be well under 15 minutes in all cases when the Freerunner has a view of the sky, however some appear to have bad solder joints between the GPS antenna
connector and the Freerunner main PCB.

This guide outlines how to gather data to help fix this problem.

It's important for both those with working GPS, and those with not-working GPS to perform this test.

There may be some with marginal GPSs that appear to work, but are drastically less sensitive than the norm.

This guide will assume that you've managed to configure your Freerunner so that you can install opkg packages from buildhost.openmoko.org/daily-feed/ , either directly through wifi or usb networking, or by downloading them to a desktop and transferring them with scp.

First of all, what were trying to do is to get a estimate on how well
the GPS works. This means that any numbers you aquire is _not_
necessarily comparable with somebody else's. If Alice reports seeing 13
satelites with an signal strength of ~ -140 dBm and got a FFix in 4
minutes then Bob can't assume he has a broken GPS if he saw only 5
satelites at a signal strength of ~ -145 dBm and it tok 45 minutes to
get a FFix. If Charlie on the other hand saw only 2 satelites @ ~ -157
dBm and didn't get a FFix after leaving the freerunner on a table for
two hours in the midle of nowhere and the freerunner had a clear 360
degrees view then Charlie can safely assume he indeed has a broken GPS.

In fact, these are the number we want you to report:
Serial number on your phone. This number is printed on both the black
box packaging and under the battery of your freerunner.
All serialnumbers are 9 digits and they begin with S/N: 8A86<xxxxx>
In adition, we would like you to report then number of satelites your
phone managed to detect and a estimate on what the average
signal strength in dBm for those satelites. (We don't need to know the
average for each satelite, just the average for all satelites.)

== howto ==

*1. Assuming you have a fresh-from-the-factory freerunner, first get some
basic networking configured. this is beyond the scope of this howto.
*2. ssh to the freerunner :
ssh root@192.168.0.202
*3a. If you have a working wifi or usb network:
opkg update
( Ignore all warnings about missing signature files, the
openmoko repository haven't got any at the moment.)
*3b. Or if your doing this the basic way, download openmoko-agpsui and
then transfer to your freerunner:
wget http://buildhost.openmoko.org/daily-feed/armv4t/openmoko-agpsui_*.ipk
scp openmoko-agpsui_*.ipk root@192.168.0.202:/home/root/.
*4. Install the package openmoko-agpsui:
opkg install openmoko-agpsui
or
opkg install openmoko-agpsui_*.ipk
*5. After having completed all these steps sucessfully your ready to
test your freerunner.
Charge your battery to full capacity (can't hurt), wait for a clear
weather and then check out places you can visit. The ideal place is
Charlie's midle of nowhere, but the next best thing is a area with
clear view of the sky and no towering foliage or buildings nearby.
Nice weather is a must have because you don't want your shiny
freerunner to get soaked do you?
*6. Find a place where your freerunner can sit on a stable surface or
at least 30 minutes without being molested, fondled or even touched.
Leave the freerunner with the screen facing upwards, preferably with
the top of the freerunner facing northish. (Not a requirement, just
trying to be scientific. ;) )
*7. on the freerunner Graphical User Interface you should find a program
called "Openmoko AGPS UI". Run this program.
The program has several interesting features. on the top left side of
it's UI you can find the tabs:
'''"Run" "SS" "AZ" "plot" "Log"'''
:"Run" is the current picture, here you start and stop the GPS
:: testing software. Everything with the word "Reset" reset's the
:: sampling and/or the chipset. "Power on"/"Power off" powers up
:: (or down) the GPS chipset and starts logging. "One Fix" starts
:: the logging but powers automatically down after having managed
:: to get FFix from a single satelite.
:"SS" gives you signalstrength, calculates average
:: signalstrength, identifies the differnt satelites by number and
:: of course lets you count the number of satelites _IF_ it can
:: manage to find at least 1 satelite.
:"AZ" gives you the position of the different satelites _after_ it
:: get's a FFIX. Otherwise a satelite is "defaulted" to being
:: somewhere over the northpole. (on a _very_ thight polar orbital
:: indeed. ;) )
:"Plot" gives a estimate on where the different satelites say _you_ are,
:: usually with a margin of +-5 meters. (10 meters in difference.)
:"Log" gives you the NEMA output from the GPS chipset. Interesting for
:: those who can read NEMAish, not so interesting for the rest of
:: us.
*8. Now press "Power on" and then "SS", then leave the darn freerunner on
the safe and flat surface for _at least 30 minutes without moving or
touching it_. Do not stand over it either, your blocking those precious
satelite signals! ( GPS runs at ~ 1,2-1,5 Ghz, this is a weak signal
with a wavelength between millimeters and centimeters, now imagine
godzilla (you) smashing them. )
*9. After having spent twidling your thumbs or reading a good book for
30 minutes you get to press the "dBm" button to translate those nasty
dB.Hz into goodness dBm signals. If you've gotten FFix some of the blue
blue bars has a nice black thing on the bottom. And on top of screen
above each bar there are two numbers, the top denoting the maximum
signal you got from each satelite and the lower number the average
signalstrength.
*10. If you haven't managed to get a FFIX your either doing something
wrong or your one of those unlucky guys (gals) with a bad solder or
something else that probably requires shipping the phone back to your
supplier/openmoko.
If you got only 3-4 satelites and had a lousy reception (say -150 to
-160 dBm) you /might/ have a faulty freerunner but you should try again
somewhere else at another time of the day just to make sure. If you had
a lousy reception but did get a FFix, try again somewhere else to se if
you can improve your record. If you on the other hand found several
satelites( +5) and had quite a good reception (maybe > -145 dBm ? )
the you probably has a working phone.
Now, I'm not a radio or wireless engineer, so any numbers in dBm should
be taken with a grain of salt. But the main thing is that you followed
the basic instruction and did a thorough scientific test! You did
Science!
*11. Now report any anomalities to the apropriate mailinglists or the guys that told
you to read this howto.

== Recommended Reading ==
http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner
http://wiki.openmoko.org/wiki/FreeRunner_GPS_antenna_repair_SOP
http://wiki.openmoko.org/wiki/USB_Networking
http://en.wikipedia.org/wiki/Global_Positioning_System

[[category:GPS]]
[[category:GTA02 Hardware]]
[[Category:Hardware]]

FreeRunner GPS antenna repair SOP

2008-07-11T13:00:20Z

Speedevil: disclaimer

This will probably void any warranty.
Make sure of this before attempting.

'''1. GPS Antenna CON(CON7601)，there are bad soldering issues with this PIN.'''

[[Image:PICT1311.JPG|500px|center]]

'''2. Need to re-solder PIN to improve connection.'''

[[Image:PICT1310.JPG|500px|center]]

'''3. There are deformities in the internal GPS connector.'''

[[Image:PICT1312.JPG|500px|center]]

'''4. Use tweezers to pinch the antenna back to original form.'''

[[Image:PICT1313.JPG|500px|center]]

'''5. Now try re-connecting the antenna. The antenna should ‘snap’ into place of the connector locking itself firmly. If it is loose and does not snap, it is possible there will be quality issues.'''

[[Image:Gps.JPG|500px|center]]

[[Category:Hardware]]
[[Category:GTA02 Hardware]]
[[Category:GPS]]

Neo 1973 GPS

2008-07-11T12:56:22Z

Speedevil: /* GTA02 GPS */ add link to repair page

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

Note that the GTA02 device contains u-blox ANTARIS 4 solution, you could find more hardware related information before GTA02 hardware page.

Assisted GPS performance requirement also defined in GSM/GPRS 3GPP TS 25.171, CDMA 3GPP2 C.S0036-0 

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

For detailed GTA02 u-blox 4 GPS information, please check here: [[GTA02 GPS]]

To turn on the GPS, echo 1 to the file /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

gpspipe -r 127.0.0.1 2947

gpspipe is in package gps-utils

{{Note|
cat /dev/ttySAC1
Produces the unknown msg*58 this doesn't happen with gpspipe}}

Before getting a fix, the GPS spits out lots of "$GPTXT,01,01,01,NMEA unknown msg*58", though these stop once a fix is obtained.

A position without a fix looks like:
* $GPGGA,235946.99,,,,,00,00,5.0,,M,0.0001999,M,0.0020199,*57
One with a fix:
* $GPGGA,065852.00,5613.022527,N,00306.725890,W,1,05,0.5,158.0,M,0.277000,M,-0.010
0515,*7A

(central Scotland)

--[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

If you are having GPS problems with your freerunner, please document these on the page [[GPS Problems]].
[[FreeRunner_GPS_antenna_repair_SOP]] documents a possible solution.

In Openmoko projects, you could find a GPS test program that could provide graphical and text dump of GPS information. This project called [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
:* [http://wiki.openstreetmap.org/index.php/Rana Raná] is the new version of pyroute
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].
* [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].
* [[GPS Sight]], a popular Openmoko project under LGPL.
* [[Orrery]], an unpopular Openmoko project for displaying the night sky.
* [http://wiki.openstreetmap.org/index.php/Gosmore Gosmore] is a routing and viewer of OSM XML data such as the planet.osm.

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

GPS Problems

2008-07-11T12:54:17Z

Speedevil: add link

See [[GPS]] for details on how to evaluate the Freerunner GPS with cat.

{|border="3"
|+Problems I'm having with the GPS
!Username||Checked outside?||External antenna?||Note
|-
|Pthorin ||Yes|| No ||I tried for about 40 minutes outside, I'm running om-gta02 P1-Snapshot-20080622. Did get GPS time outside, but only got lines like:
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30

--[[User:Pthorin|Pthorin]] 05:11, 11 July 2008 (UTC) I tried it out once again after removing the front cover and got a fix quite fast, less than five minutes. Could there be an issue with the case blocking the signals? Could the snap/latch above the antenna be a problem?
|-
|iandouglas ||Yes|| No ||Spent over a half hour outdoors, the NMEA port on my Samsung Blackjack 2 found my position just fine, but also got the same 99.99,99.99,99.99*30 line as Pthorin when powering on the GPS unit, starting gpsd, then running gpspipe at the command line
|-
|Dummy ||?|| ? ||
|}

=== Solved problems ===

''Let's collect hints which could solve the above problems here. E.g.: How to get the best results with your internal antenna''

* Before reporting a problem here, please check that you've had the GPS out in the open air, preferably with the GPS antenna pointed up, for over 15 mins. (the screen the right way up). This should get a lock in even the worst cases.

* Also note if you've tried unpluging and repluging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this may differ on freerunner, pictures appreciated)

[[FreeRunner_GPS_antenna_repair_SOP]] Indicates that the problem may be bad soldering, and includes a guide to fix. This will presumably void your warranty.

[[Category:GPS]]

Neo 1973 GPS

2008-07-10T12:42:19Z

Speedevil: /* GTA01 GPS driver (gllin) */ remove very historical

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

Note that the GTA02 device contains u-blox ANTARIS 4 solution, you could find more hardware related information before GTA02 hardware page.

Assisted GPS performance requirement also defined in GSM/GPRS 3GPP TS 25.171, CDMA 3GPP2 C.S0036-0 

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

For detailed GTA02 u-blox 4 GPS information, please check here: [http://wiki.openmoko.org/wiki/GTA02_GPS GTA02 GPS]

To turn on the GPS, echo 1 to the file /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

gpspipe -r /dev/ttySAC1

gpspipe is in package gps-utils

{{Note|
cat /dev/ttySAC1
Produces the unknown msg*58 this doesn't happen with gpspipe}}

Before getting a fix, the GPS spits out lots of "$GPTXT,01,01,01,NMEA unknown msg*58", though these stop once a fix is obtained.

A position without a fix looks like:
* $GPGGA,235946.99,,,,,00,00,5.0,,M,0.0001999,M,0.0020199,*57
One with a fix:
* $GPGGA,065852.00,5613.022527,N,00306.725890,W,1,05,0.5,158.0,M,0.277000,M,-0.010
0515,*7A

(central Scotland)

--[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

If you are having GPS problems with your freerunner, please document these on the page [[GPS Problems]].

In Openmoko projects, you could find a GPS test program that could provide graphical and text dump of GPS information. This project called [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
:* [http://wiki.openstreetmap.org/index.php/Rana Raná] is the new version of pyroute
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].
* [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].
* [[GPS Sight]], a popular Openmoko project under LGPL.
* [[Orrery]], an unpopular Openmoko project for displaying the night sky.
* [http://wiki.openstreetmap.org/index.php/Gosmore Gosmore] is a routing and viewer of OSM XML data such as the planet.osm.

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

GPS Problems

2008-07-09T19:58:43Z

Speedevil: add dissasembly link

See [[GPS]] for details on how to evaluate the Freerunner GPS with cat.

Before reporting a problem here, please check that you've had the GPS out in the open air, preferably with the GPS antenna pointed up, for over 15 mins. (the screen the right way up)

This should get a lock in even the worst cases.

Also note if you've tried unpluging and repluging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this may differ on freerunner, pictures appreciated)

{|border="3"
|+Problems I'm having with the GPS
!Username||Checked outside?||External antenna?||Note
|-
|Pthorin ||Yes|| No ||I tried for about 40 minutes outside, I'm running om-gta02 P1-Snapshot-20080622. Did get GPS time outside, but only got lines like:
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
|-
|Dummy ||?|| ? ||
|}

GPS Problems

2008-07-09T19:14:15Z

Speedevil: oops

GPS Problems

2008-07-09T19:10:54Z

Speedevil: GPS problems

FAQ

2008-07-09T19:05:07Z

Speedevil: /* Q: Can I has some money for a Neo1973? */

Frequently Asked Questions... with answers included!

==Introduction==

=== Q: What is OpenMoko? What is the Neo 1973? What is the Neo Freerunner? ===
A: [[OpenMoko]] is a software platform and the world's first completely open mobile phone software stack. It is based on Linux and allows users and enthusiasts great freedom to customise their phone.
* The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.
* The FIC [[Neo FreeRunner]] is the second Openmoko phone and is now available for sale!

=== Q: I'm a ____ expert, can I join/help OpenMoko? ===

We would love to hear from you.

* If you are interested in joining OpenMoko as a software developer, please visit http://www.openmoko.com/contact-index.html and send us an e-mail.
* Or register some your project at http://projects.openmoko.org/
* Or simply join the Openmoko Community - more info here http://wiki.openmoko.org/wiki/OpenMoko:Community_Portal

=== Q: When and where can I buy a [[Neo1973]]? ===

A: The OpenMoko Neo 1973 is now sold out (11 Feb 2008). You should get the better [[Neo FreeRunner]] instead!

=== Q: When can I buy a [[Neo FreeRunner]]? ===

A: Since 4. July 2008 July on [http://www.openmoko.com/| openmoko.com]. Watch the [[OpenMoko:Community Portal|Community Portal]] and [[Community Updates]] for further updates!

=== Q: What are the new features that the Neo Freerunner have? ===

It retains many good features from the Neo1973 such as the very high resolution touch screen and integrated GPS unit.

It adds the following features
* WiFi - 802.11 b/g - for high speed internet
* Faster processor operating at 400Mhz (up from 266Mhz) - for faster operation
* * SMedia Glamo3362 Graphics Accelerator - for improved graphical performance
* 2 3D Accelerometers - the phone applications will know which way the phone is oriented
* 256MB Flash - larger memory to run bigger applications
* LED's illuminating the 2 external buttons on the phone

=== Q: How much? ===

A: Neo1973 (Internal code name GTA01B_v04): $300 for Neo Base, $399 for Neo Advanced. Available now. See [[Neo1973]] for what is included.

A: FreeRunner (Internal code name GTA02): $399 for FreeRunner, $99 for the debug board on [http://www.openmoko.com/ www.openmoko.com].

In Europe €350 (incl. vat.) for the FreeRunner on [http://www.trisoft.de/freerunner.htm Trisoft.de] or €299 on [http://www.pulster.de/index.htm?openmoko.htm Pulster.de].

=== Q: What can I do with the Neo1973? ===

A: For long answer see [[Developer preview]]

A: The Neo1973 is a Phase 1 phone and aimed at software developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release. Here are one developer's thoughts about the possibilities [http://blog.syntaxpolice.org/isaac/technology/linuxPhones.html]

Those interested should:

* Know that there will be a device with faster cpu, gsm system etc in the spring of 2008.
* Have fun hacking devices.
* Be able to find their way through prototype software and hardware without much documentation.
* Share the dream of a device powered by free software.
* Not expect a consumer-level device.
* Come up with new ideas for exploring the age of mobile computing.
* Have $300.

Ideally they also:

* Can spot bugs and submit patches.
* Love to cooperate with a community improving the software.

=== Q: What am I be able to do with the Neo Freerunner? ===

A: The Neo Freerunner is the first phase 2 (mass release) phone from the Openmoko project and is designed for everyday use by end users and continued software development and improvements by the Openmoko team and the Openmoko community.

A: The question is almost what can you NOT do with this phone - eventually there will be a huge range of free software applications allowing both end users and developers to get much more out of this phone than a standard "locked" mobile phone using features like the integrated GPS, bluetooth, wifi and accelerometers.

=== Q: Do I need the Neo 1973 Advanced (or in due course the Neo Freerunner Advanced)? ===

End users or power users should buy the "base" unit.

Software developers may wish to buy the "advanced" model.

With Neo 1973 Base or Neo Freerunner Base you can do:
* Kernel development.
* Application development.
* Updating u-boot (equivalent to PC BIOS) using a tested image.
* Replace a non-booting kernel and/or rootfs using [[Dfu-util]].

With Neo 1973 Advanced or Neo Freerunner Advanced you can additionally do:
* U-boot development.
* Use the kernel console.
* Unbrick your device if you flash a wrong or non-working u-boot image.

=== Q: I have a shipping related question ===

For Neo1973
* See [[SH1_FAQ|Shipment 1 FAQ]].

For FreeRunner
* See [http://www.openmoko.com/ openmoko.com]

=== Q: What does the [[Neo1973]] look like? ===

* See the original launch [[Artwork|artwork]]
* Collected images from google [[http://images.google.co.uk/images?q=neo+1973&ie=UTF-8&oe=utf-8&rls=com.ubuntu:en-GB:official&client=firefox-a&um=1&sa=N&tab=wi]]

=== Q: What does the [[Neo FreeRunner]] look like? ===

* It uses the same case and dimensions as the Neo1973 (as announced at CES Jan08)

=== Q: What else do I need to know? ===

* Both Neo 1973 and Neo Freerunner are tri-band GSM phones.
* The Neo Freerunner is expected to be offered in an 850/1800/1900MHz version for North America and an 900/1800/1900MHz version for the rest of the world.
* The Neo1973 is an 900/1800/1900Mhz version only and may not work well in some rural parts of North America.

=== Q: What are the benefits of an "open" phone over a "closed" phone ===

A: In a conventional closed phone, the handset maker and the mobile network operator work together to provide a service to you that best suits their business model. The capabilities of a modern smartphone equipped with GPS, Wifi and bluetooth are amazing and the result is that many features are "locked down" because they do not suit the network operator. Up until now it has been difficult to buy a phone on which you have freedom to install sofware which is not controlled by the network operators - [[Openmoko]] changes that!

A: A list of examples of "closed" behaviour has been started here - [[Problems of typical "closed" phones]]

==Software==

=== Q: Can the software do/connect to/... ===
A: Reviews of the latest "bleeding edge" daily builds of the OpenMoko software stack can be seen [[Snapshot_review|here]]

A: At the moment, the answer to many other questions is "no". The phone is at the moment a small linux box with a touchscreen, a working dialer and some prototype apps. Most do not function in any way that would be suitable for end-users. If you want to add a feature or application request, then look over the existing [[Applications]] and either add one, or add a feature request to the applications page.

===What software is on the phone?===
At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

=== Q: Is there description and list of OpenMoko software? ===

A: See [[OpenMoko]] and [[OpenMokoFramework]]

=== Q: Is it completely free software/open source? ===

A: User space GPS/[[Gpsd]] will use a binary plugin for [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] and [[:Category:Neo1973 Hardware#GSM.2FGPRS|GSM modem]] is separate subsystem connected to S3C2410 UART1.

There are legal reasons why it is not possible to provide Open Source software for GPS and GSM modules.

Otherwise it is completely free software. See [[MokoMakefile]] and [[Development resources]].

=== Q: How do I install and manage software on OpenMoko? ===

A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg

=== Q: How can I compile programs for the Neo1973? ===

A: See [[Toolchain]].

=== Q: Is there an emulator available for OpenMoko? ===

For a lot of testing and development work, you don't actually need emulation as you can run OpenMoko on a normal PC too. The emulators also aren't 100% accurate. That being said, there are several emulation options as described in the following.

====QEMU====
QEMU can now emulate the Neo1973 device. The [[MokoMakefile]] has support for automatically building, flashing, and running [[OpenMoko under QEMU|the Neo1973 emulator]].

*Ubuntu users can follow the instructions in [[Automatic_emulation_in_Ubuntu]]

*Users of other Linux distributions can try the following:
:"make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

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

====Xoo====
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

====Xephyr====
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===

A: This should get you started:
* [[Building_a_hello_world_application]]
* http://www.gtk.org/tutorial/

=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===

A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M6800 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.

The soon-to-be-released [http://www.palm.com/foleo/ Palm Foleo], which runs a Linux port developed by Palm Inc. independently of ALP, contains a PalmOS compatibility environment that runs PalmOS apps, supposedly all of them and supposedly seamlessly. Little is known about how it works but if it's not too kludgy it should run unmodified on any ARM linux. It is not known what license it will be distributed under.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

=== Q: Does it have Java? ===
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. This project supports OpenMoko.

=== Q: What are the relevant X11 details? ===

A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

=== Q: Does OpenMoko run on any other hardware? ===

You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. You may be able to run it on other [[OpenMoko-supported_hardware | mobile platforms]]

=== Q: Why do you not build on top of the Maemo platform instead? ===

While I can't speak for the OpenMoko team, it's worth noting that maemo is fixed resolution only. That will, I've heard, change in the future, but it hasn't yet. Maemo's current layout is also optimized for wide screens, not tall narrow ones. Most third party maemo applications that are out there will need to be modified to work at different sizes. Finally, a number of the software components of the Nokia 770 and N800 are not open source. --gopi

To add up on that, according to Nokia, Maemo is designed to bring the "Desktop" experience to an Internet Tablet. A lot of Desktop paradigms just won't work on a phone. However, we really share a lot of the base-technology (gtk, dbus, eds, gconf, to name a few) with Maemo, so we are definitely not a reinvent-the-wheel team.

=== Q: Will it be possible to use popular VoIP applications such as Skype on the OpenMoko platform? ===

A: Answer for the [[Neo1973]] - Perhaps. Hardware issues mean that it won't work well on the Neo1973. (the typical latency of GPRS is far too high). Also, Skype is a closed source application, which does not provide binaries that would be suitable to run on OpenMoko. Skype's vendor could of course choose to provide binaries for OpenMoko phones. However, many telephone providers' terms of service agreements preclude running VoIP over their baseline GSM service.

A: Answer for the [[Neo FreeRunner]]. Since it has WiFi the FreeRunner should be a good platform for VOIP use. Check for softphone apps ported to the OpenMoko distribution at the [http://projects.openmoko.org/ projects] page.

=== Q: Same question for Instant Messaging applications such as MSN Messenger? ===

A: Very probably. MSN is closed source and will only run where Microsoft wants you to run it. But there are many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [http://www.pidgin.im Pidgin, formerly called GAIM]. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==Neo1973 Hardware==

=== Q: Is there description of [[:Category:Neo1973 Hardware | Neo1973 Hardware]] ? ===

A: See [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

=== Q: What are the dimensions? ===

A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")

=== Q: How heavy is it? ===

A: 185g, (6.5 ounces).

=== Q: Does it have a camera? ===

A: No, see [[:Category:Neo1973 Hardware | Neo1973]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].

=== Q: Does it have Wifi? ===

A: The currently available [[Neo1973]] does not have WiFi. There was no suitable Wifi device available when it was designed. The next version will have WiFi. See also [[FAQ#USB]].

=== Q: Does it have bluetooth? ===

A: Yes! Bluetooth 2.0.

=== Q: Does it come with a stylus? ===

A: Yes, but there's no holder for it on the phone.

=== Q: Where are the buttons? ===

[[Neo1973 Power Button|The power button]] is a small circular button, just next to the USB connector.
[[Neo1973 AUX Button|The Auxiliary button]] is a rectangular button on the top left of the edge of the phone. (on black phones it looks just like an IRDA port).

=== Q: How do I input text? ===

A: Use provided keyboard app.

A: Use Bluetooth keyboard.

A: For more methods and ideas see [[Wishlist:Text_Input]].

=== Q: Can I record calls and/or play audio files in calls? ===

A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]

=== Q: What is the battery life? ===

A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

==== Q: What can I do with the USB port on the Neo1973? ====
A: Charge the phone, communicate with it over USB-serial, or USB-networking.

A: Plug external devices, such as wifi, cameras, or mass-storage devices in. The "Mass Market" version of the phone will have wifi integrated.

==== Q: What can't I do with the USB? ====

The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.

==== Q: Why is only USB 1.1 provided? ====

A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.

==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====

A:
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.

*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)
*This is because the host socket on USB hubs is not powered.

FIC product development is looking into providing something that
conveniently solves this problem.

The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)

One solution is a three headed cable.

One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.

The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.

For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.

==== Q: What are the details of the USB port on the [[Neo1973]]? How does it compare to USB On-The-Go? ====

A: The [[Neo1973]] will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

=== Q: Are there any LEDs on the Neo 1973? ===

A: The [[Neo1973]] P1/P2 will have no LEDs besides the screen backlight.

=== Q: Will a JTAG port be made available? ===

A: Included with purchase of The "Hacker's Lunchbox" (Advanced version).

There are [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connectors]] inside case in all versions and [[Debug Board|Debug Board v2]] (JTAG and serial console) in Advanced version. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.

=== Q: Will the JTAG interface that comes with GTA01 be compatible with GTA02? ===

A: Yes

=== Q: What can we expect in future versions? ===

A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. No details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense - announced by FIC in September.

==Networking/Connectivity==

=== Q: What kind of connectivity? ===

A: Tri-band GSM (commonly known as "European tri-band", 900/1800/1900 MHz), GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR, USB in all versions. WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===

A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== Q: What providers provide the GSM required for Neo1973? ===

A: See [[Neo1973 compatible cellphone providers]]

=== Q: Will OpenMoko "Just Work" with Mac OS X? ===

A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.

A: It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.

==Misc==

=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

A: Please reply UNDER post.

=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===

A: By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from OpenMoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom OpenMoko search engine] that is using [http://www.google.com/coop/ Google Co-op].

=== Q: how many dead pixels may the LCM have before calling it defect? ===

A: the answer for the display used in GTA01 and GTA02 is '2'

=== Q: Can I has some money for a Neo1973? ===

A: No.

=Historical=
The Neo1973 was last available in Febuary 2008. See [Ne

{{Languages|FAQ}}

[[Category:Information]]
[[Category:FAQ]]

Neo 1973 GPS

2008-07-09T19:01:19Z

Speedevil: /* GTA02 GPS */

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

Note that the GTA02 device contains u-blox ANTARIS 4 solution, you could find more hardware related information before GTA02 hardware page.

Assisted GPS performance requirement also defined in GSM/GPRS 3GPP TS 25.171, CDMA 3GPP2 C.S0036-0 

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

In the very early shipment to 50 Phase 1 developers, a binary-only program for talking to the the GPS was accidentally included
in /home/root/DM2/gps, (and presumably, the same binary would function on a P0 device).
This binary is called gllin and it is a oabi binary, i.e. it will only work in the 2007.1 Openmoko environment. There is now a eabi binary, which works with 2007.2.

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

For detailed GTA02 u-blox 4 GPS information, please check here: [http://wiki.openmoko.org/wiki/GTA02_GPS GTA02 GPS]

To turn on the GPS, echo 1 to the file /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

cat /dev/ttySAC1 will work fine.

Before getting a fix, the GPS spits out lots of "$GPTXT,01,01,01,NMEA unknown msg*58", though these stop once a fix is obtained.
A position without a fix looks like:
* $GPGGA,235946.99,,,,,00,00,5.0,,M,0.0001999,M,0.0020199,*57
One with a fix:
* $GPGGA,065852.00,5613.022527,N,00306.725890,W,1,05,0.5,158.0,M,0.277000,M,-0.010
0515,*7A

(central Scotland)

--[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

If you are having GPS problems with your freerunner, please document these on the page [[GPS Problems]].

In Openmoko projects, you could find a GPS test program that could provide graphical and text dump of GPS information. This project called [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
:* [http://wiki.openstreetmap.org/index.php/Rana Raná] is the new version of pyroute
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].
* [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].
* [[GPS Sight]], a popular Openmoko project under LGPL.
* [[Orrery]], an unpopular Openmoko project for displaying the night sky.
* [http://wiki.openstreetmap.org/index.php/Gosmore Gosmore] is a routing and viewer of OSM XML data such as the planet.osm.

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

Neo 1973 GPS

2008-07-08T20:34:35Z

Speedevil: /* GTA02 GPS */ add lines

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

Note that the GTA02 device contains u-blox ANTARIS 4 solution, you could find more hardware related information before GTA02 hardware page.

Assisted GPS performance requirement also defined in GSM/GPRS 3GPP TS 25.171, CDMA 3GPP2 C.S0036-0 

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

In the very early shipment to 50 Phase 1 developers, a binary-only program for talking to the the GPS was accidentally included
in /home/root/DM2/gps, (and presumably, the same binary would function on a P0 device).
This binary is called gllin and it is a oabi binary, i.e. it will only work in the 2007.1 Openmoko environment. There is now a eabi binary, which works with 2007.2.

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

For detailed GTA02 u-blox 4 GPS information, please check here: [http://wiki.openmoko.org/wiki/GTA02_GPS GTA02 GPS]

To turn on the GPS, echo 1 to the file /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

cat /dev/ttySAC1 will work fine.

Before getting a fix, the GPS spits out lots of "$GPTXT,01,01,01,NMEA unknown msg*58", though these stop once a fix is obtained.
A position without a fix looks like:
* $GPGGA,235946.99,,,,,00,00,5.0,,M,0.0001999,M,0.0020199,*57
One with a fix:
* $GPGGA,065852.00,5613.022527,N,00306.725890,W,1,05,0.5,158.0,M,0.277000,M,-0.010
0515,*7A

(central Scotland)

--[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

In Openmoko projects, you could find a GPS test program that could provide graphical and text dump of GPS information. This project called [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].
* [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].
* [[GPS Sight]], a popular Openmoko project under LGPL.
* [[Orrery]], an unpopular Openmoko project for displaying the night sky.
* [http://wiki.openstreetmap.org/index.php/Gosmore Gosmore] is a routing and viewer of OSM XML data such as the planet.osm.

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

Neo 1973 GPS

2008-07-05T15:24:46Z

Speedevil: /* GTA02 GPS */ correct oops

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

Note that the GTA02 device contains u-blox ANTARIS 4 solution, you could find more hardware related information before GTA02 hardware page.

Assisted GPS performance requirement also defined in GSM/GPRS 3GPP TS 25.171, CDMA 3GPP2 C.S0036-0 

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

In the very early shipment to 50 Phase 1 developers, a binary-only program for talking to the the GPS was accidentally included
in /home/root/DM2/gps, (and presumably, the same binary would function on a P0 device).
This binary is called gllin and it is a oabi binary, i.e. it will only work in the 2007.1 Openmoko environment. There is now a eabi binary, which works with 2007.2.

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

For detailed GTA02 u-blox 4 GPS information, please check here: [http://wiki.openmoko.org/wiki/GTA02_GPS GTA02 GPS]

To turn on the GPS, echo 1 to the file /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

cat /dev/ttySAC1 will work fine.

Before getting a fix, the GPS spits out lots of "$GPTXT,01,01,01,NMEA unknown msg*58", though these stop once a fix is obtained. --[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

In Openmoko projects, you could find a GPS test program that could provide graphical and text dump of GPS information. This project called [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].
* [http://svn.projects.openmoko.org/svnroot/openmoko-agpsui Openmoko AGPS UI project].
* [[GPS Sight]], a popular Openmoko project under LGPL.
* [[Orrery]], an unpopular Openmoko project for displaying the night sky.
* [http://wiki.openstreetmap.org/index.php/Gosmore Gosmore] is a routing and viewer of OSM XML data such as the planet.osm.

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

Neo FreeRunner Wifi

2008-07-03T16:59:11Z

Speedevil: english

To get wlan working on your Freerunner, you can follow these steps:

1. create and edit a suitable /etc/wpa_supplicant/wpa_supplicant.conf (use your favourite search engine to find the syntax)

2. execute `ifup eth0`

3. execute `wpa_supplicant -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf` (Add an & to run in the background)

4. get a IP via dhcp: `udhcpc eth0`

That's it, your wlan should now work!

Video Player

2008-07-01T14:51:26Z

Speedevil: /* GTA02/FreeRunner */

Not a proper 'app' page, just an overview of my understanding.
--[[User:Speedevil|Speedevil]] 14:44, 1 July 2008 (UTC)

----

Video is problematic on both GTA01 and GTA02 (freerunner) though for different reasons.

==GTA01/Neo1973==
On the minus side.
*The CPU is certainly not fast enough to decode 480*640 video.
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.
However.

On the positive side.
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.
*If not, then it almost certainly will be possible at 12fps.

==GTA02/FreeRunner==
On the positive side.
* The CPU is twice as fast.
* The Glamo chip can do scaling, rotation, this means that the CPU does not have to do this, and it's more flexible than simply setting the LCD to half resolution.
* The Glamo can decode mpeg-4.

===Negatives===
Unfortunately, the Glamo brings huge negatives, which may in some cases outweigh these.

* The bandwidth to it is only 7 megabytes/second, and this is shared with the SD.
* It can only decode mpeg-4, any other format will need to be decoded on the CPU, and pushed over the very slow bus.
* The 7 megabytes/second figure uses 100% of CPU. If you need 50% of CPU to decode video, then you only have 3.5 megabytes/second.
** It's not even this good, as you need to subtract IO to the SD card from the total bandwidth.

===Summary===
It should play easily mpeg-4 (640*480*15fps and 320*240*30FPS), however other formats will require transcoding.

-In common-

*Playing most very small - postage stamp - videos as are sent by many phones should be possible.
*4G of storage should give many hours of mpeg4 video, as the quality can be reduced somewhat without being visible on the screen.

=Reports of GTA01=
From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].

400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.

With sound, this drops to 18fps.

There are optimisations for mplayer that look promising to get 25fps with sound.

For switching between QVGA and VGA mode do the following with a compatible kernel:
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga
vice versa:
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3
taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html

To make your videos/DVDs neo1973 compatible use mencoder like this:
Find out the -vf cropping parameters with
mplayer input.avi -vf cropdetect
let it run a few seconds and insert the given cropping values into this command
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi
To encode a DVD first find out the -vf cropping parameters with
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000
let it run a few seconds and insert the given cropping values into this command
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.

To avoid console blanking type
echo -e '\033[9;0]' > /dev/ttyX
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.

To avoid kernel output in vt do
echo 0 > /proc/sys/kernel/printk

== Playback using 480x640 / 640x480 ==

To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32

Also working okay:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 352 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=200:abitrate=32

You can playback the file using:
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi>

You may also want to use:
-autosync 30 -vf scale -zoom -xy 640 -vf rotate=1

[[Category:Software]]
[[Category:Neo1973 Hardware]]

Video Player

2008-07-01T14:44:29Z

Speedevil: update to FR

Not a proper 'app' page, just an overview of my understanding.
--[[User:Speedevil|Speedevil]] 14:44, 1 July 2008 (UTC)

----

Video is problematic on both GTA01 and GTA02 (freerunner) though for different reasons.

==GTA01/Neo1973==
On the minus side.
*The CPU is certainly not fast enough to decode 480*640 video.
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.
However.

On the positive side.
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.
*If not, then it almost certainly will be possible at 12fps.

==GTA02/FreeRunner==
On the positive side.
* The Glamo chip can do scaling, rotation, this means that the CPU does not have to do this, and it's more flexible than simply setting the LCD to half resolution.
* The Glamo can decode mpeg-4.

===Negatives===
Unfortunately, it brings huge negatives, which may in some cases outweigh these.

* The bandwidth to it is only 7 megabytes/second, and this is shared with the SD.
* It can only decode mpeg-4, any other format will need to be decoded on the CPU, and pushed over the very slow bus.
* The 7 megabytes/second figure uses 100% of CPU. If you need 50% of CPU to decode video, then you only have 3.5 megabytes/second.
** It's not even this good, as you need to subtract IO to the SD card from the total bandwidth.

===Summary===
It should play easily mpeg-4 (640*480*15fps and 320*240*30FPS), however other formats will require transcoding.

-In common-

*Playing most very small - postage stamp - videos as are sent by many phones should be possible.
*4G of storage should give many hours of mpeg4 video, as the quality can be reduced somewhat without being visible on the screen.

=Reports of GTA01=
From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].

400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.

With sound, this drops to 18fps.

There are optimisations for mplayer that look promising to get 25fps with sound.

For switching between QVGA and VGA mode do the following with a compatible kernel:
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga
vice versa:
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3
taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html

To make your videos/DVDs neo1973 compatible use mencoder like this:
Find out the -vf cropping parameters with
mplayer input.avi -vf cropdetect
let it run a few seconds and insert the given cropping values into this command
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi
To encode a DVD first find out the -vf cropping parameters with
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000
let it run a few seconds and insert the given cropping values into this command
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.

To avoid console blanking type
echo -e '\033[9;0]' > /dev/ttyX
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.

To avoid kernel output in vt do
echo 0 > /proc/sys/kernel/printk

== Playback using 480x640 / 640x480 ==

To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32

Also working okay:
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 352 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=200:abitrate=32

You can playback the file using:
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi>

You may also want to use:
-autosync 30 -vf scale -zoom -xy 640 -vf rotate=1

[[Category:Software]]
[[Category:Neo1973 Hardware]]

User:Speedevil

2008-06-29T22:21:32Z

Speedevil: update mail

I lurk on #openmoko generally.
Currently involved in reinsulating my house, http://www.mauve.plus.com/walls/ so don't have much spare time. :(
openmoko@mauve.plus.com will reach me.

My paypal account is currently down, so I'm using do<something>@mauve.plus.com - contact me on IRC for the real one if you need it for some reason.

Of pages that I've largely written, I will tend to harshly edit down comments that in my view do not fit the style or are better off in another article, then note that on the discussion page.
If you have comments about me ripping your prose to shreds, or making something less clear, please note it on the discussion page, and if you feel strongly about it and I don't get back to you within a day or so, revert.

Neo FreeRunner Openness

2008-05-20T18:37:17Z

Speedevil: add comments on samsung SoC, GPU, and modem

__NOTOC__
__NOEDITSECTION__
{{gta02menu}}

Many people are more interested in getting a completely (and openly) documented hardware platform than in getting one with "just" all drivers under GPL. Why is this so? Just imagine an open source kernel which is released under a copyleft license which is incompatible to the GPL (like the OpenSolaris kernel). These poor developers would have to reverse engineer a so called "open platform" as they cannot use the available drivers and header files. If you are a GPL-is-the-only-true-license guy/girl: Don't be offended by this, it's simply about choice. :)

This page tries to give you an overview how open the GTA02 hardware is documented and where to get the documentation. Your help is needed! If you know anything which is missing just add it, if possible with a reference where the info is coming from.

{|border=1
!Component
!Name
!Openness
|-
|CPU
|Samsung S3C2442
|Docs available from Samsung, but not easily. Only after registering and qualifying. Here is a copy: http://www.elektronika.opatnet.cz/datasheet/U/um_s3c2442b_rev12.pdf
|-
|NAND flash
|Samsung?
|Standard [[NAND]] command-set.
|-
|GSM modem
|TI Calypso?
|Speaks standard protocols with proprietary extensions. Most of the proprietary extensions are present also in some BenQ and/or Enfora Enabler modems which have open documentation available on internet. See also [[GTA01 gsm modem]]. The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.
The legality of reading these files may vary according to your local laws, as may generating code from them.
|-
|Transceiver
|TRF6151?
|No interaction with software.
|-
|Analog baseband
|TWL3014?
|No interaction with software.
|-
|WiFi
|Atheros AR6K
|No documentation available! GPL'ed driver only.
|-
|Bluetooth
|Delta DFBM-CS320 Class2 Module using CSR BlueCore4?
|Documented at http://www.bluetooth.com/Bluetooth/Learn/Technology/Specifications/
|-
|GPS
|u-blox/atmel ATR0635
|http://www.u-blox.com/customersupport/gps.g3/ANTARIS_Protocol_Specification(GPS.G3-X-03002).chm
|-
|Graphic Accelerator
|SMedia 3362
|Documentation is only available under NDA. It has in the past been hoped that this would be rewritten in a form which would make it available to the community. This will not now happen, (according to Raster on IRC - a core graphics developer) due to funding and time constraints.
|-
|MicroSDHC
|?
|Connected to the SMedia 3362
|-
|LCD
|TD028TTEC1 module using a Toshiba JBT6K74 TFT LCD Driver Chipset?
|No open documentation available! GPL'ed driver only.
|-
|Touch Screen
|?
|Connected to the s3c2442 similar to GTA01
|-
|Vibrator
|
|Simple motor attached to the PWM output of the s3c2442
|-
|Sound Codec
|Wolfson Codec
|Full data sheet available at http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf
|-
|Sound Amplifier
|National Semiconductor LM4857
|Full data sheet available at http://www.national.com/ds.cgi/LM/LM4857.pdf
|-
|Power management
|Philips PCF50606
|Documented at http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf
|-
|Battery
|Proprietary
|-
|JTAG
|?
|Standardized, BSDL file for the CPU will hopefully become available
|-
|Case
|Proprietary
|Openmoko has released the CAD files for the case schematics. See the [http://downloads.openmoko.org/CAD/ CAD directory]
|-
|}

[[Category:Hardware Support]]
[[Category:GTA02 Hardware]]

Flashing the Neo 1973

2008-05-12T15:09:04Z

Speedevil: minor rewrite of caution on nand erase

{{Languages|Flashing openmoko}}
This describes how to update your Neo1973 to the latest software. We'll update the kernel, the root filesystem and optionally u-boot [[partitions]] in the internal flash memory.

{{warning|If you're updating u-boot and don't have a [[Debug Board]], you might render your unit unusable if the flashing procedure is interrupted}}

{{warning|If you have U-boot from before 2008 and upload a rootfs image that is smaller than the previous one, or if you have written to the rootfs, just flashing may not work - you may need to run a "[[Nand_erase|nand erase rootfs]]" before you then upload your rootfs (details [[Bootloader#Accessing_the_bootloader_prompt|here]]). Running "nand erase rootfs" before flashing a new rootfs, is quick and saves you the time of a second rootfs upload. Attention: If you [[Nand_erase|erase NAND]] without mentioning the partition to be erased, u-boot will be wiped out and the Neo will be bricked}}

== Files to download ==
{{Note|
* MacOS X users: please refer to [[MacOS_X]].
* Users without Linux please refer to [[No_Linux]] for the moment.
}}

The rootfs & kernel images you download need to match. The loadable modules for the kernel are in /lib/modules/ on the rootfs [[partition]] - if you get the wrong combination, you will get some error messages during bootup that it cannot access /lib/modules/x.y.z-moko123 - in this case swap either the kernel or the rootfs to match the other's version. Unfortunately the rootfs filename does not seem to tell what kernel version it is compatible with, you just have to try a few. '''NOTE:''' At least some combinations seem to boot up fine even if the module versions mismatch so be sure to check the console while it's booting after flashing.

The "moko123" in the error message example above indicates the openmoko patchset version.

Necessary files are at:
*http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D

*http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/?C=M;O=D (Daily unstable builds)

*http://buildhost.automated.it/OM2007.2/?M=D (Location of more current unofficial builds.)

A list of download locations can be found at [[Repositories]]. See [[Phase 1 Software Testing]] for a list of tested images.

Changelogs can be found at:
*http://cia.vc/stats/project/openembedded/.rss

*http://cia.vc/stats/project/openmoko/.rss

Get:
* [[dfu-util]] (the precompiled binary on http://buildhost.openmoko.org is for Linux/i386)
** (this is the part that runs on the PC, that pushes the files across the USB to the phone)
* openmoko-devel-image-fic-gta01-2007********.rootfs.jffs2
* uImage-2.6.21.*-moko*-r*_0_****_0-fic-gta01.bin
* for phase 0 (Bv03) phones:
** Tested by a few people: u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin MD5SUM: 60c5aeba1bd6642b05b3a5e6f2dafe83
** Tested by hrw: u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2062.bin MD5SUM: 716f1eba9b0f2be4a0a3be4a56724935
* for phase 1 phones, uboot update should not be necessary.

== Preparing the device for DFU mode ==

You'll need to boot your openmoko into uboot menu. To do this:

* Unplug all usb devices from the host.
* Hold the phone's [[Neo1973 AUX Button | AUX button]] and then press the phone's [[Neo1973 Power Button | POWER button]].
** You'll need to hold the POWER button for about 4 seconds before the device will turn on. Otherwise the screen will only flash white for a second and the phone won't power up.
* The u-boot menu should appear:
<pre>
U-Boot ..

=== BOOT MENU ===

BOOT
Set console to USB
Set console to serial
Power off
Boot from SD
Factory reset

Press [AUX] to select, [POWER] to execute.
</pre>

* Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

'''Note:''' If the bootloader remains inactive for about 30 seconds, that is no keypresses or no use of the serial console, the device will automatically power down.
You can prevent this by just pressing the AUX button every 30 seconds or so or by telling the bootloader to not exhibit this behaviour.
To do so, please connect to the bootloader:

<pre>
cu -l /dev/ttyACM0
GTA01Bv4 # setenv boot_menu_timeout 65000
GTA01Bv4 # saveenv
</pre>
For those that are unfamiliar with cu, to exit you need to press "~."

(You may have to install the uucp package to have access to cu, and maybe also "<code>chown uucp:uucp /dev/ttyACM0</code>" as root before it will work)

No further navigation is needed in u-boot - the device will automatically start flashing the images when told to do so by dfu-util below. After flashing all the files, you can choose the "Boot" option to boot the newly flashed stuff.

== Actually flashing things into the device ==

Double check that u-boot matches your hardware version. You'll probably only want to update u-boot if you have the [[debug board]] for fixing failed u-boot updates. You can also check the current [[partitions]].

Note: It may be necessary to run the application as root (at least in Ubuntu and Debian).

Note: In case there are more than one available usb devices use -d 0x1457:0x5119 option.

To update u-boot:

{{Warning|Do not update u-boot unless you have [[debug board]] or are really sure about what you are doing. Flashing a wrong u-boot image will brick your device! Note especially that image below is for GTA01B_v03, not GTA01B_v04

./dfu-util -a u-boot -R -D u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin}}

To update the kernel:
./dfu-util -a kernel -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin
Flashing the kernel will probably take less than 1 minute. If you're having trouble, you may want to compare the output that you see to a "known good" [[Flashing openmoko/Known good kernel flash U-Boot output | U-Boot]]/[[Flashing openmoko/Known good kernel flash dmesg output | dmesg]]/[[Flashing openmoko/Known good kernel flash dfu-util output | dfu-util]] output. The phone display should show "Starting DFU DOWNLOAD to partition 'kernel'.

To update the root filesystem:
./dfu-util -a rootfs -R -D ./Openmoko-devel-image-fic-gta01-20070501054014.rootfs.jffs2

Flashing the root filesystem will probably take around 13 minutes. Note that it can take over an hour if you are using a XEN VM for doing the flash.

Here is some "known good" output from [[Flashing openmoko/Known good rootfs flash U-Boot output | U-Boot]], [[Flashing openmoko/Known good rootfs flash dmesg output | dmesg]], and [[Flashing openmoko/Known good rootfs flash dfu-util output | dfu-util]]. The phone display should show "Starting DFU DOWNLOAD to partition 'rootfs'.

Notice that it's not normally necessary to update the modules anymore. It's just for people with special needs.

...now, you'll end up with system that boots, but does not see audio/SD card. You'll need to download corresponding modules.tgz and copy them over to openmoko. - UPDATE: GTA01 phones appear to not need this step, as long as you have installed a kernel that matches the version of the modules contained in the root image ('uname -r' will show the kernel version, and 'ls /lib/modules/' will show the modules that are present).

VERY IMPORTANT NOTE (I would consider that as a design flaw - either dfu-util should do it automatically): If you upload rootfs image that is smaller that previous one it won't work - you need to attach to the u-boot bootloader, erase NAND first and then upload your rootfs:

<pre>
cu -l /dev/ttyACM0
GTA01Bv3 # nand erase rootfs
</pre>

Old versions of u-boot are buggy: You may have to press the AUX button every 25 seconds or so to prevent the phone from going to sleep while being flashed. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase rootfs.

Good luck!

== Where to go from here ==

So, now you have one of the more recent kernel and rootfs images, or one of the (semi)official ones, whats next?

You probably want to set up [[USB_Networking]] and then configure your Neo1973 some more.

Do not forget to update your Neo1973 using

ipkg update && ipkg upgrade

and have a look at additional ipkg [[repositories]].

== Troubleshooting notes ==

If you're facing errors in seemingly random places during the flashing of images, most likely the USB hub or cable through which your Neo1973 is connected is of too poor quality. It is recommended that you always connect the phone directly to the host when using dfu-util.

If dfu-util reports a message like the following, before it starts flashing:<pre>
Resetting USB...
not at least 2 device changes found ?!?
Lost device after RESET?</pre> just retry the command - it should work on a second run.

This message can also occur if you connect the usb cable before you are in the bootloader menu. You must carefully follow the sequence described at the beginning of this article and not connect the USB cable too early.

dfu-util does not seem to be able to download files if run from linux running under
VMWare on a Windows OS host.

See other notes on [[Dfu-util]] page.

[[Category:Software]]
[[Category:Applications]]
[[Category:Openmoko]]
[[Category:Guides]]

Hardware:Neo1973:Alternate Cases:Camera

2008-05-09T11:53:23Z

Speedevil: /* Materials */ delete comment about I2C cameras - the image does not come out over I2C in any of this class of cameras.

Alternate case for the Neo1973, with <strike>rear-mounted</strike> camera module.

==Concept==
A flexible phone is desired that meets most users needs. Camera module should be easily installed or removed (and left in the car) for people that are unable to take cameras into work.

=== cs mount camera ===
* allows use of any standard cs mount (or other lenses with adapters) for superior optical focus & zoom
* cs mount is used because it can be converted to use c mount lenses with a 5mm extension tube
* surface of focal plane array is 12.52mm below top of surface (requiring less room than c mount or many other standard lenses)
* module faces can be exchanged to allow operation in either camera or video-conferencing mode
* lens can easily be unscrewed, converting the image sensor into a useless memory, and replaced with a c/cs mount cap. -- This could disable camera & allow people to bring the phone into work (or you could just remove the entire module)

A strong LED could be used as a close range flash. An ambient light sensor could automatically control this function. This could also be used as a torch.

==Rendered images==
=== cs mount camera (also works with c mount lenses) ===
[http://www.likeasecret.com/Neo1973/Neo1973-Exp_CamCS.mov Neo1973 cs-mount Camera Expansion Module Quicktime rendering] 
[[Image:Neo1973-ExpCamCS.png]]

==3D model==
=== cs mount camera ===
[http://www.likeasecret.com/Neo1973/Neo1973-Exp.aoi Neo1973 Art of Illusion 3D Model] - Not fully accurate, just an artistic concept.

==Materials==
* 1 Camera with about 2MP or more for making pictures
* 1 Camera for video conferences.
=== cs mount camera ===
* Aluminum top front of case cover could allow 1" x 32tpi lens mount hole (3.8mm threaded down from surface) made directly into cover.

==Processes==
Stereolithography

==Components==
Camera module with protection 
At least 2 Mpx.

==Interest==
Leave your nickname here if you are interested in having one made. This is not an order form, but is intended to gauge interest before effort is expended designing the case. 

#[[User:changzer|changzer]] maybe it could look nicer than that, but anyway, a camera would be so sweet on this phone
#[[User:Bootlessjam|Bootlessjam]]
#[[User:Diatessaron|Diatessaron]]
#[[User:Thomas Mathiesen|Thomas Mathiesen]]
#[[User:Gizmhail|Gizmhail]]
#[[User:Fisticuffs|Fisticuffs]]
#[[User:Daniel|Daniel]]
#[[User:Deedend|Deedend]]
#[[User:Aztlek|Aztlek]]
#[[User:Mikesd|Mikesd]]
#[[User:Filippo|Filippo]]
#[[User:Beady|beady]]
#[[User:Wvrn|wvrn]] -- A camera is the only thing I am waiting on to buy this phone
#[[User:yvanxxx|yvanxxx]]
#[[User:amarov|amarov]]
#[[User:cedel|cedel]]
#[[User:gwylim|gwylim]]
#[[User:Massa|Humberto Massa]]
#[[User:hhf423|hhf423]]
#[[User:Fursund|Fursund]]
#[[User:Bubbi|Bubbi]]
#[[User:Drizzt|Drizzt]]
#[[User:Pajamabama|Pajamabama]]
#[[User:vozka|vozka]]
#[[User:dlejeune|dlejeune]]
#[[User:AnyWare|AnyWare]]
#[[User:kresp0|kresp0]]
#[[User:sin|sin]]
#[[User:DjAlxor|DjAlxor]]
#[[User:Kf|Kf]]
#[[User:Kylegordon|Kylegordon]]
#[[User:Oatty|Oatty]]
#[[User:nericastillogioleo|nericastillogioleo]]
#[[User:Fradeve11|Fradeve11]]
#[[User:solid|solid]] -- A camera is the only thing I am waiting on to buy this phone. [UPDATE]I posted this comment several months ago. My first generation razr is gimping along. The exterior screen is completely busted and the lcd looks like a purple blob. I am holding off on buying a new phone until I can get a smart phone that replaces all the personal gadgets I have to carry. I need a phone that is a personal music player,a camera and a phone. Having a phone that is deficient in any of the above functions makes it less than smart. I am running out of time. My phone is in worst shape every day. Please just tell us there is a camera in the works, Otherwise I will be buying a non-linux smart phone.
#[[User:Globbi|Globbi]]
#[[User:Madoon|Madoon]]
#[[User:Thomasgruebler|Thomasgruebler]] -- 3MP would be cool
#[[User:Blastur|Blastur]]
#[[User:Tommiku|Tommiku]] -- A camera is the only thing I am waiting on to buy this phone
#[[User:ShakataGaNai|ShakataGaNai]] — it would be nice option to have
#[[User:Bugmenout|Bugmenot]] -- The finishing touch to make it the perfect phone :)
#[[User:rydell|rydell]] -- Definitely the only missing feature! (And a near-critical one)
#[[User:PrtSoftware|PrtSoftware]]
#[[User:bob127|bob127]] -- 3MP would be really nice, I'm also a developer for a phone-related company, I could recommend this phone if it has a camera.
#[[User:Z|Z]] -- Our company would like to develop applications for this phone, the only thing that's stopping us is the lack of a camera
#[[User:dyous87|dyous87]] --A camera would make this the perfect phone for me and I would surely buy it.
#[[User:Massi|Massi]] -- 3MP would be cool
#[[User:jcdemay|jcdemay]] -- a missing feature, don't care if it's not a great one, just need one ;)
#[[User:pokazene_maslo|pokazene_maslo]] -- with flashlight
#[[User:Jackcday|Jackcday]] -- I think it needs a camera, would be great if it could have a very high MPX camera with good software so you could use it as a proper camera.
#[[User:flexd|flexd]] -- This would be excellent for a idea of mine, camera + gps + wifi/gprs/3g/edge fun! :)
#[[User:Duker|Duker]] Would be awesome, especially if the camera (lens component) were removable for those pf us who can't have cameras at work (or court)
#[[User:PipBoy2000|PipBoy2000]]
#[[User:Merire|Merire]] I really want this phone, but I'm not gonna buy one if I can't get a cam.
#[[User:Totoro|totoro]]
#[[User:bacardi55|bacardi55]]
#[[User:jplaville|jplaville]]
#[[User:v0n0|v0n0]]
#[[User:massoo|massoo]] -- A Camera integrated is really cool which will enable to have unified personal gizmo.
#[[User:conbart|conbart]]
#[[User:calavicci|calavicci]] Like others, a camera is all I need to buy the phone.
#[[User:methril|methril]] It's an usefull extra feature.
#[[User:yorick|yorick]] The lack of a camera is a very big disadvantage of this phone (compared to a HTC P3600 for example)
#[[User:Yota_VGA|Yota_VGA]] Absolutely needed!
#[[User:Treviño|Treviño]] A phone doesn't need a camera, but it could be useful to grab fun moments!
#[[User:Daverix|Daverix]] My mobile is the only thing a use to take pictures!
#[[User:snizfast|snizfast]] Would also like a flash unless its good at night
#[[User:oisinmulvihill|Oisin Mulvihill]] I second the 3MP camera and gps so you could geo-tag where the pictures are which is very handy when you want to get back to an interesting place you've come across.
#[[User:dborba|dborba]] 3MP would be ideal.
#[[User:gumpish|gumpish]] -- A camera is the only thing I am waiting on to buy this phone. Every day I pray for the sanity of the development team and that they will realize that any phone that costs over $100USD and doesn't have a camera is worse than useless!
#[[User:Martix|Martix]]
#[[User:Mibo|Michal Bořek]]
#[[User:Setr|Setr]]
[[Category:Neo1973_alternate_cases]]

Wishlist/Camera

2008-05-02T14:52:50Z

Speedevil: /* Use cases that can be satisfied with a VGA fixed-focus or macro camera. */ add stuff

{{Hardware Wishlist}}

=== General Desired Uses/Functionality ===
See [[Hardware:Neo1973:Alternate_Cases:Camera | Alternate Cases:Camera]] for phone case suggestions.
==== Use cases that can be satisfied with a VGA fixed-focus or macro camera. ====
* Take pictures of items in shops, along with their price labels. For easy comparison shopping without having to write.
* Take pictures of accidents, to ease insurance claims. (accelerometer or GPS logs may be of use too)
* Reading barcodes, or 2D barcodes. For example to enable automatic ordering as you use barcoded products.
* Scanning Barcodes.
* Scanning 2D barcodes.
* Photograph positions of hardware when disassembling.
* Seeing over tall fences.
* Seeing into confined access spaces - in some cases an LED flash would be required.
* Adding thumbnail pictures to contact lists.
* Taking pictures with the GPS position logged, with [[Openstreetmap]] to help with mapping or Upload to Google earth.
* Gesture interfaces.
* Sensing position using external lights, such as the [http://www.wiili.org/index.php/Wiimote Wii remote] does with the sensor bar.
* Capturing business card images for OCR.
* General OCR (higher res is better).
* Sending photos directly from camera to email/web without internet connection via MMS, etc.
* Taking pictures of drunk people, a system that allows near-instantaneous grab phone, take picture interaction

==== Use cases that require more specialized lenses, sensors, or hardware. ====
* Printable photos. (that would be one huge device!!!)
* Optical Zoom to distant objects.
* Low light photography.
* Astrophotography (alternatively and even better is to use an external USB Astro Web Cam, see end of article).
* Quality web-page photos.
* HDR Photography
* Principal 5MPixels camera and secondary camera for video-conference.

=== Camera interface ===

The [[Neo1973_Hardware#Processor|current Neo1973 processor]] does not have a camera interface. A chip with the [http://www.mipi.org/ MIPI] Camera Serial Interface (CSI-2) might be used as a future proof solution. The standard is available to companies who have joined the alliance.

A chip that complies to the open [http://www.smia-forum.org/ Standard Mobile Imaging Architecture (SMIA)] Compact Camera Port (CCP2) serial interface may be (more) desirable. The [http://www.framos.de/www.dir/en/hersteller/micron/sensors/image/prod.dir/2286/index_en.html Micron MT9D012] is a 2 Megapixel chip and one of many that complies to these standards.

There are [http://www.micron.com/products/cmos/ 3.1, 5 and 8 Mega Pixel chips] available as well but I don't know if they comply to the above standards. Either way a 2 Mega pixel chip would be basic by the time it was ever implemented into a newer model.

===Liquid Lens camera===
* A [http://www.varioptic.com/en/products/products01.php Liquid Lens] camera for small, low power, electronically controlled autofocus. Also available as part of an SMIA compatible camera module!

===Telescope===
* A removable [http://mobile.brando.com.hk/MobilePhoneTelescope-Nokia.php telescope] or telephoto lens.

===Tripod===

A tripod socket would make a camera more usable.

===Interface to external camera===
Even if Gen1 Neos have no camera, it would be nice to get interfaces with external cameras to allow applications like GPS tagging of photos, barcode reading, OCR, and sending photos directly to internet. Are there plans to write software to interface with cameras directly via USB? Bluetooth? WiFi?

And even if a future version of Neo gets a build in camera it would be nice to connect a external camera via USB. For example the Astrocam Philips ToUCam SPC 900NC. This webcamera has a CCD chip (not CMOS) and is available with a adapter for telescopes (german Website: http://www.teleskop-service.de/VideoCCD/philips/philips.htm). A Neo will be a practically way to collect photos from the telescope (no need for a laptop). The image processing can be done later on a PC or on the Neo itself (if the Neo have enough arithmetic performance for the needed processing).

===Browser Implementation===

A way to take a photo of a web addess (from a poster, etc), OCR it, and automatically open the web address in the browser

===Swivel Camera===

It would be nice if the integrated camera(with LED/flash) could swivel from front to back. That way the same camera could be used for taking pictures and video conferencing. Instead of using 2 cameras.

===USB-Stick camera===
Maybe a small camera like this [http://www.akihabaranews.com/en/en/news_pics/12994/Volvox_3.jpg]
Since we don't have powered usb, maybe we can include a AAA battery or something

Neo FreeRunner Hardware

2008-04-25T01:21:31Z

Speedevil: /* I2C Devices */ grammar

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



[[Image:Gta02a5 pcba cs.JPG|thumb|400px|display (top) side NOTE: GTA02 A5 PCBA Component Side photo]]
[[Image:Gta02a5 pcba ps.JPG|thumb|400px|component (back) side NOTE: GTA02 A5 PCBA Print Side photo]]
[[Image:GTA02 A5 PCB CS.jpg|thumb|400px|component (back) side NOTE: GTA02 A5 PCB Component Side photo]]
[[Image:GTA02 A5 PCB PS.jpg|thumb|400px|component (back) side NOTE: GTA02 A5 PCB Print Side photo]]

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

Detail hardware component selection can be found below.

=Features=
*Display- Topply o2.8, 480 x 640 pixels, VGA, 200 NIT minimum, resistance type touch

*User Interface Navigation- Touch screen on LCD, 2 control “buttons”, 1 Power button, 1 Aux for 911 emergency call

*Built-in 802.11b/g Radio (Atheros chipset AR6001 Flash version)

*Built-in Bluetooth 2.0 + EDR (CSR and support PCM audio , BC4 frimware version)

*Built-in 2D/3D graphics acceleration chip (S-Media 3362)

*2 built-in Tri-Axis sensor (ST accelerometer LIS302DL)

*Built in GPS Radio – -130 dBm with internal antenna, -157 dBm tracking on chipset specification, TTFF under 40 seconds with -130 dBm signal strength, and tracking (u-Blox)

*Antenna – Specialized antenna for best in hand hold GPS, GPRS and Wi-Fi/Bluetooth performance are required, -105dBm on receiving, Tx 30dbm+2 on GSM

*External Antennae – MMCX GPS connector

*GPRS Radio –GSM/GPRS radio. A Pre-PTCRB certified module will be preferred

*Linux – Linux kernel 2.6.24 or later OpenMoko kernel

*USB - Client and Host mode switch-able (to be used for software downloading), provide host 5v power

*Power- Normal mode power will be via 1200 mAh battery with built-in coulomb counter, could charge via specialized charger. Internal Lithium Ion or Lithium Polymer battery will keep device in standby mode. Battery life (Approximation/Ideal Target) Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 3-4 hrs(GSM)

*LED- LED indicator under Aux/Power button key

=Hardware Specification=
===Hardware Electrical===

*400/500 MHz Samsung 2442B Processor/SOC (400 minimum)
*Boot code in NAND FLASH or 2MB NOR FLASH (optional design)
*128 MB SDRAM total, 64 MB CPU internal, 64 MB external
*256MB NAND Flash MCP package.

=== Display ===
*Topploy VGA ; 2.8” diagonal, 480 x 640 pixels, 16 bit color depth
*Transmissive display: good readability in high ambient light is essential
*White LED backlight. Required brightness is 200 NIT minimum.
*Resistance type touch panel.

=== WiFi 802.11 b/g transceiver ===
*Must have GPL support source or GPL compatible policy
*TX power at 11 Mbps: 13 dBm minimum
*RX sensitivity at 11 Mbps: -89 dBm desired, -83 dBm minimum
*AP mode desirable, not required
*WEP and WPA supported
*Atheros preferred because it's GPL policy

=== Serial interfaces (UART) ===
*Three serial interfaces are required
*Console
*A-GPS or GPS
*GSM/GPRS

=== Accelerometer ===
* 2x accelerometer required
* Could support interrupt while suspend or power save mode
* 3 axis sensing

=== A-GPS ===
*GPS chipset receiver and antenna
*Sensitivity at Antenna port: -157 dBm tracking on chipset specification
*LNA and SAW filter for maximum interference protection
*Cold start time to first fix: 40 sec typical at -130 dBm, 60 sec max
*Must support GPL for Assist-GPS function with open API
*Industry quality GPS
*Could fit in GTA01 GPS area on the PCB

=== GPS Antenna Performance ===
*Antenna is passive and internal; 15 mm x 15 mm ceramic patch is nominal design
*Antenna LNA and SAW filter are required to meet GPS performance
*15 mm square ground plane (minimum 1 mm ground border around patch) (TBA)
*There will be one external GPS antenna connector (MMCX)
*C/N ratio should higher than 35 on production testing

=== Buttons ===
*Touch screen over LCD is primary data entry mechanism
*Two “hard” buttons: Power button (on side of Neo1973) is a mechanical switch actuated by a plastic pushbutton in a hole in the housing. Aux (911) button on the top of the device, All two of these buttons, when pushed by the operator, are binary inputs (on/off or pressed/not pressed) to the software. The effect of each button is determined by the application software in the device
*Buttons may need to be backlit
*50000 cycles on hardware specification

=== Sound outputs ===
*Speaker in box (need good volume and acoustic behavior innoise environment)
*Audio is monophonic*Max volume: 100 dB at 5 cm to assure good performance in environment.
*Support earphone with mic by jack

=== Power Design Requirements===
*Software based power management unit preferred
*NXP PCF series preferred
*Need support charge from USB function
*Need support powered by USB function
*Power switch: Neo1973 will have a power switch, for power on/off and suspend
* Power/Aux switch must be backlit
*Switch controls whether device is running or suspended by presses of the switch
*Switch does not shut off the power; it only suspends/resumes the device
*Internal Li-Ion or Li-Polymer battery is included. This battery supplies standby power to the device eliminates the rebooting of the device when local power is again reapplied. Battery is 1200 ma-hr.
*Battery life (Approximation) Ideal/Target Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 4 hrs(GSM)
*Estimated current draw for the entire device when in suspend mode (and ALL peripherals are turned off or set for deep sleep) is <5 mA at 3.6 volts (Li-Ion terminal voltage).
*GSM module deep sleep(alive and keep contact with base station) stage should take less than 8mA
*Battery will reach half capacity (~600 mAh) with 500 charge-discharge cycles. This will occur in less than 2 years of daily service.
*When powered continuously, Neo1973 must suspend (to low power mode) based either on observed low battery voltage condition or a configurable time delay.
*Neo1973 must monitor battery status while suspended and resume automatically if the charger is inserted.
*Primary power connection: 1200mAh battery
*USB charger have ID pin 47.5k pull down for Openmoko identification
*Indicators: an LED indicator visible from the side of the unit will illuminate when charging or have missing incoming call

=== GSM/GPRS ===
*850/1800/1900 and 900/1800/1900 MHz bands must be supported
*Design should allow for multi-band version (850/900 MHz)
*Module based GPRS transceiver could meeting PTCRB and appropriate FCC certifications. It preferred that the module be pre-certified with PTCRB or OTA test
*FCC/CE certification required for GSM/GPRS part

=== GSM-GPRS Antenna Performance ===
*-105 dBm receiving on each channel (GSM/PCS)
*30+2 dBm transmission on GSM channel

=== Wi-Fi Modules ===
*Must support GPL driver
*Atheros AR6k preferred
*Flash version required

=== Wi-Fi Antenna Performance ===
*The Wi-Fi antenna with TX 13 to 15 dBm
*RX -89 to -83 dBm @802.11b 11Mbps or an equivalent performance antenna

=== Bluetooth ===
*CSR BC4 or later solutions

=== USB ===
*Neo FreeRunner GTA02 will have USB, client/host. Using USB 1.1
*Could provide USB host 5v power
*Could be powered by USB

=== Microphone ===
1 microphone is in the device

=== Firmware Image ===
*Using Linux 2.6.24 or later
*Could support boot from NAND or Boot from NOR
*Shipping image should come with basic phone function
*Could do full firmware upgrade by USB cable

=== PSN ===
*Device will have a PSN (product serial number) printed on the product label and machine readable in system NAND memory

=== IMEI ===
*Production phase should have IMEI code written

= Package Specification =
*Weight: ~150 grams with battery.
*4 in 1 laser pen passed RoHs and safty regulation for laser equipment safty
*1x 512MB microSD Card (SanDisk/Transcend)
*1x USB cable Standard A to mini-B connector
*1x 1200mAh smart/gauge battery
*Quick start guide
*5v USB power cord w/100-240 switchable power plug
*Safety card, warranty card
*Package could pass 1m to 1.5m drop test
*AC USB charger,100v-240v, Passed UL and all required safety regulation
*Must pass FCC/CE certification
*Must pass NCC certification for Taiwan import regulation
*RoHS Compatible
*WEEE Report required

= Life Cycle Specification =

=== Product Life ===
The product is designed to last a minimum of 2 years.

=== Operating Temperature ===
*Target operating range is –10°C to +60°C

=== Storage Temperature ===
*-15 deg C to +70 deg C

=== ESD ===
The device can withstand a 4.0kV contact discharge and 8.0kV air

=== Drop test ===
Should pass 1m direct drop to concrete ground or 1.5m on slide with carpet

= GTA02 Hardware Component Selection =

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

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

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 Samsung SC32442B]
* User Manual: FIXME
* Core: ARM920T
* Instruction Set: ARMv4 (Android ''currently'' requires ARMv5)
* Built-in 64MB SDRAM
* Built-in 256 MB NAND
* Could run at 500Mhz
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt 
* Evaluation board: [http://www.meritech.co.kr/products/product_view.php?num=52 S3C2442 EVB]

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

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

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

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

==== NOR Flash ====

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

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

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

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

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

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

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

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

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

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

== AGPS ==
u-blox ANTARIS 4 chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
* Driver: none needed, talks standard NMEA
* u-blox Antaris 4 Protocol [http://www.u-blox.com/customersupport/antaris_doc.html Protocol download page]
* ATR0635 Datasheet: [http://www.u-blox.com/products/Data_Sheets/ATR0630_35_SglChip_Data_Sheet(GPS.G4-X-06009).pdf u-blox ATR0635] 

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

== Graphics/3D Acceleration ==

Smedia Glamo 3362.
* Homepage: http://www.smediatech.com/product3362.htm
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC)
* Connected to: S3C2442 Address/Data bus 

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

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

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

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

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

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

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

== WiFi Module==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Case ==
The new case for the FreeRunner is all black, as seen on the front page on the wiki.
Source: Mickey on IRC
=Accessory=

== Stylus ==

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

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

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

== microSD Card ==

GTA02 should comes with one of following microSD card

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

== Charger ==

AKII Technology Charger

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

= History =

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

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

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

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

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

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

== GTA02v4 ==
Mass production release candidate version 1

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

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

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

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

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

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

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

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

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

= Debug Board =

== Debug Board Connector definition ==

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

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

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

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

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

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

= Certification =

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

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

[[Category:Hardware ]]
[[Category:GTA02 Hardware]]
[[Category:Hardware Support]]

Neo 1973 hardware

2008-04-24T20:12:57Z

Speedevil: /* Debug Connector */ update with information on GSM pins from mailing list.

[[Openmoko]] is a software distribution stack that sits on top of a [[hardware]] platform. The [[Neo1973]] phone is the first hardware platform to take advantage of Openmoko. You can find specifics of the [[:Category:Neo1973 Hardware | Neo1973 Hardware]] by reviewing this introduction page and the pages in the category as shown at the bottom of this page.

'''Note that this page is about the first Openmoko phone which is now discontinued. See details on the second Openmoko phone at this page - [[Neo FreeRunner GTA02 Hardware]].'''

[[Image:Gta01b v3 top.jpg|thumb|400px|display (top) side]]
[[Image:Gta01b v3 bottom.jpg|thumb|400px|component (back) side]]

==User experiences of Phase 0 hardware==
[[Wishlist:Neo1973_P0_Review]]

==User reports of robustness==
User experiences - drops onto concrete - ... [[Neo1973 Robustness]]

== Physical Dimensions ==
* 120.7 x 62 x 18.5 mm (4.75 x 2.44 x 0.728 inch)
* 184 +/- 5 g (6.5 ounces)
* For the purposes of acquiring/cutting a properly sized screen protector, the display hole of the case is about 45 x 59 mm, while the top cover internal frame can house up to a 53 x 74 mm protector; sizes much larger than the display hole would obviously necessitate removing the front cover for installation.
* A Useful size comparison between the Neo1973, iPhone, Motorola A1200 and the SEM600i can be seen at [http://www.sizeasy.com/page/size_comparison/5512-Neo1973-vs-Apple-iPhone-vs-M600i-2-vs-A-1200 sizeasy]

== Main components ==
=== Processor ===
The main Processor (CPU) of the Neo1973 is a Samsung S3C2410AL-26 (Capable of running up to 266 MHz)

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2410 S3C2410.htm]
* User Manual: [http://www.samsung.com/global/business/semiconductor/productRightMenuDown.do?doc_file=26537 2410UserManual.pdf]
* Core: ARM920T
* Instruction Set: ARMv4 (Android ''currently'' requires ARMv5)
* BSDL File: [http://www.samsung.com/global/business/semiconductor/productRightMenuDown.do?doc_file=26554 S3C2410_BGA_BSDLJTAGFILE.bsd]
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA01Bv4/gpio.txt

=== Flash ===
64MB Samsung NAND flash (K9F1208U0B) attached to S3C2410 NAND controller.

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=158&partnum=K9F1208U0B]
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/NANDFlash/SLC_SmallBlock/512Mbit/K9F1208U0B/ds_k9f1208x0b_rev03.pdf]
* Connected to: S3C2410 NAND controller

This is the only flash memory in the device. The S3C2410 boots directly from nand, using the [[S3C2410 Steppingstone]].

We only use free software, no proprietary flash file systems. For a full description of how it is used, see [[NAND bad blocks]]

=== RAM ===
128MB SDRAM (2x Samsung K4M511633C) attached to S3C2410 SDRAM controller
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M511633C]
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M511633C/ds_k4m511633c.pdf]
* Connected to: S3C2410

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

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

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

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

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

=== [[Hardware:AGPS|AGPS]] ===
Hammerhead PMB 2520 AGPS from Global Locate.

* Product Homepage: [http://www.globalocate.com/SEMICONDUCTORS/SEMI_HAMMER_Frameset.htm Hammerhead]
* Connected to: S3C2410 UART2 (full-uart, RxD, TxD, CTS, RTS) /dev/ttySAC1 in userspace
* Driver: Implemented as a binary with NMEA output suitable for the gpsd daemon ([[gpsd]])
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch
* Externally-accessible GPS antenna connector of type MMCX

The binary driver is available - see [[GLLIN]].
Efforts to reverse engineer the protocol are partially detailed in [[Hammerhead/Protocol]], these have stalled since the announcement that [[FreeRunner]] will use a different GPS.

=== microSD-Card ===
The Neo1973 has one microSD aka Transflash slot.
It supports SDHC. MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].
* Connected to: S3C2410 MMC/SD controller
* Mounted to: /media/card
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c_mci.patch
* [[Supported microSD cards]]
* Specifications: [http://www.sdcard.org/confirm/confirm_memorycard.aspx SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]

=== LCD Module (LCM) ===
This is a 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 toppoly (tpo) TD028TTEC1 module (283 DPI), using a Toshiba JBT6K74 TFT LCD Driver Chipset.
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch
* Connected to: S3C2410 Display Controller and S3C2410 SPI Interface channel 1
* Backlight controllable via /sys/class/backlight/gta01-bl

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

==== Stylus ====

Seemingly identical to [http://cgi.ebay.com/4in1-PDA-Stylus-LED-Light-Torch-Laser-Pointer-Pen-h7_W0QQitemZ280089656134QQihZ018QQcategoryZ48677QQrdZ1QQcmdZViewItem this one on ebay]

=== Bluetooth ===
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4 (V2.0+EDR).

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

=== Vibrator ===
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch
* Connected to: S3C2410 GPIO
* Controllable via /sys/class/leds/gta01:vibrator

=== USB Host ===
The USB Host controller is inside the S3C2410
* Driver: Stock Linux kernel ohci_hcd

=== USB Device ===
The USB Device controller is inside the S3C2410
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use
* 1200mAh lithium battery charges when connected to powered host.
* Mini-B connector [http://www.cypressindustries.com/enlarge.asp?Img=products/images/ccmusbb-32005-601.gif this one].
* This can be used as a USB host: [[Neo1973_USB_host]]

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

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

==== Wolfson Codec ====

''Main article: [[WM8753]]''

There's a [[WM8753]] Wolfson Microelectronics ''codec'' (This is not a "smart" codec that can interpret MP3/... it is a simple dumb "sound card".

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

* Product Homepage: [http://www.national.com/pf/LM/LM4857.html LM4857.html]
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4857.pdf LM4857.pdf]
* Connects to: S3C2410 I2C (Control)

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

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

Pinout: [http://lists.openmoko.org/pipermail/community/2008-March/013791.html]

<pre><nowiki>
base = ground
speaker left (internal impedance 33R) to ground. (+jackinsert detection)
speaker right (internal impedance 33R) to ground.
tip = mic electret condenser type, to ground.
bias (power for mic) 2K2 from +3.3v(wolfson codec)
(+HoldButton shortcircuit to ground)
</nowiki></pre>

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

=== Power Management ===
A Philips PCF50606 is used for [[Neo1973_Power_Management|power management]].

* Data Sheet: [http://www.nxp.com/acrobat/literature/9397/75009763.pdf PCF50606/605]
* User Manual: [http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf pcf50606.pdf]
* Connected to: S3C2410 via I2C, client address is 0x08.
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-pcf50606.patch

=== Battery ===
The [[Neo1973 Battery]] is compatible with a Nokia BL5C battery.
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.

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

=== Alternate cases ===
A number of alternate case designs have been suggested and requested.

[[Neo1973 case schematics]]

[[Alternate Neo1973 case designs]]

== History ==
=== GTA01 ===
This is the most simple, non-bluetooth version of the prototype.

==== GTA01v3 ====
First generation of prototypes that was given to internal OpenMoko software developers.

Unfortunately not useful at all due to non-working touchscreen.

* ATAG_REVISION: 0x0000130

==== GTA01v4 ====
Second generation of prototypes that was given to [[User:HaraldWelte|Harald]] +[[User:Mickey|Mickey]].

Unfortunately still not useful due to half-working touchscreen.

* ATAG_REVISION: 0x00000140

=== GTA01B ===
This is the bluetooth-enabled fork of GTA01

==== GTA01Bv2 ====
This is the first produced version of the bluetooth-enabled version.

* ATAG_REVISION: 0x00000220

==== GTA01Bv3 ====
This is the second produced version of the bluetooth-enabled version. It contains mainly GPS-related fixes.

* ATAG_REVISION: 0x00000230

This is the version that is shipped in [[Neo1973#Phase_0_.28GTA01Bv3.29|Phase 0]].

===== GTA01Bv3 Errata =====
====== PMU unable to resume from suspend ======
Due to use of wrong GPIO/EINT pin, the PMU cannot wake-up the phone after suspend. This means, specifically, '''the following events can not bring the phone back from suspend-to-ram''':
* PMU RTC Alarm
* Power button press
* Charger events (charger insertion/removal/error)
* Low battery

====== Stand-by time extremely low ======
This is due to a design bug resulting in at least 30mA additional standby current, since we cannot properly switch off the power supply to the S3C2410 PLL's. There is nothing we can do to change this with post-production fixes. GTA01Bv4 will address this issue.

====== GSM doesn't resume phone from suspend ======
The GSM modem currently doesn't signalize a wakeup interrupt to the S3C2410 in case there's some noteworthy event, such as incoming call, loss of network, incoming SMS or the like.

This is a serious issue, but can be fixed with a GSM Modem Firmware update.

====== GSM Sidetone too loud ======
The local feedback sidetone (see [http://en.wikipedia.org/wiki/Sidetone]) is too loud. This will be addressed in a GSM firmware update

====== Bad block ======
Due to an error in the production process, the factory-programmed NAND bad block information has been lost. This means that some blocks in the flash will wear out rapidly, which might become as bad as rendering the device unusable.

==== GTA01Bv4 ====
This is the version that is being shipped in [[Neo1973#Phase_1_.28GTA01Bv4.29|Phase 1]]

===== Looks =====
This is what the GTA01Bv4 PCB looks like without the shielding cans, which will be fitted later.
[[Image:Gta01b_v4_front.jpg|thumb|400px|Component side]]
[[Image:Gta01b_v4_back.jpg|thumb|400px|Display side]]

===== Errata =====

There were two versions of GTA01Bv4: some were given away (red mainboard), and some were sold (green mainboard). The given-away have [[one transistor too many]].

===== Changes from GTA01Bv3 =====
# Fix all Errata items from GTA01Bv3
# Add I2C, SPI and one irq and wakeup capable GPIO pin to debug port plus have test pads for all these signals (for soldering wires directly on the pcb)
# Fix a number of production related details and minor hardware details that are not user-visible

===GTA02===
The [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]] is now called the Neo FreeRunner and shipped within the "Mass Market launch" (see [http://wiki.openmoko.org/wiki/Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|timeline]).
It is a new main release with [[Neo1973:_GTA01Bv4_versus_GTA02_comparison|features added]]

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

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

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

===Test points===

* GSM RTS - H-TP1531
* GSM CTS - H-TP1530
* GSM Modem on - R10818 - ungrounded end
* GSM_EN - R1501 (not present) - ungrounded end

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

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

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

??? So does GTA01Bv4 equal the cat /proc/cpuinfo output of
Hardware : GTA01
Revision : 0240

== Approval ==
*CE compliance is needed before a product can be sold in the EU. The CE mark indicates that a product complies to the relevant legislation, defined in the [http://ec.europa.eu/enterprise/newapproach/standardization/harmstds/reflist.html harmonised standards]. This refers also to the most relevant, for the Neo1973, [http://ec.europa.eu/enterprise/newapproach/standardization/harmstds/reflist/emc.html Directive 89/336/EEC on electromagnetic compatibility] (EMC is the art of assuring [http://en.wikipedia.org/wiki/Electromagnetic_compatibility electromagnetic compatibility] between products). The standards are defined by [http://www.cenelec.org CENELEC] (European Committee for Electrotechnical Standardization), but not verified by any authority. It is the responsibilty of the manufacturer to convince himself that a product is in compliance, and is obligated to be able to prove this (with relevant technical documentation) for a specific product to the authorities on request. Whether the current Phase 1 devices are actually tested against the directives are unknown, no documentation has been disclosed, other than the fact that the devices bear the CE mark.

*[http://www.fcc.gov/ FCC]

===GTA01 FCC test report===

[http://people.openmoko.org/tony_tu/GTA01/certificate/FCC/ FCC test report]

===GTA01 CE test report===

[http://people.openmoko.org/tony_tu/GTA01/certificate/CE/ CE test report]

===GTA01 NCC test report===

For Taiwan Import usage:

[http://people.openmoko.org/tony_tu/GTA01/certificate/NCC/ NCC test report]

[[Category:Hardware]]
[[Category:Hardware Support]]
[[Category:Neo1973 Hardware]]

Neo FreeRunner

2008-04-14T09:11:08Z

Speedevil: /* Intended use and users */ not

{{Languages|Neo FreeRunner}}
The Neo FreeRunner (internal codename GTA02) is the second phone designed to run Openmoko software and is the direct descendant of the earlier [[FIC]] [[Neo1973]]. Hardware specs are [[Neo FreeRunner GTA02 Hardware|here]].

== Finding out status before FreeRunner is released ==

To be emailed when it is released sign up to the announce mail list here http://lists.openmoko.org/mailman/listinfo/announce. For frequently asked questions please check [[FAQ]]. Approximately, twice a month an Openmoko team member writes an update to the project here [[Community Updates]].

No official launch date will be given until the phone is ready.

== Intended use and users ==

The Neo FreeRunner is a GNU/Linux based touch screen smart phone aimed at general consumer use as well as GNU/Linux desktop users and GNU/Linux software developers.

General phone users will eventually appreciate the high spec and performance of the phone and the wide range of free and custom software packages that you are free to install to make the maximum use of the hardware for your particular needs.
It will not be suitable for end users at release.
Note that software tweaks and improvements will continue after launch as both the Openmoko team developers and the wider linux community work together.

GNU/Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner

== What are the specs ==

The specs share some features with the previous [[Neo1973]] such as

* A very high resolution touch screen (1.7" x 2.27" - 43mm x 58mm) 480x640 pixels
* 128MB SDRAM memory to allow operation of many applications at once
* Internal GPS module for map and tracking programs
* Bluetooth for local data exchange
* Physical appearance will be the same as the Neo1973. See openmoko.com for more.

but will gain the additional features of

* 802.11 b/g WiFi for fast web browsing and data transfer
* A faster 400Mhz processor (up from 266MHz)
* A hardware Graphics Accelerator chip allowing the acceleration of a limited set of operations.
** Unfortunately, this is on a shared slow (7M/s) bus with the SD card.
* 2 3D accelerometers so that the phone can know its orientation for example switching to landscape mode automatically
* 2 LEDs illuminating the two buttons on the rim of the case (one bicolor [blue|orange] behind the power button, 1 unicolor [red] behind the aux button)
* Tri-band GSM and GPRS for North America (850/1800/1900 Mhz) and the rest of the world (900/1800/1900 Mhz)
* USB Host function with 500mA power allowing you to power USB devices for short periods (will drain the FreeRunner battery faster)

A full list of the hardware specs and components of the Neo FreeRunner (internal codename GTA02xxx) can be found here [[Neo FreeRunner GTA02 Hardware]]

A comparison between Neo 1973 and Neo FreeRunner is [[Neo1973: GTA01Bv4 versus GTA02 comparison|here]]

== What is the price? ==

The device will be sold in multiple channels (including [http://www.openmoko.com Openmoko.com]), the official price has been set to 399$ but it could slightly vary in some countries (due to taxes).

[[Category:Hardware Support]]
[[Category:GTA02 Hardware| ]]

Neo FreeRunner

2008-04-14T07:57:08Z

Speedevil: /* What are the specs */ correct 100mA according to ML

{{Languages|Neo FreeRunner}}
The Neo FreeRunner (internal codename GTA02) is the second phone designed to run Openmoko software and is the direct descendant of the earlier [[FIC]] [[Neo1973]]. Hardware specs are [[Neo FreeRunner GTA02 Hardware|here]].

== Finding out status before FreeRunner is released ==

To be emailed when it is released sign up to the announce mail list here http://lists.openmoko.org/mailman/listinfo/announce. For frequently asked questions please check [[FAQ]]. Approximately, twice a month an Openmoko team member writes an update to the project here [[Community Updates]].

No official launch date will be given until the phone is ready.

== Intended use and users ==

The Neo FreeRunner is a GNU/Linux based touch screen smart phone aimed at general consumer use as well as GNU/Linux desktop users and GNU/Linux software developers.

General phone users will appreciate the high spec and performance of the phone and the wide range of free and custom software packages that you are free to install to make the maximum use of the hardware for your particular needs. Note that software tweaks and improvements will continue after launch as both the Openmoko team developers and the wider linux community work together.

GNU/Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner

== What are the specs ==

The specs share some features with the previous [[Neo1973]] such as

* A very high resolution touch screen (1.7" x 2.27" - 43mm x 58mm) 480x640 pixels
* 128MB SDRAM memory to allow operation of many applications at once
* Internal GPS module for map and tracking programs
* Bluetooth for local data exchange
* Physical appearance will be the same as the Neo1973. See openmoko.com for more.

but will gain the additional features of

* 802.11 b/g WiFi for fast web browsing and data transfer
* A faster 400Mhz processor (up from 266MHz)
* A hardware Graphics Accelerator chip allowing the acceleration of a limited set of operations.
** Unfortunately, this is on a shared slow (7M/s) bus with the SD card.
* 2 3D accelerometers so that the phone can know its orientation for example switching to landscape mode automatically
* 2 LEDs illuminating the two buttons on the rim of the case (one bicolor [blue|orange] behind the power button, 1 unicolor [red] behind the aux button)
* Tri-band GSM and GPRS for North America (850/1800/1900 Mhz) and the rest of the world (900/1800/1900 Mhz)
* USB Host function with 500mA power allowing you to power USB devices for short periods (will drain the FreeRunner battery faster)

A full list of the hardware specs and components of the Neo FreeRunner (internal codename GTA02xxx) can be found here [[Neo FreeRunner GTA02 Hardware]]

A comparison between Neo 1973 and Neo FreeRunner is [[Neo1973: GTA01Bv4 versus GTA02 comparison|here]]

== What is the price? ==

The device will be sold in multiple channels (including [http://www.openmoko.com Openmoko.com]), the official price has been set to 399$ but it could slightly vary in some countries (due to taxes).

[[Category:Hardware Support]]
[[Category:GTA02 Hardware| ]]

Neo 1973

2008-04-11T22:16:16Z

Speedevil: /* Phase 1 (GTA01Bv4) */ tense

[[Image:FIC-neo1973 small.jpg|120px|right]]
The [[Neo1973 Hardware | Neo1973]] is the first phone designed to run [[Openmoko]].
It is a phone that can be used with any [[GSM]] operator, and it is manufactured by [[FIC]] who instigated the [[Openmoko]] project.

If you just received a Neo1973 here are some suggestions for [[Getting_Started_with_your_Neo1973 | getting started]].

[[Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]] have more information on the hardware.

See [[Openmoko]], [[OpenMokoFramework]], [[MokoMakefile]] and [[Development resources]] for more information about source code.

See [[FAQ]] for other Frequently Asked Questions.

There is some SVG [[ClipArt]] for simple illustrative purposes.

== Phase 0 (GTA01Bv3) ==
{{Main|Neo1973 Phase 0}}
:''See also [[Wishlist:Neo1973_P0_Review]]
36 developers have received their devices. [http://lists.openmoko.org/pipermail/announce/2007-March/000006.html]

== Phase 1 (GTA01Bv4) ==
{{Main|Neo1973 Phase 1}}

The Neo Base costed $300, with the Advanced kit costing $450.
Both have now sold out.

See [[Neo1973_Hardware#GTA01Bv4|Neo1973 Hardware]] for what components GTA01B_v04 contains.

Neo Base -- everything the mobile application developer needs to enjoy
the benefits of the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card
* Mini USB Connectivity Cable

Neo Advanced -- everything the mobile device hacker wants to get down
and dirty with the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh) (2x)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card (2x)
* Mini USB Connectivity Cable (2x)
* Debug Flex Cable
* Debug Board v2 (JTAG and serial console)
* Ruggedized Toolbox with shoulder strap
* Guitar Pick (for opening case)
* Torx T6 screwdriver

You do not need the Advanced package to do normal kernel, or application development, only perhaps hacking on [[u-boot]].

As described in [http://lists.openmoko.org/pipermail/community/2007-June/006005.html Sean's post on mailing list] (with some adjustments/corrections).

== "Phase 2" (GTA02, "Mass Market") ==
{{Main|Neo FreeRunner}}
The device will hopefully go on sale for developers in future months.

=== Estimated time line ===

* GTA02v3 design finalized - DONE
* GTA02v3 power supply flaw found, GTA02v4 needed - DONE
* GTA02v4 design finalized - DONE
* GTA02v4 small number produced for Openmoko internal developer evaluation - DONE
* GTA02v4 thorough evaluation by Openmoko internal developers - ''In progress''
* GTA02v4 flaw found, GTA02v5 needed - On hold while further development on drivers is done to ensure no further hardware bugs. - ''In progress''
* GTA02v5 design finalized - DONE
* GTA02v5 small number produced for Openmoko internal developer evaluation - Done (around 20)
* GTA02v5 thorough evaluation by Openmoko internal developers - ''In progress''
* GTA02v5 produced in moderate volume
* GTA02v5 goes on sale to community via web store

(For the very latest news, visit [[Community Updates]], which also allows you to suggest questions or topics for future updates.)

It will have the following new hardware components:[http://lists.openmoko.org/pipermail/community/2007-July/008458.html]

* Atheros 802.11 b/g WiFi
* Samsung S3C2442 B54 SoC @ 400Mhz
* SMedia Glamo3362 Graphics Accelerator
* 2x ST 3D Accelerometers
* 256MB Flash
* 128MB SDRAM
* 2MB NOR Flash
* 1200mAh Battery
* 2 LEDs illuminating the two buttons.
* u-blox/Atmel ATR0635 GPS
* Bluetooth
* 850/1800/1900 Mhz or 900/1800/1900 Mhz for GSM/GPRS
* USB Host function with power

It will also lose:
* One speaker, becoming mono.

We will sell this device through multiple channels. Direct from
openmoko.com, the price will be $399 for the Neo Base and $99 for the debug board.

Adds to the Phase 1 phone (see [[Neo1973:_GTA01Bv4_versus_GTA02_comparison|side by side comparison]]):
* 2D Graphics-Accelerator (in theory 3D - however driver is unlikely to be available to to lack of core dev time and inability to supply docs without NDA to third parties.
* 2 Accelerometers
* Faster CPU - S3C2442/400
* WiFi: [http://lists.openmoko.org/pipermail/announce/2007-April/000012.html Atheros AR6K] (see also [http://lists.openmoko.org/pipermail/community/2007-April/004934.html])
** Above from [http://sicherheitsschwankung.de/gallery/v/openmoko/IMG_8662-slide.JPG.html] '' and other sources
* 500mA powered USB host
* There will be no changes in the external housing, but internal plastics change. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html] [http://lists.openmoko.org/pipermail/community/2007-March/004255.html]



{{Languages|Neo1973}}

[[Category:Hardware Support]]
[[Category:Neo1973 Hardware| ]]

Neo 1973

2008-04-11T22:13:46Z

Speedevil: /* Estimated time line */ correct USB current as according to mailing list

[[Image:FIC-neo1973 small.jpg|120px|right]]
The [[Neo1973 Hardware | Neo1973]] is the first phone designed to run [[Openmoko]].
It is a phone that can be used with any [[GSM]] operator, and it is manufactured by [[FIC]] who instigated the [[Openmoko]] project.

If you just received a Neo1973 here are some suggestions for [[Getting_Started_with_your_Neo1973 | getting started]].

[[Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]] have more information on the hardware.

See [[Openmoko]], [[OpenMokoFramework]], [[MokoMakefile]] and [[Development resources]] for more information about source code.

See [[FAQ]] for other Frequently Asked Questions.

There is some SVG [[ClipArt]] for simple illustrative purposes.

== Phase 0 (GTA01Bv3) ==
{{Main|Neo1973 Phase 0}}
:''See also [[Wishlist:Neo1973_P0_Review]]
36 developers have received their devices. [http://lists.openmoko.org/pipermail/announce/2007-March/000006.html]

== Phase 1 (GTA01Bv4) ==
{{Main|Neo1973 Phase 1}}
You can order from https://direct.openmoko.com/ now. See also the [[Group Order]] page.

The Neo Base costs $300, the Neo Advanced costs $450.

See [[Neo1973_Hardware#GTA01Bv4|Neo1973 Hardware]] for what components GTA01B_v04 contains.

Neo Base -- everything the mobile application developer needs to enjoy
the benefits of the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card
* Mini USB Connectivity Cable

Neo Advanced -- everything the mobile device hacker wants to get down
and dirty with the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh) (2x)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card (2x)
* Mini USB Connectivity Cable (2x)
* Debug Flex Cable
* Debug Board v2 (JTAG and serial console)
* Ruggedized Toolbox with shoulder strap
* Guitar Pick (for opening case)
* Torx T6 screwdriver

You do not need the Advanced package to do normal kernel, or application development, only perhaps hacking on [[u-boot]].

As described in [http://lists.openmoko.org/pipermail/community/2007-June/006005.html Sean's post on mailing list] (with some adjustments/corrections).

== "Phase 2" (GTA02, "Mass Market") ==
{{Main|Neo FreeRunner}}
The device will hopefully go on sale for developers in future months.

=== Estimated time line ===

* GTA02v3 design finalized - DONE
* GTA02v3 power supply flaw found, GTA02v4 needed - DONE
* GTA02v4 design finalized - DONE
* GTA02v4 small number produced for Openmoko internal developer evaluation - DONE
* GTA02v4 thorough evaluation by Openmoko internal developers - ''In progress''
* GTA02v4 flaw found, GTA02v5 needed - On hold while further development on drivers is done to ensure no further hardware bugs. - ''In progress''
* GTA02v5 design finalized - DONE
* GTA02v5 small number produced for Openmoko internal developer evaluation - Done (around 20)
* GTA02v5 thorough evaluation by Openmoko internal developers - ''In progress''
* GTA02v5 produced in moderate volume
* GTA02v5 goes on sale to community via web store

(For the very latest news, visit [[Community Updates]], which also allows you to suggest questions or topics for future updates.)

It will have the following new hardware components:[http://lists.openmoko.org/pipermail/community/2007-July/008458.html]

* Atheros 802.11 b/g WiFi
* Samsung S3C2442 B54 SoC @ 400Mhz
* SMedia Glamo3362 Graphics Accelerator
* 2x ST 3D Accelerometers
* 256MB Flash
* 128MB SDRAM
* 2MB NOR Flash
* 1200mAh Battery
* 2 LEDs illuminating the two buttons.
* u-blox/Atmel ATR0635 GPS
* Bluetooth
* 850/1800/1900 Mhz or 900/1800/1900 Mhz for GSM/GPRS
* USB Host function with power

It will also lose:
* One speaker, becoming mono.

We will sell this device through multiple channels. Direct from
openmoko.com, the price will be $399 for the Neo Base and $99 for the debug board.

Adds to the Phase 1 phone (see [[Neo1973:_GTA01Bv4_versus_GTA02_comparison|side by side comparison]]):
* 2D Graphics-Accelerator (in theory 3D - however driver is unlikely to be available to to lack of core dev time and inability to supply docs without NDA to third parties.
* 2 Accelerometers
* Faster CPU - S3C2442/400
* WiFi: [http://lists.openmoko.org/pipermail/announce/2007-April/000012.html Atheros AR6K] (see also [http://lists.openmoko.org/pipermail/community/2007-April/004934.html])
** Above from [http://sicherheitsschwankung.de/gallery/v/openmoko/IMG_8662-slide.JPG.html] '' and other sources
* 500mA powered USB host
* There will be no changes in the external housing, but internal plastics change. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html] [http://lists.openmoko.org/pipermail/community/2007-March/004255.html]



{{Languages|Neo1973}}

[[Category:Hardware Support]]
[[Category:Neo1973 Hardware| ]]

Neo FreeRunner Hardware

2008-04-07T10:54:50Z

Speedevil: /* Graphics/3D Acceleration */ add corrections.

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

{{note|This page is about hardware that is currently in '''design/prototype''' phase, changes are frequent}}

[[Image:Gta02a5 pcba cs.JPG|thumb|400px|display (top) side NOTE: GTA02 A5 PCBA Component Side photo]]
[[Image:Gta02a5 pcba ps.JPG|thumb|400px|component (back) side NOTE: GTA02 A5 PCBA Print Side photo]]
[[Image:GTA02 A5 PCB CS.jpg|thumb|400px|component (back) side NOTE: GTA02 A5 PCB Component Side photo]]
[[Image:GTA02 A5 PCB PS.jpg|thumb|400px|component (back) side NOTE: GTA02 A5 PCB Print Side photo]]

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

Detail hardware component selection can be found below.

=Features=
*Display- Topply o2.8, 480 x 640 pixels, VGA, 200 NIT minimum, resistance type touch

*User Interface Navigation- Touch screen on LCD, 2 control “buttons”, 1 Power button, 1 Aux for 911 emergency call

*Built-in 802.11b/g Radio (Atheros chipset AR6001 Flash version)

*Built-in Bluetooth 2.0 + EDR (CSR and support PCM audio , BC4 frimware version)

*Built-in 2D/3D graphics acceleration chip (S-Media 3362)

*2 built-in Tri-Axis sensor (ST accelerometer LIS302DL)

*Built in GPS Radio – -130 dBm with internal antenna, -157 dBm tracking on chipset specification, TTFF under 40 seconds with -130 dBm signal strength, and tracking (u-Blox)

*Antenna – Specialized antenna for best in hand hold GPS, GPRS and Wi-Fi/Bluetooth performance are required, -105dBm on receiving, Tx 30dbm+2 on GSM

*External Antennae – MMCX GPS connector

*GPRS Radio –GSM/GPRS radio. A Pre-PTCRB certified module will be preferred

*Linux – Linux kernel 2.6.24 or later OpenMoko kernel

*USB - Client and Host mode switch-able (to be used for software downloading), provide host 5v power

*Power- Normal mode power will be via 1200 mAh battery with built-in coulomb counter, could charge via specialized charger. Internal Lithium Ion or Lithium Polymer battery will keep device in standby mode. Battery life (Approximation/Ideal Target) Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 3-4 hrs(GSM)

*LED- LED indicator under Aux/Power button key

=Hardware Specification=
===Hardware Electrical===

*400/500 MHz Samsung 2442B Processor/SOC (400 minimum)
*Boot code in NAND FLASH or 2MB NOR FLASH (optional design)
*128 MB SDRAM total, 64 MB CPU internal, 64 MB external
*256MB NAND Flash MCP package.

=== Display ===
*Topploy VGA ; 2.8” diagonal, 480 x 640 pixels
*Transmissive display: good readability in high ambient light is essential
*White LED backlight. Required brightness is 200 NIT minimum.
*Resistance type touch panel.

=== WiFi 802.11 b/g transceiver ===
*Must have GPL support source or GPL compatible policy
*TX power at 11 Mbps: 13 dBm minimum
*RX sensitivity at 11 Mbps: -89 dBm desired, -83 dBm minimum
*AP mode desirable, not required
*WEP and WPA supported
*Atheros preferred because it's GPL policy

=== Serial interfaces (UART) ===
*Three serial interfaces are required
*Console
*A-GPS or GPS
*GSM/GPRS

=== Accelerometer ===
* 2x accelerometer required
* Could support interrupt while suspend or power save mode
* 3 axis sensing

=== A-GPS ===
*GPS chipset receiver and antenna
*Sensitivity at Antenna port: -157 dBm tracking on chipset specification
*LNA and SAW filter for maximum interference protection
*Cold start time to first fix: 40 sec typical at -130 dBm, 60 sec max
*Must support GPL for Assist-GPS function with open API
*Industry quality GPS
*Could fit in GTA01 GPS area on the PCB

=== GPS Antenna Performance ===
*Antenna is passive and internal; 15 mm x 15 mm ceramic patch is nominal design
*Antenna LNA and SAW filter are required to meet GPS performance
*15 mm square ground plane (minimum 1 mm ground border around patch) (TBA)
*There will be one external GPS antenna connector (MMCX)
*C/N ratio should higher than 35 on production testing

=== Buttons ===
*Touch screen over LCD is primary data entry mechanism
*Two “hard” buttons: Power button (on side of Neo1973) is a mechanical switch actuated by a plastic pushbutton in a hole in the housing. Aux (911) button on the top of the device, All two of these buttons, when pushed by the operator, are binary inputs (on/off or pressed/not pressed) to the software. The effect of each button is determined by the application software in the device
*Buttons may need to be backlit
*50000 cycles on hardware specification

=== Sound outputs ===
*Speaker in box (need good volume and acoustic behavior innoise environment)
*Audio is monophonic*Max volume: 100 dB at 5 cm to assure good performance in environment.
*Support earphone with mic by jack

=== Power Design Requirements===
*Software based power management unit preferred
*NXP PCF series preferred
*Need support charge from USB function
*Need support powered by USB function
*Power switch: Neo1973 will have a power switch, for power on/off and suspend
* Power/Aux switch must be backlit
*Switch controls whether device is running or suspended by presses of the switch
*Switch does not shut off the power; it only suspends/resumes the device
*Internal Li-Ion or Li-Polymer battery is included. This battery supplies standby power to the device eliminates the rebooting of the device when local power is again reapplied. Battery is 1200 ma-hr.
*Battery life (Approximation) Ideal/Target Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 4 hrs(GSM)
*Estimated current draw for the entire device when in suspend mode (and ALL peripherals are turned off or set for deep sleep) is <5 mA at 3.6 volts (Li-Ion terminal voltage).
*GSM module deep sleep(alive and keep contact with base station) stage should take less than 8mA
*Battery will reach half capacity (~600 mAh) with 500 charge-discharge cycles. This will occur in less than 2 years of daily service.
*When powered continuously, Neo1973 must suspend (to low power mode) based either on observed low battery voltage condition or a configurable time delay.
*Neo1973 must monitor battery status while suspended and resume automatically if the charger is inserted.
*Primary power connection: 1200mAh battery
*USB charger have ID pin 47.5k pull down for Openmoko identification
*Indicators: an LED indicator visible from the side of the unit will illuminate when charging or have missing incoming call

=== GSM/GPRS ===
*850/1800/1900 and 900/1800/1900 MHz bands must be supported
*Design should allow for multi-band version (850/900 MHz)
*Module based GPRS transceiver could meeting PTCRB and appropriate FCC certifications. It preferred that the module be pre-certified with PTCRB or OTA test
*FCC/CE certification required for GSM/GPRS part

=== GSM-GPRS Antenna Performance ===
*-105 dBm receiving on each channel (GSM/PCS)
*30+2 dBm transmission on GSM channel

=== Wi-Fi Modules ===
*Must support GPL driver
*Atheros AR6k preferred
*Flash version required

=== Wi-Fi Antenna Performance ===
*The Wi-Fi antenna with TX 13 to 15 dBm
*RX -89 to -83 dBm @802.11b 11Mbps or an equivalent performance antenna

=== Bluetooth ===
*CSR BC4 or later solutions

=== USB ===
*Neo FreeRunner GTA02 will have USB, client/host. Using USB 1.1
*Could provide USB host 5v power
*Could be powered by USB

=== Microphone ===
1 microphone is in the device

=== Firmware Image ===
*Using Linux 2.6.24 or later
*Could support boot from NAND or Boot from NOR
*Shipping image should come with basic phone function
*Could do full firmware upgrade by USB cable

=== PSN ===
*Device will have a PSN (product serial number) printed on the product label and machine readable in system NAND memory

=== IMEI ===
*Production phase should have IMEI code written

= Package Specification =
*Weight: ~150 grams with battery.
*4 in 1 laser pen passed RoHs and safty regulation for laser equipment safty
*1x 512MB microSD Card (SanDisk/Transcend)
*1x USB cable Standard A to mini-B connector
*1x 1200mAh smart/gauge battery
*Quick start guide
*5v USB power cord w/100-240 switchable power plug
*Safety card, warranty card
*Package could pass 1m to 1.5m drop test
*AC USB charger,100v-240v, Passed UL and all required safety regulation
*Must pass FCC/CE certification
*Must pass NCC certification for Taiwan import regulation
*RoHS Compatible
*WEEE Report required

= Life Cycle Specification =

=== Product Life ===
The product is designed to last a minimum of 2 years.

=== Operating Temperature ===
*Target operating range is –10°C to +60°C

=== Storage Temperature ===
*-15 deg C to +70 deg C

=== ESD ===
The device can withstand a 4.0kV contact discharge and 8.0kV air

=== Drop test ===
Should pass 1m direct drop to concrete ground or 1.5m on slide with carpet

= GTA02 Hardware Component Selection =

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

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

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 Samsung SC32442B]
* User Manual: FIXME
* Core: ARM920T
* Instruction Set: ARMv4 (Android ''currently'' requires ARMv5)
* Built-in 64MB SDRAM
* Built-in 256 MB NAND
* Could run at 500Mhz
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt 
* Evaluation board: [http://www.meritech.co.kr/products/product_view.php?num=52 S3C2442 EVB]

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

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

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

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

==== NOR Flash ====

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

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

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

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

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

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

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

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

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

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

== AGPS ==
u-blox ANTARIS 4 chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
* Driver: none needed, talks standard NMEA
* u-blox Antaris 4 Protocol [http://www.u-blox.com/customersupport/antaris_doc.html Protocol download page]
* ATR0635 Datasheet: [http://www.u-blox.com/products/Data_Sheets/ATR0630_35_SglChip_Data_Sheet(GPS.G4-X-06009).pdf u-blox ATR0635] 

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

== Graphics/3D Acceleration ==

Smedia Glamo 3362.
* Homepage: http://www.smediatech.com/product3362.htm
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC)
* Connected to: S3C2442 Address/Data bus 

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

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

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

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

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

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

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

== WiFi Module==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Case ==
The new case for the FreeRunner is all black, as seen on the front page on the wiki.
Source: Mickey on IRC
=Accessory=

== Stylus ==

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

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

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

== microSD Card ==

GTA02 should comes with one of following microSD card

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

== Charger ==

AKII Technology Charger

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

= History =

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

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

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

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

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

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

== GTA02v4 ==
Mass production release candidate version 1

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

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

== GTA02v5 ==
Mass production candicate version 2/Mass production version

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

== GTA02v6 ==
Mass production candicate version 3/Mass production version 

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

*First 100 pcs might start from end of 2008 March
*Add capacitor space for Vbat, reduce the SMT effort
*Add GSM IR resistor for better GSM deep sleep
*Reserve 3 GPIO for hardware version control
* ATAG_REVISION: 0360

= Debug Board =

== Debug Board Connector definition ==

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

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

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

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

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

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

= Certification =

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

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

[[Category:Hardware ]]
[[Category:GTA02 Hardware]]
[[Category:Hardware Support]]

Neo FreeRunner Hardware

2008-04-07T10:52:17Z

Speedevil: /* CALYPSO ASIC digital baseband */ add doc links

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

{{note|This page is about hardware that is currently in '''design/prototype''' phase, changes are frequent}}

[[Image:Gta02a5 pcba cs.JPG|thumb|400px|display (top) side NOTE: GTA02 A5 PCBA Component Side photo]]
[[Image:Gta02a5 pcba ps.JPG|thumb|400px|component (back) side NOTE: GTA02 A5 PCBA Print Side photo]]
[[Image:GTA02 A5 PCB CS.jpg|thumb|400px|component (back) side NOTE: GTA02 A5 PCB Component Side photo]]
[[Image:GTA02 A5 PCB PS.jpg|thumb|400px|component (back) side NOTE: GTA02 A5 PCB Print Side photo]]

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

Detail hardware component selection can be found below.

=Features=
*Display- Topply o2.8, 480 x 640 pixels, VGA, 200 NIT minimum, resistance type touch

*User Interface Navigation- Touch screen on LCD, 2 control “buttons”, 1 Power button, 1 Aux for 911 emergency call

*Built-in 802.11b/g Radio (Atheros chipset AR6001 Flash version)

*Built-in Bluetooth 2.0 + EDR (CSR and support PCM audio , BC4 frimware version)

*Built-in 2D/3D graphics acceleration chip (S-Media 3362)

*2 built-in Tri-Axis sensor (ST accelerometer LIS302DL)

*Built in GPS Radio – -130 dBm with internal antenna, -157 dBm tracking on chipset specification, TTFF under 40 seconds with -130 dBm signal strength, and tracking (u-Blox)

*Antenna – Specialized antenna for best in hand hold GPS, GPRS and Wi-Fi/Bluetooth performance are required, -105dBm on receiving, Tx 30dbm+2 on GSM

*External Antennae – MMCX GPS connector

*GPRS Radio –GSM/GPRS radio. A Pre-PTCRB certified module will be preferred

*Linux – Linux kernel 2.6.24 or later OpenMoko kernel

*USB - Client and Host mode switch-able (to be used for software downloading), provide host 5v power

*Power- Normal mode power will be via 1200 mAh battery with built-in coulomb counter, could charge via specialized charger. Internal Lithium Ion or Lithium Polymer battery will keep device in standby mode. Battery life (Approximation/Ideal Target) Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 3-4 hrs(GSM)

*LED- LED indicator under Aux/Power button key

=Hardware Specification=
===Hardware Electrical===

*400/500 MHz Samsung 2442B Processor/SOC (400 minimum)
*Boot code in NAND FLASH or 2MB NOR FLASH (optional design)
*128 MB SDRAM total, 64 MB CPU internal, 64 MB external
*256MB NAND Flash MCP package.

=== Display ===
*Topploy VGA ; 2.8” diagonal, 480 x 640 pixels
*Transmissive display: good readability in high ambient light is essential
*White LED backlight. Required brightness is 200 NIT minimum.
*Resistance type touch panel.

=== WiFi 802.11 b/g transceiver ===
*Must have GPL support source or GPL compatible policy
*TX power at 11 Mbps: 13 dBm minimum
*RX sensitivity at 11 Mbps: -89 dBm desired, -83 dBm minimum
*AP mode desirable, not required
*WEP and WPA supported
*Atheros preferred because it's GPL policy

=== Serial interfaces (UART) ===
*Three serial interfaces are required
*Console
*A-GPS or GPS
*GSM/GPRS

=== Accelerometer ===
* 2x accelerometer required
* Could support interrupt while suspend or power save mode
* 3 axis sensing

=== A-GPS ===
*GPS chipset receiver and antenna
*Sensitivity at Antenna port: -157 dBm tracking on chipset specification
*LNA and SAW filter for maximum interference protection
*Cold start time to first fix: 40 sec typical at -130 dBm, 60 sec max
*Must support GPL for Assist-GPS function with open API
*Industry quality GPS
*Could fit in GTA01 GPS area on the PCB

=== GPS Antenna Performance ===
*Antenna is passive and internal; 15 mm x 15 mm ceramic patch is nominal design
*Antenna LNA and SAW filter are required to meet GPS performance
*15 mm square ground plane (minimum 1 mm ground border around patch) (TBA)
*There will be one external GPS antenna connector (MMCX)
*C/N ratio should higher than 35 on production testing

=== Buttons ===
*Touch screen over LCD is primary data entry mechanism
*Two “hard” buttons: Power button (on side of Neo1973) is a mechanical switch actuated by a plastic pushbutton in a hole in the housing. Aux (911) button on the top of the device, All two of these buttons, when pushed by the operator, are binary inputs (on/off or pressed/not pressed) to the software. The effect of each button is determined by the application software in the device
*Buttons may need to be backlit
*50000 cycles on hardware specification

=== Sound outputs ===
*Speaker in box (need good volume and acoustic behavior innoise environment)
*Audio is monophonic*Max volume: 100 dB at 5 cm to assure good performance in environment.
*Support earphone with mic by jack

=== Power Design Requirements===
*Software based power management unit preferred
*NXP PCF series preferred
*Need support charge from USB function
*Need support powered by USB function
*Power switch: Neo1973 will have a power switch, for power on/off and suspend
* Power/Aux switch must be backlit
*Switch controls whether device is running or suspended by presses of the switch
*Switch does not shut off the power; it only suspends/resumes the device
*Internal Li-Ion or Li-Polymer battery is included. This battery supplies standby power to the device eliminates the rebooting of the device when local power is again reapplied. Battery is 1200 ma-hr.
*Battery life (Approximation) Ideal/Target Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 4 hrs(GSM)
*Estimated current draw for the entire device when in suspend mode (and ALL peripherals are turned off or set for deep sleep) is <5 mA at 3.6 volts (Li-Ion terminal voltage).
*GSM module deep sleep(alive and keep contact with base station) stage should take less than 8mA
*Battery will reach half capacity (~600 mAh) with 500 charge-discharge cycles. This will occur in less than 2 years of daily service.
*When powered continuously, Neo1973 must suspend (to low power mode) based either on observed low battery voltage condition or a configurable time delay.
*Neo1973 must monitor battery status while suspended and resume automatically if the charger is inserted.
*Primary power connection: 1200mAh battery
*USB charger have ID pin 47.5k pull down for Openmoko identification
*Indicators: an LED indicator visible from the side of the unit will illuminate when charging or have missing incoming call

=== GSM/GPRS ===
*850/1800/1900 and 900/1800/1900 MHz bands must be supported
*Design should allow for multi-band version (850/900 MHz)
*Module based GPRS transceiver could meeting PTCRB and appropriate FCC certifications. It preferred that the module be pre-certified with PTCRB or OTA test
*FCC/CE certification required for GSM/GPRS part

=== GSM-GPRS Antenna Performance ===
*-105 dBm receiving on each channel (GSM/PCS)
*30+2 dBm transmission on GSM channel

=== Wi-Fi Modules ===
*Must support GPL driver
*Atheros AR6k preferred
*Flash version required

=== Wi-Fi Antenna Performance ===
*The Wi-Fi antenna with TX 13 to 15 dBm
*RX -89 to -83 dBm @802.11b 11Mbps or an equivalent performance antenna

=== Bluetooth ===
*CSR BC4 or later solutions

=== USB ===
*Neo FreeRunner GTA02 will have USB, client/host. Using USB 1.1
*Could provide USB host 5v power
*Could be powered by USB

=== Microphone ===
1 microphone is in the device

=== Firmware Image ===
*Using Linux 2.6.24 or later
*Could support boot from NAND or Boot from NOR
*Shipping image should come with basic phone function
*Could do full firmware upgrade by USB cable

=== PSN ===
*Device will have a PSN (product serial number) printed on the product label and machine readable in system NAND memory

=== IMEI ===
*Production phase should have IMEI code written

= Package Specification =
*Weight: ~150 grams with battery.
*4 in 1 laser pen passed RoHs and safty regulation for laser equipment safty
*1x 512MB microSD Card (SanDisk/Transcend)
*1x USB cable Standard A to mini-B connector
*1x 1200mAh smart/gauge battery
*Quick start guide
*5v USB power cord w/100-240 switchable power plug
*Safety card, warranty card
*Package could pass 1m to 1.5m drop test
*AC USB charger,100v-240v, Passed UL and all required safety regulation
*Must pass FCC/CE certification
*Must pass NCC certification for Taiwan import regulation
*RoHS Compatible
*WEEE Report required

= Life Cycle Specification =

=== Product Life ===
The product is designed to last a minimum of 2 years.

=== Operating Temperature ===
*Target operating range is –10°C to +60°C

=== Storage Temperature ===
*-15 deg C to +70 deg C

=== ESD ===
The device can withstand a 4.0kV contact discharge and 8.0kV air

=== Drop test ===
Should pass 1m direct drop to concrete ground or 1.5m on slide with carpet

= GTA02 Hardware Component Selection =

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

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

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 Samsung SC32442B]
* User Manual: FIXME
* Core: ARM920T
* Instruction Set: ARMv4 (Android ''currently'' requires ARMv5)
* Built-in 64MB SDRAM
* Built-in 256 MB NAND
* Could run at 500Mhz
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt 
* Evaluation board: [http://www.meritech.co.kr/products/product_view.php?num=52 S3C2442 EVB]

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

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

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

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

==== NOR Flash ====

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

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

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

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

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

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

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

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

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

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

== AGPS ==
u-blox ANTARIS 4 chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
* Driver: none needed, talks standard NMEA
* u-blox Antaris 4 Protocol [http://www.u-blox.com/customersupport/antaris_doc.html Protocol download page]
* ATR0635 Datasheet: [http://www.u-blox.com/products/Data_Sheets/ATR0630_35_SglChip_Data_Sheet(GPS.G4-X-06009).pdf u-blox ATR0635] 

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

== Graphics/3D Acceleration ==

Smedia Glamo 3362.
* Homepage: http://www.smediatech.com/product3362.htm
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: FIXME
* Connected to: S3C2442 Address/Data bus 

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

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

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

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

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

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

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

== WiFi Module==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Case ==
The new case for the FreeRunner is all black, as seen on the front page on the wiki.
Source: Mickey on IRC
=Accessory=

== Stylus ==

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

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

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

== microSD Card ==

GTA02 should comes with one of following microSD card

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

== Charger ==

AKII Technology Charger

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

= History =

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

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

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

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

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

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

== GTA02v4 ==
Mass production release candidate version 1

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

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

== GTA02v5 ==
Mass production candicate version 2/Mass production version

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

== GTA02v6 ==
Mass production candicate version 3/Mass production version 

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

*First 100 pcs might start from end of 2008 March
*Add capacitor space for Vbat, reduce the SMT effort
*Add GSM IR resistor for better GSM deep sleep
*Reserve 3 GPIO for hardware version control
* ATAG_REVISION: 0360

= Debug Board =

== Debug Board Connector definition ==

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

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

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

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

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

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

= Certification =

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

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

[[Category:Hardware ]]
[[Category:GTA02 Hardware]]
[[Category:Hardware Support]]

Neo FreeRunner

2008-04-07T10:39:59Z

Speedevil: /* What are the specs */ update

{{Languages|Neo FreeRunner}}
The Neo FreeRunner (internal codename GTA02) is the second phone designed to run Openmoko software and is the direct descendant of the earlier [[FIC]] [[Neo1973]]. Hardware specs are [[Neo FreeRunner GTA02 Hardware|here]].

== Finding out status before FreeRunner is released ==

To be emailed when it is released sign up to the announce mail list here http://lists.openmoko.org/mailman/listinfo/announce. For frequently asked questions please check [[FAQ]]. Approximately, twice a month an Openmoko team member writes an update to the project here [[Community Updates]].

No official launch date will be given until the phone is ready.

== Intended use and users ==

The Neo FreeRunner is a GNU/Linux based touch screen smart phone aimed at general consumer use as well as GNU/Linux desktop users and GNU/Linux software developers.

General phone users will appreciate the high spec and performance of the phone and the wide range of free and custom software packages that you are free to install to make the maximum use of the hardware for your particular needs. Note that software tweaks and improvements will continue after launch as both the Openmoko team developers and the wider linux community work together.

GNU/Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner

== What are the specs ==

The specs share some features with the previous [[Neo1973]] such as

* A very high resolution touch screen (1.7" x 2.27" - 43mm x 58mm) 480x640 pixels
* 128MB SDRAM memory to allow operation of many applications at once
* Internal GPS module for map and tracking programs
* Bluetooth for local data exchange
* Physical appearance will be the same as the Neo1973. See openmoko.com for more.

but will gain the additional features of

* 802.11 b/g WiFi for fast web browsing and data transfer
* A faster 400Mhz processor (up from 266MHz)
* A hardware Graphics Accelerator chip allowing the acceleration of a limited set of operations.
** Unfortunately, this is on a shared slow (7M/s) bus with the SD card.
* 2 3D accelerometers so that the phone can know its orientation for example switching to landscape mode automatically
* 2 LEDs illuminating the two buttons on the rim of the case (one bicolor [blue|orange] behind the power button, 1 unicolor [red] behind the aux button)
* Tri-band GSM and GPRS for North America (850/1800/1900 Mhz) and the rest of the world (900/1800/1900 Mhz)
* USB Host function with 100mA power allowing you to power USB devices for short periods (will drain the FreeRunner battery faster)

A full list of the hardware specs and components of the Neo FreeRunner (internal codename GTA02xxx) can be found here [[Neo FreeRunner GTA02 Hardware]]

A comparison between Neo 1973 and Neo FreeRunner is [[Neo1973: GTA01Bv4 versus GTA02 comparison|here]]

== What is the price? ==

We will sell this device through multiple channels. Distributors and prices are not finalized yet.

[[Category:Hardware Support]]
[[Category:GTA02 Hardware| ]]

Neo 1973 GPS

2008-04-07T10:33:55Z

Speedevil: update

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

Note that the GTA02 device (not yet available) contains a different GPS chip (see http://www.u-blox.com/products/atr0635.html and/or http://www.atmel.com/dyn/products/product_card.asp?part_id=3932 for specs).

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

In the very early shipment to 50 Phase 1 developers, a binary-only program for talking to the the GPS was accidentally included
in /home/root/DM2/gps, (and presumably, the same binary would function on a P0 device).
This binary is called gllin and it is a oabi binary, i.e. it will only work in the 2007.1 OpenMoko environment. There is now a eabi binary, which works with 2007.2.

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

To turn on the GPS, echo 1 to the file ./devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

cat /dev/ttySAC1 will work fine.

Before getting a fix, the GPS spits out lots of "$GPTXT,01,01,01,NMEA unknown msg*58", though these stop once a fix is obtained. --[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

Neo 1973 GPS

2008-04-07T09:52:28Z

Speedevil: add GTA02 info, and deprecation of opensource effort.

The Neo1973 device contains an integrated GPS. The particular device
is marketed as an AGPS, and there is some [[Hardware:AGPS |
discussion]] available as to what significance that "A" might have.

Note that the GTA02 device (not yet available) contains a different GPS chip (see http://www.u-blox.com/products/atr0635.html and/or http://www.atmel.com/dyn/products/product_card.asp?part_id=3932 for specs).

=== GTA01 GPS driver (gllin) ===
''Main article - [[gllin]]''

The GPS driver is available here: [http://3rdparty.downloads.openmoko.org/gllin/ http://3rdparty.downloads.openmoko.org/gllin/]. It is a command line tool that after starting writes the positioning data so that they can be read as if they were written to the file.

And here the Mail from Michael Shiloh [http://lists.openmoko.org/pipermail/community/2007-November/011916.html http://lists.openmoko.org/pipermail/community/2007-November/011916.html]

In the very early shipment to 50 Phase 1 developers, a binary-only program for talking to the the GPS was accidentally included
in /home/root/DM2/gps, (and presumably, the same binary would function on a P0 device).
This binary is called gllin and it is a oabi binary, i.e. it will only work in the 2007.1 OpenMoko environment. There is now a eabi binary, which works with 2007.2.

There was an effort to write a Free Software
program that could be used instead of this binary-only program, but this stalled after the decision to change GPS chips in GTA02.

See [[Hammerhead/Protocol]] for details and the latest status.

Some scripts for those with the binary are on [[Manually_using_GPS]]

Please see the important information on [[Gllin]]!

=== GTA02 GPS ===

To turn on the GPS, echo 1 to the file ./devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

To read from the GPS, simply read /dev/ttySAC1.

cat /dev/ttySAC1 will work fine.

I have been unable to get a fix, and the GPS spits out lots of
$GPTXT,01,01,01,NMEA unknown msg*58

Which have no apparent meaning. --[[User:Speedevil|Speedevil]] 11:52, 7 April 2008 (CEST)

=== Possible GPS programs ===

As people develop more sophisticated GPS applications, please note them here.

Here are some ideas for possibilities:

* Cairo-based mapping
* Routing
* [[Openstreetmap]] a map viewer, annotation, and editing system.
* [http://wiki.openstreetmap.org/index.php/Pyroute Pyroute] is a routing program written in Python by Ojw, and a mobile phone GUI for maps, GPS, and routing.
* [[GPS-Trail]] a simple trail logger.
* [[GPS_Navigation#roadmap|roadmap]] mapping system using freely available maps (US census TIGER, DGLib, shapefiles).
* [[Geocaching]] paper chase for advanced users
* Set Profile (Mute, etc.) to coordinates (ex. At work)
* [[qpegps]] qtopia (arm PDA) based map viewer with gps features
* [[Navit]] a car navigation system with routing engine.
* [http://www.tangogps.org TangoGPS] works very well, downloads maps on demand and stores them for later use, very efficient.
* [[QMapControl]] Qtopia based mapping widget. Displays maps and custom data, also other widgets can be bound to coordinates. GPS parser for the gllin output included.
* [http://lists.openmoko.org/pipermail/community/2007-July/007252.html collection of ideas]
* [http://www.kflog.org/cumulus/ Cumulus] GPS software for glider pilots (and pilots in general), has a port for Qtopia and pulls (world) maps from the KFLog flight planner project. I think someone has put a project like this on the projects website [http://projects.openmoko.org/projects/openvario/ here].

== Using the Neo's GPS on a Laptop ==

*First be sure you have gllin installed on the Neo.
*On host type: '''nc -vvn -l -p 5000 > /tmp/nmeaNP'''
*On the Neo type: '''nc 192.168.0.200 5000 < /tmp/nmeaNP'''
*
*On the host PC install GPSD, your GPS is attached as /tmp/nmeaNP
*start gpsd on host with: '''gpsd -p /tmp/nmeaNP'''
*run your application! I used gpsdrive and it works better than my stand-alone GPS.
*Tested with RoadNav.Works great!
*
*With this in mind if you have an unlimited data package you could export this over the internet.
*the possibilities are limitless.

== Bluetooth GPS relay ==

To make your neo appear like a regular bluetooth GPS:

*Power up the bluetooth radio
*Run the gllin script
*run '''sdptool add SP'''
*run '''rfcomm watch 0 1 sh -c "cat /tmp/nmeaNP >/dev/rfcomm0" &'''

[[Category:GPS]]

[[category:Documentation]]
[[category:Standard]]

Flashing the Neo 1973

2008-04-03T00:06:49Z

Speedevil: caveat

This describes how to update your Neo1973 to the latest software. We'll update the kernel, the root filesystem and optionally u-boot [[partitions]] in the internal flash memory.

{{warning|If you're updating u-boot and don't have a [[Debug Board]], you might render your unit unusable if the flashing procedure is interrupted}}

{{warning|If you have an older U-boot and upload a rootfs image that is smaller than the previous one, or if you were writing to the smaller jffs2 rootfs, just flashing won't work - you need to run a "[[Nand_erase|nand erase rootfs]]" before you then upload your rootfs, but better run the "nand erase rootfs" every time before you flash a new rootfs, it is quick and saves you the time of a second rootfs upload. Attention: If you [[Nand_erase|erase NAND]] without mentioning the partition to be erased, u-boot will be wiped out and the Neo will be bricked}}

== Files to download ==
{{Note|
* MacOS X users: please refer to [[MacOS_X]].
* Users without Linux please refer to [[No_Linux]] for the moment.
}}

The rootfs & kernel images you download need to match. The loadable modules for the kernel are in /lib/modules/ on the rootfs [[partition]] - if you get the wrong combination, you will get some error messages during bootup that it cannot access /lib/modules/x.y.z-moko123 - in this case swap either the kernel or the rootfs to match the other's version. Unfortunately the rootfs filename does not seem to tell what kernel version it is compatible with, you just have to try a few. '''NOTE:''' At least some combinations seem to boot up fine even if the module versions mismatch so be sure to check the console while it's booting after flashing.

The "moko123" in the error message example above indicates the openmoko patchset version.

Necessary files are at:
*http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/neo1973/?C=M;O=D

*http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/?C=M;O=D (Daily unstable builds)

*http://buildhost.automated.it/OM2007.2/?M=D (Location of more current unofficial builds.)

A list of download locations can be found at [[Repositories]]. See [[Phase 1 Software Testing]] for a list of tested images.

Changelogs can be found at:
*http://cia.vc/stats/project/openembedded/.rss

*http://cia.vc/stats/project/openmoko/.rss

Get:
* [[dfu-util]] (the precompiled binary on http://buildhost.openmoko.org is for Linux/i386)
** (this is the part that runs on the PC, that pushes the files across the USB to the phone)
* openmoko-devel-image-fic-gta01-2007********.rootfs.jffs2
* uImage-2.6.21.*-moko*-r*_0_****_0-fic-gta01.bin
* for phase 0 (Bv03) phones:
** Tested by a few people: u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin MD5SUM: 60c5aeba1bd6642b05b3a5e6f2dafe83
** Tested by hrw: u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2062.bin MD5SUM: 716f1eba9b0f2be4a0a3be4a56724935
* for phase 1 phones, uboot update should not be necessary.

== Preparing the device for DFU mode ==

You'll need to boot your openmoko into uboot menu. To do this:

* Unplug all usb devices from the host.
* Hold the phone's [[Neo1973 AUX Button | AUX button]] and then press the phone's [[Neo1973 Power Button | POWER button]].
** You'll need to hold the POWER button for about 4 seconds before the device will turn on. Otherwise the screen will only flash white for a second and the phone won't power up.
* The u-boot menu should appear:
<pre>
U-Boot ..

=== BOOT MENU ===

BOOT
Set console to USB
Set console to serial
Power off
Boot from SD
Factory reset

Press [AUX] to select, [POWER] to execute.
</pre>

* Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

'''Note:''' If the bootloader remains inactive for about 30 seconds, that is no keypresses or no use of the serial console, the device will automatically power down.
You can prevent this by just pressing the AUX button every 30 seconds or so or by telling the bootloader to not exhibit this behaviour.
To do so, please connect to the bootloader:

<pre>
cu -l /dev/ttyACM0
GTA01Bv4 # setenv boot_menu_timeout 65000
GTA01Bv4 # saveenv
</pre>
For those that are unfamiliar with cu, to exit you need to press "~."

(You may have to install the uucp package to have access to cu, and maybe also "<code>chown uucp:uucp /dev/ttyACM0</code>" as root before it will work)

No further navigation is needed in u-boot - the device will automatically start flashing the images when told to do so by dfu-util below. After flashing all the files, you can choose the "Boot" option to boot the newly flashed stuff.

== Actually flashing things into the device ==

Double check that u-boot matches your hardware version. You'll probably only want to update u-boot if you have the [[debug board]] for fixing failed u-boot updates. You can also check the current [[partitions]].

Note: It may be necessary to run the application as root (at least in Ubuntu and Debian).

Note: In case there are more than one available usb devices use -d 0x1457:0x5119 option.

To update u-boot:

{{Warning|Do not update u-boot unless you have [[debug board]] or are really sure about what you are doing. Flashing a wrong u-boot image will brick your device! Note especially that image below is for GTA01B_v03, not GTA01B_v04

./dfu-util -a u-boot -R -D u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin}}

To update the kernel:
./dfu-util -a kernel -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin
Flashing the kernel will probably take less than 1 minute. If you're having trouble, you may want to compare the output that you see to a "known good" [[Flashing openmoko/Known good kernel flash U-Boot output | U-Boot]]/[[Flashing openmoko/Known good kernel flash dmesg output | dmesg]]/[[Flashing openmoko/Known good kernel flash dfu-util output | dfu-util]] output. The phone display should show "Starting DFU DOWNLOAD to partition 'kernel'.

To update the root filesystem:
./dfu-util -a rootfs -R -D ./Openmoko-devel-image-fic-gta01-20070501054014.rootfs.jffs2

Flashing the root filesystem will probably take around 13 minutes. Note that it can take over an hour if you are using a XEN VM for doing the flash.

Here is some "known good" output from [[Flashing openmoko/Known good rootfs flash U-Boot output | U-Boot]], [[Flashing openmoko/Known good rootfs flash dmesg output | dmesg]], and [[Flashing openmoko/Known good rootfs flash dfu-util output | dfu-util]]. The phone display should show "Starting DFU DOWNLOAD to partition 'rootfs'.

Notice that it's not normally necessary to update the modules anymore. It's just for people with special needs.

...now, you'll end up with system that boots, but does not see audio/SD card. You'll need to download corresponding modules.tgz and copy them over to openmoko. - UPDATE: GTA01 phones appear to not need this step, as long as you have installed a kernel that matches the version of the modules contained in the root image ('uname -r' will show the kernel version, and 'ls /lib/modules/' will show the modules that are present).

VERY IMPORTANT NOTE (I would consider that as a design flaw - either dfu-util should do it automatically): If you upload rootfs image that is smaller that previous one it won't work - you need to attach to the u-boot bootloader, erase NAND first and then upload your rootfs:

<pre>
cu -l /dev/ttyACM0
GTA01Bv3 # nand erase rootfs
</pre>

Old versions of u-boot are buggy: You may have to press the AUX button every 25 seconds or so to prevent the phone from going to sleep while being flashed. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase rootfs.

Good luck!

== Where to go from here ==

So, now you have one of the more recent kernel and rootfs images, or one of the (semi)official ones, whats next?

You probably want to set up [[USB_Networking]] and then configure your Neo1973 some more.

Do not forget to update your Neo1973 using

ipkg update && ipkg upgrade

and have a look at additional ipkg [[repositories]].

== Troubleshooting notes ==

If you're facing errors in seemingly random places during the flashing of images, most likely the USB hub or cable through which your Neo1973 is connected is of too poor quality. It is recommended that you always connect the phone directly to the host when using dfu-util.

If dfu-util reports a message like the following, before it starts flashing:<pre>
Resetting USB...
not at least 2 device changes found ?!?
Lost device after RESET?</pre> just retry the command - it should work on a second run.

This message can also occur if you connect the usb cable before you are in the bootloader menu. You must carefully follow the sequence described at the beginning of this article and not connect the USB cable too early.

dfu-util does not seem to be able to download files if run from linux running under
VMWare on a Windows OS host.

See other notes on [[Dfu-util]] page.

[[Category:Software]]
[[Category:Applications]]
[[Category:Openmoko]]
[[Category:Guides]]

MokoMakefile

2008-03-31T16:03:06Z

Speedevil: /* Build issues */ add where it puts stuff.

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 Neo1973 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 fulfilled 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 dependencies 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 cogito

apt-get install libncurses5-dev zlib1g-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 ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

===== SuSE =====
For building OpenMoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man and [http://download.opensuse.org/repositories/devel:/tools:/scm/openSUSE_Factory/repodata/repoview/Development.Tools.group.html monotone]
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

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.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:
ENABLE_BINARY_LOCALE_GENERATION = "0"

== Building OpenMoko with MokoMakefile ==

1 - Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):
mkdir ~/moko ; cd ~/moko
2 - Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.projects.openmoko.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

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973

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

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.
You can then [[Flashing openmoko||flash these.]]

If not, and 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.

If you see:

ERROR: No providers of build target u-boot-openmoko (for [])

then look back in the log to see if you encountered an earlier error while building the openmoko-devel-image target. The above error is a side-effect of MokoMakefile's logic to handle the re-naming of "uboot-openmoko" to "u-boot-openmoko".

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

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

=== Useful commands ===
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make openmoko-devel-image : build the full development image

; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make openmoko-toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[OpenMoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

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

; make update : to update the OpenMoko repository checkout and the MokoMakefile patches to the latest version

==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 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!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".

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

[[Category:Software]]
[[Category:Applications]]
[[Category:Application Developer]]

GSM network registration

2008-03-18T23:25:12Z

Speedevil: /* Results table */ add when

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||PAYG with phone 7/2007||GTA01||Moko1||YES||Just fine||no
|-
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no
|-
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the re-registering loop starts once per minute|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]
|-
| [mailto:ahvenas@gmail.com Henrik Pihl] || Kuressaare, Estonia || Elisa || || GTA01Bv4 || Moko4 || YES || Normal, can register to the network immediately, but starts reconnecting to the network in the first minutes.|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=555&action=view log]
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || Era (Heyah) || prepaid, bought in October 2007, never charged, expired || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Card expired, home network rejects it with CME Error 32 (emergency calls only), system displays "Registering..." for several minutes. || NO
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || PlusGSM || prepaid, several years old, not charged || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Registered after entering PIN. Normal work after register. || NO
|-
| [mailto:plr@udgaard.com Peter Rasmussen] || Copenhagen Denmark || DK Sonofon || Pre-paid BiBob service since Oct. 2007 || GTA01Bv4 || Moko1 || YES || Registered immediatly after entering PIN. Works after that. No /tmp/gsm.log appears || NO
|-
| [[User:Kevin_Dean | Kevin Dean]] || Washington DC Metro Area, USA || T-Mobile || || GTA01Bv4 || Moko1 || YES || Normal, can register to the network immediately, no PIN needed|| [http://www.monochromementality.com/data/files/logs/openmoko/2008-03-17/gsm.log.edited Log (Replaced my wife's # with 9991231122)]
|-
| [[User:Dennis_Wollersheim | Dennis Wollersheim]] || Melbourne, Australia || Telstra || || GTA01Bv4 || Moko4 || Yes || Registers quickly, reregisters every 30 seconds or so|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=556&action=view gsm log]
|-
| [[User:thomasg | Thomas Gstädtner]] || Nuremberg, Germany || T-Mobile (Ericsson RBS2206, GSM900) || 2004 || GTA01Bv4 || Moko 1 || Yes || Registers nearby immediately, w/ PIN or w/o || NO
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA01Bv4 || Moko 1 || Yes || No problems || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA02 || Moko 6 || No || Does not register, pin entry works, net scan also. || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || e-plus || 200x || GTA02 (same as above) || Moko 6 || No || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Ipswich, UK || Virgin || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Lelystad, Netherlands || Virgin (Roaming on T-Mobile NL) || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Orange (Amena) || 082007 || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Vodafone || phone > 3 years || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[User:Joachim | Joachim Jaeger]] || Eschbach, Germany || O2 || Fonic prepaid card, 01/2008 || GTA01Bv4 || Moko 4 || YES || Registers immediately after entering PIN. Normal work after register. || NO
|}

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

GSM network registration

2008-03-18T23:24:04Z

Speedevil: /* Results table */ add how I got it

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||PAYG with phone||GTA01||Moko1||YES||Just fine||no
|-
| [mailto:erin_yueh@openmoko.com Erin Yueh] || Taipei, Taiwan || TW mobile || || GTA02BV5 || Moko6 || NO || Normal, can register to the network immediately|| no
|-
| [mailto:marcus.bauer@gmail.com Marcus Bauer] || Nice, France || Orange || || GTA01Bv4 || Moko4 || YES || Registers immediately and stays registered for ~10 minutes before the re-registering loop starts once per minute|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=554&action=view log]
|-
| [mailto:ahvenas@gmail.com Henrik Pihl] || Kuressaare, Estonia || Elisa || || GTA01Bv4 || Moko4 || YES || Normal, can register to the network immediately, but starts reconnecting to the network in the first minutes.|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=555&action=view log]
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || Era (Heyah) || prepaid, bought in October 2007, never charged, expired || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Card expired, home network rejects it with CME Error 32 (emergency calls only), system displays "Registering..." for several minutes. || NO
|-
| [[User:MarcinHrwJuszkiewicz | Marcin 'Hrw' Juszkiewicz]] || Poznań, Poland || PlusGSM || prepaid, several years old, not charged || GTA01Bv4 || phase0 phone (red PCB) with old GSM firmware || YES || Registered after entering PIN. Normal work after register. || NO
|-
| [mailto:plr@udgaard.com Peter Rasmussen] || Copenhagen Denmark || DK Sonofon || Pre-paid BiBob service since Oct. 2007 || GTA01Bv4 || Moko1 || YES || Registered immediatly after entering PIN. Works after that. No /tmp/gsm.log appears || NO
|-
| [[User:Kevin_Dean | Kevin Dean]] || Washington DC Metro Area, USA || T-Mobile || || GTA01Bv4 || Moko1 || YES || Normal, can register to the network immediately, no PIN needed|| [http://www.monochromementality.com/data/files/logs/openmoko/2008-03-17/gsm.log.edited Log (Replaced my wife's # with 9991231122)]
|-
| [[User:Dennis_Wollersheim | Dennis Wollersheim]] || Melbourne, Australia || Telstra || || GTA01Bv4 || Moko4 || Yes || Registers quickly, reregisters every 30 seconds or so|| [http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=556&action=view gsm log]
|-
| [[User:thomasg | Thomas Gstädtner]] || Nuremberg, Germany || T-Mobile (Ericsson RBS2206, GSM900) || 2004 || GTA01Bv4 || Moko 1 || Yes || Registers nearby immediately, w/ PIN or w/o || NO
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA01Bv4 || Moko 1 || Yes || No problems || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || vodafone d2 || 200x || GTA02 || Moko 6 || No || Does not register, pin entry works, net scan also. || No
|-
| [[User:emdete | emdete]] || Duesseldorf, Germany || e-plus || 200x || GTA02 (same as above) || Moko 6 || No || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Ipswich, UK || Virgin || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[User:ScaredyCat | ScaredyCat]] || Lelystad, Netherlands || Virgin (Roaming on T-Mobile NL) || 2007 || GTA01 || Moko 1 || Yes || No problems || No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Orange (Amena) || 082007 || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[user:jluis|jluis]] || Barcelona, Spain || Vodafone || phone > 3 years || GTA01Bv4 || Moko1 || YES || No problems|| No
|-
| [[User:Joachim | Joachim Jaeger]] || Eschbach, Germany || O2 || Fonic prepaid card, 01/2008 || GTA01Bv4 || Moko 4 || YES || Registers immediately after entering PIN. Normal work after register. || NO
|}

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