Openmoko - User contributions [en]

File:Neo front 3.gif

2009-03-20T13:36:07Z

Flerchjj: uploaded a new version of "Image:Neo front 3.gif": Improve timing on loop so dwells at 1st & last frame longer. Also got rid of some extra blank frames.

File:Neo front 3.gif

2009-03-20T13:13:04Z

Flerchjj: uploaded a new version of "Image:Neo front 3.gif": Made continuous looping copy of gif. May want to edit original timing some. Spacing is/was odd & irregular between every transition.

Mac OS X

2008-08-10T22:08:04Z

Flerchjj: /* Testing Your Connection */

Welcome to the Openmoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 and Neo Freerunner with Mac.

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here is a detailed instruction:
# download Version 1.4 or later of Openmoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

To flash the kernel:
Openmoko Flasher.app/Contents/MacOS/dfu-util -a kernel -R -D uImage
To flash the root filesystem:
Openmoko Flasher.app/Contents/MacOS/dfu-util -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko Flasher.app/Contents/MacOS/dfu-util -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===

The <code>screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem00000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are two drivers you can use to talk to the RNDIS/Ethernet Gadget that the Neo1973 presents to its host system. The main difference between them is stability, but both have their own problems. Leopard needs further testing (Apple revised the driver and the Network System Settings).

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame MacOSX for because it tries to make network configuration simpler based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the device is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether.

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== AJZaurusUSB driver ===

You can also use the open source driver from [http://www.dsitri.de/wiki.php?page=AJZaurusUSB]. It was developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.3, 10.4 and 10.5.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the neo, because the driver provides a constant ethernet address independently what the Neo says. Only flashing a new kernel might force you to update.

Issue: This driver is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Neo! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank.

You can also [[scp]] files back and forth or share displays with X11. Additional software and configuration could allow telnet, SMB, or many other possibilities using the TCP/IP network over your USB connection.

Try pinging your Mac PC from the Neo
ping 192.168.0.200

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com
If that doesn't work then see [[USB_Networking#Configure_Default_Neo_DNS | Configuring Default Neo DNS]] to try and resolve the issue.

Congordulations Elizagreth!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking
http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#PPP_Networking

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

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

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11. xhost +192.168.0.202. On the Neo: export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [[http://www.quantum-step.com/wiki.php?page=OpenMoko-Edition More Info]]
An SDK for Xcode/Interface Builder is also available: [[http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker]] [[http://www.quantum-step.com/wiki.php?page=SDK More Info]]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[[http://www.quantum-step.com/download/OpenMoko-Edition/mkfs.jffs2.tgz mkfs.jffs2]] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3]] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [[http://www.macports.org/ports.php?by=name&substr=gnueabi]] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]

USB Networking

2008-08-10T21:50:23Z

Flerchjj: /* OS or Distro Specific Configuration & Making it Permanent */

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

If Desktop/Laptop has a DNS server or is proxying DNS:
nameserver 192.168.0.200
or just put in another DNS Server - for example:
nameserver 212.147.10.10

Some Linux and Windows systems have DNS servers, especially those configured as servers, but in general they do not. You can install packages such as ''bind9'' or ''dnsmasq'' to run your own DNS server. If you have a DNS server then Test Your Connection. Otherwise you may want to proxy DNS from your Desktop/Laptop.

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

== Hostnames ==

If you become tired of remembering and typing in the ip address of the Neo (for scp, telnet, SSH, SMB, or whatever), you can give it an easy to remember hostname.

Open and enter the following line in your desktop's /etc/hosts:
192.168.0.202 openmoko
Now instead of typing the full ip address in commands like:
ssh 192.168.0.202@openmoko
You can replace the full ip with the hostname like:
ssh root@openmoko

It may also be helpful to some to edit the Neo's /etc/hosts to use "desktop" or "laptop" instead of 192.168.0.200

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= OS or Distro Specific & Automatic Configuration =

Based on [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] by Marcin 'Hrw' Juszkiewicz.
These instructions should keep you from having to run the Simple Manual Linux Configuration every time you plug in and want to connect to an Openmoko device. One run and then you're done!

If the Simple Manual Linux Configuration does not work for your OS or Distro (MacOS X, MS Windows, etc) there may be instructions here that work for you.

== MacOS X ==
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].

== Windows ==
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

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

add

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

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

= SSH Extras =

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

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

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

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

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

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone without a password prompt.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

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

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=openmoko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-10T21:38:53Z

Flerchjj: Made "Make it Permanent" title more descriptive

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

If Desktop/Laptop has a DNS server or is proxying DNS:
nameserver 192.168.0.200
or just put in another DNS Server - for example:
nameserver 212.147.10.10

Some Linux and Windows systems have DNS servers, especially those configured as servers, but in general they do not. You can install packages such as ''bind9'' or ''dnsmasq'' to run your own DNS server. If you have a DNS server then Test Your Connection. Otherwise you may want to proxy DNS from your Desktop/Laptop.

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

== Hostnames ==

If you become tired of remembering and typing in the ip address of the Neo (for scp, telnet, SSH, SMB, or whatever), you can give it an easy to remember hostname.

Open and enter the following line in your desktop's /etc/hosts:
192.168.0.202 openmoko
Now instead of typing the full ip address in commands like:
ssh 192.168.0.202@openmoko
You can replace the full ip with the hostname like:
ssh root@openmoko

It may also be helpful to some to edit the Neo's /etc/hosts to use "desktop" or "laptop" instead of 192.168.0.200

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= OS or Distro Specific Configuration & Making it Permanent =

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

== MacOS X ==
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].

== Windows ==
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

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

add

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

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

= SSH Extras =

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

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

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

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

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

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone without a password prompt.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

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

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=openmoko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

Neo 1973 and Windows

2008-08-10T21:34:42Z

Flerchjj: /* USB Ethernet emulation */

This page tries to collect some information on how to use your Neo1973 together with a computer running a Microsoft(R) Windows(TM) series operating system.

Please note that this is not really supported, and that the OpenMoko developers themselves only use Linux for testing.

Also note that Windows appears to not recognize and communicate with the neo as a USB device unless you install the .inf file below, and hence you will always have to [[forcing fast charge mode|force fast charge]] to recharge using a usb connection to a Windows machine unless you install that .inf.

== Connecting to the phone ==

=== Bluetooth connection ===

How to connect to Windows XP via Bluetooth is described here: [[Manually_using_Bluetooth#Bluetooth_networking_with_a_Windows_XP_system]]

=== USB Ethernet emulation ===
{{note|For Windows XP USB RNDIS networking ''finally works'' as of Kernel 2.6.22.5-moko11 using the procedure described below.}}

{{note|For Vista this procedure works with the 2.6.24 kernel that ships with the Neo Freerunner. The initial SSH connection seems a little slow however.}}

# Download http://privat.wmo.de/~c_schweers/NeoRndis.inf ([[NeoRndis.inf|Listing of NeoRndis.inf]]) to somewhere convenient on your Windows machine. If the file is not reachable, you can download another working inf file here: http://users.informatik.uni-halle.de/~rabe/neo/Neo1973.inf ([[Neo1973.inf|Listing of Neo1973.inf]])
# Power up your Neo1973, let it boot into OpenMoko, and then connect its USB port to the Windows machine, using a standard USB-A to USB-mini-B cable. Note that if you connect the cable ''before'' powering the phone on, Windows will detect a device presented by the [[Boot lader|boot loader]]. This probably isn't what you want. Let the phone power up first.
# Assuming the new drivers are downloaded and accessible as above, Windows should detect the Neo1973 and prompt you for a driver for a "RNDIS/Ethernet Gadget". Select to specify your own driver, and then choose the NeoRndis.inf file you downloaded earlier. This file tells Windows XP to use its own built-in RNDIS driver for the device.
# Windows may complain of "reduced network connectivity". This is because it expects to be able to get an address automatically from the Neo1973 and it doesn't provide one in the default setup. To fix this, see the next step.
# Go into the Windows network configuration for the new USB networking adapter and set the IP address of the interface to 192.168.0.200.

You should now be able to connect to your Neo1973 on 192.168.0.202 via ssh (e.g. putty)

Getting a Blue Screen of Death (BSOD) in windows XP? Some extra drivers are automatically installed with new devices (e.g. "SecureRemoteMiniPort"). Try disabling them in the device manager while the Neo is not connected. You need to select "Show hidden devices" in the view menu to see them. Then reconnect the Neo.

=== Connection to the Internet ===

If you want to connect to the internet from your Neo via Windows XP, e.g. for doing ipkg update/upgrade, you need to set up IP forwarding and routing properly.

==== Option 1, using Windows ICS ====

An easy way to do this is to use Windows Internet Connection Sharing.

To do this, you need to create a network bridge which contains the usb connection to the Neo.

Then you tell Windows to share the WAN connection (i.e. the network interface which connects your Windows system to the internet) with the new bridge.

Then you manually set the IP address of the bridge to 192.168.0.200

After you have done all this, the Neo will be able to route through the Windows machine out to the internet. DNS queries will also be proxied by the Windows machine. Of course, /etc/resolv.conf on the Neo needs to be set to your local DNS or a free DNS.

'''New''' When you have LAN with network address 192.168.0.0 you have to do some hacking.
1. Edit /etc/network/interfaces and set for usb0
'' address 192.168.2.202
netmask 255.255.255.0
network 192.168.2.0
gateway 192.168.2.1
''
On Windows go to Network settings, ''pull out LAN cable'' (so there's no connection with local DHCP server which conflicts with IP 192.168.0.1), enable connection sharing for Neo-USB cable. Then edit Neo-usb interface settings and change it's IP address to 192.168.2.1 and set gateway for yours 192.168.0.x (other which you have). Apply changes with OK. Put in net cable. Enjoy net on NEO.

'''Example: Setup for wifi only internet connection (windows xp and Neo FreeRunner)'''
# Once the Network Connections window shows both "Wireless Network Connection Status:Connected" and "openmoko Status:Connected" Right click on Wireless Network Connection and goto Properties. Select Advanced tab, and turn on Internet Connection sharing. Choose the openmoko network.
# If you get the error: the ip address is already in use. Change your wireless router address away from 192.168.0.2, to something like 192.168.1.2
# Windows will change the ip address of openmoko network to 192.168.0.1 and the Network Connections window will show "Wireless Internet Connection Status: connected,shared"
# Right click on openmoko network and goto Properties. Change the ip address of openmoko network to 192.168.0.200
# Login to openmoko using Putty (ssh client for windows) 192.168.0.202

==== Option 1.5, using a Network Bridge ====

Just bridge the USB and Ethernet networks together (Win XP).

To do this, you need to create a network bridge which contains the usb connection to the Neo and your normal Ethernet (or WiFi) connection (the one you use to go on the internets).

Then you set up the bridge like your Ethernet was (DHCP or static IP, e.g. 10.10.0.foo) and the Neo to be in the same subnet as the bridge (10.10.0.bar)

After you have done all this, the Neo will be able to route through the Windows machine out to the internet. DNS queries will also be proxied by the Windows machine. Of course, /etc/resolv.conf on the Neo needs to be set to your local DNS or a free DNS.

==== Option 2, using AnalogX ====

AnalogX is a lightweight, free network proxy for Windows. It can proxy HTTP, FTP, SMTP and other protocols. It's very easy to set up and works with any software on the phone that supports proxies (eg. opkg).

* Download and install AnalogX onto your Windows PC (http://www.analogx.com)
* Run AnalogX. The default configuration should be ok: open mode, all protocols on.
* Connect your phone using the USB cable as normal.
* Configure opkg to use the proxy by editing /etc/opkg/opkg.conf. There's 2 lines to uncomment and change.
** option http_proxy http://192.168.0.200:6588
** option ftp_proxy http://192.168.0.200:21
* opkg should now work via the proxy.

Other apps like [[Minimo]] can also be configured to use a proxy. Use the HTTP proxy URL as above.

==== Option 3, using IP Forwarding and extra routing ====

An alternative way is to do it manually:

In the Windows registry, go to:
Hkey_Local_Machine\System\CurrentControlSet\Services\Tcpip\Parameters
and set
REG_DWORD: "IPEnableRouter" to "1"
Be aware that IP Forwarding can be a security risk.

Then, if there is a router between your Windows XP system and the internet, you also need to tell the router how to get back to your Neo, so you need to set a route on it for 192.168.0.0/255.255.255.0 to your Windows XP LAN interface IP address. Windows will then forward the packets to the Neo.

=== Further references ===
* http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx
* http://maemo.org/maemowiki/USBnetworkingWinXP
* http://docwiki.gumstix.org/Setting_up_USBnet
* http://handhelds.org/moin/moin.cgi/WindowsXpUsbNetworkHowTo

[[Category:Technical]]
[[Category:Documentation]]

USB Networking

2008-08-10T21:26:20Z

Flerchjj: Put OS's with Simple Manual Linux Configuration issues first

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

If Desktop/Laptop has a DNS server or is proxying DNS:
nameserver 192.168.0.200
or just put in another DNS Server - for example:
nameserver 212.147.10.10

Some Linux and Windows systems have DNS servers, especially those configured as servers, but in general they do not. You can install packages such as ''bind9'' or ''dnsmasq'' to run your own DNS server. If you have a DNS server then Test Your Connection. Otherwise you may want to proxy DNS from your Desktop/Laptop.

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

== Hostnames ==

If you become tired of remembering and typing in the ip address of the Neo (for scp, telnet, SSH, SMB, or whatever), you can give it an easy to remember hostname.

Open and enter the following line in your desktop's /etc/hosts:
192.168.0.202 openmoko
Now instead of typing the full ip address in commands like:
ssh 192.168.0.202@openmoko
You can replace the full ip with the hostname like:
ssh root@openmoko

It may also be helpful to some to edit the Neo's /etc/hosts to use "desktop" or "laptop" instead of 192.168.0.200

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= Make it Permanent =

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

== MacOS X ==
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].

== Windows ==
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

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

add

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

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

= SSH Extras =

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

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

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

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

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

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone without a password prompt.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

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

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=openmoko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-10T21:04:35Z

Flerchjj: Added DNS Hostname info back in & cleaned up

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

If Desktop/Laptop has a DNS server or is proxying DNS:
nameserver 192.168.0.200
or just put in another DNS Server - for example:
nameserver 212.147.10.10

Some Linux and Windows systems have DNS servers, especially those configured as servers, but in general they do not. You can install packages such as ''bind9'' or ''dnsmasq'' to run your own DNS server. If you have a DNS server then Test Your Connection. Otherwise you may want to proxy DNS from your Desktop/Laptop.

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

== Hostnames ==

If you become tired of remembering and typing in the ip address of the Neo (for scp, telnet, SSH, SMB, or whatever), you can give it an easy to remember hostname.

Open and enter the following line in your desktop's /etc/hosts:
192.168.0.202 openmoko
Now instead of typing the full ip address in commands like:
ssh 192.168.0.202@openmoko
You can replace the full ip with the hostname like:
ssh root@openmoko

It may also be helpful to some to edit the Neo's /etc/hosts to use "desktop" or "laptop" instead of 192.168.0.200

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= Make it Permanent =

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

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

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

add

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

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= SSH Extras =

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

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

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

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

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

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone without a password prompt.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

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

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=openmoko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-10T20:35:33Z

Flerchjj: removed other DNS sections after consolidated

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

If Desktop/Laptop has a DNS server or is proxying DNS:
nameserver 192.168.0.200
or just put in another DNS Server - for example:
nameserver 212.147.10.10

Some Linux and Windows systems have DNS servers, especially those configured as servers, but in general they do not. You can install packages such as ''bind9'' or ''dnsmasq'' to run your own DNS server. If you have a DNS server then Test Your Connection. Otherwise you may want to proxy DNS from your Desktop/Laptop.

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
ping www.google.com
If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= Make it Permanent =

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

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

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

add

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

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= SSH Extras =

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

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

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

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

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

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone without a password prompt.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

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

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=openmoko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-10T20:32:05Z

Flerchjj: consolidated DNS settings & cleaned up

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

If Desktop/Laptop has a DNS server or is proxying DNS:
nameserver 192.168.0.200
or just put in another DNS Server - for example:
nameserver 212.147.10.10

Some Linux and Windows systems have DNS servers, especially those configured as servers, but in general they do not. You can install packages such as ''bind9'' or ''dnsmasq'' to run your own DNS server. If you have a DNS server then Test Your Connection. Otherwise you may want to proxy DNS from your Desktop/Laptop.

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
ping www.google.com
If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= Make it Permanent =

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

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

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

add

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

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= More on DNS =

== Hostnames ==

Instead of using the IP address, instead enter in your desktop's /etc/hosts:

192.168.0.202 openmoko

Then instead type:

ssh root@openmoko

== DNS proxying ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you). There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

= SSH Extras =

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

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

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

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

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

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone without a password prompt.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

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

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=openmoko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

USB Networking

2008-08-10T20:07:29Z

Flerchjj: added test items & cleaned up for more consistency with Mac setup

= OpenMoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to eg 192.168.1.(something) might save you a lot of troubleshooting later. The guides to set up USB networking for your FreeRunner assume that your router/desktop IP range differs from the USB network IP range.

A discussion of this is here http://lists.openmoko.org/pipermail/support/2008-August/001283.html

= Simple Manual Linux Configuration =

Try this first. If it works, then you can add permanent configuration or use more sophisticated setups below:

(as root on your desktop):

iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ifconfig usb0 192.168.0.200

If your Internet connection is also in the range 192.168.0.x then instead you might want to use:

ifconfig usb0 192.168.0.200 netmask 255.255.255.248

Then (ideally, not as root):

ssh root@192.168.0.202

The default password is blank.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support, in particular, you will need to have enabled full masquerading in the kernel and USB networking options enabled. For default kernels in many Linux distributions, this will already be the case. If not, you will need to enable:

* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER

Both USB networking options are available in the ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters -> Multipurpose USB Networking Framework''. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

It can be complex to set all the correct options for masquerading in the kernel if they are not turned on. This could be detailed further.

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner. It should contain:

nameserver 192.168.0.200 or just put in another DNS Server for example "nameserver 212.147.10.10"

Which means that by default it expects your desktop to have a DNS server. On some Linux and Windows systems this is true, especially those configured as servers, but in general it is not. You can install packages such as ''bind9'' or ''dnsmasq''. See the section below on [[USB Networking#More on DNS|More on DNS]] for other solutions.

Test if it works:

ping www.google.com

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

=== Testing Your Connection ===
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

= Make it Permanent =

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

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.192/26
</pre>

This is more sophisticated than the manual setup. The allow-hotplug stanza ties into Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner's is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

An other possible configuration that adds DNS forward and removes
the iptable changes after the unplugg.

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(cat /etc/resolv.conf | grep nameserver | awk '{ print $2 }' | head -n 1 )

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu Issues ===

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules, editing the two lines at the end of the file:

SUBSYSTEM=="net", DRIVERS=="?*", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

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

LABEL="net_end"

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

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

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)

== Mandriva ==

Tested with Mandriva 2008.1. The idea here is that we will carve out a small (8 hosts) subnet from the main subnet. So our netmask will be 255.255.255.252

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.252
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

/etc/sysconfig/network-scripts/usb0-routes:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.252

Now we need to restart the network system to pick up the changes.

service network restart

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC8 & FC5 ===

/etc/sysconfig/network-scripts/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
# from http://www.handhelds.org/moin/moin.cgi/UsbNet
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}

/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash

. /etc/init.d/functions

cd /etc/sysconfig/network-scripts
. ./network-functions

[ -f ../network ] && . ../network

CONFIG=${1}

need_config ${CONFIG}

source_config

NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`

/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}

/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

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

add

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

== Gentoo ==

Open /etc/conf.d/net and add:

# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )

Create a new init script:

cd /etc/init.d
ln -s net.lo net.usb0

Put iptables into use:

iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.

preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

== MacOS X ==
See the [[MacOS_X#USB_Networking|USB Networking section in the MacOS X article]].

== Windows ==
See the [[Neo1973_and_Windows#USB_Ethernet_emulation|USB Ethernet emulation section in the Neo1973 and Windows]] article.

= More on DNS =

== Hostnames ==

Instead of using the IP address, instead enter in your desktop's /etc/hosts:

192.168.0.202 openmoko

Then instead type:

ssh root@openmoko

== DNS proxying ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you). There are a number of ways to do this:

=== Proxying with dnrd ===

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

=== Proxying with a UDP forwarder ===

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

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

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1

Where <tt>192.168.0.1</tt> is the IP of your router.

= SSH Extras =

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

To avoid ssh added a new line for every ssh host-key to you known_hosts you can add the following to the phone section in ~/.ssh/config

UserKnownHostsFile /dev/null

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

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

ssh-keygen -t rsa

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

# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone without a password prompt.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

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

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

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts).

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows:

ssh -l root -X -v 192.168.0.202

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

If you get an error like this:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the Freerunner before launching the process from your desktop. You can find the value of this variable by using a command such as
ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS
Note that you must run that command on the Freerunner. Back on your desktop, run the process you want with the ''env'' command like this:
env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process''

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=openmoko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:USB]]
[[Category:Hardware]]
[[Category:Implemented]]
[[Category:Networking]]

Flashing the Neo FreeRunner

2008-08-10T19:47:29Z

Flerchjj: cleaned up text

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

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

On a desktop computer when you want to replace the operating system (OS), you would boot it from a CD-ROM drive, then copy OS files from the CD to the internal hard drive. The FreeRunner does not have a CD-ROM drive and files must typically be re-written/flashed directly into internal storage (NAND flash). It is also possible to load all the OS files to and boot from a microSD.

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

The NAND Flash is divided into 3 partitions for the bootloader, kernel, and root filesystem - so each of these components can be flashed separately. For example if you are trying to install a modified kernel, you only have to follow the steps to flash the kernel image.

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

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

== Alternative : running from microSD card ==

You may install this distribution on the microSD card, in order to [[Booting from SD | boot from microSD card]]. That allows you to keep another distribution installed in NAND (for instance to test 2008.08 while still having 2007.2 for default boot).

== Collect the things you need ==

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

You will download that program on your desktop computer. It will allow you to connect to the FreeRunner through the USB cable and control its bootloader. That connection uses a special protocol which addresses the bootloader's interface, and differs from USB networking. There is a separate page to describe it in more detail: [[dfu-util]].

'''Note:''' dfu-util seems to consistently fail with a "-62" error on 64-bit Linux. If you have access to a 32-bit machine, use it instead!

'''MacOS X:''' [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

'''Linux:''' http://buildhost.openmoko.org/releases/Freerunner/dfu-util

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

'''Windows:''' http://projects.openmoko.org/frs/?group_id=166&release_id=162

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

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

Exactly what files you need depends on what you are trying to install. In most cases you will need to install a Kernel and a Root Filesystem (rootfs). In rare cases, when there is a bug you need fixed, you will also install a new bootloader.

Please read [[Distributions]] for choosing the distribution which fits your needs, and then see [[Download]] for downloading.

== Boot the FreeRunner from NOR Flash ==

[[Image:menu15.jpg|thumb|Booting from NOR Flash]]

# Read the other sections of this page first, because you will have 30 seconds to enter the flashing commands, come back here when ready.
# Do not connect the USB cable from the PC to your Neo FreeRunner yet (disconnect it).
# Boot your Neo Freerunner into the NOR uBoot menu for flashing.
## Press and hold AUX button
## Press the Power button until the boot menu comes up
## This menu is labelled '''*** BOOT MENU (NOR) ***'''
## See also [[Booting the Neo FreeRunner]]
# Stay in NOR uBoot menu, do not to select or enter any item in menu. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.
# The FreeRunner only stays at the NOR boot prompt for about 30 seconds and then shuts off unless you do something.
# Connect your Neo to the GNU/Linux or Windows host via a USB cable.
# Now you can enter the dfu-util commands on your PC as described below.
# If the Neo FreeRunner turns off before you press start flashing ('''screen goes black'''), go back to step 2. If you start flashing in time, the phone will not turn off meanwhile.



Note that the dfu-util connection does '''not''' use Ethernet over USB - that is, you should not attempt to set up a usb0 network interface on your GNU/Linux host desktop (on Windows, you need a DFU class driver, or you can use the LibUSB-Win32 driver described on the [[Dfu-util-windows]] page). The dfu-util utility sets up its own connection to the FreeRunner. In fact, you will not be able to make an Ethernet-over-USB connection to the FreeRunner when it is at the uBoot menu; this type of connection is only available when the FreeRunner has booted fully.

After connecting the FreeRunner to your host via USB cable, you can test whether dfu-util "sees" the FreeRunner by executing:

dfu-util -l
If you get error messages from the dfu-util command then try again. Often it works on the second try.

== Do a backup ==

If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]].

== Using dfu-util ==

dfu-util can be used to read flash memory, write memory, and get information from the device.

This is the general command format to write an image file to a (predefined) "partition name" (referred to as ''altsetting'' in dfu-util help/manual) :

dfu-util -a ''altsetting'' -R -D ''file_name''

where: 
-a ''altsetting'' : Specify the altsetting of the DFU interface by name or by number 
-R : Issue USB Reset signalling once we're finished 
-D ''file_name'' : Write firmware from ''file_name'' into device

On Linux, you run dfu-util from a command shell prompt. If you have not put it somewhere on your command path you probably need to prefix it with a "./" like this '''./dfu-util'''.
On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

On Windows, you need to open a command window and run from a command line. Use Start-Run Program and type "cmd" to open a Window.

More detailed manual for gfu-util is available here : [[Dfu-util]]

== Flashing the Kernel ==

The command format is

dfu-util -a kernel -R -D ''/path/to/uImage''

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the Root Filesystem ==

The root filesystem has to be an image in jffs2 format. If the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a rootfs -R -D ''rootfs_filename.jffs2''

where ''rootfs_filename.jffs2'' is the name of the file containing the root filesystem.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the boot loader to the NAND==

The boot loader (U-boot) file should have a .bin extension. As with the root filesystem, if the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a u-boot -R -D ''uboot.bin''

where ''uboot.bin'' is the name of the boot loader binary image file.

''Reminder'': You should have [[Flashing_the_Neo_FreeRunner#Boot_the_FreeRunner_from_NOR_Flash|rebooted from NOR first]], in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates.


(Optional) After an upgrade, you may wish to check that the u-boot version matches the one you have just flashed. You can use 'grep Bootloader /dev/mtdblock1' from a shell on the FreeRunner (and possibly the 1973 as well) to get the '''NAND''' u-boot version, like this:
root@om-gta02:~# grep Bootloader /dev/mtdblock1
Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb

You can grep for the same string in /dev/mtdblock0 to retrieve the '''NOR''' u-boot version:
root@om-gta02:~# grep Bootloader /dev/mtdblock0
Neo1973 Bootloader U-Boot 1.3.2-moko12



== Reboot the FreeRunner from NAND ==

You should now be able to boot into the new images.

Pay attention '''to booting from the NAND flash this time''', in particular if you upgraded the boot-loader (in short: 1. press and hold ''power button'' down, and then 2. press ''aux button'')

The boot menu should be labelled '''*** BOOT MENU (NAND) ***''' this time (see [[Booting#Log_into_U-Boot_in_the_NAND_Flash|booting from NAND]] for more detailed instructions).

[[Category:Flashing Openmoko| ]]

Flashing the Neo FreeRunner

2008-08-10T18:59:39Z

Flerchjj: /* Overview */

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

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

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

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

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

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

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

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

The steps to reflash NAND are

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

== Collect the things you need ==

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

You will download that program on your desktop computer. It will allow you to connect to the FreeRunner through the USB cable and control its bootloader. That connection uses a special protocol which addresses the bootloader's interface, and differs from USB networking. There is a separate page to describe it in more detail: [[dfu-util]].

'''Note:''' dfu-util seems to consistently fail with a "-62" error on 64-bit Linux. If you have access to a 32-bit machine, use it instead!

'''MacOS X:''' [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

'''Linux:''' http://buildhost.openmoko.org/releases/Freerunner/dfu-util

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

'''Windows:''' http://projects.openmoko.org/frs/?group_id=166&release_id=162

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

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

Exactly what files you need depends on what you are trying to install. In most cases you will need to install a Kernel and a Root Filesystem (rootfs). In rare cases, when there is a bug you need fixed, you will also install a new bootloader.

Please read [[Distributions]] for choosing the distribution which fits your needs, and then see [[Download]] for downloading.

== Boot the FreeRunner from NOR Flash ==

[[Image:menu15.jpg|thumb|Booting from NOR Flash]]

# Read the other sections of this page first, because you will have 30 seconds to enter the flashing commands, come back here when ready.
# Do not connect the USB cable from the PC to your Neo FreeRunner yet (disconnect it).
# Boot your Neo Freerunner into the NOR uBoot menu for flashing.
## Press and hold AUX button
## Press the Power button until the boot menu comes up
## This menu is labelled '''*** BOOT MENU (NOR) ***'''
## See also [[Booting the Neo FreeRunner]]
# Stay in NOR uBoot menu, do not to select or enter any item in menu. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.
# The FreeRunner only stays at the NOR boot prompt for about 30 seconds and then shuts off unless you do something.
# Connect your Neo to the GNU/Linux or Windows host via a USB cable.
# Now you can enter the dfu-util commands on your PC as described below.
# If the Neo FreeRunner turns off before you press start flashing ('''screen goes black'''), go back to step 2. If you start flashing in time, the phone will not turn off meanwhile.



Note that the dfu-util connection does '''not''' use Ethernet over USB - that is, you should not attempt to set up a usb0 network interface on your GNU/Linux host desktop (on Windows, you need a DFU class driver, or you can use the LibUSB-Win32 driver described on the [[Dfu-util-windows]] page). The dfu-util utility sets up its own connection to the FreeRunner. In fact, you will not be able to make an Ethernet-over-USB connection to the FreeRunner when it is at the uBoot menu; this type of connection is only available when the FreeRunner has booted fully.

After connecting the FreeRunner to your host via USB cable, you can test whether dfu-util "sees" the FreeRunner by executing:

dfu-util -l
If you get error messages from the dfu-util command then try again. Often it works on the second try.

== Do a backup ==

If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]].

== Using dfu-util ==

dfu-util can be used to read flash memory, write memory, and get information from the device.

This is the general command format to write an image file to a (predefined) "partition name" (referred to as ''altsetting'' in dfu-util help/manual) :

dfu-util -a ''altsetting'' -R -D ''file_name''

where: 
-a ''altsetting'' : Specify the altsetting of the DFU interface by name or by number 
-R : Issue USB Reset signalling once we're finished 
-D ''file_name'' : Write firmware from ''file_name'' into device

On Linux, you run dfu-util from a command shell prompt. If you have not put it somewhere on your command path you probably need to prefix it with a "./" like this '''./dfu-util'''.
On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

On Windows, you need to open a command window and run from a command line. Use Start-Run Program and type "cmd" to open a Window.

More detailed manual for gfu-util is available here : [[Dfu-util]]

== Flashing the Kernel ==

The command format is

dfu-util -a kernel -R -D ''/path/to/uImage''

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the Root Filesystem ==

The root filesystem has to be an image in jffs2 format. If the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a rootfs -R -D ''rootfs_filename.jffs2''

where ''rootfs_filename.jffs2'' is the name of the file containing the root filesystem.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the boot loader to the NAND==

The boot loader (U-boot) file should have a .bin extension. As with the root filesystem, if the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a u-boot -R -D ''uboot.bin''

where ''uboot.bin'' is the name of the boot loader binary image file.

''Reminder'': You should have [[Flashing_the_Neo_FreeRunner#Boot_the_FreeRunner_from_NOR_Flash|rebooted from NOR first]], in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates.


(Optional) After an upgrade, you may wish to check that the u-boot version matches the one you have just flashed. You can use 'grep Bootloader /dev/mtdblock1' from a shell on the FreeRunner (and possibly the 1973 as well) to get the '''NAND''' u-boot version, like this:
root@om-gta02:~# grep Bootloader /dev/mtdblock1
Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb

You can grep for the same string in /dev/mtdblock0 to retrieve the '''NOR''' u-boot version:
root@om-gta02:~# grep Bootloader /dev/mtdblock0
Neo1973 Bootloader U-Boot 1.3.2-moko12



== Reboot the FreeRunner from NAND ==

You should now be able to boot into the new images.

Pay attention '''to booting from the NAND flash this time''', in particular if you upgraded the boot-loader (in short: 1. press and hold ''power button'' down, and then 2. press ''aux button'')

The boot menu should be labelled '''*** BOOT MENU (NAND) ***''' this time (see [[Booting#Log_into_U-Boot_in_the_NAND_Flash|booting from NAND]] for more detailed instructions).

[[Category:Flashing Openmoko| ]]

Mac OS X

2008-08-10T06:35:43Z

Flerchjj: add Terminal flashing details

Welcome to the Openmoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 and Neo Freerunner with Mac.

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here is a detailed instruction:
# download Version 1.4 or later of Openmoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

To flash the kernel:
Openmoko Flasher.app/Contents/MacOS/dfu-util -a kernel -R -D uImage
To flash the root filesystem:
Openmoko Flasher.app/Contents/MacOS/dfu-util -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko Flasher.app/Contents/MacOS/dfu-util -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===

The <code>screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem00000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are two drivers you can use to talk to the RNDIS/Ethernet Gadget that the Neo1973 presents to its host system. The main difference between them is stability, but both have their own problems. Leopard needs further testing (Apple revised the driver and the Network System Settings).

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame MacOSX for because it tries to make network configuration simpler based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the device is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether.

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== AJZaurusUSB driver ===

You can also use the open source driver from [http://www.dsitri.de/wiki.php?page=AJZaurusUSB]. It was developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.3, 10.4 and 10.5.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the neo, because the driver provides a constant ethernet address independently what the Neo says. Only flashing a new kernel might force you to update.

Issue: This driver is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Neo! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank.

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Try pinging your Mac PC from the Neo
ping 192.168.0.200

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

Congordulations Elizagreth!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking
http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#PPP_Networking

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

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

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11. xhost +192.168.0.202. On the Neo: export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [[http://www.quantum-step.com/wiki.php?page=OpenMoko-Edition More Info]]
An SDK for Xcode/Interface Builder is also available: [[http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker]] [[http://www.quantum-step.com/wiki.php?page=SDK More Info]]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[[http://www.quantum-step.com/download/OpenMoko-Edition/mkfs.jffs2.tgz mkfs.jffs2]] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3]] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [[http://www.macports.org/ports.php?by=name&substr=gnueabi]] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]

Mac OS X

2008-08-10T06:14:51Z

Flerchjj: correct 2 switched ip addresses

Welcome to the Openmoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 and Neo Freerunner with Mac.

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here is a detailed instruction:
# download Version 1.4 or later of Openmoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===

The <code>screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem00000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are two drivers you can use to talk to the RNDIS/Ethernet Gadget that the Neo1973 presents to its host system. The main difference between them is stability, but both have their own problems. Leopard needs further testing (Apple revised the driver and the Network System Settings).

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame MacOSX for because it tries to make network configuration simpler based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the device is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether.

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== AJZaurusUSB driver ===

You can also use the open source driver from [http://www.dsitri.de/wiki.php?page=AJZaurusUSB]. It was developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.3, 10.4 and 10.5.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the neo, because the driver provides a constant ethernet address independently what the Neo says. Only flashing a new kernel might force you to update.

Issue: This driver is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Neo! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank.

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Try pinging your Mac PC from the Neo
ping 192.168.0.200

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

Congordulations Elizagreth!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking
http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#PPP_Networking

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

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

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11. xhost +192.168.0.202. On the Neo: export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [[http://www.quantum-step.com/wiki.php?page=OpenMoko-Edition More Info]]
An SDK for Xcode/Interface Builder is also available: [[http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker]] [[http://www.quantum-step.com/wiki.php?page=SDK More Info]]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[[http://www.quantum-step.com/download/OpenMoko-Edition/mkfs.jffs2.tgz mkfs.jffs2]] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3]] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [[http://www.macports.org/ports.php?by=name&substr=gnueabi]] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]

Mac OS X

2008-08-10T06:10:06Z

Flerchjj: re-organize to make more logical flow

Welcome to the Openmoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 and Neo Freerunner with Mac.

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here is a detailed instruction:
# download Version 1.4 or later of Openmoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===

The <code>screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem00000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are two drivers you can use to talk to the RNDIS/Ethernet Gadget that the Neo1973 presents to its host system. The main difference between them is stability, but both have their own problems. Leopard needs further testing (Apple revised the driver and the Network System Settings).

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame MacOSX for because it tries to make network configuration simpler based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the device is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether.

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== AJZaurusUSB driver ===

You can also use the open source driver from [http://www.dsitri.de/wiki.php?page=AJZaurusUSB]. It was developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.3, 10.4 and 10.5.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the neo, because the driver provides a constant ethernet address independently what the Neo says. Only flashing a new kernel might force you to update.

Issue: This driver is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Neo! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.0.200

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank.

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Try pinging your Mac PC from the Neo
ping 192.168.0.202

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

Congordulations Elizagreth!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking
http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#PPP_Networking

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

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

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11. xhost +192.168.0.202. On the Neo: export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [[http://www.quantum-step.com/wiki.php?page=OpenMoko-Edition More Info]]
An SDK for Xcode/Interface Builder is also available: [[http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker]] [[http://www.quantum-step.com/wiki.php?page=SDK More Info]]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[[http://www.quantum-step.com/download/OpenMoko-Edition/mkfs.jffs2.tgz mkfs.jffs2]] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3]] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [[http://www.macports.org/ports.php?by=name&substr=gnueabi]] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]

Mac OS X

2008-08-10T05:57:45Z

Flerchjj: expanded missing parts of testing connection

Welcome to the Openmoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 and Neo Freerunner with Mac.

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here is a detailed instruction:
# download Version 1.4 or later of Openmoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===

The <code>screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem00000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are two drivers you can use to talk to the RNDIS/Ethernet Gadget that the Neo1973 presents to its host system. The main difference between them is stability, but both have their own problems. Leopard needs further testing (Apple revised the driver and the Network System Settings).

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame MacOSX for because it tries to make network configuration simpler based on the assumption of stable Ethernet addresses.

Use this configuration on the new interface:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want to use:
<pre>
Subnet: 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Neo! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.0.200

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank.

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Try pinging your Mac PC from the Neo
ping 192.168.0.202

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

Congordulations Elizagreth!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the device is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether.

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== AJZaurusUSB driver ===

You can also use the open source driver from [http://www.dsitri.de/wiki.php?page=AJZaurusUSB]. It was developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.3, 10.4 and 10.5.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the neo, because the driver provides a constant ethernet address independently what the Neo says. Only flashing a new kernel might force you to update.

Issue: This driver is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking
http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#PPP_Networking

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

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

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11. xhost +192.168.0.202. On the Neo: export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [[http://www.quantum-step.com/wiki.php?page=OpenMoko-Edition More Info]]
An SDK for Xcode/Interface Builder is also available: [[http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker]] [[http://www.quantum-step.com/wiki.php?page=SDK More Info]]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[[http://www.quantum-step.com/download/OpenMoko-Edition/mkfs.jffs2.tgz mkfs.jffs2]] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3]] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [[http://www.macports.org/ports.php?by=name&substr=gnueabi]] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]

Latest Images

2008-07-31T04:26:39Z

Flerchjj: milestone 2

This page is intended to summarize in one place the various images you can try out on your Openmoko Neo FreeRunner (GTA02) or 1973 (GTA01). Note however, that some of these are works in progress and may not have even released any files yet. Nothing is guaranteed to work. Proceed at your own risk.

;See [[Distributions]] for a chart comparing the features of the various images.

Michael Lauer's blog also has an entry comparing the distributions: [http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO? TMTLA!]

Instructions on flashing your FreeRunner or 1973 are provided at [[Flashing the Neo FreeRunner]] and [[Getting Started with your Neo1973]], respectively.
----
==2007.2 GTK Image==
The latest most stable release should reside here:
[http://buildhost.openmoko.org/releases/Freerunner/ http://buildhost.openmoko.org/releases/Freerunner/]

*You can download the latest daily builds here:
**For Neo FreeRunner [http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
***Look for files of the form: Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta02.rootfs.tar.gz
***and: openmoko-devel-image-om-gta02.tar.gz
**For Neo 1973 the link is [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
***Look for files of the form: openmoko-devel-image-om-gta01.tar.gz
***and: Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta01.rootfs.tar.gz
**Tools, like dfu-util and openocd [http://buildhost.openmoko.org/daily/tools/ http://buildhost.openmoko.org/daily/tools/]

Several videos of this stack by [http://uk.youtube.com/user/freeyourphone Youtube user freeyourphone]
and [http://uk.youtube.com/watch?v=U05kZfURPig&NR=1 video review by BVB Tech]
=== ScaredyCat ===
Users may have heard of "ScaredyCat" images. These are usable images created by [http://blog.automated.it/category/openmoko/ Andy Powell] and are currently based on the 2007.02 software stack.

Hey, all file names are with "gta01" !
Is this an error and they are gta02 (FR) ??

scroll down a bit, or search for gta02 on the page. they're there, just not on the first page. (ozzloy)

http://buildhost.automated.it/OM2007.2/
----

==ASU (April|August Software Update) qtopia-based Image==
There has not been a recommended release of the ASU yet. You may wish to review the [[ASU_Feature_Plan|ASU feature plan]] or some [http://dos.jogger.pl/2008/06/29/asu-to-przyszlosc/ screenshots]

*You can download the latest daily builds here:
**For Neo FreeRunner [http://buildhost.openmoko.org/daily/freerunner/ http://buildhost.openmoko.org/daily/freerunner/]
***Look for files of the form: openmoko-qtopia-x11-image-om-gta02.tar.gz
***and: Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta02.rootfs.tar.gz
**For Neo 1973 the link is [http://buildhost.openmoko.org/daily/neo1973/ http://buildhost.openmoko.org/daily/neo1973/]
***Look for files of the form: openmoko-qtopia-x11-image-om-gta01.tar.gz
***and: Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-YYYYMMDD-om-gta01.rootfs.tar.gz
----

==FSO (FreeSmartPhone.org) Image==
Milestone 1 is here: [http://downloads.openmoko.org/framework/milestone1/ http://downloads.openmoko.org/framework/milestone1/]

[http://www.youtube.com/watch?v=toPe0S8QpJY Video of FSO Milestone 1]

Milestone 2 is here: [http://downloads.openmoko.org/framework/milestone2/ http://downloads.openmoko.org/framework/milestone2/]

Browse the source: [http://trac.freesmartphone.org:8000/trac-example/browser http://trac.freesmartphone.org:8000/trac-example/browser]

Learn more at its wiki page: [[OpenmokoFramework]]
----

==Qtopia image from qtopia.net==
[http://www.qtopia.net/modules/mydownloads/index.php Qtopia.net images] for the
*Neo FreeRunner
**[http://www.qtopia.net/modules/mydownloads/visit.php?lid=67 Freerunner flash image] (qtopia-4.3.2-gta02-flash.tgz) <-- a tarball with both a rootfs and kernel
**and the [http://www.qtopia.net/modules/mydownloads/visit.php?lid=68 root file system (ficgta02-qtopia-developer-rootfs.tgz)]
*Neo 1973
**[http://qtopia.net/downloads/neo/qtopia-4.3.2-gta01-flash.tgz Neo 1973 flash image] (qtopia-4.3.2-gta01-flash.tgz) <-- a tarball with both a rootfs and kernel
**[http://www.qtopia.net/modules/mydownloads/visit.php?lid=39 Neo 1973 root file system] (Link temporarily broken.)
**A Neo 1973 image is also available from here [http://buildhost.automated.it/OM2007.2/openmoko-qtopia-image-om-gta01.tar.gz openmoko-qtopia-image-om-gta01.tar.gz]
*[http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6 Alternate download page]
*You might also try [http://trolltech.com/developer/downloads/qtopia/qtopia-source-gpl ftp.trolltech.com snapshots]

Addtional packages can be added from the Trolltech feed for this image, found at
http://qtopia.net/packages/feed/4.3.2/neo/
To get to these packages, you need to add the feed as a source in the Qtopia package manager.
----

==SHR (Stable Hybrid Release) Image==
The Stable Hybrid Release (SHR) is intended to be a combination of the
FSO, some of the 2007.2 GTK software, and the ASU that provides all of
the functionality of the 2007.2 software, but with the stability of
the FSO and the new GUI toolkits provided by the ASU. It will probably
be based on an ASU build, with the FSO software and GTK end-user apps
added.

The SHR doesn't exist anywhere but in a few people's heads at the moment (2008-07-05). Hopefully, all the work in it will be integrated back into one of the other releases, and it will cease to exist. The point is to get us a release with stable calls & suspend/resume, plus access to all those other nifty apps we had on 2007.2 and the ASU.

Learn more at its wiki page: [[Stable_Hybrid_Release]]
----

==Debian==
See [[Debian]].

==Copying a jffs2 image to ext2 to boot from microSD==
If you want to copy a rootfs jffs2 to a ext2 filesystem on an microSD card, see [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) | this]].

[[category:Openmoko]]

Mac OS X

2008-07-30T22:15:59Z

Flerchjj: fix closing tag

Welcome to the Openmoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 and Neo Freerunner with Mac.

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here is a detailed instruction:
# download Version 1.4 or later of Openmoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===

The <code>screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem00000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are two drivers you can use to talk to the RNDIS/Ethernet Gadget that the Neo1973 presents to its host system. The main difference between them is stability, but both have their own problems. Leopard needs further testing (Apple revised the driver and the Network System Settings).

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame MacOSX for because it tries to make network configuration simpler based on the assumption of stable Ethernet addresses.

Use this configuration on the new interface:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want to use:
<pre>
Subnet: 255.255.255.248
</pre>

Test: You should be able to connect to your Neo! Try using ping 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.

Test: run "ssh root@192.168.0.202" to get in, and try pinging (from the neo) the outside world (e.g. "ping google.com"). If that works then your Mac is routing the neo globally--congratulations!--if not.. XXX fill in. You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the device is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether.

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== AJZaurusUSB driver ===

You can also use the open source driver from [http://www.dsitri.de/wiki.php?page=AJZaurusUSB]. It was developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.3, 10.4 and 10.5.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the neo, because the driver provides a constant ethernet address independently what the Neo says. Only flashing a new kernel might force you to update.

Issue: This driver is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking
http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#PPP_Networking

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

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

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11. xhost +192.168.0.202. On the Neo: export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [[http://www.quantum-step.com/wiki.php?page=OpenMoko-Edition More Info]]
An SDK for Xcode/Interface Builder is also available: [[http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker]] [[http://www.quantum-step.com/wiki.php?page=SDK More Info]]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[[http://www.quantum-step.com/download/OpenMoko-Edition/mkfs.jffs2.tgz mkfs.jffs2]] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3]] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [[http://www.macports.org/ports.php?by=name&substr=gnueabi]] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]

Mac OS X

2008-07-30T22:15:17Z

Flerchjj: added alternate subnet to resolve issues

Welcome to the Openmoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 and Neo Freerunner with Mac.

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here is a detailed instruction:
# download Version 1.4 or later of Openmoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===

The <code>screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem00000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are two drivers you can use to talk to the RNDIS/Ethernet Gadget that the Neo1973 presents to its host system. The main difference between them is stability, but both have their own problems. Leopard needs further testing (Apple revised the driver and the Network System Settings).

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame MacOSX for because it tries to make network configuration simpler based on the assumption of stable Ethernet addresses.

Use this configuration on the new interface:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want to use:
<pre>
Subnet: 255.255.255.248
<pre>

Test: You should be able to connect to your Neo! Try using ping 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.

Test: run "ssh root@192.168.0.202" to get in, and try pinging (from the neo) the outside world (e.g. "ping google.com"). If that works then your Mac is routing the neo globally--congratulations!--if not.. XXX fill in. You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the device is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether.

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== AJZaurusUSB driver ===

You can also use the open source driver from [http://www.dsitri.de/wiki.php?page=AJZaurusUSB]. It was developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.3, 10.4 and 10.5.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the neo, because the driver provides a constant ethernet address independently what the Neo says. Only flashing a new kernel might force you to update.

Issue: This driver is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking
http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#PPP_Networking

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

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

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11. xhost +192.168.0.202. On the Neo: export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [[http://www.quantum-step.com/wiki.php?page=OpenMoko-Edition More Info]]
An SDK for Xcode/Interface Builder is also available: [[http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker]] [[http://www.quantum-step.com/wiki.php?page=SDK More Info]]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[[http://www.quantum-step.com/download/OpenMoko-Edition/mkfs.jffs2.tgz mkfs.jffs2]] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3]] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [[http://www.macports.org/ports.php?by=name&substr=gnueabi]] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]

Getting Started with your Neo FreeRunner

2008-07-30T04:41:08Z

Flerchjj: undo

{{Languages|Getting Started with your Neo FreeRunner}}

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc; width:75% " |

Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of [[Openmoko]]. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.


Some Frequently Asked Questions for new owners are featured in the [[Getting Started FAQ]].


! style="background:#fcfcfc; width:25% " |
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]
|}

== Package Contents ==

[[Image:GTA02ALL.png|left|400px|thumb|Inside the package]]
 
: [[Image:Circle２.gif|10px]] Neo FreeRunner
: [[Image:Circle２.gif|10px]] Stylus
: [[Image:Circle２.gif|10px]] Battery
: [[Image:Circle２.gif|10px]] Charger
: [[Image:Circle２.gif|10px]] USB Cable (A -> Mini-B 5-pole)
: [[Image:Circle２.gif|10px]] microSD Card 512MB & SD adapter

<div style="clear: both"> </div>

== Setting up the hardware, getting to know the Neo FreeRunner physically ==

===Installing the Micro-SD card, the SIM card, and the Battery ===

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|Open the case like this.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Opening !|center]]</td>
</tr>
<tr valign="top" style="background: #ffffff">
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here.|center]]</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|Finally, put in the battery.|center]]</td>
</tr></table>
</div>

# Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.
# Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.
# Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.
# Lift up on the SIM card holder.
# The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.
# Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo Freerunner.
# Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.
# Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.
# Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.
# Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.
# Replace the rear cover on the FreeRunner.

[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]

[[http://video.google.de/videoplay?docid=-8343770443102960945 A short video]] is also available. It was shot using the previous version of the Neo, but the installation procedures remains the same.

===Charging the Neo FreeRunner===

When using the Neo FreeRunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger (at 1000mA) or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.

Charging an empty battery at 100mA takes 12~15 hours, at 500mA takes 2,5~3,5 hours, and at 1000mA takes 1.5~2.5 hours. (90%~100%) [to be confirmed]

Make sure that the battery never discharges completely. This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work. Should the battery become completely discharged, your options are:
- Use external stand-alone charger (compatible with the Nokia BL-5C battery)
- Boot the FreeRunner with an alternative battery, or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
- Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.

===Buttons and connectors===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Power Button, USB and external GPS Antenna (left to right)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack (left to right)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Power'''
Tapping the power button exits the current application.

Holding the power button brings up a menu allowing you to:
* Power on and off the GPS, wifi, GSM, and bluetooth antennae
* Change power management mode to:
** Dim first then lock
** Dim only, don't lock
** Disabled
* Lock the screen
* Shutdown the device.</td>
<td></td>
<td>'''Aux'''

Holding the Aux button brings up a menu allowing you to:

* Hide and show the title bar (Fullscreen toggle)
* Alternate wide or tall display modes (Swap Orientation)
* Save the content of the screen as an image file (Screenshot)
</td>
</tr>
</table>

The phone jack is a 2.5mm connector with four contacts: stereo + MIC. It is compatible with the headsets used by Motorola smartphones (A780,A1200, ...) and the V-360.

To plug regular (i.e. without microphone) headphones commonly used to listen to music, a compatible 2.5mm 4 rings jack to 3.5mm stereo jack adapter is needed. It has been reported that Nokia's 2.5mm -> 3.5mm adapters do not work, but that a 3.5mm Stereo Audio Adapter for Motorola MPx200/E398 works well. You will also want to switch from speaker output to headset, by restoring the appropriate alsa.state-file (usually the mediaplayer should do this for you) or via alsamixer (see below), to enable stereo output in there.

===Unlocking the screen===

When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.

== Navigating menus and applications ==

''Note:'' this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

====Today Page====

[[Image:Todaypage_reduced_true.png|200px|right]] Openmoko starts by displaying the "Today" page, which is your home page. Icons in the top row indicate the status of the phone. The bottom row consists of three tabs. The tab with a home on the left lead to the "Today" page you're viewing now. The central tab lead to the "Launch Task" page, which is the main menu used to start applications. The tab with gears on the right lead to the "Running Tasks" page, which is used to deal with currently open windows and applications.

 

[[Image:Todaypage_reduced_false.png|right|200px|]] The "Today" page is empty, as shown above, when you first start Openmoko. We explain below how to turn on the "full view", displayed to the right. In the full view, a second row of icons give quick links to commonly-used applications such as the dialer, the adressbook, mailbox and calendar. The main body of the screen displays a clock and other useful information.

See [[Today/2007.2]] for more information about the Today page and customization.

 

====Launch Task Page====

{{stub}}

[[Image:LaunchTasks.png|right|200px]] This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Current categories are [[PIM Suite]], [[Applications]], [[Games]], [[Utilities]], and All.

 

====Running Tasks Page====

{{stub}}

[[Image:RunningTasks.png|right|200px]] This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

 

====Exiting from and switching to an Application====

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can cycle through active applications using the AUX button

Clicking the top-left of the screen displays the drop down ''task menu''. This menu lists all active applications and allows to switch directly to any one. ''Note:'' If the task menu is not shown, click and hold the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".

== Using the terminal ==

To start a console from "Today" page, click the middle tab at the bottom of the screen to display the "Launch applications" page, then select Terminal in the "Applications" submenu. The multitaps keyboard slides up (and down) from the bottom of the screen automatically when you touch the screen.

===Setting date and time===

From the terminal, type the following, but replace ''MM'' with the month (01-12); ''DD'' with the day (01-31); ''hhmm'' with the time (0000-2359); ''YYYY'' with the year (optional); and ''.ss'' with the seconds (optional).

date -s ''MMDDhhmmYYYY.ss''

To make the change persist between reboots, sync the hardware clock with the updated system time.

hwclock --systohc

See [[Setting_Date_and_Time]] for more discussion, including synchronizing with an NTP server.

===Adjusting the Volume===

As of this writing, there is no way to adjust the volume from the screen.

For now, run the terminal application or [[USB_Networking|log in via usb]], and run the [[Neo alsamixer]] application (to see all the options, including Mic2, you will need to run ''alsamixer -V all''). The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use
alsactl -f ''path-to-statefile'' store
to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):
:gsmhandset.state
:gsmheadset.state
:gsmspeakerout.state
:headset.state
:stereoout.state

These correspond to the various Sound Profiles accessible in the Debug Tool under Applications.

To manually restore one of the state files,
alsactl -f ''path-to-statefile'' restore

One way to increase the volume of the microphone is to do the following:
# ssh into your Freerunner
# vi /usr/share/openmoko/scenarios/gsmhandset.state
# search for "Mic2"
# change to "value 3"
If people report not being able to hear you when you call, then setting the Mic2 value to 2 or 3 should fix that.

'''Question: I am using headphones but only the right speaker work the left don't work how can I fix this ?'''

R: This should be set correctly by restoring gsmheadset.state.
Pull and replug the headset jack to make sure the correct state-file is restored.
To manually control the switch between Speaker and headset:
Start alsamixer, scroll along to the right until you find "Amp Spk" and mute it (m), the sound will then come out from both channels of the
headphones and not out of the speaker.

[[Freerunner_Hardware_Issues]]

=== Accessing the microSD card ===

Mounted at /media/card by default.

If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc.

== Set up USB-based networking and update ==

===Connect with and log in the Neo FreeRunner===

This is discussed in the [[USB_Networking|USB Networking]] section.

===Use the package manager===

There are three layers to the software on the FreeRunner:

* uBoot: Think of u-boot as a combination of the BIOS and Grub on a PC.
* Kernel: The Linux kernel
* Root Filesystem: The rest of the system

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intervals. There are two main methods of doing this: using the package manager opkg (discussed in this section) or [[Flashing the Neo FreeRunner|flashing the device]].

uboot, the kernel and the root filesystem can all be flashed to update them. For uboot, this is the only possibility. The advantage of flashing the kernel, rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.

Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use, so either upgrade dropbear from the FreeRunner's terminal and then upgrade the rest via ssh, or upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal. For example, go to the FreeRunner terminal and type:

# opkg upgrade dropbear

which will upgrade it to the latest version. Then connect to the FreeRunner via ssh and type:

# opkg upgrade

If you do your first upgrade in two installments like this, it will go more smoothly.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented

=== Installing multimedia, web browsing and other applications ===

There are many applications you can install - check out the [[Repositories]] for a list of packages, an example of how to add a repository using scaredy cat as an example can also be found here. A list of pre-installed and available packages with descriptions can be found here - [[Available Packages]].

The calendar can be installed with

opkg install openmoko-dates2

For a Media Player:

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

If you want a basic image viewer, have a look at the one from the gpe suite:

opkg install gpe-icons
opkg install gpe-gallery

To obtain the standard web browser, use:

opkg install openmoko-browser2

An alternative browser, minimo, offers many more features.
First download and unpack it on your GNU/Linux host:

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

Copy it over to the FreeRunner:
scp minimo_* root@192.168.0.202:/tmp

Then on the FreeRunner:
opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]

=== Importing contacts ===

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.

==The next steps==

Congratulations for setting up your Neo FreeRunner. There are many more ressources to help free your phone:

===Customize the interface: clock, keyboard...===

The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# /etc/init.d/xserver-nodm restart

If you rather have a regular clock instead of the digital one, do this instead:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false
# /etc/init.d/xserver-nodm restart

More information about today screen customization at [[Today/2007.2]].

With either clock, you may wish to set the correct [[Date]] and [[Timezone]].

Also, if you prefer having a full keyboard, using matchbox's qwerty keybord, see [[Switching_Keyboards#Matchbox_keyboard|these instructions]]. Then you may also see [http://lists.openmoko.org/pipermail/community/2008-July/021296.html these], which describe a way to add an applet allowing the showing/hiding of that keyboard.

===WLAN, GPRS, Bluetooth and GPS===

'''WLAN''': See [[GTA02 WLAN]]

'''GPRS''': See [[Manually using GPRS]]

'''Bluetooth''': See [[Manually using Bluetooth]]

Simple guide to get going with '''GPS''':

# opkg install gpsd
# echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd

and restart gpsd, the gps daemon, with

# /etc/init.d/gpsd restart

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install http://www.tangogps.org/downloads/tangogps_0.9.2-r1_armv4t.ipk

More information on [[GPS]] page.

There were critical [[GPS Problems]] earlier that are largely fixed with newest kernel. To install the updates when they become available, you will probably want to learn about [[Booting the Neo FreeRunner]] and [[Flashing the Neo FreeRunner]].

=== The community ===
==== Mailing lists ====

There are several [[http://lists.openmoko.org/mailman/listinfo/ Mailing lists]]

There is an active community mailing list.
You may ask for help on the support mailing list : more details at https://lists.openmoko.org/mailman/listinfo/support

If you are more comfortable with a web-based approach, you can also read and post the lists with http://lists.openmoko.org/nabble.html

An excellent tool for searching all the openmoko mailing lists is http://openmoko.markmail.org/

==== The wiki ====

If you want to know more about the Neo FreeRunner then you can get more information in the following topics:

* [[GTA02 Openness]]
* [[Neo FreeRunner]]
* [[Neo FreeRunner GTA02 Hardware]]
* [[FreeRunner/Buttons and LEDs]]
* [[Latest Images]]
* [[Distributions]]
* [[GTA02_FAQ]]

To search this wiki with Google, use the following search term:

<search term> site:http://wiki.openmoko.org/wiki/

==== Blogs ====

The [http://planet.openmoko.org/ collection of blogs on OpenMoko].

==== Other documents ====

* http://quickstart.openmoko.org/

[[Category:GTA02 Hardware]]
[[Category:Guides]]
[[Category:User Guides]]

Getting Started with your Neo FreeRunner

2008-07-30T04:37:06Z

Flerchjj: add Mac reference

{{Languages|Getting Started with your Neo FreeRunner}}

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc; width:75% " |

Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of [[Openmoko]]. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.


Some Frequently Asked Questions for new owners are featured in the [[Getting Started FAQ]].


! style="background:#fcfcfc; width:25% " |
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]
|}

== Package Contents ==

[[Image:GTA02ALL.png|left|400px|thumb|Inside the package]]
 
: [[Image:Circle２.gif|10px]] Neo FreeRunner
: [[Image:Circle２.gif|10px]] Stylus
: [[Image:Circle２.gif|10px]] Battery
: [[Image:Circle２.gif|10px]] Charger
: [[Image:Circle２.gif|10px]] USB Cable (A -> Mini-B 5-pole)
: [[Image:Circle２.gif|10px]] microSD Card 512MB & SD adapter

<div style="clear: both"> </div>

== Setting up the hardware, getting to know the Neo FreeRunner physically ==

===Installing the Micro-SD card, the SIM card, and the Battery ===

<div align-center>
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|Open the case like this.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Opening !|center]]</td>
</tr>
<tr valign="top" style="background: #ffffff">
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here.|center]]</td>
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu12.jpg|233px|thumb|Finally, put in the battery.|center]]</td>
</tr></table>
</div>

# Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.
# Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.
# Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.
# Lift up on the SIM card holder.
# The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.
# Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo Freerunner.
# Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.
# Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.
# Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.
# Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.
# Replace the rear cover on the FreeRunner.

[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]

[[http://video.google.de/videoplay?docid=-8343770443102960945 A short video]] is also available. It was shot using the previous version of the Neo, but the installation procedures remains the same.

===Charging the Neo FreeRunner===

When using the Neo FreeRunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger (at 1000mA) or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.

Charging an empty battery at 100mA takes 12~15 hours, at 500mA takes 2,5~3,5 hours, and at 1000mA takes 1.5~2.5 hours. (90%~100%) [to be confirmed]

Make sure that the battery never discharges completely. This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work. Should the battery become completely discharged, your options are:
- Use external stand-alone charger (compatible with the Nokia BL-5C battery)
- Boot the FreeRunner with an alternative battery, or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
- Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.

===Buttons and connectors===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Power Button, USB and external GPS Antenna (left to right)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack (left to right)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Power'''
Tapping the power button exits the current application.

Holding the power button brings up a menu allowing you to:
* Power on and off the GPS, wifi, GSM, and bluetooth antennae
* Change power management mode to:
** Dim first then lock
** Dim only, don't lock
** Disabled
* Lock the screen
* Shutdown the device.</td>
<td></td>
<td>'''Aux'''

Holding the Aux button brings up a menu allowing you to:

* Hide and show the title bar (Fullscreen toggle)
* Alternate wide or tall display modes (Swap Orientation)
* Save the content of the screen as an image file (Screenshot)
</td>
</tr>
</table>

The phone jack is a 2.5mm connector with four contacts: stereo + MIC. It is compatible with the headsets used by Motorola smartphones (A780,A1200, ...) and the V-360.

To plug regular (i.e. without microphone) headphones commonly used to listen to music, a compatible 2.5mm 4 rings jack to 3.5mm stereo jack adapter is needed. It has been reported that Nokia's 2.5mm -> 3.5mm adapters do not work, but that a 3.5mm Stereo Audio Adapter for Motorola MPx200/E398 works well. You will also want to switch from speaker output to headset, by restoring the appropriate alsa.state-file (usually the mediaplayer should do this for you) or via alsamixer (see below), to enable stereo output in there.

===Unlocking the screen===

When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.

== Navigating menus and applications ==

''Note:'' this section describes the interface used by the "2007.2" image, which is the current default image for Openmoko.

====Today Page====

[[Image:Todaypage_reduced_true.png|200px|right]] Openmoko starts by displaying the "Today" page, which is your home page. Icons in the top row indicate the status of the phone. The bottom row consists of three tabs. The tab with a home on the left lead to the "Today" page you're viewing now. The central tab lead to the "Launch Task" page, which is the main menu used to start applications. The tab with gears on the right lead to the "Running Tasks" page, which is used to deal with currently open windows and applications.

 

[[Image:Todaypage_reduced_false.png|right|200px|]] The "Today" page is empty, as shown above, when you first start Openmoko. We explain below how to turn on the "full view", displayed to the right. In the full view, a second row of icons give quick links to commonly-used applications such as the dialer, the adressbook, mailbox and calendar. The main body of the screen displays a clock and other useful information.

See [[Today/2007.2]] for more information about the Today page and customization.

 

====Launch Task Page====

{{stub}}

[[Image:LaunchTasks.png|right|200px]] This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.

Current categories are [[PIM Suite]], [[Applications]], [[Games]], [[Utilities]], and All.

 

====Running Tasks Page====

{{stub}}

[[Image:RunningTasks.png|right|200px]] This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.

 

====Exiting from and switching to an Application====

Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.

Alternatively, you can cycle through active applications using the AUX button

Clicking the top-left of the screen displays the drop down ''task menu''. This menu lists all active applications and allows to switch directly to any one. ''Note:'' If the task menu is not shown, click and hold the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".

== Using the terminal ==

To start a console from "Today" page, click the middle tab at the bottom of the screen to display the "Launch applications" page, then select Terminal in the "Applications" submenu. The multitaps keyboard slides up (and down) from the bottom of the screen automatically when you touch the screen.

===Setting date and time===

From the terminal, type the following, but replace ''MM'' with the month (01-12); ''DD'' with the day (01-31); ''hhmm'' with the time (0000-2359); ''YYYY'' with the year (optional); and ''.ss'' with the seconds (optional).

date -s ''MMDDhhmmYYYY.ss''

To make the change persist between reboots, sync the hardware clock with the updated system time.

hwclock --systohc

See [[Setting_Date_and_Time]] for more discussion, including synchronizing with an NTP server.

===Adjusting the Volume===

As of this writing, there is no way to adjust the volume from the screen.

For now, run the terminal application or [[USB_Networking|log in via usb]], and run the [[Neo alsamixer]] application (to see all the options, including Mic2, you will need to run ''alsamixer -V all''). The mixer is simpler than it looks. Just use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.

You may need to update configuration files in /usr/share/openmoko/scenarios/ to make the microphone setting permanent. Use
alsactl -f ''path-to-statefile'' store
to do this.

The default files are as follows (in /usr/share/openmoko/scenarios/):
:gsmhandset.state
:gsmheadset.state
:gsmspeakerout.state
:headset.state
:stereoout.state

These correspond to the various Sound Profiles accessible in the Debug Tool under Applications.

To manually restore one of the state files,
alsactl -f ''path-to-statefile'' restore

One way to increase the volume of the microphone is to do the following:
# ssh into your Freerunner
# vi /usr/share/openmoko/scenarios/gsmhandset.state
# search for "Mic2"
# change to "value 3"
If people report not being able to hear you when you call, then setting the Mic2 value to 2 or 3 should fix that.

'''Question: I am using headphones but only the right speaker work the left don't work how can I fix this ?'''

R: This should be set correctly by restoring gsmheadset.state.
Pull and replug the headset jack to make sure the correct state-file is restored.
To manually control the switch between Speaker and headset:
Start alsamixer, scroll along to the right until you find "Amp Spk" and mute it (m), the sound will then come out from both channels of the
headphones and not out of the speaker.

[[Freerunner_Hardware_Issues]]

=== Accessing the microSD card ===

Mounted at /media/card by default.

If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc.

== Set up USB-based networking and update ==

===Connect with and log in the Neo FreeRunner===

This is discussed in the [[USB_Networking|USB Networking]] section
and in the [[MacOS_X#USB_Networking|USB Networking with Mac OS X]] section.

===Use the package manager===

There are three layers to the software on the FreeRunner:

* uBoot: Think of u-boot as a combination of the BIOS and Grub on a PC.
* Kernel: The Linux kernel
* Root Filesystem: The rest of the system

In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intervals. There are two main methods of doing this: using the package manager opkg (discussed in this section) or [[Flashing the Neo FreeRunner|flashing the device]].

uboot, the kernel and the root filesystem can all be flashed to update them. For uboot, this is the only possibility. The advantage of flashing the kernel, rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.

Assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with

# opkg update
# opkg upgrade

The first updates the repository information, telling opkg what packages are available. The second upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.

Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use, so either upgrade dropbear from the FreeRunner's terminal and then upgrade the rest via ssh, or upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal. For example, go to the FreeRunner terminal and type:

# opkg upgrade dropbear

which will upgrade it to the latest version. Then connect to the FreeRunner via ssh and type:

# opkg upgrade

If you do your first upgrade in two installments like this, it will go more smoothly.

It will be possible in the future to update uboot with opkg, but this has not yet been implemented

=== Installing multimedia, web browsing and other applications ===

There are many applications you can install - check out the [[Repositories]] for a list of packages, an example of how to add a repository using scaredy cat as an example can also be found here. A list of pre-installed and available packages with descriptions can be found here - [[Available Packages]].

The calendar can be installed with

opkg install openmoko-dates2

For a Media Player:

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

If you want a basic image viewer, have a look at the one from the gpe suite:

opkg install gpe-icons
opkg install gpe-gallery

To obtain the standard web browser, use:

opkg install openmoko-browser2

An alternative browser, minimo, offers many more features.
First download and unpack it on your GNU/Linux host:

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

Copy it over to the FreeRunner:
scp minimo_* root@192.168.0.202:/tmp

Then on the FreeRunner:
opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk

You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]

=== Importing contacts ===

If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.

==The next steps==

Congratulations for setting up your Neo FreeRunner. There are many more ressources to help free your phone:

===Customize the interface: clock, keyboard...===

The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# /etc/init.d/xserver-nodm restart

If you rather have a regular clock instead of the digital one, do this instead:

# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false
# /etc/init.d/xserver-nodm restart

More information about today screen customization at [[Today/2007.2]].

With either clock, you may wish to set the correct [[Date]] and [[Timezone]].

Also, if you prefer having a full keyboard, using matchbox's qwerty keybord, see [[Switching_Keyboards#Matchbox_keyboard|these instructions]]. Then you may also see [http://lists.openmoko.org/pipermail/community/2008-July/021296.html these], which describe a way to add an applet allowing the showing/hiding of that keyboard.

===WLAN, GPRS, Bluetooth and GPS===

'''WLAN''': See [[GTA02 WLAN]]

'''GPRS''': See [[Manually using GPRS]]

'''Bluetooth''': See [[Manually using Bluetooth]]

Simple guide to get going with '''GPS''':

# opkg install gpsd
# echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd

and restart gpsd, the gps daemon, with

# /etc/init.d/gpsd restart

To test GPS, you can use agpsui:

# opkg install openmoko-agpsui

For a nice map, try tangoGPS:

# opkg install http://www.tangogps.org/downloads/tangogps_0.9.2-r1_armv4t.ipk

More information on [[GPS]] page.

There were critical [[GPS Problems]] earlier that are largely fixed with newest kernel. To install the updates when they become available, you will probably want to learn about [[Booting the Neo FreeRunner]] and [[Flashing the Neo FreeRunner]].

=== The community ===
==== Mailing lists ====

There are several [[http://lists.openmoko.org/mailman/listinfo/ Mailing lists]]

There is an active community mailing list.
You may ask for help on the support mailing list : more details at https://lists.openmoko.org/mailman/listinfo/support

If you are more comfortable with a web-based approach, you can also read and post the lists with http://lists.openmoko.org/nabble.html

An excellent tool for searching all the openmoko mailing lists is http://openmoko.markmail.org/

==== The wiki ====

If you want to know more about the Neo FreeRunner then you can get more information in the following topics:

* [[GTA02 Openness]]
* [[Neo FreeRunner]]
* [[Neo FreeRunner GTA02 Hardware]]
* [[FreeRunner/Buttons and LEDs]]
* [[Latest Images]]
* [[Distributions]]
* [[GTA02_FAQ]]

To search this wiki with Google, use the following search term:

<search term> site:http://wiki.openmoko.org/wiki/

==== Blogs ====

The [http://planet.openmoko.org/ collection of blogs on OpenMoko].

==== Other documents ====

* http://quickstart.openmoko.org/

[[Category:GTA02 Hardware]]
[[Category:Guides]]
[[Category:User Guides]]

Neo FreeRunner Hardware

2008-06-05T22:18:39Z

Flerchjj: fixed manual reference

{{Languages|Neo FreeRunner GTA02 Hardware}}
__NOTOC__
__NOEDITSECTION__
{{gta02menu}}
[[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]]
[[Image:SimpleComponentDiagram.jpg|thumb|400px|Simplified Hardware Component Diagram]]

=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 in noisy environments)
*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
*Provides 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: [http://210.118.57.197/Products/Semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/SC32442/um_s3c2442b_rev12.pdf Samsung SC32442B]
* 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 case for the FreeRunner is all black, as seen on the front page of the wiki.

Openmoko has released the CAD files for the case schematics for the OpenMoko [[Neo1973]] (GTA01) and Neo FreeRunner. These are available in the original Pro/E (.asm/.prt) format and alternative formats created from the originals.

We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.

* [http://downloads.openmoko.org/CAD/NeoFreerunner_ProE.zip The original Pro/E (.asm/.prt) format]

[http://downloads.openmoko.org/CAD/ Browse CAD directory]

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

== CE ==
*For Europe
**Registration number: M528583V-EO
**[http://people.openmoko.org/tony_tu/GTA02/certificate/CE/ CE report and certificate]

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

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

Openmoko Community Applications

2008-05-07T19:14:44Z

Flerchjj: /* Cool application name goes here */

== Overview ==
This page is intended for ordinary end users of [[OpenMoko]] smartphones. It lists some of the cool applications provided by the Openmoko community that you can install and enjoy. Freedom to share! You can find many more applications here - http://projects.openmoko.org

'''Please note that not all of these applications are in a finished format yet. When they are complete you will be able to download them via a menu on the phone. At the moment, following a recipe of commands in the console window may be needed to install. This will of course improve with time :-) '''

'''Please also note that there is "some risk" in installing developing software or software from an unknown source! However, if the license for the code is an open source license then you have the comfort that anyone in the OpenMoko community has the power to check the operation of the software and thus malicious or vulernable code is minimised'''

Any problems with the software below should be reported to the individual software developer rather than the OpenMoko core team.

== Note to application developers ==

No more than 8 featured OpenMoko Community Applications should be listed on this page at a time. The main place for OpenMoko device owners to browse software remains http://projects.openmoko.org. Applications listed here should have mass appeal as an advert of what the platform can do for Linux fans and ordinary smartphone users alike.

Please provide
* a link to your project page
* a short video if possible
* screenshots
* indicate whether your application is stable or still under development
* state which models of OpenMoko phone the application is designed for.
* a short paragraph describing features
* the license the code is provided under

Please add your application to the bottom of the list

== TangoGPS ==

{| border="1"
|-
|Project Homepage
|http://www.tangogps.org
|-
|Video
|http://www.youtube.com/watch?v=hn7wuxlTNvs
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|gps and map program
|-
|Software License
|Add your software license here
|-
|}

== Mokopedia ==

{| border="1"
|-
|Project Homepage
|http://mokopedia.projects.openmoko.org/
|-
|Video
|http://www.rabenfrost.net/mokopedia_demo2.ogg
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Special compressed version of Wikipedia stored in your SD storage card. Access to wikipedia wherever you are!
|-
|Software License
|Add your software license here
|-
|}

== Thumbtribes ==

{| border="1"
|-
|Project Homepage
|http://thumbtribes.mobi/
|-
|Video
|It's a D-Bus daemon...Doh!
|-
|Screenshots
|See above
|-
|Application Status
|Funky
|-
|Application Description
|Low bandwidth distance calculation daemon
|-
|Software License
|GPL
|-
|}

== Minimo ==

{| border="1"
|-
|Wiki Link
|[http://wiki.openmoko.org/wiki/Minimo Minimo for Moko]
|-
|-
|Video
|Add your video hyperlink here
|-
|Screenshots
|[[Image:Minimo-slashdot.jpeg|thumb|left]]
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Minimo is a Mozilla based web browser. It features full AJAX support and other goodies. It is listed as an alternative to standard Webkit based browser.
|-
|Software License
|Add your software license here
|-
|}

== orrery ==

{| border="1"
|-
|Wiki Link
|[http://wiki.openmoko.org/wiki/Orrery orrery for Moko]
|-
|-
|Video
|None available
|-
|Screenshots
|[[Image:OrreryImage1.png|thumb|left]][[Image:OrreryImage2.png|thumb|right]]
|-
|Application Status
|It works, but is not neatly packaged yet. Available as tarball.
|-
|Application Description
|Orrery displays the objects in the night (or day) sky. It uses the GPS position, if available.
|-
|Software License
|GPL
|-
|}

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

Openmoko Community Applications

2008-05-07T19:12:12Z

Flerchjj: /* Note to application developers */

== Overview ==
This page is intended for ordinary end users of [[OpenMoko]] smartphones. It lists some of the cool applications provided by the Openmoko community that you can install and enjoy. Freedom to share! You can find many more applications here - http://projects.openmoko.org

'''Please note that not all of these applications are in a finished format yet. When they are complete you will be able to download them via a menu on the phone. At the moment, following a recipe of commands in the console window may be needed to install. This will of course improve with time :-) '''

'''Please also note that there is "some risk" in installing developing software or software from an unknown source! However, if the license for the code is an open source license then you have the comfort that anyone in the OpenMoko community has the power to check the operation of the software and thus malicious or vulernable code is minimised'''

Any problems with the software below should be reported to the individual software developer rather than the OpenMoko core team.

== Note to application developers ==

No more than 8 featured OpenMoko Community Applications should be listed on this page at a time. The main place for OpenMoko device owners to browse software remains http://projects.openmoko.org. Applications listed here should have mass appeal as an advert of what the platform can do for Linux fans and ordinary smartphone users alike.

Please provide
* a link to your project page
* a short video if possible
* screenshots
* indicate whether your application is stable or still under development
* state which models of OpenMoko phone the application is designed for.
* a short paragraph describing features
* the license the code is provided under

Please add your application to the bottom of the list

== TangoGPS ==

{| border="1"
|-
|Project Homepage
|http://www.tangogps.org
|-
|Video
|http://www.youtube.com/watch?v=hn7wuxlTNvs
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|gps and map program
|-
|Software License
|Add your software license here
|-
|}

== Mokopedia ==

{| border="1"
|-
|Project Homepage
|http://mokopedia.projects.openmoko.org/
|-
|Video
|http://www.rabenfrost.net/mokopedia_demo2.ogg
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Special compressed version of Wikipedia stored in your SD storage card. Access to wikipedia wherever you are!
|-
|Software License
|Add your software license here
|-
|}

== Thumbtribes ==

{| border="1"
|-
|Project Homepage
|http://thumbtribes.mobi/
|-
|Video
|It's a D-Bus daemon...Doh!
|-
|Screenshots
|See above
|-
|Application Status
|Funky
|-
|Application Description
|Low bandwidth distance calculation daemon
|-
|Software License
|GPL
|-
|}

== Minimo ==

{| border="1"
|-
|Wiki Link
|[http://wiki.openmoko.org/wiki/Minimo Minimo for Moko]
|-
|-
|Video
|Add your video hyperlink here
|-
|Screenshots
|[[Image:Minimo-slashdot.jpeg|thumb|left]]
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Minimo is a Mozilla based web browser. It features full AJAX support and other goodies. It is listed as an alternative to standard Webkit based browser.
|-
|Software License
|Add your software license here
|-
|}

== orrery ==

{| border="1"
|-
|Wiki Link
|[http://wiki.openmoko.org/wiki/Orrery orrery for Moko]
|-
|-
|Video
|None available
|-
|Screenshots
|[[Image:OrreryImage1.png|thumb|left]][[Image:OrreryImage2.png|thumb|right]]
|-
|Application Status
|It works, but is not neatly packaged yet. Available as tarball.
|-
|Application Description
|Orrery displays the objects in the night (or day) sky. It uses the GPS position, if available.
|-
|Software License
|GPL
|-
|}

== Cool application name goes here ==

{| border="1"
|-
|Project Homepage
|Add your project hyperlink here
|-
|Video
|Add your video hyperlink here
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Add your status notes here
|-
|Software License
|Add your software license here
|-
|}
[[Category:Software]]
[[Category:Applications]]
[[Category:Openmoko]]
[[Category:Guides]]

Om 2007.2 Applications

2008-05-07T19:08:51Z

Flerchjj: /* Overview */

== Overview ==
This page describes the set of core applications '''currently''' included in Openmoko. Additional/Community Apps listed here is limited to popular apps under consideration for inclusion into the core.

Additional apps are also accessible from the Terminal. These '''will not''' be included here. This list is aimed toward apps included in the GUI and Basic Use. If an app gets a gui & is added to '''Launch Tasks''', then it can be added here.

Community applications may be found on the [[Wish_List|Wish List]], [[OpenMoko_Community_Applications | Openmoko Featured Apps]], and on [http://projects.openmoko.org projects.openmoko.org]

If interested in core applications planned for future development see [[Applications|Application Roadmap]]

== Core Applications ==

=== List / Description ===

==== Home Applications ====
* Home / Clock
* [[Dialer/2007.2|Dialer]]: Telephone Calls
* [[Contacts/2007.2|Contacts]]: Address Book
* [[Today/2007.2|Today]]
* Launch Tasks: PIM/App/Game/Utility Menu
* Running Tasks: Switch to or close running tasks
* Keyboard: Open/Close virtual keyboard. Also opens automatically from widgets requiring input

==== PIM Suite ====
All are currently included under Applications

==== Applications ====
* Application Manager: Update, install and remove applications
* Calculator: Perform Simple Calculations (also a PIM app)
* [[Contacts/2007.2|Contacts]]: Address Book (also a PIM app)
* Dates: Calendar (also a PIM app)
* [[Dialer/2007.2|Dialer]]: Telephone Calls (also a PIM app)
* Feed Reader: Read From Your Favorite RSS Feed (also a PIM app)
* Media Player: Enjoy music and movies
* Take Screenshot: Save a screenshot or upload it to h...
* Tasks: What you need to do (also a PIM app)
* Terminal: Command Line Interface Terminal
* Web Browser: Conquer the net (also a PIM app)

==== Games ====
Over 20 games including Sudoku and Mines. Most are puzzle games of some form.

see [[User's_Manual/Games]] for details

==== Utilities ====
NONE

=== Screen Shots ===
{| border="1"
|-
|align="right"|[[Image:System_boot.png|border|300px]] Power On
|align="right"|[[Image:HomeClock.png|border|300px]] Home / Clock
|-
|align="right"|[[Image:Contacts-main-double-height.png|border|300px]] Contacts: Main
|align="right"|[[Image:Contacts-info.png|border|300px]] Contacts: Info
|-
|align="right"|[[Image:Contacts-edit.png|border|300px]] Contacts: Edit
|align="right"|[[Image:Contacts-history.png|border|300px]] Contacts: History
|-
|align="right"|[[Image:Contacts-groups.png|border|300px]] Contacts: Groups
|align="right"|[[Image:MediaPlayer.png|border|300px]] Media Player
|-
|align="right"|[[Image:LaunchTasks.png|border|300px]] Launch Tasks
|align="right"|[[Image:RunningTasks.png|border|300px]] Running Tasks
|-
|align="right"|[[Image:Dialer.png|border|300px]] Dialer
|align="right"|[[Image:Dialer-History.png|border|300px]] Dialer History
|-
|align="right"|[[Image:Calculator.png|border|300px]] Calculator
|
|}

== Additional/Community Applications ==
Only a few applications that appear to be under consideration for addition to the core apps will be listed here. Community applications may be found on the [[Wish_List|Wish List]] and on [http://projects.openmoko.org projects.openmoko.org]

=== List / Description ===
* [[Display_Locker|Display Locker]]: Locks screen to prevent accidental triggering of events.

=== Screen Shots ===
{| border="1"
|-
|align="right"|[[Image:DisplayLocker_MokoClassic.png|border|300px]] Display Locker: Classic Orange
|align="right"|[[Image:Moko classic blue.png|border|300px]] Display Locker: Classic Blue
|-
|align="right"|[[Image:Mokopuzzle.png|border|300px]] Display Locker: Puzzle
|align="right"|[[Image:Openmokochoice.png|border|300px]] Display Locker: Choice
|}

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

Om 2007.2 Applications

2008-05-07T01:31:14Z

Flerchjj: referenced to user manual page & removed redundant material

== Overview ==
This page describes the set of core applications '''currently''' included in Openmoko. Additional/Community Apps listed here is limited to popular apps under consideration for inclusion into the core.

Additional apps are also accessible from the Terminal. These '''will not''' be included here. This list is aimed toward apps included in the GUI and Basic Use. If an app gets a gui & is added to '''Launch Tasks''', then it can be added here.

Community applications may be found on the [[Wish_List|Wish List]] and on [http://projects.openmoko.org projects.openmoko.org]

If interested in core applications planned for future development see [[Applications|Application Roadmap]]

== Core Applications ==

=== List / Description ===

==== Home Applications ====
* Home / Clock
* [[Dialer/2007.2|Dialer]]: Telephone Calls
* [[Contacts/2007.2|Contacts]]: Address Book
* [[Today/2007.2|Today]]
* Launch Tasks: PIM/App/Game/Utility Menu
* Running Tasks: Switch to or close running tasks
* Keyboard: Open/Close virtual keyboard. Also opens automatically from widgets requiring input

==== PIM Suite ====
All are currently included under Applications

==== Applications ====
* Application Manager: Update, install and remove applications
* Calculator: Perform Simple Calculations (also a PIM app)
* [[Contacts/2007.2|Contacts]]: Address Book (also a PIM app)
* Dates: Calendar (also a PIM app)
* [[Dialer/2007.2|Dialer]]: Telephone Calls (also a PIM app)
* Feed Reader: Read From Your Favorite RSS Feed (also a PIM app)
* Media Player: Enjoy music and movies
* Take Screenshot: Save a screenshot or upload it to h...
* Tasks: What you need to do (also a PIM app)
* Terminal: Command Line Interface Terminal
* Web Browser: Conquer the net (also a PIM app)

==== Games ====
Over 20 games including Sudoku and Mines. Most are puzzle games of some form.

see [[User's_Manual/Games]] for details

==== Utilities ====
NONE

=== Screen Shots ===
{| border="1"
|-
|align="right"|[[Image:System_boot.png|border|300px]] Power On
|align="right"|[[Image:HomeClock.png|border|300px]] Home / Clock
|-
|align="right"|[[Image:Contacts-main-double-height.png|border|300px]] Contacts: Main
|align="right"|[[Image:Contacts-info.png|border|300px]] Contacts: Info
|-
|align="right"|[[Image:Contacts-edit.png|border|300px]] Contacts: Edit
|align="right"|[[Image:Contacts-history.png|border|300px]] Contacts: History
|-
|align="right"|[[Image:Contacts-groups.png|border|300px]] Contacts: Groups
|align="right"|[[Image:MediaPlayer.png|border|300px]] Media Player
|-
|align="right"|[[Image:LaunchTasks.png|border|300px]] Launch Tasks
|align="right"|[[Image:RunningTasks.png|border|300px]] Running Tasks
|-
|align="right"|[[Image:Dialer.png|border|300px]] Dialer
|align="right"|[[Image:Dialer-History.png|border|300px]] Dialer History
|-
|align="right"|[[Image:Calculator.png|border|300px]] Calculator
|
|}

== Additional/Community Applications ==
Only a few applications that appear to be under consideration for addition to the core apps will be listed here. Community applications may be found on the [[Wish_List|Wish List]] and on [http://projects.openmoko.org projects.openmoko.org]

=== List / Description ===
* [[Display_Locker|Display Locker]]: Locks screen to prevent accidental triggering of events.

=== Screen Shots ===
{| border="1"
|-
|align="right"|[[Image:DisplayLocker_MokoClassic.png|border|300px]] Display Locker: Classic Orange
|align="right"|[[Image:Moko classic blue.png|border|300px]] Display Locker: Classic Blue
|-
|align="right"|[[Image:Mokopuzzle.png|border|300px]] Display Locker: Puzzle
|align="right"|[[Image:Openmokochoice.png|border|300px]] Display Locker: Choice
|}

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

Main Page

2008-05-07T01:19:16Z

Flerchjj: link to current userspace apps in default image - reduce jumble of kernel software, system daemons, retired 2007 apps, & new/updated apps

{{Languages|Main Page}}
__NOTOC__
__NOEDITSECTION__
__NOTOC__

<DIV ALIGN=CENTER><big>'''[[Openmoko]]™ Open. Mobile. Free.'''</big> </DIV>
 

==Introduction to Openmoko==
[[Image:GTA02.gif |100px|left|frontside]]
[[Openmoko]]™ born as an [http://en.wikipedia.org/wiki/Open_source Open Source] project under [[License| GPL and LGPL license]] and dedicated to delivering an open software stack on mobile platforms, shipped its first product, the Neo 1973, on July 9 2007; and then, turned the project into a start-up company with one aim: create great mobile products using the Openmoko stack: Open. Mobile. Free.

The Openmoko stack, which includes a full X server, allows users and developers to transform mobile hardware platforms into a unique products. Our licence gives developers and users freedom from the "iron to the eyeballs," freedom to cosmetically customize their device or radically remix it; change the wallpaper or rebuild the entire house! It grants them the freedom, for example, to transform a phone into a medical device or point of sale device or the freedom to simply install their own favorite software. Beyond freeing the software on our devices we have also released our CAD files under Creative Commons. By freeing the software under GPL, we enable the community of FOSS developers to "make it new." By freeing the CAD files we give industrial designers and engineers this same opportunity.

{| class="wikitable" cellspacing="0" cellpadding="0" width=100%
! width=30% style="background:#ff6600;border-left:0px solid white;border-right:0px solid white;border-top:0px solid white;" | 
! width=30% style="background:#ff6600;border-left:0px solid white;border-right:0px solid white;border-top:0px solid white;" |
|-
|valign="TOP" style="background:#333333;border-left:0px solid white;border-right:0px solid white;border-bottom:0px solid white;" |
:*[[Background]]
:*[[Meet_the_Core_Team|The Original Core Team]]
:*[[OpenmokoFramework|New Framework Initiative]]
|valign="TOP" style="background:#333333;border-left:0px solid white;border-right:0px solid white;border-bottom:0px solid white;" |
*[[Trademark Policy]]
*[[License]]
|}

==Openmoko Products==
[[image:FIC-neo1973 small.jpg|100px|left|frontside]]

The first Openmoko product, the [[Neo1973]], sold exclusively through [https://direct.openmoko.com/ Openmoko Online Shop]. It sold out in early February 2008.

Openmoko will ship Neo FreeRunner (GTA02), the second generation of Neo in the first half
of 2008.Add your nickname to those interested buying the Neo FreeRunner at [[Buying_Interest_List|Buying Interest List]]. Also, look for a group to buy with at [[GroupSales]] for a discount and extra goodies.

{| class="wikitable" cellspacing="4" cellpadding="4" width=80%
! width=40% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " |GTA01 - Neo 1973
! width=40% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |GTA02 - Neo FreeRunner
|-
|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
<div align=left>
*[[Neo1973]]
*[[Getting Started with your Neo1973]]
*[[Neo1973 hardware]]
=====Debug Board=====
*[[Neo1973 Debug Board v2]]
*[[Neo1973 Debug Board v3]]

 ※[[: Category:Neo1973 Hardware | See More About Neo 1973....]]
|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
*[[Neo FreeRunner]]
*[[Getting Started with your Neo FreeRunner]]
*[[Neo FreeRunner GTA02 Hardware]]
*[[Neo1973: GTA01Bv4 versus GTA02 comparison]]</div>
*[[GTA02 Openness]]

 ※[[: Category: GTA02 Hardware | See More About GTA02....]]
====Other Products====
*[[OpenMoko-supported hardware]]
*[[HXD8]]

 ※[[:Category:Hardware Support | See More About Hardware Support...]]

|}

==Join Openmoko development==

{| class="wikitable" cellspacing="4" cellpadding="6" width=100%
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | Hardware Docs and Testing
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |Software Documentation
|-
|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
===Getting Started===
* [[Installation guide]]
* [[Customizing the Openmoko Distribution]]
* [[Getting Started with your Neo1973]]
* [[MokoMakefile|Building Openmoko using the MokoMakefile]]
* [[Building OpenMoko from scratch (pre-BBT)]]
* [[Migration to bad block tolerant builds]]

 ※ [[:Category:Guides| See More About Guides...]]
=== Hardware Reference Documentation ===

Overview about the Components we use, PCB Photographs
** [[Disassembling Neo1973]] -A photo story about disassembling the hardware
* [[Debug Board]] -The Debug Board for the Neo1973
** [[Connecting Neo1973 with Debug Board v2]]
** [[Neo1973 Debug Board v1]] -The old version of the Debug Board
* [[QT2410]] -A S3C2410 development board that we used during early development

 ※[[:Category: Hardware | See More About Hardware]]
===Test===
*[[GSM unit test]]
*[[GSM 850 test]]
*[[GSM unit test]]
*[[Test Plans]]
 ※ [[:Category: Test | See More About Test]]

===Emulation===
*[[Getting OpenMoko working on host with Xephyr]]
*[[Test_Openmoko Emulation with chroot image]]

|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |

=== Software Reference Documentation ===
* Architectural
** [[OpenmokoFramework]] -The Openmoko Application Framework
* Host utilities
** [[sjf2410-linux]] -a JTAG NAND flashing program, last-resort phone un-bricking
** [[s3c2410_boot_usb]] -a program for transferring code to the RAM of QT2410 (not Neo1973)
** [[Toolchain]] -The toolchain we use for compilation
** [[Neo1973 OpenOCD]] -The On-Chip Debugger we use for development
** [[OpenEmbedded]] -The distribution building framework
* Device Software
** Low-Level
*** [[u-boot]] -The bootloader we use, including docs to our modifications
*** [[kernel]] -The Linux Kernel we use, including docs to our modifications
** Userspace
*** [[gsmd]] -the GSM daemon managing the GSM Modem
*** [[agpsd]] -the AGPS (Assisted GPS) daemon
*** [[OpenMoko]] -The Openmoko distribution
**** [[Openmoko_Core_Applications | Included Applications]]
**** [[OpenMoko2007]] - The first intended release of it
**** [[Userspace root image]]

※[[:Category: Software | See More About Software ]]

|}

==Openmoko community==
Anyone can join the Openmoko project and contribute to designing open products. Join us and collaborate through any of the [[Development resources | project resources]], including this Openmoko Wiki. See the [[Help:Contents | wiki editing help]]page for information on making contributions to this wiki.

You can start by using the [[introduction]] page, photos, videos and Openmoko Wiki Official Index Page. As always, the usual [[FAQ | Frequently Asked Questions]] (FAQ) and [http://lists.openmoko.org/mailman/listinfo/| mailing list] pages are helpful.

{| class="wikitable" cellspacing="4" cellpadding="6" width=100%
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | In News
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |Community & Events
|-
|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |
==Getting Started ==
*[[Getting Started with your Neo FreeRunner]]
*[[Getting Started with your Neo1973]]
==Snapshot==
*You can always download the [http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/ latest build] here.
*Reviews of the daily snapshot build are [[Snapshot_review|here]] and the recommended kernel and root image from the review will always be available [http://downloads.openmoko.org/recommended/ here].
Note that the recommended set is not always the latest, but is the most stable, reliable, and functional.
|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |

== Community Update==
For the latest status updates, see [[Community_Updates|Community Updates]]

 ※[[:Category:Community| See More About Community...]]

==Get the overview of wiki==
*To get the overview of Openmoko Wiki, see [[Openmoko Wiki Official Index Page]].
==Events==
*[[Summer of Code 2008]]
*[[OpenMoko Education/zh tw]]
*[[Events:FOSDEM 2008]]
*[[OpenLab]]

 ※[[:Category:Event| See More About Event...]]

|}

==Getting started with Openmoko Wiki==
The Openmoko Wiki is open. Everyone can join. You'll find information including: hardware and software documentation, bug lists, community news of Openmoko and much more. Join our wiki, edit the wiki, contribute valued content, and help others. For the full picture of Openmoko Wiki, please visit the [[Openmoko Wiki Official Index Page|Openmoko Wiki Official Index Page]].

* Please read our [[Openmoko Wiki Editing Guidelines]]
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://meta.wikimedia.org/wiki/Help:Wikitext_reference MediaWiki Wikitext Reference]
* If you add a new page, you can reference the [[Openmoko Wiki Categories Index Page|Openmoko Wiki Categories Index Page]] to put your page on the right category.
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]

※[[:Category: Help | See More About Help ]]

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

Neo FreeRunner Openness

2008-05-06T22:35:20Z

Flerchjj:

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 still missing on Samsungs site, but 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]]. No further documentation available?
|-
|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 will be released in the future according to http://lists.openmoko.org/pipermail/community/2007-September/010175.html . Speaks OpenGL ES 1.2 according to vendor homepage.
|-
|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
|Thankfully it seems to be compatible with a widely used and cheap other one ;)
|-
|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]]

Neo FreeRunner Hardware

2008-05-05T00:16:34Z

Flerchjj: Added CAD File 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.



[[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 in noisy environments)
*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 case for the FreeRunner is all black, as seen on the front page of the wiki.

Openmoko has released the CAD files for the case schematics for the OpenMoko [[Neo1973]] (GTA01) and Neo FreeRunner. These are available in the original Pro/E (.asm/.prt) format and alternative formats created from the originals.

We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.

* [http://downloads.openmoko.org/CAD/NeoFreerunner_ProE.zip The original Pro/E (.asm/.prt) format]

[http://downloads.openmoko.org/CAD/ Browse CAD directory]

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

OpenMoko Community Applications

2008-02-29T04:12:10Z

Flerchjj: /* Minimo */

== Overview ==
This page is intended for ordinary end users of [[OpenMoko]] smartphones. It lists some of the cool applications provided by the Openmoko community that you can install and enjoy. Freedom to share! You can find many more applications here - http://projects.openmoko.org

'''Please note that not all of these applications are in a finished format yet. When they are complete you will be able to download them via a menu on the phone. At the moment, following a recipe of commands in the console window may be needed to install. This will of course improve with time :-) '''

'''Please also note that there is "some risk" in installing developing software or software from an unknown source! However, if the license for the code is an open source license then you have the comfort that anyone in the OpenMoko community has the power to check the operation of the software and thus malicious or vulernable code is minimised'''

Any problems with the software below should be reported to the individual software developer rather than the OpenMoko core team.

== Note to application developers ==

No more than 8 of the best OpenMoko Community Applications should be listed on this page. The main place for OpenMoko device owners to browse software remains http://projects.openmoko.org. Applications listed here should have mass appeal as an advert of what the platform can do for Linux fans and ordinary smartphone users alike.

Please provide
* a link to your project page
* a short video if possible
* screenshots
* indicate whether your application is stable or still under development
* state which models of OpenMoko phone the application is designed for.
* a short paragraph describing features
* the license the code is provided under

Please add your application to the bottom of the list

== TangoGPS ==

{| border="1"
|-
|Project Homepage
|http://www.tangogps.org
|-
|Video
|http://www.youtube.com/watch?v=hn7wuxlTNvs
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|gps and map program
|-
|Software License
|Add your software license here
|-
|}

== Mokopedia ==

{| border="1"
|-
|Project Homepage
|http://mokopedia.projects.openmoko.org/
|-
|Video
|http://www.rabenfrost.net/mokopedia_demo2.ogg
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Special compressed version of Wikipedia stored in your SD storage card. Access to wikipedia wherever you are!
|-
|Software License
|Add your software license here
|-
|}

== thumbtribes ==

{| border="1"
|-
|Project Homepage
|http://thumbtribes.mobi/
|-
|Video
|Need a new one!
|-
|Screenshots
|In a state of flux
|-
|Application Status
|Highly experimental
|-
|Application Description
|Low bandwidth location-aware blogging and messaging
|-
|Software License
|GPL
|-
|}

== Minimo ==

{| border="1"
|-
|Wiki Link
|[[Minimo for Moko]]
|-
|Screenshots
|[[Image:Minimo-slashdot.jpeg|thumb|left]]
|-
|Application Description
|Minimo is a Mozilla based web browser. It features full AJAX support and other goodies. It is listed as an alternative to standard Webkit based browser.
|-
|}

== Cool application name goes here ==

{| border="1"
|-
|Project Homepage
|Add your project hyperlink here
|-
|Video
|Add your video hyperlink here
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Add your cool features here
|-
|Software License
|Add your software license here
|-
|}

OpenMoko Community Applications

2008-02-29T04:11:13Z

Flerchjj: /* Cool application name goes here */

== Overview ==
This page is intended for ordinary end users of [[OpenMoko]] smartphones. It lists some of the cool applications provided by the Openmoko community that you can install and enjoy. Freedom to share! You can find many more applications here - http://projects.openmoko.org

'''Please note that not all of these applications are in a finished format yet. When they are complete you will be able to download them via a menu on the phone. At the moment, following a recipe of commands in the console window may be needed to install. This will of course improve with time :-) '''

'''Please also note that there is "some risk" in installing developing software or software from an unknown source! However, if the license for the code is an open source license then you have the comfort that anyone in the OpenMoko community has the power to check the operation of the software and thus malicious or vulernable code is minimised'''

Any problems with the software below should be reported to the individual software developer rather than the OpenMoko core team.

== Note to application developers ==

No more than 8 of the best OpenMoko Community Applications should be listed on this page. The main place for OpenMoko device owners to browse software remains http://projects.openmoko.org. Applications listed here should have mass appeal as an advert of what the platform can do for Linux fans and ordinary smartphone users alike.

Please provide
* a link to your project page
* a short video if possible
* screenshots
* indicate whether your application is stable or still under development
* state which models of OpenMoko phone the application is designed for.
* a short paragraph describing features
* the license the code is provided under

Please add your application to the bottom of the list

== TangoGPS ==

{| border="1"
|-
|Project Homepage
|http://www.tangogps.org
|-
|Video
|http://www.youtube.com/watch?v=hn7wuxlTNvs
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|gps and map program
|-
|Software License
|Add your software license here
|-
|}

== Mokopedia ==

{| border="1"
|-
|Project Homepage
|http://mokopedia.projects.openmoko.org/
|-
|Video
|http://www.rabenfrost.net/mokopedia_demo2.ogg
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Special compressed version of Wikipedia stored in your SD storage card. Access to wikipedia wherever you are!
|-
|Software License
|Add your software license here
|-
|}

== thumbtribes ==

{| border="1"
|-
|Project Homepage
|http://thumbtribes.mobi/
|-
|Video
|Need a new one!
|-
|Screenshots
|In a state of flux
|-
|Application Status
|Highly experimental
|-
|Application Description
|Low bandwidth location-aware blogging and messaging
|-
|Software License
|GPL
|-
|}

== Minimo ==

{| border="1"
|-
|Wiki Link
|[[Minimo for Moko]]
|-
|Screenshots
|[[Image:Minimo-slashdot.jpeg|thumb|left]]
|-
|Application Description
|Minimo is a Mozilla based web browser. It features full AJAX support and other goodies. It is listetd as an alternative to standard Webkit based browser.
|-
|}

== Cool application name goes here ==

{| border="1"
|-
|Project Homepage
|Add your project hyperlink here
|-
|Video
|Add your video hyperlink here
|-
|Screenshots
|Add your screenshots here
|-
|Application Status
|Add your status notes here
|-
|Application Description
|Add your cool features here
|-
|Software License
|Add your software license here
|-
|}

Openmoko Local Groups: Denver

2008-02-29T04:02:58Z

Flerchjj:

Are there any other OpenMoko community members here?

{|border=1
!Name
!Skills
!Interest
!Location
! Has Device
|-
|[[User:mike|Mike Welter]]
|Programming/Hardware
|Location-based apps.
|Evergreen, CO (Denver)
|Yes (and debug board)
|-
|[[User:Flerchjj|Jeremiah Flerchinger]]
|Programming/Hardware
|Using as VOIP phone, random app development
|Colorado Springs, CO
|No, waiting for GTA02
|}

[[Category:Community]]

Neo 1973 hardware

2008-02-28T21:11:21Z

Flerchjj: added core & instruction set

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

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

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

{{Languages|Neo1973 Hardware}}

[[Category:Neo1973 Hardware| ]]
[[Category:Hardware ]]
[[Category:Supported Phone| ]]

Neo FreeRunner Hardware

2008-02-28T21:08:52Z

Flerchjj: added core & instruction set

[[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 specifics of the hardware by reviewing this introduction page and the pages in the category as shown at the bottom of this page.

You could find more high level definition in [[Neo_FreeRunner_GTA02_Hardware_Specification]]

{{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 Component Side photo]]
[[Image:Gta02a5 pcba ps.JPG|thumb|400px|component (back) side NOTE: GTA02 A5 Print Side photo]]

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

* Data Sheet: FIXME
* User Manual: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page]
* 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: FIXME
* 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.

*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.
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: TBD
* 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]
* 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 

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

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

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

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

===Accessory===

==== Stylus ====

Using 4 in 1 laser pen
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]
*GTA02 standard setup comes with 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
* Default using SANYO 1200mAh cell. 

==== microSD Card ====

GTA02 should comes with one of following microSD card

* Trendsend 512MB microSD card
* SanDisk 512MB microSD card 

==== Charger ====

AKII Technology Charger

*Model: 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: FIXME

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

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

=== GTA02v4 ===
Mass production release candicate 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

=== GTA02v5 ===
Mass production candicate version 2/Mass production version

*First batch fabricate 2008/1/14 at FIC SuZhou
*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
* First batch of prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]

=== 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 - 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
** 850/1800/1900 Band, FCC ID: EUNGTA02
** 900/1800/1900 Band, FCC ID: EUNGTA02E

*NCC (for Taiwan Import)

{{Languages|Neo1973 GTA02 Hardware}}

[[Category:Neo1973 Phase 2 related| ]]
[[Category:Neo1973 Hardware| ]]

Neo FreeRunner Hardware

2008-02-28T03:29:52Z

Flerchjj: reorg to better mirror layout in gta01

[[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 specifics of the hardware by reviewing this introduction page and the pages in the category as shown at the bottom of this page.

You could find more high level definition in [[Neo_FreeRunner_GTA02_Hardware_Specification]]

{{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 Component Side photo]]
[[Image:Gta02a5 pcba ps.JPG|thumb|400px|component (back) side NOTE: GTA02 A5 Print Side photo]]

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

* Data Sheet: FIXME
* User Manual: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page]
* 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: FIXME
* 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.

*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.
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: TBD
* 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]
* 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 

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

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

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

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

===Accessory===

==== Stylus ====

Using 4 in 1 laser pen
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]
*GTA02 standard setup comes with 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
* Default using SANYO 1200mAh cell. 

==== microSD Card ====

GTA02 should comes with one of following microSD card

* Trendsend 512MB microSD card
* SanDisk 512MB microSD card 

==== Charger ====

AKII Technology Charger

*Model: 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: FIXME

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

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

=== GTA02v4 ===
Mass production release candicate 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

=== GTA02v5 ===
Mass production candicate version 2/Mass production version

*First batch fabricate 2008/1/14 at FIC SuZhou
*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
* First batch of prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]

=== 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 - 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
** 850/1800/1900 Band, FCC ID: EUNGTA02
** 900/1800/1900 Band, FCC ID: EUNGTA02E

*NCC (for Taiwan Import)

{{Languages|Neo1973 GTA02 Hardware}}

[[Category:Neo1973 Phase 2 related| ]]
[[Category:Neo1973 Hardware| ]]

Main Page

2008-02-28T00:05:39Z

Flerchjj: Made system specs & software more obvious

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

[[Image:GTA02.jpg |200px|right|frontside]]
OpenMoko™ is an [http://en.wikipedia.org/wiki/Open_source Open Source] project to create the world's first free mobile phone operating system which runs a full X server and can therefore run most X applications. The [[OpenMoko]] project is a community that anyone can join, to help design their ideal phone.

You can install any [[OpenMoko]] software over the whole range of [[OpenMoko-supported hardware|supported phones]], and if you upgrade your phone, you won't lose that software. Bugs fixed on any phone are fixed on all.

The [[Neo1973 | Neo 1973 (GTA01)]] from [[FIC]] is the first of many phones that OpenMoko may be used on and has now sold out (Feb 11 2008) as can be seen here - [https://direct.openmoko.com/ Openmoko Online Shop].

The [[Neo FreeRunner | Neo FreeRunner (GTA02)]] is not yet available - see further down this page for info on the development status and further information. You can add your nickname to those interested buying the Neo FreeRunner [[Buying_Interest_List|here]].

Please join us in collaborating on the OpenMoko project through any of the [[Development resources | project resources]] including this OpenMoko wiki. Please see the [[Help:Contents | wiki editing help]] page for information on making contributions to this wiki. A [[Meet the Core Team | core team]] of developers funded by FIC, Inc. leads the project.

An [[introduction]] page and [[OPENMOKO WIKI Official Index Page |index page]] is available, with [[Introduction#Photos|photos]], [[Introduction#Videos|videos]] and index of wiki . Moreover, the usual [[FAQ | Frequently Asked Questions]] (FAQ) and [[OPENMOKO WIKI Official Index Page |index page]] pages might be helpful. Developers may find the [[ChangeLog | change log]] an important resource.

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

'''OpenMoko Open Source Engineering and Schedule Policy'''
As an extension of the Open Source attitude towards source code, OpenMoko attempts to be open about as much of the engineering process as possible. Obviously this is not always possible, and because this is a fairly new notion, we are still learning how to do this properly. Our current policy is to attempt to tell you as much as possible about what we are doing, but never to attempt any schedule prediction. This is not due to secrecy, but rather is due to the large number of dependencies that are out of our control. For the latest status updates, see [[Community_Updates|Community Updates]]

'''FUTURE MODELS DEVELOPMENT STATUS'''
[[Neo FreeRunner]] is still under development, and we are still testing the hardware. Since this is happening at the kernel and driver level, progress can be monitored on the openmoko-kernel mailing list, which is public. Once we complete this we will build a few more for further testing within the company. If this testing is successful, then we will start manufacturing units for sale. For the latest status updates, see [[Community_Updates|Community Updates]]

Status on the U-Boot and Kernel side can be found at [[Kernel-dev-status|Kernel-dev-status]].

{| class="wikitable" cellspacing="0" cellpadding="5" width=100%
! width=100% colspan="2" style="background:#F9D163;border-left:5px solid white;border-right:5px solid white;border-top:5px solid white;" | Latest status
|-
|valign="TOP" width="50%" style="background:#FCE9B4;border-left:5px solid white;border-bottom:5px solid white;" |
* The latest Qtopia snapshot can now be successfully used to make and receive calls, to send and receive SMS and use Contacts for both. However, if you do not enable suspend, one battery will only last 3-5 hours, but in suspend, incoming calls do not wake up Qtopia! See [[Qtopia on Neo 1973]] for instructions.
|valign="TOP" width="50%" style="background:#FCE9B4;border-right:5px solid white;border-bottom:5px solid white;" |
* The [http://downloads.openmoko.org/snapshots/2007.11/ OpenMoko 2007.11 Snapshot] can make and receive calls most of the time. Power management (suspend, standby time) are still experiencing problems. Reports on the new snapshots built daily (will break sometimes) are [[Snapshot_review|here]]
* For the latest status updates, see [[Community_Updates|Community Updates]]
|}

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

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

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

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

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

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

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

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

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

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

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

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

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



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

CAD models

2008-02-06T15:05:39Z

Flerchjj: /* Official case schematics */

==Official case schematics==

OpenMoko has released the CAD files for the case schematics for the OpenMoko [[Neo1973]] (GTA01). These are available in the original Pro/E (.asm/.prt) format and alternative formats that have been converted to from the originals.

We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact michael@openmoko.org. We are especially interested in the DXF format and in images rendered from these files.

* [http://downloads.openmoko.org/CAD/GTA01_ProE.zip The original Pro/E (.asm/.prt) format]
* [http://downloads.openmoko.org/CAD/GTA01_IGES_STEP.zip IGES & STEP formats]

[http://downloads.openmoko.org/CAD/ Browse CAD directory]

[[Category:Neo1973_Hardware]]

==Artistic Renderings==

A basic 3D rendering has been created for ''artistic'' use. It has also been used to make a short *.mov animation in '''Art of Illusion'''. Feel free to edit it to conceptually illustrate case ideas or provide more exact measurements so we can refine the model.

[http://www.likeasecret.com/Neo1973/Neo1973.aoi Neo1973 Art of Illusion 3D Model] - Not fully accurate, please provide full dimensions if you have them 
[http://www.likeasecret.com/Neo1973/Neo1973.mov Neo1973 Art of Illusion 3D Quicktime rendering] 
[[Image:Neo1973.png]]

CAD models

2008-01-24T17:56:49Z

Flerchjj: /* Conversions of schematics */

Schematics of the existing case/internals have been requested from FIC, but this will take some time, so for the time being the existing case will need to be measured and schematics uploaded here by an owner of a Neo1973.

Even though we don't have schematics or accurate dimensions, a basic 3D rendering has been created for ''artistic'' use. It has also been used to make a short *.mov animation in '''Art of Illusion'''. Feel free to edit it to conceptually illustrate case ideas or provide more exact measurements so we can refine the model.

[http://www.likeasecret.com/Neo1973/Neo1973.aoi Neo1973 Art of Illusion 3D Model] - Not fully accurate, please provide full dimensions if you have them 
[http://www.likeasecret.com/Neo1973/Neo1973.mov Neo1973 Art of Illusion 3D Quicktime rendering] 
[[Image:Neo1973.png]]

==Official case schematics==
The schematics for the FIC [[Neo1973]] GTA01, have been initially released in Pro/E (.asm/.prt) format at [http://downloads.openmoko.org/CAD/GTA01_dimensions.zip a temporary place]. Renderings and conversions of the content are encouraged.

=== Conversions of schematics ===
Converted versions of official have started to appear in the [http://downloads.openmoko.org/CAD CAD Folder].

Some Conversions include the following:
* [http://downloads.openmoko.org/CAD/GTA01_IGES_STEP.zip IGES & STEP formats]
* DXF & others soon to come!

[[Category:Neo1973_Hardware]]

CAD models

2008-01-24T17:53:59Z

Flerchjj: /* Official case schematics */

Wish List - Hardware

2008-01-24T15:47:19Z

Flerchjj: /* Internal Communication Bus */

This page details hardware features which some would like to go into future phones similar to the [[Neo1973]].

Related pages are:
*[[Wishlist - Hardware - Novel Devices]] - openmoko will run on a large number of devices in the future, some of which may be DVD players, cameras, or convergance devices.
*[[Wishlist:Unlikely]] - Hardware that is unlikely to appear in any OpenMoko device, due to it being impossible to fabricate with near-term technology, or for other reasons.
*[[Wishlist:Accessories]] - Accessories that people would like, that connect easily to the phone - initially primarily for the Neo1973
*[[Wishlist:Expansion]] - add-ons to the phone, maybe involving hardware changes, and software and hardware protocols to implement these.

This page is rather long. Before adding a new idea, please read through this page and the above pages, to make sure your idea has not been suggested before.
==Processor==
===A FPGA===
A FPGA is a general purpose reconfigurable logic device.
See [[Wish List - Hardware:FPGA]] for more details.

===Samsung S3C2443===
*[http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2443&&ppmi=1427 Samsung S3C2443] Up to 533 MHz, can act as a USB 2.0 device.

==Internal Memory==
===RAM===
128MB Dedicated for open files, running software etc., not for storage, or 256MB at all would be really nice and enough for any future software.

===ROM===
Enough to Hold O/S and a fair number of applications and their settings. Persistent Storage with XIP capability. About 128 MB.

===Storage===
An internal Micro SDHC should be used for users' files and additional software

==Wireless data networking==

===WiMAX support===
[http://en.wikipedia.org/wiki/Wimax WiMAX] is a high-speed data service, similar to wifi, though longer range and newer. Where service is available, this would complement WiFi. Unfortunately, unlike wifi, frequencies vary worldwide, so global usage may be complex. In South Korea, 2.3Ghz is available for WiMAX, known as WiBro. WiMAX Forum sets heart on 2.5 GHz for global use.
----
Two campuses of the University of California have just completed a deal with a WiMAX service provider to lease UC's ITFS/EBS spectrum to provide WiMAX in the SF Bay Area. Bidding was aggressive between Nextwave, Sprint-Nextel, and Clearwire. Other UC campuses have awarded other contracts throughout California to various of the three contenders. The point here is: these three companies are competing aggressively for spectrum in the 2.5-2.7 GHz range, and it's not limited to CA. At a National ITFS Association meeting in 2005, representatives from Intel said they would be ready to release a WiMAX chipset compatible with these frequencies in 2007, for inclusion in laptops. I assume the folks at [[FIC]] know much more about it that I do! Based on these and other clues, I think WiMAX is coming in the 2.5-2.7 GHz band in the near future... I'll be surprised if I do not see some offerings by early 2009.

-[[User:Tzf|Tzf]] 21:54, 24 November 2007 (CET)

===LTE support===
[http://en.wikipedia.org/wiki/3GPP_Long_Term_Evolution Long Term Evolution (LTE)] is a high-speed data service, similar to WiMax, but designed to be more compatible with existing GSM systems. While Sprint & Clearwire are currently testing WiMax deployment in the US, AT&T and Verizon appear to be in preference of LTE.

While the project is ongoing and general in scope, it has set itself some specific goals, many of which are oriented around upgrading UMTS to a so-called fourth generation mobile communications technology, essentially a wireless broadband Internet system with voice and other services built on top.

===Emerging Protocols===
*[http://en.wikipedia.org/wiki/Near_Field_Communication Near Field Communication] has a few centimeter range, useable for keys, ID badges, pairing bluetooth devices and similar uses. Mentioned in newer bluetooth and SD standards. (No products.)
*[http://en.wikipedia.org/wiki/ZigBee ZigBee] is designed for connecting sensors and switches in buildings, with many options including mesh networks and aggressive power saving compared to bluetooth. (Almost no products available.)
*The [http://en.wikipedia.org/wiki/ANT_%28network%29 ANT network] is for connecting worn devices. Similar to ZigBee, but much simpler and maybe lower power. ([http://www.thisisant.com/?section=9 Short list] of products.)

==Camera==

* A camera that can take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading, buisness card reading, healthcare, servicing, and more.

* Some people can't take cameras into work - a model without the camera, or some way of removing the camera would be useful or leave the camera chip in place and have a removable lens assembly and replacement backcover.
*See [[Hardware:Neo1973:Alternate_Cases:Camera | Alternate Cases:Camera]] for phone casing suggestions.

* See [[Wishlist:Camera]] for a more detailed wishlist.

==Display==
===Multitouch screen===

''Main article: [[Wishlist:Spell_weaving|Spell weaving]]''

See also [http://pogue.blogs.nytimes.com/2007/03/27/the-multi-touch-screen/ this page] containing a link to a video demonstration.

A history of multitouch implementations is [http://billbuxton.com/multitouchOverview.html here] ([http://google.com/search?q=cache:billbuxton.com/multitouchOverview.html google cache version])

*Use examples: [http://www.youtube.com/watch?v=UcKqyn-gUbY&mode=related&search= Multi-touch interface (from Adobe TED)], [http://www.youtube.com/watch?v=1ftJhDBZqss&mode=related&search= Multi Touch (new touchscreen technology)]

===Bigger and better screen===
2.8" widescreen (like in [http://etencorp.com E-ten] PDA/smartphones), or 3.5" widescreen (like in [http://www.expansys.ie/d.aspx?i=134944 Fujitsu Siemens LOOX N560]).

262k or 16.7M colurs for displaying images and especially videos.

OLED for better contrast, more rich colours, and less energy consumption.

Maybe the [http://www.sharpsme.com/Page.aspx/europe/en/part/LS037V7DW01/ LS037V7DW01] by Sharp could be a solution. It has nearly the same specs as the currently used, but 3,7" -- [[User:Wedge | Wedge]]

===Distance sensing touchscreen===
{{Main|Hardware:NearlyTouchScreen}}
TouchKo's (now Wacom Company Ltd.) spatial capacitive "touchscreen", can sense fingers at a small distance, so you do not get your display greasy, and can unlike some touchscreens, be operated with gloves.

===<s>Video acceleration</s>===
Hardware acceleration for video playback and 2D/3D accelleration will be present in [[Neo1973 GTA02]].

===EPD===
Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, lightweight, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].

Pro: laserprinter like quality, glossy, very stable image, easy on the eyes. Electronics are similar to TFT. Very low power consumption.

Con: Black and grey only (like a newspaper, but glossy), although there were already color prototypes in 2005. low framerate (5fps). Can reflect light (like paper), backlight is impossible.

===Transreflective===
It would be nice to have (the option of) a transreflective display, which while being less bright, is readable without needing to power the backlight. Then again, it depends on how much power the backlight uses compared to everything else...

==="Slightly" Larger Screen===
43mm x 57mm (2.8inch diagonal) is tiny. A 53mm x 71mm (3.5 inch diagonal) like on the TD035STEE1 would be a nice improvement. A widescreen format at about 53mm x 82.5mm instead of the 3:4 aspect ratio would be even cooler (if one could be found).

===Second Display===
A 32x32 OLED display possibly on the back for camera framing or on an edge so it can be viewed like a pager.
This could be used to display any number of alerts (from any installed software) the alerts could have a dynamic prioritisation which means during the work day a message from the boss has high priority but lower at home (could be GPS/Time controlled?) multiple alerts shrink the icons to a 3x3 grid higher priority messages get more space.

===Micro Projector===
[http://www.engadget.com/media/2006/02/digismartphone2.jpg Like the one shown here], new cellphones are now coming out with a small, low power projector. This can be used to show movies from your cell phone with 0.5m high image on a while wall for example...

==Input devices==

===No Dependence on Stylus===
The Neo's basic functionality should be completely usable without a stylus, Like the iPhone but with stylus use for precision work.

===A laser projection keyboard===
Similar to [http://www.thinkgeek.com/computing/input/8193/ this], except the device would be integrated into the phone itself. Setting the Neo up on a stand on a flat surface (perhaps a stand could be built into the back of the Neo itself, or into a case) would turn the Neo into a micro-laptop. There may be several issues with the inclusion of this technology, including patents, the space required to project the laser grids, and the power consumption. If possible, however, it would make text input a breeze.

===Just a few more Buttons===

2 buttons more, 3 buttons total, mounted sideways would be enough. You could use them for play/pause and loudness controll while the phone remains in your pocket (display locked, ...), reading mails, rss, ebooks,... without wasting display space and so on.

With 5 buttons in total you could possibly emulate a keyboard (2^5 = 32 combinations) for those who know how to play a flute. Useable onehanded, not wasting display space and faster than t9. (It's not faster than T9 - I've used this system with the microwriter agenda --[[User:Speedevil|Speedevil]] 00:00, 2 July 2007 (CEST)) Hopefully this is not patented already.

===D-Pad and Buttons===
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)

Game buttons would be best on both sides of the screen. The larger the buttons, the better. 2x 4 buttons in up-down-left-right configuration + some extra buttons separately a bit lower on the device would be good for many for emulation games.

Here is a concept drawing of a possible neo1973 gaming version:
(This has a 4-way direction pad, 8 way may be better for gaming)
 
[[Image:Neogame90.jpg]]
 
Shoulder buttons would be a great addition, too. It would be interesting if there was a total 4 of them, one for every corner. It would make the phone very flexible for rotating and 2 to 6 players playing on one device.
 
:''Note'' : The [http://en.wikipedia.org/wiki/Tapwave_Zodiac Tapwave Zodiac] Palm PDA / Game console hybrid had a similar setup - with an analog stick on the left (also used for quick selection using a radial main menu when working as a PDA), 4 buttons on the right (also configurable for shortcuts when using the device as PDA), and 2 shoulder buttons. Also it had and still has an enthusiastic scene of homebrew development (almost any console emulator for PalmOS can also take advantage of the additional buttons and graphic power of the device). If we also take into account the success encountered by the [http://en.wikipedia.org/wiki/GP32 GP32] in the past and the [http://en.wikipedia.org/wiki/GP2X GP2X] currently on the homebrew scene, it's not unreasonable to plan a future OpenMoko device with both a SmartPhone/PDA functionnality ''and'' hand-held console targeting homebrew development.

===Thumb keyboard or keyboard attachment accessory===
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).
*Cheap clippable miniusb keyboard
*One of the layouts proposed in [[Hardware:Keyboards]]
* What about virtual keyboard? [[http://www.extremetech.com/article2/0,3973,539778,00.asp Keyboard]]

===Analogue Controllers===

====Trackball====
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry® models.
Maybe instead an optical sensor as are used in mice could be used so that the whole phone can be moved over a surface just like a mouse. (It could function as a Bluetooth mouse for other devices like laptop computers: see [[Bluetooth_Support#Acting_as_HID_device]]. Adding one other two-axis analogue input (possibly just the screen) would make the Neo usable as a TrackPoint or scroll-and-tilt mouse.) The same sensor might be usable as a barcode reader.

====Analog Joystick====
A joystick, or [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device would provide additional control, compared with touchscreen only.
*A standard [http://en.wikipedia.org/wiki/Pointing_stick pointing stick (ie. TrackPoint)] might serve well. As a fairly standard part, might they be quite inexpensive?

====Dual analogues====
Dual analogue controllers (one trackball or joystick above, one below the screen, most likely) might even be feasible. That might be overkill since the accelerometers or touchscreen can be used to provide a second analogue input. But it would be nice to have four axes of analogue control without having to tilt the screen away from you or partly cover it with your hand.

===TV/radio receiver===
[[Digital Television]], [[Digital Radio]] or even normal analogue TV/radio is widely available in the world, though unfortunately in various different forms. In markets where one standard is widespread, and hardware is suitable, it would be a great extension of the phone to a general entertainment device for when you're away from home. Multi standard devices would be ideal, but may not be small, low-power, or cheap.
A good start would be an FM tuner, since it's one of the most widely used formats of radio broadcasting in the world.

Here's a selection of chips, though it's not clear if the drivers are open source. http://www.sigmatel.com/products/portable/wireless/fmtuner.aspx#fragment-14
http://www.st.com/stonline/products/families/automotive/am_fm_tuners.htm

===Accelerometer===
This enables the phone to sense which direction 'down' is, and to sense any movements the phone makes.

See [[Accelerometer Fundamentals]] for more information on accelerometers as they may be used in phones.

In some cases integrated gyroscopes may also be needed. A [[#Digital compass]] can even be of more use since it gives absolute rotation so slow rotations could also be measured. A 3D compass would be nicest, but a simple 2D compass already is a helpful addition to the accelerometers.

*[[Wishlist:3D Viewport|3D Viewport]]
*[[Wishlist:Computer Mouse|Computer Mouse]]
*[[Wishlist:Determine Position|Determine Position]]
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]
*Change media player playlist when jogging vs walking.
*Attempt to use to stabilise any future camera.

This feature is scheduled for inclusion in the phase 2 Neo1973, GTA02.

===Side-Mounted Touch Strip===
Add a "touch strip" sensor onto the side of the phone which can be used to scroll. By having it on the side you can use your thumb to scroll comfortably while holding the phone one-handed. An 8-element capacitive sensor would work wonderfully and be easy to fab using either a Quantum QT411 (http://www.qprox.com/products/qslide_qt411.php) or Analog Devices AD7143 (http://www.analog.com/en/prod/0,2877,AD7143,00.html) controller. The Analog Devices chip seems better suited due to it's smaller allowable element size.
*With the AD7143 you can have an 8-element (128-position) 25mm long strip - Perfect!.
*With a few OLED screens beneath the strip it could be used as dynamic configurable buttons/alerts eg. zoom/flash/shutter with a camera application and SMS/Email/Voicemail alerts in standby

===Heart Rate Compatibility===

An RF interface to receive data from popular heart rate straps (Polar, Garmin, Sigma, Suunto, etc.). This would go along well with the existing GPS functionality and possible future Accelerometer functionality to make for a full-blown workout tool.

Software can be written to track heart rate along a running, cycling, skiing, swimming loop, to monitor max and min heart rate, to match heart rate data to GPS coordinates and print map data w/ relevant data.

===Digital compass===
A digital compass is useful for orienting maps to the terrain and other location/direction/orientation based applications (... is 300 meter that way) when the user is standing still (regardless of GPS reception) and for following a bearing when GPS reception is poor or speed is low. Also could be used to make the accelerometer data more exact.

Very small [[I2C]] sensors like [http://www.ssec.honeywell.com/magnetic/hmc6352.html Honeywell's HMC6352 2-Axis Digital Integrated Compass] (6.5 x 6.5 x 1.5 mm) are very appropriate for this.

*[[Wishlist:Auto Align Map]]

See [[Wishlist - Hardware: Digital compass]] for more information

===Thermometer===
An electronic thermometer might become handy for some users.

There are very small [[I2C]] devices available, that could easily integrate to the existing bus. For example [http://focus.ti.com/docs/prod/folders/print/tmp100.html this one from ti].
(Could just be cheap and use the thermometer from the battery, thats how they did it in the nokia 5140's). Also is integrated in a barometer/altimeter like the SMD500 mentioned in [[Wish List - Hardware - Atmospheric]].
::But if you carry it in you pocket it is unlikely to show the correct air temperature anyway. [[User:AudriusA|AudriusA]] 17:12, 12 January 2008 (CET)

===Barometer and Variometer (Altimeter)===

A Barometer measures air pressure. This can be used to give weather information, and also as a variometer, to sense relative altitude. Variometers are commonly used in flying microlight and ultralight aircraft, to get accurate relative altitude.

These are also common on high end GPS units. This is a great feature for walkers as you can tell how far you have got on any ascent/decent.

See [[Wish List - Hardware - Atmospheric]] for more information.

===Finger print sensor===
A fingerprint sensor gives easy and fast access to the phone, could lock the touchscreen etc. An example of this device can be found at [http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_BrowseCatalog-Start?CategoryName=cpu_VAIONotebookComputers_UX_Series&Dept=computers Sony UX17].

Most fingerprint sensors in the embedded market include a navigation mode, where they work similar to either a touch-stick or touch-pad of a laptop.

===Barcode Scanner===
*less cpu intensive and more reliable than camera+ocr
*though, bluetooth-enabled readers are already available.

===Light Sensor===
Ability to sense ambient light, and act accordingly. i.e if it's 3am and LightValue<.1 then Ring Quietly.

===Wheel===
A navigation wheel like on a sony/ericsson 810i would be nice.

===Proximity Sensor===
Switch off backlight when you place the phone to your ear. Prevent accidental activation of speakerphone or other sounds when the phone is near the ear (prevent hearing damage). Possibly switch the speakerphone on or off automatically depending on if the phone is by your head or not.

=== Make ''all'' unlocking of phone, password protected===

When my (current non-neophone) phone is in my pocket and I have it locked, it sometimes accidentally unlocks itself since only two keystrokes in the correct order are necessary to unlock it. When it's unlocked and still in my pocket it sometimes calls someone without my knowledge. All phones I've seen today have a press-just-one-button bypass to answer an incoming call even when the phone is locked. I suggest making the locking mechanism let the user configure it so that the user has to enter a password even for answering incoming calls. The likeliness of the phone accidentally runbbing against my car keys, hitting a ten character long password, unlocking the phone without my knowledge and consent is low enough even for us most unlucky users.

==Expansion==
===Positioning of Buttons, Connections and ports===

Ideally any cable ports such as charging, USB, audio, docking should not get in the way of your hand or fingers when holding it in it's normal orientation. For the sake of SDIO cards an external SD slot should be on the top edge. IR for remote control software and ease of inter-device communication should be on the corner so that it is facing away from you for both orientations. Buttons obviously are positioned for finger control. An example of how '''not''' to do this would be the HTC Universal

===Storage===

====MMC/SD/SDIO slot (rather than?) miniSD or microSD====
*Cheaper, more durable cards in a widely accepted format.
*Much much larger storage capacity, [http://blog.scifi.com/tech/archives/2007/08/23/toshiba_unleash_1.html even 32GB]
*Cards are harder to lose
*Wider selection of accessories, including SDIO accessories.
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)
*[http://en.wikipedia.org/wiki/Secure_Digital_card#SDHC SDHC] compatible. It seems to already have the right hardware for it - see [[Neo1973_Hardware#microSD-Card]].

====Two SD slots====
*Micro SDHC for /home partition. Keep like current design underneath SIM card
*Hot swappable externally accessible normal size SDHC/SDIO slot

=== Internal Communication Bus ===
*A standard and/or documented internal communication bus of some sort could simplify adding new hardware modules.
*Serial USB or I2C connector internal to case towards the top
*Several digital I/O pins that operate at TTL levels
*A few analogue I/O pins attached to a A/D converter
*Documentation of Debug board connector could provide some of this functionality.

I2C is used on the Neo with some details of resources already in use documented!
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973.

===Local Communication===

====USB====
* 5V Powered, to avoid having to carry around a hub for when you want to occasionally plug in a memory stick. Many powered hubs will not recognize a totally unpowered host. Provide a maximum current to drive a basic USB keyboard/memory stick/mouse/webcam/astrowebcam. This could be done by adding a small cheap power converter like the [http://www.national.com/pf/LM/LM2753.html LM2753]
* USB 2.0
* Standard type A socket for quick & easy insertion of memory sticks etc.
* OTG, to be able connect usb keyboard like [http://www.mobile-review.com/pda/review/cherry-kb-en.shtml Cherry G84-4321 SUNRG]
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash.
* Protection against incorrectly wired USB ports: some USB ports are wired incorrectly; if the +5V and GND are swapped, the device would get -5V when it's expecting +5V, which could burn some chips. A reverse-biased diode between +5V and GND, D+ and GND, D- and GND, and (if used) ID and GND, with a low enough forward voltage drop (to limite the negative voltages to what the chips can withstand), would protect the device by tripping the port's short circuit protection.

====Wireless USB support====
[http://en.wikipedia.org/wiki/Wireless_USB Wireless USB] is the wireless version of USB offering data-rates up to 480 Mbit/s over short distances (<3 meter). Chipsets suitable for a phone are likely to take some time to be available.

====SIR/FIR transceiver (Serial Infrared) / IR remote control====
*An infrared transceiver is cheap, small, and useful for sync with many laptops and mobile phones.
*Replace/emulate all IR-based remote controls used for your tv, vcr, etc on your neo cell phone.
** replaces multiple 'dumb' devices with a single intelligent device (your neo) that you will probably carry with you at all times anyway.
**Command sets should be retrieved from a database or learned from other less intelligent remote control devices with macros.
**reduces clutter, particularly in the living room.
**inceases the neo's practical status as an 'always-have' device.

Other uses.
*Detecting reflections from inside of a caddy, and switching from active mode.
*FIR would be a nice option, as it's some 40 times faster than SIR.

===Other===

====Video Out====
*Through a docking port
**S-Video/Composite Out
**DVI Out
**HDMI Out
**Display Port

==Output devices==

===LED===
*The Neo1973 GTA02 will have LEDs of some sort behind at least one button. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]
*A blinking LED would be a cheap, low power way to inform the user of new SMS/Email....
**An alternative to this would be for one small part of the LCD to be separately backlit.
**This requires the CPU and LCD to be somewhat active, to keep the LCD refreshed, but gives much more information.
**A Small OLED Screen could be used and display much more information than a LED with minimal power usage.

*For example a multicolor LED which pulses yellow for GSM/GPRS transmit, blue for Bluetooth/Wifi, green to indicate non-urgent information - missed call etc, red to indicate battery low or other urgent notices.

**The LED and button ideas could be combined: illuminated buttons.
**It must be possible to completely disable the LED to save power or other personal preferences.

=== Flashlight ===
For finding keys, or any other application. May also optionally pulse in time with ring, to make phone more visible.
This is really well done in Nokia 5500.

-I second this one. The most used feature in my Nokia 5140 after the calling and sms features is the flashlight. It's just one simple LED, but powerful enough to see with if it's really dark. If it ain't dark, you won't need the light anyway. :)

Also, Who hasn't lost their keys and opened up their cell phone to use as a flashlight?

=== FM transmitter ===
Small FM transmitter to output to car, and other nearby radios.

Fix the biggest flaw in the iPod before Apple does!

=== Infrared Transmitter w/ universal remote software ===
Infrared LED on top of device with universal remote software so you can control televisions, DVDs etc.
[http://www.novii.tv/ Here] is an example of universal remote software.
===HAC Compliance===
[http://quux.wiki.zoho.com/WhereAreHACphones.html Here] is some summary/discussion of how hearing aid compliance rules work in the US. Specifically it would be nice to see the phone include a [http://www.hearingresearch.org/Dr.Ross/telecoil_and_telephones.htm telecoil], which allows the phone to connect wirelessly to many standard hearing aids.

==Mobile Communication options==

===Generic Access Network / Unlicensed Mobile Access===
This technology requires cooperation from the cellular provider, but [http://en.wikipedia.org/wiki/Unlicensed_Mobile_Access UMA/GAN] is already offered by T-Mobile in the United States, and perhaps others in other countries. Allowing the user to roam from GSM to wifi, this technology can save the end user a significant amount of money, and also allow the user to deploy coverage where there was none before. There are only a few UMA capable phones currently, but it would be great if this could be made to work on a phase 2 type OpenMoko device.

Note that this features requires more advanced access to the GSM modem.
Special messages needs to be exchanged with the network.

===Faster/better mobile connectivity.===
[http://en.wikipedia.org/wiki/Gsm GSM]/[http://en.wikipedia.org/wiki/GPRS GPRS] is at best slow. An incremental improvement would be a radio with [http://en.wikipedia.org/wiki/EDGE EDGE ] support. EDGE is an evolved GSM standard and, like GPRS, it operates on the same frequency as voice. This means a quad-band EDGE radio will have near-complete worldwide coverage.

[http://en.wikipedia.org/wiki/UMTS UMTS] - which is widespread in Europe and being deployed in the US, [http://en.wikipedia.org/wiki/HSDPA HSDPA] (asia) and any other mobile standards would be nice for faster data connectivity and coverage.
It is unlikely that all of these will be supported initially, but it is a goal. These faster standards operate in different frequencies from GSM/GPRS/EDGE. Which frequency exactly will depend on the carrier and country. For UMTS in the US, AT&T uses 850/1900 MHz but T-Mobile will use 2100/1700 MHz for example.

Until that goal is reached, it is likely that some phones will be brought out for various specific markets - Europe, Asia, US.

===Ability to use multiple SIMs/networks===
* External SIM sockets are widely available in China, a dual external socket would be a very good solution.
* [http://www.fonefunshop.co.uk/dualsim/digital.htm Dual SIM card kit] - two SIMs are trimmed and combined, software supportwould be needed, and both can't be used at once...
* Some networks support multiple numbers on one SIM. Unfortunately this won't allow split networks.
* A second/dual GSM module would allow full use of both sims at all times.
* As a hack, [http://wiki.openmoko.org/wiki/Wish_List#Bluetooth_powered_Multi-SIM_support use another mobile via BT].
** As many as three SIM slots would be genuinely useful, especially for a 3G phone - some 3G data tariffs are only available on data-only SIMs. A user could quite reasonably have one SIM for data, once SIM for his personal voice calls, and a third SIM for his business number.

===PMR446/FRS Radio===
* Include a PMR/FRS Radio.
* A two-way walkie talkie lets you use the phone to communicate with friends without requiring a GSM connection (crowded networks at festivals, at locations with no GSM coverage).

===[[DECT]]===
* Include a [[DECT]] GAP/CAT-iq transceiver so you can use your home and/or office PSTN line
** Ability to use Alcatel phonebook stuff (like provided by the eventphone.de phone equipment) would be very nice too

===[[SIP phone]]===
Make stripped down (and thus cheaper) version of the Neo1973 phone for use as a SIP phone. Remove GPS, GSM, accelerometers, stylus.

Addition of an centimeters-precise location system [http://en.wikipedia.org/wiki/Real_Time_Location_Systems RTLS] would be nice, as it will allow highly sensible indoor context detection. Imagine putting the phone next to your mirror (where you shave daily) and watch it automatically switch to news radio channel. Or put it next to your bed and see it automatically switch to "sleeping" mode, when only calls from predefined numbers are accepted.

=='''Casing'''==
See also: [[Alternate Neo1973 case designs]] for a list of cases being considered for design/manufacture by the community.

=== [[Hardware:Neo1973:Alternate_Cases:Expansion_Module_Casing | Expansion Module Casing]] ===
Longer case (150-160mm+) with space in the top to put expansion modules, including test & hobby hardware. Would require use of a standard internal power & communications bus. Could be left empty with blank cover or house cameras, solar panels, a crank powered charger, special transmitters/recievers, or anything else imaginable.

[http://www.likeasecret.com/Neo1973/Neo1973-Exp.mov Neo1973 Expansion Module Quicktime rendering] 
[[Image:Neo1973-Exp.png]]

=== Expansion Back Casing ===
Replacement backs with additional features ranging from solar power, larger batteries, extra hardware, ...

===[[Hardware:Neo1973:Alternate_Cases:Expansion_Front_Casing|Expansion Front Casing]]===
Replacement fronts with e.g. extra buttons.

=== Space efficient Lanyard ===
The hole at the bottom of the phone takes a lot of space. A [http://en.wikipedia.org/wiki/Kensington_Security_Slot Kensington Security Slot] could be used instead.

=== Rugged version ===
We need something you can drop from 4 feet in to a puddle of dirty water on construction site. Sunlight readable display, maybe aluminium case. The big ugly pseudo military version.

=== Transparent ===
Make a transparent, see-through casing. Why do we need a closed casing for open hardware and open software? Show the world it is a truly Free/Open source phone.

That makes sense to me. I second that idea!

=== Blank ===
Even though the transparent case would work too, I would like to see a blank case of pure black or white so people could have the option of air-brushing,painting or even drawing on the case.

==Misc==
===Galileo/GLONASS/GPS receiver===
*A multi-standard satellite positioning module would be nice eventually, it does not seem to be near-term due to chipset availability problems. Galileo is the to be launched (2011) European positioning system. GLONASS is the already existing Russian one.

===X10 RF Remote===
Many PC-based media centers are being equipped with an RF (433 MHz) / X10-based remote control. The [http://en.wikipedia.org/wiki/X10_(industry_standard) X10] protocol also facilitates home automation to control lamps, switches, etc.
The advantages of using RF for control instead of Infra-red this that it also works when furniture, walls, or doors are blocking the path between RF remote and the equipment or device. [http://www.lirc.org/ Lirc] supports X10-based RF remotes (but expects having an USB RF receiver attached to the media center).

===RFID tag/RFID Reader===
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]
*An enable-able tag would be of use - for example being able to use the phone to open doors, or cars. Unfortunately, it's moderately hard to do secure programmable tags that are compatible with existing systems, for obvious reasons.
* Say you have RFID tags on your personal belongings: cellphone, keys... Neo could be programmed to remember the last recorded GPS location before it lost contact with the respective RFIDs. It'd be trivial to check where you left your cellphone, get directions from a map...or beep when the phone gets out of RFID range.

*I agree with this idea, a great idea and you have to do it (Jackcday)

===NFC chip===
*A Near Field Communication chip, with this chip it will be possible to pay with your phone (like a credit card)in the near future, see [http://www.nokia.com/A4305081 Nokia]for details
*NXP is a chip fabricator which provides NFC chips [http://nxp.com NXP] direct link>> www.nxp.com/#/pip/cb=[type=product,path=/53420/53424]|pip=[pfp=53424][0] their chips also support the above RFID reading

===Less weight===
* Work on the weight of the Neo1973 and following devices. At the present time the Neo1973 is just a moderate / normal business or multimedia phone. The ordinary "user" may want something lighter. Take a look at the following table, that's the Neo1973 compared with other common bussiness or multimedia phones.
{|border="1"
| Neo1973 || Fujitsu-Siemens LOOX N560 || E-Ten Glofiish X500+ || Sony Ericsson P990i || iPhone || Nokia E65
|-
| 184 g || 160 g || 146 g || 150 g || 135 g || 115 g
|-
|}

===Make it smaller===
* To stay within physical matters: Maybe the Neo1973 is also just a normal business/multimedia phone when looking at the size. It would be great the shrink it a bit. Especially the thickness of 18.5 mm could be worked on!

===Standard 3.5mm headphone jack===
The Neo1973 uses a 4-conductor 2.5mm jack for stereo headphones and a microphone. A 2.5mm jack is the most common for headsets.

There is an emerging convention used in the Nokia N800 and some other devices. A 4-conductor 3.5mm jack that can use a microphone with special headsets, but can also be used with off-the-shelf 3.5mm stereo headphones. Adapters to 2.5mm are of course available and this 3.5mm jack is much more robust.

Neglecting space limitations, multiple sockets - 2.5mm and 3.5mm would be nice. Probably not practical in a phone. Other expanded plugs might allow remote controls.

Other uses might be better met using bluetooth, or USB audio.

===Laser Pointer===
Include a built in laser pointer. Everything is better with lasers.

===Completely free hardware===
Consider selling one device with absolutely no non-free components in it, even if that means dropping the GSM support. I believe having one such device available would be good, because then it could be recommended by organizations like the FSF which typically never recommends anything if it has even a little non-free code in it.

=== Consider economy / inexpensive / less featured edition ===
Some people want less features, because they do not need them. Leaving out some features either lets the phone get smaller or possibly enhances battery live.

One big suggestion in this area is a b/w lower res display instead of the big color display.

=== Inductive Charger ===

It would be nice if it was possible to charge the phone without having to connect a cable. I'd like to have a simple docking station with an inductive charger like the type that's used for electric toothbrushes [http://home.howstuffworks.com/question292.htm ]. The charger itself could get its power from a standard wall-wart power supply, or it could be USB/Firewire powered.

=== Solarpanel/dynamo Charger===

It would be very nice to be able to charge the phone outside of the electric grid (for example on hikes and boating trips). A combined solarpanel and muscle empowered (rotational etc.) charger would do the trick nicely.

'''some mobile Solarpanels'''

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=off01011&k_id=1400&hot=0 Off-Grid Systems Sunbag L]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=off01001&k_id=1400&hot=0 Off-Grid Systems Sunbag S]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=sv_01011&k_id=1400&hot=0 Silva Solar I]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=sv_01012&k_id=1400&hot=0 Silva Solar II]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=sol01011&k_id=1400&hot=0 Solarc e-Go Professional]

[http://www.heise.de/mobil/suche/ergebnis?rm=result;q=solar;url=/mobil/artikel/74142/;words=solar Solarc e-Go *]

[http://www.heise.de/newsticker/suche/ergebnis?rm=result;words=Solar%20solar;q=solar;url=/newsticker/meldung/91536/ Solar JKT]

- I think a dynamo charger ("share charger", rotational, ...) would be more practical as a peripheral, connected through the USB-interface using the same principle cellphones now charge when connected to an USB-port. You could very easily hack this together. [http://www.metacafe.com/watch/449950/hack_a_flashlight_to_power_your/ flashligh recharge hack] Random thought; Why not create some merchandise toys with a small lithium battery which charge through centrifugal force allowing to recharge the phone with a small "general" connector.

[http://www.heise.de/mobil/artikel/61368/0 Article about aome mobile power-sources]

=== Plastic Solar/Back side on the Neo===

Sollar cells from Plastic, on the reverse side of the Neo 1973
modified and intergreated in the batery backcover/flap,
like an energy source when the display is in standby mode.
Thats can be use also as alternate charge method's and also helps in emergency.

==Related Hardware==
See [[Related Hardware]]

[[Category:Hardware ideas| ]]
[[Category:User]]

Neo 1973 hardware

2008-01-24T15:42:41Z

Flerchjj: /* Main components */

[[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 version of Neo1973 hardware, which may be discontinued. The future one is GTA02 of which there is an own page: [[Neo1973 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]
* 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.

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

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

{{Languages|Neo1973 Hardware}}

[[Category:Neo1973 Hardware| ]]

Neo FreeRunner Hardware

2008-01-24T15:41:26Z

Flerchjj: /* I2C Devices */

[[OpenMoko]] is a software distribution stack that sits on top of a [[hardware]] platform. The [[Neo1973|Neo1973 GTA02]] 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|This page is about hardware that is currently in '''design/prototype''' phase, changes are frequent}}

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

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

== Main components ==
=== Processor ===
The main Processor (CPU) of the Neo1973 GTA02 is a [[Samsung S3C2442B]] (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
* BSDL File: FIXME
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt

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

* Product Homepage: FIXME
* Data Sheet: FIXE
* Connected to: S3C2442 NAND controller

12MBit NOR flash for 'unbrickable emergency boot' feature.

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

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

U-blox ANTARIS 4 chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
* Driver: none needed, talks standard NMEA
* Datasheet: [http://atmel.com/dyn/resources/prod_documents/doc4928.pdf Atmel ATR0635]

=== microSD-Card ===
The Neo1973 has one microSD aka Transflash slot.
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: TBD
* [[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)]

=== LCD Module (LCM) ===
This is a 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 toppoly (tpo) 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]
* 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

==== Stylus ====

Seemingly identical to [http://search.ebay.com/4in1-PDA-Stylus-LED-Light-Torch-Laser-Pointer-Pen this one on ebay]

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

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

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

=== Graphics ===

Smedia Glamo 3362.
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: TBD
* Connected to: S3C2442 Address/Data bus

=== WiFi ===

TBD (Atheros AR6001 based)
* Connected to: S3C2442 SDIO controller
* Driver: http://svn.openmoko.org/developers/sameo/patches/

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

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

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

=== Power Management ===
A Philips PCF50633 is used for [[Neo1973_Power_Management|power management]].

* Data Sheet: FIXME
* User Manual: FIXME
* Connected to: S3C2442 via I2C, client address is 0x08.
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch

=== Battery ===
The [[Neo1973 GTA02 Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility 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 GTA02 features two buttons:
# [[Neo1973 Power Button|The Power Button]]
# [[Neo1973 AUX Button|The "Aux" button]]

=== 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 I2C, client addresses FIXME, S3C2442 EINT interrupt inputs.

== History ==

=== GTA02v1 ===
First generation of prototypes that was given to internal OpenMoko software developers.

It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash

* ATAG_REVISION: FIXME

=== GTA02v2 ===
Second generation of prototypes

FIXME

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

== Approval ==
TBD

{{Languages|Neo1973 GTA02 Hardware}}

[[Category:Neo1973 Phase 2 related| ]]
[[Category:Neo1973 Hardware| ]]

Neo FreeRunner Hardware

2008-01-24T15:40:25Z

Flerchjj: /* Main components */

[[OpenMoko]] is a software distribution stack that sits on top of a [[hardware]] platform. The [[Neo1973|Neo1973 GTA02]] 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|This page is about hardware that is currently in '''design/prototype''' phase, changes are frequent}}

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

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

== Main components ==
=== Processor ===
The main Processor (CPU) of the Neo1973 GTA02 is a [[Samsung S3C2442B]] (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
* BSDL File: FIXME
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt

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

* Product Homepage: FIXME
* Data Sheet: FIXE
* Connected to: S3C2442 NAND controller

12MBit NOR flash for 'unbrickable emergency boot' feature.

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

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

U-blox ANTARIS 4 chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
* Driver: none needed, talks standard NMEA
* Datasheet: [http://atmel.com/dyn/resources/prod_documents/doc4928.pdf Atmel ATR0635]

=== microSD-Card ===
The Neo1973 has one microSD aka Transflash slot.
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: TBD
* [[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)]

=== LCD Module (LCM) ===
This is a 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 toppoly (tpo) 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]
* 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

==== Stylus ====

Seemingly identical to [http://search.ebay.com/4in1-PDA-Stylus-LED-Light-Torch-Laser-Pointer-Pen this one on ebay]

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

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

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

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

=== Graphics ===

Smedia Glamo 3362.
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/smedia-glamo.patch
* Data sheet: TBD
* Connected to: S3C2442 Address/Data bus

=== WiFi ===

TBD (Atheros AR6001 based)
* Connected to: S3C2442 SDIO controller
* Driver: http://svn.openmoko.org/developers/sameo/patches/

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

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

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

=== Power Management ===
A Philips PCF50633 is used for [[Neo1973_Power_Management|power management]].

* Data Sheet: FIXME
* User Manual: FIXME
* Connected to: S3C2442 via I2C, client address is 0x08.
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch

=== Battery ===
The [[Neo1973 GTA02 Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility 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 GTA02 features two buttons:
# [[Neo1973 Power Button|The Power Button]]
# [[Neo1973 AUX Button|The "Aux" button]]

=== 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 I2C, client addresses FIXME, S3C2442 EINT interrupt inputs.

== History ==

=== GTA02v1 ===
First generation of prototypes that was given to internal OpenMoko software developers.

It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash

* ATAG_REVISION: FIXME

=== GTA02v2 ===
Second generation of prototypes

FIXME

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

== Approval ==
TBD

{{Languages|Neo1973 GTA02 Hardware}}

[[Category:Neo1973 Phase 2 related| ]]
[[Category:Neo1973 Hardware| ]]

Hardware:Neo 1973:Alternate Cases

2008-01-17T03:26:09Z

Flerchjj: /* Manufacture */

This page is a repository for alternate case designs for the [[Neo1973]], intended to be designed, built and fitted by the community/the phone's owner. Many specific suggestions can be found in [[Wish List - Hardware#Casing]] and corresponding links.

Each alternate case design suggestion needs some or all of: a description, intended uses, design options, a 3D model in an open format (e.g. [http://en.wikipedia.org/wiki/STL_(file_format) .stl], .blend (Blender), .obj (Wavefront), [http://en.wikipedia.org/wiki/Art_of_Illusion .aoi (Art of Illusion)] ), rendered images of the intended design, materials, components and information regarding interfacing electronically to components within the phone.

== Manufacture ==

There are numerous rapid prototyping companies that will very cheaply make small run components from various polymers, including:

[http://www.absprototypes.net ABS Protytpes] - Invalid website name

[http://ponoko.com Ponoko] - requires EPS files (makes 2D flat cut-outs)

[http://rapidobject.com Rapid Object] - requires STL or VRML (for extra detailed models) files

[http://www.rapidprototyping.co.nz Rapid Prototyping New Zealand] - 3D powder based printer, not particularly well suited to this application.

[http://www.redeyerpm.com/Default.aspx Red Eye RPM] - requires STL files

Other materials may require traditional manufacturing techniques including milling, forging, injection-moulding, either by the user or short-run companies such as:

[http://emachineshop.com/ eMachine Shop] - Requires companies own MS Windows based drawing software

[http://www.msersen.net/msgme.php?p={$pagef}&c={$setcount}/ (4 axis) gantry style cnc router for hire. Click for inquiries]

[http://techshop.ws Techshop]

==Cost Example==
Rapid Object charge from 1.9 Euros per cm^3 of material (photosensitive polymer) used, plus postage. The case for the Neo looks to be about 1.5mm thick, so conservatively, the back of the case will be approximately: 
120 x 60 x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 10,800 
+ 3,240

= 14,040 mm^3

~ 14 cm^3

~ 26 Euros

and the front will be (allowing for the screen hole): 
(120 x 60 - 43 x 58) x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 7,059 
+ 3,240

= 10,299 mm^3

~ 10cm^3

~ 19 Euros

==Notes==
None of this can be accomplished without the dimensions of existing phones - if FIC are unable/unwilling to release precise dimensions, a user of a Neo1973 will need to measure their phone and upload the information to [[Neo1973 case schematics]] in the form of a 3D CAD model.

Some users may want combinations of the variants listed - popular/simple options such as Stylus Mount/Different speaker orientation/Extra battery/Extra storage may be combined into one model.

== Design Variant Suggestions ==
Some of these are a copy of requests in [[Wish List - Hardware#Casing]], some are from ideas thrown up in the community mailing list.

Many of these cannot be implemented without some design changes to the phone PCB. As mentioned in [[Expansion Back]]

=== Alternate Case Suggestion Format ===
* 1 Rendered images
** Images & any videos
** [[Image:Neo1973.png]]
* 2 3D model
** Open format, as suggested previously.
** See [[Neo1973 case schematics]] for standard Neo1973 case design
* 3 Etching templates
* 4 Materials
* 5 Processes
* 6 Interest
** who's interested in this design

{{Languages|:Category:Neo1973 alternate cases}}

[[Category:Neo1973 alternate cases| ]]

Hardware:Neo 1973:Alternate Cases

2008-01-17T02:44:08Z

Flerchjj: /* Manufacture */

This page is a repository for alternate case designs for the [[Neo1973]], intended to be designed, built and fitted by the community/the phone's owner. Many specific suggestions can be found in [[Wish List - Hardware#Casing]] and corresponding links.

Each alternate case design suggestion needs some or all of: a description, intended uses, design options, a 3D model in an open format (e.g. [http://en.wikipedia.org/wiki/STL_(file_format) .stl], .blend (Blender), .obj (Wavefront), [http://en.wikipedia.org/wiki/Art_of_Illusion .aoi (Art of Illusion)] ), rendered images of the intended design, materials, components and information regarding interfacing electronically to components within the phone.

== Manufacture ==

There are numerous rapid prototyping companies that will very cheaply make small run components from various polymers, including:

[http://www.absprototypes.net ABS Protytpes] - Invalid website name

[http://ponoko.com Ponoko] - requires EPS files (makes 2D flat cut-outs)

[http://rapidobject.com Rapid Object] - requires STL or VRML (for extra detailed models) files

[http://www.rapidprototyping.co.nz Rapid Prototyping New Zealand]

[http://www.redeyerpm.com/Default.aspx Red Eye RPM] - requires STL files

Other materials may require traditional manufacturing techniques including milling, forging, injection-moulding, either by the user or short-run companies such as:

[http://emachineshop.com/ eMachine Shop] - Requires companies own MS Windows based drawing software

[http://www.msersen.net/msgme.php?p={$pagef}&c={$setcount}/ (4 axis) gantry style cnc router for hire. Click for inquiries]

[http://techshop.ws Techshop]

==Cost Example==
Rapid Object charge from 1.9 Euros per cm^3 of material (photosensitive polymer) used, plus postage. The case for the Neo looks to be about 1.5mm thick, so conservatively, the back of the case will be approximately: 
120 x 60 x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 10,800 
+ 3,240

= 14,040 mm^3

~ 14 cm^3

~ 26 Euros

and the front will be (allowing for the screen hole): 
(120 x 60 - 43 x 58) x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 7,059 
+ 3,240

= 10,299 mm^3

~ 10cm^3

~ 19 Euros

==Notes==
None of this can be accomplished without the dimensions of existing phones - if FIC are unable/unwilling to release precise dimensions, a user of a Neo1973 will need to measure their phone and upload the information to [[Neo1973 case schematics]] in the form of a 3D CAD model.

Some users may want combinations of the variants listed - popular/simple options such as Stylus Mount/Different speaker orientation/Extra battery/Extra storage may be combined into one model.

== Design Variant Suggestions ==
Some of these are a copy of requests in [[Wish List - Hardware#Casing]], some are from ideas thrown up in the community mailing list.

Many of these cannot be implemented without some design changes to the phone PCB. As mentioned in [[Expansion Back]]

=== Alternate Case Suggestion Format ===
* 1 Rendered images
** Images & any videos
** [[Image:Neo1973.png]]
* 2 3D model
** Open format, as suggested previously.
** See [[Neo1973 case schematics]] for standard Neo1973 case design
* 3 Etching templates
* 4 Materials
* 5 Processes
* 6 Interest
** who's interested in this design

{{Languages|:Category:Neo1973 alternate cases}}

[[Category:Neo1973 alternate cases| ]]

Hardware:Neo 1973:Alternate Cases

2008-01-17T02:28:57Z

Flerchjj: /* Manufacture */

This page is a repository for alternate case designs for the [[Neo1973]], intended to be designed, built and fitted by the community/the phone's owner. Many specific suggestions can be found in [[Wish List - Hardware#Casing]] and corresponding links.

Each alternate case design suggestion needs some or all of: a description, intended uses, design options, a 3D model in an open format (e.g. [http://en.wikipedia.org/wiki/STL_(file_format) .stl], .blend (Blender), .obj (Wavefront), [http://en.wikipedia.org/wiki/Art_of_Illusion .aoi (Art of Illusion)] ), rendered images of the intended design, materials, components and information regarding interfacing electronically to components within the phone.

== Manufacture ==

There are numerous rapid prototyping companies that will very cheaply make small run components from various polymers, including:

[http://www.absprototypes.net ABS Protytpes]

[http://ponoko.com Ponoko]

[http://rapidobject.com Rapid Object]

[http://www.rapidprototyping.co.nz Rapid Prototyping New Zealand]

[http://www.redeyerpm.com/Default.aspx Red Eye RPM] - requires STL files

Other materials may require traditional manufacturing techniques including milling, forging, injection-moulding, either by the user or short-run companies such as:

[http://emachineshop.com/ eMachine Shop] - Requires companies own MS Windows based drawing software

[http://www.msersen.net/msgme.php?p={$pagef}&c={$setcount}/ (4 axis) gantry style cnc router for hire. Click for inquiries]

[http://techshop.ws Techshop]

==Cost Example==
Rapid Object charge from 1.9 Euros per cm^3 of material (photosensitive polymer) used, plus postage. The case for the Neo looks to be about 1.5mm thick, so conservatively, the back of the case will be approximately: 
120 x 60 x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 10,800 
+ 3,240

= 14,040 mm^3

~ 14 cm^3

~ 26 Euros

and the front will be (allowing for the screen hole): 
(120 x 60 - 43 x 58) x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 7,059 
+ 3,240

= 10,299 mm^3

~ 10cm^3

~ 19 Euros

==Notes==
None of this can be accomplished without the dimensions of existing phones - if FIC are unable/unwilling to release precise dimensions, a user of a Neo1973 will need to measure their phone and upload the information to [[Neo1973 case schematics]] in the form of a 3D CAD model.

Some users may want combinations of the variants listed - popular/simple options such as Stylus Mount/Different speaker orientation/Extra battery/Extra storage may be combined into one model.

== Design Variant Suggestions ==
Some of these are a copy of requests in [[Wish List - Hardware#Casing]], some are from ideas thrown up in the community mailing list.

Many of these cannot be implemented without some design changes to the phone PCB. As mentioned in [[Expansion Back]]

=== Alternate Case Suggestion Format ===
* 1 Rendered images
** Images & any videos
** [[Image:Neo1973.png]]
* 2 3D model
** Open format, as suggested previously.
** See [[Neo1973 case schematics]] for standard Neo1973 case design
* 3 Etching templates
* 4 Materials
* 5 Processes
* 6 Interest
** who's interested in this design

{{Languages|:Category:Neo1973 alternate cases}}

[[Category:Neo1973 alternate cases| ]]

Hardware:Neo 1973:Alternate Cases

2008-01-17T02:22:14Z

Flerchjj: /* Manufacture */

This page is a repository for alternate case designs for the [[Neo1973]], intended to be designed, built and fitted by the community/the phone's owner. Many specific suggestions can be found in [[Wish List - Hardware#Casing]] and corresponding links.

Each alternate case design suggestion needs some or all of: a description, intended uses, design options, a 3D model in an open format (e.g. [http://en.wikipedia.org/wiki/STL_(file_format) .stl], .blend (Blender), .obj (Wavefront), [http://en.wikipedia.org/wiki/Art_of_Illusion .aoi (Art of Illusion)] ), rendered images of the intended design, materials, components and information regarding interfacing electronically to components within the phone.

== Manufacture ==

There are numerous rapid prototyping companies that will very cheaply make small run components from various polymers, including:

[http://www.absprototypes.net ABS Protytpes]

[http://ponoko.com Ponoko]

[http://rapidobject.com Rapid Object]

[http://www.rapidprototyping.co.nz Rapid Prototyping New Zealand]

[http://www.redeyerpm.com/Default.aspx Red Eye RPM]

Other materials may require traditional manufacturing techniques including milling, forging, injection-moulding, either by the user or short-run companies such as:

[http://emachineshop.com/ eMachine Shop] - Requires companies own MS Windows based drawing software

[http://www.msersen.net/msgme.php?p={$pagef}&c={$setcount}/ (4 axis) gantry style cnc router for hire. Click for inquiries]

[http://techshop.ws Techshop]

==Cost Example==
Rapid Object charge from 1.9 Euros per cm^3 of material (photosensitive polymer) used, plus postage. The case for the Neo looks to be about 1.5mm thick, so conservatively, the back of the case will be approximately: 
120 x 60 x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 10,800 
+ 3,240

= 14,040 mm^3

~ 14 cm^3

~ 26 Euros

and the front will be (allowing for the screen hole): 
(120 x 60 - 43 x 58) x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 7,059 
+ 3,240

= 10,299 mm^3

~ 10cm^3

~ 19 Euros

==Notes==
None of this can be accomplished without the dimensions of existing phones - if FIC are unable/unwilling to release precise dimensions, a user of a Neo1973 will need to measure their phone and upload the information to [[Neo1973 case schematics]] in the form of a 3D CAD model.

Some users may want combinations of the variants listed - popular/simple options such as Stylus Mount/Different speaker orientation/Extra battery/Extra storage may be combined into one model.

== Design Variant Suggestions ==
Some of these are a copy of requests in [[Wish List - Hardware#Casing]], some are from ideas thrown up in the community mailing list.

Many of these cannot be implemented without some design changes to the phone PCB. As mentioned in [[Expansion Back]]

=== Alternate Case Suggestion Format ===
* 1 Rendered images
** Images & any videos
** [[Image:Neo1973.png]]
* 2 3D model
** Open format, as suggested previously.
** See [[Neo1973 case schematics]] for standard Neo1973 case design
* 3 Etching templates
* 4 Materials
* 5 Processes
* 6 Interest
** who's interested in this design

{{Languages|:Category:Neo1973 alternate cases}}

[[Category:Neo1973 alternate cases| ]]

Wish List - Hardware

2008-01-15T20:36:17Z

Flerchjj: /* Wireless data networking */ LTE added by WiMax

This page details hardware features which some would like to go into future phones similar to the [[Neo1973]].

Related pages are:
*[[Wishlist - Hardware - Novel Devices]] - openmoko will run on a large number of devices in the future, some of which may be DVD players, cameras, or convergance devices.
*[[Wishlist:Unlikely]] - Hardware that is unlikely to appear in any OpenMoko device, due to it being impossible to fabricate with near-term technology, or for other reasons.
*[[Wishlist:Accessories]] - Accessories that people would like, that connect easily to the phone - initially primarily for the Neo1973
*[[Wishlist:Expansion]] - add-ons to the phone, maybe involving hardware changes, and software and hardware protocols to implement these.

This page is rather long. Before adding a new idea, please read through this page and the above pages, to make sure your idea has not been suggested before.
==Processor==
===A FPGA===
A FPGA is a general purpose reconfigurable logic device.
See [[Wish List - Hardware:FPGA]] for more details.

===Samsung S3C2443===
*[http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=S3C2443&&ppmi=1427 Samsung S3C2443] Up to 533 MHz, can act as a USB 2.0 device.

==Internal Memory==
===RAM===
128MB Dedicated for open files, running software etc., not for storage, or 256MB at all would be really nice and enough for any future software.

===ROM===
Enough to Hold O/S and a fair number of applications and their settings. Persistent Storage with XIP capability. About 128 MB.

===Storage===
An internal Micro SDHC should be used for users' files and additional software

==Wireless data networking==

===WiMAX support===
[http://en.wikipedia.org/wiki/Wimax WiMAX] is a high-speed data service, similar to wifi, though longer range and newer. Where service is available, this would complement WiFi. Unfortunately, unlike wifi, frequencies vary worldwide, so global usage may be complex. In South Korea, 2.3Ghz is available for WiMAX, known as WiBro. WiMAX Forum sets heart on 2.5 GHz for global use.
----
Two campuses of the University of California have just completed a deal with a WiMAX service provider to lease UC's ITFS/EBS spectrum to provide WiMAX in the SF Bay Area. Bidding was aggressive between Nextwave, Sprint-Nextel, and Clearwire. Other UC campuses have awarded other contracts throughout California to various of the three contenders. The point here is: these three companies are competing aggressively for spectrum in the 2.5-2.7 GHz range, and it's not limited to CA. At a National ITFS Association meeting in 2005, representatives from Intel said they would be ready to release a WiMAX chipset compatible with these frequencies in 2007, for inclusion in laptops. I assume the folks at [[FIC]] know much more about it that I do! Based on these and other clues, I think WiMAX is coming in the 2.5-2.7 GHz band in the near future... I'll be surprised if I do not see some offerings by early 2009.

-[[User:Tzf|Tzf]] 21:54, 24 November 2007 (CET)

===LTE support===
[http://en.wikipedia.org/wiki/3GPP_Long_Term_Evolution Long Term Evolution (LTE)] is a high-speed data service, similar to WiMax, but designed to be more compatible with existing GSM systems. While Sprint & Clearwire are currently testing WiMax deployment in the US, AT&T and Verizon appear to be in preference of LTE.

While the project is ongoing and general in scope, it has set itself some specific goals, many of which are oriented around upgrading UMTS to a so-called fourth generation mobile communications technology, essentially a wireless broadband Internet system with voice and other services built on top.

===Emerging Protocols===
*[http://en.wikipedia.org/wiki/Near_Field_Communication Near Field Communication] has a few centimeter range, useable for keys, ID badges, pairing bluetooth devices and similar uses. Mentioned in newer bluetooth and SD standards. (No products.)
*[http://en.wikipedia.org/wiki/ZigBee ZigBee] is designed for connecting sensors and switches in buildings, with many options including mesh networks and aggressive power saving compared to bluetooth. (Almost no products available.)
*The [http://en.wikipedia.org/wiki/ANT_%28network%29 ANT network] is for connecting worn devices. Similar to ZigBee, but much simpler and maybe lower power. ([http://www.thisisant.com/?section=9 Short list] of products.)

==Camera==

* A camera that can take reasonable quality video and pictures is something many want. Applications vary from simple snapping, to gesture interfaces, video conferencing, barcode reading, buisness card reading, healthcare, servicing, and more.

* Some people can't take cameras into work - a model without the camera, or some way of removing the camera would be useful or leave the camera chip in place and have a removable lens assembly and replacement backcover.
*See [[Hardware:Neo1973:Alternate_Cases:Camera | Alternate Cases:Camera]] for phone casing suggestions.

* See [[Wishlist:Camera]] for a more detailed wishlist.

==Display==
===Multitouch screen===

''Main article: [[Wishlist:Spell_weaving|Spell weaving]]''

See also [http://pogue.blogs.nytimes.com/2007/03/27/the-multi-touch-screen/ this page] containing a link to a video demonstration.

A history of multitouch implementations is [http://billbuxton.com/multitouchOverview.html here] ([http://google.com/search?q=cache:billbuxton.com/multitouchOverview.html google cache version])

*Use examples: [http://www.youtube.com/watch?v=UcKqyn-gUbY&mode=related&search= Multi-touch interface (from Adobe TED)], [http://www.youtube.com/watch?v=1ftJhDBZqss&mode=related&search= Multi Touch (new touchscreen technology)]

===Bigger and better screen===
2.8" widescreen (like in [http://etencorp.com E-ten] PDA/smartphones), or 3.5" widescreen (like in [http://www.expansys.ie/d.aspx?i=134944 Fujitsu Siemens LOOX N560]).

262k or 16.7M colurs for displaying images and especially videos.

OLED for better contrast, more rich colours, and less energy consumption.

Maybe the [http://www.sharpsme.com/Page.aspx/europe/en/part/LS037V7DW01/ LS037V7DW01] by Sharp could be a solution. It has nearly the same specs as the currently used, but 3,7" -- [[User:Wedge | Wedge]]

===Distance sensing touchscreen===
{{Main|Hardware:NearlyTouchScreen}}
TouchKo's (now Wacom Company Ltd.) spatial capacitive "touchscreen", can sense fingers at a small distance, so you do not get your display greasy, and can unlike some touchscreens, be operated with gloves.

===<s>Video acceleration</s>===
Hardware acceleration for video playback and 2D/3D accelleration will be present in [[Neo1973 GTA02]].

===EPD===
Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, lightweight, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].

Pro: laserprinter like quality, glossy, very stable image, easy on the eyes. Electronics are similar to TFT. Very low power consumption.

Con: Black and grey only (like a newspaper, but glossy), although there were already color prototypes in 2005. low framerate (5fps). Can reflect light (like paper), backlight is impossible.

===Transreflective===
It would be nice to have (the option of) a transreflective display, which while being less bright, is readable without needing to power the backlight. Then again, it depends on how much power the backlight uses compared to everything else...

==="Slightly" Larger Screen===
43mm x 57mm (2.8inch diagonal) is tiny. A 53mm x 71mm (3.5 inch diagonal) like on the TD035STEE1 would be a nice improvement. A widescreen format at about 53mm x 82.5mm instead of the 3:4 aspect ratio would be even cooler (if one could be found).

===Second Display===
A 32x32 OLED display possibly on the back for camera framing or on an edge so it can be viewed like a pager.
This could be used to display any number of alerts (from any installed software) the alerts could have a dynamic prioritisation which means during the work day a message from the boss has high priority but lower at home (could be GPS/Time controlled?) multiple alerts shrink the icons to a 3x3 grid higher priority messages get more space.

===Micro Projector===
[http://www.engadget.com/media/2006/02/digismartphone2.jpg Like the one shown here], new cellphones are now coming out with a small, low power projector. This can be used to show movies from your cell phone with 0.5m high image on a while wall for example...

==Input devices==

===No Dependence on Stylus===
The Neo's basic functionality should be completely usable without a stylus, Like the iPhone but with stylus use for precision work.

===A laser projection keyboard===
Similar to [http://www.thinkgeek.com/computing/input/8193/ this], except the device would be integrated into the phone itself. Setting the Neo up on a stand on a flat surface (perhaps a stand could be built into the back of the Neo itself, or into a case) would turn the Neo into a micro-laptop. There may be several issues with the inclusion of this technology, including patents, the space required to project the laser grids, and the power consumption. If possible, however, it would make text input a breeze.

===Just a few more Buttons===

2 buttons more, 3 buttons total, mounted sideways would be enough. You could use them for play/pause and loudness controll while the phone remains in your pocket (display locked, ...), reading mails, rss, ebooks,... without wasting display space and so on.

With 5 buttons in total you could possibly emulate a keyboard (2^5 = 32 combinations) for those who know how to play a flute. Useable onehanded, not wasting display space and faster than t9. (It's not faster than T9 - I've used this system with the microwriter agenda --[[User:Speedevil|Speedevil]] 00:00, 2 July 2007 (CEST)) Hopefully this is not patented already.

===D-Pad and Buttons===
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)

Game buttons would be best on both sides of the screen. The larger the buttons, the better. 2x 4 buttons in up-down-left-right configuration + some extra buttons separately a bit lower on the device would be good for many for emulation games.

Here is a concept drawing of a possible neo1973 gaming version:
(This has a 4-way direction pad, 8 way may be better for gaming)
 
[[Image:Neogame90.jpg]]
 
Shoulder buttons would be a great addition, too. It would be interesting if there was a total 4 of them, one for every corner. It would make the phone very flexible for rotating and 2 to 6 players playing on one device.
 
:''Note'' : The [http://en.wikipedia.org/wiki/Tapwave_Zodiac Tapwave Zodiac] Palm PDA / Game console hybrid had a similar setup - with an analog stick on the left (also used for quick selection using a radial main menu when working as a PDA), 4 buttons on the right (also configurable for shortcuts when using the device as PDA), and 2 shoulder buttons. Also it had and still has an enthusiastic scene of homebrew development (almost any console emulator for PalmOS can also take advantage of the additional buttons and graphic power of the device). If we also take into account the success encountered by the [http://en.wikipedia.org/wiki/GP32 GP32] in the past and the [http://en.wikipedia.org/wiki/GP2X GP2X] currently on the homebrew scene, it's not unreasonable to plan a future OpenMoko device with both a SmartPhone/PDA functionnality ''and'' hand-held console targeting homebrew development.

===Thumb keyboard or keyboard attachment accessory===
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).
*Cheap clippable miniusb keyboard
*One of the layouts proposed in [[Hardware:Keyboards]]
* What about virtual keyboard? [[http://www.extremetech.com/article2/0,3973,539778,00.asp Keyboard]]

===Analogue Controllers===

====Trackball====
A trackball would provide an efficient mouse-like interface in a very compact package. As exemplified in the newer Blackberry® models.
Maybe instead an optical sensor as are used in mice could be used so that the whole phone can be moved over a surface just like a mouse. (It could function as a Bluetooth mouse for other devices like laptop computers: see [[Bluetooth_Support#Acting_as_HID_device]]. Adding one other two-axis analogue input (possibly just the screen) would make the Neo usable as a TrackPoint or scroll-and-tilt mouse.) The same sensor might be usable as a barcode reader.

====Analog Joystick====
A joystick, or [http://www.extremetech.com/article2/0,1697,1772689,00.asp Rollermouse]-like device would provide additional control, compared with touchscreen only.
*A standard [http://en.wikipedia.org/wiki/Pointing_stick pointing stick (ie. TrackPoint)] might serve well. As a fairly standard part, might they be quite inexpensive?

====Dual analogues====
Dual analogue controllers (one trackball or joystick above, one below the screen, most likely) might even be feasible. That might be overkill since the accelerometers or touchscreen can be used to provide a second analogue input. But it would be nice to have four axes of analogue control without having to tilt the screen away from you or partly cover it with your hand.

===TV/radio receiver===
[[Digital Television]], [[Digital Radio]] or even normal analogue TV/radio is widely available in the world, though unfortunately in various different forms. In markets where one standard is widespread, and hardware is suitable, it would be a great extension of the phone to a general entertainment device for when you're away from home. Multi standard devices would be ideal, but may not be small, low-power, or cheap.
A good start would be an FM tuner, since it's one of the most widely used formats of radio broadcasting in the world.

Here's a selection of chips, though it's not clear if the drivers are open source. http://www.sigmatel.com/products/portable/wireless/fmtuner.aspx#fragment-14
http://www.st.com/stonline/products/families/automotive/am_fm_tuners.htm

===Accelerometer===
This enables the phone to sense which direction 'down' is, and to sense any movements the phone makes.

See [[Accelerometer Fundamentals]] for more information on accelerometers as they may be used in phones.

In some cases integrated gyroscopes may also be needed. A [[#Digital compass]] can even be of more use since it gives absolute rotation so slow rotations could also be measured. A 3D compass would be nicest, but a simple 2D compass already is a helpful addition to the accelerometers.

*[[Wishlist:3D Viewport|3D Viewport]]
*[[Wishlist:Computer Mouse|Computer Mouse]]
*[[Wishlist:Determine Position|Determine Position]]
*[[Wishlist:Dynamic Screen Orientation|Dynamic Screen Orientation]]
*Change media player playlist when jogging vs walking.
*Attempt to use to stabilise any future camera.

This feature is scheduled for inclusion in the phase 2 Neo1973, GTA02.

===Side-Mounted Touch Strip===
Add a "touch strip" sensor onto the side of the phone which can be used to scroll. By having it on the side you can use your thumb to scroll comfortably while holding the phone one-handed. An 8-element capacitive sensor would work wonderfully and be easy to fab using either a Quantum QT411 (http://www.qprox.com/products/qslide_qt411.php) or Analog Devices AD7143 (http://www.analog.com/en/prod/0,2877,AD7143,00.html) controller. The Analog Devices chip seems better suited due to it's smaller allowable element size.
*With the AD7143 you can have an 8-element (128-position) 25mm long strip - Perfect!.
*With a few OLED screens beneath the strip it could be used as dynamic configurable buttons/alerts eg. zoom/flash/shutter with a camera application and SMS/Email/Voicemail alerts in standby

===Heart Rate Compatibility===

An RF interface to receive data from popular heart rate straps (Polar, Garmin, Sigma, Suunto, etc.). This would go along well with the existing GPS functionality and possible future Accelerometer functionality to make for a full-blown workout tool.

Software can be written to track heart rate along a running, cycling, skiing, swimming loop, to monitor max and min heart rate, to match heart rate data to GPS coordinates and print map data w/ relevant data.

===Digital compass===
A digital compass is useful for orienting maps to the terrain and other location/direction/orientation based applications (... is 300 meter that way) when the user is standing still (regardless of GPS reception) and for following a bearing when GPS reception is poor or speed is low. Also could be used to make the accelerometer data more exact.

Very small [[I2C]] sensors like [http://www.ssec.honeywell.com/magnetic/hmc6352.html Honeywell's HMC6352 2-Axis Digital Integrated Compass] (6.5 x 6.5 x 1.5 mm) are very appropriate for this.

*[[Wishlist:Auto Align Map]]

See [[Wishlist - Hardware: Digital compass]] for more information

===Thermometer===
An electronic thermometer might become handy for some users.

There are very small [[I2C]] devices available, that could easily integrate to the existing bus. For example [http://focus.ti.com/docs/prod/folders/print/tmp100.html this one from ti].
(Could just be cheap and use the thermometer from the battery, thats how they did it in the nokia 5140's). Also is integrated in a barometer/altimeter like the SMD500 mentioned in [[Wish List - Hardware - Atmospheric]].
::But if you carry it in you pocket it is unlikely to show the correct air temperature anyway. [[User:AudriusA|AudriusA]] 17:12, 12 January 2008 (CET)

===Barometer and Variometer (Altimeter)===

A Barometer measures air pressure. This can be used to give weather information, and also as a variometer, to sense relative altitude. Variometers are commonly used in flying microlight and ultralight aircraft, to get accurate relative altitude.

These are also common on high end GPS units. This is a great feature for walkers as you can tell how far you have got on any ascent/decent.

See [[Wish List - Hardware - Atmospheric]] for more information.

===Finger print sensor===
A fingerprint sensor gives easy and fast access to the phone, could lock the touchscreen etc. An example of this device can be found at [http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_BrowseCatalog-Start?CategoryName=cpu_VAIONotebookComputers_UX_Series&Dept=computers Sony UX17].

Most fingerprint sensors in the embedded market include a navigation mode, where they work similar to either a touch-stick or touch-pad of a laptop.

===Barcode Scanner===
*less cpu intensive and more reliable than camera+ocr
*though, bluetooth-enabled readers are already available.

===Light Sensor===
Ability to sense ambient light, and act accordingly. i.e if it's 3am and LightValue<.1 then Ring Quietly.

===Wheel===
A navigation wheel like on a sony/ericsson 810i would be nice.

===Proximity Sensor===
Switch off backlight when you place the phone to your ear. Prevent accidental activation of speakerphone or other sounds when the phone is near the ear (prevent hearing damage). Possibly switch the speakerphone on or off automatically depending on if the phone is by your head or not.

=== Make ''all'' unlocking of phone, password protected===

When my (current non-neophone) phone is in my pocket and I have it locked, it sometimes accidentally unlocks itself since only two keystrokes in the correct order are necessary to unlock it. When it's unlocked and still in my pocket it sometimes calls someone without my knowledge. All phones I've seen today have a press-just-one-button bypass to answer an incoming call even when the phone is locked. I suggest making the locking mechanism let the user configure it so that the user has to enter a password even for answering incoming calls. The likeliness of the phone accidentally runbbing against my car keys, hitting a ten character long password, unlocking the phone without my knowledge and consent is low enough even for us most unlucky users.

==Expansion==
===Positioning of Buttons, Connections and ports===

Ideally any cable ports such as charging, USB, audio, docking should not get in the way of your hand or fingers when holding it in it's normal orientation. For the sake of SDIO cards an external SD slot should be on the top edge. IR for remote control software and ease of inter-device communication should be on the corner so that it is facing away from you for both orientations. Buttons obviously are positioned for finger control. An example of how '''not''' to do this would be the HTC Universal

===Storage===

====MMC/SD/SDIO slot (rather than?) miniSD or microSD====
*Cheaper, more durable cards in a widely accepted format.
*Much much larger storage capacity, [http://blog.scifi.com/tech/archives/2007/08/23/toshiba_unleash_1.html even 32GB]
*Cards are harder to lose
*Wider selection of accessories, including SDIO accessories.
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)
*[http://en.wikipedia.org/wiki/Secure_Digital_card#SDHC SDHC] compatible. It seems to already have the right hardware for it - see [[Neo1973_Hardware#microSD-Card]].

====Two SD slots====
*Micro SDHC for /home partition. Keep like current design underneath SIM card
*Hot swappable externally accessible normal size SDHC/SDIO slot

=== Internal Communication Bus ===
*A standard and/or documented internal communication bus of some sort could simplify adding new hardware modules.
*Serial USB or I2C connector internal to case towards the top
*Several digital I/O pins that operate at TTL levels
*A few analogue I/O pins attached to a A/D converter
*Documentation of Debug board connector could provide some of this functionality.

===Local Communication===

====USB====
* 5V Powered, to avoid having to carry around a hub for when you want to occasionally plug in a memory stick. Many powered hubs will not recognize a totally unpowered host. Provide a maximum current to drive a basic USB keyboard/memory stick/mouse/webcam/astrowebcam. This could be done by adding a small cheap power converter like the [http://www.national.com/pf/LM/LM2753.html LM2753]
* USB 2.0
* Standard type A socket for quick & easy insertion of memory sticks etc.
* OTG, to be able connect usb keyboard like [http://www.mobile-review.com/pda/review/cherry-kb-en.shtml Cherry G84-4321 SUNRG]
* Bootable USB device emulation: the possibility to boot any computer on a bootable flagged partition of the transflash.
* Protection against incorrectly wired USB ports: some USB ports are wired incorrectly; if the +5V and GND are swapped, the device would get -5V when it's expecting +5V, which could burn some chips. A reverse-biased diode between +5V and GND, D+ and GND, D- and GND, and (if used) ID and GND, with a low enough forward voltage drop (to limite the negative voltages to what the chips can withstand), would protect the device by tripping the port's short circuit protection.

====Wireless USB support====
[http://en.wikipedia.org/wiki/Wireless_USB Wireless USB] is the wireless version of USB offering data-rates up to 480 Mbit/s over short distances (<3 meter). Chipsets suitable for a phone are likely to take some time to be available.

====SIR/FIR transceiver (Serial Infrared) / IR remote control====
*An infrared transceiver is cheap, small, and useful for sync with many laptops and mobile phones.
*Replace/emulate all IR-based remote controls used for your tv, vcr, etc on your neo cell phone.
** replaces multiple 'dumb' devices with a single intelligent device (your neo) that you will probably carry with you at all times anyway.
**Command sets should be retrieved from a database or learned from other less intelligent remote control devices with macros.
**reduces clutter, particularly in the living room.
**inceases the neo's practical status as an 'always-have' device.

Other uses.
*Detecting reflections from inside of a caddy, and switching from active mode.
*FIR would be a nice option, as it's some 40 times faster than SIR.

===Other===

====Video Out====
*Through a docking port
**S-Video/Composite Out
**DVI Out
**HDMI Out
**Display Port

==Output devices==

===LED===
*The Neo1973 GTA02 will have LEDs of some sort behind at least one button. [http://lists.openmoko.org/pipermail/community/2007-July/008458.html]
*A blinking LED would be a cheap, low power way to inform the user of new SMS/Email....
**An alternative to this would be for one small part of the LCD to be separately backlit.
**This requires the CPU and LCD to be somewhat active, to keep the LCD refreshed, but gives much more information.
**A Small OLED Screen could be used and display much more information than a LED with minimal power usage.

*For example a multicolor LED which pulses yellow for GSM/GPRS transmit, blue for Bluetooth/Wifi, green to indicate non-urgent information - missed call etc, red to indicate battery low or other urgent notices.

**The LED and button ideas could be combined: illuminated buttons.
**It must be possible to completely disable the LED to save power or other personal preferences.

=== Flashlight ===
For finding keys, or any other application. May also optionally pulse in time with ring, to make phone more visible.
This is really well done in Nokia 5500.

-I second this one. The most used feature in my Nokia 5140 after the calling and sms features is the flashlight. It's just one simple LED, but powerful enough to see with if it's really dark. If it ain't dark, you won't need the light anyway. :)

Also, Who hasn't lost their keys and opened up their cell phone to use as a flashlight?

=== FM transmitter ===
Small FM transmitter to output to car, and other nearby radios.

Fix the biggest flaw in the iPod before Apple does!

=== Infrared Transmitter w/ universal remote software ===
Infrared LED on top of device with universal remote software so you can control televisions, DVDs etc.
[http://www.novii.tv/ Here] is an example of universal remote software.
===HAC Compliance===
[http://quux.wiki.zoho.com/WhereAreHACphones.html Here] is some summary/discussion of how hearing aid compliance rules work in the US. Specifically it would be nice to see the phone include a [http://www.hearingresearch.org/Dr.Ross/telecoil_and_telephones.htm telecoil], which allows the phone to connect wirelessly to many standard hearing aids.

==Mobile Communication options==

===Generic Access Network / Unlicensed Mobile Access===
This technology requires cooperation from the cellular provider, but [http://en.wikipedia.org/wiki/Unlicensed_Mobile_Access UMA/GAN] is already offered by T-Mobile in the United States, and perhaps others in other countries. Allowing the user to roam from GSM to wifi, this technology can save the end user a significant amount of money, and also allow the user to deploy coverage where there was none before. There are only a few UMA capable phones currently, but it would be great if this could be made to work on a phase 2 type OpenMoko device.

Note that this features requires more advanced access to the GSM modem.
Special messages needs to be exchanged with the network.

===Faster/better mobile connectivity.===
[http://en.wikipedia.org/wiki/Gsm GSM]/[http://en.wikipedia.org/wiki/GPRS GPRS] is at best slow. An incremental improvement would be a radio with [http://en.wikipedia.org/wiki/EDGE EDGE ] support. EDGE is an evolved GSM standard and, like GPRS, it operates on the same frequency as voice. This means a quad-band EDGE radio will have near-complete worldwide coverage.

[http://en.wikipedia.org/wiki/UMTS UMTS] - which is widespread in Europe and being deployed in the US, [http://en.wikipedia.org/wiki/HSDPA HSDPA] (asia) and any other mobile standards would be nice for faster data connectivity and coverage.
It is unlikely that all of these will be supported initially, but it is a goal. These faster standards operate in different frequencies from GSM/GPRS/EDGE. Which frequency exactly will depend on the carrier and country. For UMTS in the US, AT&T uses 850/1900 MHz but T-Mobile will use 2100/1700 MHz for example.

Until that goal is reached, it is likely that some phones will be brought out for various specific markets - Europe, Asia, US.

===Ability to use multiple SIMs/networks===
* External SIM sockets are widely available in China, a dual external socket would be a very good solution.
* [http://www.fonefunshop.co.uk/dualsim/digital.htm Dual SIM card kit] - two SIMs are trimmed and combined, software supportwould be needed, and both can't be used at once...
* Some networks support multiple numbers on one SIM. Unfortunately this won't allow split networks.
* A second/dual GSM module would allow full use of both sims at all times.
* As a hack, [http://wiki.openmoko.org/wiki/Wish_List#Bluetooth_powered_Multi-SIM_support use another mobile via BT].
** As many as three SIM slots would be genuinely useful, especially for a 3G phone - some 3G data tariffs are only available on data-only SIMs. A user could quite reasonably have one SIM for data, once SIM for his personal voice calls, and a third SIM for his business number.

===PMR446/FRS Radio===
* Include a PMR/FRS Radio.
* A two-way walkie talkie lets you use the phone to communicate with friends without requiring a GSM connection (crowded networks at festivals, at locations with no GSM coverage).

===[[DECT]]===
* Include a [[DECT]] GAP/CAT-iq transceiver so you can use your home and/or office PSTN line
** Ability to use Alcatel phonebook stuff (like provided by the eventphone.de phone equipment) would be very nice too

===[[SIP phone]]===
Make stripped down (and thus cheaper) version of the Neo1973 phone for use as a SIP phone. Remove GPS, GSM, accelerometers, stylus.

Addition of an centimeters-precise location system [http://en.wikipedia.org/wiki/Real_Time_Location_Systems RTLS] would be nice, as it will allow highly sensible indoor context detection. Imagine putting the phone next to your mirror (where you shave daily) and watch it automatically switch to news radio channel. Or put it next to your bed and see it automatically switch to "sleeping" mode, when only calls from predefined numbers are accepted.

=='''Casing'''==
See also: [[Alternate Neo1973 case designs]] for a list of cases being considered for design/manufacture by the community.

=== [[Hardware:Neo1973:Alternate_Cases:Expansion_Module_Casing | Expansion Module Casing]] ===
Longer case (150-160mm+) with space in the top to put expansion modules, including test & hobby hardware. Would require use of a standard internal power & communications bus. Could be left empty with blank cover or house cameras, solar panels, a crank powered charger, special transmitters/recievers, or anything else imaginable.

[http://www.likeasecret.com/Neo1973/Neo1973-Exp.mov Neo1973 Expansion Module Quicktime rendering] 
[[Image:Neo1973-Exp.png]]

=== Expansion Back Casing ===
Replacement backs with additional features ranging from solar power, larger batteries, extra hardware, ...

===[[Hardware:Neo1973:Alternate_Cases:Expansion_Front_Casing|Expansion Front Casing]]===
Replacement fronts with e.g. extra buttons.

=== Space efficient Lanyard ===
The hole at the bottom of the phone takes a lot of space. A [http://en.wikipedia.org/wiki/Kensington_Security_Slot Kensington Security Slot] could be used instead.

=== Rugged version ===
We need something you can drop from 4 feet in to a puddle of dirty water on construction site. Sunlight readable display, maybe aluminium case. The big ugly pseudo military version.

=== Transparent ===
Make a transparent, see-through casing. Why do we need a closed casing for open hardware and open software? Show the world it is a truly Free/Open source phone.

That makes sense to me. I second that idea!

=== Blank ===
Even though the transparent case would work too, I would like to see a blank case of pure black or white so people could have the option of air-brushing,painting or even drawing on the case.

==Misc==
===Galileo/GLONASS/GPS receiver===
*A multi-standard satellite positioning module would be nice eventually, it does not seem to be near-term due to chipset availability problems. Galileo is the to be launched (2011) European positioning system. GLONASS is the already existing Russian one.

===X10 RF Remote===
Many PC-based media centers are being equipped with an RF (433 MHz) / X10-based remote control. The [http://en.wikipedia.org/wiki/X10_(industry_standard) X10] protocol also facilitates home automation to control lamps, switches, etc.
The advantages of using RF for control instead of Infra-red this that it also works when furniture, walls, or doors are blocking the path between RF remote and the equipment or device. [http://www.lirc.org/ Lirc] supports X10-based RF remotes (but expects having an USB RF receiver attached to the media center).

===RFID tag/RFID Reader===
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]
*An enable-able tag would be of use - for example being able to use the phone to open doors, or cars. Unfortunately, it's moderately hard to do secure programmable tags that are compatible with existing systems, for obvious reasons.
* Say you have RFID tags on your personal belongings: cellphone, keys... Neo could be programmed to remember the last recorded GPS location before it lost contact with the respective RFIDs. It'd be trivial to check where you left your cellphone, get directions from a map...or beep when the phone gets out of RFID range.

*I agree with this idea, a great idea and you have to do it (Jackcday)

===NFC chip===
*A Near Field Communication chip, with this chip it will be possible to pay with your phone (like a credit card)in the near future, see [http://www.nokia.com/A4305081 Nokia]for details
*NXP is a chip fabricator which provides NFC chips [http://nxp.com NXP] direct link>> www.nxp.com/#/pip/cb=[type=product,path=/53420/53424]|pip=[pfp=53424][0] their chips also support the above RFID reading

===Less weight===
* Work on the weight of the Neo1973 and following devices. At the present time the Neo1973 is just a moderate / normal business or multimedia phone. The ordinary "user" may want something lighter. Take a look at the following table, that's the Neo1973 compared with other common bussiness or multimedia phones.
{|border="1"
| Neo1973 || Fujitsu-Siemens LOOX N560 || E-Ten Glofiish X500+ || Sony Ericsson P990i || iPhone || Nokia E65
|-
| 184 g || 160 g || 146 g || 150 g || 135 g || 115 g
|-
|}

===Make it smaller===
* To stay within physical matters: Maybe the Neo1973 is also just a normal business/multimedia phone when looking at the size. It would be great the shrink it a bit. Especially the thickness of 18.5 mm could be worked on!

===Standard 3.5mm headphone jack===
The Neo1973 uses a 4-conductor 2.5mm jack for stereo headphones and a microphone. A 2.5mm jack is the most common for headsets.

There is an emerging convention used in the Nokia N800 and some other devices. A 4-conductor 3.5mm jack that can use a microphone with special headsets, but can also be used with off-the-shelf 3.5mm stereo headphones. Adapters to 2.5mm are of course available and this 3.5mm jack is much more robust.

Neglecting space limitations, multiple sockets - 2.5mm and 3.5mm would be nice. Probably not practical in a phone. Other expanded plugs might allow remote controls.

Other uses might be better met using bluetooth, or USB audio.

===Laser Pointer===
Include a built in laser pointer. Everything is better with lasers.

===Completely free hardware===
Consider selling one device with absolutely no non-free components in it, even if that means dropping the GSM support. I believe having one such device available would be good, because then it could be recommended by organizations like the FSF which typically never recommends anything if it has even a little non-free code in it.

=== Consider economy / inexpensive / less featured edition ===
Some people want less features, because they do not need them. Leaving out some features either lets the phone get smaller or possibly enhances battery live.

One big suggestion in this area is a b/w lower res display instead of the big color display.

=== Inductive Charger ===

It would be nice if it was possible to charge the phone without having to connect a cable. I'd like to have a simple docking station with an inductive charger like the type that's used for electric toothbrushes [http://home.howstuffworks.com/question292.htm ]. The charger itself could get its power from a standard wall-wart power supply, or it could be USB/Firewire powered.

=== Solarpanel/dynamo Charger===

It would be very nice to be able to charge the phone outside of the electric grid (for example on hikes and boating trips). A combined solarpanel and muscle empowered (rotational etc.) charger would do the trick nicely.

'''some mobile Solarpanels'''

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=off01011&k_id=1400&hot=0 Off-Grid Systems Sunbag L]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=off01001&k_id=1400&hot=0 Off-Grid Systems Sunbag S]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=sv_01011&k_id=1400&hot=0 Silva Solar I]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=sv_01012&k_id=1400&hot=0 Silva Solar II]

[http://www.globetrotter.de/de/shop/detail.php?mod_nr=sol01011&k_id=1400&hot=0 Solarc e-Go Professional]

[http://www.heise.de/mobil/suche/ergebnis?rm=result;q=solar;url=/mobil/artikel/74142/;words=solar Solarc e-Go *]

[http://www.heise.de/newsticker/suche/ergebnis?rm=result;words=Solar%20solar;q=solar;url=/newsticker/meldung/91536/ Solar JKT]

- I think a dynamo charger ("share charger", rotational, ...) would be more practical as a peripheral, connected through the USB-interface using the same principle cellphones now charge when connected to an USB-port. You could very easily hack this together. [http://www.metacafe.com/watch/449950/hack_a_flashlight_to_power_your/ flashligh recharge hack] Random thought; Why not create some merchandise toys with a small lithium battery which charge through centrifugal force allowing to recharge the phone with a small "general" connector.

[http://www.heise.de/mobil/artikel/61368/0 Article about aome mobile power-sources]

=== Plastic Solar/Back side on the Neo===

Sollar cells from Plastic, on the reverse side of the Neo 1973
modified and intergreated in the batery backcover/flap,
like an energy source when the display is in standby mode.
Thats can be use also as alternate charge method's and also helps in emergency.

==Related Hardware==
See [[Related Hardware]]

[[Category:Hardware ideas| ]]
[[Category:User]]

CAD models

2007-12-27T16:09:32Z

Flerchjj: broke up big text blurb into paragraphs

Hardware:Neo 1973:Alternate Cases

2007-12-27T16:04:32Z

Flerchjj:

This page is a repository for alternate case designs for the [[Neo1973]], intended to be designed, built and fitted by the community/the phone's owner. Many specific suggestions can be found in [[Wish List - Hardware#Casing]] and corresponding links.

Each alternate case design suggestion needs some or all of: a description, intended uses, design options, a 3D model in an open format (e.g. [http://en.wikipedia.org/wiki/STL_(file_format) .stl], .blend (Blender), .obj (Wavefront), [http://en.wikipedia.org/wiki/Art_of_Illusion .aoi (Art of Illusion)] ), rendered images of the intended design, materials, components and information regarding interfacing electronically to components within the phone.

== Manufacture ==

There are numerous rapid prototyping companies that will very cheaply make small run components from various polymers, including:

[http://www.absprototypes.net ABS Protytpes]

[http://ponoko.com Ponoko]

[http://rapidobject.com Rapid Object]

[http://www.rapidprototyping.co.nz Rapid Prototyping New Zealand]

[http://www.redeyerpm.com/Default.aspx Red Eye RPM]

Other materials may require traditional manufacturing techniques including milling, forging, injection-moulding, either by the user or short-run companies such as:

[http://emachineshop.com/ eMachine Shop]

[http://www.msersen.net/msgme.php?p={$pagef}&c={$setcount}/ (4 axis) gantry style cnc router for hire. Click for inquiries]

[http://techshop.ws Techshop]

==Cost Example==
Rapid Object charge from 1.9 Euros per cm^3 of material (photosensitive polymer) used, plus postage. The case for the Neo looks to be about 1.5mm thick, so conservatively, the back of the case will be approximately: 
120 x 60 x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 10,800 
+ 3,240

= 14,040 mm^3

~ 14 cm^3

~ 26 Euros

and the front will be (allowing for the screen hole): 
(120 x 60 - 43 x 58) x 1.5 
+ 120 x 9 x 1.5 x 2 (2 sides) 
= 7,059 
+ 3,240

= 10,299 mm^3

~ 10cm^3

~ 19 Euros

==Notes==
None of this can be accomplished without the dimensions of existing phones - if FIC are unable/unwilling to release precise dimensions, a user of a Neo1973 will need to measure their phone and upload the information to [[Neo1973 case schematics]] in the form of a 3D CAD model.

Some users may want combinations of the variants listed - popular/simple options such as Stylus Mount/Different speaker orientation/Extra battery/Extra storage may be combined into one model.

== Design Variant Suggestions ==
Some of these are a copy of requests in [[Wish List - Hardware#Casing]], some are from ideas thrown up in the community mailing list.

Many of these cannot be implemented without some design changes to the phone PCB. As mentioned in [[Expansion Back]]

=== Alternate Case Suggestion Format ===
* 1 Rendered images
** Images & any videos
** [[Image:Neo1973.png]]
* 2 3D model
** Open format, as suggested previously.
** See [[Neo1973 case schematics]] for standard Neo1973 case design
* 3 Etching templates
* 4 Materials
* 5 Processes
* 6 Interest
** who's interested in this design

{{Languages|:Category:Neo1973 alternate cases}}

[[Category:Neo1973 alternate cases| ]]