Openmoko - User contributions [en]

Debian

2008-12-28T01:53:18Z

Jidanni: swap links

{{Languages|Debian}}

Debian is used on many other embedded devices. Using Debian on the FreeRunner gives access to the Huge army of software packaged in the Debian repositories, already compiled for the arm processors. Moreover, one can build one's own things without having to learn the OpenEmbedded way. For example compiling natively is a snap with Debian, just apt-get gcc&libc-dev.

In the early days, one had to install [[Manual Debian|Debian manually]]. Now there is an installer script. The "official" instructions on how to install [http://wiki.debian.org/DebianOnFreeRunner Debian on FreeRunner] or [http://wiki.debian.org/DebianOnNeo1973 Debian on Neo1973] are hosted on Debian's wiki. This page is about post-install configuration and FreeRunner specific tips. For support or bug reporting please read the section [[Debian#Support|Support]].

= Configuring a base system =
== Password ==

The default root password is blank. You should change that as soon as possible
<pre>
# passwd
</pre>

== Suspend ==

Press the power button or run 'apm -s' to suspend.
To change the time for the display to darken/turn off edit in

<code>/usr/share/python-support/fso-frameworkd/framework/subsystems/odeviced/idlenotifier.py</code>

the section

<code>
self.timeouts = { \
"idle": 10,
"idle_dim": 20,
"idle_prelock": 12,
"lock": 2,
"suspend": 20, \
</code>

idle_dim is the time in seconds to dim the display (which adds up to the idle time), idle_prelock is the time to turn it off. After that execute

<code>mv /var/lib/python-support/python2.5/framework/subsystems/odeviced/idlenotifier.pyc /var/lib/python-support/python2.5/framework/subsystems/odeviced/idlenotifier.pyc.old</code>

You can turn off Suspend completely by commenting out the entire section "Idleness Brightness Handling" in

<code>/etc/freesmartphone/oevents/rules.yaml</code>

== Time ==

The default time zone is UTC. Reconfigure it by running
<pre>
# dpkg-reconfigure tzdata
</pre>
To set the clock manually do something like
<pre>
# date -s 00:33
</pre>
If you have a network connection, do something like
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
If you want to synchronize the internal clock with GPS time you can use a script like
<pre>
#!/usr/bin/env python
#
# Set the gps time
# Be sure your GPS is active before to launch this script

import dbus
import subprocess
import time

proxy = dbus.SystemBus().get_object('org.freesmartphone.frameworkd', '/org/freedesktop/Gypsy') # bus name, object name
interface = dbus.Interface(proxy, 'org.freedesktop.Gypsy.Time');
subprocess.call(['date',time.strftime( '%m%d%H%M%Y.%S', time.localtime(interface.GetTime()))])
</pre>

== Wifi ==
=== Using GUI ===

If you don't want to mess up with configuration files and is looking for an easy gui for wireless configuration, then wifi-radar or wicd is what you are looking for.

<pre>apt-get install wifi-radar
wifi-radar</pre>
or
<pre>apt-get install wicd
wicd-client -n</pre>

If you are looking for more, read on...

=== Using /etc/network/interfaces (simple mode) ===

Make sure the following packages are installed:
<pre>apt-get install wireless-tools wpasupplicant dhcp3-client</pre>

Assuming your wireless router uses WPA security and DHCP,
edit <code>/etc/network/interfaces</code> to include a section like this:
<pre>
auto eth0
iface eth0 inet dhcp
wpa-driver wext
wpa-ssid "MyWirelessName"
wpa-psk "MyWirelessPassword"
</pre>
Where, of course, you're using the name of your wireless network and it's password
instead of ''MyWirelessName'' and ''MyWirelessPassword''.

You can test by running
<pre>
# ifup eth0
</pre>
You can determine your IP address by running
<pre>
# ifconfig eth0
</pre>
Issues:
* only works if in presence of wireless network on boot, or when manually running <code>ifup eth0</code>
* booting away from wireless network is slower because waits for DHCP to time out
* does not reestablish connection when leaving wireless area and then returning
* does not support multiple wireless networks or open hotspots that you may travel between

Once wpa_supplicant has begun managing your wifi interface, you should type "wpa_action eth0 stop" instead of "ifdown eth0".

===Using wpa-supplicant (roaming mode)===

To configure WPA to roam between wireless networks, you will need to create a new configuration file:

<pre>/etc/wpa_supplicant/wpa_supplicant.conf</pre>

a template for this file (and more documentation) is available in:

<pre>/usr/share/doc/wpasupplicant/examples/wpa-roam.conf</pre>

You'll need to add networks to this file. Examples:

* WEP:
<pre>
network={
ssid="MySSID"
key_mgmt=NONE
wep_key0="abcdefghijklm"
# wep_key0=6162636465 # <- no quotes, so hex number
wep_tx_keyidx=0
id_str="MySSID"
}
</pre>
* No key:
<pre>
network={
ssid="SomeNetwork"
key_mgmt=NONE
}
</pre>
* WPA:
<pre>
network={
ssid="Example WPA Network"
psk="mysecretpassphrase"
id_str="home"
}
</pre>

Next, you'll need to edit /etc/network/interfaces. This lets you configure your wireless networks to use dhcp, or other appropriate TCP/IP settings:
<pre>
auto eth0
iface eth0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

# MySSID comes from an id_str above.
iface MySSID inet dhcp

# default is what's used if there is no id_str setting.
# so the 'SomeNetwork' network will use DHCP.
iface default inet dhcp

iface home inet static
# static interface settings, or whatever...
</pre>

Finally, if you want attempts to access the internet to default to eth0 (and not usb0), then comment out this line under usb0 adapter configuration:

<pre>
gateway 192.168.0.200
</pre>

* Roaming from network to network is not automatic. Instead, you need to manually run "wpa_action eth0 stop; ifup eth0" to switch networks

For some reason, I had to reboot for the id_str settings to take effect. However, you should now be able to use "ifup eth0" to associate with the access point and "wpa_action eth0 stop" to down the wifi adapter.

{{todo|Which of the issues that single network configurations suffer from are addressed by WPA roaming mode? Would ifplugd / guessnet help, or just make things more complicated?}}

=== Further reading ===

To use all the possibilities of <code>wpasupplicant</code> like roaming and automatic connection to different networks,
you should read <code>/usr/share/doc/wpasupplicant/README.Debian.gz</code>

== [[Bluetooth]] ==

The FreeRunner uses the standard Linux bluez stack, installed with
<pre>
# apt-get install bluez-utils
</pre>
There is also a module missing from /etc/modules, which is critical to getting your device recognized. (kudos to johnsu01 on irc.freenode.net:#openmoko-debian for the find)
<pre>
# echo ohci-hcd >> /etc/modules
</pre>
The first time you try this, you can also
<pre>
# modprobe ohci-hcd
</pre>
The only atypical part of using bluetooth on the FreeRunner is turning it on, which can be done with
<pre>
# mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/Device/PowerControl/Bluetooth SetPower 1
</pre>
Then the device should be visible using
<pre>
# hcitool dev
</pre>
{{todo|Then what to do next?}}

== Packages manager ==
You can install <tt>[http://packages.debian.org/search?keywords=dselect dselect]</tt>(~2.2MB) or <tt>[http://packages.debian.org/search?keywords=aptitude aptitude]</tt>(~12MB) to visually inspect the available debian packages using the desktop's console. 
Also the gtk-based package-manager <tt>[http://packages.debian.org/search?keywords=synaptic synaptic]</tt>(~15.7MB) is working
after installing <tt>[http://packages.debian.org/search?keywords=lsb-release lsb-release]</tt> and <tt>[http://packages.debian.org/search?keywords=hicolor-icon-theme hicolor-icon-theme]</tt>, but it is very slow. 
Finally, on constrained systems, just issue the command:
<pre>grep -e Package: -e Description /var/lib/dpkg/available|more</pre>

== Xglamo acceleration ==
By default debian uses fbdev, but we can use Xglamo to get better performance:
<pre>apt-get install xserver-xglamo</pre>
after that edit /etc/X11/xorg.conf and change the line
<pre>Driver "fbdev"</pre>
to:
<pre>Driver "Xglamo"</pre>
and if you want to run xserver as normal user:
<pre>chmod u+s /usr/bin/Xglamo</pre>
You may also want to force the X server to 96 dpi to have the same fonts as with fbdev. Add "-dpi 96" to the X_OPTIONS variable in '''/etc/init.d/nodm''':<pre>X_OPTIONS="vt4 -nolisten tcp -dpi 96"</pre>
with that you:
*can use xrandr
*don't have the pointer callibration bug with the rotated mode
*have better performances

Using xglamo you must remember that:
*You can't use on xorg.conf the "Option Rotate" to rotate the screen
*You can't use the tslib patch to simulate right click

== Running X as normal user ==
1. Create a new user
<pre>
# useradd -m -G audio,dialout,floppy,video,staff username
# passwd username
</pre>

2. Edit /etc/init.d/nodm and change USER=root to USER=username in it. Then to make sure changes are not lost on upgrade, run
<pre>
dpkg-divert --add /etc/init.d/nodm
</pre>
This will make new versions of /etc/init.d/nodm be written to /etc/init.d/nodm.distrib

3. Edit <code>/etc/X11/Xwrapper.config</code> and change <code>allowed_users=console</code> to <code>allowed_users=anybody</code> (Or use <code>dpkg-reconfigure x11-common</code>)

4. Copy /root/.xsession into ~username/

5. Note that, if you ran zhone as root first, you may have to change ownership or remove /tmp/zhone.log, as a normal user is not able to write to a file owned by root.

== Sound ==
Make sure to put your user in the audio group ("adduser <username> audio").

If there is no error but no sound, try these state files:
[[Talk:Manual_Debian#Sound]]

== Kernel ==

=== Debian way ===
When Debian is installed, the kernel is provided by the package <code>linux-image-2.6.24-openmoko-gta02</code>. This package can be installed only in POSIX compliant filesystems, so it can not be used if your boot partition is a vfat one. Your kernel will be keep updated like the other packages of the system. You must to use this way if you are unsure and you need an (almost) stable system.

=== Openmoko way ===
Otherwise you can choose to manual install an OM kernel. But only do this if you know what you are doing.
At the moment there is a little problem in the question which kernel to use. Hopefully it will be solved in the near future.

The original openmoko kernel works fine inclusive suspending and supports different really nice usb gadgets (not all working at the moment). :) 
download stable: http://downloads.openmoko.org/releases/Om2008.9/ 
download testing: http://downloads.openmoko.org/daily/

The new FSO4 kernel works fine and suspend/resume is also possible. But this kernel still has no loadable usb gadget modules (10-Nov-2008). :/ 
download testing: http://downloads.freesmartphone.org/fso-testing/images/ 
download unstable: http://downloads.freesmartphone.org/fso-unstable/images/
# Download a recent'' kernel'' and ''rootfs'' (tar.gz) from one of the above mentioned sources. It's your decision if you want suspend or usb gadget modules at the moment.
# Backup your running kernel like <code>mv /boot/uImage.bin /boot/uImage.bin.old</code>, then copy the downloaded uImage file to the freerunner as <tt>/boot/uImage.bin</tt>.
# Backup your actual modules like <code>mv /lib/modules/2.6.24 /lib/modules/2.6.24.old</code>, then extract the downloaded rootfs tar.gz to a temporary directory and copy <tt>lib/modules/2.6.24</tt> from the temp directory to <tt>/lib/modules/2.6.24</tt> on the FreeRunner.
# Do a <code>chown -R root.root /lib/modules/2.6.24</code> because the owner from the tar.gz is something else (for me).
# Run a <code>depmod -a</code>.
# This step is only needed for the OM kernel but it doesn't harm the FSO kernel setup. Add "g_ether" Module to /etc/modules like <code>echo g_ether >> /etc/modules</code>. I read in an email, that the module "ohci-hcd" is also needed for some bluetooth functions, but i don't know this for real. I inserted it to my modules file to be on the safe side.
# Reboot and hope everything works as expected. :)

= Desktop enviroments =
== Matchbox with fbpanel ==
It is not really a Desktop enviroment, but using fbpanel with Matchbox you can have a fast, lightweight, gtk2 desktop panel.
[[Image:Debian_fbpanel_zhone.png|right|thumb|300px|Debian with fbpanel, matchbox-window-manager and Zhone running]]
<ol><li>Install fbpanel:
<pre>sudo apt-get install fbpanel</pre></li>
<li>Customize the X startup process:
<pre>~/.xsession</pre>
<pre>
#!/bin/sh
export GTK_MODULES=libgtkstylus.so
zhone &
xsetroot -solid black
matchbox-keyboard-toggle &
matchbox-window-manager -use_titlebar yes &
# -use_titlebar yes to minimize & toggle between apps
# fbpanel's taskbar does not work with matchbox-window-manager
#~/bin/auxlaunch &
while true;
do
fbpanel;
sleep 1;
done;
</pre></li>

<li>Read http://fbpanel.sourceforge.net/docs.html#config
<pre>~/.fbpanel/default</pre>
<pre>
mkdir ~/.fbpanel
cp /etc/fbpanel/default ~/.fbpanel/default
nano ~/.fbpanel/default
</pre>
Remove section with 'taskbar' plugin - it's useless with matchbox-window-manager. You may add plugin 'cpu'
<pre>Plugin {
type = cpu
}</pre>
Also, plugin 'genmon' is useful:
<pre>Plugin {
type = genmon
config {
Command = echo -e $(grep "MemFree" /proc/meminfo | awk '{printf "%0.2f", $2 / 1024}') "|"\
$(cat /proc/loadavg | awk '{print $3}') "|" $(apm | awk '{print $5}')
PollingTime = 60
TextSize = small
TextColor = darkblue
}
}</pre>
After 'killall fbpanel' it will show: free mem in megabytes | loadavg | battery % left.</li>
<li>Default theme is ugly. You can change it and / or make font's bigger:
<pre>~/.gtkrc-2.0</pre>
<pre>sudo apt-cache search gtk2-engines
sudo apt-get install gtk2-engines gtk-theme-switch
DISPLAY=:0 gtk-theme-switch2</pre>
Now choose your theme, font and save it. To see changes do 'killall fbpanel'.</li></ol>

== XFCE ==
The debian installation script installs by default the matchbox window manager. It doesn't feature a desktop environment. '''xfce''' is a small and lightweight desktop environment and so is quite fast for the FreeRunner.

<pre>apt-get install xfce4</pre>

Edit your .xsession to launch xfce4 at X startup :

<pre>#!/bin/sh
xfce4-session</pre>

Edit section [Failsafe Session] of /etc/xdg/xfce4-session/xfce4-session.rc (or ~/.config/xfce4-session/xfce4-session.rc) to handle the auto-started apps. For example:
<pre>[Failsafe Session]
Count=3
Client0_Command=xfce4-panel
Client0_PerScreen=False
Client1_Command=xfdesktop
Client1_PerScreen=False
Client2_Command=zhone
Client2_PerScreen=True</pre>
Start XFCE !

<pre>/etc/init.d/nodm restart</pre>

The desktop takes a while to start but once up was snappy as can be expected.
I've not yet looked at the reason for the seemingly too slow start for the desktop.

zhone is available from the "Office" menu in xfce.
The matchbox keyboard is available in "Accessories".

If you want to display the screen on the long side (ie rotated, 4:3 aspect), add the following to the /etc/X11/xorg.conf in both the Device and InputDevice sections :

<pre>Option "Rotate" "CCW"</pre>

and then (re)start xfce.

If you want to be able to shutdown/restart the device, add the following line to ''/etc/sudoers'' (don't forget to replace ''username'' with your actual username):
<pre>username localhost = NOPASSWD: /usr/sbin/xfsm-shutdown-helper</pre>

=== Using matchbox-window-manager with XFCE ===

XFCE's window manager is poorly configured for use with the FreeRunner. Fortunately, matchbox's window manager is compatible with xfce. To use the matchbox window manager, modify ~/.xsession as follows:

<pre>#!/bin/sh
exec matchbox-window-manager -use_titlebar no -use_cursor no &
xfce4-session</pre>

== LXDE ==

I you want a really nice desktop enviroment but you think XFCE is too fat, you can try to install [http://en.wikipedia.org/wiki/LXDE LXDE]. It give to you the GTK comfort, but use only a fraction of the ram needed by XFCE.

To install it:
<pre>apt-get install lxde</pre>

to launch it create a <code>/etc/init.d/lxde</code> script in the same way descripted for xfce4, replacing <code>startxfce4</code> accorence with <code>startlxde</code>.

= Additional Software =
== Web Browser ==
[http://lists.openmoko.org/nabble.html#nabble-td781547 Arne Anka suggested] trying the light-weight webkit-based [http://en.wikipedia.org/wiki/Midori_(browser) midori] browser:
<pre>apt-get install midori</pre>

Another light-weight browser is [http://en.wikipedia.org/wiki/Dillo Dillo]. It can be easily installed with:
<pre>apt-get install dillo</pre>

If you think the previous options are quite slow on Freerunner try Links2.
<pre>apt-get install links2</pre>

Run as:
<pre>xlinks2</pre>

== GPS ==
Openmoko Freerunner has integrated a good AGPS chip that can be used to know in every moment the phone position.
The most known free applications to use gps with graphical maps are:

*{{main|TangoGPS}}
*{{main|Navit}} (Attention: Navit is not yet present on Debian repository)

== E-Book reader ==

To read an E-Book you have diffent possibilities:

* [[FBReader]] a good reader that can display txt, fb2, html and various other formats.
* [[Epdfview]] a simple and lightweight PDF viewer, it can be installed from Debian repository.
* [http://en.wikipedia.org/wiki/Evince Evince] the official Gnome viewer, it can display pdf, djvu, cbz, and other formats.
There is also an hack to convert drm protected adobe ebooks to .cbz files readable as mentioned on the mailing list.

= Miscellaneous =
== Making the cursor invisible ==

=== Using matchbox ===

Matchbox has an option, <code>use_cursor</code>, that can be used to control whether to show the cursor.
For the default setup, edit <code>/usr/bin/zhone-session</code> and change the matchbox command to
matchbox-window-manager -use_titlebar no -use_cursor no

=== Using unclutter ===

Unclutter is a program that hides the cursor after a period of inactivity. To use unclutter, install it
#apt-get install unclutter
and choose ''Yes'' to the question <code>Start unclutter automatically?</code>. To change settings edit
<code>/etc/default/unclutter</code>.

=== Changing the cursor ===
To make the cursor invisible create a file called empty.cursor with this content:
<pre>
#define empty.cursor_width 16
#define empty.cursor_height 16
static unsigned char empty.cursor_bits[] = {
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
</pre>
Now you can execute:
xsetroot -cursor empty.cursor empty.cursor
and the cursor will be invisible. To make this permanent you have to invent something ;) It must be executed after zhone has finished starting up.

== Running X applications on your desktop in nested X server ==
Sometimes it is helpful to have a big screen, keyboard and mouse. You can run X applications in a nested X server window.
On your desktop install the nested X server application Xephyr (better that Xnest)
apt-get install xserver-xephyr
Run a nested X server as display :1
Xephyr :1 -ac -br -screen 480x640 -reset -terminate &
Now you are able to run apps on your Neo which will display on your desktop PC. Make sure to set the display, for example if "mydesktop" is your desktop hostname
DISPLAY=mydesktop:1 xfce4-session &

== Simulating right click with stylus ==
=== With fbdev driver from xserver-xorg ===
To have the right click with stylus an easy way is to use the Sebastian Ohl's tslib patch: you can find it [http://www.ohli.de/download/xserver-xorg-input-tslib_0.0.5-1+fso1_armel.deb here] until it will not enter in the official Debian package.

You can install it with:
<pre>
wget http://www.ohli.de/download/xserver-xorg-input-tslib_0.0.5-1+fso1_armel.deb
dpkg --install xserver-xorg-input-tslib
</pre>

'''Warning''': this patch is external to Debian repository and is not (yet) supported by Debian comunity.

In this way, to get a right click you can simply tap and hold the stylus and after a while a right click will occurs.

'''Warning''': tslib patch is incompatible with <code>xserver-xglamo</code>. Use <code>libgtkstylus</code> instead (see below).
=== With Xglamo driver from xserver-xglamo ===
# <pre>apt-get install libgtkstylus</pre>
# Insert this line at the beginning of '''~/.xsession''':<pre>export GTK_MODULES=libgtkstylus.so</pre>

== Using the mouse and keyboard from your desktop on the OM device ==
=== Method 1: xsession export (works with a linux host) ===
If you are running Linux (or a similar xorg capable operating system) on your Desktop, you can export your xsession to the openmoko device and use your mouse and keyboard on the Neo screen. A little program called x2x makes it even possible to do this simultaneously on the fly. When activated you just move your mouse to the edge of your monitor and then the mouse cursor continues on the screen of your openmoko device. If you select a window on the OM, the input of your keyboard is automatically entered in that window. You can even use the clipboard to copy data from tour desktop to OM and in the reverse direction.

Configure your desktop computer to export your xsession:
On your desktop (with root permissions):
Make sure that sshd is installed and in /etc/ssh/sshd_config you have set
X11Forwarding yes

In K/Ubuntu sshd is in the package openssh-server.

On your OM device install x2x (with root permissions)
apt-get install xauth x2x
Now open a new X terminal on your desktop computer. You MUST be the same user that is running the xsession on your desktop (i.e. do not su to root or another user in your x terminal!). Use the same username that is running an xsession on your OM device. Assuming that you have a usb networking connection to OM (with standard configuration) on the user prompt of your desktop type:
user@desktop:~$ ssh -X openmoko@192.168.0.202 "/usr/bin/x2x -east -to :0.0"
Hit return and enter your password. The xterm window will be unresponsive after that, but keep it open until you disconnect your OM device.

Now move your mouse cursor across the right edge of your monitor. It should enter the screen of your OM device from the left. Of course you can also use -west, -north or -south, depending on your preference where you place your OM.

If computer says:
sh: /usr/X11R6/bin/xauth: No such file or directory
X11 connection rejected because of wrong authentication.
x2x - error: can not open display localhost:11.0

It means you haven't installed xauth on your OM. So on your OM (with root permissions)
apt-get install xauth

=== Method 2: synergy (works with a windows/linux host) ===
With this method you can have the following functionality:
* Mouse moves from screen edge to the next screen
* Keyboard types on the focused window
* Clipboard is transferred as well
* Connect as many computers and screens you wish
* Connect windows computers too

All devices/computers in question should be able to install [http://synergy2.sourceforge.net synergy].
Windows computers can use an installer exe.
Debian devices have a package ready to be used.
<pre>
apt-get install synergy quicksynergy
</pre>
quick synergy will appear in your XFCE programs menu (Accessories->QuickSynergy).
Run it, switch to the "Use" tab, enter the IP address of the computer with the mouse and keyboard you wish to use, and press Execute.

In the windows host, (or linux) run the synergy after installation,
and configure it to share its keyboard and mouse(server),
configuration is fairly simple, you add all the hostnames of the devices/computers that ever would be joined to the "screens" list, and create 2 links for each connection.

If your desktop's hostname is homepc, and the device's is debian_gta02, and i place the device to the left of the desktop, the links would look like this:
<pre>
homepc is right of debian_gta02
debian_gta02 is left of homepc
</pre>
Now move back to the main screen, and press Start.

That should be it, in windows you should have an icon with a yellow lightning in it when synergy is connected and working.
Synergy supports connection of more then one screen so one could set up a full lab with only one keyboard and mouse :)

= See also=
== Support ==

To have more information about Debian go to [http://www.debian.org Debian homepage].

If you have some problems, you can find support in [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland smartphone mailing list]. Report your discovered bugs to this list but remember to put [mailto:nomeata@debian.org Joachim Breitner] in CC.

If you'd like to help the packaging activities, you can join the [http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint fso mainteiner list].

Consider a swap partition [http://lists.openmoko.org/pipermail/community/2008-September/031106.html]
[http://lists.openmoko.org/pipermail/community/2008-October/032964.html].

== Known Issues ==

'''apt-get segmentation fault''' Whenever you get a segmentation fault while using apt-get or aptitude, clean the database so it will rebuild it
rm /var/cache/apt/*.bin

Manual Debian

2008-12-28T01:51:35Z

Jidanni: /* Prepare SD card */swap links

{{Languages|Debian}}

''Contents of this page is probably old and superceded by this new pae : [[Debian]].''

[[Image:Debian.png|thumb|480px|''Debian on neo1973'']]
This page is to explain how to run Debian armel port on Openmoko devices. You can do this from scratch, or download a prebuilt file system.
The former will take some time, perhaps 2 hours, depending on your internet connection

= Prebuilt Filesystem =

Download and extract to an ext2 formatted filesystem on your SD card:

wget http://rabenfrost.net/debian/debian-armel-xfce.tar.bz2

Note that the above is just a bit too big to fit on a 512MB SD card. A smaller image will soon be provided.

Access via SSH is much the same as under other images using [[USB Networking]], with the user accounts below:

* root password: openmoko
* First user and password: openmoko

Note: If you upgrade your your debian and your touchscreen doesn't work any more, you most likely have to adjust /etc/udev/rules.d/50-udev.rules by applying the settings described later in this document for /etc/udev/udev.rules

== (Optional) Install Known Good Kernel ==

This kernel was build by Marcel_M and has some important patches in it such as removed sd debug symbols.

wget http://rabenfrost.net/celtune/uImage-2.6.24+svnr4194-r4165-r3-neo1973.bin
./dfu-util -d 0x1457:0x5119 -a kernel -R -D ./uImage-2.6.24+svnr4194-r4165-r3-neo1973.bin

This kernel doesn't work for gta02, but the kernel from Om 2008.9 works good.
http://downloads.openmoko.org/releases/Om2008.9/Om2008.9-gta02-20080916.uImage.bin

== (Optional) Recompiling Kernel to Add Drivers ==
(Based on http://lists.openmoko.org/pipermail/support/2008-August/001240.html)

Steps to build the kernel standalone with the "moredrivers" config (to get additional drivers, such as the usb tether drivers that were moved out as kernel modules, compiled directly into the kernel).

~ - git clone git://git.openmoko.org/git/kernel.git linux-2.6
~ - cd linux-2.6
~ - git checkout origin/stable
~ - edit ./build to point to your compiler path
~ - cp defconfig-2.6.24 .config
~ - ./build

That gets you a uImage.bin you can DFU or copy into your SD Card filesystem.

== Configure booting from SD/SDHC ==

Do as proposed here: [[Booting_from_SD]]

Note that these instructions are in need a rewrite.

= Build your own armel filesystem =

== Prepare SD card ==

ssh to your neo and format your sd card appropriately. I'm using an 8GB SDHC card here.

:''NOTE: On the Freerunner one also will need a vfat or ext2 (only vfat worked for me with the stock u-boot for the freerunner) partition on which to place the kernel to boot off. See the [[Booting_from_SD]] If you have not done so already.''

fdisk /dev/mmcblk0
We will now create a 8 mb partition for our kernel and another one for the rootfs which will take up all the
remaining space.
Command (m for help): d
Selected partition 1
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-983, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (18-983, default 18):
Using default value 18
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):
Using default value 983
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.

Consider a swap partition [http://lists.openmoko.org/pipermail/community/2008-September/031106.html]
[http://lists.openmoko.org/pipermail/community/2008-October/032964.html]
mkfs.vfat /dev/mmcblk0p1

mkfs.ext2 /dev/mmcblk0p2
mount /dev/mmcblk0p2 /media/card

== debootstrap on the neo ==

you can download and debootstrap natively on the neo by downloading cdebootstrap-static.

wget http://ftp.de.debian.org/debian/pool/main/c/cdebootstrap/cdebootstrap-static_0.5.3_armel.deb
ar -x cdebootstrap-static_0.5.3_armel.deb data.tar.gz
tar -xz -C / -f data.tar.gz
rm data.tar.gz cdebootstrap-static_0.5.3_armel.deb
wget http://ftp.de.debian.org/debian/pool/main/d/debian-archive-keyring/debian-archive-keyring_2008.04.16+nmu1_all.deb
ar -x debian-archive-keyring_2008.04.16+nmu1_all.deb data.tar.gz
tar -xz -C / -f data.tar.gz
cdebootstrap-static --variant=minbase --include=ifupdown,udev,procps,netbase,nano,module-init-tools,wget,openssh-server lenny /media/card/ http://ftp.de.debian.org/debian/

== Complete debootstrap Process ==

execute the following commands (just copypaste everything below)
echo "neo1973-debian" > /media/card/etc/hostname
echo -e "auto lo\n\
iface lo inet loopback\n\
auto usb0\n\
iface usb0 inet static\n\
address 192.168.0.202\n\
netmask 255.255.255.0\n\
network 192.168.0.0\n\
gateway 192.168.0.200\n\
up echo nameserver 192.168.0.200 >/etc/resolv.conf" > /media/card/etc/network/interfaces
echo -e "rootfs / ext2 defaults,errors=remount-ro,noatime 0 1\n\
proc /proc proc defaults 0 0\n\
tmpfs /etc/network/run tmpfs defaults,noatime 0 0\n\
tmpfs /tmp tmpfs defaults,noatime 0 0\n\
tmpfs /var/lock tmpfs defaults,noatime 0 0\n\
tmpfs /var/run tmpfs defaults,noatime 0 0\n\
tmpfs /var/tmp tmpfs defaults,noatime 0 0" > /media/card/etc/fstab
echo 'root:openmoko' | chroot /media/card/ chpasswd
== Get X Running ==
Now reboot and start Debian. Login with ssh and start configuring xorg:

apt-get install xorg

configure /etc/X11/xorg.conf so that it looks like this:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
EndSection
Section "Device"
Identifier "Configured Video Device"
Driver "fbdev"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Configured Mouse"
EndSection
Start X in the first vt:
startx -- vt1

== Get touchscreen working ==
Install the tslib driver:

apt-get install xserver-xorg-input-tslib

and edit the InputDevice section in your xorg.conf

Section "InputDevice"
Identifier "Configured Mouse"
Driver "tslib"
Option "CorePointer"
Option "TslibDevice" "/dev/input/event1"
Option "Protocol" "Auto"
EndSection
calibrate your touchscreen
for gta01:
echo -67 36365 -2733100 -48253 -310 45219816 65536 > /etc/pointercal

calibration for the gta02
echo -67 38667 -4954632 -51172 121 46965312 65536 > /etc/pointercal

Note from Tkrahn:

First the above calibration for gta02 worked fine for me, but after a
apt-get update && apt-get upgrade the pointer didn't follow the stylo
anymore. I needed to overwrite /etc/udev/rules.d/50-udev.rules with
/etc/udev/udev.rules.dpkg-bak and a restart of the X server to get it
moving again. But then the pointer was very far off from the tip of
the stylo. Obviously the mode how the calculation of the position worked
has changed with the upgrade. I changed the calibration empirically.
The following /etc/pointercal parameters worked for me:

0 80000 -8000000 -80500 0 74500000 65536

(On GATA02v5 after the upgrade!)

same goes for gta01. these parameters work at least better then nothing - plz help improving these by doing your own tests:

0 80000 -8000000 -78000 0 72000000 65536

Start X and enjoy!
startx -- vt1

== Install GDM and xfce4 ==

apt-get install gdm xfce4 xvkbd

Configure gdm so xkvbd will allow you to put in your username and password. simply add this to the end of /etc/gdm/Init/Default before exit 0 so that the three last lines look like this:

fi
sleep 20 && /usr/bin/xvkbd -xdm -compact -geometry 480x210+0+0 &
exit 0

Simply click on the focus button of xvkbd and then on the input box of GDM to input your user name and password there. On each boot gdm should start automatically now.

If you like you can also download a correctly sized Debian wallpaper I generated from the SVG source for 480x640:

wget <nowiki>http://rabenfrost.net/debian/debian-blueish-wallpaper-480x640.png</nowiki> -O /usr/share/images/desktop-base/desktop-background

== Clean Up ==
apt-get clean

== Load Additional Kernel Modules ==

These are for sound, bluetooth and USB. Use the modules archive that fits to your kernel.

wget http://rabenfrost.net/celtune/modules-2.6.24+svnr4194-r4165-r3-neo1973.tgz
tar -xf modules-2.6.24+svnr4194-r4165-r3-neo1973.tgz -C /
depmod -a
echo -e "hci_usb\n\
hidp\n\
ohci-hcd\n\
rfcomm\n\
snd-mixer-oss\n\
snd-pcm-oss\n\
snd-soc-neo1973-wm8753" > /etc/modules

Note: On the FreeRunner, the sound module (on the last line) is called snd-soc-neo1973-gta02-wm8753
[[Image:Sonata.png|480px|''Sonata on neo1973'']]
== Enable Sound ==

Now we turn our Debian into a jukebox!

apt-get install alsa-base
wget http://rabenfrost.net/celtune/alsa_state_files-working.tar.gz
tar -xf alsa_state_files-working.tar.gz -C /etc
alsactl -f /etc/alsa_state_files-working/stereoout.state restore
addgroup openmoko audio

I currently use mpd+sonata - let me know if you know another nice lightweight gtk player. Unfortunately RhythmBox is way too much for the Neo to handle - the MP3 playing stops after 20secs.

== Enable Modem ==

Here comes the phone functionality - just add this line into the "serial devices" section in your /etc/udev/rules.d/50-udev.rules

# serial devices
KERNEL=="s3c2410_serial[0-9]", NAME="ttySAC%n"

= Miscellaneous =

== Chroot installation ==

If you just want to run random debian programs without completely booting to debian you can use the following minimal steps:

on desktop:

sudo debootstrap --arch armel --foreign sid sid
sudo tar cjf sid.tar.bz2 sid
nc -w3 -lp1234 < sid-arm.tar.bz2

on neo:

cd /media/card
nc 192.168.0.200 1234 | tar -x -j -f -
mount -t none -o bind /dev /media/card/sid/dev
mount -t none -o bind /proc /media/card/sid/proc
mount -t none -o bind /sys /media/card/sid/sys
mount -t none -o bind /tmp /media/card/sid/tmp
chroot /media/card/sid /deboostrap/deboostrap --second-stage
cp /etc/resolv.conf /media/card/sid
chroot /media/card/sid apt-get update
chroot /media/card/sid apt-get install mplayer
chroot /media/card/sid mplayer http://relay.slayradio.org:8000/

== Using Xglamo on the FreeRunner ==

Copy /usr/bin/Xglamo (and /usr/bin/Xfbdev) to /usr/bin in Debian from FSO/ASU/2007.2/2008.8.

Add this to your .bashrc (to tell tslib to use the correct input device):
export TSLIB_TSDEVICE=/dev/input/event1

The X server binaries are linked against version 1 of tslib, for some reason Debian calls its version 0, even though it actually is version 1. Symlink the library to the alternative name by running (as root):
ln -s /usr/lib/libts-0.0.so.0 /usr/lib/libts-1.0.so.0

We also need to change the symlink for the X server to either Xfbdev or Xglamo (this should better be handled by update-alternatives!):
cd /usr/bin && mv X X.orig && ln -s Xfbdev X
(replace Xfbdev by Xglamo if you want to use that, Xglamo is faster, but rotation still does not work correctly as of 2008-08-12).

== Rotating screen to landscape ==

add the following to the /etc/X11/xorg.conf in both the Device and InputDevice sections to get landscape mode

Option "Rotate" "CCW"

== Hiding the cursor ==

To make the cursor invisible create a file called empty.cursor with this content:

#define empty.cursor_width 16
#define empty.cursor_height 16
static unsigned char empty.cursor_bits[] = {
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

add
xsetroot -cursor empty.cursor empty.cursor

to your ~/.xinitrc

=Official Debian Port=

An official Debian port based on the FSO image is being created. First information can be found at http://wiki.debian.org/DebianOnFreeRunner. Early adopters are welcome.

[[Category:Debian]]

GTA02 sysfs

2008-12-28T01:25:37Z

Jidanni: what are the new paths?

'''NOTE: These only apply to Linux kernel 2.6.24, 2.6.28 has different paths''' (which are what?)

==GTA02 Kernel sysfs highlights==
sysfs is a filesystem that is mounted on /sys which contains various fake "files" that are actually filled by a variety of drivers and other kernel subsystems. You can often also write stuff into these "files" using

echo 1 > /sys/blah...

to change settings and behaviours of the kernel and drivers dynamically. (When doing this, take care you have a space before the redirection operator > or the shell will do something completely different with your command.)
However[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!

===USB Host / Device===
====/sys/devices/platform/neo1973-pm-host.0/hostmode====
* Defaults to 0, GTA02 USB hardware is configured to be a device, no power is generated for USB, charging is enabled and host 15K pulldowns are removed from D+ and D-
* Set to 1 to put the GTA02 USB hardware into host mode, so it starts to generate 5V power, disables charging from USB, and applies 15K pulldowns to USB D+ and D-
====/sys/devices/platform/s3c2410-ohci/usb_mode====
* Defaults to "device", it means the USB peripheral in the CPU is logically configured for device mode
* Set to "host" to logically configure the peripheral to act like a host for other USB devices to be plugged into it

Normally you set these two guys at the same time for the same mode, but there is a trick possible to select logical host mode but leave the power arrangements as if it was in device mode and apply external power. You need to [[Specialized USB cables|externally add]] 15K pulldowns on D+ and D- if you do this, because we did not enable them the normal way. With this, you can have a USB device attached to GTA02, and use external power and charge the battery at the same time.

===GSM Subsystem===
====/sys/devices/platform/neo1973-pm-gsm.0/power_on====
* Defaults to "0", GSM power OFF
* Set to "1" to enable power to GSM logic
====/sys/devices/platform/neo1973-pm-gsm.0/reset====
* Defaults to "0", no reset
* Set to "1" briefly after power applied to reset GSM logic
====/sys/devices/platform/neo1973-pm-gsm.0/download====
* Defaults to "0", no insane clicking sound
* Set to "1" to drive yourself crazy and enable serial access to GSM chips down headphone socket / once a second loud clicks / chirps

===Resume Reason===
====/sys/devices/platform/neo1973-resume.0/resume_reason====
If you cat this you get a list of possible resume sources in text with one or more * at the left of the active source that woke us. You need a recent U-Boot to get the * set.

===MEMCONFIG===
====/sys/devices/platform/neo1973-memconfig.0/BANKCON0 .. 7====
For extreme meddlers (I salute you), these let you control the wait states and other characteristics of the memory regions of the FreeRunner. Information and warnings about how to use these are here:

http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=fd25f90517322fc6c07bfb8d34752d3cb41cb4b6

===FIQ and HDQ===
====/sys/devices/platform/sc32440_fiq.0/fiq/count====
FIQ is used to provide precision interrupt service in order to implement the HDQ protocol used to the battery couloumb counter. This shows how many FIQ interrupts have been run since the kernel started. It's turned off unless it is required.
====/sys/devices/platform/gta02-hdq.0/hdq/dump====
If you cat this, you will see the raw contents of HDQ device register space. This is the bq27000 couloumb counter in our case.
====/sys/devices/platform/gta02-hdq.0/hdq/write====
This allows you to write to raw HDQ registers, using "<decimal register index> <decimal value>"

===power_supply battery information===
Most of these are coming from the coulomb counter over HDQ dynamically, but the bq27000 does not update a lot of its registers any more often than once per 4 seconds. Therefore a lot of this info can be a bit stale or averaged over that period.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/uevent====
All informations about battery.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/type====
Just says "Battery"
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/status====
This will summarize what goes on generally with the battery
* "Not Charging" - there's a charger in, but right now it isn't charging us. Normal if you are fully charged and still powered.
* "Charging" - there's a charger in and it is charging the battery
* "Discharging" - we are running on battery
* "Full" - not normally given as a result (Not Charging used instead)
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/voltage_now====
Battery voltage in uV, averaged. Obviously this depends on load and place on discharge curve, etc.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/current_now====
Current being drawn from battery (+ve) or pushed into battery during charging (-ve) in uA
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/charge_full====
Coulomb Counter's estimate of the capacity of the battery measured in uA/h. It roughly means that if full, for one hour it could supply current at this rate. I saw 1197913 reported on mine, so it estimates it can provide 1.2A for an hour.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/temp====
This is the battery temperature reported by the Coulomb Counter chip that is part of the physical battery. It is in Celcius * 10, so 251 means 25.1 degrees.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/technology====
"Li-ion"
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/present====
* "0" the battery is absent, or not one with a Coulomb Counter
* "1" the smart battery is present
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/time_to_empty_now====
At current rate of discharge, estimate of how long we can run for. If battery is not discharging, it won't make an estimate and will return a magic value "3932100" meaning "no estimate". The coulomb counter averages the load and adjusts this value slowly to be its estimate of when we will blow chunks.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/time_to_full_now====
This estimates how long until we are fully charged, at current rate of charging, in seconds. If we are not charging, it gives the magic value "3932100" meaning "no estimate".
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/capacity====
This is the remaining capacity of charge in the battery in percent. This is probably the most useful figure here.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/online====
* "0" no charger is present
* "1" A powered charger is present

===PMU info===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/chgmode====
* "enabled" means the charger is powered and willing to charge, although if you're full it might not be right now
* "disabled" means there was no power or not enough power supplied to charge

Looks like it may also report "fast" here. [[User:OlivierBerger|OlivierBerger]] 07:47, 25 July 2008 (UTC)

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/charger_type====
Shows the detected charger type followed by the mode it is running in. So "charger 500mA mode 100mA" would be the case for non-enumerated USB connection, "charger 500mA mode 500mA" for after enumeration (or "host/500mA usb mode 500mA" as here [[User:OlivierBerger|OlivierBerger]]).

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous====
This is added to allow the PMU to be told to take more current than the default rules allow. Use it only if you know your charger source can handle it. For example

echo 500 > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous

will allow PMU to draw 500mA even though you are connected to a dumb charger where the limit is normally held at 100mA, since it didn't enumerate the GTA02. You can give 0, 100, 500 or 1000 here, but make sure your charger source can handle what you give here, otherwise it can exceed what is safe for your charging source to provide.

More details at [[Forcing_fast_charge_mode]].

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/dump_regs====
cat this to get a dump of the I2C registers for the PMU, useful for debugging power problems.

===Bluetooth===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/power_on====
* Default "0" no power to Bluetooth device
* set to "1" to enable power to Bluetooth
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/reset====
* Default to "0", no reset
* set to "1" to reset BT (needed after powerup)

===GPS===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron====
* Default "0" GPS unpowered
* set to "1" to power GPS section

===Audio codec===
====/sys/devices/platform/soc-audio/codec_reg====
cat this to get a dump of codec registers. Note they are 9-bit wide.
====/sys/devices/platform/soc-audio/codec_reg_write====
You can write to any codec register by echoing "<codec reg index in hex> <value in hex>" to here

===Glamo===
====/sys/devices/platform/glamo3362.0/regs====
cat this to get a dump of selected Glamo regs. You can write the regs by echoing "<glamo reg index in decimal> <value in decimal>" here.

===LED & Vibrator===
(per: Jeff Tickle)
====/sys/devices/platform/neo1973-vibrator.0/leds/neo1973:vibrator/brightness====

For the Vibration, my very limited testing indicates it will accept a
range of 0-255, with 0 being off and 255 being full force. So, you can
actually set the strength of vibration.

Keep in mind that the vibration will positively eat your battery, so
use with caution!

====/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/brightness====
====/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness====
====/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness====

For the LEDs, you can echo 1 for on or 0 for off to any of these files
to control the state of the LEDs.

===Accelerometers===
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/power/wakeup====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/power/wakeup====
Turns on accelerometers.

====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/dump====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/dump====
Dumps accelerometers raw contents.

====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/full_scale====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/full_scale====
Switches the accelerometers between 2G and 8G mode. Echo "9.2" into it for 8G, any other value for 2G (default)[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/004029.html]

[[Category:Flashing Openmoko]]
[[Category:System Developers]]

Timezone

2008-12-27T01:55:15Z

Jidanni: /* Debian */ntp

== Timezone ==

At this time, there is no preferences application to set the timezone of your Openmoko device.

For now, either open the terminal application or log in to your Openmoko over the USB networking
connection and change the timezone via commandline commands.

To change the timezone on your FreeRunner you have to

opkg install tzdata

and then install one of these

tzdata-africa
tzdata-americas
tzdata-antarctica
tzdata-arctic
tzdata-asia
tzdata-atlantic
tzdata-australia
tzdata-europe
tzdata-misc
tzdata-pacific
tzdata-posix
tzdata-right

after that, you should create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're on the East Coast of the U.S., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:

ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime

for Germany for example it is TZ="Europe/Berlin"
for France TZ="Europe/Paris"
and so on

Alternatively, you can take the more invasive approach and change the TZ="UTC" in your /etc/profile
to the timezone you want.

Once the timezone is set, restart of your x-server with

/etc/init.d/xserver-nodm restart

you should now have the right timezone.

In the future, expect the time zone to be set automatically by the telephone stack once connected to the network.

See also [[Date]] for setting the date and time.

===Debian===
Just use <code>dpkg-reconfigure tzdata</code>. Also consider installing the <code>ntp</code> package.

[[Category:Advanced End User]]
[[Category:Settings]]

Timezone

2008-12-27T01:53:02Z

Jidanni: Debian is so simple

== Timezone ==

At this time, there is no preferences application to set the timezone of your Openmoko device.

For now, either open the terminal application or log in to your Openmoko over the USB networking
connection and change the timezone via commandline commands.

To change the timezone on your FreeRunner you have to

opkg install tzdata

and then install one of these

tzdata-africa
tzdata-americas
tzdata-antarctica
tzdata-arctic
tzdata-asia
tzdata-atlantic
tzdata-australia
tzdata-europe
tzdata-misc
tzdata-pacific
tzdata-posix
tzdata-right

after that, you should create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're on the East Coast of the U.S., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:

ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime

for Germany for example it is TZ="Europe/Berlin"
for France TZ="Europe/Paris"
and so on

Alternatively, you can take the more invasive approach and change the TZ="UTC" in your /etc/profile
to the timezone you want.

Once the timezone is set, restart of your x-server with

/etc/init.d/xserver-nodm restart

you should now have the right timezone.

In the future, expect the time zone to be set automatically by the telephone stack once connected to the network.

See also [[Date]] for setting the date and time.

===Debian===
Just use <code>dpkg-reconfigure tzdata</code>.

[[Category:Advanced End User]]
[[Category:Settings]]

Qi

2008-12-27T01:43:10Z

Jidanni: /* Partitions */half true

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

==Concept==
Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

==Partitions==
Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card.
* Qi looks for a kernel in the first, second and third partition, silently ignoring FAT partitions.
* Qi expects the / (root) filesystem to be on the same partition as /boot ([http://permalink.gmane.org/gmane.comp.hardware.smartphones.pkg-fso-maint/104 half true]).
* If both uImage-GTA02.bin and uImage-GTA03.bin files are present, Qi loads the right one for the machine.

Failing to find a kernel in the SD card, Qi will boot from the kernel in NAND (if the kernel works of course, see below). Failing to find a valid kernel, Qi perform a memory test. It means that one can either move kernels out of the way to get the memory test, or make an SD Card just with normal Qi on it and no kernels to get a memory test.
* Up to Nov. 28th, Qi would blink the blue Power LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==
The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
Look at your dmesg(1) output for the CPU to pick the right s3c* version. OK, actually they are:
*qi-s3c2410 --> GTA01
*qi-s3c2442 --> GTA02
*qi-s3c6410 --> GTA03

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

==Enabling console messages==
[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
console=tty0 loglevel=8
and you'll see the messages on boot. If it's NAND right now you need to edit the default commandline in Qi for gta02.

==SD Initialisation==
If you don't specify loglevel=8 in append-GTAXX, and booting fails with a "VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)", the SD card needs a little bit more time to initialise.

Put a "rootdelay=" in append-GTAXX like so:
rootdelay=1

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* Qi often doesn't want to resume after suspend.
* Qi is able to load kernels larger than 2MB correctly, uBoot has a bug.

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]

Community Updates/2008-12-15

2008-12-18T00:40:38Z

Jidanni: link Qi

Welcome back everybody to the Seventh edition of our [[Community Updates]] newsletter. It was actually chilly around here, especially when John announced that the Optimization Team was disbanded, but there was still no release. A perfect weather to sip hot drinks from a fan mug bought at the newly opened [http://www.cafepress.com/openmoko_inc Openmoko merchandise online store]. The money will go to community projects, for example bounties set up at [http://cofundos.org/projects.php?tag=openmoko cofundos.org], where ideas and money-rich but time-poors users can meet the enterprising hackers.

== Applications ==

These weeks, new or updated applications are arriving almost every day. I cannot wait for Chrismas break, when people will really have time to hobby code !

New:
* [http://www.opkg.org/package_58.html OpenTTD]. An open source clone of the popular Transport Tycoon Deluxe game.
* [[Enotes]] (formerly fido) a TODO list manager written with elementary, designed for distributions that use illume, like SHR.
* [[OMoney]] a bookkeeping application to track daily incomes and expenses.
* [http://www.opkg.org/package_55.html ePiano] 0.1 A virtual piano keyboard to play simple songs.
* [http://www.opkg.org/package_54.html SCR] 1.432 (new on opkg) a alternative input method for entring text with your finger.
* [[ZOMG!]] the embryo of a graphical package manager in Java.
* Alex O. of the [http://moko.networld.to/ MokSec] project released a call control firewall ([http://opkg.networld.to/moksec/testing/ ipk]) based on a black- and whitelist system. Next up is integration with FSO, which needs a filtering extension.

Updated:
* [[TwitterMoko]] O.4. Packaging improvements following suggestions by experienced Debian Dev.
* [[Gpsdcontrol]] 0.4. A Python script to turn on/off gpsd and gps antenna from the desktop. Add: icon changes to show GPS system state.
* [[Orrery]] 2.3. Added a Planet Compass (on opts menu), dates of major moon phases, minor bugfixes.
* [[neoqplayer]] 0.2 "sunset". Finger friendly, cover show, playlist view, nicer theme, bugfixes.
* [[gtkaddpoi]] 0.5a, SHR compatibility fix.
* [http://projects.openmoko.org/projects/aphasia/ Aphasia] A very innovative project to communicate with images rather than sounds, experimental code. Now using dbus.
* [[Paroli]] gets some documentation and a wiki page.
* [http://blog.1407.org/2008/12/12/omnewrotate-052-is-out/ OMNewRotate] 0.5.2, desktop icon and script, uses autotools, fix suspend bug.
* [[Navit]] is a car navigation system with routing engine. Nathan K. wrote that the [http://download.navit-project.org/navit/openmoko/svn/ newer opkg] were a vast improvement (the directory can also be used as a feed).

Note to projects.openmoko.org project admins: Please consider announcing new releases/updates, as the GForge engine does not do it automatically.

== Distributions ==

Okay, we are still waiting to see which distribution will be the first to get out officially with the newer 2.6.28 kernel.

* Android really jumped up in the hit-parade of the [http://wiki.openmoko.org/wiki/Wiki_statistic_numbers#November.2C_2008 most popular pages]. The wiki page with installation instructions has moved to [[Android on Freerunner]], so from now on please use the page [[User_talk:Seanmcneil3]] for discussion. Koolu's Android git is online at http://git.koolu.org/.
* The [[Debian]] wiki page still needs a good cleanup.
* [[FDOM]] successfully moved its build system to an OpenEmbedded overlay and is considering jumping over from ASU stable to ASU testing.
* Qt Extended (formerly [[Qtopia]]). The currently best version seem to be [http://other.lastnetwork.net/OpenMoko/ Hypnotize's unofficial ones]. Lorn (our liaison Software Engineer at Nokia) will try to get an official snapshot out before the solstice.
* [[SHR]] latest Dec. 9th image has fastboot patches in.
* An [[FSO]] user [http://lists.openmoko.org/pipermail/community/2008-December/037603.html suggested] that it was time to test the newer kernel, that the needed changes [http://trac.freesmartphone.org/ticket/293 described on FSO's trac] were minor. He reported good things about it.
* [http://lists.hackable1.org/pipermail/hackable1-dev/2008-December/000030.html Hackable:1] build system is ready, image released and "how you can join" email.

== Infrastructure ==

* The hottest and bloodiest kernels are at [http://people.openmoko.org/andy Andy's]. They have Nicolas Dufresne's patches for WSOD, a power supply driver ([http://lists.openmoko.org/nabble.html#nabble-td1506725 pcf50633 rewrite]), touchscreen reliability improvements, a WLAN driver using the mainline SDIO stack, almost Android-readiness, plus all the Kernel features and fixes between 2.6.24 and 2.6.28, especially [http://lists.openmoko.org/nabble.html#nabble-td1618262 resume/suspend improvements]. As these kernels are larger than 2MB, one need to [http://lists.openmoko.org/pipermail/community/2008-December/036921.html meddle with u-Boot] or use [[Qi]] to test them and the newer /sys.
* Openmoko used to build its distribution using its own copy of OpenEmbedded's Bitbake tree, hosted in its own git under project name [http://git.openmoko.org/?p=openmoko.git;a=summary org.openmoko.dev]. That project has been terminated. Local changes are now being backported upstream so that FSO and everybody else benefits. From now on, further fixes or updates should be directly committed upstream to OpenEmbedded

== Hardware ==
* Erin documentad how to use the [[Manually_using_Bluetooth#OBEX|OBEX]] protocol to send files via Bluetooth.
* Someone asked how to make new, original cases in quantities less than 100. The answer was that there are [http://en.wikipedia.org/wiki/3D_printing 3D Printing] shops around that would gladly make any object you design, you just need to provide them with the CAD file. http://ponoko.com, http://emachineshop.com, http://www.shapeways.com were nomminated.
* Following up on [http://lists.openmoko.org/pipermail/devel/2008-December/003641.html Graeme G's] report on the steady but slow progress of the Xorg glamo driver, [http://lists.openmoko.org/pipermail/devel/2008-December/003667.html Thomas W.] and Andreas P. reported promising initial progress on 3D acceleration. GG all !
* Joerg released the draft of the technical paper describing the hardware fix to the buzz issue. Steve is working on the next difficult question: [http://lists.openmoko.org/pipermail/community/2008-December/037536.html how to apply the rework to the A5/A6 units already sold] ?

== Community ==
* By popular demand, Openmoko opened a virtual [http://www.cafepress.com/openmoko_inc merchandise store] online. Everybody is invited to post cool t-shirts design. Profits will go to bounties and other programs to aid the community. [http://pyneo.org/ pyneo] fans note that their favorite distribution has its own [http://pyneo.org/t-shirt/ online shop].
* The FreeRunner is on the cover of December's [http://www.lfymag.com/index.asp?id=13 Linux for You] magazine.
* The community is trying out the bounty system at [http://cofundos.org/projects.php?tag=openmoko cofundos.org]. As a start, there is one offer for the accelerated X driver, but media player, volume control/mixer, wifi network manager have also been discussed. This is still a social experiment. We need help and more discussion to define the bounties and claim conditions more precisely.
* [http://opkg.org opkg.org] was updated. There is now a simple REST interface ([http://www.opkg.org/api.php API documentation]) to query the database, and a "source code URL" field. Thank you Tobias for this useful community service !

* Geocaching is a high-tech treasure hunting game played throughout the world by adventure seekers equipped with GPS devices. The basic idea is to locate hidden containers, called geocaches, outdoors and then share your experiences online. Geocaching is enjoyed by people from all age groups, with a strong sense of community and support for the environment. Here is a [http://www.zindep.com/blog-zindep/geocaching_tangogps small script] to play it with [[TangoGPS]].

* JesusMcCloud created a finger friendly keyboard layout for Illume, with bigger Symbols. You can find more information and a photo in the german [http://freeyourphone.de/portal_v1/viewtopic.php?f=23&t=775&p=8087&hilit=fingertaugliches#p8062 freeyourphone.de forum]

''Did you know it?'' Sean Moss-Pultz introduced OpenMoko's Neo1973 on November 7th, 2006. It was the "Mystery Guest" at the inaugural Open Source in Mobile ([http://www.osimworld.com/newt/l/handsetsvision/osim08/ OSiM]) conference in Amsterdam. The link to the presentation on [[Openmoko:Current_events]] is broken, but one can still [http://web.archive.org/web/19960101-re_/http://www.openmoko.com/files/OpenMoko_Amsterdam.pdf web archive the PDF] or read it online at [http://www.linuxdevices.com/news/NS2986976174.html linuxdevices]. Oh, the screenshots looked so cool on the presentation !

== Direct from Openmoko ==

The optimization team finished their work a few weeks ago. No formal update was released so far. According to [http://n2.nabble.com/-Full-test-report-of-Om2008.testing%28Om2008.12.2%29--part2-tp1642645p1642645.html testing reports], the image is only a little better than 2008.9 update. There are still about 10 critical bugs that an end user would not accept in a smartphone product. Three of those bugs should be already fixed in the latests (2.6.28) kernels, however. There are also [http://lists.openmoko.org/pipermail/community/2008-December/037229.html GTK regressions remaining] compared to 2007.2.

Wolfgang Spraul [http://n2.nabble.com/No-more-optimization-team-tp1637861p1638039.html explained] Openmoko's software strategy for the next 6 months as follows:

====1. Current stable image====
Our current stable image is [http://downloads.openmoko.org/releases/Om2008.9/ Om2008.9]
We are sometimes cherry-picking fixes into it, but admittedly not as many as we would like. If someone wants to step up to become stable maintainer for this image and cherry-pick more fixes into it, please let me know.
Alternatively, a number of other images are available, see [[Distributions]].

====2. Mickey's framework milestones====
As many people know, the next big thing for Openmoko will be Mickey's FSO [[OpenmokoFramework]] around D-bus and Python, and the [[Paroli]] telephony UI. A few weeks ago, Mickey released [http://downloads.freesmartphone.org/fso-stable/milestone4.1/ milestone 4]. In late January, he plans to come out with milestone 5, in late March with milestone 6.
See here for a more detailed roadmap: http://trac.freesmartphone.org/roadmap

====3. Next major release, Om2009====
After the next 2 FSO milestones, Openmoko will fork off a stable branch, and spend 2-3 months on testing and bug fixing. This will lead to our next major release, Om2009. The telephony UI will be Paroli, see http://code.google.com/p/paroli/
The way things are going right now, we will probably have this release mid-next year.

====Position available====
Openmoko [http://n2.nabble.com/No-more-optimization-team-tp1637861p1638092.html is looking for] a serious distribution maintainer. Someone who can do the exceptionally hard work of distribution integration, fixing bugs, small and large, from top to bottom of the stack, from UI to kernel, across many packages. Someone with a proven Free Software background. Any applications just email Wolfgang Spraul < wolfgang at openmoko.com > .
[[Category:Community Update]]

Mailing List Duplicates

2008-12-12T02:13:10Z

Jidanni: All didn't go well?

{{Note|Ticket was closed on November 3rd, 2008. Consider deleting this page in by November 10th if all goes well. But all [http://permalink.gmane.org/gmane.discuss/12065 didn't?]}}

Q: How long has there been duplicates on the Openmoko mailing lists?

A: Since the list got so big that sita.openmoko.org can't handle it. See [http://admin-trac.openmoko.org/trac/ticket/1372 ticket #1372].

Q: How long has that been?

A: At least a year, maybe more.

Q: Has Openmoko done anything about it?

A: Doesn't seem so. Must be a hard problem.

Q: Is Openmoko likely to fix it?

A: If they haven't fixed it by now, then chances are they probably won't.

Q: What should I do about it?

A: Don't email the list about - we all know already.

Q: How can I fix it locally for me?

A: Get a mail reader that understands that a message with a duplicate Message-Id header field doesn't need to be displayed to the user.

[[Category:Community]]

Qi

2008-12-12T01:50:32Z

Jidanni: /* Download and installation */mention versions

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

==Concept==
Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

==Partitions==
Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card.
* Qi looks for a kernel in the first, second and third partition, silently ignoring FAT partitions.
* Qi expects the / (root) filesystem to be on the same partition as /boot.
* If both uImage-GTA02 and uImage-GTA03 files are present, Qi loads the right one for the machine.

Failing to find a kernel in the SD card, Qi will boot from the kernel in NAND (if the kernel works of course, see below). Failing to find a valid kernel, Qi perform a memory test. It means that one can either move kernels out of the way to get the memory test, or make an SD Card just with normal Qi on it and no kernels to get a memory test.
* Up to Nov. 28th, Qi would blink the blue Power LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==
The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
Look at your dmesg(1) output for the CPU to pick the right s3c* version. OK, actually they are:
*qi-s3c2410 --> GTA01
*qi-s3c2442 --> GTA02
*qi-s3c6410 --> GTA03

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

==Enabling console messages==
[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
console=tty0 loglevel=8
and you'll see the messages on boot. If it's NAND right now you need to edit the default commandline in Qi for gta02.

==SD Initialisation==
If you don't specify loglevel=8 in append-GTAXX, and booting fails with a "VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)", the SD card needs a little bit more time to initialise.

Put a "rootdelay=" in append-GTAXX like so:
rootdelay=1

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* Qi often doesn't want to resume after suspend.
* Qi is able to load kernels larger than 2MB correctly, uBoot has a bug.

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]

Openmoko:Current events

2008-12-11T22:01:24Z

Jidanni: fix slob links

This ''Current Events'' page provides information on both [[#Upcoming|upcoming]] and [[#Past|past]] events where FIC or Openmoko had or will have a presence.

== Upcoming ==

* 2008-11-18: [http://www.balug.org/ Bay Area Linux Users Group (BALUG) 2008] November 18, 2008 | [http://www.fourseasr.com/ Four Seas Restaurant], San Francisco, USA | Sean will speak there

== Past ==
* 2008-09-24: [http://www.openexpo.ch/openexpo-2008-zuerich/ OpenExpo 2008 Zürich] September 24-25, 2008 | Winterthur, Switzerland | Booth organised by the [[Openmoko Local Groups: Switzerland|Openmoko Local Group Switzerland]]
* 2008-09-17: [http://www.osimworld.com/newt/l/handsetsvision/osim08/ OSiM Open Source in Mobile World] September 17-18, 2008 | Hotel Palace Berlin, Germany | Sean gave a speech on the 17th, interview [http://arstechnica.com/news.ars/post/20080918-openmoko-ceo-embrace-fragmentation-diversity-is-a-strength.html here]
* 2008-08-23: [http://www.froscon.org FrOSCon 2008] August 23-24, 2008 | Bonn / St.Augustin, Germany | [[User:Mickey|Mickey]] gave a talk.
* 2008-08-04: [http://www.linuxworldexpo.com/live/12/ LinuxWorld 2008] August 04-07, 2008 | Moscone Center, San Francisco, CA | in booth 1625 and in the Linux Garage Pavilion booth 1234 in the Moscone Center North Hall | Michael, Harry, Steve, Sean and Jeremy were there
* 2008-07-10: [http://wiki.oreillynet.com/foocamp08/ O'Reilly Foo Camp] July 11-13, 2008 | Sebastopol, CA | Michael Shiloh was there
* 2008-06-24: [http://www.campus-party.com.co/ Campus Party in Colombia] June 23-29, 2008 | Bogota, Colombia | Sean gave a speech on 25th
* 2008-05-28: [http://www.linuxtag.org LinuxTag 2008] May 27-31, 2008 | Berlin, Germany | LinuxTag | [[User:Mickey|Mickey]] had a talk, Openmoko had a booth.
* 2008-05-16: [http://www.bsdcan.org/2008/ BSDCan] May 16-18, 2008 | Ottawa, CA | [[User:Idarwin|Ian Darwin]] presented Openmoko FreeRunner to the BSD crowd.
* 2008-04-09: Wednesday April 9, 2008 | London, UK | [http://ole.tange.dk Ole Tange] presented Openmoko / Freerunner to the [http://www.ukuug.org/events/openmoko/ UK Unix Users Group]
* 2008-04-08: [https://www.linux-foundation.org/events/collaboration The Linux Foundation Spring 2008 Collaboration Summit] April 8-10, 2008 | University of Texas Commons Center, Austin, TX | Sean is invited as one of the speakers
* 2008-03-28: [[Openmoko Education/zh tw]] - Friday March 28, 2008. | Hualien, Taiwan | Taiwan School promotion: Openmoko concepts will be presented at National Dong Hwa University
* 2008-03-26: [[Openmoko Education/zh tw]] - Wednesday March 26, 2008. | Chung Li, Taiwan | Taiwan School promotion: Openmoko concepts will be presented at Yuan Ze University
* 2008-03-16: [http://www.bossaconference.indt.org/ Bossa'08] - March 16-19, 2008 | Porto de Galinhas, Brazil| [[User:Raster|Raster]] is attending and will give a talk
* 2008-03-12: [http://www.openexpo.ch/openexpo-2008-bern/ OpenExpo'08] - March 12-13, 2008 | Bern, Switzerland | [[User:Mickey|Mickey]] is giving a talk about Openmoko | [[User:C7|C7]] is organising an OpenMoko booth
* 2008-03-06: [http://en.oreilly.com/et2008/public/schedule/detail/3330 OpenMoko and Ubiquitous Computing] - March 6, 2008 | San Diego, California | [[User:Michaelshiloh|Michael Shiloh]] is attending and will give a talk at ETech
* 2008-03-03: [[Openmoko Education/zh tw]] - Monday March 3, 2008. | Chung Li, Taiwan | Taiwan School promotion: Openmoko concepts will be presented at Chung Yuan Christian University
* 2008-02-27: [[Openmoko Education/zh tw]] - Wednesday February 27, 2008. | Hsinzhu, Taiwan | Taiwan School promotion: OpenMoko concepts will be presented at National Chiao Tung University
* 2008-02-23: [http://www.fosdem.org Fosdem'08] - February 23-24, 2008 | Brussels, Belgium | OpenMoko will be present at the [http://www.openembedded.org OpenEmbedded] booth, lots of OpenMoko developers will be present. [[Events:FOSDEM_2008 | Will you be there?]]
* 2008-02-22: [[Openmoko Education/zh tw]] - Friday February 22, 2008. | Tainan, Taiwan | Taiwan School promotion: OpenMoko concepts will be presented at National Cheng Kung University
* 2008-02-19: [http://www.oss.org.cn/index.php?option=com_content&task=view&id=677&Itemid=162 2008 Linux Developer Symposium-China] - February 19, 2008 | Beijing, China | Neo1973 was presented in a booth by Sun Liantao from [http://www.csip.org.cn CSIP] and [http://www.beijinglug.org BLUG]
* 2008-02-08: [http://www.socallinuxexpo.org/ SCALE'08] - February 8-10, 2008 | Los Angeles, USA | [[User:Raster|Raster]] is attending and will man the OpenMoko and Enlightenment booths
* 2008-01-07: Consumer Electronics Trade Show. [[Neo FreeRunner]] was presented. Links to stories, pictures, and videos: 
[[http://gizmodo.com/341755/openmoko-neo-freerunner-linux-smartphone-hands+on gizmodo]] 
[[http://takezero.net/3g-and-mobile-news/hands-on-with-fics-openmoko-powered-freerunner-2 takezero ]] 
[[http://youtube.com/watch?v=SZsps3bj6yE youtube]] 
[[http://www.reghardware.co.uk/2008/01/11/ces_video_openmoko_handset/ reghardware]] 
* 2007-12-19: [[OpenLab 2nd Event/zh tw]] - December 19, Wed. | Taipei, Taiwan | OpenLab 2nd Event: GPL & Apache License Talk and Discussion.
* 2007-11-17: [[Openmoko OpenLab Opening]] - November 17, Sat. | Taipei, Taiwan | OpenLab for OpenMoko Community is going to open.
* 2007-11-04: [http://coscup.org/2007/ Conference for Open Source Coders, Users and Promoters] - November 04 | Taipei, Taiwan | Jollen gave a talk about OpenMoko and OpenLab ideas.
* 2007-10-13: [http://onlinux.ca OnLinux Ontario Linux Fest 2007] - October 13 | Toronto, Canada | [[User:Idarwin|Ian Darwin]] gave a talk about Openmoko (slides [http://www.darwinsys.com/openmoko/ here]).
* 2007-10-02: [http://www.coss.fi/web/openmind/programme Openmind Conference] - October 02-03, 2007 | Tampere, Finland | Michael Shiloh as a speaker
* 2007-09-26: [http://imm.dtu.dk/ IMM at Danish Technical University] - [http://ole.tange.dk Ole Tange] is giving a talk.
* 2007-09-23: [http://www.barcamporlando.org/ BarCamp Orlando] Orlando, FL, USA | [[User:Writchie|Wally Ritchie]] will show Neos and talk about Openmoko project
* 2007-09-20: [http://www.openexpo.ch/openexpo-2007-zuerich/ OpenExpo'07] - September 19-20, 2007 | Zurich, Switzerland | [[User:Mickey|Mickey]] gave a talk about OpenMoko | [[User:C7|C7]] was organising an OpenMoko booth
* 2007-09-15: [http://mrmcd110b.metarheinmain.de metarheinmain chaosdays 110b] - ixs igave a [https://mrmcd110b.metarheinmain.de/fahrplan/events/2107.en.html talk]
* 2007-09-12: [http://dmusyd.edu/ Datamatikeruddannelsen i Nykøbing Falster] - [http://ole.tange.dk Ole Tange] gave a talk.
* 2007-08-30: [http://mobiledevices.kom.aau.dk/team_and_organization/events/mobile_developer_days_2007/ Mobile Developer Days 2007] - August 30 - September 2, 2007 | at Aalborg University, Denmark | [[User:Mickey|Mickey]] was invited to give a speech
* 2007-08-25: [http://www.froscon.org/Home.2.0.html?L=1 FrosCon'07] - August 25-26, 2007 | Sankt Augustin, Bonn, Germany | Mickey gave a talk about OpenMoko
* 2007-08-21: [http://www.beijinglug.org/en/index.php Beijing LUG] - August 21, 2007 | Sean and other OpenMoko team members were there to talk and give a presentation
* 2007-08-08 till 08-12: [http://events.ccc.de/camp/2007/Chaos_Communication_Camp_2007 Chaos Communication Camp 2007] took place in Finowfurt (close to Berlin, Germany) featuring the [http://events.ccc.de/camp/2007/GSM_Village GSM Village]
* 2007-08-04: [http://barcamp.org/BarCampRDU BarCampRDU] Raleigh, NC, USA | [[User:Writchie|Wally Ritchie]] showed neos and talk about OpenMoko project
* 2007-08-03: [http://wikimania2007.wikimedia.org/wiki/Main_Page wikimania 2007] - August 03-05, 2007 | Taipei, Taiwan | OpenMoko has been invited to co-host with Wiki heads to promote open content in Taiwan.
* 2007-07-26 [http://conferences.oreillynet.com/os2007/ OSCON 2007] | OpenMoko Birds of a Feather session July 26th, Portland Oregon
* 2007-07-15: [http://www.guadec.org GUADEC, The GNOME Conference 2007] - July 15-21, 2007 | Birmingham, United Kingdom | [[User:Mickey|Mickey]] gave a talk about OpenMoko
* 2007-07-10: [http://www.rmll.info 8th Libre Software Meeting] - July 10-14, 2007 | Amiens, France | [http://datenfreihafen.org Stefan Schmidt] gave a [http://www.rmll.info/article136.html?lang=en talk] about OpenEZX and OpenMoko
* 2007-07-09: The [http://www.openmoko.com openmoko.com web shop] was opened; first sales of GTA01_v4 devices.
* 2007-06-05: [http://www.computextaipei.com.tw Computex Taipei 2007] - June 5-9, 2007 | Taipei World Trade Center, Taipei, Taiwan | OpenMoko was in the FIC Group's Booth
* 2007-06-01: [http://www.linuxtag.org/2007/en/home/welcome.html LinuxTag 2007] - May 30-June-2, 2007 | LinuxTag in Berlin, Germany | [[User:Mickey|Mickey]] gave a [http://www.linuxtag.org/2007/en/conf/events/vp-speakers/details.html?talkid=84 talk] about OpenMoko
* 2007-05-19: [http://www.makerfaire.com/ Maker Faire Events] -- May 19-May 20, 2007 | San Francisco Bay Area, San Mateo Expo Center, USA | Michael Shiloh and Jon Phillips presented at OpenMoko's booth on behalf of Sean
* 2007-05-08 [http://wiki.tossug.org/SignUp:2007-05 Taipei Open Source Software User Group (TOSSUG)] - Cafe Lumiere, Taipei, Taiwan | May 8, 2007
* 2007-04-04 [http://fostel2007.fostel.org/index.php/Main_Page FOSTEL] - European Institute of Technology, Paris, France | April 4-5, 2007
* 2007-03-16: On March 16, 2007 [[User:Mickey|Mickey]] presented the device at a Zaurus User Group Meeting in Düsseldorf, Germany.
* 2007-03-15: On March 15-18, 2007 there was a Polish Linux User Group conference [http://pingwinaria.linux.org.pl/PLUG/imprezy/pingwinaria/2007/agenda Pingwinaria 2007] in Krynica Zdrój, Poland. Tomasz Zieliński gave a talk about OpenMoko and two Neo1973 devices were present there. Also Marcin Juszkiewicz presented OpenEmbedded project there.
* 2007-03-05: 36 P0 devices shipped to developers.
* 2007-03-03: [http://www.linuxforum.dk/2007/program/saturday/Martin_Hansen.shtml Martin Hansen and Ole Tange] spoke at [http://www.linuxforum.dk LinuxForum]
* 2007-02-27: February 27th-March 1st the [http://conferences.oreillynet.com/etel2007/ O'Reilly Emerging Telephony conference] was held at the San Francisco Airport Mariott, Burlingame, CA. Open Phones are on the agenda: Sean presented a workshop on February 27; Surj Patel and Matt Hamrick of Tuxphone and the homebrew club also presented. An OpenMoko/Open Phones Social gathering was proposed on the evening of the last day, March 1. We hope Tuxphone and SVHMPC people will join us as well.
* 2007-02-23: Meeting at [[Events:FOSDEM_2007|FOSDEM 2007]]
* 2007-02-14: The openmoko.org web site was [http://lists.openmoko.org/pipermail/announce/2007-February/000004.html opened to the public].
* 2007-01-06 [http://www.lunchat.com/ Lunch@Piero's] - CES, Las Vegas, NE | 7-9 January, 2007
* 2006-11-07: [http://www.informatm.com/NASApp/cs/ContentServer?pagename=marlin/home&MarlinViewType=MARKT_EFFORT&siteid=30000000861&marketingid=20001437372&proceed=true&MarEntityId=1162023598681&entHash=100595e9ac1 Open Source in Mobile] - Amsterdam, The Netherlands, 7-8 November 2006. Sean Moss-Pultz's "Mystery Guest" presentation can be found [http://www.openmoko.com/files/OpenMoko_Amsterdam.pdf here].

{{Languages|Openmoko:Current events}}

[[Category:Community]]
[[Category:Event]]

Gentoo

2008-12-03T02:43:24Z

Jidanni: /* Installation */swap

{{Languages|Gentoo}}
== Overview ==
Gentoo armv4tl-softfloat-linux-gnueabi optimalized for Openmoko (-Os -march=armv4t -mtune=arm920t) on 2008.0/arm profile (glibc based, sane bootstrapable toolchain) 
(embedded uclibc/arm profile armv4tl-softfloat-linux-uclibcgnueabi in plans)

[http://img46.imageshack.us/img46/646/80330048oy9.jpg Screenshot (hosted at ImageShack)]

== Read first ==
'''http://www.gentoo.org/doc/en/handbook/handbook-arm.xml''' (Skip points 2 and 3)

== Needed things ==

*At least 2GB SD card
*Gentoo stage: http://torindel.sezamkowa.net/openmoko/armv4tl-softfloat-linux-gnueabi/~arm/
*Portage snapshot: look for mirror on: http://www.gentoo.org/main/en/mirrors2.xml and get snapshots/portage-DATE.tar.bz2
*Kernel and modules
*Any working Openmoko distro

== Installation ==
<ol>
<li>Partition your sd card if needed (don`t make swap partitions
(but see [http://lists.openmoko.org/pipermail/community/2008-September/031106.html]), ensure card isn't mounted): </li>
fdisk /dev/mmcblk0

<li>Make ext2 or ext3 filesystem: </li>
mkfs.ext2 /dev/mmcblk0p1

<li>Mount partition: </li>
mount /dev/mmcblk0p1 /media/card

<li>Copy stage and portage from host to moko (e.g. on localhost): </li>
scp stage3-armv4tl-*.tar.bz2 portage-*.tar.bz2 root@openmoko:/media/card

<li>Unpack stage and portage: </li>
tar -xjpf /media/card/stage3-armv4tl-*.tar.bz2 -C /media/card
tar -xjpf /media/card/portage-*.tar.bz2 -C /media/card/usr

<li>Cleanup removing tar.bz2: </li>
rm /media/card/stage3-armv4tl-*.tar.bz2 /media/card/portage-*.tar.bz2

<li>Chroot: </li>
chroot /media/card /bin/bash

<li>Update chroot environment: </li>
source /etc/profile; env-update

<li>Set timezone: </li>
cp /usr/share/zoneinfo/YOURZONE /etc/localtime

<li>Set hostname: </li>
nano /etc/conf.d/hostname

<li>Remove console font changing (small is beautiful ;]): </li>
rc-update del consolefont boot

<li>Setup fstab: </li>
nano /etc/fstab

<li>Edit inittab (hash out c3, c4, c5, c6, s0, s1 lines): </li>
nano /etc/inittab

<li>Setup usb networking: </li>
echo "modules=\"g_ether\"" >> /etc/conf.d/modules
ln -s /etc/init.d/net.lo /etc/init.d/net.usb0
echo "config_usb0=\"192.168.0.202 netmask 255.255.255.0\"" > /etc/conf.d/net
echo "routes_usb0=\"default via 192.168.0.200\"" >> /etc/conf.d/net
echo "nameserver 192.168.0.200" > /etc/resolv.conf

<li>Enable sshd: </li>
rc-update add sshd default

<li>Change root password: </li>
passwd

<li>Leave chroot: </li>
exit

<li>Copy kernel. </li>
cp /boot/uImage-2.6.24 /media/card/boot/

<li>Copy modules. </li>
cp -rpf /lib/modules /media/card/lib/

<li>Setup uboot for booting from sd card. </li>
<li>Reboot. </li>
<li>Setup/emerge rest of the system. </li>

== Emerging binary packages ==
*Binary package sites
:http://tinderbox.dev.gentoo.org/embedded/openmoko/armv4tl-softfloat-linux-gnueabi/
:http://torindel.sezamkowa.net/openmoko/armv4tl-softfloat-linux-gnueabi/~arm/packages/All
*Add PORTAGE_BINHOST to make.conf
:<tt>e.g.</tt> <pre>echo "PORTAGE_BINHOST=\"http://torindel.sezamkowa.net/openmoko/armv4tl-softfloat-linux-gnueabi/~arm/packages/All\"" >> /etc/make.conf</pre>
*Update environment
:<tt>e.g.</tt> <pre>source /etc/profile; env-update</pre>
*Setup install mask if you don't want compiler headers/docs etc (mask headers only if you'll be always using binary packages)
:<tt>e.g.</tt> <pre>export INSTALL_MASK="*.h"</pre>
*Add the following line to make.conf to tell portage to always use binary packages. <pre>EMERGE_DEFAULT_OPTS="-gK"</pre>

== Alternative: Squashed Portage ==
An alternative to installing a full, writeable, and uncompressed portage tree directly on the microSD card, is to compress portage using SquashFS and then to mount the resuling SquashFS file (usually compressed from about 500 MB to 50 MB) at /usr/portage.

In this case, it is also suggested to set DISTDIR to /tmp/distfiles, because the default DISTDIR (/usr/portage/distfiles) is not writeable. Similarly, PKGDIR can be set to /tmp/binpkgs instead of the default /usr/portage/packages.

See [http://perpetual-notion.blogspot.com/2008/06/gentoo-on-eee-pc.html this] blog post for further details. If you are lacking in extra space on your flash device, or are concerned about extraneous write-cycles to your flash memory, then you should perform all of the steps on desktop linux machine and then finally copy the resulting squashfs image to the FreeRunner.

== Openmoko Overlay ==
Add svn://torindel.sezamkowa.net/openmoko to layman (emerge layman)

== Binary package wishlist ==
As i'll be adding some packages to ftp above you might want to ask for some package here: [[GentooPackageWishList]] 
Overlay with moko things and more packages coming soon.

[[category:Distributions]]

Manual Debian

2008-12-03T02:40:46Z

Jidanni: /* Prepare SD card */swap

{{Languages|Debian}}

''Contents of this page is probably old and superceded by this new pae : [[Debian]].''

[[Image:Debian.png|thumb|480px|''Debian on neo1973'']]
This page is to explain how to run Debian armel port on Openmoko devices. You can do this from scratch, or download a prebuilt file system.
The former will take some time, perhaps 2 hours, depending on your internet connection

= Prebuilt Filesystem =

Download and extract to an ext2/ext3 formatted filesystem on your SD card:

wget http://rabenfrost.net/debian/debian-armel-xfce.tar.bz2

Note that the above is just a bit too big to fit on a 512MB SD card. A smaller image will soon be provided.

Access via SSH is much the same as under other images using [[USB Networking]], with the user accounts below:

* root password: openmoko
* First user and password: openmoko

Note: If you upgrade your your debian and your touchscreen doesn't work any more, you most likely have to adjust /etc/udev/rules.d/50-udev.rules by applying the settings described later in this document for /etc/udev/udev.rules

== (Optional) Install Known Good Kernel ==

This kernel was build by Marcel_M and has some important patches in it such as removed sd debug symbols and build-in ext3 support.

wget http://rabenfrost.net/celtune/uImage-2.6.24+svnr4194-r4165-r3-neo1973.bin
./dfu-util -d 0x1457:0x5119 -a kernel -R -D ./uImage-2.6.24+svnr4194-r4165-r3-neo1973.bin

This kernel doesn't work for gta02 (just my expirience, it didn't detect ext3), but the kernel from Om 2008.9 works good.
http://downloads.openmoko.org/releases/Om2008.9/Om2008.9-gta02-20080916.uImage.bin

== (Optional) Recompiling Kernel to Add Drivers ==
(Based on http://lists.openmoko.org/pipermail/support/2008-August/001240.html)

Steps to build the kernel standalone with the "moredrivers" config (to get additional drivers, such as the usb tether drivers that were moved out as kernel modules, compiled directly into the kernel).

~ - git clone git://git.openmoko.org/git/kernel.git linux-2.6
~ - cd linux-2.6
~ - git checkout origin/stable
~ - edit ./build to point to your compiler path
~ - cp defconfig-2.6.24 .config
~ - ./build

That gets you a uImage.bin you can DFU or copy into your SD Card filesystem.

== Configure booting from SD/SDHC ==

Do as proposed here: [[Booting_from_SD]]

Note that these instructions are in need a rewrite.

= Build your own armel filesystem =

== (Option 1) debootstrap your rootfs on Debian or Ubuntu host ==

debootstrap --verbose --arch armel --foreign sid ./armel-chroot http://ftp.de.debian.org/debian/

== (option 2) download ready to use armel rootfs ==

If you don't have debootstrap on your system you can download the results here:

wget http://rabenfrost.net/debian/armel-chroot-first-stage.tar.gz

== Prepare SD card ==

ssh to your neo and format your sd card appropriately. I'm using an 8GB SDHC card here.

:''NOTE: it might be a good idea not to use ext3. This is because ext3 is a heavily journalising file system and on the freerunner (sd card) might cause premature death of the card. It is recommened you use ext2 or another similar file system. One also will need a vfat or ext2 (only vfat worked for me with the stock u-boot for the freerunner. On which to place the kernel to boot off. See the [[Booting_from_SD]] If you have not done so already.''

fdisk /dev/mmcblk0
We will now create a 8 mb partition for our kernel and another one for the rootfs which will take up all the
remaining space.
Command (m for help): d
Selected partition 1
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-983, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (18-983, default 18):
Using default value 18
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):
Using default value 983
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.

[http://lists.openmoko.org/pipermail/community/2008-September/031106.html Consider a swap partition].

mkfs.vfat /dev/mmcblk0p1

mkfs.ext3 /dev/mmcblk0p2
mount /dev/mmcblk0p2 /media/card

copy the armel chroot to your device by tar'ing it to circumvent symbolic link cycles (https://bugzilla.mindrot.org/show_bug.cgi?id=1059 <= WONTFIX)

tar -C ./armel-chroot/ -c . | ssh root@192.168.0.202 tar -C /media/card -xv
or if you downloaded the archive

cat armel-chroot-first-stage.tar.gz | ssh root@192.168.0.202 tar -C /media/card -xzvf -

== Complete debootstrap Process ==

ssh to your device and execute the following commands (just copypaste everything below)

echo "nameserver 192.168.0.200" > /media/card/etc/resolv.conf
echo "fic-gta01" > /media/card/etc/hostname
echo "127.0.0.1 localhost.localdomain localhost fic-gta01" > /media/card/etc/hosts
echo -e "auto lo\n\
iface lo inet loopback\n\
auto usb0\n\
iface usb0 inet static\n\
address 192.168.0.202\n\
netmask 255.255.255.0\n\
network 192.168.0.0\n\
gateway 192.168.0.200\n\
up echo nameserver 192.168.0.200 >/etc/resolv.conf" > /media/card/etc/network/interfaces
echo -e "rootfs / ext3 defaults,errors=remount-ro,noatime 0 1\n\
proc /proc proc defaults 0 0\n\
tmpfs /etc/network/run tmpfs defaults,noatime 0 0\n\
tmpfs /tmp tmpfs defaults,noatime 0 0\n\
tmpfs /var/lock tmpfs defaults,noatime 0 0\n\
tmpfs /var/run tmpfs defaults,noatime 0 0\n\
tmpfs /var/tmp tmpfs defaults,noatime 0 0" > /media/card/etc/fstab
now chroot into your armel rootfs and finish the install
chroot /media/card
/debootstrap/debootstrap --second-stage
make sure your internal clock is set to the correct date because aptitude will complain if otherwise (does not work on the gta02 at the moment: "Cannot access the Hardware Clock via any known method.")
hwclock --set --date="MM/DD/YY hh:mm:ss"
install openssh so you can login remotely
echo "deb http://ftp.de.debian.org/debian sid main" > /etc/apt/sources.list
aptitude update
aptitude upgrade
aptitude install openssh-server
install and configure locales
aptitude install locales
dpkg-reconfigure locales
install udev to dynamically create /dev
aptitude install udev
set a root password
passwd
create a normal user
adduser <yournamehere>

== Get X Running ==
Now reboot and start Debian. Login with ssh and start configuring xorg:

aptitude install xorg

configure /etc/X11/xorg.conf so that it looks like this:

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
EndSection
Section "Device"
Identifier "Configured Video Device"
Driver "fbdev"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Configured Mouse"
EndSection
Start X in the first vt:
startx -- vt1

== Get touchscreen working ==
Install the tslib driver:

aptitude install xserver-xorg-input-tslib

and edit the InputDevice section in your xorg.conf

Section "InputDevice"
Identifier "Configured Mouse"
Driver "tslib"
Option "CorePointer"
Option "TslibDevice" "/dev/input/event1"
Option "Protocol" "Auto"
EndSection
calibrate your touchscreen
for gta01:
echo -67 36365 -2733100 -48253 -310 45219816 65536 > /etc/pointercal

calibration for the gta02
echo -67 38667 -4954632 -51172 121 46965312 65536 > /etc/pointercal

Note from Tkrahn:

First the above calibration for gta02 worked fine for me, but after a
apt-get update && apt-get upgrade the pointer didn't follow the stylo
anymore. I needed to overwrite /etc/udev/rules.d/50-udev.rules with
/etc/udev/udev.rules.dpkg-bak and a restart of the X server to get it
moving again. But then the pointer was very far off from the tip of
the stylo. Obviously the mode how the calculation of the position worked
has changed with the upgrade. I changed the calibration empirically.
The following /etc/pointercal parameters worked for me:

0 80000 -8000000 -80500 0 74500000 65536

(On GATA02v5 after the upgrade!)

Start X and enjoy!
startx -- vt1

== Install GDM and xfce4 ==

aptitude install gdm xfce4 xvkbd

Configure gdm so xkvbd will allow you to put in your username and password. simply add this to the end of /etc/gdm/Init/Default before exit 0 so that the three last lines look like this:

fi
sleep 20 && /usr/bin/xvkbd -xdm -compact -geometry 480x210+0+0 &
exit 0

Simply click on the focus button of xvkbd and then on the input box of GDM to input your user name and password there. On each boot gdm should start automatically now.

If you like you can also download a correctly sized Debian wallpaper I generated from the SVG source for 480x640:

wget <nowiki>http://rabenfrost.net/debian/debian-blueish-wallpaper-480x640.png</nowiki> -O /usr/share/images/desktop-base/desktop-background

== Clean Up ==
aptitude clean

== Load Additional Kernel Modules ==

These are for sound, bluetooth and USB. Use the modules archive that fits to your kernel.

wget http://rabenfrost.net/celtune/modules-2.6.24+svnr4194-r4165-r3-neo1973.tgz
tar -xf modules-2.6.24+svnr4194-r4165-r3-neo1973.tgz -C /
depmod -a
echo -e "hci_usb\n\
hidp\n\
ohci-hcd\n\
rfcomm\n\
snd-mixer-oss\n\
snd-pcm-oss\n\
snd-soc-neo1973-wm8753" > /etc/modules

Note: On the FreeRunner, the sound module (on the last line) is called snd-soc-neo1973-gta02-wm8753
[[Image:Sonata.png|480px|''Sonata on neo1973'']]
== Enable Sound ==

Now we turn our Debian into a jukebox!

aptitude install alsa-base
wget http://rabenfrost.net/celtune/alsa_state_files-working.tar.gz
tar -xf alsa_state_files-working.tar.gz -C /etc
alsactl -f /etc/alsa_state_files-working/stereoout.state restore
addgroup openmoko audio

I currently use mpd+sonata - let me know if you know another nice lightweight gtk player. Unfortunately RhythmBox is way too much for the Neo to handle - the MP3 playing stops after 20secs.

= Using a keyboard =
[[Image:Debian+frogpad.jpg|480px|''Using irssi on [[Debian]] together with the frogpad to IRC on #neo1973-germany'']]
nezza prepared a nice guide for this here: [[Frogpad]]

= Chroot installation =

If you just want to run random debian programs without completely booting to debian you can use the following minimal steps:

on desktop:

sudo debootstrap --arch armel --foreign sid sid
sudo tar cjf sid.tar.bz2 sid
nc -w3 -lp1234 < sid-arm.tar.bz2

on neo:

cd /media/card
nc 192.168.0.200 1234 | tar -x -j -f -
mount -t none -o bind /dev /media/card/sid/dev
mount -t none -o bind /proc /media/card/sid/proc
mount -t none -o bind /sys /media/card/sid/sys
mount -t none -o bind /tmp /media/card/sid/tmp
chroot /media/card/sid /deboostrap/deboostrap --second-stage
cp /etc/resolv.conf /media/card/sid
chroot /media/card/sid apt-get update
chroot /media/card/sid apt-get install mplayer
chroot /media/card/sid mplayer http://relay.slayradio.org:8000/

=For X applications / xserver on the FreeRunner=

Copy /usr/bin/Xglamo (and /usr/bin/Xfbdev) to /usr/bin in Debian from FSO/ASU/2007.2/2008.8.

Add this to your .bashrc (to tell tslib to use the correct input device):
export TSLIB_TSDEVICE=/dev/input/event1

The X server binaries are linked against version 1 of tslib, for some reason Debian calls its version 0, even though it actually is version 1. Symlink the library to the alternative name by running (as root):
ln -s /usr/lib/libts-0.0.so.0 /usr/lib/libts-1.0.so.0

We also need to change the symlink for the X server to either Xfbdev or Xglamo (this should better be handled by update-alternatives!):
cd /usr/bin && mv X X.orig && ln -s Xfbdev X
(replace Xfbdev by Xglamo if you want to use that, Xglamo is faster, but rotation still does not work correctly as of 2008-08-12).

= GPS =
{{main|TangoGPS}}

=Official Debian Port=

An official Debian port based on the FSO image is being created. First information can be found at http://wiki.debian.org/DebianOnFreeRunner. Early adopters are welcome.

[[Category:Debian]]

Talk:Manual Debian

2008-12-03T02:38:19Z

Jidanni: /* Partitions */swap

== Booting ==

=== Umount ===

I remember seeing a umount /media/card command on this page which i don't see anymore. That's needed or you will get
/dev/mmcblk0p1 is mounted; will not make a filesystem here!
Fdisk will also complain
WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
I needed to umount and rewrite the partition table in order for /dev/mmcblk0p2 to appear.

=== Partitions ===

Why don't we boot from NAND?

What's the reason for two partitions? Is it because ext2load was broken? Can we just upgrade u-boot and use one partition?

Is there any need for a swap partition?

--[[User:Brian 252|Brian 252]] 15:22, 8 August 2008 (UTC)
: [http://lists.openmoko.org/pipermail/community/2008-September/031106.html Some say] it helped. [[User:Jidanni|Jidanni]] 02:38, 3 December 2008 (UTC)

== Touch screen calibration ==

Few days ago there was added calibration for gta02. It doesn't work correctly on my freerunnuer (the mouse pointer doesn't move where I click ant the touchscreen area is about 1/3 smaller then the screen). I tried /etc/pointercal from qtopia and openmoko but it is the same as with parameters from this wiki. Has somebody a tip how to fix this?

--[[User:Jakubzeman|Jakubzeman]] 07:42, 8 August 2008 (UTC)

I'm using lenny. Oh and if some one wants to see if they can get a debian based kernel / merge / get some more modules from debian / general modules into a kernel for other hardware (such as a rt73 chipset wireless card that would be great :) ) [[User:Dbmoodb|Dbmoodb]] 08:09, 8 August 2008 (UTC)

Thanks for suggestion. I'll try it (and I'll report if I'm successful or not).
--[[User:Jakubzeman|Jakubzeman]] 08:56, 8 August 2008 (UTC)

== Sound ==

http://tehinterweb.com/freerunner/alsa.state.tgz --[[User:Dbmoodb|Dbmoodb]] 13:55, 21 August 2008 (UTC) (if it doesn't work for you... try these alsa states or the ones posted below from openmoko.org...)

If the sound card is configured properly but there's no sound coming out of the Freerunner, it most likely helps to restore an appropriate statefile from the tgz above which are also available on the [[Openmoko svn]] (/trunk/src/target/audio/om-gta0*).

For simple sound output to the internal stereo speakers, do:
alsactl -f /path/to/statefiles/stereoout.state restore
--[[User:Tanuva|Tanuva]] 12:59, 21 August 2008 (UTC)

==debugging fso ==
The following are taken instructions are taken from lindi on irc.
/etc/init.d/frameworkd stop
/etc/init.d/fso-frameworkd stop
add 'log_level = DEBUG' to '[ogsmd]' in
/etc/frameworkd.conf
run "frameworkd" and watch the output
--[[User:Dbmoodb|Dbmoodb]] 08:34, 22 August 2008 (UTC)

I found that i actually had to do the following ...
/etc/init.d/fso-frameworkd stop
/etc/init.d/x11-common stop
/etc/init.d/openmoko-fso restart
then go frameworkd

== Problems Making This Work ==

I tried the instructions for loading Debian on my Freerunning and was disappointed to find it didnt work for me. I tried it twice, once with an Ext2 partition on the SDCARD and once with out, about a week ago, both gave exactly the same result. Its a very slow process too. The result when booting is that the phone brings up the openmoko logo , then a completly white screen and then goes back to the openmoko logo, it continues doing this ad-infinitum. It seems like the uboot image is wrong (=invalid) but I cant see how to fix this. Its still possible to boot original OS but via NOR screen. (Boot from card is the default now.)

Is there no chance of a binary debian image or starter image that can go into flash? I have flashed my phone many times with kernel and jffs2 images and although described as a "major" thing to do, it has always worked so far. Ive looked everywhere for a Debian image and cannot find.

Any comments appreciated.

== The above problem can be resolved as follows ==

I had the same problem, and got the hint from Julian Köpke, who suggested the following and it works.

Your uboot version is too old. You can get the newest
[http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin uboot image]
and then follow [http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader_to_the_NAND these instructions]
--[[User:Nagarjuna|Nagarjuna]] 10:14, 13 September 2008 (UTC)

Jokes

2008-12-03T01:48:41Z

Jidanni: minimal <DL>

'''Q: Why did OM cross the road?'''

A: To get to another toolkit :)

'''Q: How many OM devs does it take to change a lightbulb?'''

A: Well first we need to abandon the old lightbulb holder because at a later date we may not be able to plug a floodlight in, bring in a new lightbulb holder and adapt it to multiple floodlights, meanwhile the engineering team has realized that this will only run green floodlights and has started rewiring the whole house.. :) The burnt out lightbulb is due to be fixed at a later date :)

'''Q: What is the difference between a professional photographer and OM user?'''

A: The OM user has to flash more often :)

'''Q: Why did the OM newbie log onto #openmoko?'''

A: Because they had not read:
*# the wiki, and
*# the topic
As then they would know you slide your finder up on the keyboard to get the numbers to enter your sim pin.

'''Q: What's the difference between an iphone and a freerunner?'''

A: One works but takes away your freedom, the other is free but needs your work

Knock, Knock
Who's There?
A Neo User
A Neo User

'''Q: What did the Neo say to the insomniac?'''

A: At least when you go to sleep you know you'll wake up!

'''Ancient chinese proverb:''' "Neo owner is man carrying wall charger"

'''Q: What's the difference between a brick and a freerunner?'''

A: A brick isn't designed to make phone calls.

'''OM2008.9 and FSO walk into a bar.'''

"How are you? How are you?" asks FSO.

"Buzzzzzzz" says OM2008.9

'''Q: How to switch off this phone?'''

A: You have to write program :)

'''IRC quotes:'''

[16:03] <jadams_> does 2008.8 support the neo yet?

'''Release announcements:'''
* New distribution: [http://scap.linuxtogo.org/files/2c3159f3e1a2622fd56fe29d2f222d9c.png OpenmokoMe Millenium Edition] !
* New hardware: [http://notnews.today.com/2008/09/22/free-software-foundation-announces-gnuphone/ the GnuPhone].


;Q What if somebody important calls?:A Err..

Jokes

2008-12-03T01:46:31Z

Jidanni: best formatting

Jokes

2008-12-03T01:40:49Z

Jidanni: what If somebody important calls

Qi

2008-11-28T05:29:08Z

Jidanni: ==Enabling console messages==

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

==Concept==
Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

==Partitions==
Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card. (Note: Qi expects the / (root) filesystem to be on the same partition as /boot!) It
tries the it will try first, second and then third partitions. Failing to find that, it will boot from the
kernel in NAND (if the kernel works of course, see below). Failing to find that, it will blink the blue Power
LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==
The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
(look at your dmesg output for the CPU to pick the right s3c* version.)

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

==Enabling console messages==
[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
console=tty0 loglevel=8
and you'll see the messages on boot. If it's NAND right now you need to edit the default commandline in Qi for gta02.

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* Qi often doesn't want to resume after suspend.

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]

EFL Documentation

2008-11-28T04:00:19Z

Jidanni: say what EFL means

This is a collection of links to possibly useful [http://en.wikipedia.org/wiki/Enlightenment_Foundation_Libraries EFL] documentation.

<ul>
<li>Example apps for the Python bindings in E17 svn 
https://svn.enlightenment.org/svn/e/trunk/BINDINGS/python/</li>
<li>Python EFL API documentation 
http://staff.get-e.org/~barbieri/python-efl-api/</li>
<li>"Introduction To The EFL" 
http://homepages.pathfinder.gr/kazanaki/contrib/</li>
<li>"Building Interfaces With Edje" 
http://www.cuddletech.com/edje/docs/html/edje_book.html</li>
<li>And, of course, the E17 wiki 
http://wiki.enlightenment.org/index.php/Main_Page</li>
<li>And, officially, the E17 docs 
http://docs.enlightenment.org/</li>
</ul>

[[Category:Application Developer]]

Wiki Issues

2008-11-28T01:27:56Z

Jidanni: whitespace problem fixed

If you think something is wrong with a Wiki page, please fix it. If the problem is larger with this Wiki in general, please add your thoughts on this page and mail the openmoko [http://lists.openmoko.org/mailman/listinfo/documentation documentation mailing list]. You may just want to read existing proposals and put your vote on them, [[Wiki Maintainers]] will appreciate. [[Wiki Maintenance Agenda]].

When adding an issue please

* Provide a reason
* Provide your name as vote for the action to be taken (you can automatically enter your username by typing "
<nowiki>~~~</nowiki> ")

{{Warning|Comments without name might be deleted without consideration. We may need to ask for more information before implementing a proposal. Thanks for understanding.}}

Accepted and implemented requests should be deleted. Rejected requests should be moved to the bottom of the page to avoid requesting them again.

==Wiki Pages==

I think that we should use specific "editor's notes templates" rather that nominate individual pages here. We can make automatic list of pages using a given template by having a Category:X tag inside the template. See for example the [[:Category:ToDo]] . [[User:MinhHaDuong|MinhHaDuong]] 09:44, 7 October 2008 (UTC)

===Pages capable of development===
* [[Openmoko:Community Portal]]
* [[AR6K]] (Needs more info)
* [[GTA02 partitions]]: seems to be about the GTA01; could someone with a GTA02 please correct the partition sizes and names?
* [[Advanced_End-user]], [[Basic_End-user]], [[System_Developer]]: These are not up to the standard we set for List Pages on [[Openmoko_Wiki_Editing_Guidelines#List_pages]] [[User:Kempelen|Kempelen]]

===Redundant Pages===
* There are several pages concerning Openmoko compatible service providers:
** [[Carriers]], most up-to-date, confirmed service providers.
*** [[Carriers/ATT]]
*** [[Carriers/TMobile]]
*** [[Carriers/Fido]]
*** [[Carriers/Rogers]]
** [[Neo1973 compatible cellphone providers]]

*I suggest merging the editing help pages:
**[[Help:Editing]]
**[[Edit Wiki]]

*pages about GPS:
**[[Hardware:AGPS]]
**[[Gpsd]]
**[[Neo 1973 GPS]]
**[[Neo FreeRunner GPS]]

*applications:
**[[Available Packages]]
**[[Applications]]
**[[Applications directory]]
**[[Om 2007.2 Applications]]

===Tidy up===
* [[Wishlist:Text Input]] - tidy up/sort, give short feedback to each method
* [[Booting_from_SD]] - tidy up and a rewrite

=== Pages proposed for deletion ===

'''Please help cleaning these''': Check if there is a red (nonexisting) link in this table, click it, click "What links here" in the toolbox and '''update the broken links'''. When done, remove the deleted entry from this table.

{| border=1 cellspacing=0
!Page
!Reason
!Yes kill it votes
!No keep it votes
|-
| Nothing is propsed for deletion at the moment || || ||
|}

See also: [[:Category:Candidates for speedy deletion]]

=== Pages that especially need work ===

* [[Special:Lonelypages]] - Orphaned pages
* [[Special:DoubleRedirects]] - Pages that redirect to a redirected page
* [[Special:Popularpages]] - Pages that get viewed a lot
* [[Special:Ancientpages]] - Old pages
* [[Special:Newpages]] - New pages
* [[Special:Wantedpages]] - Wanted pages
* [[Special:Uncategorizedpages]]
* [[Special:Shortpages]] - Informationally light pages
* [[Special:BrokenRedirects]] - Broken redirects

=== Application pages ===

Maturity level ideas from the documentation list copied by [[User:Kempelen|Kempelen]] 19:05, 1 October 2008 (UTC):

* It might be nice to have a single word stating the code maturity, perhaps only 3 simple options like prototype, functional, mature
* Why not stick with pre-alpha, alpha, beta, stable, mature

Decision postponed. :-) (Feel free to vote here anyway.)

== Categories ==

{{Main|:Category talk:Categories}}

== CSS ==

We have discussed design on the mailing list, with the conclusion that revising was not a big priority. However, the wiki should be skinnable from user-space by editing : http://wiki.openmoko.org/wiki/MediaWiki:Common.css . And for development, each user can have his/her own CSS to eat his own dogfood. But I can't seem to make this feature work here.
Reference: http://en.wikipedia.org/wiki/Help:Monobook
[[User:MinhHaDuong|MinhHaDuong]] 12:26, 12 September 2008 (UTC).

* The gutter is too wide
* Too much footer's padding
* Could shave 1 or 2 em of vertical space in the header
* The tabbed navigation layout is non-standard (no framing effect)
* The search box is below the fold (depends on window height of course)
* The toolbox (bottom left) has no border
* Mediawiki's user personal toolbox is prohibited
* Too many links in the navbar that belongs to the home page but not to every page

== Portals ==

We should explore another wiki organization tool: [http://en.wikipedia.org/wiki/Portal:Contents/Portals portals]. A portal is an introductory page for a given topic. It complements the main article of the subject by introducing the reader to key articles, images, and categories that further describe the subject. Portals also help editors find related projects and things they can do to help. [[User:MinhHaDuong|MinhHaDuong]] 13:53, 20 September 2008 (UTC)

== Navigation templates ==

(FYI Description moved to [[Openmoko_Wiki_Editing_Guidelines#Navigation_templates]], [[User:Kempelen|Kempelen]])

* The [[Distributions]] page feature a non-templated navigation box
* We should name these templates distinctly. I suggest using a prefix like "NavBox:".
* Visual design is by hand (not CSS), and not beautiful
* Need to test positioning at bottom of article.

'''References'''

http://en.wikipedia.org/wiki/Wikipedia:Navigation_templates
http://en.wikipedia.org/wiki/Wikipedia:Categories,_lists,_and_series_boxes

[http://lists.openmoko.org/pipermail/documentation/2008-August/000405.html First discussion in the mailing list] (Note: in the middle of a thread about left navboxes)

* '''Yes votes''': [[User:Kempelen|Kempelen]] (For real wikipedia like navigation templates at the bottom, not at TOC position, we should move this section to editing guidelines as soon as template implementation improves a bit. Do not delete this please!)

== DolfjeBot1 proposals ==
Their is a bot on the openmoko wiki that's controlled by [[User:Dolfje]]. If you have tasks for the bot, please put them [[User:DolfjeBot1|here]].
A request has been made to tag DolfjeBot1 user account with the 'bot' flag. [[Special:Listusers/bureaucrat| Here is the lists of users]] with permissions at the necessary `bureaucrat' level.

==Wiki engine issues==

=== Disappearing Pre-formatting ===
There is an issue with pre-formatting disappearing when people edit. See for instance recent edits here:

http://wiki.openmoko.org/index.php?title=Accelerometer_data_retrieval&diff=59334&oldid=55556

Actually I thing it's whitespace in general that is lost since python/ruby code is also messed up.
I have confirmed that this happens cross browser (both firefox3 and opera), but not on all pages, and not for all people.

[[User:Gromgull|Gromgull]] 10:47, 9 November 2008 (UTC)

Yes, it is driving me bananas and must me due to some
[[Special:Version#Hooks|hook]] the maintainers have added.

<pre>
In standard MediaWiki, a mere space at the beginning of these lines
will produce this box. But no, here on this wiki, one needs

<nowiki><pre></nowiki> , and your spaces get eaten.
The problem can be isolated as even returning mangled code in the edit box when you hit
the preview button. Never on real MediaWiki has anything dared to return a mangled edit box before.
Indeed the contents of this very paragraph have been jumbled by it. I have no control. Indeed, do
you see that gap above? It grows with each edit.
</pre>
On the [http://jidanni.org/comp/index.html wikis I maintain], I never go hog-wild adding too many hooks.

This bug got me. I managed to fix the page I accidentally broke, but apparently it causes the preformatted text to slowly sink into ordinary text with each edit, making the
wiki less readable, for example see: http://wiki.openmoko.org/index.php?title=GPRS_FSO&oldid=55571 and http://wiki.openmoko.org/index.php?title=GPRS_FSO .
This should be fixed ASAP, as it makes the quality of the wiki do down. :-( [[User:Zub|zub]] 00:47, 18 November 2008 (UTC)

[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.documentation/7 Whitespace problem fixed]. [[User:Jidanni|Jidanni]] 01:27, 28 November 2008 (UTC)
====Emergency: eating categories off the bottom of pages====
=====Proof of Category eating=====
...Oh, the categories only disappear temporarily, due to http://www.mediawiki.org/wiki/Extension:SelectCategoryTagCloud .
OK, sorry for the alarm. [[User:Jidanni|Jidanni]] 04:08, 16 November 2008 (UTC)
----

Can we please install/fix the following features for this wiki:
* '''Math''' - the Tex math markup does not work currently. Test:
** <math> z =\left (1-\left(\frac{P_{ind}}{101.325}\right)^{0.190263} \right ) \times \frac{87.828}{0.00198122} </math>
** <math> P_{ind} </math>
* [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi '''Syntax''' Highlighting - makes code much more readable]
* [http://www.mediawiki.org/wiki/Extension:GraphViz GraphViz] works with the commonly known dot language - it allows us to draw '''graphs''' using easy markup.
* [http://www.mediawiki.org/wiki/Extension:AnyWikiDraw AnyWikiDraw] allows us to draw svg '''diagrams''' directly on the wiki page.
* Make '''visited links''' a different color.

== Change Sitename ==

The name of this wiki is currently "Openmoko". I think it should be "Openmoko Wiki" for the following reasons:

* The other parts of this site (Planet, Projects, Docs) have similar names
* Media Wiki automatically creates a [http://www.mediawiki.org/wiki/Manual:Namespace namespace] for the Sitename (currently "Openmoko"). This means that content of pages beginning with "Openmoko:" cannot be found through the normal search function of this wiki. (At the moment there are five pages of this kind: [[Openmoko:About]], [[Openmoko:Community Portal]], [[Openmoko:Current events]], [[Openmoko:Searching]], [[Openmoko:Privacy policy]])--[[User:Marko Knöbl|Marko Knöbl]] 18:33, 8 August 2008 (UTC)

'''Yes votes''': [[User:Marko Knöbl|Marko Knöbl]], [[User:MinhHaDuong|Minh]]

'''No votes''':

::OpenmokoIT still do some research now. [[User:Coolcat|coolcat]]

::Then fix the search function (by restoring the standard MediaWiki search function). Anyway they are [[Special:Allpages/Openmoko:]]. Anyway, any links like [[Special:Allpages/Openmoko:]] will break, unless you use [[Special:Allpages/Project:]]. Furthermore, the longer the name of the Project ($wgSitename) becomes, the longer the UTF-8 translations of it will become, and as e.g., for Chinese UTF-8 at 3*3=9 ASCII %XX%XX%XX per character, you'll end up with mile long URLs before long, that is if one day the site becomes fully translated. [[User:Jidanni|Jidanni]] 01:04, 22 November 2008 (UTC)

== Organize translations ==

I suggest moving the translations to sub-wikis, like the way wikipedia does it. Currently all translations show up in searches and under category-lists. --[[User:Johndoesacc|Johndoesacc]] 12:03, 25 August 2008 (UTC)

+1. See issues and solutions for a multilingual mediawiki at:
http://www.mediawiki.org/wiki/Multilingual_MediaWiki
Also, the correspondence between translation should be maintained with tags:
http://en.wikipedia.org/wiki/Help:Interlanguage_links
The request [http://lists.openmoko.org/pipermail/documentation/2008-September/000557.html has been heard] but maybe not in the right places. What is the best operational frequency to ping the hosting engineers for that ? [[User:MinhHaDuong|MinhHaDuong]] 13:02, 10 September 2008 (UTC)

After discussion on the Documentation ML, sub-wikis are out. We want to try namespaces. [[User:MinhHaDuong|MinhHaDuong]] 09:31, 7 October 2008 (UTC)

== Downloads ==

=== Symlinks in download directories ===

This is not strictly Wiki issue, but discussed on the documentation list as being a serious usability disadvantage. Symlinks and .tar.gz files should be removed from the release directories because they confuse users. Ref: [http://lists.openmoko.org/pipermail/documentation/2008-September/000808.html]

=== Improve README.html ===

Example: http://downloads.openmoko.org/releases/Om2008.9/README.html

It should at least link to: [[Om_2008.9_Update#Download_and_Flashing]]

== Rejected requests ==

When a requested Wiki Issue is voted for not to be done, it must be moved here, to make sure it won't get continously requested again.

* '''Don't translate the wiki - rejected''' proposed by [[User:Minime|Minime]] August 2007, moved to rejected by [[User:Kempelen|Kempelen]] August 2008: the Documentation Team looks to support the idea.
* '''Use namespaces to separate user-oriented and developper-oriented content'''. Assuming the default namespace is user-oriented that would exclude developper-oriented pages from searches (unless the user ticks the box, but who does ?). And it can't be done purely in the wiki, it needs admin time. Better to use categories and a prefix in the page name (like BlendeWiki). [[:User:MinhHaDuong|MinhHaDuong]]
* '''Use category pages instead List Pages''' Good list pages are allowed and encouraged, as the documentation team today agreed on the mailing list. [[User:Kempelen|Kempelen]] 21:27, 30 August 2008 (UTC)

[[Category:Wiki Editing]]

Why Openmoko

2008-11-27T22:45:40Z

Jidanni: add reality check

{{Languages|Why_Openmoko}}

This article discusses the pros and cons of various operating systems for the mobile platform, and tells us why Openmoko is the true ‘open’ platform.

There are many mobile platforms that exist on this planet today. The situation is very similar to the desktop segment, where we have operating systems like GNU/Linux, BSD, Mac OS X, Windows and a few others. To me, the fact that Linux is an open source model makes it a much better OS. We also have great mobile operating systems like Symbian, Windows Mobile Platform and Linux. But none of these are really ‘open’. Surprised to see Linux in this list? Linux as a mobile OS comes in different shapes and sizes that are not very compatible with each other, as there are many different implementations of the platform. There are no common APIs available for developers to build on top of. Examples include implementations from Motorola and MontaVista. At least, this is not the case with proprietary OSs such as Symbian and Windows Mobile. They provide abundant information to aid third-party programmers to build on their platform.

Let us now set aside all this for a while and concentrate on a Linux-based mobile platform project called Openmoko—a project that combines the true essence of open source with a rich application-programming interface. Openmoko is a true conversion of the desktop Linux into mobile Linux, which doesn’t bring in any non-standard or hidden aspects. It was built using standard X-server, GTK, ALSA, Dbus and so on. The beauty is that even the hardware platform is as open as the software platform. Openmoko makes use of a standard platform to make the mobile environment complete. Even the circuit-board hackers will find Openmoko a dream come true!

==What is wrong with the others? ==

Let’s now take a look at what is seriously wrong.

===Symbian OS===

First up is the Symbian OS, considered the Windows of the mobile world. More than 75 percent of the smart phones sold today, run Symbian, and it’s perhaps the most developed mobile operating system, backed by such industry leaders as Nokia, Motorola, Sony and Lenovo. But there are a few things I don’t like about Symbian, which I’m listing below.

*'''A proprietary OS:''' Symbian is a closed source OS developed by Symbian Ltd, and perhaps the worst thing about it is that it uses open programs like GCC, Java, Perl and many others in its SDK, but doesn’t share its code base or support any open source OS for its application development.

*'''A restricted development environment:''' Symbian only supports Windows for application development. There is no official SDK that can be used with Linux or Mac OSX. What is ironic is that most of Symbian’s SDK components will fail without the supporting open source programs.

*'''Poor backward compatibility:''' Every new version of the OS breaks the code. You can’t just recompile the code and run the application on a new platform. You need to re-write the whole application to support the code.

*'''High-end systems requirements:''' Symbian phones require a pretty decent hardware configuration to run properly. Even if you do have that, you may come across messages like “Out of Memory”. I am sure that many of our readers using Nokia smart phones are already aware of this.

*'''Difficult to program:''' Even though it offers a rich set of APIs, these are difficult to program. You may say that Symbian supports many programming languages, but remember — if you really want to program, you must know that Symbian C++ is very different from the standard C++, and hence has a very steep learning curve.

*'''Confused UI platforms:''' Symbian uses two confusing and mutually incompatible UI platforms— namely, S60 (formerly Series 60) and User Interface Quartz (UIQ). For developers, this means that even though you are developing for Symbian, you need to learn UI specific details in order to be up and running.

*'''Poor developer support:''' Starting with Symbian 9, the company has started punishing third-party developers. Most of the phone features are open only to subscribers of Symbian Signed. If you are not a member of the Symbian Signed programme, then you won’t be able to make use of many core features of the OS.

*'''Version lock:''' The OS doesn’t support OS upgradation—if your machine has got Symbian 9.1, it will remain as it is as long as you use it. You won’t be able to upgrade it to a later version of the same OS. So you are bound to live in the Stone Age unless you spend a fortune on getting a new device with a newer OS.

*'''Symbian is a mobile-only OS:''' You can’t use your existing skills to build on it. Or, in other words, you can’t use your Symbian skills anywhere else.

===Windows Mobile===

Considering Symbian drawbacks, Symbian is not exactly like Windows on the desktop, even though it is doing quite well. Windows is better than Symbian in some ways. It has got better developer support and has a plethora of developer documentation available. Visual Studio is an excellent IDE for it. But there are a few things I don’t like about Windows Mobile too.

*'''Microsoft vendor lock:''' Nothing is worse than a vendor lock-in, where the keys of the locks are with Microsoft.
*'''Closed source:''' I don’t need to stress on this, do I?
*'''Microsoft’s partiality:''' When it comes to a Microsoft product, there is always a reasonable amount of partiality. One example is in Windows Mobile 6, where some of the improvements to email and the calendar application require that you have Exchange Server 2007. The situation is exactly like that on the desktop, where you can’t have DX 10 if you don’t have Vista. Remember all those anti-trust cases that Microsoft is facing?
*'''Poor API support:''' Not all the Windows APIs are available for third party use. You may need to sign an NDA with Microsoft before you want to fully unleash the OS’s potential.

===iPhone===
Apple's iPhone is very popular, we must take that into consideration as well. iPhone is not exactly a mobile application platform – rather, it is a product name. And, unfortunately, as of today, there is nothing much in store for the developers and end users. Let’s list the disadvantages here as well:

* '''Apple’s insane vendor lock:''' This phone is locked in to Apple and the cellular company, and you as the user, end up paying both.

==Why Openmoko is the best==
Linux is the best way to program. All that still stands true, as Openmoko is all about programming on Linux itself. And here’s why I think so:

* '''Open source:''' It is truly open source—not only in terms of software, but also in terms of hardware. You get to see all the nuts and bolts behind your excellent phone.
* '''Built from open source:''' Openmoko is an amazing collection of already popular open source programs to build a mobile development platform.
* '''Cross-platform development:''' Moving forward, Openmoko SDK will support Windows and Mac too, thus giving you the option to develop on your choice of platform.
* '''Easy application development:''' Since it makes use of popular technologies, it’s pretty easy to get up and running with Openmoko in a very short period of time. All Linux programmers will feel at home, as Openmoko makes use of popular open source components like GTK, X server, ALSA and so on.
* '''Low on hardware requirements:''' It doesn’t require a very high-end configuration to run on.
* '''Great developer support:''' Even though the project is in its infancy, it already has got great community support. Apart from this, all the components used in building Openmoko have their own communities. So, there may already be someone to help you out.
* '''A very rich API:''' Openmoko has got a very rich set of APIs. A few have been developed exclusively for Openmoko, while the others are simply derived from other projects. Openmoko enables you to use your existing skill set to create the phone applications that you want to.

==The Openmoko Architecture==
The Openmoko architecture is simple, yet very powerful. Most of it is based on already-available open source technologies. However, new technologies have also been developed exclusively for the platform. Openmoko consists of the following major components:
[[Image:Software1.jpg]]

* '''Linux kernel 2.6 and associated device drivers:''' The project makes use of the vanilla kernel 2.6 series, patched against Openmoko-specific patches. The patch set includes additional support for various embedded devices like USB, SD, touch screen, and communication drivers. All these drivers reside in the kernel space, and are loaded at boot time.
* '''Linux Core (or system) services:'''

** '''udev:''' It acts as the device manger and maintains all the device nodes in a pseudo /dev filesystem. udev provides a standard way for device components to interact.
** '''blueZ:''' It is the official LinuxBluetooth stack that is responsible for all Bluetooth related activities in Openmoko.
** '''Dbus:''' This provides an IPC (inter-process communication) framework. In other words, Dbus allows applications to talk to each other.
** '''GSM:''' It consists of GSM (the core GSM module), GSMd (a daemon to manage the GSM backend) and libgsm (an API to communicate with the GSM subsystem).
** '''GPS:''' It consists of GPS (a core GPS module) and GPSd (a daemon to manage the GPS backend).

* '''The user interface (UI)'''
**'''kdrive:''' It is the thin X server for embedded platforms, which runs directly on a frame-buffer device and supports OpenGL.
**'''matchbox:''' It is a window manager for embedded platforms. Matchbox has been very popular with its recent adoption in Nokia’s Linux tablet and the One Laptop Per Child project.
**'''GTK:''' This cross-platform widget toolkit is popular due to its truly open source nature and wide cross-platform support. GTK sits behind the popular desktop environment GNOME. UPDATE: Qt is now supported widget.
**'''ALSA:''' The Advanced Linux Sound Architecture (ALSA) provides the audio functionality. ALSA is already very popular in Linux systems and is now part of the standard kernel.
**'''Qtopia:''' It is the robust and commercial-grade mobile phone and PDA platform from Trolltech, and arguably much more than just a GUI toolkit.
* '''The application framework:'''
**'''Core (libmokocore):''' This provides the core functionality to the framework, such as the switching device, reading/ writing data, application-toapplication signalling, etc. It makes use of the Dbus and Gconf packages.
**'''.Net (libmokonet):''' It provides the core networking functionality to the framework. It makes use of libgsm, bluez-lib and libgps.
**'''UI (libmokoui):''' It provides the UI programming capabilities to the platform and makes use of GTK and ALSA (for applications interacting with audio devices). The standard GTK has been customised to provide a rich mobile application-development experience.
**'''PIM (libmokopim):''' Provides the core PIM (personal information management) capabilities. It makes use of the embedded Evolution data server.
* '''Applications:'''
**'''X11 applications:''' Standard X11 applications linked to libX11.
**'''Finger applications:''' Includes the dialler, menu, media player, etc.
**'''Stylus applications:''' Includes contacts, messages, search applications, etc.
**'''Third-party applications:''' Various heavy-duty applications like Web browsers, instant messaging applications, etc.

Subsequent to this quick introduction to the upcoming Openmoko platform, in forthcoming articles I’ll show you how to build and run Openmoko applications. The experience is like hacking the world’s best phone environment at your workbench—and yes, nobody is going to sue you! Dont forget to post in your comments at kunaldeo at gmail.com

--[[User:Kunaldeo|Kunaldeo]] 10:54, 30 June 2008 (UTC)

==But what if somebody important calls?==
The reader should still be aware that Openmoko is not the fully polished product
as some of the other phones on the market. However, with your help...

[[Category:Distributions]]

Flashing the Neo FreeRunner

2008-11-27T22:28:36Z

Jidanni: see also Qi

{{Languages|Flashing_the_Neo_FreeRunner}}
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.

Usually it is not necessary to re-write the the NOR flash. Instructions to do so is here: [[Flashing NOR]].

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

'''MacOS X:''' [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

'''Linux:''' http://downloads.openmoko.org/daily/dfu-util

Make sure it is executable by setting the permissions with this command: chmod a+x dfu-util

'''Linux 64-bit:''' You need 64-bit version of dfu-util, which usually can be found in your distribution repository.
If your destribution does not provide 64-bit dfu-util, or it consistently fails with a "-62" error, you have two ways to go:
# Seek for 32-bit machine and do flashing form it.
# Use 32-bit chroot (on amd64 debian). Worked for me --[[User:Bubak|Bubak]] 16:54, 4 September 2008 (UTC).

'''Windows:''' http://projects.openmoko.org/frs/?group_id=166&release_id=162

See additional driver installation instructions for Windows at [[Dfu-util-windows]]

'''''Note:''' While there has been some limited success reported using dfu-util from within a Virtual Machine (such as VMware), in general it is not possible to use dfu-util in this fashion. You must use dfu-util on an operating system that has direct access to the physical USB device hardware.''

=== GUI for DFU-util ===

Optionally, you may want to use this GUI tool instead the dfu-util commands: [[NeoTool]]

=== 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 (uImage) 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 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:

<pre>dfu-util -l</pre>

If you get error messages from the dfu-util command then try again. Often it works on the second try.

dfu-util uses the DeviceFirmwareUpgrade protocol, and may list more than one device. If so, try unplugging the other device (e.g. a USB mouse) or using the -d switch to tell dfu-util which device it should talk to, as described at the relevant bug report [http://docs.openmoko.org/trac/ticket/2039].

Also, please remember to execute the dfu-util command with sufficient privileges (ie. root) -- you will need complete control over the usb bus.

== 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 dfu-util is available here : [[Dfu-util]]

GUI frontend for dfu-util (and more): [[NeoTool]]

== Flashing the Kernel ==

Note: The phone needs to be in the U-boot bootup menu for this to work.
Get there by holding down the aux button while powering up the device.

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 may fail with an error -110. This indicates that the kernel is too big for the default kernel partition. uboot can be used to change the size of the default partitions on the device. It may also mean that you are trying to put the wrong thing in the kernel space.

== 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, bz2, .zip, tar, tar.gz or .tgz extension) you have to uncompress it first.

The command format is

<pre>
dfu-util -a rootfs -R -D ''rootfs_filename.jffs2''
</pre>

where ''rootfs_filename.jffs2'' is the name of the file containing the root file system.

The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing.

When flashing succeeds the following will be shown:

<pre>
status(0) = No error condition is present
Done!
</pre>

== Flashing the boot loader to the NAND==

{{Note|In most cases you don't need to flash your bootloader. Flash it only if you want to update for a specific feature or due to a specific problem.}}

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

=== Verifying boot-loader version ===




(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).

== A command line script to simplify dfu-util ==

DFUScript developed to assist users who have multiple devices in using dfu-util via the command line. Information on where to download and use DFUScript can be found on [[DFUScript]]

==See also==
*[[Qi]] alternative to uboot

[[Category:Flashing Openmoko| ]]

FreeRunner GPS antenna repair SOP

2008-11-27T03:13:43Z

Jidanni: fixed sloppy links

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

'''WARNING''' - Please check the SD-Card interfering Problem first! This should solve the [[GPS Problems]] for most people:
[[FreeRunner Hardware Issues#GPS_Slow_TTFF]]

'''WARNING''' - Only attempt this repair if you are sure it will correct a GPS problem.

'''WARNING''' - Do not use arcing cold heat soldering tools as the high current could damage sensitive electronics.

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

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

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

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

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

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

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

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

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

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

[[Category:Hardware]]
[[Category:Neo FreeRunner Hardware]]
[[Category:GPS]]

Booting the Neo FreeRunner from SD via U-Boot

2008-11-27T02:29:04Z

Jidanni: note Qi

{{Languages}}
This page explains how to boot a FreeRunner from the [[Supported_microSD_cards|(micro-)SD card]] rather than from the built-in NAND flash memory. The SD card shares a bus with the GPU, so it may not perform as well, but it is another option.

{{Warning | Booting from SDHC may cause problems at this time (see below).}}

== Booting from SDHC / suspend problems ==

First, a warning. There is a longstanding bug, probably somewhere in the Linux kernel, that tends to eat the partition table of high-capacity SD cards when the system suspends. This is ticket [https://docs.openmoko.org/trac/ticket/1802 #1802]. See [http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/19154/focus=19281| this thread] for explanation of the partition table removal on suspend and maybe other problems related to using high capacity SD cards. A safety net is to keep a written copy of the partition table on paper, just in case one needs to recreate it.

== How it Works ==

On the Neo, [[u-boot]] performs a similar role to the 'grub' bootloader on a PC. U-boot loads a kernel image into memory and then passes a list of parameters to the kernel. These parameters specify, among other things, the device on which the root filesystem is located.

As the kernel boots, it initializes the hardware and then mounts the root filesystem. The kernel then runs "/sbin/init", which handles the rest of the boot-up sequence (such as displaying the splash screen and progress bar).

This sequence is the same whether the device is booting from built-in Flash or from the SD card. The differences are how the kernel is loaded, and which device is mounted as the root filesystem.

The following sections provide additional details.

=== Menu Entries ===

U-boot menu entries are defined by environment variables named "menu_X" (where X is a number). The value of the environment variable is a string "<label>:<commands>", where <label> is the text shown on the screen, and <commands> is a sequence of u-boot commands (delimited by ';' characters) to be executed when the menu item is selected. When entering a string of commands, the ';' and '$' characters must be backslash-escaped ("\;" and "\$").

=== Loading the Kernel ===

A pair of u-boot commands must be used to load the kernel from SD. First is "mmcinit", which will cause u-boot to detect the card. Next is a command to load a file into memory - either "fatload" or "ext2load" depending on whether the kernel is on a FAT filesytem or an ext2/ext3 filesystem.

The command syntax is:

fatload mmc 1: 0x32000000 <filepath>
ext2load mmc 1: 0x32000000 <filepath>

where is the partition number, and <filepath> is the path to the file that is to be loaded.

{{Note| The "ext2load" command is broken on u-boot binary earlier than "20080723", including the one shipped with the first batch of FreeRunners, are affected by bug [http://docs.openmoko.org/trac/ticket/799 #799]. If you update your U-Boot and kernel packages you can use direct ext2 / 3 boot all in one partition.}}

{{Warning | Be careful when updating u-boot on a Neo1973 as there is a risk of bricking the device (unless you have a debug board). This is not an issue for the FreeRunner as it has a protected copy of u-boot in the NOR flash }}

{{Note| U-Boot supports SDHC protocol on the FreeRunner only: on the Neo1973, u-boot is unable to access SDHC cards (4G or larger). The kernel does have SDHC support on Neo1973, so it is possible to have the root filesystem on SDHC and the kernel on NAND flash to work around it. }}

=== Root Filesystem Parameters ===

The contents of the "bootargs" environment variable are passed to the kernel. Bootargs is a space-delimited list of "name=value" definitions. The items relevant to SD-booting are "root", "rootfstype", and "rootdelay".

For example, the following parameters would tell the kernel to mount the third partition of the SD-card as an ext3 filesystem:

root=/dev/mmcblk0p3 rootfstype=ext3 rootdelay=5

The "rootdelay" parameter allows time for the card to be properly initialized before it is accessed.

Note that the kernel must have built-in support (i.e. not a module) for the filesystem specified in "rootfstype". The default Openmoko kernel configs as of [http://git.openmoko.org/?p=kernel.git;a=commit;h=642cbda5f3b7e7a61512426e1d30a41ab4691123| 2008-07-17] have built-in support for both ext2 and ext3. You can check the available filesystems with the Linux command

less /proc/filesystems

It is not possible to use VFAT for the root filesystem.

==== ext2 vs. ext3 ====

Opinion is divided on whether it is better to use ext2 or ext3 for the root filesystem. Ext3 in general is a superior choice, because it is a journalled filesystem and so does not require a long 'fsck' (file system check) after an unclean shutdown. However, if used on a flash device that does not support wear-leveling then ext3 may cause premature wear on the blocks of the card where the journal is stored. SD cards are supposed to support wear leveling, but this can not be guaranteed for all vendors.

== Acquiring a tarfile rootfs ==

There are two ways of acquiring an rootfs image as a tar archive. You can either build it on your own using the OpenEmbedded Distribution. Or download it from the openmoko buildhost.

=== Possibility 1: Downloading the rootfs/kernel tar from the Openmoko buildhost ===

Choose and find the rootfs/kernel combo you would like to install at [[Latest Images]].

=== Possibility 2: Building a tarfile distribution using OpenEmbedded ===

Another possibility to get a tar archive of your rootfs is to build it on your own with the OpenEmbedded environment.

To build OM-2007.2 you need to add "tar" to the image types in your ''local.conf'':

IMAGE_FSTYPES = "jffs2 tar"

After that build a new image by issuing:

bitbake openmoko-devel-image

or if you are using the MokoMakefile:

make openmoko-devel-image

After the process finished there will be a ''Openmoko-....tar'' in the deploy directory, which is your newly created rootfs archive

=== Possibility 3 : Convert a jff2 image to a tarfile ===

See [[Userspace root image]] for more details on how to access contents of a jffs2 image.

== Prepare the SD card ==

=== Partioning the SD card ===

u-boot pre-2008-07-23 can only boot from FAT filesystems; if you update u-boot, you can boot from FAT or ext2.
This example shows how to do an example partition using the fdisk utility. Feel free to use the partitioning utility of your liking for this task.

fdisk /dev/mmcblk0

'''''Note:''''' The device file might differ on your system. If you are not sure about it, you may check your kernel message log by calling ''dmesg'' to find the correct device.

We will now create a 8 MB partition for our kernel and another one for the rootfs which will take up all the remaining space.

Command (m for help): d
Selected partition 1
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-983, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (18-983, default 18):
Using default value 18
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):
Using default value 983
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.

''Should probably need to change type of first partition to FAT 16 too ?''

''(type "t" in fdisk, choose the partition 1 and type "6" for FAT16. Check with "p", then type "w" to write)''

''How about a swap partition also?''

if it exits with something like

Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy

do

umount /dev/mmcblk0p1

on another shell and try again.

=== Formatting the SD card ===

Just issue the following command to create at FAT filesystem:

mkfs.vfat /dev/mmcblk0p1
{{Note|if you do not have mkfs.vfat you must find and install the "dosfstools" package. This package does not seem to be in the official feeds, but an unofficial build may be downloaded from http://members.shaw.ca/mmontour/neo/dosfstools_2.11-r0_armv4t.ipk}}

The second partition is about to be formatted with ext3 (for ext2 to work you need to make sure you compiled the kernel with the correct configuration):

mkfs.ext3 /dev/mmcblk0p2

== Populate SD card ==

Your sd card is now ready to be filled up with the rootfs and the needed kernel to boot.

Mount the second partition of your SD card somewhere and put the image on it:

mount /dev/mmcblk0p2 /mnt/moko
tar -C /mnt/moko/ -xzvf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar.gz

'''''Note:''''' As always in this guide the device name as well as the rootfs name needs to be adjusted to your device and filename structure

'''''Note:''''' There's a nice gotcha to take care about if you use your host OS automount. Some hosts mount these removable devices with "nodev" option by default for security. If the image you are unpacking has a populated /dev directory, the nodes will fail to create as devices then. If automounting the SD on your host, confirm there are no unexpected mount options by using "mount" command alone to list the mounts.

The next step is to mount the first partition of the sd card and install the kernel on it.

mount /dev/mmcblk0p1 /mnt/mokokernel
cp uImage-fic-gta01-latest.bin /mnt/mokokernel/uImage.bin

Or, for some versions of NOR u-boot:

mount /dev/mmcblk0p1 /mnt/mokokernel
cp uImage-fic-gta01-latest.bin /mnt/mokokernel/uimage

(Yes, lower case i and no extension.)

Make sure your kernel is called ''uImage.bin'' (or ''uimage'' for some versions of NOR u-boot). If the u-boot doesn't find the kernel image during boot, [[Bootloader#Using usbtty from Linux|log into the bootloader]] with ''[http://www.airs.com/ian/uucp.html cu]'', mount the partition with mmcinit and check the presence and the name of the kernel image with ''fatls mmc 1:1'' for FAT filesystem or ''ext2ls mmc 1:1'' for ext2 filesystem. Compare this carefully with the result of ''printenv sd_image_name''. Remember that you can modify the environment in NAND FLASH, but not in NOR FLASH, so if you plan to boot from NOR FLASH you have to modify the file name to match the environment variable.

Unmount both the rootfs partition and the kernel partition and make sure all remaining buffers are written to it:

umount /mnt/moko
umount /mnt/mokokernel
sync

== Add uboot boot entry ==
*See also" [[Qi]]

Depending on the revision of the phone and the partition type (ext2/ext3) you are using, it might be necessary to add an entry to the bootmenu to be able to boot the system off your SD card.
If you are using a FreeRunner and have created an FAT kernel/ext2 rootfs partition you should be able to boot from the card right out of the box, because a boot menu entry for this should already exist in the NOR/NAND boot menu.
In any other case you should at least make sure the needed entry exists in your menu before proceeding.
You will need to enter the uboot shell of the NAND boot menu for this. A description on how to connect to the uboot loader shell can be found in this article: [[Uboot#Bootloader_prompt]]. Details on howto get into the NAND boot menu can be found [[Booting#Log_into_U-Boot_in_the_NAND_Flash|here]].

After you read these two references you should be connected to your NAND uboot shell right now. The first thing to do is to set the boot menu timeout to a really high value. Unfortunately if you don't do this, the boot loader will continue booting after the default timeout (60 seconds) even if you are connected to the uboot shell. Just enter the following command to the menu prompt:

<pre>
setenv boot_menu_timeout 99999
</pre>

This will set the timeout to 99999 seconds which should definitely enough time for us finish whatever work we want accomplish in the boot loader shell.

Now we will make sure a appropriate menu item for booting from sd exists, or create it otherwise. You can print the defined boot loader environment by issuing the command:

<pre>
printenv
</pre>

If it shows a line beginning with ''menu_'' followed by the commands which are just to follow in this guide, you do not need to create a new menu entry. In any other case please proceed with the following.

Please make sure you are using the correct configuration based on the decisions you made earlier. For more information on the uboot prompt, see
* help
* help <command>
* and [[Bootloader]] and [[Bootloader commands]].

{{Note| The backslashes (\) are important for uboot to set the command as new environment variable (menu_9) instead of just executing them as soon as enter is pressed.}}

{{Note| Copy and paste may not work depending on your terminal emulator. Commi just works or you can use [[NeoCon|neocon]] terminal emulator and add a per-character delay. Otherwise, you will have to type in the commandline manually.}}

It is important to distinguish between FAT or ext2 kernel partitions and ext2 or ext3 root partitions at this point.

Please watch partition numbers in the following commands. In particular, you may need to change some of
<pre>
root=/dev/mmcblk0p#
fatload mmc#
ext2load mmc#
</pre>
depending on which partition number your root and kernel, respectively, are located. Number starts from unity.

'''Boot entry for FAT kernel+ext3 rootfs partitions:'''

<pre>
setenv menu_9 Boot from microSD (FAT+ext3): setenv bootargs \${bootargs_base} rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000
</pre>

'''Boot entry for FAT kernel+ext2 rootfs partitions:'''

<pre>
setenv menu_9 Boot from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000
</pre>

or: with additional 'init=/sbin/init' kernel parameter (may be needed for some images):

<pre>
setenv menu_9 Boot 200808 from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} init=/sbin/init ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000
</pre>

'''Boot entry for ext2 kernel+ext2 rootfs partitions: (requires newer u-boot)'''

<pre>
setenv menu_2 Boot from microSD part2 (ext2+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; ext2load mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000
</pre>

'''Boot entry for kernel and rootfs on same ext2 partition (tested with Qtopia/requires newer u-boot)'''

<pre>
setenv menu_3 QTopia: setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p1 rootdelay=5 \${mtdparts} ro\; mmcinit\; ext2load mmc 1:1 0x32000000 \${sd_image_name}\; bootm 0x32000000
</pre>

You are nearly done. Just issue a

<pre>
printenv
</pre>

and verify that your newly created entry is correctly displayed (This time the backslashes are not displayed anymore).

If everything looks fine enter

<pre>
saveenv
</pre>

into the prompt and press enter. The new configuration should now be saved to the NAND.

Shutdown your neo with the following command:

<pre>
neo1973 power-off
</pre>

After you restarted the Neo and got back to the NAND boot menu you should be able to select your newly created menu entry and successfully boot into the rootfs from your SD card.

If you got error when loading kernel, add sleep to boot entry.

Before:
<pre>
mmcinit\; ext2load mmc 1 0x32000000 \${sd_image_name}\;
</pre>
After:
<pre>
mmcinit\; sleep 1\; ext2load mmc 1 0x32000000 \${sd_image_name}\;
</pre>

----

See also [[Moving current system from flash to SD]] which shows how to move the running system currently running in flash to an SD card, in order to keep a backup system on SD on which to boot from.

----

== Appendix ==

=== Boot from SDHC ===

{{Note|the following text was written for the Neo1973. SDHC and SD should both work in a FreeRunner if you have u-boot from 2008-07-23 or later.}}

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

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

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

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

=== Autoboot from SDHC ===

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

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

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

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

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

=== Fixing udev automount ===

Udev automatically mounts the SD Card in /media/mmcblk0p1/ you can disable this with

echo /dev/mmcblk >> /etc/udev/mount.blacklist

=== Remarks on Kernel Parameters ===

==== loglevel ====

Some people suggested adding:

loglevel=8

to the kernel command line. IF you also have "console=tty0" on your kernel commandline this makes the boot process extremely slow because the framebuffer (the neo display in text mode) has to print out tons of lines of debug messages like:

s3c2410-sdi s3c2410-sdi: ......
mmc0: ....

{{Languages|Booting_from_SD}}

[[Category:Advanced End User]]
[[Category:Flashing Openmoko]]
[[Category:System Developers]]

USB host

2008-11-27T01:46:46Z

Jidanni: remove unnecessary `"'

{{Languages|USB host}}
The mini-USB port on both the Neo 1973 and the Neo FreeRunner supports both USB host and USB device. This opens up a range of possibilities, such as adding USB cameras and USB input devices.

=== Using USB host mode ===
==== Selecting USB host modes ====

By default, the mini-USB port is in device mode. To tell the Neo that it is logically a host¹):

# echo host > [[GTA02 sysfs|/sys]]/devices/platform/s3c2410-ohci/usb_mode

Independent of the logical mode of the USB port, the Neo FreeRunner can provide 5 volt USB power to an attached USB device. To enable this (not available on Neo 1973):

# echo 1 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note: You may want to run <code>ifconfig usb0 down</code> prior to switching to USB host mode, as the Neo's USB networking may not like having its USB port disappear. You'll probably want to ssh into your Neo over WiFi or Bluetooth before starting all of this, alternatively use an on screen keyboard.

Note that in full USB host mode the FreeRunner will power the external device. To avoid draining the battery use a powered USB hub, then on the FreeRunner enable logical host mode:

# echo host > /sys/devices/platform/s3c2410-ohci/usb_mode

but NOT electrical host mode

# echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note that powered USB hubs do not send power upstream, that is, into the host. If you wish to power or charge the FreeRunner, you will need a [[Specialized USB cables|special USB cable]].

¹)Debian note: You'll need the ohci-hcd module:
modprobe ohci-hcd

* NOTE: with [FSO] based distributions one should use the [[Dbus device API|dbus APIs]] and not the method stated above.

==== Returning to USB device mode ====
After doing whatever is needed to safely remove your device and unplugging it you can remove the provision of 5 volt power and return to device mode.

echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo device > /sys/devices/platform/s3c2410-ohci/usb_mode
 
You can now safely restart USB networking.

==== USB-Mode-Script====
These simple script is useful to switch the USB-Modes:
 

<nowiki>#!/bin/sh</nowiki> 
grep -q 'host' /sys/devices/platform/s3c2410-ohci/usb_mode 
if [ $? -eq 0 ] 
then 
echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo device > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo USB-Port is in device-mode now. 
else 
ifconfig usb0 down 
echo host > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo 1 > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo USB-Port is in host-mode now. 
fi 
 
You can easily create a push button menu item for this: [http://blogs.thehumanjourney.net/finds/entry/usb_host_mode_the_button Instructions]

==== Using a GUI ====
* Using the packaged push button derived from the script above: [http://blogs.thehumanjourney.net/finds/resource/usbmode-button_0.1_armv4t.ipk Download]
* [[User:Techiem2|Mark D. Montgomery II]]'s [http://techiem2.net/index.php?/archives/10-Freerunner-USB-Mode-Control-Program.html application] controls all the various modes through a GUI
* Thomas Vesely's [http://projects.openmoko.org/projects/usbchmod/ project]
* Using the gtk+ gui [[Framework-settings]]
* Using openmoko-panel-plugin (confirmation and link needed)

=== Providing power to connected USB devices while in host mode ===

Normally, USB host ports provide power to any connected USB device.

Available power in host mode is the full maximum of 500mA according to USB-specifications on the Neo FreeRunner, and no power is available in host mode on the Neo 1973. If your USB device respects USB-standards and consumes not more than 500mA, you may connect it directly to your Neo FreeRunner.

To provide power to USB devices attached to your Neo 1973, or to provide power to your Neo FreeRunner while USB-device connected, you can provide power by using a (modified [for powering FreeRunner]) powered USB hub (see below), or by manually injecting power into the attached USB device (and Neo FreeRunner) via one of the [[specialized_USB_cables]].

=== Powered USB hubs known to work with the Neo ===

(please add any known to work)

=== Providing power to run and charge the Neo while in host mode ===

A slightly separate issue is power to run and charge the Neo (both types) itself. When the USB port is in device mode, the Neo FreeRunner/1973 can be powered and recharged via the USB port, but when in standard host mode, the Neo FreeRunner is set to provide power and does not charge. Fortunately, control of the direction of power (in or out) is independent of the personality of the USB port (host or device):

To recap, the direction of power can be controlled:

Set to 0 (default), no power is provided at the USB port, charging is enabled, and host 15K pulldowns are removed from D+ and D-:

echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Set to 1, provides up to 500mA USB power at the USB port (FreeRunner only), disables charging from USB, and applies 15K pulldowns to USB D+ and D-:

echo 1 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Next, power must somehow be injected. An unmodified powered USB hub only provides power to the connected devices, but not to the connected host, so the only solution here is to modify a USB-hub¹) or to create a custom cable which will inject power into the host. See [[specialized_USB_cables]] for some examples.

(However, as there is a wide range[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.hardware/415]
of USB hubs out there, one might find power (on a powered USB hub)
is available already on the hub's mini USB 5 pin socket already, so not need a specialized cable after all!
Check with a test meter.)

Finally, there is the question of charge rate. The charging logic in the Neo will only charge at 100mA by default. Charging at 500mA will take place only if the charging device responds appropriatly to USB negotiation to increase power consumption. Charging at 1000mA will only take place if the Neo detects the appropriate resistor on the ID pins.

You can manually set the charge rate. See [[Forcing_fast_charge_mode]]

¹) often it's sufficient to short a diode in USB-hub to feed power to the host-connector too.
# Edit 05 Oct. 2008 : Not being able to find any diode on my ([[User:Henrikz|Henrikz]]) USB Hub (Brand: Equip, Type: 4 port, aluminum) I simply connected +5V (pin 1) from one of the downstream ports to pin 1 of the upstream port.

=== Power Concerns ===
You'll need to force the Neo to go into fast charge mode, since it can't do its usual power negotiation over USB.

echo -n fast_cccv > /sys/devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/chgmode

(Also this should be done by kernel when seeing 47K at ID-pin)

=== Working Examples ===

==== USB Keyboard ====

Pictures [http://blogs.thehumanjourney.net/finds/entry/20080716 here]

==== Connecting a USB-Stick ====
[[Image:connecting-usb-stick-1.jpg|thumb|left]]
I found this adapter, it has 2 Type A jacks, rather cheap (about 5 €).
 

[[Image:connecting-usb-stick-2.jpg|thumb|left]]
I borrowed the cable from a card reader, it has the same pinout like the cable that comes with the Neo.
 

[[Image:connecting-usb-stick-3.jpg|thumb|left]]
With the above commands I could mount the memory stick.
 

[[Image:connecting-usb-stick-4.jpg|thumb|left]]
 

[[Category:Neo1973 Hardware]]
[[Category:Neo FreeRunner Hardware]]
[[Category:USB]]

Neo Freerunner audio subsystem

2008-11-26T02:48:34Z

Jidanni: wikify and put header onto table head

The Neo Freerunner (GTA02) inherited the audio subsystem from its older brother the Neo 1973 (GTA01). However, there are a few small differences.
This page tries to show and explain the differences and points you to the [[Neo_1973_audio_subsystem | Neo 1973]] page whenever it touches the common points (but there may be overlaps for the sake of usability). As wiki pages are, errors and omissions are likely, and your help is welcomed.

==Differences from Neo 1973==
* There is only 1 (mono) built-in loud speaker instead of 2 (stereo).
* The Wolfson Codec driver presents 94 separate controls {switches, multiplexers, and volumes} to the alsa system (in both Neos). Unfortunately they are not mapped exactly the same for the GTA01 as for the GTA02.

==Possible sound connections through the Wolfson Codec==
* "Yes" = Confirmed, alsa state file exists.
* "No" = Not possible / not desirable.
* "Should" = Should be possible, not confirmed yet.
* "?" = Have no idea.

{| cellspacing="0" cellpadding="5" border="1"

|- align="center"
! - !! CPU !! GSM !! Bluetooth

|- align="center"
! GSM
| ?

|- align="center"
! Bluetooth
| ? || Yes

|- align="center"
! Wired Speaker
| Yes || Yes || ?

|- align="center"
! Wired Mic
| Yes || Yes || ?

|- align="center"
! Body Earpiece
| Should || Yes || ?

|- align="center"
! Body Speaker
| Yes || Should || ?

|- align="center"
! Body Mic
| Should || Yes || ?

|}

==Alsamixer channel controls==
The ALSA state files are installed by default, and belong to package ''"openmoko-alsa-scenarios"''.
To see where the files reside, do ''"opkg files openmoko-alsa-scenarios"''.
Currently they are in ''"/usr/share/openmoko/scenarios/"''.

# State: '''''GSM <-> Built-in Handset''''' (file gsmhandset.state)
## Mic volume:
##* Control 48: "Mic2 Capture Volume" (alsamixer name: "Mic2". Suggested value: max)
##* Control 12: "Mono Sidetone Playback Volume" (alsamixer name: "Mono sidetone" Suggested value: 5..7(max))
##* Control 5: "Mono Playback Volume" (alsamixer name: "Mono" Value: as needed)
## Speaker volume:
##* Control 6: "Bypass Playback Volume"
##* Control 4: "Speaker Playback Volume"
# State: '''''GSM <-> Built-in Handsfree''''' (file gsmspeakerout.state)
## Mic volume:
##* Control ?:
## Speaker volume:
##* Control ?:
# State: '''''GSM <-> Wired Headset''''' (file gsmheadset.state)
## Mic volume:
##* Control 49: "Mic1 Capture Volume"
##* Control 12: "Mono Sidetone Playback Volume"
##* Control 5: "Mono Playback Volume"
## Speaker volume:
##* Control 6: "Bypass Playback Volume"
##* Control 3: "Headphone Playback Volume"
# State: '''''GSM <-> Bluetooth Headset''''' (file ???)
## Alternative working state files: [http://handheldshell.com/gsm_headset.txt]
## Mic volume:
##* Control 13: "Mono Voice Playback Volume"
##* Control 5: "Mono Playback Volume"
# State: '''''CPU <-> Built-in Handset''''' (file voip-handset.state)
## Mic volume:
##* Control ?:
## Speaker volume:
##* Control ?:
# State: '''''CPU <-> Wired Headset''''' (file headset.state)
## Stereo sound:
##* Control ?:
## Headset output:
##* Control 94: "Amp Spk Switch" <- false
# State: '''''CPU <-> Buildin Speaker''''' (file stereoout.state)
## Mono sound:
##* Control ?:
## Headset output:
##* Control 94: "Amp Spk Switch" <- true

* These files I still don't know what they are for:

--[[User:Femto|Femto]] 12:39, 24 September 2008 (UTC) I've updated above values. Must be checked.

=== Volume Control ===

Angus Ainslie has written a simple [http://n2.nabble.com/Sound-quality-in-calls.-tp1087522p1096155.html python volume control] (which is getting more and more sophisticated) using some of these settings.

Installing the GUI mixer

:Download the the following files

:http://handheldshell.com/pymixer.py
:http://handheldshell.com/volume.desktop

<pre>
cp pymixer.py /usr/bin
chmod u+x /usr/bin/pymixer.py
cp volume.desktop /usr/share/applications
opkg install python-pygtk
opkg install http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk
</pre>

If the python script aborts unexpectedly then look [http://lists.openmoko.org/nabble.html#nabble-td1128064 here] for a fix

[[Category:Neo FreeRunner Hardware]]
[[Category:Audio]]

User:Henrikz

2008-11-26T02:13:11Z

Jidanni: nothing extra needed

Living in:
* Germany
Interested in:
* implementing some rendering stuff (for some unknown reason/purpose)
* using gpgp and/or implementing encryption/key-signing for e.g. sms

Can be contacted by email
h e n r i k @ z i m m e r . t o

See my [http://www.henrikzimmer.com/om FreeRunner-Experience-Blog-a-la-Amateur] (btw. in German)

=== Usb Power ===
To be able to have a keyboard (i.e. FR acting as a USB host) connected to the FreeRunner and charging the FreeRunner (FR acting as a device) at the same time I modified my USB Hub
* Brand: Equip
* Type: 4 Port USB2.0 aluminum
to also supply power to the upstream port of the hub.

Supposedly this is done by shorting a certain diode in the hub, which enables current to reach the upstream port ([[USB_host]]).
Since I was unable to locate any diode on my hub I decided to do as mentioned here [http://chockerblockablog.blogspot.com/2008/03/neo1973-no-wifi3gbattery-life-no.html Chockerblockablog], that is
to simply connect the +5V (pin 1) from one of the downstream ports to pin 1 of the upstream port (connected to the FreeRunner).
[For all the hubs I've bought here in Taiwan, plugging an external power supply into their coaxial port also supplies 5V to the Mini 5 pin socket, as well of course to the 4 USB A sockets. [[User:Jidanni|Jidanni]] 02:13, 26 November 2008 (UTC)]
Also the FreeRunner needs to be told to 1. Be a host, 2. to charge (faster than 100mA default).
These are the steps (as I did them, no warranty...)
* Modify USB Hub by bypassing diode with a jumper OR connect pin 1 (+5V) from downstream port to pin 1 of the upstream port
* Tell FR to act as a USB Host
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode
* Tell FR to enable charging
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode
* The FR is now charging with 100mA
cat /sys/class/i2c-adapter/i2c-0/0-0073/usb_curlim
outputs "100mA"
* Set charging to 500mA (or more... I wouldn't) [[Forcing_fast_charge_mode]]
echo 500 > /sys/class/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous
* DONE! Now the FR is charging with
cat /sys/class/i2c-adapter/i2c-0/0-0073/usb_curlim
"500mA" and now a Usb keyboard, mouse etc. can be used while charging!

''NOTE: to actually attach the Usb Hub to the FreeRunner, I used a USB gender changer (here are some (other) suggestions [[Specialized_USB_cables]]))''

''NOTE2: Another (solder-less) option is described here [http://tabletblog.com/2006/01/no-solder-usb-host-method.html no-solder-usb-host-method (for a N770, but who cares)]''

''NOTE3: Also, wikipedia is your [http://en.wikipedia.org/wiki/Universal_Serial_Bus USB-friend ]''

Advertising

2008-11-25T02:21:53Z

Jidanni: or no advertising

== Text ==
* There could be a description of Openmoko/Neo1973 features
* There could be a short story about what Openmoko/the Neo1973 does different:
** e.g.:
After leaving work your Neo's GPS automatically switches your Alarm Profile from
Silent to Loud and guides you to the next gas station. At home, your Neo automatically
deploys its WiFi functionality, retrieves your email (free of charge) and activates
voice over ip capabilities (free of charge).
And so on...
** e.g.:
Neo: Hi, I'm a Neo.
iPhone: And I'm an iPhone.
* iPhone looks on a big map and tries to orientate himself
Neo: What are you doing?
iPhone: I try to locate myself by using Google Maps.
Neo: Oh, that doesn't seem to be very exciting. I use GPS for that kind of stuff.
Works automatically.
iPhone: GPS, yeah?
Neo: Yes. Oh, wait, I'm entering the cinema. I think, it's better for me, to
switch to stand-by now. See you after the movie.
iPhone: Oh, bye.
* Neo leaves, iPhone looks on the map again.
iPhone: Oh, here we are! Finally...
[http://lists.openmoko.org/pipermail/community/2007-July/006141.html]
** e.g.:
Scene: Completely blank white background.
Two people enter the frame.
Moko: Hi, I'm an Openmoko
iPhone: And I'm an iPhone
* Openmoko looks like he's enjoying himself
iPhone: What are you doing?
Moko: Oh, I just downloaded this great new game I came across. Want to try it?
iPhone: I, er, I can't play new games. I've got this great game of solitaire, though!
Moko: That's a shame. Nothing at all?
iPhone: Well, I can play games off the web. Some of them. Want a game of bejeweled?
Moko: ...thanks, no. I'm fine.
[http://lists.openmoko.org/pipermail/community/2007-July/006110.html]
* There ''should'' be some pre-composed basic information that can be copy'n'pasted into one's Myspace/Facebook/whatever/-profile.
* There ''should'' be some pre-composed advanced information for press/blogs/mobile service providers

=== Printed Advertisement ===
...

== Video ==

Adam Krikstone did some nice Openmoko video ads: (youtube)

[http://www.youtube.com/view_play_list?p=472DE700A3CC70A4 Playlist]

[http://www.youtube.com/watch?v=DCQ7dmGuAU8]

[http://www.youtube.com/watch?v=tQPjfUqp-dk]

[http://www.youtube.com/watch?v=4qP-K1HOMHk]

[http://www.youtube.com/watch?v=S--2HeQqjq4]

[http://www.youtube.com/watch?v=dpwxzEopg60]

[http://www.youtube.com/watch?v=EuG2hYiO9AU]

[http://www.youtube.com/watch?v=lGjY7tigdkA]

[http://www.youtube.com/watch?v=YR4ezMgRlWo]

[http://www.youtube.com/watch?v=OZC3mjRW5Tg]

[http://www.youtube.com/watch?v=GxsVFG7jHI8]

[http://www.youtube.com/watch?v=62kLhNngE20]

[http://www.youtube.com/watch?v=kR-4VhlsiV8]

== Sound empathy / Jingle ==
* There should be some kind of jingle for Openmoko, just like this "Hello Moto" thing from Motorola
** [http://tetraden.te.funpic.de/openmoko/OpenMoko_free_your_phone02.ogg Number one] (suggestions/whishes? franzkautz@yahoo.de Topic: sth. with Openmoko)
** [http://tetraden.te.funpic.de/openmoko/OpenMoko_free_your_phone04.ogg Number two] (franzkautz@yahoo.de)

== Thoughts, Notions ==
=== General Ideas ===
* '''What is advertised?'''
* If we advertise a phone by claiming it can do everything maybe no one will buy it.
* '''Question''': Who is supposed to buy this phone?
# '''Average Phone User''' probably only wants a phone to make calls. Why would he buy an opensource linux phone with additional command line? We ''need'' reasons for ''him'' to buy a phone running Openmoko:
#* Easy to use (not implemented though ;-)
#* Rich and powerfull text input methods
#* MS Outlook/whatever Sync
#* Music and video playing capabilities (not fully implemented?)
#* (please add)
# '''Advanced Phone User''': won't be hard to persuade him. As we likely are all advanced phone users it will be easy to find reasons/features for him to buy this phone:
#* GPS-based profiles
#* Seamless GPS-based GSM/WiFi/VoIP-switching
#* NFS file sync (maybe possible)
#* (please add)
# '''Technophobe Phone User''' really needs some reasons for this phone:
#* Really easy to use (really not implemented ;-)
#* Flashy UI look
#* (please add)
#'''Businesses/Government''' (Entities willing to roll their own code in-house to get the functionality they desire from a smart-phone)

=== Further Ideas ===
Something that came to me passing some mobile service provider's outlet today. This should be done when GTA_02 is available and software running.

''A guy walks into a mobile service provider's outlet or approached by the outlet's staff. The guy asks the clerk about their phones and ends up showing him his Neo. He explains him the Neo's features that stand unrivaled to any of the mobile service provider's offered phones and eventually leaves him completly flabbergasted and pondering about the meaning of life and mobile connectivity/whatever''

--[[User:Minime|Minime]] 16:58, 7 July 2007 (CEST)

''A dude dressed in t-shirt and jeans (deja-vu?), walks through a crowded lane. Everyone except him are dressed in prison clothes and march in the opposite direction with their "closed" phones, some of the guys look at this "free" man and stare. To add to the effect we play an ambient techno music and everything is white in colour. The man walks in front of the camera, at that moment, gets a call, smiles and says "Hello World...", We then fade into the "Free your phone" and "Openmoko" thingy as seen in the rocking youtube videos.''

Source: http://lists.openmoko.org/pipermail/community/2007-July/007551.html

=== Slogans ===

"The Phone" for "The Matrix" tm.
"The One Phone" for Mddle-earth.
"The Next Generation Phone" for "Star Trek" tm conventions.
"The True Phone" for religious occasions.
"The Liberated Phone"
http://lists.openmoko.org/pipermail/community/2007-July/007122.html

"The Phone with the only force" (wheel of time)
"The diy phone" (steampunk scene)
"The ZAT'NI'KATEL'PHONE" (stargate)
http://lists.openmoko.org/pipermail/community/2007-July/007168.html

Unleash your phone.
http://lists.openmoko.org/pipermail/community/2007-July/007141.html

"The Open Phone"
"Our Phone"
"The Human Phone" (ok, sounds a bit like Ubuntu)
"Free your Phone" (wich obviously is not the same as "The free phone". It sounds good, and is already used in the youtube ads)
"More then a Phone"
"Phone++"
"The Phone from people to people"
"The Freedom Phone"
"Teh ub3rz h4ck70r7 Ph0n3!!11oneeleven"
http://lists.openmoko.org/pipermail/community/2007-July/007171.html

Everyone wants to be an individual these days. How about something like:
"The individual phone."
"_Your_ phone."
"Express yourself!"
"Express yourphone!"
"It's yours."
"It's in your hands."
"It's up to you."
"Expand your Mind!"
"Communicate yourself!"

Wordplays are very good too.
"Openmoko - If you call for more."
"Openmoko and you will call attention."
"Openmoko - Don't call for help."
"Openmoko - With a phone jack."

Apparently stupid statements call attention too, I think.
"It's mobile"
"_You_ can change the battery."
"You can simply buy it."

=== Testimonials ===
See: [[Testimonials]]

=== Controversial Issues ===
* We need to be careful about using copyrighted material (e.g. youtube)
** Other legal issues...?
** Be aware of what we are advertising: What functions does Openmoko currently feature, what is planned and what not? Are functions advertised protected by patents?
* What is the community's goal in advertising?
** Are we advertising Openmoko?
** Are we advertising the Neo1973? And if so, is this our job? The Neo1973 is after all, a commerical product.

==Word of mouth==
Or: ''the phone so cool that you learn about it via word of mouth'',
as with most open software things, and not via advertising.

Of course you will still have to prove that your grandparents can use it, daily, before you promote it, advertising or not.

[[Category:Community]]
[[Category:Openmoko Inc]]

Manually using Bluetooth

2008-11-25T02:16:09Z

Jidanni: /* Power it up */use DBUS they tell me

{{InProgress}}
Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.
Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.

This page details how to use bluetooth from the command line.
We have quite a lot of plans about what exactly Bluetooth should be used for.

== Power it up ==

Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.

The old way to do it is a shell command (for kernels before 2.6.24):

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

For kernel 2.6.24 (or later) use

root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on

and on the GTA02 *only* (i.e. not on the GTA01) also use

root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset

But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!

At the shell, "hciconfig" should print information about the adapter if it powered up properly:

hciconfig

The devices should show as UP. If not you can use

hciconfig <device> up

== Bluetooth Functions ==

===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===

In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use "0000". Also, you can set the name to "Neo (%d)".

=== Scanning for bluetooth devices ===

hcitool scan

This will list the addresses of any discoverable bluetooth devices in the vicinity

=== passkey agent example ===

There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.

passkey-agent --default 0000 &

Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).

=== HID (Human Input Device) ===

==== Being able to use HID devices ====

Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing "p" twice on the bt keyboard actually gives you a "q".

We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.
To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)

hidd --connect 11:22:33:44:55:66

and press "Connect" on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:

hidd --search

to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.

Tested on:
* [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]
* [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&cl=us,en Logitech Dinovo Media Desktop (keyboard)]
* [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.
* [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.
* [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)
* [http://www.apple.com/support/keyboard/ Apple's white "Wireless Keyboard (original)"] - details may be the same as above. (tested some time ago)
* [http://www.frogpad.com/ FrogPad] - as above
* [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.
* [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.
* [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)
* [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.

==== Acting as HID device ====

We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]

=== RFCOMM ===

Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).

First, switch on the GPS and identify the BT address:

hcitool scan

Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:

rfcomm0 {
# Automatically bind the device at startup
bind no;
# Bluetooth address of the device
device 00:11:22:33:44:55;
# RFCOMM channel for the connection (check your GPS docs for details)
channel 1;
# Description of the connection
comment "Bluetooth GPS";
}

Restart the BT services:

root@neo:~$ /etc/init.d/bluetooth stop
root@neo:~$ /etc/init.d/bluetooth start

You should now be able to bind the GPS to /dev/rfcomm0, like this:

root@neo:~$ rfcomm bind 0

Confirm the connect:

root@neo:~$ rfcomm
rfcomm0: 00:11:22:33:44:55 channel 1 clean

... and watch the NMEA strings coming from your GPS:

root@neo:~$ cat /dev/rfcomm0
$GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F
$GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50
$GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D

If you have nothing better to do, you can now pinpoint my office :-).

=== OBEX ===

=== Networking ===

==== Using PC's connection from Neo ====

===== Bluetooth networking with a Linux system =====

Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.

'''On the laptop'''

* Start bluetooth
/etc/init.d/bluetooth start

* Start pand as server
pand -s

* As soon as pand is started on the phone configure your IP address
ip a add 10.0.0.1/24 dev bnep0
ip l set bnep0 up

* Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.

'''On the Neo'''

* There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.

* Power on bluetooth (see above)

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

* Connect to the laptop pand
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8

* Configure your IP address
ip a add 10.0.0.2/24 dev bnep0
ip r add default via 10.0.0.1

* Sometimes you may need to bring up the bnep0 on the phone as well:
ip l set bnep0 up
* Enjoy

*--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).
I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.

Should see log line like
''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''

if connection is successful in server's /var/log/messages.

===== Bluetooth networking with a MacOS X system =====

Please refer to [[MacOS_X#Bluetooth_2]]

For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]

===== Bluetooth networking with a Windows XP system =====

This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack

* Start bluetooth on Windows XP

* Enable "Network Access" in the Bluetooth configuration

* Scan for the Neo and pair with the Neo (right click, select pair)

On the Neo

* Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service

* Power on bluetooth (see above)

* Scan for the laptop
root@fic-gta01:~$ hcitool scan
Scanning ...
<laptop_bt_address> Thinkpad
...

* Connect to the laptop pand
pand -c <laptop_bt_address> -r PANU -d NAP -e bnep0 -A -E -S
(add '-n' to see the pand status messages until you get it right)

For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:
pand -l -r PANU -d NAP -e bnep0 -A -E -S
(add '-n' to see the pand status messages until you get it right)

* Configure your IP address. It should work like when connecting to Linux:
ip a add 10.0.0.2/24 dev bnep0
ip r add default via 10.0.0.1
If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.

* You should now be able to ssh/putty from Windows to your Neo. Enjoy!
By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.

===== PPP Networking =====

If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:

* Edit the /etc/default/bluetooth file and set the following options:
RFCOMM_ENABLE=true
DUND_ENABLE=true
DUND_OPTIONS="--listen --persist call dun"

* Create an /etc/ppp/peers/dun file with options like the following:
115200
192.168.2.202:192.168.2.200
passive
local
noipdefault
noauth
nodefaultroute

* Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)

To connect from a MacOS 10.3 client:

* Open "Applications/Utilities/Bluetooth Serial Utility"

* Click on "New"

* Choose a name, then click "Choose Device"

* Locate your Neo, then select the "LAN Access Point" service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other.

* Select "Port type: RS-232" and "Show in Network Preferences". Click OK.

* Open the Network Preferences page then "Show: Network Port Configurations". Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)

* Choose "Show: <your-device-name>", then click "Modem"

* Select "Null Modem 115200" from the list of available devices. Uncheck "Wait for dial tone" and "Enable error correction and compression in modem". Optionally check "Show modem status in menu bar".

* Click "Connect". If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.

===== Bluetooth networking with a Linux system - More secure way =====

''Check this, probably needs some corrections''

Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.

On the laptop

* check these options in /etc/bluetooth/hcid.conf
security auto;
passkey "your pin";
lm master;

* Start bluetooth
# /etc/init.d/bluetooth start

* Start pand as server
pand --listen --role NAP --encrypt

* Add in /etc/network/interfaces (see [[USB_Networking]])
auto bnep0
iface bnep0 inet static
address 192.168.1.1
netmask 255.255.255.0
network 192.168.1.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT

On the Neo

* Power on bluetooth (see above)

* Scan for the laptop
root@fic-gta01:~$ hcitool scan
Scanning ...
00:20:E0:5A:FE:C8 laptop

* Set pin
root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &

* Connect to the laptop pand
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8

* Configure your IP address
root@fic-gta01:~$ ifconfig bnep0 192.168.1.2
root@fic-gta01:~$ route add default gateway 192.168.1.1

* Enjoy

==== Using Neo's connection from PC ====

===== Calling Neo's GPRS modem via Bluetooth =====

In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.

This section not written yet. Has someone set it up?

===== Sharing existing Neo's connection =====

In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.

On the PC
# Check with hciconfig you have working Bluetooth
On the Neo
(if on Debian etc., remember modprobe ohci_hcd hci_usb)
# Initialize Bluetooth as told before:
## echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
## echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset
# install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk
# modprobe bnep
# Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)
# Use default passkey "1234" in /etc/bluetooth/hcid.conf
# pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below ("On the PC") or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on
# ifconfig bnep0 10.0.5.2 up
# echo 1 > /proc/sys/net/ipv4/ip_forward
# iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0
On the PC:
# sudo pand --connect <your bluetooth mac address> --service NAP --autozap
# ifconfig bnep0 10.0.5.1 up
# You can test the connection with ping 10.0.5.2
# sudo ip route add default via 10.0.5.2 dev bnep0
# [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf

== Advanced Audio Distribution Profile (A2DP) ==

=== A2DP quickie ===

* If you experience problems with choppyness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC)

It's now possible (if a little hackish) to stream mp3 to a bluetooth headset. It's a known problem that the playback rate changes (pitch varies). Timing issues are also likely the reason for gaps in playback.

If the bluez packages are recent enough, you can use a shortcut. I'll document it here and leave the longer version below (the long version also demonstrates the API used by the GUI to manage headsets)

Create /etc/asound.conf with your bluetooth headset's address filled in:

pcm.!default {
type bluetooth
device "xx:xx:xx:xx:xx:xx"
}

then play a song

madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay

or for smoother results...

madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:song.wav
aplay song.wav

=== A2DP ===

If that doesn't work... all the more hackish... install required packages:

echo "src/gz python http://www.angstrom-distribution.org/unstable/feed/armv4t/python/" >> /etc/ipkg/angstrom-python.conf
echo "src/gz base http://www.angstrom-distribution.org/unstable/feed/armv4t/base/" >> /etc/ipkg/angstrom-base.conf
ipkg update ; ipkg install python-core python-xml python-dbus bluez-utils bluez-utils-alsa

Create /etc/asound.conf:

pcm.!default {
type bluetooth
}
ctl.!default {
type bluetooth
}
pcm.bluetooth {
type bluetooth
}
ctl.bluetooth {
type bluetooth
}

Run the passkey agent (see above in this page)

Fill in your bluetooth headset address below and execute the python script (with your headset turned on)

#!/usr/bin/python
import dbus
bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')
conn = manager.ActivateService('audio')
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')
path = audio.CreateDevice('00:0D:3C:44:33:22')
audio.ChangeDefaultDevice(path)
sink = dbus.Interface(bus.get_object(conn, path), 'org.bluez.audio.Sink')
sink.Connect()

FINALLY: play a song

madplay /media/card/song.mp3 --sample-rate=44100 --output=wave:- | aplay

=== Headset Audio ===

[[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.

To try this out, follow the instructions in the a2dp section to install software and run the passkey agent.

Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.

Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:

#!/usr/bin/python
import dbus
bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')
conn = manager.ActivateService('audio')
audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')
path = audio.CreateHeadset('00:0B:2E:39:33:22')
audio.ChangeDefaultHeadset(path)
headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')
headset.Connect()
headset.Play()

Now place a call and try to route it to bluetooth (after it's in progress):

alsactl -f /etc/gsmbluetooth.state restore

You may also be able to listen to system audio given the right state file:

alsactl -f /etc/systembluetooth.state restore
madplay song.mp3

==Bluetooth Headset on Freerunner ==

[http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:

:Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]

:Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.

:http://handheldshell.com/BtConfigure.py
:Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run
BtConfigure.py

:Download the the following python scripts to set up the audio service and set the headset as the default device:

:http://handheldshell.com/BtHeadset.py
:http://handheldshell.com/passkey.py
:http://handheldshell.com/BtHeadsetDisconnect.py
:http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?

:Download the the following python scripts if you prefer not to mess around with alsactl:

:http://handheldshell.com/pymixer.py
:http://handheldshell.com/volume.desktop

:put pymixer in /usr/bin

chmod u+x /usr/bin/pymixer.py

:put volume.desktop in /usr/share/applications

:Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed

cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state

:from the home screen run Volume

:from the terminal run

BtHeadset.py

:Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.

:Now start the call

:In the volume control switch to the btheadset tab. press restore

:You should now hear the call in your headset.

:End the call

BtHeadsetDisconnect.py

:This was all done with the 2008-updates image from sept 4.

:The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :

pcm.headset {
type bluetooth
device <headset mac>
profile "voice"
}

== Further reading ==

http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio
http://www.gentoo.org/doc/en/bluetooth-guide.xml

{{Languages|Manually_using_Bluetooth}}

[[Category:Bluetooth| ]]
[[Category:Networking]]
[[Category:Application Developer]]

GTA02 sysfs

2008-11-25T02:11:42Z

Jidanni: use DBUS they tell me

==GTA02 Kernel sysfs highlights==
sysfs is a filesystem that is mounted on /sys which contains various fake "files" that are actually filled by a variety of drivers and other kernel subsystems. You can often also write stuff into these "files" using

echo 1 > /sys/blah...

to change settings and behaviours of the kernel and drivers dynamically. (When doing this, take care you have a space before the redirection operator > or the shell will do something completely different with your command.)
However[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!

===USB Host / Device===
====/sys/devices/platform/neo1973-pm-host.0/hostmode====
* Defaults to 0, GTA02 USB hardware is configured to be a device, no power is generated for USB, charging is enabled and host 15K pulldowns are removed from D+ and D-
* Set to 1 to put the GTA02 USB hardware into host mode, so it starts to generate 5V power, disables charging from USB, and applies 15K pulldowns to USB D+ and D-
====/sys/devices/platform/s3c2410-ohci/usb_mode====
* Defaults to "device", it means the USB peripheral in the CPU is logically configured for device mode
* Set to "host" to logically configure the peripheral to act like a host for other USB devices to be plugged into it

Normally you set these two guys at the same time for the same mode, but there is a trick possible to select logical host mode but leave the power arrangements as if it was in device mode and apply external power. You need to [[Specialized USB cables|externally add]] 15K pulldowns on D+ and D- if you do this, because we did not enable them the normal way. With this, you can have a USB device attached to GTA02, and use external power and charge the battery at the same time.

===GSM Subsystem===
====/sys/devices/platform/neo1973-pm-gsm.0/power_on====
* Defaults to "0", GSM power OFF
* Set to "1" to enable power to GSM logic
====/sys/devices/platform/neo1973-pm-gsm.0/reset====
* Defaults to "0", no reset
* Set to "1" briefly after power applied to reset GSM logic
====/sys/devices/platform/neo1973-pm-gsm.0/download====
* Defaults to "0", no insane clicking sound
* Set to "1" to drive yourself crazy and enable serial access to GSM chips down headphone socket / once a second loud clicks / chirps

===Resume Reason===
====/sys/devices/platform/neo1973-resume.0/resume_reason====
If you cat this you get a list of possible resume sources in text with one or more * at the left of the active source that woke us. You need a recent U-Boot to get the * set.

===MEMCONFIG===
====/sys/devices/platform/neo1973-memconfig.0/BANKCON0 .. 7====
For extreme meddlers (I salute you), these let you control the wait states and other characteristics of the memory regions of the FreeRunner. Information and warnings about how to use these are here:

http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=fd25f90517322fc6c07bfb8d34752d3cb41cb4b6

===FIQ and HDQ===
====/sys/devices/platform/sc32440_fiq.0/fiq/count====
FIQ is used to provide precision interrupt service in order to implement the HDQ protocol used to the battery couloumb counter. This shows how many FIQ interrupts have been run since the kernel started. It's turned off unless it is required.
====/sys/devices/platform/gta02-hdq.0/hdq/dump====
If you cat this, you will see the raw contents of HDQ device register space. This is the bq27000 couloumb counter in our case.
====/sys/devices/platform/gta02-hdq.0/hdq/write====
This allows you to write to raw HDQ registers, using "<decimal register index> <decimal value>"

===power_supply battery information===
Most of these are coming from the coulomb counter over HDQ dynamically, but the bq27000 does not update a lot of its registers any more often than once per 4 seconds. Therefore a lot of this info can be a bit stale or averaged over that period.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/uevent====
All informations about battery.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/type====
Just says "Battery"
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/status====
This will summarize what goes on generally with the battery
* "Not Charging" - there's a charger in, but right now it isn't charging us. Normal if you are fully charged and still powered.
* "Charging" - there's a charger in and it is charging the battery
* "Discharging" - we are running on battery
* "Full" - not normally given as a result (Not Charging used instead)
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/voltage_now====
Battery voltage in uV, averaged. Obviously this depends on load and place on discharge curve, etc.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/current_now====
Current being drawn from battery (+ve) or pushed into battery during charging (-ve) in uA
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/charge_full====
Coulomb Counter's estimate of the capacity of the battery measured in uA/h. It roughly means that if full, for one hour it could supply current at this rate. I saw 1197913 reported on mine, so it estimates it can provide 1.2A for an hour.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/temp====
This is the battery temperature reported by the Coulomb Counter chip that is part of the physical battery. It is in Celcius * 10, so 251 means 25.1 degrees.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/technology====
"Li-ion"
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/present====
* "0" the battery is absent, or not one with a Coulomb Counter
* "1" the smart battery is present
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/time_to_empty_now====
At current rate of discharge, estimate of how long we can run for. If battery is not discharging, it won't make an estimate and will return a magic value "3932100" meaning "no estimate". The coulomb counter averages the load and adjusts this value slowly to be its estimate of when we will blow chunks.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/time_to_full_now====
This estimates how long until we are fully charged, at current rate of charging, in seconds. If we are not charging, it gives the magic value "3932100" meaning "no estimate".
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/capacity====
This is the remaining capacity of charge in the battery in percent. This is probably the most useful figure here.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/online====
* "0" no charger is present
* "1" A powered charger is present

===PMU info===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/chgmode====
* "enabled" means the charger is powered and willing to charge, although if you're full it might not be right now
* "disabled" means there was no power or not enough power supplied to charge

Looks like it may also report "fast" here. [[User:OlivierBerger|OlivierBerger]] 07:47, 25 July 2008 (UTC)

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/charger_type====
Shows the detected charger type followed by the mode it is running in. So "charger 500mA mode 100mA" would be the case for non-enumerated USB connection, "charger 500mA mode 500mA" for after enumeration (or "host/500mA usb mode 500mA" as here [[User:OlivierBerger|OlivierBerger]]).

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous====
This is added to allow the PMU to be told to take more current than the default rules allow. Use it only if you know your charger source can handle it. For example

echo 500 > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous

will allow PMU to draw 500mA even though you are connected to a dumb charger where the limit is normally held at 100mA, since it didn't enumerate the GTA02. You can give 0, 100, 500 or 1000 here, but make sure your charger source can handle what you give here, otherwise it can exceed what is safe for your charging source to provide.

More details at [[Forcing_fast_charge_mode]].

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/dump_regs====
cat this to get a dump of the I2C registers for the PMU, useful for debugging power problems.

===Bluetooth===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/power_on====
* Default "0" no power to Bluetooth device
* set to "1" to enable power to Bluetooth
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/reset====
* Default to "0", no reset
* set to "1" to reset BT (needed after powerup)

===GPS===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron====
* Default "0" GPS unpowered
* set to "1" to power GPS section

===Audio codec===
====/sys/devices/platform/soc-audio/codec_reg====
cat this to get a dump of codec registers. Note they are 9-bit wide.
====/sys/devices/platform/soc-audio/codec_reg_write====
You can write to any codec register by echoing "<codec reg index in hex> <value in hex>" to here

===Glamo===
====/sys/devices/platform/glamo3362.0/regs====
cat this to get a dump of selected Glamo regs. You can write the regs by echoing "<glamo reg index in decimal> <value in decimal>" here.

===LED & Vibrator===
(per: Jeff Tickle)
====/sys/devices/platform/neo1973-vibrator.0/leds/neo1973:vibrator/brightness====

For the Vibration, my very limited testing indicates it will accept a
range of 0-255, with 0 being off and 255 being full force. So, you can
actually set the strength of vibration.

Keep in mind that the vibration will positively eat your battery, so
use with caution!

====/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/brightness====
====/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness====
====/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness====

For the LEDs, you can echo 1 for on or 0 for off to any of these files
to control the state of the LEDs.

===Accelerometers===
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/power/wakeup====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/power/wakeup====
Turns on accelerometers.

====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/dump====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/dump====
Dumps accelerometers raw contents.

====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/full_scale====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/full_scale====
Switches the accelerometers between 2G and 8G mode. Echo "9.2" into it for 8G, any other value for 2G (default)[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/004029.html]

[[Category:Flashing Openmoko]]
[[Category:System Developers]]

Openmoko Education Taiwan

2008-11-24T22:54:47Z

Jidanni: 煩請註年份

==Openmoko 校園演講==
('''煩請各項註年份''')
===輔仁大學 2008-10-22===

開放手機平臺熱潮在開發者社群與校園燃燒，Openmoko是Android、iPhone之外的另一個開放手機平臺。Openmoko從開放原始碼開始，一路公開機構設計（CAD）與電路圖（schematics），並且建立了一個龐大的開發者社群。現在，Openmoko正將開放之路，朝向「開放學習」邁進。 Om2008.8 又稱為 ASU 是 Openmoko 重要的一個 Openmoko Linux distribution 版本，本演講將介紹 Om2008 的主要變更，以及如何在 FreeRunner 上撰寫第一個 EFL 程式。透過這個講座，能帶領同學在開放手機撰寫一個小程式。

*題目：Openmoko Linux 2008: 開放手機新體驗（Openmoko Linux 2008: Programming Neo FreeRunner）
*時間：2008-10-22（三），14:00～15:30
*地點：輔仁大學資工系聖言樓

===台北科技大學 10-16===

開放手機平臺熱潮在開發者社群與校園燃燒，Openmoko是Android、iPhone之外的另一個開放手機平臺。Openmoko從開放原始碼開始，一路公開機構設計（CAD）與電路圖（schematics），並且建立了一個龐大的開發者社群。現在，Openmoko正將開放之路，朝向「開放學習」邁進。 Om2008.8 又稱為 ASU 是 Openmoko 重要的一個 Openmoko Linux distribution 版本，本演講將介紹 Om2008 的主要變更，以及如何在 FreeRunner 上撰寫第一個 EFL 程式。透過這個講座，能帶領同學在開放手機撰寫一個小程式。

*題目：Openmoko Linux 2008: 開放手機新體驗（Openmoko Linux 2008: Programming Neo FreeRunner）
*時間：2008-10-16（四），15:30～16:30
*地點：台北科技大學綜合科學館地下室第三演講聽

===義守大學 09-25===

上學期 Openmoko 結合校園課程，為大家帶來「開放手機革命」的題目。這學期，Openmoko 再度結合校園課程，為大家再次準備了「開放手機新體驗」的課程。本學期的課程將著重在實機體驗與程式開發，歡迎有興趣的朋友與主辦單位連繫。

*題目：開放手機新體驗（Exploring and Programming Neo FreeRunner）
*時間：2008-09-25（四），13:40～15:20
*地點：義守大學資工系

===九十六學年度下學期校園演講總覽===

[[Image:0222-ncku-campus.jpg|200px|thumb|Right|Seminar at NCKU Campus]]
[[Image:0222-ncku-campus2.jpg|200px|thumb|Right|Seminar at NCKU Campus]]
[[Image:0227-nctu-campus.jpg|200px|thumb|Right|Seminar at NCTU Campus]]
[[Image:0227-nctu-campus2.jpg|200px|thumb|Right|Seminar at NCTU Campus]]
[[Image:0409-cycu-campus.jpg|200px|thumb|Right|Seminar at CYCU Campus]]

'''新聞稿'''

Openmoko與各大名校聯手推動行動通訊教育課程 2008/02/14
開放源碼手機廠進駐校園培養工程師

2008年2月14日---世界開放源碼手機軟體大廠Openmoko表示，從九十六學年度下學期開始，即將與台灣各大資訊通訊相關學系、科技大學共同展開一系列的巡迴開放源碼課程，讓學生能夠在學校進行「手機軟體」的研究計畫。Openmoko此舉為業界的一個先驅挑戰，選擇在台灣進行Openmoko平台的人才培育，作為長期開發該產業資源的根基。配合學校的教育課程外，同時Openmoko也將提供暑期實習機會給學生，並預計吸收優秀的人才在畢業後進入Openmoko工作。

Openmoko總經理Mr. Sean Moss-Puitz強調，除了致力發展Linux作業系統的行動通訊平台，公司並以推動free and open source software (FOSS)專案為主要的經營策略。他更指出，Openmoko看好台灣開放手機市場的發展前景，長期經營社群關係，並將大多數的研發資源投資在台灣，所以在台北內湖科學園區建立起全世界第一個 Openmoko開源手機體驗實驗室，提供開發者以及社群人員一個更為開放的討論空間。

Openmoko此次校園演講結合企業實務經驗與學術討論，帶給國內多所大專院校資訊相關科系學生豐富精彩的開放Linux平台與行動通訊觀念。此次校園巡迴演講將鎖定開放手機的未來為主題，並且融合多項時下熱門話題，包含智慧型手機、行動2.0時代、作業系統技術等多項領域，除此之外，並將於現場提供Openmoko最新款產品 Neo FreeRunner讓學生親身體驗，一窺未來手機的風貌；從創意思考、技術討論，到產品研發等完整流程，讓學生可以一次獲取所有最新資訊。

Openmoko大中華區行銷部 Jollen Chen 指出，Openmoko對於能夠和學生面對面交流非常開心，也格外重視此次校園演講計畫，期望能透過學生之間的交流，尋找對此研究領域專精的年輕學子，也希望透過學生的另類思考帶給Openmoko更多進步空間。

此次校園巡迴演講將於2月22日正式起跑，首站即為國內首屈一指的指標大學國立成功大學，陸續將於2月27日於國立交通大學、3月3日於中原大學、3月18日於逢甲大學、3月26日於元智大學、3月28日於國立東華大學等多所大專院校正式登場。

'''參與學校'''

Openmoko 因為開放源碼的特性，因此很適合教學與研究場合。Openmoko 在2月份到6月份之間，於以下以學校進行教育課程。

* 成功大學：2/22（五），02:30PM~04:00PM，資訊工程學系 4263教室（資工講座）
* 交通大學：2/27（三），01:30PM~03:30PM
* 中原大學：3/03（一），02:00PM~04:00PM，電學105講堂
* 元智大學：3/26（三），07:00PM~09:00PM
* 東華大學：3/28（五），02:00PM~04:00PM
* 昆山大學：4/07（一），09:00AM~12:00PM
* 中原大學：4/09（三），06:10PM~07:40PM
* 淡江大學（研究所）：4/10(四)，02:10PM~04:00PM
* 淡江大學（大學部）：4/18(四)，03:10PM~05:00PM
* 中正大學：4/28(一），02:00PM~04:00PM

'''演講稿下載'''

{|
! 課程場次 !! 日期 !! 講義下載
|- style="background-color:#eeeedd;"
! colspan="3"|九十六學年度下學期課程
|-
|成功大學 || 2/22（五） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-ncku.pdf Om-campus-freeyourphone-ncku.pdf]
|-
|交通大學 || 2/27（三） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-nctu.pdf Om-campus-freeyourphone-nctu.pdf]
|-
|中原大學 || 3/03（一） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-cycu.pdf Om-campus-freeyourphone-cycu.pdf]
|-
|元智大學 || 3/26（三） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-yzu.pdf Om-campus-freeyourphone-yzu.pdf]
|-
|東華大學 || 3/28（五） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-ndhu.pdf Om-campus-freeyourphone-ndhu.pdf]
|-
|昆山大學 || 4/07（一） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-ksu.pdf Om-campus-freeyourphone-ksu.pdf]
|-
|中原大學 || 4/09（三） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-cycu.2.pdf Om-campus-freeyourphone-cycu.2.pdf]
|-
|淡江大學（研究所） || 4/10（四） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-tku.pdf Om-campus-freeyourphone-tku.pdf]
|-
|淡江大學（大學部） || 4/18（四） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-tku.2.pdf Om-campus-freeyourphone-tku.2.pdf]
|-
|中正大學 || 4/28(一） || [http://people.openmoko.org/jollen/Om-campus-freeyourphone-ccu.pdf Om-campus-freeyourphone-ccu.pdf]
|}

==Openmoko 校園課程==

===成功大學電機工程學系: 開放手機平臺軟體發展技術第一次訓練課程 10-9===

[[Image:ncku-training-1009.jpg|200px|thumb|Right|Openmoko Training using E-courseware Draft]]

開放手機平臺熱潮在開發者社群與校園燃燒。Openmoko從開放原始碼開始，一路公開機構設計（CAD）與電路圖（schematics），並且建立了一個龐大的開發者社群。現在，Openmoko正將開放之路，朝向「開放學習」邁進。

'''主辦單位：國立成功大學電機工程學系'''

'''協辦單位：教育部嵌入式軟體聯盟（ESW）、我本墨客股份有限公司（Openmoko Inc.）'''

歡迎有興趣的老師帶著您的學生一起參加此一Openmoko開放手機平台軟體發展技術訓練課程。

'''活動報名'''

*時間：97 年 10 月 9 日（星期四）AM 9:30～16:30
*地點：
**國立成功大學自強校區電機工程館地下1樓令洋廳
**臺南市東區大學路1號
*名額：限80人（因場地容量有限，依報名先後順序，額滿為止）
*費用：免費
*報名日期：自9月25日起至10月6日止或額滿為止，恕不接受現場報名。
*報名方式：請配合下列說明使用電子郵件(e-mail)報名，以便處理您的報名。
#電子郵件主旨請註明“報名10月9日Openmoko訓練課程”；
#電子郵件內文請提供參加本訓練課程人員之資料：
##教師請提供：姓名、職稱、校系(所)名、電話與電子郵件等聯絡資料
##學生請提供：姓名、年級、校系(所)名、電話與電子郵件等聯絡資料
##其他人士請提供：姓名、工作單位與職稱、電話與電子郵件等聯絡資料
#可多人以同一電子郵件報名；
#為避免電子郵件失誤，系統將自動回覆；若逾2日未獲回覆請電詢；
#請使用報名專用電子郵件帳號：om081009 AT rtpc06 DOT ee DOT ncku DOT edu DOT tw
*主辦單位聯絡查詢窗口：
**陳敬 (成功大學電機工程學系助理教授)
**06-2757575分機62376 jchen AT mail DOT ncku DOT edu DOT tw

'''活動內容'''

{|
! 時間 !! 10月9日活動內容 !! Note
|- style="background-color:#eeeedd;"
! colspan="3"|Openmoko 開放手機軟體發展技術訓練課程
|-
|09:00~09:30 || ・報到 ||
|-
|09:30~10:20 || ・Openmoko 與 Mobile 2.0: 開放手機新機會 ||
|-
|10:20~10:30 || ・中場休息 ||
|-
|10:30~11:40 || ・Openmoko 手機軟體開發環境建置: Pre-Built Toolchain & 模擬器 ||
|-
|11:40~12:00 || ・GSM Telephony: libgsmd ||
|-
|12:00~13:30 || ・午餐休息（午餐請自理） ||
|-
|13:30~14:20 || ・Openmoko Software Stack 架構介紹: Om2008.8、ASU、FSO ||
|-
|14:20~14:30 || ・中場休息 ||
|-
|14:30~15:20 || ・Openmoko Linux Distribution: Om2008.x 手機開發新體驗 ||
|-
|15:20~15:30 || ・中場休息 ||
|-
|15:30~16:20 || ・手機應用軟體開發: 以Neo FreeRunner 加速度感測器為例 ||
|-
|16:20~16:30 || ・Q & A ||
|-
|}

'''ChangeLog'''

# 為配合 Openmoko Linux distribution 更新（Om2008.x），課程主題略做調整。
# Edje 將移至第二次訓練課程做講解。
# 因開發環境建置需要實機展示，需要較多時數，故調整 libgsmd 的時間。

===中央大學通訊工程學系: Openmoko開放手機訓練課程 09-10===

開放手機平臺熱潮在開發者社群與校園燃燒。Openmoko是基於Linux與自由軟體（Free Software）的開放手機平臺，同時也是全世界第一個真正100%開放的手機平臺，Openmoko目前已釋出完整的GSM+GPS手機（Neo FreeRunner）、手機軟體平臺、開發環境、電路圖及機構設計，相當適合使用於教學與研究用途。

Openmoko為Linux開放式手機，使用者可自由地將自己的服務創意具體實現在手機上。本基礎訓練課程主要在提供學校老師與同學瞭解Openmoko基本架構、手機軟體開發環境、及應用程式等技術，協助老師順利將開放手機平臺使用在嵌入式系統相關課程，並使用Openmoko手機發展GSM與GPS應用。

敬邀老師帶著您的學生一起參加。

時間：97 年 9月10日（星期三）

地點：中央大學通訊工程學系 E1-101 會議室

對象：大專院校老師與學生

活動連絡人：Jollen Chen <jollen at openmoko (dot) com>

主辦單位：

* Openmoko
* 國立中央大學通訊工程學系

課程主題：

# Openmoko手機軟體開發環境建置與程式設計
# 手機軟體開發技術：以Neo FreeRunner動作感測器為例
# Openmoko 手機軟體課程與教學

[[Category:Openmoko Taiwan]]
[[Category:Event]]

USB host

2008-11-23T10:20:55Z

Jidanni: /* Selecting USB host modes */guessing link

{{Languages|USB host}}
The mini-USB port on both the Neo 1973 and the Neo FreeRunner supports both USB host and USB device. This opens up a range of possibilities, such as adding USB cameras and USB input devices.

=== Using USB host mode ===
==== Selecting USB host modes ====

By default, the mini-USB port is in device mode. To tell the Neo that it is logically a host¹):

# echo host > [[GTA02 sysfs|/sys]]/devices/platform/s3c2410-ohci/usb_mode

Independent of the logical mode of the USB port, the Neo FreeRunner can provide 5 volt USB power to an attached USB device. To enable this (not available on Neo 1973):

# echo 1 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note: You may want to run <code>ifconfig usb0 down</code> prior to switching to USB host mode, as the Neo's USB networking may not like having its USB port disappear. You'll probably want to ssh into your Neo over WiFi or Bluetooth before starting all of this, alternatively use an on screen keyboard.

Note that in full USB host mode the FreeRunner will power the external device. To avoid draining the battery use a powered USB hub, then on the FreeRunner enable logical host mode:

# echo host > /sys/devices/platform/s3c2410-ohci/usb_mode

but NOT electrical host mode

# echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note that powered USB hubs do not send power upstream, that is, into the host. If you wish to power or charge the FreeRunner, you will need a [[Specialized USB cables|special USB cable]].

¹)Debian note: You'll need the ohci-hcd module:
modprobe ohci-hcd

* NOTE: with [FSO] based distributions one should use the [[Dbus device API|dbus APIs]] and not the method stated above.

==== Returning to USB device mode ====
After doing whatever is needed to safely remove your device and unplugging it you can remove the provision of 5 volt power and return to device mode.

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
 
You can now safely restart USB networking.

==== USB-Mode-Script====
These simple script is useful to switch the USB-Modes:
 

<nowiki>#!/bin/sh</nowiki> 
grep -q 'host' /sys/devices/platform/s3c2410-ohci/usb_mode 
if [ $? -eq 0 ] 
then 
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo USB-Port is in device-mode now. 
else 
ifconfig usb0 down 
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo USB-Port is in host-mode now. 
fi 
 
You can easily create a push button menu item for this: [http://blogs.thehumanjourney.net/finds/entry/usb_host_mode_the_button Instructions]

==== Using a GUI ====
* Using the packaged push button derived from the script above: [http://blogs.thehumanjourney.net/finds/resource/usbmode-button_0.1_armv4t.ipk Download]
* [[User:Techiem2|Mark D. Montgomery II]]'s [http://techiem2.net/index.php?/archives/10-Freerunner-USB-Mode-Control-Program.html application] controls all the various modes through a GUI
* Thomas Vesely's [http://projects.openmoko.org/projects/usbchmod/ project]
* Using the gtk+ gui [[Framework-settings]]
* Using openmoko-panel-plugin (confirmation and link needed)

=== Providing power to connected USB devices while in host mode ===

Normally, USB host ports provide power to any connected USB device.

Available power in host mode is the full maximum of 500mA according to USB-specifications on the Neo FreeRunner, and no power is available in host mode on the Neo 1973. If your USB device respects USB-standards and consumes not more than 500mA, you may connect it directly to your Neo FreeRunner.

To provide power to USB devices attached to your Neo 1973, or to provide power to your Neo FreeRunner while USB-device connected, you can provide power by using a (modified [for powering FreeRunner]) powered USB hub (see below), or by manually injecting power into the attached USB device (and Neo FreeRunner) via one of the [[specialized_USB_cables]].

=== Powered USB hubs known to work with the Neo ===

(please add any known to work)

=== Providing power to run and charge the Neo while in host mode ===

A slightly separate issue is power to run and charge the Neo (both types) itself. When the USB port is in device mode, the Neo FreeRunner/1973 can be powered and recharged via the USB port, but when in standard host mode, the Neo FreeRunner is set to provide power and does not charge. Fortunately, control of the direction of power (in or out) is independent of the personality of the USB port (host or device):

To recap, the direction of power can be controlled:

Set to 0 (default), no power is provided at the USB port, charging is enabled, and host 15K pulldowns are removed from D+ and D-:

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Set to 1, provides up to 500mA USB power at the USB port (FreeRunner only), disables charging from USB, and applies 15K pulldowns to USB D+ and D-:

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Next, power must somehow be injected. An unmodified powered USB hub only provides power to the connected devices, but not to the connected host, so the only solution here is to modify a USB-hub¹) or to create a custom cable which will inject power into the host. See [[specialized_USB_cables]] for some examples.

(However, as there is a wide range[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.hardware/415]
of USB hubs out there, one might find power (on a powered USB hub)
is available already on the hub's mini USB 5 pin socket already, so not need a specialized cable after all!
Check with a test meter.)

Finally, there is the question of charge rate. The charging logic in the Neo will only charge at 100mA by default. Charging at 500mA will take place only if the charging device responds appropriatly to USB negotiation to increase power consumption. Charging at 1000mA will only take place if the Neo detects the appropriate resistor on the ID pins.

You can manually set the charge rate. See [[Forcing_fast_charge_mode]]

¹) often it's sufficient to short a diode in USB-hub to feed power to the host-connector too.
# Edit 05 Oct. 2008 : Not being able to find any diode on my ([[User:Henrikz|Henrikz]]) USB Hub (Brand: Equip, Type: 4 port, aluminum) I simply connected +5V (pin 1) from one of the downstream ports to pin 1 of the upstream port.

=== Power Concerns ===
You'll need to force the Neo to go into fast charge mode, since it can't do its usual power negotiation over USB.

echo -n "fast_cccv" > /sys/devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/chgmode

(Also this should be done by kernel when seeing 47K at ID-pin)

=== Working Examples ===

==== USB Keyboard ====

Pictures [http://blogs.thehumanjourney.net/finds/entry/20080716 here]

==== Connecting a USB-Stick ====
[[Image:connecting-usb-stick-1.jpg|thumb|left]]
I found this adapter, it has 2 Type A jacks, rather cheap (about 5 €).
 

[[Image:connecting-usb-stick-2.jpg|thumb|left]]
I borrowed the cable from a card reader, it has the same pinout like the cable that comes with the Neo.
 

[[Image:connecting-usb-stick-3.jpg|thumb|left]]
With the above commands I could mount the memory stick.
 

[[Image:connecting-usb-stick-4.jpg|thumb|left]]
 

[[Category:Neo1973 Hardware]]
[[Category:Neo FreeRunner Hardware]]
[[Category:USB]]

USB host

2008-11-23T10:16:54Z

Jidanni: /* Selecting USB host modes */link

{{Languages|USB host}}
The mini-USB port on both the Neo 1973 and the Neo FreeRunner supports both USB host and USB device. This opens up a range of possibilities, such as adding USB cameras and USB input devices.

=== Using USB host mode ===
==== Selecting USB host modes ====

By default, the mini-USB port is in device mode. To tell the Neo that it is logically a host¹):

# echo host > [[GTA02 sysfs|/sys]]/devices/platform/s3c2410-ohci/usb_mode

Independent of the logical mode of the USB port, the Neo FreeRunner can provide 5 volt USB power to an attached USB device. To enable this (not available on Neo 1973):

# echo 1 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note: You may want to run <code>ifconfig usb0 down</code> prior to switching to USB host mode, as the Neo's USB networking may not like having its USB port disappear. You'll probably want to ssh into your Neo over WiFi or Bluetooth before starting all of this, alternatively use an on screen keyboard.

Note that in full USB host mode the FreeRunner will power the external device. To avoid draining the battery use a powered USB hub, then on the FreeRunner enable logical host mode:

# echo host > /sys/devices/platform/s3c2410-ohci/usb_mode

but NOT electrical host mode

# echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note that powered USB hubs do not send power upstream, that is, into the host. If you wish to power or charge the FreeRunner, you will need a [[Specialized USB cables|special USB cable]].

¹)Debian note: You'll need the ohci-hcd module:
modprobe ohci-hcd

* NOTE: with [FSO] based distributions one should use the dbus APIs and not the method stated above.

==== Returning to USB device mode ====
After doing whatever is needed to safely remove your device and unplugging it you can remove the provision of 5 volt power and return to device mode.

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
 
You can now safely restart USB networking.

==== USB-Mode-Script====
These simple script is useful to switch the USB-Modes:
 

<nowiki>#!/bin/sh</nowiki> 
grep -q 'host' /sys/devices/platform/s3c2410-ohci/usb_mode 
if [ $? -eq 0 ] 
then 
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo USB-Port is in device-mode now. 
else 
ifconfig usb0 down 
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo USB-Port is in host-mode now. 
fi 
 
You can easily create a push button menu item for this: [http://blogs.thehumanjourney.net/finds/entry/usb_host_mode_the_button Instructions]

==== Using a GUI ====
* Using the packaged push button derived from the script above: [http://blogs.thehumanjourney.net/finds/resource/usbmode-button_0.1_armv4t.ipk Download]
* [[User:Techiem2|Mark D. Montgomery II]]'s [http://techiem2.net/index.php?/archives/10-Freerunner-USB-Mode-Control-Program.html application] controls all the various modes through a GUI
* Thomas Vesely's [http://projects.openmoko.org/projects/usbchmod/ project]
* Using the gtk+ gui [[Framework-settings]]
* Using openmoko-panel-plugin (confirmation and link needed)

=== Providing power to connected USB devices while in host mode ===

Normally, USB host ports provide power to any connected USB device.

Available power in host mode is the full maximum of 500mA according to USB-specifications on the Neo FreeRunner, and no power is available in host mode on the Neo 1973. If your USB device respects USB-standards and consumes not more than 500mA, you may connect it directly to your Neo FreeRunner.

To provide power to USB devices attached to your Neo 1973, or to provide power to your Neo FreeRunner while USB-device connected, you can provide power by using a (modified [for powering FreeRunner]) powered USB hub (see below), or by manually injecting power into the attached USB device (and Neo FreeRunner) via one of the [[specialized_USB_cables]].

=== Powered USB hubs known to work with the Neo ===

(please add any known to work)

=== Providing power to run and charge the Neo while in host mode ===

A slightly separate issue is power to run and charge the Neo (both types) itself. When the USB port is in device mode, the Neo FreeRunner/1973 can be powered and recharged via the USB port, but when in standard host mode, the Neo FreeRunner is set to provide power and does not charge. Fortunately, control of the direction of power (in or out) is independent of the personality of the USB port (host or device):

To recap, the direction of power can be controlled:

Set to 0 (default), no power is provided at the USB port, charging is enabled, and host 15K pulldowns are removed from D+ and D-:

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Set to 1, provides up to 500mA USB power at the USB port (FreeRunner only), disables charging from USB, and applies 15K pulldowns to USB D+ and D-:

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Next, power must somehow be injected. An unmodified powered USB hub only provides power to the connected devices, but not to the connected host, so the only solution here is to modify a USB-hub¹) or to create a custom cable which will inject power into the host. See [[specialized_USB_cables]] for some examples.

(However, as there is a wide range[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.hardware/415]
of USB hubs out there, one might find power (on a powered USB hub)
is available already on the hub's mini USB 5 pin socket already, so not need a specialized cable after all!
Check with a test meter.)

Finally, there is the question of charge rate. The charging logic in the Neo will only charge at 100mA by default. Charging at 500mA will take place only if the charging device responds appropriatly to USB negotiation to increase power consumption. Charging at 1000mA will only take place if the Neo detects the appropriate resistor on the ID pins.

You can manually set the charge rate. See [[Forcing_fast_charge_mode]]

¹) often it's sufficient to short a diode in USB-hub to feed power to the host-connector too.
# Edit 05 Oct. 2008 : Not being able to find any diode on my ([[User:Henrikz|Henrikz]]) USB Hub (Brand: Equip, Type: 4 port, aluminum) I simply connected +5V (pin 1) from one of the downstream ports to pin 1 of the upstream port.

=== Power Concerns ===
You'll need to force the Neo to go into fast charge mode, since it can't do its usual power negotiation over USB.

echo -n "fast_cccv" > /sys/devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/chgmode

(Also this should be done by kernel when seeing 47K at ID-pin)

=== Working Examples ===

==== USB Keyboard ====

Pictures [http://blogs.thehumanjourney.net/finds/entry/20080716 here]

==== Connecting a USB-Stick ====
[[Image:connecting-usb-stick-1.jpg|thumb|left]]
I found this adapter, it has 2 Type A jacks, rather cheap (about 5 €).
 

[[Image:connecting-usb-stick-2.jpg|thumb|left]]
I borrowed the cable from a card reader, it has the same pinout like the cable that comes with the Neo.
 

[[Image:connecting-usb-stick-3.jpg|thumb|left]]
With the above commands I could mount the memory stick.
 

[[Image:connecting-usb-stick-4.jpg|thumb|left]]
 

[[Category:Neo1973 Hardware]]
[[Category:Neo FreeRunner Hardware]]
[[Category:USB]]

USB Networking

2008-11-23T10:14:06Z

Jidanni: /* From desktop to FreeRunner */repair

= 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 e.g. 192.168.1.(something) might save you a lot of troubleshooting later. A discussion of this is [http://lists.openmoko.org/pipermail/support/2008-August/thread.html#1277 here].

= Simple Manual Linux Configuration =

Try this first (as root on your desktop, with FreeRunner attached via USB cable and booted properly, not at the Boot Menu). If it works, then you can add permanent configuration or use more sophisticated setups below.

<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
ip addr add 192.168.0.200/24 dev usb0</pre>

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

<pre>ip addr add 192.168.0.200/28 dev usb0</pre>

(This will just map the net from 192.168.0.192 to 192.168.0.207 onto usb0. If you get the error 'Cannot find device "usb0"', double-check that your FreeRunner is turned on and connected by USB. If that doesn't work, try unplugging and replugging the USB cable.)

And in this case you should enable ARP proxy on internet facing interface INSTEAD of using iptables:

<pre>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>ifconfig usb0 up</pre>

Then (ideally, not as root):

<pre>ssh root@192.168.0.202</pre>

The default password is blank.

Due to the fact that in most cases your Neo will use the same dns servers as your computer uses, you can automate the process of writing dns servers to your phone:

<pre>#!/bin/sh
/sbin/route add -host 192.168.0.202/32 dev usb0
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
iptables -P FORWARD ACCEPT
sysctl -w net.ipv4.ip_forward=1
su `whoami` -c "scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf"</pre>

Again if your net already is 192.168.0.0, replace the POSTROUTING statement with
<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/28</pre>

This simple script will set up routing for your Freerunner and than copy resolv.conf with dns addresses straight to the phone.
All you have to do is connect phone to the computer, run the script and enjoy internet connection from your phone.

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

Masquerading options (tested on Linux 2.6.26.3) are found in:

''Networking --->
Networking options --->''

To see the other options, enable

* CONFIG_NETFILTER (''Network packet filtering framework (Netfilter)'')

Then, from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
Core Netfilter Configuration --->''

You need at least following options enabled as modules:

* CONFIG_NF_CONNTRACK (''Netfilter connection tracking support'')
* CONFIG_NF_CONNTRACK_FTP (''FTP protocol support'')
* CONFIG_NETFILTER_XTABLES (''Netfilter Xtables support'')

Rest of the needed options are found from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
IP: Netfilter Configuration --->''

You need to enable (again, as modules is fine):

* CONFIG_NF_CONNTRACK_IPV4 (''IPv4 connection tracking support (required for NAT)'')
* CONFIG_IP_NF_IPTABLES (''IP tables support (required for filtering/masq/NAT)'')
* CONFIG_NF_NAT (''Full NAT'')
* CONFIG_IP_NF_TARGET_MASQUERADE (''MASQUERADE target support'')

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

You should add the IP address of the DNS servers as provided by your ISP. Check your router's or PC's network status for the nameserver IP addresses.

<pre>echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf</pre>

You can also add the public DNS server called openDNS:
<pre>echo nameserver 208.67.222.222 > /etc/resolv.conf
echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

These settings will be lost on reboot. You can set the DNS for the next connect, by adding the following to the end of the usb0 setting in /etc/network/interfaces, right above the bluetooth networking section:
<pre>up echo nameserver 208.67.222.222 > /etc/resolv.conf
up echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

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

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

=== Proxying with iptables ===

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

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

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

Test if it works:
<pre>ping www.google.com</pre>

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

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

== FreeBSD ==
You need to load the cdce kernel module (if it is not already linked into your kernel). As root do:

# kldload cdce

The Neo should then show up as cdce0 interface and you can handle the cdce0 interface just like the usb0 device under Linux. For more information see the cdce manpage. An easy way to assign the IP address to the cdce0 interface is using the devd(8) daemon. Create the following two files,

/usr/local/etc/devd/cdce.conf as:

notify 1 {
match "system" "IFNET";
match "subsystem" "cdce0";
match "type" "ATTACH";
action "/usr/local/etc/devd/cdce.sh $subsystem $type";
};

and /usr/local/etc/devd/cdce.sh as:

#!/bin/sh
case $2 in
'ATTACH')
ifconfig cdce0 192.168.0.200 netmask 255.255.255.0
exit 0 ;
;;
esac
exit 0

Then restart the devd(8) daemon with:

# /etc/rc.d/devd restart

If you now plugin the FreeRunner into the USB port the cdce0 interface gets created and the IP addr will be assigned.

== Debian, Ubuntu and others ==

Edit /etc/network/interfaces and add:

<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/ipv4/ip_forward &
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &

</pre>

This is more sophisticated than the manual setup. The 'auto usb' stanza ties into the Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner 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.

Another possible configuration that adds DNS forward and removes
the iptables changes after unplugging:

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=$(awk '$1 == "nameserver"{print $2; exit(0);}' /etc/resolv.conf)

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

It is possible to use network-manager to automatically connect to the Freerunner using udev. The process uses udev to run a script when the Frerunner is plugged in. The script uses the ip command to set the mac address of the usb network interface. To begin, create /etc/udev/rules.d/80-freerunner.rules :

<pre>
# This file causes programs to be run on device insertion.
# See udev(7) for syntax.

# rule to assign a fixed mac address specified in /
KERNEL=="usb[0-9]*", DRIVERS=="cdc_ether", ACTION=="add", RUN+="/usr/local/sbin/freerunner-usb-add.sh %k"
</pre>

Next, create the /usr/local/sbin/freerunner-usb-add.sh :

<pre>
#!/bin/sh

(
busNum=$( printf %.2d $( expr match "$1" "usb$[0-9]*$") )

ip link set "$1" address 00:00:22:55:bb:$busNum &> /dev/null

) &

exit 0
</pre>

Finally run "chmod +x /usr/local/sbin/freerunner-usb-add.sh" to make it executable. Now you can use network-manager with mac-address specific settings and get it to automatically connect.

=== Ubuntu Issues ===

Ubuntu 8.10 doesn't work as expected if you used /etc/network/interfaces to automate the connection. Network manager likes to latch onto the network device and add a default route through 192.168.0.202, breaking your network connection. Network manager also says you can't edit or remove this connection from its list. I'm going back to making the connection manually.

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. Moving the DRIVERS=="*?" out of the top GOTO, to ACTION=="add" line fixes the problem.

<pre>
SUBSYSTEM=="net", 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", DRIVERS=="?*", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"

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

LABEL="net_end"
</pre>

The bug is that the DRIVERS variable isn't set at all when the device is unplugged.

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)
:Actually it appears that it's not fixed, but patching that file and disconnecting and reconnecting the phone works perfectly. --[[User:Johndoesacc|Johndoesacc]] 18:37, 20 August 2008 (UTC)

== Mandriva ==

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

<tt>/etc/sysconfig/network-scripts/ifcfg-usb0</tt>:

DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
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)

<tt>/etc/sysconfig/network-scripts/usb0-routes</tt>:

ADDRESS0=192.168.0.200
NETMASK0=255.255.255.0

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

service network restart

This didn't work for me (Mandriva 2008.1), giving errors from Shorewall. However, simply using MCC, Network->Sharing Internet Access worked fine. You need to connect Neo when starting it. --[[User:Alih|Alih]] 18:50, 22 September 2008 (UTC)

== 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
=== Option C - tested on F9 ===
(seemed to work on FC8 also)

Plug in the usb cable. NetworkManager should detect the phone automatically but you should ignore it.
Open Network Configuration tool (System -> Administration -> Network) and perform following steps:
# Click '''New''' button on top bar
# Click '''Forward'''
# Select OpenMoko from device list
# Click '''Forward'''
# Select 'Statically set IP address:' and enter address: 192.168.0.200, netmask 255.255.255.0 (or use 255.255.255.240 if you want only route ip range 192.168.0.192-192.168.0.207). Leave gateway empty.
# Click '''Forward'''
# Click '''Apply''' to close add dialog
# Select newly added usb0 device from the device list.
# Click '''Edit''' button on top bar
# You might want to remove a tick from 'Activate device when computer starts' check box.
# Click '''Ok''' to close window dialog.
Save settings and close the window.

Open Firewall Configuration (System -> Administration -> Firewall) and enable masquerading:
# Select '''Masquerading''' from left panel
# Check device(s) which you'd like to share internet connection. Typically eth0 or wlan0.
# Click '''Apply''' and close application

Open terminal and perform (as root user):
# ifdown usb0
# ifup usb0
The first command will remove any existing settings given by the NetworkManager and second command brings the device up with appropriate settings.

Now you should be able to ping e.g. 74.125.39.99 [www.google.com] from OpenMoko. Configure /etc/resolv.conf and you should have full a internet access.

==== Troubleshooting ====
If Network Configuration tool cannot see the the usb0 try to unplug the usb cable for a few seconds and wait until the NetworkManager finds it again.

NetworkManager will assign a new ip address for the OpenMoko if link goes down for a while. You can fix this by issuing '''ifup usb0''' again.

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

=== Manual Configuration ===

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

=== Automatic Configuration ===
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
}

== Slackware (tested with 12.1) ==

Following is based on [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].

Create a new udev rules file <tt>/etc/udev/rules.d/91-openmoko.rules</tt>:

<pre>
SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="1457", ATTRS{idProduct}=="5122", RUN+="/sbin/om-usb $env{INTERFACE} start"
SUBSYSTEM=="net", ACTION=="remove", ENV{INTERFACE}=="usb[0-9]", RUN+="/sbin/om-usb $env{INTERFACE} stop"
</pre>

Then create the script <tt>/sbin/om-usb</tt>:

<pre>
#!/bin/sh
INTERFACE=$1
ACTION=$2

# udev fails silently when the script fails, e.g. due to commands not
# being found
PATH=/usr/sbin:/sbin:/usr/bin:/bin

case $ACTION in
'start')
# Put all your setup here
;;
'stop')
# Put all your tear down here
;;
*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac
</pre>

The <tt>INTERFACE</tt> will be <tt>usb0</tt> in most cases.

== Archlinux ==
Following is based on [http://xenos.altervista.org/blogs/index.php?blog=3&title=openmoko-usb-networking-su-archlinux furester's solution].

Install package [http://aur.archlinux.org/packages.php?ID=20220 openmoko-usb-networking] from AUR:

$ yaourt -S openmoko-usb-networking

= 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 adding a new line for every ssh host-key to your known_hosts you can add the following to the phone section in ~/.ssh/config (or see the snippet at : [[USB Networking#Changing_host_keys]] bellow)

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:

user@host$ 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:

root@phone# mkdir ~/.ssh

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

user@host$ scp ~/.ssh/id_rsa.pub root@phone:~/.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt using a command like 'ssh root@phone' from the account user@host because the public key in the file user@host:~/.ssh/id_rsa.pub is contained in the list of keys which have access in the file root@phone:~/.ssh/authorized_keys (since scp is used, only one key exists, but you can grant access to the phone from more than one account, for example user@host, user@laptop).

To make ssh login as root by default, add the following lines to ~/.ssh/config:

Host phone
User root

Replace ''phone'' with the hostname or ip of your phone. You should now be able to ssh into the phone without having to type ''root@'' every time.

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). Now you have set this, you can issue the following command to connect to your moko :

ssh root@moko

== 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'' #(isn't the "env" redundant here?)

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

==Automated setup network and mounting partitions==

See [https://bugs.launchpad.net/ubuntu/+bug/289548 Ubuntu bug report in launchpad].


{{Languages|USB Networking}}

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

GTA02 sysfs

2008-11-23T10:10:38Z

Jidanni: /* /sys/devices/platform/s3c2410-ohci/usb_mode */link

==GTA02 Kernel sysfs highlights==
sysfs is a filesystem that is mounted on /sys which contains various fake "files" that are actually filled by a variety of drivers and other kernel subsystems. You can often also write stuff into these "files" using

echo 1 > /sys/blah...

to change settings and behaviours of the kernel and drivers dynamically. (When doing this, take care you have a space before the redirection operator > or the shell will do something completely different with your command.)

===USB Host / Device===
====/sys/devices/platform/neo1973-pm-host.0/hostmode====
* Defaults to 0, GTA02 USB hardware is configured to be a device, no power is generated for USB, charging is enabled and host 15K pulldowns are removed from D+ and D-
* Set to 1 to put the GTA02 USB hardware into host mode, so it starts to generate 5V power, disables charging from USB, and applies 15K pulldowns to USB D+ and D-
====/sys/devices/platform/s3c2410-ohci/usb_mode====
* Defaults to "device", it means the USB peripheral in the CPU is logically configured for device mode
* Set to "host" to logically configure the peripheral to act like a host for other USB devices to be plugged into it

Normally you set these two guys at the same time for the same mode, but there is a trick possible to select logical host mode but leave the power arrangements as if it was in device mode and apply external power. You need to [[Specialized USB cables|externally add]] 15K pulldowns on D+ and D- if you do this, because we did not enable them the normal way. With this, you can have a USB device attached to GTA02, and use external power and charge the battery at the same time.

===GSM Subsystem===
====/sys/devices/platform/neo1973-pm-gsm.0/power_on====
* Defaults to "0", GSM power OFF
* Set to "1" to enable power to GSM logic
====/sys/devices/platform/neo1973-pm-gsm.0/reset====
* Defaults to "0", no reset
* Set to "1" briefly after power applied to reset GSM logic
====/sys/devices/platform/neo1973-pm-gsm.0/download====
* Defaults to "0", no insane clicking sound
* Set to "1" to drive yourself crazy and enable serial access to GSM chips down headphone socket / once a second loud clicks / chirps

===Resume Reason===
====/sys/devices/platform/neo1973-resume.0/resume_reason====
If you cat this you get a list of possible resume sources in text with one or more * at the left of the active source that woke us. You need a recent U-Boot to get the * set.

===MEMCONFIG===
====/sys/devices/platform/neo1973-memconfig.0/BANKCON0 .. 7====
For extreme meddlers (I salute you), these let you control the wait states and other characteristics of the memory regions of the FreeRunner. Information and warnings about how to use these are here:

http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=fd25f90517322fc6c07bfb8d34752d3cb41cb4b6

===FIQ and HDQ===
====/sys/devices/platform/sc32440_fiq.0/fiq/count====
FIQ is used to provide precision interrupt service in order to implement the HDQ protocol used to the battery couloumb counter. This shows how many FIQ interrupts have been run since the kernel started. It's turned off unless it is required.
====/sys/devices/platform/gta02-hdq.0/hdq/dump====
If you cat this, you will see the raw contents of HDQ device register space. This is the bq27000 couloumb counter in our case.
====/sys/devices/platform/gta02-hdq.0/hdq/write====
This allows you to write to raw HDQ registers, using "<decimal register index> <decimal value>"

===power_supply battery information===
Most of these are coming from the coulomb counter over HDQ dynamically, but the bq27000 does not update a lot of its registers any more often than once per 4 seconds. Therefore a lot of this info can be a bit stale or averaged over that period.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/uevent====
All informations about battery.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/type====
Just says "Battery"
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/status====
This will summarize what goes on generally with the battery
* "Not Charging" - there's a charger in, but right now it isn't charging us. Normal if you are fully charged and still powered.
* "Charging" - there's a charger in and it is charging the battery
* "Discharging" - we are running on battery
* "Full" - not normally given as a result (Not Charging used instead)
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/voltage_now====
Battery voltage in uV, averaged. Obviously this depends on load and place on discharge curve, etc.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/current_now====
Current being drawn from battery (+ve) or pushed into battery during charging (-ve) in uA
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/charge_full====
Coulomb Counter's estimate of the capacity of the battery measured in uA/h. It roughly means that if full, for one hour it could supply current at this rate. I saw 1197913 reported on mine, so it estimates it can provide 1.2A for an hour.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/temp====
This is the battery temperature reported by the Coulomb Counter chip that is part of the physical battery. It is in Celcius * 10, so 251 means 25.1 degrees.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/technology====
"Li-ion"
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/present====
* "0" the battery is absent, or not one with a Coulomb Counter
* "1" the smart battery is present
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/time_to_empty_now====
At current rate of discharge, estimate of how long we can run for. If battery is not discharging, it won't make an estimate and will return a magic value "3932100" meaning "no estimate". The coulomb counter averages the load and adjusts this value slowly to be its estimate of when we will blow chunks.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/time_to_full_now====
This estimates how long until we are fully charged, at current rate of charging, in seconds. If we are not charging, it gives the magic value "3932100" meaning "no estimate".
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/capacity====
This is the remaining capacity of charge in the battery in percent. This is probably the most useful figure here.
====/sys/devices/platform/bq27000-battery.0/power_supply/bat/online====
* "0" no charger is present
* "1" A powered charger is present

===PMU info===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/chgmode====
* "enabled" means the charger is powered and willing to charge, although if you're full it might not be right now
* "disabled" means there was no power or not enough power supplied to charge

Looks like it may also report "fast" here. [[User:OlivierBerger|OlivierBerger]] 07:47, 25 July 2008 (UTC)

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/charger_type====
Shows the detected charger type followed by the mode it is running in. So "charger 500mA mode 100mA" would be the case for non-enumerated USB connection, "charger 500mA mode 500mA" for after enumeration (or "host/500mA usb mode 500mA" as here [[User:OlivierBerger|OlivierBerger]]).

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous====
This is added to allow the PMU to be told to take more current than the default rules allow. Use it only if you know your charger source can handle it. For example

echo 500 > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/force_usb_limit_dangerous

will allow PMU to draw 500mA even though you are connected to a dumb charger where the limit is normally held at 100mA, since it didn't enumerate the GTA02. You can give 0, 100, 500 or 1000 here, but make sure your charger source can handle what you give here, otherwise it can exceed what is safe for your charging source to provide.

More details at [[Forcing_fast_charge_mode]].

====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/dump_regs====
cat this to get a dump of the I2C registers for the PMU, useful for debugging power problems.

===Bluetooth===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/power_on====
* Default "0" no power to Bluetooth device
* set to "1" to enable power to Bluetooth
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-bt.0/reset====
* Default to "0", no reset
* set to "1" to reset BT (needed after powerup)

===GPS===
====/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron====
* Default "0" GPS unpowered
* set to "1" to power GPS section

===Audio codec===
====/sys/devices/platform/soc-audio/codec_reg====
cat this to get a dump of codec registers. Note they are 9-bit wide.
====/sys/devices/platform/soc-audio/codec_reg_write====
You can write to any codec register by echoing "<codec reg index in hex> <value in hex>" to here

===Glamo===
====/sys/devices/platform/glamo3362.0/regs====
cat this to get a dump of selected Glamo regs. You can write the regs by echoing "<glamo reg index in decimal> <value in decimal>" here.

===LED & Vibrator===
(per: Jeff Tickle)
====/sys/devices/platform/neo1973-vibrator.0/leds/neo1973:vibrator/brightness====

For the Vibration, my very limited testing indicates it will accept a
range of 0-255, with 0 being off and 255 being full force. So, you can
actually set the strength of vibration.

Keep in mind that the vibration will positively eat your battery, so
use with caution!

====/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/brightness====
====/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/brightness====
====/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/brightness====

For the LEDs, you can echo 1 for on or 0 for off to any of these files
to control the state of the LEDs.

===Accelerometers===
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/power/wakeup====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/power/wakeup====
Turns on accelerometers.

====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/dump====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/dump====
Dumps accelerometers raw contents.

====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/full_scale====
====/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.1/full_scale====
Switches the accelerometers between 2G and 8G mode. Echo "9.2" into it for 8G, any other value for 2G (default)[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/004029.html]

[[Category:Flashing Openmoko]]
[[Category:System Developers]]

Specialized USB cables

2008-11-23T02:20:03Z

Jidanni: /* How to make a USB cable for powering attached USB devices and charging the Neo while in host mode */ Type A plugs have four slots, not 5 pins

{{note|work in progress}}

== Attaching the Neo (acting as a USB host) to a USB device ==

The USB port (5 position mini type B jack) on the Neo 1973 and Neo FreeRunner can be both a USB device or a USB host. The provided cable (5 position mini type B plug to type A plug) is used when attaching the Neo to a USB host.

A specialized cable is required when attaching the Neo to a USB device. (The device has a USB type A jack).

(picture)

Alternately, an adapter capable of connecting two type A plugs will allow attaching the provided USB cable to the USB cable that came with the USB device. This adapter is also known as a gender changer.

(picture)

=== Ready-made mini type A plug to a type A jack adapter ===

You can now purchase a proper [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 custom-manufacturered mini-A to full-sized A USB adapter from here]. This adapter already has Pins 4 and 5 shorted together internally; the unique form factor also makes it very handy and eliminated the need for things like the double USB female adapter trick shown at the bottom of this page.

[[Image:USBOTGSwivel.jpg]]

=== Ready-made mini type B plug to a type A jack cable ===

You can buy [[http://www.jaykang.com/usbafetousbm1.html this]] ready-made USB A-Type Female to USB Mini-B Type 5 Pin Male Adapter.
[[Image:jaykang_usbafetousbm1.jpg|thumb|none]]

A Mini-B to Female-A cable is also available from [http://www.usbfirewire.com/Parts/rr-2mb-020.html www.usbfirewire.com].

=== How to make a mini type B plug to a type A jack cable ===

(picture, as soon as I build it)

Parts list:

* Mini type B plug: Digi-Key [[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=H2958-ND H2958-ND]]
* type A jack: I have not yet been able to find a source for these. Meanwhile, use the jack from a standard USB extension cord
* Cable: Ideally, the data lines should be twisted and 28 AWG, the power lines should be 20 or 28 AWG, e.g. Hitachi Cable [[http://www.hcm.hitachi.com/electronic_round_cable/bulk-usb-cable.shtml 49248 ]]

Construction instructions:

(TBA)

=== Ready-made type A jack to a type A jack adapter (gender changer) ===

You can buy [[http://www.jaykang.com/usbtyfetotyf.html this]] ready-made USB Type A Female to Female Gender Changer.
[[Image:jaykang_usbtyfetotyf.jpg|thumb|none]]

=== How to make a type A jack to a type A jack adapter (gender changer) ===

This community provided instruction shows how to build an adapter from a USB socket salvaged from a computer motherboard.

Note that these instructions are provided in the hope that they are useful but without any warranty!

[[Image:2-usb-receptables.jpg|thumb|none]]

:#Find an old motherboard with a set of two USB receptacles as shown above.
:#Desolder this set of receptacles from the motherboard. This can be bit tricky but it is doable at least with a desoldering gun.
:#Each receptacle has four pins. Use a multimeter to verify that you have no short circuits between the pins or the shield.
:#Solder adjacent pins together (GND to GND, D- to D-, D+ to D+, VCC to VCC).
:#(Optional) Build a test cable. Cut an USB cable with A plug into half, connect it a receptacle and again measure that you have no short circuits. Then connect the test cable to PC and verify that you see
*black GND
*green 0V
*white 0V
*red +5V
:#FreeRunner is shipped with a mini-B-to-A-plug cable. Connect this to a receptacle.
:#(Optional)Connect test cable to the other receptacle and verify that you see
*black GND
*green 0V
*white 0V
*red 0V
when freerunner acts as a device and
*black GND
*green 0V
*white 0V
*red +5V
when it acts as a host.
:#At your own risk, switch freerunner to USB host mode and connect an USB device to the other receptacle of the adapter. Here's how the setup should look like:

<gallery>
Image:Usb-gender-changer1.jpg
Image:Usb-gender-changer2.jpg
</gallery>

=== How to make a type A jack to a type A jack adapter (gender changer) without soldering ===

:#Find a 2-port USB front-panel with a 9-pin connector. Usually you can get one from a PC motherboard package box.
:#Align it in a way so you see the connector pins as a 2 row 5 column matrix with one pin missing.
:#Use 4 staples to short the pins residing in a same column.
:#FreeRunner is shipped with a mini-B-to-A-plug cable. Use it to connect the first port of your panel with your FreeRunner.
:#At your own risk, switch freerunner to USB host mode and connect an USB device to the other receptacle of the adapter.

If you have a ASUS USB/MIR front panel, it is even easier - you can use jumpers to short the pins.

[[Image:asususb.jpg]]

=== Compatibility ===

The adapter works with kingston data traveller 4G memory stick and aiptec pencam webcam. However, for some reason (probably the missing 15k resistors at D+ and D-) it did not work with any of the tested USB keyboards or mice:
<pre>
usb 1-2: new full speed USB device using s3c2410-ohci and address 24
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 25
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 26
usb 1-2: device not accepting address 26, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 27
usb 1-2: device not accepting address 27, error -62
</pre>
However, if I connect neo to small (unpowered) USB hub
<pre>
usb 1-2: new full speed USB device using s3c2410-ohci and address 61
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
</pre>
and connect the keyboard to the hub then it is correctly recognized:
<pre>
usb 1-2.3: new low speed USB device using s3c2410-ohci and address 62
usb 1-2.3: configuration #1 chosen from 1 choice
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.0/input/input13
input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-s3c24xx-2.3
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.1/input/input14
input: USB HID v1.10 Device [ USB Keyboard] on usb-s3c24xx-2.3
</pre>
With the hub I can also use both keyboard and usb memory stick at the same time.

==== Power consumption ====

When I unplug the USB hub (with only keyboard connected to it) the power consumption estimate at /sys/devices/platform/bq2700-battery.0/power_supply/bat/current_now decreases from 175000 to 145000 (are these microamperes?).

== How to make a USB cable for powering attached USB devices and charging the Neo while in host mode ==

{{note|work in progress}}

This cable might be necessary for a number of reasons, e.g.

* The application requires that the Neo not become suspended
* The application requires long run time
* The attached USB device consumes a lot of power

(However, as there is a wide range[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.hardware/415]
of USB hubs out there, one might find power (on a powered USB hub)
is available already on the hub's mini USB 5 pin socket already, so not need a specialized cable after all!
Check with a test meter.)

These instructions will show you how to make a cable with 3 ends:

* A mini-USB type B cable for the Neo itself
* A cable of whatever type to go to your USB device.
* A cable going to a +5V +/-10%(max!) power supply with enough power for your device and to charge the Neo. This could be a wall charger or even another USB plug.

You connect the Data+ and Data- wires of the Neo and the device, and connect all of the ground wires together and all of the +5V wires together. This powers the Neo and the device, while letting the neo talk to the device.
You have to connect 2 pcs 15k ohm resistors, one from D+ to ground, and one from D- to ground, to comply with USB-spec for hostmode, as Neo is switching off the internal resistors when you enable charging/powering over USB by asserting EN_USBHOST.
See schematics, LOCATION:49XX

Just for reference, the USB wires from left to right are:
*Black: Power -
*Green: Data -
*White: Data +
*Red: Power +

The Mini_USB-B connector has a fifth pin, the ID-pin.
This pin is supposed to be short to ground to signal FreeRunner to enter hostmode. For the Y-cable and enabling external power while in hostmode, you may connect a 47k ohm resistor from ID-pin to ground. This is the same trick the OM-wallcharger uses to signal to FreeRunner it can charge with 1A. Future kernels should switch to hostmode + external power when seeing this 47k resistor.

===Parts===
USB 2.0 Plug type A to mini 5 pin USB Plug type B that should include the ID signal, so that you can add the 47k ohm resistor to ID-pin to trigger fast charging

# [http://www.firefold.com/Products/6-Foot-USB-20-Plug-type-A-to-mini-USB-Plug-type-B-5-pin-Cable---Black__USB-5PMINI-6.aspx firefold]
# Belkin 5 pin (find reference)

[[Category:USB]]
[[Category:Neo FreeRunner Hardware]]

Specialized USB cables

2008-11-23T02:12:00Z

Jidanni: /* How to make a USB cable for powering attached USB devices and charging the Neo while in host mode */ grammar

{{note|work in progress}}

== Attaching the Neo (acting as a USB host) to a USB device ==

The USB port (5 position mini type B jack) on the Neo 1973 and Neo FreeRunner can be both a USB device or a USB host. The provided cable (5 position mini type B plug to type A plug) is used when attaching the Neo to a USB host.

A specialized cable is required when attaching the Neo to a USB device. (The device has a USB type A jack).

(picture)

Alternately, an adapter capable of connecting two type A plugs will allow attaching the provided USB cable to the USB cable that came with the USB device. This adapter is also known as a gender changer.

(picture)

=== Ready-made mini type A plug to a type A jack adapter ===

You can now purchase a proper [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 custom-manufacturered mini-A to full-sized A USB adapter from here]. This adapter already has Pins 4 and 5 shorted together internally; the unique form factor also makes it very handy and eliminated the need for things like the double USB female adapter trick shown at the bottom of this page.

[[Image:USBOTGSwivel.jpg]]

=== Ready-made mini type B plug to a type A jack cable ===

You can buy [[http://www.jaykang.com/usbafetousbm1.html this]] ready-made USB A-Type Female to USB Mini-B Type 5 Pin Male Adapter.
[[Image:jaykang_usbafetousbm1.jpg|thumb|none]]

A Mini-B to Female-A cable is also available from [http://www.usbfirewire.com/Parts/rr-2mb-020.html www.usbfirewire.com].

=== How to make a mini type B plug to a type A jack cable ===

(picture, as soon as I build it)

Parts list:

* Mini type B plug: Digi-Key [[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=H2958-ND H2958-ND]]
* type A jack: I have not yet been able to find a source for these. Meanwhile, use the jack from a standard USB extension cord
* Cable: Ideally, the data lines should be twisted and 28 AWG, the power lines should be 20 or 28 AWG, e.g. Hitachi Cable [[http://www.hcm.hitachi.com/electronic_round_cable/bulk-usb-cable.shtml 49248 ]]

Construction instructions:

(TBA)

=== Ready-made type A jack to a type A jack adapter (gender changer) ===

You can buy [[http://www.jaykang.com/usbtyfetotyf.html this]] ready-made USB Type A Female to Female Gender Changer.
[[Image:jaykang_usbtyfetotyf.jpg|thumb|none]]

=== How to make a type A jack to a type A jack adapter (gender changer) ===

This community provided instruction shows how to build an adapter from a USB socket salvaged from a computer motherboard.

Note that these instructions are provided in the hope that they are useful but without any warranty!

[[Image:2-usb-receptables.jpg|thumb|none]]

:#Find an old motherboard with a set of two USB receptacles as shown above.
:#Desolder this set of receptacles from the motherboard. This can be bit tricky but it is doable at least with a desoldering gun.
:#Each receptacle has four pins. Use a multimeter to verify that you have no short circuits between the pins or the shield.
:#Solder adjacent pins together (GND to GND, D- to D-, D+ to D+, VCC to VCC).
:#(Optional) Build a test cable. Cut an USB cable with A plug into half, connect it a receptacle and again measure that you have no short circuits. Then connect the test cable to PC and verify that you see
*black GND
*green 0V
*white 0V
*red +5V
:#FreeRunner is shipped with a mini-B-to-A-plug cable. Connect this to a receptacle.
:#(Optional)Connect test cable to the other receptacle and verify that you see
*black GND
*green 0V
*white 0V
*red 0V
when freerunner acts as a device and
*black GND
*green 0V
*white 0V
*red +5V
when it acts as a host.
:#At your own risk, switch freerunner to USB host mode and connect an USB device to the other receptacle of the adapter. Here's how the setup should look like:

<gallery>
Image:Usb-gender-changer1.jpg
Image:Usb-gender-changer2.jpg
</gallery>

=== How to make a type A jack to a type A jack adapter (gender changer) without soldering ===

:#Find a 2-port USB front-panel with a 9-pin connector. Usually you can get one from a PC motherboard package box.
:#Align it in a way so you see the connector pins as a 2 row 5 column matrix with one pin missing.
:#Use 4 staples to short the pins residing in a same column.
:#FreeRunner is shipped with a mini-B-to-A-plug cable. Use it to connect the first port of your panel with your FreeRunner.
:#At your own risk, switch freerunner to USB host mode and connect an USB device to the other receptacle of the adapter.

If you have a ASUS USB/MIR front panel, it is even easier - you can use jumpers to short the pins.

[[Image:asususb.jpg]]

=== Compatibility ===

The adapter works with kingston data traveller 4G memory stick and aiptec pencam webcam. However, for some reason (probably the missing 15k resistors at D+ and D-) it did not work with any of the tested USB keyboards or mice:
<pre>
usb 1-2: new full speed USB device using s3c2410-ohci and address 24
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 25
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 26
usb 1-2: device not accepting address 26, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 27
usb 1-2: device not accepting address 27, error -62
</pre>
However, if I connect neo to small (unpowered) USB hub
<pre>
usb 1-2: new full speed USB device using s3c2410-ohci and address 61
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
</pre>
and connect the keyboard to the hub then it is correctly recognized:
<pre>
usb 1-2.3: new low speed USB device using s3c2410-ohci and address 62
usb 1-2.3: configuration #1 chosen from 1 choice
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.0/input/input13
input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-s3c24xx-2.3
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.1/input/input14
input: USB HID v1.10 Device [ USB Keyboard] on usb-s3c24xx-2.3
</pre>
With the hub I can also use both keyboard and usb memory stick at the same time.

==== Power consumption ====

When I unplug the USB hub (with only keyboard connected to it) the power consumption estimate at /sys/devices/platform/bq2700-battery.0/power_supply/bat/current_now decreases from 175000 to 145000 (are these microamperes?).

== How to make a USB cable for powering attached USB devices and charging the Neo while in host mode ==

{{note|work in progress}}

This cable might be necessary for a number of reasons, e.g.

* The application requires that the Neo not become suspended
* The application requires long run time
* The attached USB device consumes a lot of power

(However, as there is a wide range[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.hardware/415]
of USB hubs out there, one might find power (on a powered USB hub)
is available already on the hub's mini USB 5 pin socket already, so not need a specialized cable after all!
Check with a test meter.)

These instructions will show you how to make a cable with 3 ends:

* A mini-USB type B cable for the Neo itself
* A cable of whatever type to go to your USB device.
* A cable going to a +5V +/-10%(max!) power supply with enough power for your device and to charge the Neo. This could be a wall charger or even another USB plug.

You connect the Data+ and Data- wires of the Neo and the device, and connect all of the ground wires together and all of the +5V wires together. This powers the Neo and the device, while letting the neo talk to the device.
You have to connect 2pcs 15kOhm resistors, one from D+ to ground, and one from D- to ground, to comply with USB-spec for hostmode, as Neo is switching off the internal resistors when you enable charging/powering over USB by asserting EN_USBHOST.
See schematics, LOCATION:49XX

Just for reference, the USB wires from left to right are:
*Black: Power -
*Green: Data -
*White: Data +
*Red: Power +

The Mini_USB-B connector has a fifth pin, the ID-pin.
This pin is supposed to be short to ground to signal FreeRunner to enter hostmode. For the Y-cable and enabling external power while in hostmode, you may connect a 47k ohm resistor from ID-pin to ground. This is the same trick the OM-wallcharger uses to signal to FreeRunner it can charge with 1A. Future kernels should switch to hostmode + external power when seeing this 47k resistor.

===Parts===
5 pin USB 2.0 Plug type A to mini USB Plug type B that should include the ID signal, so that you can add the 47kOhm resistor to ID-pin to trigger fast charging

# [http://www.firefold.com/Products/6-Foot-USB-20-Plug-type-A-to-mini-USB-Plug-type-B-5-pin-Cable---Black__USB-5PMINI-6.aspx firefold]
# Belkin 5 pin (find reference)

[[Category:USB]]
[[Category:Neo FreeRunner Hardware]]

Wiki Issues

2008-11-22T01:04:13Z

Jidanni: /* Change Sitename */ asking for trouble

If you think something is wrong with a Wiki page, please fix it. If the problem is larger with this Wiki in general, please add your thoughts on this page and mail the openmoko [http://lists.openmoko.org/mailman/listinfo/documentation documentation mailing list]. You may just want to read existing proposals and put your vote on them, [[Wiki Maintainers]] will appreciate. [[Wiki Maintenance Agenda]].

When adding an issue please

* Provide a reason
* Provide your name as vote for the action to be taken (you can automatically enter your username by typing "
<nowiki>~~~</nowiki> ")

{{Warning|Comments without name might be deleted without consideration. We may need to ask for more information before implementing a proposal. Thanks for understanding.}}

Accepted and implemented requests should be deleted. Rejected requests should be moved to the bottom of the page to avoid requesting them again.

==Wiki Pages==

I think that we should use specific "editor's notes templates" rather that nominate individual pages here. We can make automatic list of pages using a given template by having a Category:X tag inside the template. See for example the [[:Category:ToDo]] . [[User:MinhHaDuong|MinhHaDuong]] 09:44, 7 October 2008 (UTC)

===Pages capable of development===
* [[Openmoko:Community Portal]]
* [[AR6K]] (Needs more info)
* [[GTA02 partitions]]: seems to be about the GTA01; could someone with a GTA02 please correct the partition sizes and names?
* [[Advanced_End-user]], [[Basic_End-user]], [[System_Developer]]: These are not up to the standard we set for List Pages on [[Openmoko_Wiki_Editing_Guidelines#List_pages]] [[User:Kempelen|Kempelen]]

===Redundant Pages===
* There are several pages concerning Openmoko compatible service providers:
** [[Carriers]], most up-to-date, confirmed service providers.
*** [[Carriers/ATT]]
*** [[Carriers/TMobile]]
*** [[Carriers/Fido]]
*** [[Carriers/Rogers]]
** [[Neo1973 compatible cellphone providers]]

*I suggest merging the editing help pages:
**[[Help:Editing]]
**[[Edit Wiki]]

*pages about GPS:
**[[Hardware:AGPS]]
**[[Gpsd]]
**[[Neo 1973 GPS]]
**[[Neo FreeRunner GPS]]

*applications:
**[[Available Packages]]
**[[Applications]]
**[[Applications directory]]
**[[Om 2007.2 Applications]]

===Tidy up===
* [[Wishlist:Text Input]] - tidy up/sort, give short feedback to each method
* [[Booting_from_SD]] - tidy up and a rewrite

=== Pages proposed for deletion ===

'''Please help cleaning these''': Check if there is a red (nonexisting) link in this table, click it, click "What links here" in the toolbox and '''update the broken links'''. When done, remove the deleted entry from this table.

{| border=1 cellspacing=0
!Page
!Reason
!Yes kill it votes
!No keep it votes
|-
| Nothing is propsed for deletion at the moment || || ||
|}

See also: [[:Category:Candidates for speedy deletion]]

=== Pages that especially need work ===

* [[Special:Lonelypages]] - Orphaned pages
* [[Special:DoubleRedirects]] - Pages that redirect to a redirected page
* [[Special:Popularpages]] - Pages that get viewed a lot
* [[Special:Ancientpages]] - Old pages
* [[Special:Newpages]] - New pages
* [[Special:Wantedpages]] - Wanted pages
* [[Special:Uncategorizedpages]]
* [[Special:Shortpages]] - Informationally light pages
* [[Special:BrokenRedirects]] - Broken redirects

=== Application pages ===

Maturity level ideas from the documentation list copied by [[User:Kempelen|Kempelen]] 19:05, 1 October 2008 (UTC):

* It might be nice to have a single word stating the code maturity, perhaps only 3 simple options like prototype, functional, mature
* Why not stick with pre-alpha, alpha, beta, stable, mature

Decision postponed. :-) (Feel free to vote here anyway.)

== Categories ==

{{Main|:Category talk:Categories}}

== CSS ==

We have discussed design on the mailing list, with the conclusion that revising was not a big priority. However, the wiki should be skinnable from user-space by editing : http://wiki.openmoko.org/wiki/MediaWiki:Common.css . And for development, each user can have his/her own CSS to eat his own dogfood. But I can't seem to make this feature work here.
Reference: http://en.wikipedia.org/wiki/Help:Monobook
[[User:MinhHaDuong|MinhHaDuong]] 12:26, 12 September 2008 (UTC).

* The gutter is too wide
* Too much footer's padding
* Could shave 1 or 2 em of vertical space in the header
* The tabbed navigation layout is non-standard (no framing effect)
* The search box is below the fold (depends on window height of course)
* The toolbox (bottom left) has no border
* Mediawiki's user personal toolbox is prohibited
* Too many links in the navbar that belongs to the home page but not to every page

== Portals ==

We should explore another wiki organization tool: [http://en.wikipedia.org/wiki/Portal:Contents/Portals portals]. A portal is an introductory page for a given topic. It complements the main article of the subject by introducing the reader to key articles, images, and categories that further describe the subject. Portals also help editors find related projects and things they can do to help. [[User:MinhHaDuong|MinhHaDuong]] 13:53, 20 September 2008 (UTC)

== Navigation templates ==

(FYI Description moved to [[Openmoko_Wiki_Editing_Guidelines#Navigation_templates]], [[User:Kempelen|Kempelen]])

* The [[Distributions]] page feature a non-templated navigation box
* We should name these templates distinctly. I suggest using a prefix like "NavBox:".
* Visual design is by hand (not CSS), and not beautiful
* Need to test positioning at bottom of article.

'''References'''

http://en.wikipedia.org/wiki/Wikipedia:Navigation_templates
http://en.wikipedia.org/wiki/Wikipedia:Categories,_lists,_and_series_boxes

[http://lists.openmoko.org/pipermail/documentation/2008-August/000405.html First discussion in the mailing list] (Note: in the middle of a thread about left navboxes)

* '''Yes votes''': [[User:Kempelen|Kempelen]] (For real wikipedia like navigation templates at the bottom, not at TOC position, we should move this section to editing guidelines as soon as template implementation improves a bit. Do not delete this please!)

== DolfjeBot1 proposals ==
Their is a bot on the openmoko wiki that's controlled by [[User:Dolfje]]. If you have tasks for the bot, please put them [[User:DolfjeBot1|here]].
A request has been made to tag DolfjeBot1 user account with the 'bot' flag. [[Special:Listusers/bureaucrat| Here is the lists of users]] with permissions at the necessary `bureaucrat' level.

==Wiki engine issues==

=== Disappearing Pre-formatting ===
There is an issue with pre-formatting disappearing when people edit. See for instance recent edits here:

http://wiki.openmoko.org/index.php?title=Accelerometer_data_retrieval&diff=59334&oldid=55556

Actually I thing it's whitespace in general that is lost since python/ruby code is also messed up.
I have confirmed that this happens cross browser (both firefox3 and opera), but not on all pages, and not for all people.

[[User:Gromgull|Gromgull]] 10:47, 9 November 2008 (UTC)

Yes, it is driving me bananas and must me due to some
[[Special:Version#Hooks|hook]] the maintainers have added.

<pre>
In standard MediaWiki, a mere space at the beginning of these lines
will produce this box. But no, here on this wiki, one needs

<nowiki><pre></nowiki> , and your spaces get eaten.
The problem can be isolated as even returning mangled code in the edit box when you hit
the preview button. Never on real MediaWiki has anything dared to return a mangled edit box before.
Indeed the contents of this very paragraph have been jumbled by it. I have no control. Indeed, do
you see that gap above? It grows with each edit.
</pre>
On the [http://jidanni.org/comp/index.html wikis I maintain], I never go hog-wild adding too many hooks.

This bug got me. I managed to fix the page I accidentally broke, but apparently it causes the preformatted text to slowly sink into ordinary text with each edit, making the
wiki less readable, for example see: http://wiki.openmoko.org/index.php?title=GPRS_FSO&oldid=55571 and http://wiki.openmoko.org/index.php?title=GPRS_FSO .
This should be fixed ASAP, as it makes the quality of the wiki do down. :-( [[User:Zub|zub]] 00:47, 18 November 2008 (UTC)

====Emergency: eating categories off the bottom of pages====
=====Proof of Category eating=====
...Oh, the categories only disappear temporarily, due to http://www.mediawiki.org/wiki/Extension:SelectCategoryTagCloud .
OK, sorry for the alarm. [[User:Jidanni|Jidanni]] 04:08, 16 November 2008 (UTC)
----

Can we please install/fix the following features for this wiki:
* '''Math''' - the Tex math markup does not work currently. Test:
** <math> z =\left (1-\left(\frac{P_{ind}}{101.325}\right)^{0.190263} \right ) \times \frac{87.828}{0.00198122} </math>
** <math> P_{ind} </math>
* [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi '''Syntax''' Highlighting - makes code much more readable]
* [http://www.mediawiki.org/wiki/Extension:GraphViz GraphViz] works with the commonly known dot language - it allows us to draw '''graphs''' using easy markup.
* [http://www.mediawiki.org/wiki/Extension:AnyWikiDraw AnyWikiDraw] allows us to draw svg '''diagrams''' directly on the wiki page.
* Make '''visited links''' a different color.

== Change Sitename ==

The name of this wiki is currently "Openmoko". I think it should be "Openmoko Wiki" for the following reasons:

* The other parts of this site (Planet, Projects, Docs) have similar names
* Media Wiki automatically creates a [http://www.mediawiki.org/wiki/Manual:Namespace namespace] for the Sitename (currently "Openmoko"). This means that content of pages beginning with "Openmoko:" cannot be found through the normal search function of this wiki. (At the moment there are five pages of this kind: [[Openmoko:About]], [[Openmoko:Community Portal]], [[Openmoko:Current events]], [[Openmoko:Searching]], [[Openmoko:Privacy policy]])--[[User:Marko Knöbl|Marko Knöbl]] 18:33, 8 August 2008 (UTC)

'''Yes votes''': [[User:Marko Knöbl|Marko Knöbl]], [[User:MinhHaDuong|Minh]]

'''No votes''':

::OpenmokoIT still do some research now. [[User:Coolcat|coolcat]]

::Then fix the search function (by restoring the standard MediaWiki search function). Anyway they are [[Special:Allpages/Openmoko:]]. Anyway, any links like [[Special:Allpages/Openmoko:]] will break, unless you use [[Special:Allpages/Project:]]. Furthermore, the longer the name of the Project ($wgSitename) becomes, the longer the UTF-8 translations of it will become, and as e.g., for Chinese UTF-8 at 3*3=9 ASCII %XX%XX%XX per character, you'll end up with mile long URLs before long, that is if one day the site becomes fully translated. [[User:Jidanni|Jidanni]] 01:04, 22 November 2008 (UTC)

== Organize translations ==

I suggest moving the translations to sub-wikis, like the way wikipedia does it. Currently all translations show up in searches and under category-lists. --[[User:Johndoesacc|Johndoesacc]] 12:03, 25 August 2008 (UTC)

+1. See issues and solutions for a multilingual mediawiki at:
http://www.mediawiki.org/wiki/Multilingual_MediaWiki
Also, the correspondence between translation should be maintained with tags:
http://en.wikipedia.org/wiki/Help:Interlanguage_links
The request [http://lists.openmoko.org/pipermail/documentation/2008-September/000557.html has been heard] but maybe not in the right places. What is the best operational frequency to ping the hosting engineers for that ? [[User:MinhHaDuong|MinhHaDuong]] 13:02, 10 September 2008 (UTC)

After discussion on the Documentation ML, sub-wikis are out. We want to try namespaces. [[User:MinhHaDuong|MinhHaDuong]] 09:31, 7 October 2008 (UTC)

== Downloads ==

=== Symlinks in download directories ===

This is not strictly Wiki issue, but discussed on the documentation list as being a serious usability disadvantage. Symlinks and .tar.gz files should be removed from the release directories because they confuse users. Ref: [http://lists.openmoko.org/pipermail/documentation/2008-September/000808.html]

=== Improve README.html ===

Example: http://downloads.openmoko.org/releases/Om2008.9/README.html

It should at least link to: [[Om_2008.9_Update#Download_and_Flashing]]

== Rejected requests ==

When a requested Wiki Issue is voted for not to be done, it must be moved here, to make sure it won't get continously requested again.

* '''Don't translate the wiki - rejected''' proposed by [[User:Minime|Minime]] August 2007, moved to rejected by [[User:Kempelen|Kempelen]] August 2008: the Documentation Team looks to support the idea.
* '''Use namespaces to separate user-oriented and developper-oriented content'''. Assuming the default namespace is user-oriented that would exclude developper-oriented pages from searches (unless the user ticks the box, but who does ?). And it can't be done purely in the wiki, it needs admin time. Better to use categories and a prefix in the page name (like BlendeWiki). [[:User:MinhHaDuong|MinhHaDuong]]
* '''Use category pages instead List Pages''' Good list pages are allowed and encouraged, as the documentation team today agreed on the mailing list. [[User:Kempelen|Kempelen]] 21:27, 30 August 2008 (UTC)

[[Category:Wiki Editing]]

Specialized USB cables

2008-11-22T00:48:38Z

Jidanni: /* Providing power to run and charge the Neo while in host mode */ power might already be available

{{note|work in progress}}

== Attaching the Neo (acting as a USB host) to a USB device ==

The USB port (5 position mini type B jack) on the Neo 1973 and Neo FreeRunner can be both a USB device or a USB host. The provided cable (5 position mini type B plug to type A plug) is used when attaching the Neo to a USB host.

A specialized cable is required when attaching the Neo to a USB device. (The device has a USB type A jack).

(picture)

Alternately, an adapter capable of connecting two type A plugs will allow attaching the provided USB cable to the USB cable that came with the USB device. This adapter is also known as a gender changer.

(picture)

=== Ready-made mini type A plug to a type A jack adapter ===

You can now purchase a proper [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 custom-manufacturered mini-A to full-sized A USB adapter from here]. This adapter already has Pins 4 and 5 shorted together internally; the unique form factor also makes it very handy and eliminated the need for things like the double USB female adapter trick shown at the bottom of this page.

[[Image:USBOTGSwivel.jpg]]

=== Ready-made mini type B plug to a type A jack cable ===

You can buy [[http://www.jaykang.com/usbafetousbm1.html this]] ready-made USB A-Type Female to USB Mini-B Type 5 Pin Male Adapter.
[[Image:jaykang_usbafetousbm1.jpg|thumb|none]]

A Mini-B to Female-A cable is also available from [http://www.usbfirewire.com/Parts/rr-2mb-020.html www.usbfirewire.com].

=== How to make a mini type B plug to a type A jack cable ===

(picture, as soon as I build it)

Parts list:

* Mini type B plug: Digi-Key [[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=H2958-ND H2958-ND]]
* type A jack: I have not yet been able to find a source for these. Meanwhile, use the jack from a standard USB extension cord
* Cable: Ideally, the data lines should be twisted and 28 AWG, the power lines should be 20 or 28 AWG, e.g. Hitachi Cable [[http://www.hcm.hitachi.com/electronic_round_cable/bulk-usb-cable.shtml 49248 ]]

Construction instructions:

(TBA)

=== Ready-made type A jack to a type A jack adapter (gender changer) ===

You can buy [[http://www.jaykang.com/usbtyfetotyf.html this]] ready-made USB Type A Female to Female Gender Changer.
[[Image:jaykang_usbtyfetotyf.jpg|thumb|none]]

=== How to make a type A jack to a type A jack adapter (gender changer) ===

This community provided instruction shows how to build an adapter from a USB socket salvaged from a computer motherboard.

Note that these instructions are provided in the hope that they are useful but without any warranty!

[[Image:2-usb-receptables.jpg|thumb|none]]

:#Find an old motherboard with a set of two USB receptacles as shown above.
:#Desolder this set of receptacles from the motherboard. This can be bit tricky but it is doable at least with a desoldering gun.
:#Each receptacle has four pins. Use a multimeter to verify that you have no short circuits between the pins or the shield.
:#Solder adjacent pins together (GND to GND, D- to D-, D+ to D+, VCC to VCC).
:#(Optional) Build a test cable. Cut an USB cable with A plug into half, connect it a receptacle and again measure that you have no short circuits. Then connect the test cable to PC and verify that you see
*black GND
*green 0V
*white 0V
*red +5V
:#FreeRunner is shipped with a mini-B-to-A-plug cable. Connect this to a receptacle.
:#(Optional)Connect test cable to the other receptacle and verify that you see
*black GND
*green 0V
*white 0V
*red 0V
when freerunner acts as a device and
*black GND
*green 0V
*white 0V
*red +5V
when it acts as a host.
:#At your own risk, switch freerunner to USB host mode and connect an USB device to the other receptacle of the adapter. Here's how the setup should look like:

<gallery>
Image:Usb-gender-changer1.jpg
Image:Usb-gender-changer2.jpg
</gallery>

=== How to make a type A jack to a type A jack adapter (gender changer) without soldering ===

:#Find a 2-port USB front-panel with a 9-pin connector. Usually you can get one from a PC motherboard package box.
:#Align it in a way so you see the connector pins as a 2 row 5 column matrix with one pin missing.
:#Use 4 staples to short the pins residing in a same column.
:#FreeRunner is shipped with a mini-B-to-A-plug cable. Use it to connect the first port of your panel with your FreeRunner.
:#At your own risk, switch freerunner to USB host mode and connect an USB device to the other receptacle of the adapter.

If you have a ASUS USB/MIR front panel, it is even easier - you can use jumpers to short the pins.

[[Image:asususb.jpg]]

=== Compatibility ===

The adapter works with kingston data traveller 4G memory stick and aiptec pencam webcam. However, for some reason (probably the missing 15k resistors at D+ and D-) it did not work with any of the tested USB keyboards or mice:
<pre>
usb 1-2: new full speed USB device using s3c2410-ohci and address 24
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 25
usb 1-2: device descriptor read/64, error -62
usb 1-2: device descriptor read/64, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 26
usb 1-2: device not accepting address 26, error -62
usb 1-2: new full speed USB device using s3c2410-ohci and address 27
usb 1-2: device not accepting address 27, error -62
</pre>
However, if I connect neo to small (unpowered) USB hub
<pre>
usb 1-2: new full speed USB device using s3c2410-ohci and address 61
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
</pre>
and connect the keyboard to the hub then it is correctly recognized:
<pre>
usb 1-2.3: new low speed USB device using s3c2410-ohci and address 62
usb 1-2.3: configuration #1 chosen from 1 choice
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.0/input/input13
input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-s3c24xx-2.3
input: USB Keyboard as /devices/platform/s3c2410-ohci/usb1/1-2/1-2.3/1-2.3:1.1/input/input14
input: USB HID v1.10 Device [ USB Keyboard] on usb-s3c24xx-2.3
</pre>
With the hub I can also use both keyboard and usb memory stick at the same time.

==== Power consumption ====

When I unplug the USB hub (with only keyboard connected to it) the power consumption estimate at /sys/devices/platform/bq2700-battery.0/power_supply/bat/current_now decreases from 175000 to 145000 (are these microamperes?).

== How to make a USB cable for powering attached USB devices and charging the Neo while in host mode ==

{{note|work in progress}}

This cable might be necessary for a number of reasons, e.g.

* The application requires that the Neo not become suspended
* The application requires long run time
* The attached USB device consumes a lot of power

(However, as there is a wide range[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.hardware/415]
of USB hubs out there, one might find power (on a powered USB hub)
is available already on the hub's mini USB 5 pin socket already, so not need a specialized cable after all!
Check with a test meter.)

These instructions will show you how to make a cable with 3 ends:

* A mini-USB type B cable for the Neo itself
* A cable of whatever type to go to your USB device.
* A cable going to a +5V +/-10%(max!) power supply with enough power for your device and to charge the Neo. This could be a wall charger or even another USB plug.

You connect the Data+ and Data- wires of the Neo and the device, and connect all of the ground wires together and all of the +5V wires together. This powers the Neo and the device, while letting the neo talk to the device.
You have to connect 2pcs 15kOhm resistors, one from D+ to ground, and one from D- to ground, to comply with USB-spec for hostmode, as Neo is switching off the internal resistors when you enable charging/powering over USB by asserting EN_USBHOST.
See schematics, LOCATION:49XX

Just for reference, the USB wires from left to right are:
*Black: Power -
*Green: Data -
*White: Data +
*Red: Power +

The Mini_USB-B connector has a fifth pin, the ID-pin.
This pin is supposed to be short to ground to signal FreeRunner to enter hostmode. For the Y-cable and enabling external power while in hostmode, you may connect a 47kOhm resistor from ID-pin to ground. This is the same trick the OM-wallcharger uses to signal to FreeRunner it can charge with 1A. Future kernels should switch to hostmode + external power when seeing this 47k resistor.

===Parts===
5 pin USB 2.0 Plug type A to mini USB Plug type B that should include the ID signal, so that you can add the 47kOhm resistor to ID-pin to trigger fast charging

# [http://www.firefold.com/Products/6-Foot-USB-20-Plug-type-A-to-mini-USB-Plug-type-B-5-pin-Cable---Black__USB-5PMINI-6.aspx firefold]
# Belkin 5 pin (find reference)

[[Category:USB]]
[[Category:Neo FreeRunner Hardware]]

USB host

2008-11-22T00:45:54Z

Jidanni: /* Providing power to run and charge the Neo while in host mode */ power might already be available

{{Languages|USB host}}
The mini-USB port on both the Neo 1973 and the Neo FreeRunner supports both USB host and USB device. This opens up a range of possibilities, such as adding USB cameras and USB input devices.

=== Using USB host mode ===
==== Selecting USB host modes ====

By default, the mini-USB port is in device mode. To tell the Neo that it is logically a host¹):

echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode

Independent of the logical mode of the USB port, the Neo FreeRunner can provide 5 volt USB power to an attached USB device. To enable this (not available on Neo 1973):

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note: You may want to run <code>ifconfig usb0 down</code> prior to switching to USB host mode, as the Neo's USB networking may not like having its USB port disappear. You'll probably want to ssh into your Neo over WiFi or Bluetooth before starting all of this, alternatively use an on screen keyboard.

Note that in full USB host mode the FreeRunner will power the external device. To avoid draining the battery use a powered USB hub, then on the FreeRunner enable logical host mode:

~ - echo host > /sys/devices/platform/s3c2410-ohci/usb_mode

but NOT electrical host mode

~ - echo 0 > /sys/devices/platform/neo1973-pm-host.0/hostmode

Note that powered USB hubs do not send power upstream, that is, into the host. If you wish to power or charge the FreeRunner, you will need a [[Specialized USB cables|special USB cable]].

¹)Debian note: You'll need the ohci-hcd module:
modprobe ohci-hcd

* NOTE: with [FSO] based distributions one should use the dbus APIs and not the method stated above.

==== Returning to USB device mode ====
After doing whatever is needed to safely remove your device and unplugging it you can remove the provision of 5 volt power and return to device mode.

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
 
You can now safely restart USB networking.

==== USB-Mode-Script====
These simple script is useful to switch the USB-Modes:
 

<nowiki>#!/bin/sh</nowiki> 
grep -q 'host' /sys/devices/platform/s3c2410-ohci/usb_mode 
if [ $? -eq 0 ] 
then 
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo USB-Port is in device-mode now. 
else 
ifconfig usb0 down 
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode 
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode 
echo USB-Port is in host-mode now. 
fi 
 
You can easily create a push button menu item for this: [http://blogs.thehumanjourney.net/finds/entry/usb_host_mode_the_button Instructions]

==== Using a GUI ====
* Using the packaged push button derived from the script above: [http://blogs.thehumanjourney.net/finds/resource/usbmode-button_0.1_armv4t.ipk Download]
* [[User:Techiem2|Mark D. Montgomery II]]'s [http://techiem2.net/index.php?/archives/10-Freerunner-USB-Mode-Control-Program.html application] controls all the various modes through a GUI
* Thomas Vesely's [http://projects.openmoko.org/projects/usbchmod/ project]
* Using the gtk+ gui [[Framework-settings]]
* Using openmoko-panel-plugin (confirmation and link needed)

=== Providing power to connected USB devices while in host mode ===

Normally, USB host ports provide power to any connected USB device.

Available power in host mode is the full maximum of 500mA according to USB-specifications on the Neo FreeRunner, and no power is available in host mode on the Neo 1973. If your USB device respects USB-standards and consumes not more than 500mA, you may connect it directly to your Neo FreeRunner.

To provide power to USB devices attached to your Neo 1973, or to provide power to your Neo FreeRunner while USB-device connected, you can provide power by using a (modified [for powering FreeRunner]) powered USB hub (see below), or by manually injecting power into the attached USB device (and Neo FreeRunner) via one of the [[specialized_USB_cables]].

=== Powered USB hubs known to work with the Neo ===

(please add any known to work)

=== Providing power to run and charge the Neo while in host mode ===

A slightly separate issue is power to run and charge the Neo (both types) itself. When the USB port is in device mode, the Neo FreeRunner/1973 can be powered and recharged via the USB port, but when in standard host mode, the Neo FreeRunner is set to provide power and does not charge. Fortunately, control of the direction of power (in or out) is independent of the personality of the USB port (host or device):

To recap, the direction of power can be controlled:

Set to 0 (default), no power is provided at the USB port, charging is enabled, and host 15K pulldowns are removed from D+ and D-:

echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Set to 1, provides up to 500mA USB power at the USB port (FreeRunner only), disables charging from USB, and applies 15K pulldowns to USB D+ and D-:

echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Next, power must somehow be injected. An unmodified powered USB hub only provides power to the connected devices, but not to the connected host, so the only solution here is to modify a USB-hub¹) or to create a custom cable which will inject power into the host. See [[specialized_USB_cables]] for some examples.

(However, as there is a wide range[http://permalink.gmane.org/gmane.comp.handhelds.openmoko.hardware/415]
of USB hubs out there, one might find power (on a powered USB hub)
is available already on the hub's mini USB 5 pin socket already, so not need a specialized cable after all!
Check with a test meter.)

Finally, there is the question of charge rate. The charging logic in the Neo will only charge at 100mA by default. Charging at 500mA will take place only if the charging device responds appropriatly to USB negotiation to increase power consumption. Charging at 1000mA will only take place if the Neo detects the appropriate resistor on the ID pins.

You can manually set the charge rate. See [[Forcing_fast_charge_mode]]

¹) often it's sufficient to short a diode in USB-hub to feed power to the host-connector too.
# Edit 05 Oct. 2008 : Not being able to find any diode on my ([[User:Henrikz|Henrikz]]) USB Hub (Brand: Equip, Type: 4 port, aluminum) I simply connected +5V (pin 1) from one of the downstream ports to pin 1 of the upstream port.

=== Power Concerns ===
You'll need to force the Neo to go into fast charge mode, since it can't do its usual power negotiation over USB.

echo -n "fast_cccv" > /sys/devices/platform/s3c2410-i2c/i2c-adapter/i2c-0/0-0008/chgmode

(Also this should be done by kernel when seeing 47K at ID-pin)

=== Working Examples ===

==== USB Keyboard ====

Pictures [http://blogs.thehumanjourney.net/finds/entry/20080716 here]

==== Connecting a USB-Stick ====
[[Image:connecting-usb-stick-1.jpg|thumb|left]]
I found this adapter, it has 2 Type A jacks, rather cheap (about 5 €).
 

[[Image:connecting-usb-stick-2.jpg|thumb|left]]
I borrowed the cable from a card reader, it has the same pinout like the cable that comes with the Neo.
 

[[Image:connecting-usb-stick-3.jpg|thumb|left]]
With the above commands I could mount the memory stick.
 

[[Image:connecting-usb-stick-4.jpg|thumb|left]]
 

[[Category:Neo1973 Hardware]]
[[Category:Neo FreeRunner Hardware]]
[[Category:USB]]

Manually using scap

2008-11-21T19:03:19Z

Jidanni: link to find out what scap means

== Screen shot upload service scap ==

If you don't use the standard gui and your neo lacks the menu entry for scap you can do the same with a simple shell script:

#!/bin/sh -e
n=/tmp/scap$$.png
fbgrab $n
curl \
-F file=@$n \
-F key=secret \
-F model=`uname -n` \
-F submit=Upload \
-F text=no\ comment \
http://scap.linuxtogo.org/tickle.php
rm $n

you need the packages for curl and fbgrab:

ipkg install fbgrab curl

that's all.
==See also==
*[[Gpe-scap]]
[[Category:Application Developer]]

NeoCon

2008-11-21T04:21:22Z

Jidanni: note main feature

'''neocon''' is a handy serial console utility (not only) for [[Bootloader|u-boot]].

'''neocon''' has a few graving advantages over some other terminal apps:

* You don't have to be <code>root</code> to access <code>/dev/ttyACM0</code> with '''neocon'''. Beeing member of <code>dialout</code> should give you sufficient privileges.
* by specifying a delay on keyboard input(as shown below), '''neocon''' will allow you to paste commands directly from clipboard without making [[Bootloader|u-boot]] choke on it.
* '''neocon''' can be started without <code>/dev/ttyACM0</code> being available. It will automatically connect as soon as you start [[Bootloader|u-boot]] on the Neo:

The main feature of neocon is actually that you can give it a list
of devices and it will pick one that works, e.g.,

# neocon /dev/ttyUSB{0,1,2}

If you don't like the one it picked, you can switch to the next with
~n

This is useful for dynamically allocated devices, such as ttyUSBn
or ttyACMn. You can of course also use them with other communication
programs - there's certainly no shortage of them - but then you have
to handle reconnects manually.

==Installation==
Download the source from http://svn.openmoko.org/developers/werner/neocon/ to a directory of your choice and build '''neocon''' by issuing

make

==Usage==
To connect to the [[bootloader]] use

./neocon -t 30 /dev/ttyACM0

To quit neocon type:

~.

An alternative to {{PAGENAME}} is [[picocom]].

[[Category:System Developers]]
[[Category:USB]]

NeoCon

2008-11-21T00:09:21Z

Jidanni: Category:USB

Picocom

2008-11-21T00:08:06Z

Jidanni: broach picocom

An alternative to [[NeoCon]] for connection to one's phone is {{PAGENAME}}.

root@desktop# apt-get install picocom
holmes@desktop$ picocom /dev/ttyACM0
picocom v1.4

port is : /dev/ttyACM0
flowcontrol : none
baudrate is : 9600
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : no
nolock is : no
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv

Terminal ready
In: usbtty
Out: usbtty
Err: usbtty
PCB rev: 0x001
Power: 1000mA
switching led 2 0
switching led 2 1
switching led 2 0
DEVICE_CONFIGURED: 1
## Executing script at 18050100
mtdparts mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
READY.
GTA02v6 # help
help
? - alias for 'help'
askenv - get environment variables from stdin
autoscr - run script from memory
...
[[Category: System Developers]]
[[Category: USB]]

NeoCon

2008-11-21T00:02:10Z

Jidanni: broach picocom

U-Boot environment

2008-11-21T00:00:37Z

Jidanni: /* Console */mention NeoCon

{{Languages|Bootloader environment}}

{{Bootloader}}

The bootloader environment configures the [[bootloader]]. Between reboots, the environment is stored with a checksum in the internal flash [[Partitions|partition]] called "u-boot_env". On the bootloader console, there are [[bootloader commands#Environment|bootloader commands for environment manipulation]].

== Typical environment ==

<pre>
baudrate=115200
bootargs=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
usbtty=cdc_acm
bootdelay=10
stdout=serial
stderr=serial
stdin=serial
mtdparts=mtdparts=neo1973-nand:0x00030000(u-boot),0x0000c000(u-boot_env),0x00200000(kernel),0x00130000(splash),0x03c94000(rootfs)
mtdids=nand0=neo1973-nand
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
pcf50606_int1=0x40
filesize=160C000
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
</pre>

== Timeouts ==

If the boot loader menu is on the screen, the phone will power off when there hasn't been activity for a while. This is not nice if you are working on the boot loader console, but you can make the time longer:
<pre>
setenv boot_menu_timeout [seconds]
</pre>

After the phone is powered on, there is a short period of time when you can connect to the console and cancel the automatic boot without going to the menu:
<pre>
setenv bootdelay [seconds]
</pre>

== Menu ==

You can add items to the boot menu by setting environment variables of the form ''menu_<number>'' to values of the form ''<Title>: U-Boot-Commands''.

For example the following command will add a boot menu entry that switches to autofast charging and turns off the backlight:
setenv menu_6 Autofast-Charge and Backlight Off: neo1973 charger autofast\; neo1973 backlight off

While in this state, your Neo1973 can be charged with a generic USB charger. You also need to set boot_menu_timeout to 65000 to keep it from powering down, though.

=== Booting to the menu ===
To stop in the NAND menu, press and hold the AUX key after pressing the power button at startup. In recent versions of u-boot (builds from august 5 200?), you can also permanently enter the menu by setting the <tt>stop_in_menu</tt> environment variable to <tt>yes</tt>:

setenv stop_in_menu yes
saveenv

to restore normal startup, unset this variable or set it to <tt>no</tt>.

== Console ==

To get access to the bootloader console over USB with e.g., [[NeoCon]], the following settings need to be made:
<pre>
GTA01Bv2 # setenv stderr usbtty
GTA01Bv2 # setenv stdout usbtty
GTA01Bv2 # setenv stdin usbtty
</pre>

== See also ==

* http://lists.openmoko.org/pipermail/community/2008-September/029845.html
* http://markmail.org/message/d2abi2nm5vms3unh

{{Languages|Bootloader}}

[[Category:System Developers]]

U-Boot environment

2008-11-20T23:57:57Z

Jidanni: /* Booting to the menu */what year?

{{Languages|Bootloader environment}}

{{Bootloader}}

The bootloader environment configures the [[bootloader]]. Between reboots, the environment is stored with a checksum in the internal flash [[Partitions|partition]] called "u-boot_env". On the bootloader console, there are [[bootloader commands#Environment|bootloader commands for environment manipulation]].

== Typical environment ==

<pre>
baudrate=115200
bootargs=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
usbtty=cdc_acm
bootdelay=10
stdout=serial
stderr=serial
stdin=serial
mtdparts=mtdparts=neo1973-nand:0x00030000(u-boot),0x0000c000(u-boot_env),0x00200000(kernel),0x00130000(splash),0x03c94000(rootfs)
mtdids=nand0=neo1973-nand
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
pcf50606_int1=0x40
filesize=160C000
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
</pre>

== Timeouts ==

If the boot loader menu is on the screen, the phone will power off when there hasn't been activity for a while. This is not nice if you are working on the boot loader console, but you can make the time longer:
<pre>
setenv boot_menu_timeout [seconds]
</pre>

After the phone is powered on, there is a short period of time when you can connect to the console and cancel the automatic boot without going to the menu:
<pre>
setenv bootdelay [seconds]
</pre>

== Menu ==

You can add items to the boot menu by setting environment variables of the form ''menu_<number>'' to values of the form ''<Title>: U-Boot-Commands''.

For example the following command will add a boot menu entry that switches to autofast charging and turns off the backlight:
setenv menu_6 Autofast-Charge and Backlight Off: neo1973 charger autofast\; neo1973 backlight off

While in this state, your Neo1973 can be charged with a generic USB charger. You also need to set boot_menu_timeout to 65000 to keep it from powering down, though.

=== Booting to the menu ===
To stop in the NAND menu, press and hold the AUX key after pressing the power button at startup. In recent versions of u-boot (builds from august 5 200?), you can also permanently enter the menu by setting the <tt>stop_in_menu</tt> environment variable to <tt>yes</tt>:

setenv stop_in_menu yes
saveenv

to restore normal startup, unset this variable or set it to <tt>no</tt>.

== Console ==

To get access to the bootloader console over USB, the following settings need to be made:
<pre>
GTA01Bv2 # setenv stderr usbtty
GTA01Bv2 # setenv stdout usbtty
GTA01Bv2 # setenv stdin usbtty
</pre>

== See also ==

* http://lists.openmoko.org/pipermail/community/2008-September/029845.html
* http://markmail.org/message/d2abi2nm5vms3unh

{{Languages|Bootloader}}

[[Category:System Developers]]

Dfu-util

2008-11-20T23:32:01Z

Jidanni: /* Troubleshooting notes */any error means failed transfer

{{Languages|Dfu-util}}

{{warning|Dfu-util is currently broken on [http://en.wikipedia.org/wiki/Big_endian#Endianness_and_hardware big-endian] architectures}}
{{warning|Do not flash U-Boot unless you are sure you need to}}
{{note|You need to connect your neo directly to your pc with no hub between. Otherwise there could be problems with the hub and the usb reset.}}

== Purpose ==

dfu-util is a program that implements the Host (PC) side of the [[USB DFU]] (Universal Serial Bus Device Firmware Upgrade) protocol.

In the Openmoko project, we use this program to communicate with our specially enhanced [[u-boot]] boot loader, which implements the DFU device side.

Using dfu-util and your smartphone, you can
* transfer and flash [[Partitions|partitions]] in internal [[NAND Flash]].
* transfer anything into RAM
** this can be used for fast development cycles of low-level code such as kernels without flashing them
* read out the current internal NAND [[Partitions|partitions]]
** this is an easy and efficient way of doing full backups of your phone

== Source Code ==
On Debian and Ubuntu, you'll need libusb-dev:
sudo apt-get install libusb-dev autogen pkg-config autotools-dev autoconf automake

On Fedora you'll need libusb-devel and libusb-static:
yum install libusb-devel libusb-static

On Gentoo you can emerge openmoko-dfu-util after unmasking it:
echo "app-mobilephone/openmoko-dfu-util **" >> /etc/portage/package.keywords
emerge -va app-mobilephone/openmoko-dfu-util

You can check out and build the latest version of dfu-util using the following subversion commands:
svn co http://svn.openmoko.org/trunk/src/host/dfu-util/
cd dfu-util
./autogen.sh
./configure
make

The resulting binary is dfu-util/src/dfu-util.

== Binaries ==

Binary packages will be [http://downloads.openmoko.org/releases/Om2008.8-update/dfu-util made available] as part of the regular Openmoko builds. Currently, there is a dfu-util for Linux/i386.

You need to make the downloaded file (dfu-util) executable with:
<pre>
chmod +x dfu-util
</pre>
you can then run it with
<pre>
./dfu-util
</pre>
see below for full instructions.

[http://packages.debian.org/dfu-util dfu-util is packaged] for Debian ''>= lenny'', so can be installed with: <tt>apt-get install dfu-util</tt>

[http://downloads.sourceforge.net/slackfr-packs/dfu-util-svn4686-i686-1cfdev12.1.tgz dfu-util is packaged] for '''Slackware''' (12.1), so can be installed with: <tt>pkgtool</tt>

Currently, there is a largely untested binary for Win32 (see [[Dfu-util-windows]]). Windows users can refer to [[No_Linux]] for a more tested approach.

Compiling dfu-util on Mac:
* http://lists.openmoko.org/pipermail/community/2007-July/008438.html
* [[User:SNMoore]]
* [[MacOS_X#Flashing_to_your_device]]

== Reference Documentation ==

To run dfu-util, you need to have /proc/bus/usb mounted and working. The terminal command "ls /proc/bus/usb" should return something similar to, "001 002 003 004 005 devices", it shouldn't be empty. If it is empty, use this command:

<pre>
sudo mount -t usbfs usbfs /proc/bus/usb
</pre>

You can permanently add it in your fstab so that it automatically mounts. You can use emacs to edit you fstab using the command "sudo emacs /etc/fstab -nw" in your terminal window. Add the below line to your fstab:

<pre>
usbfs /proc/bus/usb usbfs defaults
</pre>

=== Before using dfu-util ===
You'll need to boot your phone into the NAND Boot Menu:
* Ensure your phone is connected directly to the host computer by USB (not the USB-charger! :)
* Ensure that you execute all dfu-util commands as root
* Power off the phone
* Hold down AUX
* Press POWER until the Boot Menu appears
see also [[Booting the Neo FreeRunner]]

=== Command-line options ===

==== --help ====

<pre>
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Usage: dfu-util [options] ...
-h --help Print this help message
-V --version Print the version number
-l --list List the currently attached DFU capable USB devices
-d --device vendor:product Specify Vendor/Product ID of DFU device
-c --cfg config_nr Specify the Configuration of DFU device
-i --intf intf_nr Specify the DFU Interface number
-a --alt alt_nr Specify the Altseting of the DFU Interface
-t --transfer-size Specify the number of bytes per USB Transfer
-U --upload file Read firmware from device into <file>
-D --download file Write firmware from <file> into device
-R --reset Issue USB Reset signalling once we're finished
</pre>

==== --alt ====
With the -a switch you specify the location on the device you want to write to or read from.
However, for most cases, ''kernel'' and ''rootfs'' will be enough.

See [[Neo_FreeRunner_partitions]] for a list. You may also use the ''--list'' switch (see below), to get an online list.

==== --list ====

Using the --list option, you can list the available DFU capable devices, their configuration, interface and altsettings.
Below is an example for a current Neo1973 phone in u-boot '''Runtime Mode'''
<pre>
# ./dfu-util --list
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Found DFU Runtime: [0x1457:0x5119] devnum=0, cfg=0, intf=2, alt=0, name="USB Device Firmware Upgrade"
</pre>

Below is an example for a current Neo1973 phone in u-boot '''DFU Mode'''
<pre>
# ./dfu-util --list
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Found DFU: [0x1457:0x5119] devnum=16, cfg=0, intf=0, alt=0, name="RAM 0x32000000"
Found DFU: [0x1457:0x5119] devnum=16, cfg=0, intf=0, alt=1, name="u-boot"
Found DFU: [0x1457:0x5119] devnum=16, cfg=0, intf=0, alt=2, name="u-boot_env"
Found DFU: [0x1457:0x5119] devnum=16, cfg=0, intf=0, alt=3, name="kernel"
Found DFU: [0x1457:0x5119] devnum=16, cfg=0, intf=0, alt=4, name="splash"
Found DFU: [0x1457:0x5119] devnum=16, cfg=0, intf=0, alt=5, name="rootfs"
</pre>

This shows you six interfaces, all in '''configuration 0''' and '''interface 0''', with altsetting 0...5, for RAM and each [[Partitions|partition]].

==== --device ====

You can specify the USB Vendor and Product ID of the device you want to program:

dfu-util --device 0x1457:0x5119

If you only have one standards-compliant DFU device attached to your PC, this is optional. However, as soon as you have multiple DFU devices, dfu-util will detect this and abort, asking you to specify which device it shall use.

==== --transfer-size ====

Specifies the size of each individual USB transfer. If you don't use it, the maximum possible size for your combination of host operating system and USB device is chosen (for optimal performance).

==== --download ====

download the given file into the device.

==== --upload ====

upload from the DFU device into the given file[name].

{{note|Upload support is currently broken - [http://docs.openmoko.org/trac/ticket/676 #676]}}

== Phrasebook ==

There's no full-fledged manual yet. Instead, some examples:

=== Flashing the rootfs ===

dfu-util -a rootfs -R -D /path/to/openmoko-devel-image.jffs2

=== Flashing the kernel ===

dfu-util -a kernel -R -D /path/to/uImage

=== Flashing the bootloader ===

dfu-util -a u-boot -R -D /path/to/u-boot.bin

=== Flashing the splash image ===

dfu-util -a splash -R -D /path/to/splash.gz

see also [[Configuring_the_boot_splash_screens]]

=== Copying a kernel into RAM ===

dfu-util -a 0 -R -D /path/to/uImage

Once this has finished, the kernel will be available at the default load address of 0x32000000 in Neo1973 RAM.

{{note|You cannot transfer more than 2MB of data into RAM using this method}}

== Troubleshooting notes ==

If during flashing of an image using dfu-util you're consistently getting an error -110 message, check that the size of the destination NAND [[Partitions|partition]] is big enough to hold the image. For example the kernel partition is only 2 MB big by default and a kernel with debugging info compiled-in can often exceed this. It's possible to change the partition layout to enlarge a given partition and shrink other partitions but you have to remember to reflash all partitions whose start offset has changed afterwards. To adjust partitions layout use the ''mtdparts'' [[Bootloader|u-boot command]].

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

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

If dfu-util complains about not being able to program the device while in runtime mode, do the following: while in the boot menu, remove the usb cable and insert it again. Depending on the version of uBoot it should display somewhere in the menu that it is now in DFU mode. Now dfu-util should be able to continue.

If dfu-util is too slow on Windows, that's a known bug. A suggestion is to run Linux on a virtual box. An full root image 97MB that is 776Mbit, the USB 1.1 on the Neo FreeRunner is capable of either 1.5 Mbit/s (Low-Speed) and 12 Mbit/s (Full-Speed). So flashing it should take less than 9 minutes with low speed and a bit more than a minute with full-speed. Plus transfer overhead, plus decompression on the Neo side.

Note that any error messages indicate a probable failed transfer, despite latter messages emitted about success, etc.

== See also ==
*[[Flashing the Neo 1973]] to the latest software.
*[[Flashing the Neo FreeRunner]]

[[Category:Flashing Openmoko]]

Backup

2008-11-20T23:27:10Z

Jidanni: /* Backing up just PIM data (contacts/tasks/calendar) */grammar

== Backing up just PIM data (contacts/tasks/calendar) ==
The following applies to all Qtopia PIM suite based derivations (FDOM, 2008.8, Qtopia)

Contacts, calendar appointments, and tasks are kept in ~/Applications/Qtopia/qtopia_db.sqlite

To backup simply use secure copy:
scp -pr root@192.168.0.202:~/Applications/ .
scp -pr root@192.168.0.202:~/Documents/ .
And to restore do the reverse:
scp -pr Applications root@192.168.0.202:~/
scp -pr Documents root@192.168.0.202:~/
Make sure you restart to allow the Qtopia PIM suite to see the changes:
reboot
This way we can flash applicable distributions with minimal effort and not lose all our important data.

== Backing up just /home/root ==

To backup the home folder (all your personal files in theory).

From the desktop pc run:

ssh root@phone 'tar -cpz /home/root' > moko-home-`date +%Y%m%d-%H%M%S`.tar.gz

Where phone is the ip address of your phone (192.168.0.202).

Personally I added an entry to /etc/hosts so the above works for me. I also added the desktop key to /home/root/.ssh/authorized_keys on the phone as per the instructions in [[USB_Networking#SSH_Keys]].

If you want to check what is in the backup, run the following, replacing the filename with what was just created.

tar -tzf moko-home-20080802-203108.tar.gz | less

[http://timwise.wikispaces.com/my+neo+freerunner reference]

== Backing up everything ==

You may either :
* Backup the flash contents, in order to be able to restore (see below)
* or move the system to SD to be able to boot it from SD in case of need. See [[Moving current system from flash to SD]]

=== Backing-up flash images ===

{{note|Upload support is currently broken - [http://docs.openmoko.org/trac/ticket/676 #676], [http://docs.openmoko.org/trac/ticket/1843 #1843]}}

You will need the [[Dfu-util]] to make a backup of your existing image.

As when [[Flashing_the_Neo_FreeRunner|flashing]], you will need to be in [[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|U-Boot in the NOR Flash]]. Log into the NOR uBoot menu and select ''Set console to USB'' (for FreeRunner just stay in NOR uBoot menu, do not select or enter anything). Now you will be able to flash, make backups of your FreeRunner or query the FreeRunner with [[Dfu-util|dfu-util]]. Backup is fairly slow; it took over ten minutes to back up a 247 MB rootfs.

It is important that you connect the USB cable directly from your computer to your phone. If there is a hub between them, backup (and flashing) will mostly likely fail.

{{note|On a Windows host, omit the "./" or "sudo ./" that precedes the commands listed on this page}}

<pre>
sudo ./dfu-util -a kernel -R -U good-kernel.bin
sudo ./dfu-util -a rootfs -R -U good-rootfs.jffs2
sudo ./dfu-util -a splash -R -U good-splash.bin
sudo ./dfu-util -a u-boot -R -U good-u-boot.bin
sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin
</pre>

Here is what a successful dfu-util backup run looks like:

on the host PC:
<pre>
$ sudo ./dfu-util -a kernel -R -U good-kernel.img
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=12, cfg=0, intf=0, alt=3, name="kernel"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
Resetting USB to switch back to runtime mode
</pre>

on the FreeRunner:
<pre>
DFU: Switching to DFU Mode
DEVICE_CONFIGURED: 1
Starting DFU Upload of partition 'kernel'
</pre>

A failed run of dfu-util looks like this:
<pre>
dfu-util - (C) 2007 by Openmoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0000:0x0000...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x1d50:0x5119] devnum=20, cfg=0, intf=0, alt=6, name="rootfs"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x1000
dfu_upload error -110

And shows errors demsg like this:
usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110
</pre>

=== Backing-up flash images (alternative) ===

On the device:
<pre>
mkdir /var/tmp/root
mount /dev/root /var/tmp/root
</pre>

If you have om2008.9 you have to use:
<pre>
mount -t jffs2 /dev/mtdblock6 /var/tmp/root
</pre>

On your workstation:
<pre>
ssh root@192.168.0.202 "mkfs.jffs2 -d /var/tmp/root -e 128 --pad --no-cleanmarkers -x lzo" | pv -W > rootfs.jffs2
</pre>
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)

On the device:
<pre>
umount /var/tmp/root
</pre>

=== Backing-up in a tar archive ===

ssh root@192.168.0.202 "tar c /bin /etc /home /lib /opt /sbin /tmp /usr /var" | pv -W > rootfs.tar
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)

Extract it and use <code>mkfs.jffs2</code> if you want convert it to a jffs2 image.

==Backup Scripts==

If you plan on backing up frequently, using a script will simplify the process:

===Simple backup script===

This script works well if you want to configure it to backup always the same device.

<pre>
#!/bin/sh
#
# Back up all partitions of the phone to a backup directory,
# adding today's date to the saved filenames.

DATE=`date +%Y-%m-%d`
DFU=./dfu-util
BACKUP_DIR=bak/

${DFU} -a kernel -R -U ${BACKUP_DIR}kernel-${DATE}.bin
${DFU} -a rootfs -R -U ${BACKUP_DIR}rootfs-${DATE}.jffs2
${DFU} -a splash -R -U ${BACKUP_DIR}splash-${DATE}.bin
${DFU} -a u-boot -R -U ${BACKUP_DIR}u-boot-${DATE}.bin
${DFU} -a u-boot_env -R -U ${BACKUP_DIR}u-boot_env-${DATE}.bin
</pre>

===Interactive script===

This script is based on the above "Simple backup script" (by unknown). It does the backup of what you want and choose promting you for choices. Enjoy it! test it! contribute! You can find us at /server irc.freenode.net /j #openmoko and we'll be pleased to accept you help (ideas || code).

NOTE that the script works for me(tm) but it still needs some love. especially on traps and catches for wrong choices.

<pre>
#!/bin/bash

#############################################################################################################
## ##
## This script is Free Software, it's licensed under the GPLv3 and has ABSOLUTELY NO WARRANTY ##
## you can find and read the complete version of the GPLv3 @ http://www.gnu.org/licenses/gpl.html ##
## ##
## Q: what does this script do? ##
## A: the script back up all partitions of the phone to a backup directory, interactively, ##
## adding today's date to the saved filenames. ##
## ##
## IMPORTANT:!!! REMEMBER TO RUN THIS SCRIPT AS ROOT SINCE dfu-util HAS TO BE USED AS ROOT!!! ##
## ##
## based on the orginal simple backup script at http://wiki.openmoko.org/wiki/Backup ##
## ##
## this version has been conceived and written by cga, x77686d, Infoport, jomat at /server irc.freenode.net##
## /j #openmoko,#bash and my collegue aubba @ work. ##
## ##
## for any suggestions and contributions contact cga (or one of the above) in the #openmoko channel ##
## ##
#############################################################################################################

## let's roll!!

## sets the date format for the date in the backup file, change accordingly to your local custom if you need
DATE=`date +%d-%m-%Y`

## here the scripts try to find the dfu-util binary and set it as the DFU var:
if which dfu-util >/dev/null ; then
echo
echo "dfu-util found in your path"
echo
## 1 the function use this if you placed/linked dfu-util in your $PATH
DFU=dfu-util

elif ls dfu-util >/dev/null ; then
echo
echo "dfu-util found in current directory"
echo
## or 2 use following line if dfu-util is placed in the same directory where you run the script
DFU=./dfu-util

else
## or 3 if the script doesn't find dfu-util shows the link for installing it and exit
echo
echo "dfu-util NOT found! install and use howto @ http://wiki.openmoko.org/wiki/Dfu-util"
echo
exit 1
fi

## here we get the hex code for devices found with dfu-util --list
## the hex code is grabbed and the name of the device is shown accordingly and you are prompetd to chose the right one:
echo
echo 'these are the devices i found:'
echo
for device in `${DFU} --list | grep 0x | cut -f3 -d' ' | tr -d '[]'` ; do
if [ "$device" == '0x1457:0x5119' ] ; then
echo 'Neo 1973'
elif [ "$device" == '0x1d50:0x5119' ] ; then
echo "Neo FreeRunner"
else
echo 'other device found, DO NOT use dfu-util on this!!! it might bork it...'
exit 1
fi
done | nl
echo
echo 'choose the device to backup:'
echo
read selection
HEX=$(${DFU} --list | grep 0x | head -n $selection | tail -1 | cut -f3 -d' ' | tr -d '[]')

## use the built-in read command to ask you and use the directory for the backup
while [ -z "$BACKUP_DIR" ] ; do
echo
read -e -p $"enter the directory for the backup:" BACKUP_DIR
echo

## chek wether the dir exist and proceed, else create it and proceed.
if [ ! -d "$BACKUP_DIR" ] ; then
echo
echo -n "$BACKUP_DIR does not exist, create it? [Y/n] "
echo
read CREATE_DIR
if [ x"$CREATE_DIR" = xy -o x"$CREATE_DIR" = xY -o -z "$CREATE_DIR" ] ; then
mkdir -p -v "${BACKUP_DIR}"
else
BACKUP_DIR=
fi
fi
done

## here you get prompted to chose the backup you want, you can backup single files or all of them.
echo
echo 'choose the component to backup from the list:'
echo

select howto in kernel splash u-boot u-boot_env rootfs all quit; do
if [ "$howto" == "kernel" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a kernel -R -U ${BACKUP_DIR}/kernel-${DATE}.bin
fi
if [ "$howto" == "splash" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a splash -R -U ${BACKUP_DIR}/splash-${DATE}.bin
fi
if [ "$howto" == "u-boot" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot -R -U ${BACKUP_DIR}/u-boot-${DATE}.bin
fi
if [ "$howto" == "u-boot_env" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a u-boot_env -R -U ${BACKUP_DIR}/u-boot_env-${DATE}.bin
fi
if [ "$howto" == "rootfs" -o "$howto" == "all" ] ; then
${DFU} -d ${HEX} -a rootfs -R -U ${BACKUP_DIR}/rootfs-${DATE}.jffs2
fi
if [ "$howto" == "quit" ] ; then
exit 0
fi
echo
echo 'the component(s) has/have been backed up, what next? (press enter for menu)'
echo
done

exit 0

</pre>

=== Pretty GUI Script ===

[[NeoTool]] is a zenity-based script which allows you to both backup and Flash your device from a pretty GUI. It uses both the dfu-util method and the alternate method described on this page, and can produce flashable images of everything including rootfs. Check it out.

[[category:Advanced End User]]
[[Category:Flashing Openmoko]]

Qi

2008-11-20T21:40:36Z

Jidanni: /* Download and installation */ source code location

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card. (Note: Qi expects the / (root) filesystem to be on the same partition as /boot!) It
tries the it will try first, second and then third partitions. Failing to find that, it will boot from the
kernel in NAND (if the kernel works of course, see below). Failing to find that, it will blink the blue Power
LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==

The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
(look at your dmesg output for the CPU to pick the right s3c* version.)

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

One could [http://git.openmoko.org/?p=qi.git;a=summary poke around the source code] but it may be less
confusing to just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* {{Ticket|2095}} describes sound trouble (=no sound at all) on 2.6.24 kernel
* Qi often doesn't want to resume after suspend.

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]

Main Page

2008-11-20T20:46:18Z

Jidanni: add direct link to source code

{{Languages|Main Page}}
__NOTOC__
__NOEDITSECTION__ [[Image:Freerunner02.gif|thumb|150px|right|Neo FreeRunners]]

<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div>

Openmoko™ is a project dedicated to delivering mobile phones with an [[Source Code|open source software stack]]. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.

The Openmoko stack, which includes a full X server, allows users and developers to transform mobile hardware platforms into unique products. Our license gives developers and users 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 [http://downloads.openmoko.org/CAD/ CAD] files. And at LinuxWorld 2008, we announced the release of the [http://downloads.openmoko.org/schematics/ schematics for our products].

<div style="clear:both"> </div>

<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white">
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">News and events</td>
<td width="50%">New to Openmoko?</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
* 17/11: [[Community Updates/November 16th, 2008|Community updates~16,Nov]]
* 11/11: [[OpenmokoFramework/Status Update 5|Openmoko Framework Team Status Report 2008.11.1]]
* 10/11: Three weeks into the refocused [http://onlinedev.blogspot.com/2008/11/back-to-basics-update.html Back to Basics] development strategy.
* 05/11: Freerunner with [http://tw.youtube.com/watch?v=SG3fAHFNs2c mechanical legs]. Really.
* 04/11: [[User:Seanmcneil3|Android on Freerunner]], first bootable images.
* 03/11: [[Community_Updates/November 2nd, 2008|Community update]].
*
* 31/10: Nokia released [http://qtextended.org/ Qt Extended 4.4.2] ([http://qtextended.org/modules/mydownloads/visit.php?lid=98 image]).
* 30/10: [[Freerunner Alternative Case Designs]]
* 23/10: [[FDOM]], the Fat and Dirty Openmoko Distribution [http://lists.openmoko.org/pipermail/community/2008-October/034219.html updated]. Now with an installer script.

 
* [[News Archive|(news archive)]]
</td>
<td>
===About Openmoko===
* [[Introduction]]
* [[Why Openmoko]]
* [[Neo FreeRunner|Neo FreeRunner phone]]
* [[Supported Hardware]]
* [[FAQ]]

===Getting Openmoko===
* [[Getting Openmoko]]
* [http://www.openmoko.com Openmoko Inc.]

</td>
</tr>
<tr style="background:#ff6600; text-align:center; font-weight:bold">
<td width="50%">for Users</td>
<td width="50%">for Developers</td>
</tr>
<tr valign="top" style="background:#333333">
<td>
===Getting started===
* [[Getting Started with your Neo FreeRunner | Neo FreeRunner getting started guide]]
* [[Applications]]

===Distributions===
* [[Distributions|Features comparison table]]
* [[Om 2008.8|Om 2008.8 (ASU)]] - [[Om 2007.2|Om 2007.2 (old stable)]]
* [[OpenmokoFramework|FSO]] - [[FDOM - a Fat and Dirty OM based distribution|FDOM]] - [[Qtopia / Qt Extended on FreeRunner|Qt Extended]] - [[Debian]] - [[Gentoo]] - [[Android]]

===Openmoko community===
* [[Discussion_Forums| Discussion Forums]]
* [[Community Repository]]
* [[Development resources | Development resources]]
* [[Openmoko E-courseware | E-courseware]]
</td>
<td>
===Applications development===
* [[Openmoko developer guide]]
* [[Toolchain|The toolchain]]

* [[Python|Introduction to Python]]
* [http://projects.openmoko.org/ Projects hosted in our GForge]
* [[OpenmokoFramework|Openmoko dbus-based service level framework]]

===Integration and distributions===
* [[OpenEmbedded|The OpenEmbedded distribution building framework]]
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]
* [[Opkg|The Opkg package manager]]

===Emulation===
* [[Openmoko under QEMU]]
</td>
</tr>
</table>

Browse articles by [[:Category:Categories|Categories]].

Qi

2008-11-20T20:38:14Z

Jidanni: boot/uImage-GTA02.bin ...

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card. (Note: Qi expects the / (root) filesystem to be on the same partition as /boot!) It
tries the it will try first, second and then third partitions. Failing to find that, it will boot from the
kernel in NAND (if the kernel works of course, see below). Failing to find that, it will blink the blue Power
LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==

The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
(look at your dmesg output for the CPU to pick the right s3c* version.)

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* {{Ticket|2095}} describes sound trouble (=no sound at all) on 2.6.24 kernel
* Qi often doesn't want to resume after suspend.

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]