Openmoko - User contributions [en]

User:Treviño

2011-06-17T16:14:44Z

Treviño: /* Community Update Draft */

Just to start, [http://www.3v1n0.net My Web World]

Backup

2009-12-02T04:24:24Z

Treviño: /* Backing-up in a tar archive */

== Backing up just PIM data ==

The following applies to all Qtopia PIM suite based derivations (FDOM, 2008.8, Qtopia). PIM data covers:

* Contacts, calendar appointments, and tasks
* E-Mails and text messages

To make a backup which can be easily restored later on use secure copy:

scp -pr root@192.168.0.202:~/Applications/ .
scp -pr root@192.168.0.202:~/Documents/ .

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 without loosing important data. To access the PIM data on the computer take a look at the following files and folders:

* Contacts, calendar appointments, and tasks are kept in <tt>~/Applications/Qtopia/qtopia_db.sqlite</tt>.
* E-Mails and text messages are kept in <tt>~/Applications/qtmail/mail/</tt>.

== 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 '''<tt>phone</tt>''' 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'
DEVICE_CONFIGURED: 1
</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
</pre>
And shows demsg errors like this:
<pre>
usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd dfu-util rqt 161 rq 2 len 4096 ret -110
</pre>
This error is detected within the Linux USB stack (drivers/usb/core/message.c) and looking at
errno.h for the negatived error status number, the reason is e.g.
{|
| 110 || ETIMEDOUT || Connection timed out
|-
| 84 || EILSEQ || Illegal byte sequence
|-
| 108 || ESHUTDOWN || Cannot send after transport endpoint shutdown
|-
| ... || ||
|}
Insure yourself, that you connect the FR directly to the computer (without any USB hubs), if you experience timed out connections
and use the
<pre>
dfu-util -d 0x1d50:0x5119 ...
</pre>
option, if the FR is not detected properly.

=== 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 -s 2200000 -W > rootfs.tar
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by; the "-s" option presume you're transferring 2200000 bytes of data)

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.

== Backing up the incremental rsync hardlink way ==

Following is a very simple implementation of
[http://www.mikerubel.org/computers/rsync_snapshots/ incremental rsync snapshots with hardlinks]. Just put it to /etc/cron.daily/backup-neo
on your PC and setup ssh keys between your PC and neo. It will then
daily try to backup all files in the / partition. Each successful
backup is hardlinked under a timestamped directory so you can access
old backups easily. In fact, you can even NFS mount /backup/neo to
phone and then chroot inside the backups to run programs in the
backup'ed environment.
#!/bin/bash
# /etc/cron.daily/backup-neo
rsync --delete -ax --numeric-ids 192.168.0.202:/ /backup/neo/latest 2> /dev/null
ret=$?

case $ret in
0)
# backup done, let's save it
cp -al /backup/neo/latest /backup/neo/`date -I`
;;
12)
# neo was not at home
;;
*)
echo "backup failed with return value $ret"
;;
esac

== Backing up internal flash when booted on external SD-card ==

#Freerunner
mkdir internal_flash
mount /dev/mtdblock6 internal_flash -t jffs2

Now you can pack directory or copy selected files out from it.

(This mounting is usefull also if your internal operating system is non-bootable. You can get files out or even repair the system using operating system on external card.)

== Weblinks ==
* [http://www.oesf.org/forum/index.php?showtopic=25994#entry178835 read jffs file system on pc]

[[Category:PIM]]
[[category:Advanced End User]]
[[Category:Flashing Openmoko]]

NeoCon

2009-12-02T03:02:33Z

Treviño:

'''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'''. Being a member of the <code>dialout</code> group 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 <code>ttyUSBn</code>
or <code>ttyACMn</code>. 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:Middleware]]
[[Category:Bootloaders]]
[[Category:Bootloader]]
[[Category:USB]]

Community Updates/Draft

2009-11-17T14:46:39Z

Treviño: /* Applications */

{{Improve}}
{{Note|
*Take a moment and look at Discussion page to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
*I you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.</nowiki>
*Please fill in everything you think the community should know.
*On YYYY-MM-DD this content will be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.
*Post a note about CU release on the community mailing list.
}}



====='''Period YYYY-MM-DD to YYYY-MM-DD'''=====

==Distributions==
{{DistributionBox|
Name=Distro Name [version]|
Description=Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.|
Screenshot=System_boot.png|
Codename='codename'|
Homepage=http://www.homepage.org|
Image=[http://www.homepage.org/path/to/ images]|
Works={{Works}}
}}

==Applications==
===New Applications===

{{ApplicationBox|
Name=emenu - openmoko program launcher|
Description=This launcher was intended to use it with the hardware keys of the Openmoko phones. You can define own xml files for any of your target actions. Perhaps you will launch a other menu when you push the power or aux button. For example ⇒ pyemenu.py aux.xml [http://wiki.yourse.de/lib/exe/fetch.php?w=200&media=python:pyemenu.png screenshot].

emenu is written in python and in gtk.|
Screenshot=System_boot.png|
Homepage=http://wiki.yourse.de/doku.php?id=python:emenu|
TestedOn=|
PackageName=
}}

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff..|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

===Application Updates===
{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff...
* new example feature 1
* new example feature 2|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

==Community==
Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

==Event News==
* '''2009-mm-dd''' [http://example.url.xom Example event] | add your event here

[[Category:Community Update]]

3D7K

2009-03-05T19:44:43Z

Treviño:

3D7K (previously known as GTA03) is the codename of a phone that is currently in [[Phone Development|development]] by Openmoko. It seems as if it will not be available before Q3 2009. This [http://n2.nabble.com/Stage-of-GTA03-development--tp1664400p1803187.html post] from Steve Mosher gives more details.

The 3D7K will be based on a more advanced system-on-a-chip of same family as the [[Neo FreeRunner]] ([[GTA02 revisions|GTA02]]). It will presumably differ from it by having EDGE and a camera. 3D7K will not include support for 3G networks because of the high price of 3G chips for low volume phones [http://lists.openmoko.org/pipermail/community/2008-December/038395.html].

{{Speculations}}

== 3D7K Specifications ==
The 3D7K will be based on the [[GTA02 revisions|GTA02]] introducing several major hardware changes

New:
* New case design
* New GSM chip: [http://www.cinterion.com/en/ktcm/modules_terminals/gerneral_purpose/Scalable_platform/MC75i_TC63i_TC65i Cinterion, (Siemens) MC75i]
** 2.75G / EDGE
** Quad-Band (850/900/1800/1900 MHz)
* New WiFi/Bluetooth chip: [http://www.marvell.com/press/pressNewsDisplay.do?releaseID=603 Marvell 88W8688] - Update (2009-01-23): [http://lists.openmoko.org/pipermail/devel/2009-January/004354.html currently removed]
* Different Battery ([[Wishlist/LiFePO4 Battery]] based? - for long life?)
* Camera: Samsung S5K CCM camera (S5K4BA - UXGA: 2 Megapixel [http://www.csi-sensor.com.tw/eng/Lists/AreaSensorCubic/DispForm.aspx?ID=8&Source=http%3A%2F%2Fwww%2Ecsi%2Dsensor%2Ecom%2Etw%2Feng%2Fareasensors%2Easpx info]) [http://www.datasheetarchive.com/search.php?q=S5K*+CMOS some S5K datasheets]
* SoC: [http://semicon.samsung.de/applicationprocessors/tracking/aboutS3C6410.aspx s3c6410]
** includes Samsungs own 3D accelerator
** 533/667MHz operating frequency
** Vector Floating-Point (VFP) coprocessor
* GPS: [http://www.u-blox.com/technology/u-blox5/index.html ANTARIS 5]
* Display: TPO LPJ028T007A 2.8" [http://n2.nabble.com/-PATCH-0-2--Add-support-of-TPO-L1K002-LCM-driver-td2185408.html LCM]
* Touchscreen: EETI PCAP7200 capacitive touch device [http://lists.openmoko.org/nabble.html#nabble-td1690756%7Ca1690756 driver].
Removed:
* SMEDIA Glamo

== GTA03 Evaluation Board ==
* 2008-08-11: the 25 first GTA03EVB arrived in office
* 2008-08-12: U-boot ported to GTA03EVB (Matt)
* 2008-08-12: The core can run at 533 MHz with 133MHz SDRAM
* 2008-08-12: GTA03EVB Hardware Verification of the u-blox 5 Antaris
* 2008-08-12: GPS performance tested
* 2008-08-18: GTA03EVB Hardware Verification of the Siemens MC 75i EDGE MODEM

== Sources ==
* http://n2.nabble.com/Weekly-Engineering-News-33-2008-tp729555p729555.html
* [[MokoForesight]]

[[Category:GTA03]]

[[Category:3D7K]]

3D7K

2009-03-04T16:19:59Z

Treviño: /* 3D7K Specifications */

3D7K (previously known as GTA03) is the codename of a phone that is currently in [[Phone Development|development]] by Openmoko. It seems as if it will not be available before Q3 2009. This [http://n2.nabble.com/Stage-of-GTA03-development--tp1664400p1803187.html post] from Steve Mosher gives more details.

The 3D7K will be based on a more advanced system-on-a-chip of same family as the [[Neo FreeRunner]] ([[GTA02 revisions|GTA02]]). It will presumably differ from it by having EDGE and a camera. 3D7K will not include support for 3G networks because of the high price of 3G chips for low volume phones [http://lists.openmoko.org/pipermail/community/2008-December/038395.html].

{{Speculations}}

== 3D7K Specifications ==
The 3D7K will be based on the [[GTA02 revisions|GTA02]] introducing several major hardware changes

New:
* New case design
* New GSM chip: [http://www.cinterion.com/en/ktcm/modules_terminals/gerneral_purpose/Scalable_platform/MC75i_TC63i_TC65i Cinterion, (Siemens) MC75i]
** 2.75G / EDGE
** Quad-Band (850/900/1800/1900 MHz)
* New WiFi/Bluetooth chip: [http://www.marvell.com/press/pressNewsDisplay.do?releaseID=603 Marvell 88W8688] - Update (2009-01-23): [http://lists.openmoko.org/pipermail/devel/2009-January/004354.html currently removed]
* Different Battery ([[Wishlist/LiFePO4 Battery]] based? - for long life?)
* Camera: Samsung S5K camera [http://www.datasheetarchive.com/search.php?q=S5K*+CMOS datasheets]
* SoC: [http://semicon.samsung.de/applicationprocessors/tracking/aboutS3C6410.aspx s3c6410]
** includes Samsungs own 3D accelerator
** 533/667MHz operating frequency
** Vector Floating-Point (VFP) coprocessor
* GPS: [http://www.u-blox.com/technology/u-blox5/index.html ANTARIS 5]
* Display: TPO LPJ028T007A 2.8" [http://n2.nabble.com/-PATCH-0-2--Add-support-of-TPO-L1K002-LCM-driver-td2185408.html LCM]
* Touchscreen: EETI PCAP7200 capacitive touch device [http://lists.openmoko.org/nabble.html#nabble-td1690756%7Ca1690756 driver].
Removed:
* SMEDIA Glamo

== GTA03 Evaluation Board ==
* 2008-08-11: the 25 first GTA03EVB arrived in office
* 2008-08-12: U-boot ported to GTA03EVB (Matt)
* 2008-08-12: The core can run at 533 MHz with 133MHz SDRAM
* 2008-08-12: GTA03EVB Hardware Verification of the u-blox 5 Antaris
* 2008-08-12: GPS performance tested
* 2008-08-18: GTA03EVB Hardware Verification of the Siemens MC 75i EDGE MODEM

== Sources ==
* http://n2.nabble.com/Weekly-Engineering-News-33-2008-tp729555p729555.html
* [[MokoForesight]]

[[Category:GTA03]]

[[Category:3D7K]]

3D7K

2009-03-04T16:15:13Z

Treviño: New page: 3D7K (previously known as GTA03) is the codename of a phone that is currently in development by Openmoko. It seems as if it will not be available before Q3 2009. This...

3D7K (previously known as GTA03) is the codename of a phone that is currently in [[Phone Development|development]] by Openmoko. It seems as if it will not be available before Q3 2009. This [http://n2.nabble.com/Stage-of-GTA03-development--tp1664400p1803187.html post] from Steve Mosher gives more details.

The 3D7K will be based on a more advanced system-on-a-chip of same family as the [[Neo FreeRunner]] ([[GTA02 revisions|GTA02]]). It will presumably differ from it by having EDGE and a camera. 3D7K will not include support for 3G networks because of the high price of 3G chips for low volume phones [http://lists.openmoko.org/pipermail/community/2008-December/038395.html].

{{Speculations}}

== 3D7K Specifications ==
The 3D7K will be based on the [[GTA02 revisions|GTA02]] introducing several major hardware changes

New:
* New case design
* New GSM chip: [http://www.cinterion.com/en/ktcm/modules_terminals/gerneral_purpose/Scalable_platform/MC75i_TC63i_TC65i Cinterion, (Siemens) MC75i]
** 2.75G / EDGE
** Quad-Band (850/900/1800/1900 MHz)
* New WiFi/Bluetooth chip: [http://www.marvell.com/press/pressNewsDisplay.do?releaseID=603 Marvell 88W8688] - Update (2009-01-23): [http://lists.openmoko.org/pipermail/devel/2009-January/004354.html currently removed]
* Different Battery ([[Wishlist/LiFePO4 Battery]] based? - for long life?)
* Camera: Samsung S5K camera [http://www.datasheetarchive.com/S5K-datasheet.html datasheets]
* SoC: [http://semicon.samsung.de/applicationprocessors/tracking/aboutS3C6410.aspx s3c6410]
** includes Samsungs own 3D accelerator
** 533/667MHz operating frequency
** Vector Floating-Point (VFP) coprocessor
* GPS: [http://www.u-blox.com/technology/u-blox5/index.html ANTARIS 5]
* Display: TPO LPJ028T007A 2.8" [http://n2.nabble.com/-PATCH-0-2--Add-support-of-TPO-L1K002-LCM-driver-td2185408.html LCM]
* Touchscreen: EETI PCAP7200 capacitive touch device [http://lists.openmoko.org/nabble.html#nabble-td1690756%7Ca1690756 driver].
Removed:
* SMEDIA Glamo

== GTA03 Evaluation Board ==
* 2008-08-11: the 25 first GTA03EVB arrived in office
* 2008-08-12: U-boot ported to GTA03EVB (Matt)
* 2008-08-12: The core can run at 533 MHz with 133MHz SDRAM
* 2008-08-12: GTA03EVB Hardware Verification of the u-blox 5 Antaris
* 2008-08-12: GPS performance tested
* 2008-08-18: GTA03EVB Hardware Verification of the Siemens MC 75i EDGE MODEM

== Sources ==
* http://n2.nabble.com/Weekly-Engineering-News-33-2008-tp729555p729555.html
* [[MokoForesight]]

[[Category:GTA03]]

[[Category:3D7K]]

GTA03

2009-03-04T16:10:36Z

Treviño: Redirecting to 3D7K

#REDIRECT [[3D7K]]

GTA03

2009-01-26T00:00:16Z

Treviño:

GTA03 is the codename of a phone that is currently in [[Phone Development|development]] by Openmoko. It seems as if it will not be available before Q3 2009. This [http://n2.nabble.com/Stage-of-GTA03-development--tp1664400p1803187.html post] from Steve Mosher gives more details.

The GTA03 will be based on a more advanced system-on-a-chip of same family as the [[Neo FreeRunner]] ([[GTA02 revisions|GTA02]]). It will presumably differ from it by having EDGE and a camera. GTA03 will not include support for 3G networks because of the high price of 3G chips for low volume phones [http://lists.openmoko.org/pipermail/community/2008-December/038395.html].

{{Speculations}}

== GTA03 Specifications ==
The GTA03 will be based on the [[GTA02 revisions|GTA02]] introducing several major hardware changes

New:
* New case design
* New GSM chip: [http://www.cinterion.com/en/ktcm/modules_terminals/gerneral_purpose/Scalable_platform/MC75i_TC63i_TC65i Cinterion, (Siemens) MC75i]
** 2.75G / EDGE
** Quad-Band (850/900/1800/1900 MHz)
* New WiFi/Bluetooth chip: [http://www.marvell.com/press/pressNewsDisplay.do?releaseID=603 Marvell 88W8688] - Update (2008-01-23): [http://lists.openmoko.org/pipermail/devel/2009-January/004354.html currently removed]
* Different Battery ([[Wishlist/LiFePO4 Battery]] based? - for long life?)
* Camera
* SoC: [http://semicon.samsung.de/applicationprocessors/tracking/aboutS3C6410.aspx s3c6410]
** includes Samsungs own 3D accelerator
** 533/667MHz operating frequency
** Vector Floating-Point (VFP) coprocessor
* GPS: [http://www.u-blox.com/technology/u-blox5/index.html ANTARIS 5]
* Display: TPO LPJ028T007A 2.8" [http://n2.nabble.com/-PATCH-0-2--Add-support-of-TPO-L1K002-LCM-driver-td2185408.html LCM]
* Touchscreen: EETI PCAP7200 capacitive touch device [http://lists.openmoko.org/nabble.html#nabble-td1690756%7Ca1690756 driver].
Removed:
* SMEDIA Glamo

== GTA03 Evaluation Board ==
* 2008-08-11: the 25 first GTA03EVB arrived in office
* 2008-08-12: U-boot ported to GTA03EVB (Matt)
* 2008-08-12: The core can run at 533 MHz with 133MHz SDRAM
* 2008-08-12: GTA03EVB Hardware Verification of the u-blox 5 Antaris
* 2008-08-12: GPS performance tested
* 2008-08-18: GTA03EVB Hardware Verification of the Siemens MC 75i EDGE MODEM

== Sources ==
* http://n2.nabble.com/Weekly-Engineering-News-33-2008-tp729555p729555.html
* [[MokoForesight]]

[[Category:GTA03]]

[[Category:GTA03]]

Community Updates/2009-01-12

2009-01-13T16:41:29Z

Treviño:

Hi! This is the nineth [[Community Updates]], January 12th issue. For the new year we [http://n2.nabble.com/Questions-and-Answers-tp2103754p2103754.html interviewed Sean] on everything that matters for the community: sales in 2008 were around the low five digits, om-locations is what remains of an ambitious mesh network project, and the most surprising development to him was the explosion of distributions. Back on the mailing lists, activity was rater slow during the first week of the year, but got more intense than ever after the holidays. Illume's keyboard received lots of localisations. Opkg.org reached the critical mass of packages. SHR and FSO are counting down toward their next milestone, while coding continues for kernel, drivers, Android and the like. It looks like the switch to 2.6.28 is going to happen soonish, before the switch to the Paroli phone stack.

== Distributions ==
* SHR: According to Julien's latest on [http://blog.shr-project.org/ the SHR project blog], the baby is [http://blog.shr-project.org/2009/01/release-time-is-close-whats-left-what-are-we-doing-what-do-we-need.html expected really soon now].
* Marek announced the new [http://lists.openmoko.org/pipermail/community/2009-January/039227.html organisation of package and images repositories].
* Android: The [http://n2.nabble.com/New-openmoko-android-binary-tp2133865.html;cid=1230847584604-21 latest compatible kernel] has wifi and bluetooth working now. Suspend and resume work, but they have some usability issues.
* [[FSO]] MS5 should branch out for really soon now (the roadmap says release January 31st, but they want a longer stabilization period this time). It will be the first milestone that will have support not only for GTA01 and 02, but also for the Motorola EZX A780. [http://www.freesmartphone.org/index.php/Meeting_2008-12-18_Braunschweig meeting minutes].
* Hackable:1 [http://lists.hackable1.org/pipermail/hackable1-dev/2009-January/000104.html buildbot is up and running]. Images are generated every morning around 4:00. Happy testing !
* [[User:Bytestore]] has updated assemblage 2008.12 from Russian community, work with gprs, headphone jack plug, ru keyboard and many other things were [http://openmoko.spb.ru/viewtopic.php?f=9&t=11 updated] (download [http://dl.linuxphone.ru/openmoko/images/bytestore/bytestore-rootfs-OM200812-2009-01-11-112312.jffs2 rootfs], see [http://dl.linuxphone.ru/openmoko/images/bytestore/screenshot_2009_01_11_112312_en screenshots])

== New applications ==

* [[LED clock]] When an Openmoko is sitting unused at night, turn it into an alarm clock with large 7-segment digits on a black background in landscape mode.
* [http://projects.openmoko.org/projects/gprssettings/ GPRSsettings] is a GUI script designed to change apn, login, dialnumber.
* Samuel's script for [http://blog.samuelpereira.net/?p=4 a toggle wifi icon].
* [http://www.opkg.org/package_86.html ylock] 0.1 Python screen lock and low battery monits.
* [http://www.opkg.org/package_85.html AppManager] 1.0.1 Zenity package manager.
* Mirko [http://lists.openmoko.org/pipermail/community/2009-January/039376.html announced] that pre-alpha [[Paroli]] was now packaged in testing. Development [http://charlie137-2.blogspot.com/2009/01/paroli-get-website.html moved] to their own domain: [http://www.paroli-project.org/ paroli-project] hosts trac, git, blog and documentation.
* Kurt's [[Gwaterpas]] allows to use the Freerunner as a leveling tool.
* There are now 75 packages at [http://opkg.org opkg.org]. Novelties include osmupdater (updates OSM maps directory), sortdesk (sorts the desk), MokoCard (flashcards learning aid), sms-sentry (query the unit's location by SMS, handy if it was just stolen), pyring (a key ring), EFpLayer (mplayer GUI), playstankontakarta (an icon displaying remaining credit with POLISH PLAY pre-paid phone provider), various illume keyboards and more. It was mentioned unofficially that Openmoko's community repository is going to be dismantled.

== Ports and updates ==
* Lots of [[Navit]] activity. Distributions are kindly suggested to package the sample map separately from the main binary to conserve space.
* The [[opkg]] package manager development [http://lists.openmoko.org/pipermail/opkg-devel/2008-December/000181.html moved from OM svn to Google code]. The recommended stable version is r172, there is a significant data structures+algorithm refactorization going on.
* Version 2.4 of [[orrery]] is now available. It has a new schematic Solar System View page, showing the position of the planets and our moon in their orbits, a new moon calendar, and a less ugly icon.
* The [[ZOMG!]] package manager is now available on [http://www.opkg.org/package_96.html opkg.org], and now allows to add/remove/edit repositories (i.e. feeds).
* Angus [http://www.mail-archive.com/community@lists.openmoko.org/msg37043.html updated BtGPS.py] to work with FSO. With this script, [[Neo FreeRunner GPS#Bluetooth GPS relay|the FreeRunner works as a bluetooth GPS]].
* Marco shared his [http://lists.openmoko.org/pipermail/community/2009-January/039370.html success in compiling the latest E17 svn] on 2008.12. There was trouble on SHR with the Elementary widget set, tough.

== Community ==
* Sean's [http://n2.nabble.com/Questions-and-Answers-tp2103754p2103754.html new year interview]
* Rakshat Hooja's company IDA Systems will be at Mumbai's TechFest. There are [http://lists.openmoko.org/pipermail/community/2009-January/039505.html gifts] waiting for the first 10 FreeRunner owners to show up at their booth!
* The [http://lists.openmoko.org/pipermail/devel/2009-January/004064.html Future of location services] thread started as an attempt to clarify the GPS drivers tangle, and then turned to using GSM celltowers and wifi access points location information. Dima [http://lists.openmoko.org/pipermail/devel/2009-January/004074.html signalled that] there are several free databases of GSM tower locations, and that his gta02 Perl script to query [http://www.opencellid.org/ OpenCellID] for the approximate tower location, and then initialize the AGPS with this data works great. There is a database of Wifi access points at [http://wigle.net/ wigle.net].
* Two new mailing lists were announced. One to discuss [https://lists.openmoko.org/mailman/listinfo/testing testing of all Openmoko Products]. The other to discuss [http://lists.projects.openmoko.org/mailman/listinfo/siteadmin-general projects.openmoko.org] administration. While we are at it, here are the number of subscriptions as of 07/01/2009 according to Werner: hardware 670, kernel 692, support 1016, devel 1262, community 2323, announce 11258.
* The Department CSIE of National Chung Cheng University [http://wiki.openmoko.org/wiki/Special:Search?search=CSIE&go=Go launched dozens of projects] this week.

== Hardware and drivers ==
* Werner [http://lists.openmoko.org/pipermail/hardware/2008-December/000890.html announced] he made an [http://www.almesberger.net/misc/idbg/ debug board] that fits inside the case. Schematics contributed as a community member, not as an Openmoko employee.
* Filter AUX key bouncing [http://git.openmoko.org/?p=kernel.git;a=commit;h=39a497b0421174c3f23ef3dffb0675a4db3aa3a0 patches].
* There is a thread about the [[Touchscreen Filters|touchscreen driver]] on the devel list, how it should be [http://lists.openmoko.org/pipermail/devel/2008-December/003888.html split between kernelspace and userspace], and [http://lists.openmoko.org/pipermail/devel/2009-January/004037.html how to contribute it upstream] to the Linux kernel. I find the mix of high-level technical arguments with social and emotional considerations fascinating.
* It is a pleasure to say that the Community localized the [[Illume keyboard]] to at least [[Illume#List_of_illume_keyboards|nine different languages]]. This does not only involves layout and icon, but also building up a dictionary (the keyboard emits key symbols when in "terminal" mode, but uses predictive dictionary lookups when in "strings" mode.) The frontier: asian languages input.
* The Freeunner is also a target platform for many innovative new input methods.
* Carl proposed a simple in-car mount: stick a piece of velcro on the dashboard, strap the FreeRunner onto it through the hole, flipping the display with ''xrandr -o 2''. Add a standard USB car charger, you are all set.
* GSM firmware updater and hardware buzzfix program: not released yet, still working on it.
* Video driver code was ported from kdrive to xorg architecture, Graeme is now [http://lists.openmoko.org/pipermail/devel/2009-January/003964.html in debugging mode]. Andreas, Chris and Tom are also working on it.
* Miguel's [http://www.youtube.com/watch?v=rOBWSrI14BM video] showcases that the [[Arduino]], a popular open-source electronic prototyping platform, complements well the FreeRunner when it comes to reading sensors and controlling actuators.
* [[Qi]] supports the zImage kernel format.

== Tips and tricks ==

* Booting 2008.12 from a microsd fails with "Only GTA01 hardware supported by ASoc driver" ? Option "ro" on the kernel commandline is fatal for startup of 2008.12. Check your U-Boot env if you're using that for "ro", or try adding rw to /boot/append-GTA02 if you are on SD Card and Qi.
* tangogps 0.9.2 and 0.9.3 have an issue converting between coordinate formats in the western or southern hemispheres. If you use the DD.dd format it should display the correct value.
* Current FSO should support both the 2.6.24 and 2.6.28 kernels. The patch to use old FSO with new kernel is [http://trac.freesmartphone.org/ticket/293 here].
* Howto [https://docs.openmoko.org/trac/ticket/2192#comment:3 get the wrench and QWERTY] buttons in 2008.12 with the ASU theme.
* Chris Samuel offers a [http://www.csamuel.org/2009/01/08/echo-suppression-fix-for-qt-extended-442-on-openmoko-neo noise reduction+echo suppression patch and binary for QtE 4.4.2].

GTA03

2008-12-23T13:31:04Z

Treviño: /* GTA03 Specifications */

GTA03 is the codename of a phone that is currently in development by Openmoko. For more information about other phones in development, visit [[Phone Development]]. The GTA03 will be based on a more advanced system-on-a-chip of same family as the [[Neo FreeRunner]] ([[GTA02 revisions|GTA02]]). It will presumably differ from it by having EDGE and a camera. GTA03 will not include support for 3G networks.

{{Speculations}}

== GTA03 Specifications ==
The GTA03 will be based on the [[GTA02 revisions|GTA02]] introducing several major hardware changes

New:
* New case design
* New GSM chip (2.75/EDGE): [http://www.cinterion.com/en/ktcm/modules_terminals/gerneral_purpose/Scalable_platform/MC75i_TC63i_TC65i Cinterion, (Siemens) MC75i]
* New WiFi/Bluetooth chip: [http://www.marvell.com/press/pressNewsDisplay.do?releaseID=603 Marvell 88W8688]
* Different Battery ([[Wishlist/LiFePO4 Battery]] based? - for long life?)
* Camera
* SoC: [http://semicon.samsung.de/applicationprocessors/tracking/aboutS3C6410.aspx s3c6410]
* GPS: [http://www.u-blox.com/technology/u-blox5/index.html ANTARIS 5]
* Touchscreen: EETI PCAP7200 capacitive touch device [http://lists.openmoko.org/nabble.html#nabble-td1690756%7Ca1690756 driver].
Removed:
* SMEDIA Glamo

== GTA03 Evaluation Board ==
* AUG.11.2008: the 25 first GTA03EVB arrived in office
* Aug.12.2008: U-boot ported to GTA03EVB (Matt)
* Aug.12.2008: The core can run at 533 MHz with 133MHz SDRAM
* Aug.12.2008: GTA03EVB Hardware Verification of the u-blox 5 Antaris
* Aug.12.2008: GPS performance tested
* Aug.18.2008: GTA03EVB Hardware Verification of the Siemens MC 75i EDGE MODEM

== Sources ==
* http://n2.nabble.com/Weekly-Engineering-News-33-2008-tp729555p729555.html
* [[MokoForesight]]

[[Category:GTA03]]

[[Category:GTA03]]

Scummvm

2008-12-16T04:06:29Z

Treviño: /* ScummVM */

= ScummVM =

ScummVM is a program which allows you to run certain classic graphical point-and-click adventure games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the game, allowing you to play them on systems for which they were never designed!

You can obtain it either by using [[Mokomakefile]] via

# make build-package-scummvm

or using a binary, like so:

opkg install http://www.angstrom-distribution.org/feeds/2007/ipk/glibc/armv4t/base/libmad0_0.15.1b-r0_armv4t.ipk \
http://www.angstrom-distribution.org/feeds/2007/ipk/glibc/armv4t/base/libmpeg2-0_0.4.0b-r4_armv4t.ipk \
http://downloads.tuxfamily.org/3v1deb/openmoko/scummvm_0.12.0_armv4t.ipk

[[Image:MonkeyIsland.png|Monky Island]]

The games are copyrighted and the copyright holder has not given you a license to redistribute them so you'll only be able to play those you own. You can also download some free games from [http://www.scummvm.org/downloads.php#extras scummvm.org] and from the [http://www.the-underdogs.info Home of the Underdogs].

When starting ScummVM use the command

# openmoko-scummvm

This will map '''AUX''' button to the '''F5''' key, which is used to access the ScummVM menu. You should also find an entry on the main menu under ''Games''.

'''Note:''' On the Neo Freerunner the wrong keycode (not '''AUX''') is mapped to '''F5'''. Here is a corrected version of the file ''/usr/bin/openmoko-scummvm'':

<pre>#!/bin/sh

# Save current AUX Key mapping
SAVE_KEY="$(xmodmap -pke | grep 'keycode 177')"

# Map AUX Key to F5
xmodmap -e "keycode 177 = F5"

# Turn LCD feft
xrandr -o left

# Start the scummvm in fullscreen mode
scummvm --fullscreen --themepath=/usr/share/scummvm/

# Turn LCD normal
xrandr -o normal

# Restore the AUX Key mapping
xmodmap -e "$SAVE_KEY"</pre>

'''Note:''' It would be great if it where possible to get audio through the headphones and speaker muted.

More information on ScummVM can be found on the [http://www.scummvm.org/ official] site

=== Monkey Island 2 ===

To be able to play Monkey Island 2 you need to pass ScummVM a parameter:<br>
root@fic-gta01:/$ DISPLAY=:0 openmoko-scummvm --boot-param=10001 monkey2

For easy access from the menu you can create a menu entry by creating the file /usr/share/applications/monkeyisland2.desktop with the following content:

<pre>[Desktop Entry]
Encoding=UTF-8
Name=LeChuck's Revenge
Comment=Monkey Island 2: LeChuck's Revenge
Exec=openmoko-scummvm --boot-param=10001 monkey2
Icon=monkeyisland2.png
Terminal=false
Type=Application
Categories=Games;
StartupNotify=false</pre>

'''No Desktop Icon Method'''

Making a change to your scummvmrc does not clutter up your desktop with another icon and keeps the interface consistent. Add the following to your scummvmrc (default location of ~/.scummvmrc) at the top global section add:

copy_protection=0

And after adding the Monkey Island 2 via the Scummvm GUI add the following below the [monkey2] section:

boot_param=10001

Then you can launch Monkey Island 2 from the menu like any other game without the annoying copy protection screens.

<onlyinclude>
{{ApplicationBox|
Name=[[Scummvm]]|
Description=ScummVM is a program which allows you to run certain classic graphical point-and-click adventure games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the game, allowing you to play them on systems for which they were never designed!|
Screenshot=MonkeyIsland.png|
Homepage=http://www.scummvm.org|
TestedOn=|
PackageName=
}}
</onlyinclude>
'''Source Code released : http://www.scummvm.org/downloads.php#source'''

[[Category:Gaming]]

Applications

2008-12-16T04:03:43Z

Treviño: /* Games */

This is the wiki's master application list for the Openmoko smartphones.

== How to register new applications ?==

This list can not be exhaustive, as new things are showing up every week. This page is here to help spreading awareness about applications. Here are instructions on how to add a specific application to this list. There are many ways to go

Method 1 (preferred):
* Register your application at http://opkg.org. You will get a package number there, for example 33.
* Notify the community mailing list.
* Come back here, click on "edit" next to the appropriate section title, then add a line like:
<pre>* {{opkg.org|33|Application name}} A short description</pre>

Method 2: Just link to wherever the application is hosted.
* Click on "edit" next to the appropriate section title, add a line like:
<pre>* [http://your.host.domain/the/path/to/app/page.html Application name] A short description</pre>

Method 3: Create a new page in this wiki.
* Click on "edit" next to the appropriate section title, then add a line like:
<pre>* [[Application name]] A short description</pre>
* The application name will appear in red, click on it to create and edit the new page.

== Audio ==

* [[Openmoko-mediaplayer2]] - Play music and video (mp3...)
* [[Openmokast]] - Play audio stream and slideshow stream
* [[Pythm]] - Audio player GUI using mplayer and mpd as backend.
* [[Mokoko]]-Play music.
* [[Satan]] - Create your own music!
* [[Fourier]]- Realtime frequency analysis of sound data.
* [[Neoqplayer]] - a multimedia player written in Qt4
----

== Games ==

* [[Games/Om 2007.2]] - Many small games on Om 2007.2
* [[Om 2008.8 Sudoku]] - Number placement based puzzle game
* [[Moko-sudoku]] - Another sudoku puzzle game.
* {{opkg.org|66|ScummVM}} ([[Scummvm|Wiki]]) Virtual Machine for several classic graphical point-and-click adventure games
* [[Kobodeluxe]] - A top-view space shooter, available from 2008.8 repositories.
* [[Sander|Pingus]] - Pingus is a lemmings clone with penguins.
* [[Duke Nukem 3D]] - Legendary First Person Shooter.
* [[Numptyphysics]] - A drawing puzzle game.
* [[Gnuboy]] - An emulator for the handheld gaming all-time bestseller.
* [[XBill]] - Little action game to stop Bill from installing Windows(tm) on computers.
* [[Xlogical]]-A puzzle based game where you turn spinners to move balls around.
* [[Liquid War]]-Liquid War is a truly original multiplayer wargame.
* [http://unsyncopated.com/BrainSolvent/Doom%20Port DOOM]- Shooting game , now prot on FreeRunner.
* [http://www.opkg.org/package_49.html MBAC]- MBAC is "Moko Bulls and Cows", a classic game for openmoko written in pygtk similar to mastermind.
* [http://minucci.net/file/openvibe.py OpenVibe] - The first opensource vibrator.
* [http://scalde.free.fr/index.php?option=com_content&view=article&id=93:pong-pogresses&catid=43:openmoko&Itemid=66 Pong progresses]
* [[OpenMooCow]] - OpenMooCow reads information out of your accelerometers. Now, if you turn the phone upside down and back again, it "moos" like one of the little toy.
----

== GPS ==

* [[GPS Sight]] - Display GPS information, location, tracks, etc, without maps.
* [[Gpsdrive]] - Car (bike, etc) navigation system
* [[Om 2008.8 Locations]] - (aka Splinter) - Location sharing based on GPS and SMS
* [[Navit]] - Car navigation system with routing engine
* [[TangoGPS]] - Display map (OSM..), record GPS tracks...
* [[Pyroute]] - Pyroute is a routing program written in Python. It features mobile phone GUI for maps, GPS, and routing.
* [http://wiki.openstreetmap.org/index.php/Mumpot mumpot] - Display map (OSM), routing, OSM tag editing, a bit of live editing
* [[QMapControl]] - Display maps (OSM..) and add points, lines...
* [[Qpegps]] - Display map with current position
* [[Idle Hands]] - Give a task to you based on your location
* [[Gtkaddpoi]] - Utility for add a POI to TangoGPS using address or coordinates
* [[Gpsdcontrol]] A simple python script for start or stop gpsd daemon with a button on the desktop.

== Graphics ==

* [[Orrery]] - Displays the night sky
* [[OMView]] - Image viewer
* [[PyPenNotes]] - Write notes using pen and touchscreen
* [[Gpe-scap]] - Take screenshots
* [[Flash|Gnash]]-Play flash file on Neo

----

== Internet ==

* [[Twinkle]] - Voice over IP
* [[Linphone]] - Voice over IP
* [[Midori]] - Webkit based web browser
* [[Minimo]] - Mozilla based web browser
* [http://www.dillo.org/ Dillo] - Multiplatform fast and small web browser ([http://misc.andi.de1.cc/dillo/ .ipk]).
* [[Mokopedia]] - Read small Wikipedia dumps offline
* [[Openmoko-browser2]] - The original Openmoko web browser
* [[Openmokast]] - Play audio stream and slideshow stream
* [[Openmoko Mail]] - E-mail client
* [[Pidgin]] - Instant messaging client (ICQ, MSN, Jabber, Yahoo and more.)
* [[CenterIM]] - Instant messaging client (terminal-based).
* [[PyFeedRead]] - RSS feed reader
* [[Qtmail]] - Default mail program on Om 2008.8
* [[TwitterMoko]] - A Twitter client for Openmoko
* [http://code.google.com/p/pyqt-browser/ pyqt-browser] - modified the sample code from python-pyqt4 and changed it to use webkit for web browsing.
* [http://we.trekbeyond.org/~kd8ikt/moko/shr_pkgz/ ettercap-ng]

== Office ==
* [[Epdfview]] - PDF reader.
* Evince - Document reader for PDF, PS, DJVU and more.
* [[FBReader]] - E-book reader program (TXT, FB2, HTML and more)
* [[Gutenflash]] - Fast text reader by scrolling text
* [[OMoney]] - A bookkeeping application

== Settings ==

* [[Mofi]] - Wifi setup tool
* [[Lint-wifi]] - Wifi setup tool
* [[Om 2008.8 Installer]] - Graphical software installer
* [[Opkg]] - Command line software installer
* [[Sephora]] - Settings manager
* [[SettingsGUI]] - Edit various settings
* [[Wicd]] - Wifi setup tool
* [[ZOMG!]] - A graphical package manager (opkg frontend -> should work on any distro)

== System ==
* [[Auxlaunch]] - Finger-friendly app launcher and window switcher
* [[Display Locker]] - Screen lock
* [[Gestures]] - Detect movement and display information, rotate screen
* [[Keychain]] - SSH keys
* [[MokoFEM]] - Monitors GSM information
* [[Mokostat]] - Monitors battery
* [[Openmoko Bluetooth remote controller|ReMoko]] - Control stuff via BlueTooth
* [[Rotate]] - Rotate screen when phone is rotated
* [[Terminal]] - Commando prompt
* [[Ts calibrate]] - Calibrates touchscreen
* [[Zedlock]] - Screen locker
* [http://fso-control.projects.openmoko.org/ fso-control] - Popup Power menu to shutdown/suspend/reboot.
* [[omkeys_functions]] - Remap AUX key bindings
* [[Siglaunchd]] - A daemon that listens to dbus signals and launches appliactions upon arrival.
* [[Pexpect]]-a pure Python module for spawning child applications; controlling them; and responding to expected patterns in their output.

----

== Telephony ==
* [[Dialer/2007.2]] - The dialer application in Om 2007.2
* [[Openmoko SMS Middleware]]- SMS middleware is a Openmoko middleware software for additional features related to SMS. Plugin architecture and Python based code gives this project lots of flexibility and enchancebility.
* [[Paroli]] -Paroli is an integrated phone application based on Tichy (and so also written in python).

----

== Utility ==
* [[Unison]] - Unison is a file-synchronization tool for Unix and Windows. It determines all differences between two directory trees and lets the user decide, how to proceed with every differing file.
* [[HP48 Series RPN Calculator]] - Calculator with many functions
* [[qwo]]- An alternative input method.
* {{opkg.org|57|fido}} - [[fido]] is a todo list\note manager written with elementary
* [http://meuk.spritesserver.nl/lightsaber-0.1.tgz The Lightsaber]. Pre-alpha starwaresque orphanware.
* [[NeoTool]] NeoTool is a bash script for your desktop system to provide a friendly GUI frontend to some common management tasks.
* [[NeoCon]] - neocon is a handy serial console utility (not only) for u-boot. The main feature of neocon is actually that you can give it a list of devices and it will pick one that works.
* [[AaTerm]]-Terminal that have features like openmoko-terminal2, but have space like xterm.
* [http://techiem2.net/index.php?/archives/10-Freerunner-USB-Mode-Control-Program.html usbmode]-a quick pygtk program.
* [[Enotes]] - Enotes is the implementation of a TODOlist manager written with elementary to appear better with distribution that use illume, like SHR.

----

==Setting Application==
* [[Wmiconfig]]- wmiconfig is a tool written by Atheros Communications Inc to configure the Ar6k WIFI chip used in the Neo Freerunner. This is a standalone C executable, released under GPL v2.
* [[GTA02 sysfs]]- 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 use it to change settings and behaviours of the kernel and drivers dynamically.

== Video ==

* [[Video Player]] - Using Mplayer on Openmoko smartphones.
* [http://katastrophos.net/andre/blog/software/quasar-media-player/ Quasar] - a mplayer frontend for X11.

----

== daemon ==
* [[PyPhonelog]] - daemon uses the framework to track and log all the calls made to and from the moko.
* [[Lscd]] - LSC library/daemon on Linux System.

== An automatic list of application-related wiki pages ==

The pages linked above are all maintained manually. We also maintain an automatic categorization system by tagging wiki pages. Here is the list of application-related pages in this wiki. Normally, every page listed below should be also listed above in the same category. The converse is false: there are applications without a wiki page.

<div style="border: solid 1px black; padding: 1ex"><b>Applications in this Wiki:</b>
<categorytree mode=pages depth=2 hideroot=on>Applications</categorytree>
</div>

== Where to find more applications? ==

At [http://opkg.org opkg.org] !

Not all Openmoko apps are listed on this wiki - there are much more [http://projects.openmoko.org/softwaremap/ projects at the Openmoko GForge] than the wiki can list, not to mention self-hosted applications on their own websites. Actually the phones can run most Linux based Free Software, using for example the [[Debian]] distribution. The [http://handhelds.freshmeat.net/browse/1038/ mobile phones section of Freshmeat] may be a interesting place to look.

Note also that there are many packages in the repository that are not installed by default. If what you want is a classic, chances are that it is already packaged. Suppose you want to install Perl:
opkg list|grep perl
opkg install perl

More application download related pages:

* [[Community Repository]]
* [[Users Repositories]]

<div style="clear:both"> </div>

== Where to find full distributions ? ==

* [[Download]]: for complete system downloads

== The usual warnings ==
<small>
* Some of these software are developed by Openmoko Inc. and some are contributed by the community. Any problems with community contributed software should be reported to the individual software developer rather than the Openmoko core team.
* Most programs listed here are not mature/stable, but only useable/beta.
* Many programs listed here are not yet packaged for your distribution and integrated in its repositories. Whichever it is.
* Installing experimental software from the internet is certain to break things. Running it as root is a very insecure thing to do. Kown that you will be burned, have backups, and be ready to apologize to everybody in your phone contact list in case they receive strange SMSs...
</small>

[[Category:Applications|Applications]]
[[Category:Basic End User]]

Buzz or not

2008-12-11T18:50:19Z

Treviño:

== Who suffers from the buzz and who doesn't? ==

We, people who have a phone with an anoying buzz (and because off that are not able to place normal phone calls with this phone), need your input to identify why only some people suffer from the infamous buzz problem

Who is "WE"? On OM-HW-EE side this poll isn't considered helpful, as it contains no info whatsoever about actual network-situation (which is widely assumed to be the cause of buzz appearing in a particular situation). Please note the original poster seems not affiliated to OM technical staff, and we (OM) might eventually ask our customers to support a different poll. Also note there's a rework paper to fix buzz, a non-verified draft for now [jOERG]

We, I like to think, are the people who are having a problem using the FreeRunner as a phone. If you want to put up an official OpenMoko poll/questionnaire please do so, but can you make it quick? Tel us how people who can't handle a soldering tool in a professional way can fix their phones. [Michel an OpenMoko '''customer''' and believer that a phone can be open source]

([http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]).

Put your information in the form below.

{| border="1" cellpadding="2" cellspacing="0"
!Name
!Country
!Buzz Y/N
![http://docs.openmoko.org/trac/ticket/1267 Echo] Y/N
![http://docs.openmoko.org/trac/ticket/1841 WSOD] Y/N
![http://docs.openmoko.org/trac/ticket/1024 Bouncing Calypso] Y/N
!Date code (1)
!s/n
!p/n
!Carrier
!Mhz (2)
!Distro
!Remarks/Comments
|-
|mivaho
|NL
|Y
|?
|N
|?
|20080617
|8A8603161
|56-21147-00
|T-Mobile
|900
|FSO 4.1
|Didn't test buzz with headset
|-
|Rakshat
|India
|N
|N
|N
|?
|20080618
|8A8602471
|56-21147-00
|Airtel
|900
|QTExtended4.2.2
|No echo since flashing QTExtended
|-
|Vasco Nevoa
|Portugal
|Y
|Y
|N
|N
|20080621
|8A8602272
|56-21147-00
|Optimus (mostly GSM1800)
|900
|OM2008 testing (20081211)
|Didn't test buzz with headset
|-
|Andreas Fischer
|Germany
|N
|Y
|N
|?
|20080725
|8A8710691
|56-21147-00
|O2 (Telefonica)
|900
|OM2008 testing (20081211)
|Didn't test buzz with headset
|-
|Simon Fiebiger
|Germany
|Y
|Y
|N
|?
|20080722
|8A8704112
|56-21147-00
|Fonic / Blau
|1800 / 1800
|OM2008 testing (20081211)/ SHR
|tested w/o Headset - Buzz only with GSM1800
|-
|Simon Fiebiger
|Germany
|N
|Y
|N
|?
|20080722
|8A8704112
|56-21147-00
|Vodafone / Congstar
|900 / 900
|OM2008 testing (20081211)/ SHR
|tested w/o Headset - No Buzz at all with GSM900
|-
|Drac
|Canada
|Y
|Y
|?
|?
|20080620
|8A8604782
|56-21146-00
|Fido
|850 / 1900
|QTExt 4.2.2 / FDOM 23Oct
|Buzz 90% of the time , Echo 30% using QtExt
|-
|Nathan Kinkade
|U.S.A.
|N
|N
|N
|?
|20080621
|8A8604521
|56-21146-00
|T-Mobile / AT&T
|850
|FDOM (QtExt. 4.2.2, Om2008.[8,9])
|
|-
|marrano
|Italy
|Y
|Y
|Y
|?
|20080521
|8B8400153
|56-21147-00
|Wind
|900
|every
|
|-
|Treviño
|Italy
|N
|Y
|N
|N
|20080621
|8A8603221
|56-21147-00
|Wind
|900
|Om2008
|Echo solved by using the Calypso hidden commands.
|}

1 = Date code on phone (under battery)

2 = 850 (USA,etc.) or 900 (Europe,etc.)

Android

2008-12-05T18:30:34Z

Treviño: /* Building the Koolu Android Source */

{{Languages|Android}}
{{Distributions|Android}}

= Updates =
* 20081202 [http://www.koolu.com Koolu.com] has released the source code for the FreeRunner port of Android in their git repositories at [http://git.koolu.org/ Koolu GIT] ([http://koolu.com/Press-Release/ Press Release])
* 20081120 [http://www.koolu.com Koolu.com] has pushed back selling the OpenMoko Freerunner with Android pre-installed , as well as offering free downloads of the Freerunner port of Android to existing Freerunner owners. Untill December 2008
* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']
* 20081029 [[User:Cfriedt]] [http://benno.id.au Benno] has modified Android's build system so that it will output a JFFS2 image instead of YAFFS . Unlike JFFS2, which [http://wiki.openmoko.org/wiki/Userspace_root_image can be mounted read-only from an image], mounting a YAFFS image is not possible unless it's already been written to flash (it complains about the block device being of type '1' and not 'NAND'). JFFS2 also has the benefit that it's a standard OpenMoko image format (See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]])
* 20081023 [[User:Bricode]] To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw
* 20081022 [[User:Cfriedt]] I was able to 'trivially' compile all of the Android source code without error for the ARMv4T architecture by removing v5TE instructions. Although it will definitely not run anything predictably, at least now that I know the build system will work with a few simple substitutions in build/core/combo/arm-linux.mk. At this point I am able to go ahead and re-implement v5TE instructions as v4T instruction sequences instead (or re-implement entire sections of assembly with hand-optimized v4T instructions).
* 20081021 [[User:Cfriedt]] Android -> FreeRunner updates on my [http://perpetual-notion.blogspot.com/search/label/android blog]
* 20081021 Google released the majority [http://source.android.com/download source code] for the phone under Apache free and open-source [http://source.android.com/license license], with portions covered by other existing licenses, such as the Linux kernel under GPLv2.
* 200810?? [http://www.koolu.com Koolu.com] has announced that they will be '''selling the OpenMoko Freerunner with Android pre-installed''' beginning in November 2008, as well as offering '''free downloads of the Freerunner port of Android''' to existing Freerunner owners. Well-known open-source advocate [http://koolu.com/The-Koolu-Team/maddog.html Jon "maddog" Hall] is CTO and Ambassador for Koolu.

= Introduction =
This page is dedicated to porting the [http://www.android.com Android OS] to the [[Neo 1973]] and [[Neo FreeRunner]] handsets. Since the Android OS was [http://source.android.com/posts/opensource publically released] on 20081021, [http://benno.id.au/blog/2007/11/21/android-neo1973 work] [http://perpetual-notion.blogspot.com/search/label/android is] [http://groups.google.com/group/android-porting currently underway] to port Android to the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

== Goals ==
# Systematically introduce patches for ARMv4T in the Android codebase
# Provide Neo1973 and Neo FreeRunner hardware-dependent patches in the Android codebase, leveraging the work already done by the Openmoko developers, without forcing Android-specific changes upstream
# Provide a useable Android filesystem and kernel on the [[Distributions]] page that conform to current Openmoko installation routines

== Early Attempts ==
As [http://benno.id.au Ben Leslie] had pointed out on his [http://benno.id.au/blog/2007/11/21/android-neo1973 blog] far before the source code was released, [http://www.android.com Android] was originally designed to work with the ARMv5TE [http://en.wikipedia.org/wiki/Instruction_set_architecture instruction set architecture] (ISA), which allows for [http://en.wikipedia.org/wiki/ARM_architecture#DSP_Enhancement_Instructions DSP enhanced instructions]. Contrary to the ARMv5TE ISA, the Neo1973 and FreeRunner handsets both feature an arm920t core, which comply to the ARMv4T ISA.

Before the source code was released, kernel trap handlers were implemented to 'emulate' the ARMv5TE ISA. Although the results worked in many cases, trapping is costly and performance suffered as a result. Moreover, without explicitly knowing which conditions were set by various instructions, such as Thumb Mode execution, the result became nondeterministic.

== Current State ==

With the release of the Android [http://source.android.com source code], the Open Source community is no longer limited to dealing with a binary-only product. The Open Handset Alliance (OHA) has let their source code become their product for everyone enrich and benefit from.

Currently, porting efforts are underway in many circles. Patches should be submitted via the [http://source.android.com/submit-patches official Android channels].

[http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.com http://git.koolu.com]. See the [[#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw [[User:Bricode]]

[[User:Seanmcneil3|Sean McNeil]] said that he was able to get Android running (including telephony) in his Freerunner [http://3v1n0.tuxfamily.org/tumblelog/post/368 source].

Ben Leslie mentioned on the android-porting list that he was able to get the 'Android' logo to appear on his Neo 1973.

=== Building the Koolu Android Source ===

# Configure your machine with the prerequisites documented in the [http://source.android.com/download#TOC-Setting-up-your-machine Setting up your machine] section of Google's build instructions.
# Install <tt>repo</tt> and download the source, as documented at http://trac.koolu.org/, '''but before running the <tt>make</tt> command in step 7, do the following:'''
# Install the toolchain provided by Koolu at http://trac.koolu.org/attachment/wiki/Toolchain/android-toolchain_20081019-koolu1_i386.deb.
# Create a ''<tt>buildspec.mk</tt>'' file at the top level of your Android source tree, and add the following line to it:
<pre>
TARGET_TOOLS_PREFIX := /opt/android-toolchain/bin/armv4t-android-eabi-
TARGET_PRODUCT := freerunner
</pre>
as documented at http://trac.koolu.org/wiki/Toolchain.
# Now you can start the build with the following command: <pre>$ make </pre>
# After the build finishes you can put together a root file system by editing and running Sean McNeil's scripts, which are attached to [http://lists.openmoko.org/pipermail/community/2008-December/036982.html this message]. The first script (cp_android_OS) is used to copy the newly built files into a staging area. The second one (mkjffs2) makes a jffs2 image from the staging area. Be sure to edit the paths in the two files to match your environment.
# The output of the second script is a file, <tt>androidfs.jffs2</tt>, which may be flashed to your Freerunner.

==== Building an jffs2 image ====
You can use this script:
<pre>
#!/bin/sh

currentdir=`pwd`

ANDROID_OUT=out
ANDROID_DEVICE=freerunner
EXPORT_ROOT=$currentdir/build_jffs2_tmp

Usage()
{
echo "Usage: $0 release|debug jffs2filename"
}

BuildImage()
{

if [ -d $1 ]
then
echo "[INFO] Copying from... $1"

sudo rm -rf $EXPORT_ROOT
mkdir $EXPORT_ROOT
mkdir $EXPORT_ROOT/root

# Copy the image...
cd $1
tar cf - root | (cd $EXPORT_ROOT; sudo tar xf -)
tar cf - system | (cd $EXPORT_ROOT/root; sudo tar xf -)

# Change owner and permissions...
cd $EXPORT_ROOT
sudo chown -R root:root root
sudo chmod -R 777 root

cd $currentdir

# Make the JFFS2 file
mkfs.jffs2 --pad=0x700000 -o $2 -e 0x20000 -n -d$EXPORT_ROOT/root/
echo "[INFO] Image written to $2"

sudo rm -rf $EXPORT_ROOT
else
echo "$1 does not exist!"
fi
}

if [ $# != 2 ]
then
Usage
else

case $1 in
release)
BuildImage $ANDROID_OUT/target/product/$ANDROID_DEVICE $2
;;
debug)
BuildImage $ANDROID_OUT/debug/target/product/$ANDROID_DEVICE $2
;;
*)
Usage
esac
fi

</pre>

There is currently no documented way to build a Freerunner/Android kernel. [[User:Seanmcneil3|Sean McNeil]] has been releasing kernels at http://people.openmoko.org/sean_mcneil/. Most of the patches required to run Android have be incorporated into the <tt>andy-tracking</tt> kernel branch, which will eventually be the new stable kernel. Once all the patches are in the kernel, it should be possible to run Android with a stock kernel.

=== Windows Connectivity ===

It is possible to get Windows to at least recognize the Android "Ethernet Gadget" and charge the FreeRunner using the Android USB Windows driver (http://dl.google.com/android/android_usb_windows.zip) by modifying the android_usb.inf file in that package before attempting to install the driver. The following modifications are required:

Add the following to the [Google.NTx86] section of the android_usb.inf file:

<pre>
; Neo FreeRunner
%USB\VID_1457&PID_5117.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117
%USB\VID_1457&PID_5117&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117&MI_01
</pre>

and add the following to the to the [Strings] section of the android_usb.inf file:

<pre>
USB\VID_1457&PID_5117.DeviceDescRelease="Neo FreeRunner"
USB\VID_1457&PID_5117&MI_01.DeviceDescRelease="Neo FreeRunner Composite ADB Interface"
</pre>

The Windows version of adb does not appear to recognize the connected device yet but at least the FreeRunner charges and the device driver indicates that "This device is working properly."

= How to Help =

== Getting Started ==

You can start by following the instructions to download and build the Android source from scratch. Please see [http://source.android.com/download http://source.android.com/download] and follow the instructions for your architecture.

== Publicize Your Efforts ==

It's generally a good idea to make your efforts known via wiki systems, public mailing lists, forums, and publically open version control systems.

Always take credit for your work but please don't do it in the form of comments. Some code is already hard enough to read without comments polluting the text. The best thing to do is to create a patch and put a header with your information at the top. Collaboration systems such as git might already do this for you (??).

If you create something new and have the ability to designate the license for it, please consider license compatibility issues.

== Porting Strategy ==

* Analysis and leverage of the existing build system
** buid/core/combo/arm-linux.mk
*** -D__ARCH_ARM_4__ -D__ARCH_ARM_4T__
*** -march=armv4t -mcpu=arm920t
** fix various static references to 'armv5'
* Isolating ARMv5TE ISA dependent code
** e.g. grep -n -R -i "${armv5te_isa_pattern}" ~/android
* Abstracting
** ( C/C++ )
*** Use inlined functions / #ifdef statments to implement functions in a portable manner
*** For inlined assembler calls, it's acceptable for now to use generic C code instead, so long as later on we optimize it by hand.
** ( ASM )
*** Proprocessor statements based on ISA / architecture, e.g. #ifdef __ARCH_ARM_5__ ... #endif #ifdef __ARCH_ARM_4__ ... #endif
*** It's highly suggested that preprocessor statements should not be nested (i.e. make them mutually exclusive)
*** Some people have suggested that we should not do #ifdef's based on ARCH or ISA, but rather based on an AndroidConfig.h which would define macros like PLD(...) #ifdef HAVE_ARM_PLD pld #else ... #endif .

For each ARMv5TE instruction, one could potentially
* Implement the instruction using general registers instead of DSP calls (i.e. eabi / softfloat)
* If that is a) nondeterministic, or b) slow, then sections of code need to be analyzed and hand-optimized for the ARMv4T isa

== List of Unsupported Instructions ==

This is a list of opcodes, extracted from the Android source, that are unsupported for ARMv4T compliant processors (specifically the arm920t). The opcodes represent instructions available for ARMv5, ARMv5T, and ARMv5TE architectures, which are not present in the ARMv4T ISA. The list was obtained by exhaustively editing the recompiling the Android source code until it compiled without error.

Please keep in mind, that in some cases, translating these instructions into a sequence of ARMv4T instructions will be impossible and / or result in nondeterministic execution because of
* the requirement of additional context
* the tendencies of certain opcodes to change condition registers that may or may not be present in the arm920t core

=== Opcodes ===

{{scroll box|height=480px|text=
<TABLE BORDER="1">
<TR>
<TH>Opcode</TH>
<TH>Desription</TH>
<TH>[[http://www.arm.com/miscPDFs/14128.pdf PDF]] Page Number</TH>
<TH>C</TH>
<TH>ASM</TH>
</TR>
<TR>
<TH VALIGN="TOP">BLX(1)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>166</TD>
<TD>N/A (Unused in Android)</TD>
<TD>N/A (Unused in Android)</TD>
</TR>
<TR>
<TH VALIGN="TOP">BLX(2)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>168</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_BLX
... (inline asm) ...
#else
... (inline asm with equivalent blx code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_BLX
#define BLX(a) \
blx a
#else
#define BLX(a) \
mov pc,lr \
bx a
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">CLZ</TH>
<TD>Count Leading Zeros</TD>
<TD>175</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_CLZ
... (inline asm) ...
#else
... (inline asm with equivalent clz code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081029
<pre>
#ifdef HAVE_CLZ
#define CLZ(Rd,Rm) \
clz Rd,Rm
#else
#define CLZ(Rd,Rm) \
...
#endif
...
CLZ(Rd,Rm)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">LDRD</TH>
<TD>Load Registers Doubleword</TD>
<TD>200</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_LDRD
... (inline asm) ...
#else
... (inline asm with ldrd substituted) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_LDRD
#define LDRD(a,b) \
ldrd a,b
#else
#define LDRD(a,b) \
...
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">PLD</TH>
<TD>Preload Data</TD>
<TD>240</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_PLD
... (inline asm) ...
#else
... (inline asm with pld removed) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove or substitute with a macro reference such as
<pre>
#ifdef HAVE_PLD
#define PLD(a,b) \
pld a,b
#else
#define PLD(a,b)
#endif
...
PLD(r0,#0)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLA<x><y></TH>
<TD>Signed Multiply-Accumulate</TD>
<TD>291</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAL<x><y></TH>
<TD>Signed Multiply Accumulate Long</TD>
<TD>298</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAW<y></TH>
<TD>Signed Multiply-Accumulate Word</TD>
<TD>302</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMUL<x><y></TH>
<TD>Signed Multiply</TD>
<TD>316</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULW<y></TH>
<TD>Signed Multiply Word</TD>
<TD>320</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QADD</TH>
<TD>Saturating Add</TD>
<TD>242</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDADD</TH>
<TD>Saturating Double and Add</TD>
<TD>249</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDSUB</TH>
<TD>Saturating Double and Subtract</TD>
<TD>251</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QSUB</TH>
<TD>Saturating Subtract</TD>
<TD>253</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">STRD</TH>
<TD>Store Registers Doubleword</TD>
<TD>349</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_STRD
... (inline asm) ...
#else
... (inline asm without strd) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_STRD
#define STRD(a,b) \
strd a,b
#else
#define STRD(a,b) \
...
#endif
</pre>

</TD>
</TR>
</TABLE>
}}

=== Scanning for Files That Use the ARMv5TE ISA ===

Using the above list of opcodes, one can scan the Android source code for ARMv4T-incompatible instruction sequences.

'''Code:'''
{{scroll box|height=240px|text=
<pre>
#!/bin/sh

# $1 is the android directory

if [ $# -ne 1 ]; then
exit -1
fi

cd "${1}"

opcodes="blx clz ldrd pld smlabb smlabt smlatt
smlal smlawb smlawt smulbb smulbt smultt smulwb
smulwt qadd qdadd qdsub qsub strd"

for op in ${opcodes}; do

echo "* ${op} ====================================="

if [ ! -e .files.${op} ]; then

files="$(grep -R -i "${op} " * 2>/dev/null)"
files="$(echo $files | grep -v "^Binary file" | sed -e 's/:.*//')"
files="$(echo $files| grep -v "CREDIT\|README\|^$kernel/\|.git/$\|$\.txt$$" | sort -u)"

echo "${files}" > .files.${op}

else
files="$(cat .files.${op})"
fi

for fil in ${files}; do
lines="$(grep -n -i "${op} " ${fil} | sed -e 's/:.*//g' )"
lines="$(echo $lines | sed -e 's/ /,/g')"
echo "** ${fil}: lines {${lines}}"
done
done
</pre>
}}

=== Source Files in Android that Use the ARMv5TE ISA ===

The list of files below may or may not be complete. There might also be some assembly code that is generated with a python script (verification?).

{{scroll box|height=150px|text=
* blx =====================================
** bionic/libc/tools/gensyscalls.py: lines {168,186}
** bootloader/legacy/nandwrite/init.S: lines {77}
** bootloader/legacy/usbloader/init.S: lines {95}
** dalvik/vm/arch/arm/CallEABI.S: lines {239}
** dalvik/vm/arch/arm/CallOldABI.S: lines {145}
** development/emulator/qtools/thumbdis.cpp: lines {187,265}
** external/qemu/target-arm/translate.c: lines {1151,1971,2444}
** external/qemu/trace.c: lines {774,1353,1358}
** system/core/libpixelflinger/codeflinger/disassem.c: lines {416}
* clz =====================================
** development/emulator/qtools/armdis.cpp: lines {654}
** external/opencore/codecs_v2/audio/aac/dec/src/pv_normalize.h: lines {67,84}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/norm_l.h: lines {137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/normalize_amr_wb.h: lines {78,95}
** external/opencore/codecs_v2/audio/mp3/dec/src/pvmp3_normalize.h: lines {67,84}
** external/opencore/codecs_v2/video/avc_h264/dec/src/vlc.cpp: lines {23}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/vlc_encode_inline.h: lines {125,162,168,204,218}
** external/qemu/target-arm/translate.c: lines {1247}
** external/skia/libcorecg/Sk64.cpp: lines {340,341,343}
** external/skia/libcorecg/SkMatrix.cpp: lines {500,501}
** external/skia/libsgl/effects/SkColorMatrixFilter.cpp: lines {135}
** external/skia/libsgl/sgl/SkBitmap.cpp: lines {945,946,947}
** external/skia/libsgl/sgl/SkBitmapShader.cpp: lines {32,33,34}
** external/skia/libsgl/sgl/SkGraphics.cpp: lines {429,437}
* ldrd =====================================
** dalvik/vm/mterp/armv5/OP_AGET_WIDE.S: lines {28}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE.S: lines {37}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE_QUICK.S: lines {10}
** dalvik/vm/mterp/armv5/OP_SGET_WIDE.S: lines {17}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2653,7464,8318,8390}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {40,41,42,43}
* pld =====================================
** bionic/libc/arch-arm/bionic/memcmp.S: lines {37,44,45,56,57,107,108,195,196}
** bionic/libc/arch-arm/bionic/memcmp16.S: lines {37,44,45,67,68,116,117,198,199}
** bionic/libc/arch-arm/bionic/memcpy.S: lines {55,56,57,145,266,293,320}
** bionic/libc/arch-arm/bionic/strlen.c: lines {59,65}
** bionic/libc/kernel/arch-arm/asm/arch/irqs.h: lines {162}
** external/elfutils/src/Makefile: lines {243}
** external/elfutils/src/Makefile.am: lines {32}
** external/elfutils/src/Makefile.in: lines {243}
** external/jpeg/jidctfst.S: lines {69,235,247}
** external/qemu/target-arm/translate.c: lines {1149}
** system/core/libpixelflinger/codeflinger/ARMAssembler.cpp: lines {368}
** system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp: lines {104,108,117}
** system/core/libpixelflinger/t32cb16blend.S: lines {111,112,134,143}
* smlabb =====================================
** external/jpeg/jidctfst.S: lines {110,115,155,156}
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {584,589}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {147,166}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {120,129}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {514,533}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {418,429}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {202}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {250}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {119,155,167,278,326,341}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {178,225,437,517}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {405,436}
* smlabt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {184}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {138}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {131,143,294,310}
* smlatt =====================================
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {585,590}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {157}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {441}
* smlal =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4.h: lines {179,223,236,257,267}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4_gcc.h: lines {264,341}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {178,188,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9.s: lines {84,90,96,101,109,114,116,118,121,132,138,150,163,165,167,174,176,178}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9_gcc.s: lines {73,79,86,90,98,103,105,107,110,121,127,139,152,154,156,163,165,167}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.asm: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.s: lines {145,164,180,190,194,201,209,219,227,233,239,243,246}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18_gcc.s: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.asm: lines {62,63,66,72,76,77,81,82,85,90,94,97,99,100,103,108,113,114,118,119,122,129,136,137,176,179,183,187,190,193}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.s: lines {67,68,71,77,81,82,86,87,90,95,99,102,104,105,108,113,118,119,123,124,127,134,141,142,181,184,188,192,195,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window_gcc.s: lines {65,66,69,75,79,80,84,85,88,93,97,100,102,103,106,111,116,117,121,122,125,132,139,140,179,182,186,190,193,196}
** external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm.h: lines {148}
** external/qemu/trace.c: lines {813}
** frameworks/base/opengl/libagl/iterators.S: lines {66,67}
** frameworks/base/opengl/libagl/matrix.h: lines {67,68,96,126,127,282,283,314,315,316}
* smlawb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {203,259}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {166,416}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {93,109}
** frameworks/base/opengl/libagl/matrix.h: lines {163,203}
* smlawt =====================================
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {114}
** frameworks/base/opengl/libagl/matrix.h: lines {162,202,243,244}
* smulbb =====================================
** external/jpeg/jidctfst.S: lines {109,114,151,153}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {79}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {71,81}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {207,251,297,348,361,375,427,440,487}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {199,234,274,314,316,326,367,369,404}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {121,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {123,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {122,140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {132,134,138,164,177,191}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {127,129,150,163}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mult.h: lines {121,141}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {115,139,151,163,189,190,212}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {112,113,164,183,201,218,265}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {250,457,531}
** external/skia/include/corecg/SkMath.h: lines {170}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {420,462}
** system/core/libpixelflinger/t32cb16blend.S: lines {39,66,74,82}
* smulbt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {115}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {109}
** system/core/libpixelflinger/codeflinger/texturing.cpp: lines {1091}
** system/core/libpixelflinger/t32cb16blend.S: lines {47,55}
* smultt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {131}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {100}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {467}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {73}
* smulwb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {221}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {373}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {222}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {283}
** external/opencore/codecs_v2/audio/sbc/enc/src/sbcenc_filter.h: lines {33}
** frameworks/base/opengl/libagl/matrix.h: lines {161,201,242}
* smulwt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {202,240}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {385,415}
* qadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {64}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {60}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {130,256}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {128,235}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_add.h: lines {122,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {123,145}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {71,102,152,176,192}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {91,115,148,202,234}
** external/openssl/crypto/bn/bn_prime.c: lines {454,455}
* qdadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/calc_sbr_synfilterbank.cpp: lines {116,162}
** external/opencore/codecs_v2/audio/aac/dec/src/trans4m_freq_2_time_fxp.cpp: lines {472,494}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {212,356,370,385,435,449}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {200,315,321,331,368,371}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {122,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {133,136,140,172,186,201}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {128,131,158,172}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {116}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {184}
* qdsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {302}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {275}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {124,147}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {165}
* qsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {167}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {162}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_sub.h: lines {121,138}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {88,127}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {70,133}
* strd =====================================
** dalvik/vm/mterp/armv5/OP_APUT_WIDE.S: lines {31}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE.S: lines {39}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE_QUICK.S: lines {14}
** dalvik/vm/mterp/armv5/OP_SPUT_WIDE.S: lines {21}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2834,7530,8331,8542}
** dalvik/vm/oo/Object.h: lines {589}
** external/opencore/fileformats/avi/parser/include/pv_avifile_streamlist.h: lines {179}
** external/opencore/fileformats/avi/parser/src/pv_avifile_streamlist.cpp: lines {153}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {47,52,56,60}
}}

=== Discussion ===
=== Notes ===
The file
<pre>
system/core/libpixelflinger/codeflinger/ARMAssembler.cpp
</pre>

will need special attention. It's responsible for dynamic generation of DSP code.

== Suggestions ==
* [[User:Cfriedt]] 20081024 I'm not sure how feasible this is, given that the [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#SMedia_3362_Documentation_.26_OpenGL_ES_Drivers SMedia 3362 is heavily NDA'd]. However, since the arm920t lacks a floating-point unit / DSP core, is it possible to use the SMedia chip for general-purpose math? This would help in the Android platform, at least, for things like audio and video codecs. Aside from an OpenGL ES driver, OpenMoko documentation for the SMedia would be highly appreciated.

= Important Links =
(Please Update Me)

== Documentation ==
* [http://source.android.com/documentation Android Documentation]
* [http://www.arm.com/documentation/ ARM Documentation], (keywords: armv4t, armv5t, armv5te, arm920t, arm926ej-s)
* [http://www.arm.com/miscPDFs/9658.pdf ARM Assembly Language Programming]
* [http://www.cse.unsw.edu.au/~cs3221/labs/assembler-intro.pdf An Introduction to the GNU Assembler]
* [http://www.heyrick.co.uk/assembler/apcsintro.html ARM Procedure Call Standard], [http://en.wikipedia.org/wiki/Calling_convention#ARM ARM Calling Conventions]

== Instruction Set References ==
* [http://www.arm.com/miscPDFs/14128.pdf ARM Architecture Reference Manual], The definitive ISA documentation
* [http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf ARM Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001l/QRC0001_UAL.pdf ARM and Thumb -2 Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0025b/DVI0025.pdf ARMv4T] (See section 1.4.13)
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0014a/DVI0014A_ARM10T_PO.pdf ARMv5T] (See section 4.16)
* [http://www.arm.com/pdfs/ARM-DSP.pdf ARM DSP Enhanced Instruction Set]
* [http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042c/IHI0042C_aapcs.pdf Procedure Call Standard for the ARM Architecture]

== Hardware Reference ==

* [[Neo1973 Hardware]]
* [[Neo FreeRunner GTA02 Hardware]]

== Communities ==
* [http://source.android.com/discuss Android Public Mailing Lists]
** Specifically, [http://groups.google.com/group/android-porting android-porting]
* [http://lists.openmoko.org/mailman/listinfo OpenMoko Mailing Lists]
** Specifically, [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel openmoko-kernel]
* [http://forum.koolu.org/viewforum.php?f=10 Android on FreeRunner] at KoolU.com
* [[Openmoko Local Groups]]
* [[Openmoko:Community_Portal]]

= See also =

* [[Debug_Board]]

= External Links =
== Youtube video /Android on FreeRunner ==

[http://tw.youtube.com/watch?v=m4NbsLmF9j0 Video 1]

[http://tw.youtube.com/watch?v=r6Op-7tNTiw Video 2]

== Headline text ==

[[Category:Distributions]]

Android

2008-12-05T18:29:43Z

Treviño: /* Building the Koolu Android Source */

{{Languages|Android}}
{{Distributions|Android}}

= Updates =
* 20081202 [http://www.koolu.com Koolu.com] has released the source code for the FreeRunner port of Android in their git repositories at [http://git.koolu.org/ Koolu GIT] ([http://koolu.com/Press-Release/ Press Release])
* 20081120 [http://www.koolu.com Koolu.com] has pushed back selling the OpenMoko Freerunner with Android pre-installed , as well as offering free downloads of the Freerunner port of Android to existing Freerunner owners. Untill December 2008
* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']
* 20081029 [[User:Cfriedt]] [http://benno.id.au Benno] has modified Android's build system so that it will output a JFFS2 image instead of YAFFS . Unlike JFFS2, which [http://wiki.openmoko.org/wiki/Userspace_root_image can be mounted read-only from an image], mounting a YAFFS image is not possible unless it's already been written to flash (it complains about the block device being of type '1' and not 'NAND'). JFFS2 also has the benefit that it's a standard OpenMoko image format (See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]])
* 20081023 [[User:Bricode]] To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw
* 20081022 [[User:Cfriedt]] I was able to 'trivially' compile all of the Android source code without error for the ARMv4T architecture by removing v5TE instructions. Although it will definitely not run anything predictably, at least now that I know the build system will work with a few simple substitutions in build/core/combo/arm-linux.mk. At this point I am able to go ahead and re-implement v5TE instructions as v4T instruction sequences instead (or re-implement entire sections of assembly with hand-optimized v4T instructions).
* 20081021 [[User:Cfriedt]] Android -> FreeRunner updates on my [http://perpetual-notion.blogspot.com/search/label/android blog]
* 20081021 Google released the majority [http://source.android.com/download source code] for the phone under Apache free and open-source [http://source.android.com/license license], with portions covered by other existing licenses, such as the Linux kernel under GPLv2.
* 200810?? [http://www.koolu.com Koolu.com] has announced that they will be '''selling the OpenMoko Freerunner with Android pre-installed''' beginning in November 2008, as well as offering '''free downloads of the Freerunner port of Android''' to existing Freerunner owners. Well-known open-source advocate [http://koolu.com/The-Koolu-Team/maddog.html Jon "maddog" Hall] is CTO and Ambassador for Koolu.

= Introduction =
This page is dedicated to porting the [http://www.android.com Android OS] to the [[Neo 1973]] and [[Neo FreeRunner]] handsets. Since the Android OS was [http://source.android.com/posts/opensource publically released] on 20081021, [http://benno.id.au/blog/2007/11/21/android-neo1973 work] [http://perpetual-notion.blogspot.com/search/label/android is] [http://groups.google.com/group/android-porting currently underway] to port Android to the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

== Goals ==
# Systematically introduce patches for ARMv4T in the Android codebase
# Provide Neo1973 and Neo FreeRunner hardware-dependent patches in the Android codebase, leveraging the work already done by the Openmoko developers, without forcing Android-specific changes upstream
# Provide a useable Android filesystem and kernel on the [[Distributions]] page that conform to current Openmoko installation routines

== Early Attempts ==
As [http://benno.id.au Ben Leslie] had pointed out on his [http://benno.id.au/blog/2007/11/21/android-neo1973 blog] far before the source code was released, [http://www.android.com Android] was originally designed to work with the ARMv5TE [http://en.wikipedia.org/wiki/Instruction_set_architecture instruction set architecture] (ISA), which allows for [http://en.wikipedia.org/wiki/ARM_architecture#DSP_Enhancement_Instructions DSP enhanced instructions]. Contrary to the ARMv5TE ISA, the Neo1973 and FreeRunner handsets both feature an arm920t core, which comply to the ARMv4T ISA.

Before the source code was released, kernel trap handlers were implemented to 'emulate' the ARMv5TE ISA. Although the results worked in many cases, trapping is costly and performance suffered as a result. Moreover, without explicitly knowing which conditions were set by various instructions, such as Thumb Mode execution, the result became nondeterministic.

== Current State ==

With the release of the Android [http://source.android.com source code], the Open Source community is no longer limited to dealing with a binary-only product. The Open Handset Alliance (OHA) has let their source code become their product for everyone enrich and benefit from.

Currently, porting efforts are underway in many circles. Patches should be submitted via the [http://source.android.com/submit-patches official Android channels].

[http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.com http://git.koolu.com]. See the [[#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw [[User:Bricode]]

[[User:Seanmcneil3|Sean McNeil]] said that he was able to get Android running (including telephony) in his Freerunner [http://3v1n0.tuxfamily.org/tumblelog/post/368 source].

Ben Leslie mentioned on the android-porting list that he was able to get the 'Android' logo to appear on his Neo 1973.

=== Building the Koolu Android Source ===

# Configure your machine with the prerequisites documented in the [http://source.android.com/download#TOC-Setting-up-your-machine Setting up your machine] section of Google's build instructions.
# Install <tt>repo</tt> and download the source, as documented at http://trac.koolu.org/, '''but before running the <tt>make</tt> command in step 7, do the following:'''
# Install the toolchain provided by Koolu at http://trac.koolu.org/attachment/wiki/Toolchain/android-toolchain_20081019-koolu1_i386.deb.
# Create a ''<tt>buildspec.mk</tt>'' file at the top level of your Android source tree, and add the following line to it: <pre>TARGET_TOOLS_PREFIX := /opt/android-toolchain/bin/armv4t-android-eabi-
TARGET_PRODUCT := freerunner</pre> as documented at http://trac.koolu.org/wiki/Toolchain.
# Now you can start the build with the following command: <pre>$ make </pre>
# After the build finishes you can put together a root file system by editing and running Sean McNeil's scripts, which are attached to [http://lists.openmoko.org/pipermail/community/2008-December/036982.html this message]. The first script (cp_android_OS) is used to copy the newly built files into a staging area. The second one (mkjffs2) makes a jffs2 image from the staging area. Be sure to edit the paths in the two files to match your environment.
# The output of the second script is a file, <tt>androidfs.jffs2</tt>, which may be flashed to your Freerunner.

==== Building an jffs2 image ====
You can use this script:
<pre>
#!/bin/sh

currentdir=`pwd`

ANDROID_OUT=out
ANDROID_DEVICE=freerunner
EXPORT_ROOT=$currentdir/build_jffs2_tmp

Usage()
{
echo "Usage: $0 release|debug jffs2filename"
}

BuildImage()
{

if [ -d $1 ]
then
echo "[INFO] Copying from... $1"

sudo rm -rf $EXPORT_ROOT
mkdir $EXPORT_ROOT
mkdir $EXPORT_ROOT/root

# Copy the image...
cd $1
tar cf - root | (cd $EXPORT_ROOT; sudo tar xf -)
tar cf - system | (cd $EXPORT_ROOT/root; sudo tar xf -)

# Change owner and permissions...
cd $EXPORT_ROOT
sudo chown -R root:root root
sudo chmod -R 777 root

cd $currentdir

# Make the JFFS2 file
mkfs.jffs2 --pad=0x700000 -o $2 -e 0x20000 -n -d$EXPORT_ROOT/root/
echo "[INFO] Image written to $2"

sudo rm -rf $EXPORT_ROOT
else
echo "$1 does not exist!"
fi
}

if [ $# != 2 ]
then
Usage
else

case $1 in
release)
BuildImage $ANDROID_OUT/target/product/$ANDROID_DEVICE $2
;;
debug)
BuildImage $ANDROID_OUT/debug/target/product/$ANDROID_DEVICE $2
;;
*)
Usage
esac
fi

</pre>

There is currently no documented way to build a Freerunner/Android kernel. [[User:Seanmcneil3|Sean McNeil]] has been releasing kernels at http://people.openmoko.org/sean_mcneil/. Most of the patches required to run Android have be incorporated into the <tt>andy-tracking</tt> kernel branch, which will eventually be the new stable kernel. Once all the patches are in the kernel, it should be possible to run Android with a stock kernel.

=== Windows Connectivity ===

It is possible to get Windows to at least recognize the Android "Ethernet Gadget" and charge the FreeRunner using the Android USB Windows driver (http://dl.google.com/android/android_usb_windows.zip) by modifying the android_usb.inf file in that package before attempting to install the driver. The following modifications are required:

Add the following to the [Google.NTx86] section of the android_usb.inf file:

<pre>
; Neo FreeRunner
%USB\VID_1457&PID_5117.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117
%USB\VID_1457&PID_5117&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117&MI_01
</pre>

and add the following to the to the [Strings] section of the android_usb.inf file:

<pre>
USB\VID_1457&PID_5117.DeviceDescRelease="Neo FreeRunner"
USB\VID_1457&PID_5117&MI_01.DeviceDescRelease="Neo FreeRunner Composite ADB Interface"
</pre>

The Windows version of adb does not appear to recognize the connected device yet but at least the FreeRunner charges and the device driver indicates that "This device is working properly."

= How to Help =

== Getting Started ==

You can start by following the instructions to download and build the Android source from scratch. Please see [http://source.android.com/download http://source.android.com/download] and follow the instructions for your architecture.

== Publicize Your Efforts ==

It's generally a good idea to make your efforts known via wiki systems, public mailing lists, forums, and publically open version control systems.

Always take credit for your work but please don't do it in the form of comments. Some code is already hard enough to read without comments polluting the text. The best thing to do is to create a patch and put a header with your information at the top. Collaboration systems such as git might already do this for you (??).

If you create something new and have the ability to designate the license for it, please consider license compatibility issues.

== Porting Strategy ==

* Analysis and leverage of the existing build system
** buid/core/combo/arm-linux.mk
*** -D__ARCH_ARM_4__ -D__ARCH_ARM_4T__
*** -march=armv4t -mcpu=arm920t
** fix various static references to 'armv5'
* Isolating ARMv5TE ISA dependent code
** e.g. grep -n -R -i "${armv5te_isa_pattern}" ~/android
* Abstracting
** ( C/C++ )
*** Use inlined functions / #ifdef statments to implement functions in a portable manner
*** For inlined assembler calls, it's acceptable for now to use generic C code instead, so long as later on we optimize it by hand.
** ( ASM )
*** Proprocessor statements based on ISA / architecture, e.g. #ifdef __ARCH_ARM_5__ ... #endif #ifdef __ARCH_ARM_4__ ... #endif
*** It's highly suggested that preprocessor statements should not be nested (i.e. make them mutually exclusive)
*** Some people have suggested that we should not do #ifdef's based on ARCH or ISA, but rather based on an AndroidConfig.h which would define macros like PLD(...) #ifdef HAVE_ARM_PLD pld #else ... #endif .

For each ARMv5TE instruction, one could potentially
* Implement the instruction using general registers instead of DSP calls (i.e. eabi / softfloat)
* If that is a) nondeterministic, or b) slow, then sections of code need to be analyzed and hand-optimized for the ARMv4T isa

== List of Unsupported Instructions ==

This is a list of opcodes, extracted from the Android source, that are unsupported for ARMv4T compliant processors (specifically the arm920t). The opcodes represent instructions available for ARMv5, ARMv5T, and ARMv5TE architectures, which are not present in the ARMv4T ISA. The list was obtained by exhaustively editing the recompiling the Android source code until it compiled without error.

Please keep in mind, that in some cases, translating these instructions into a sequence of ARMv4T instructions will be impossible and / or result in nondeterministic execution because of
* the requirement of additional context
* the tendencies of certain opcodes to change condition registers that may or may not be present in the arm920t core

=== Opcodes ===

{{scroll box|height=480px|text=
<TABLE BORDER="1">
<TR>
<TH>Opcode</TH>
<TH>Desription</TH>
<TH>[[http://www.arm.com/miscPDFs/14128.pdf PDF]] Page Number</TH>
<TH>C</TH>
<TH>ASM</TH>
</TR>
<TR>
<TH VALIGN="TOP">BLX(1)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>166</TD>
<TD>N/A (Unused in Android)</TD>
<TD>N/A (Unused in Android)</TD>
</TR>
<TR>
<TH VALIGN="TOP">BLX(2)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>168</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_BLX
... (inline asm) ...
#else
... (inline asm with equivalent blx code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_BLX
#define BLX(a) \
blx a
#else
#define BLX(a) \
mov pc,lr \
bx a
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">CLZ</TH>
<TD>Count Leading Zeros</TD>
<TD>175</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_CLZ
... (inline asm) ...
#else
... (inline asm with equivalent clz code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081029
<pre>
#ifdef HAVE_CLZ
#define CLZ(Rd,Rm) \
clz Rd,Rm
#else
#define CLZ(Rd,Rm) \
...
#endif
...
CLZ(Rd,Rm)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">LDRD</TH>
<TD>Load Registers Doubleword</TD>
<TD>200</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_LDRD
... (inline asm) ...
#else
... (inline asm with ldrd substituted) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_LDRD
#define LDRD(a,b) \
ldrd a,b
#else
#define LDRD(a,b) \
...
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">PLD</TH>
<TD>Preload Data</TD>
<TD>240</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_PLD
... (inline asm) ...
#else
... (inline asm with pld removed) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove or substitute with a macro reference such as
<pre>
#ifdef HAVE_PLD
#define PLD(a,b) \
pld a,b
#else
#define PLD(a,b)
#endif
...
PLD(r0,#0)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLA<x><y></TH>
<TD>Signed Multiply-Accumulate</TD>
<TD>291</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAL<x><y></TH>
<TD>Signed Multiply Accumulate Long</TD>
<TD>298</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAW<y></TH>
<TD>Signed Multiply-Accumulate Word</TD>
<TD>302</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMUL<x><y></TH>
<TD>Signed Multiply</TD>
<TD>316</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULW<y></TH>
<TD>Signed Multiply Word</TD>
<TD>320</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QADD</TH>
<TD>Saturating Add</TD>
<TD>242</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDADD</TH>
<TD>Saturating Double and Add</TD>
<TD>249</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDSUB</TH>
<TD>Saturating Double and Subtract</TD>
<TD>251</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QSUB</TH>
<TD>Saturating Subtract</TD>
<TD>253</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">STRD</TH>
<TD>Store Registers Doubleword</TD>
<TD>349</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_STRD
... (inline asm) ...
#else
... (inline asm without strd) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_STRD
#define STRD(a,b) \
strd a,b
#else
#define STRD(a,b) \
...
#endif
</pre>

</TD>
</TR>
</TABLE>
}}

=== Scanning for Files That Use the ARMv5TE ISA ===

Using the above list of opcodes, one can scan the Android source code for ARMv4T-incompatible instruction sequences.

'''Code:'''
{{scroll box|height=240px|text=
<pre>
#!/bin/sh

# $1 is the android directory

if [ $# -ne 1 ]; then
exit -1
fi

cd "${1}"

opcodes="blx clz ldrd pld smlabb smlabt smlatt
smlal smlawb smlawt smulbb smulbt smultt smulwb
smulwt qadd qdadd qdsub qsub strd"

for op in ${opcodes}; do

echo "* ${op} ====================================="

if [ ! -e .files.${op} ]; then

files="$(grep -R -i "${op} " * 2>/dev/null)"
files="$(echo $files | grep -v "^Binary file" | sed -e 's/:.*//')"
files="$(echo $files| grep -v "CREDIT\|README\|^$kernel/\|.git/$\|$\.txt$$" | sort -u)"

echo "${files}" > .files.${op}

else
files="$(cat .files.${op})"
fi

for fil in ${files}; do
lines="$(grep -n -i "${op} " ${fil} | sed -e 's/:.*//g' )"
lines="$(echo $lines | sed -e 's/ /,/g')"
echo "** ${fil}: lines {${lines}}"
done
done
</pre>
}}

=== Source Files in Android that Use the ARMv5TE ISA ===

The list of files below may or may not be complete. There might also be some assembly code that is generated with a python script (verification?).

{{scroll box|height=150px|text=
* blx =====================================
** bionic/libc/tools/gensyscalls.py: lines {168,186}
** bootloader/legacy/nandwrite/init.S: lines {77}
** bootloader/legacy/usbloader/init.S: lines {95}
** dalvik/vm/arch/arm/CallEABI.S: lines {239}
** dalvik/vm/arch/arm/CallOldABI.S: lines {145}
** development/emulator/qtools/thumbdis.cpp: lines {187,265}
** external/qemu/target-arm/translate.c: lines {1151,1971,2444}
** external/qemu/trace.c: lines {774,1353,1358}
** system/core/libpixelflinger/codeflinger/disassem.c: lines {416}
* clz =====================================
** development/emulator/qtools/armdis.cpp: lines {654}
** external/opencore/codecs_v2/audio/aac/dec/src/pv_normalize.h: lines {67,84}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/norm_l.h: lines {137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/normalize_amr_wb.h: lines {78,95}
** external/opencore/codecs_v2/audio/mp3/dec/src/pvmp3_normalize.h: lines {67,84}
** external/opencore/codecs_v2/video/avc_h264/dec/src/vlc.cpp: lines {23}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/vlc_encode_inline.h: lines {125,162,168,204,218}
** external/qemu/target-arm/translate.c: lines {1247}
** external/skia/libcorecg/Sk64.cpp: lines {340,341,343}
** external/skia/libcorecg/SkMatrix.cpp: lines {500,501}
** external/skia/libsgl/effects/SkColorMatrixFilter.cpp: lines {135}
** external/skia/libsgl/sgl/SkBitmap.cpp: lines {945,946,947}
** external/skia/libsgl/sgl/SkBitmapShader.cpp: lines {32,33,34}
** external/skia/libsgl/sgl/SkGraphics.cpp: lines {429,437}
* ldrd =====================================
** dalvik/vm/mterp/armv5/OP_AGET_WIDE.S: lines {28}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE.S: lines {37}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE_QUICK.S: lines {10}
** dalvik/vm/mterp/armv5/OP_SGET_WIDE.S: lines {17}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2653,7464,8318,8390}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {40,41,42,43}
* pld =====================================
** bionic/libc/arch-arm/bionic/memcmp.S: lines {37,44,45,56,57,107,108,195,196}
** bionic/libc/arch-arm/bionic/memcmp16.S: lines {37,44,45,67,68,116,117,198,199}
** bionic/libc/arch-arm/bionic/memcpy.S: lines {55,56,57,145,266,293,320}
** bionic/libc/arch-arm/bionic/strlen.c: lines {59,65}
** bionic/libc/kernel/arch-arm/asm/arch/irqs.h: lines {162}
** external/elfutils/src/Makefile: lines {243}
** external/elfutils/src/Makefile.am: lines {32}
** external/elfutils/src/Makefile.in: lines {243}
** external/jpeg/jidctfst.S: lines {69,235,247}
** external/qemu/target-arm/translate.c: lines {1149}
** system/core/libpixelflinger/codeflinger/ARMAssembler.cpp: lines {368}
** system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp: lines {104,108,117}
** system/core/libpixelflinger/t32cb16blend.S: lines {111,112,134,143}
* smlabb =====================================
** external/jpeg/jidctfst.S: lines {110,115,155,156}
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {584,589}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {147,166}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {120,129}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {514,533}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {418,429}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {202}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {250}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {119,155,167,278,326,341}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {178,225,437,517}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {405,436}
* smlabt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {184}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {138}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {131,143,294,310}
* smlatt =====================================
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {585,590}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {157}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {441}
* smlal =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4.h: lines {179,223,236,257,267}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4_gcc.h: lines {264,341}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {178,188,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9.s: lines {84,90,96,101,109,114,116,118,121,132,138,150,163,165,167,174,176,178}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9_gcc.s: lines {73,79,86,90,98,103,105,107,110,121,127,139,152,154,156,163,165,167}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.asm: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.s: lines {145,164,180,190,194,201,209,219,227,233,239,243,246}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18_gcc.s: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.asm: lines {62,63,66,72,76,77,81,82,85,90,94,97,99,100,103,108,113,114,118,119,122,129,136,137,176,179,183,187,190,193}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.s: lines {67,68,71,77,81,82,86,87,90,95,99,102,104,105,108,113,118,119,123,124,127,134,141,142,181,184,188,192,195,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window_gcc.s: lines {65,66,69,75,79,80,84,85,88,93,97,100,102,103,106,111,116,117,121,122,125,132,139,140,179,182,186,190,193,196}
** external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm.h: lines {148}
** external/qemu/trace.c: lines {813}
** frameworks/base/opengl/libagl/iterators.S: lines {66,67}
** frameworks/base/opengl/libagl/matrix.h: lines {67,68,96,126,127,282,283,314,315,316}
* smlawb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {203,259}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {166,416}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {93,109}
** frameworks/base/opengl/libagl/matrix.h: lines {163,203}
* smlawt =====================================
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {114}
** frameworks/base/opengl/libagl/matrix.h: lines {162,202,243,244}
* smulbb =====================================
** external/jpeg/jidctfst.S: lines {109,114,151,153}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {79}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {71,81}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {207,251,297,348,361,375,427,440,487}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {199,234,274,314,316,326,367,369,404}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {121,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {123,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {122,140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {132,134,138,164,177,191}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {127,129,150,163}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mult.h: lines {121,141}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {115,139,151,163,189,190,212}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {112,113,164,183,201,218,265}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {250,457,531}
** external/skia/include/corecg/SkMath.h: lines {170}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {420,462}
** system/core/libpixelflinger/t32cb16blend.S: lines {39,66,74,82}
* smulbt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {115}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {109}
** system/core/libpixelflinger/codeflinger/texturing.cpp: lines {1091}
** system/core/libpixelflinger/t32cb16blend.S: lines {47,55}
* smultt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {131}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {100}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {467}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {73}
* smulwb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {221}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {373}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {222}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {283}
** external/opencore/codecs_v2/audio/sbc/enc/src/sbcenc_filter.h: lines {33}
** frameworks/base/opengl/libagl/matrix.h: lines {161,201,242}
* smulwt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {202,240}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {385,415}
* qadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {64}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {60}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {130,256}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {128,235}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_add.h: lines {122,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {123,145}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {71,102,152,176,192}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {91,115,148,202,234}
** external/openssl/crypto/bn/bn_prime.c: lines {454,455}
* qdadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/calc_sbr_synfilterbank.cpp: lines {116,162}
** external/opencore/codecs_v2/audio/aac/dec/src/trans4m_freq_2_time_fxp.cpp: lines {472,494}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {212,356,370,385,435,449}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {200,315,321,331,368,371}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {122,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {133,136,140,172,186,201}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {128,131,158,172}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {116}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {184}
* qdsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {302}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {275}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {124,147}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {165}
* qsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {167}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {162}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_sub.h: lines {121,138}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {88,127}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {70,133}
* strd =====================================
** dalvik/vm/mterp/armv5/OP_APUT_WIDE.S: lines {31}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE.S: lines {39}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE_QUICK.S: lines {14}
** dalvik/vm/mterp/armv5/OP_SPUT_WIDE.S: lines {21}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2834,7530,8331,8542}
** dalvik/vm/oo/Object.h: lines {589}
** external/opencore/fileformats/avi/parser/include/pv_avifile_streamlist.h: lines {179}
** external/opencore/fileformats/avi/parser/src/pv_avifile_streamlist.cpp: lines {153}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {47,52,56,60}
}}

=== Discussion ===
=== Notes ===
The file
<pre>
system/core/libpixelflinger/codeflinger/ARMAssembler.cpp
</pre>

will need special attention. It's responsible for dynamic generation of DSP code.

== Suggestions ==
* [[User:Cfriedt]] 20081024 I'm not sure how feasible this is, given that the [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#SMedia_3362_Documentation_.26_OpenGL_ES_Drivers SMedia 3362 is heavily NDA'd]. However, since the arm920t lacks a floating-point unit / DSP core, is it possible to use the SMedia chip for general-purpose math? This would help in the Android platform, at least, for things like audio and video codecs. Aside from an OpenGL ES driver, OpenMoko documentation for the SMedia would be highly appreciated.

= Important Links =
(Please Update Me)

== Documentation ==
* [http://source.android.com/documentation Android Documentation]
* [http://www.arm.com/documentation/ ARM Documentation], (keywords: armv4t, armv5t, armv5te, arm920t, arm926ej-s)
* [http://www.arm.com/miscPDFs/9658.pdf ARM Assembly Language Programming]
* [http://www.cse.unsw.edu.au/~cs3221/labs/assembler-intro.pdf An Introduction to the GNU Assembler]
* [http://www.heyrick.co.uk/assembler/apcsintro.html ARM Procedure Call Standard], [http://en.wikipedia.org/wiki/Calling_convention#ARM ARM Calling Conventions]

== Instruction Set References ==
* [http://www.arm.com/miscPDFs/14128.pdf ARM Architecture Reference Manual], The definitive ISA documentation
* [http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf ARM Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001l/QRC0001_UAL.pdf ARM and Thumb -2 Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0025b/DVI0025.pdf ARMv4T] (See section 1.4.13)
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0014a/DVI0014A_ARM10T_PO.pdf ARMv5T] (See section 4.16)
* [http://www.arm.com/pdfs/ARM-DSP.pdf ARM DSP Enhanced Instruction Set]
* [http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042c/IHI0042C_aapcs.pdf Procedure Call Standard for the ARM Architecture]

== Hardware Reference ==

* [[Neo1973 Hardware]]
* [[Neo FreeRunner GTA02 Hardware]]

== Communities ==
* [http://source.android.com/discuss Android Public Mailing Lists]
** Specifically, [http://groups.google.com/group/android-porting android-porting]
* [http://lists.openmoko.org/mailman/listinfo OpenMoko Mailing Lists]
** Specifically, [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel openmoko-kernel]
* [http://forum.koolu.org/viewforum.php?f=10 Android on FreeRunner] at KoolU.com
* [[Openmoko Local Groups]]
* [[Openmoko:Community_Portal]]

= See also =

* [[Debug_Board]]

= External Links =
== Youtube video /Android on FreeRunner ==

[http://tw.youtube.com/watch?v=m4NbsLmF9j0 Video 1]

[http://tw.youtube.com/watch?v=r6Op-7tNTiw Video 2]

== Headline text ==

[[Category:Distributions]]

Android

2008-12-05T18:16:34Z

Treviño: /* Building the Koolu Android Source */

{{Languages|Android}}
{{Distributions|Android}}

= Updates =
* 20081202 [http://www.koolu.com Koolu.com] has released the source code for the FreeRunner port of Android in their git repositories at [http://git.koolu.org/ Koolu GIT] ([http://koolu.com/Press-Release/ Press Release])
* 20081120 [http://www.koolu.com Koolu.com] has pushed back selling the OpenMoko Freerunner with Android pre-installed , as well as offering free downloads of the Freerunner port of Android to existing Freerunner owners. Untill December 2008
* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']
* 20081029 [[User:Cfriedt]] [http://benno.id.au Benno] has modified Android's build system so that it will output a JFFS2 image instead of YAFFS . Unlike JFFS2, which [http://wiki.openmoko.org/wiki/Userspace_root_image can be mounted read-only from an image], mounting a YAFFS image is not possible unless it's already been written to flash (it complains about the block device being of type '1' and not 'NAND'). JFFS2 also has the benefit that it's a standard OpenMoko image format (See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]])
* 20081023 [[User:Bricode]] To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw
* 20081022 [[User:Cfriedt]] I was able to 'trivially' compile all of the Android source code without error for the ARMv4T architecture by removing v5TE instructions. Although it will definitely not run anything predictably, at least now that I know the build system will work with a few simple substitutions in build/core/combo/arm-linux.mk. At this point I am able to go ahead and re-implement v5TE instructions as v4T instruction sequences instead (or re-implement entire sections of assembly with hand-optimized v4T instructions).
* 20081021 [[User:Cfriedt]] Android -> FreeRunner updates on my [http://perpetual-notion.blogspot.com/search/label/android blog]
* 20081021 Google released the majority [http://source.android.com/download source code] for the phone under Apache free and open-source [http://source.android.com/license license], with portions covered by other existing licenses, such as the Linux kernel under GPLv2.
* 200810?? [http://www.koolu.com Koolu.com] has announced that they will be '''selling the OpenMoko Freerunner with Android pre-installed''' beginning in November 2008, as well as offering '''free downloads of the Freerunner port of Android''' to existing Freerunner owners. Well-known open-source advocate [http://koolu.com/The-Koolu-Team/maddog.html Jon "maddog" Hall] is CTO and Ambassador for Koolu.

= Introduction =
This page is dedicated to porting the [http://www.android.com Android OS] to the [[Neo 1973]] and [[Neo FreeRunner]] handsets. Since the Android OS was [http://source.android.com/posts/opensource publically released] on 20081021, [http://benno.id.au/blog/2007/11/21/android-neo1973 work] [http://perpetual-notion.blogspot.com/search/label/android is] [http://groups.google.com/group/android-porting currently underway] to port Android to the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

== Goals ==
# Systematically introduce patches for ARMv4T in the Android codebase
# Provide Neo1973 and Neo FreeRunner hardware-dependent patches in the Android codebase, leveraging the work already done by the Openmoko developers, without forcing Android-specific changes upstream
# Provide a useable Android filesystem and kernel on the [[Distributions]] page that conform to current Openmoko installation routines

== Early Attempts ==
As [http://benno.id.au Ben Leslie] had pointed out on his [http://benno.id.au/blog/2007/11/21/android-neo1973 blog] far before the source code was released, [http://www.android.com Android] was originally designed to work with the ARMv5TE [http://en.wikipedia.org/wiki/Instruction_set_architecture instruction set architecture] (ISA), which allows for [http://en.wikipedia.org/wiki/ARM_architecture#DSP_Enhancement_Instructions DSP enhanced instructions]. Contrary to the ARMv5TE ISA, the Neo1973 and FreeRunner handsets both feature an arm920t core, which comply to the ARMv4T ISA.

Before the source code was released, kernel trap handlers were implemented to 'emulate' the ARMv5TE ISA. Although the results worked in many cases, trapping is costly and performance suffered as a result. Moreover, without explicitly knowing which conditions were set by various instructions, such as Thumb Mode execution, the result became nondeterministic.

== Current State ==

With the release of the Android [http://source.android.com source code], the Open Source community is no longer limited to dealing with a binary-only product. The Open Handset Alliance (OHA) has let their source code become their product for everyone enrich and benefit from.

Currently, porting efforts are underway in many circles. Patches should be submitted via the [http://source.android.com/submit-patches official Android channels].

[http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.com http://git.koolu.com]. See the [[#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw [[User:Bricode]]

[[User:Seanmcneil3|Sean McNeil]] said that he was able to get Android running (including telephony) in his Freerunner [http://3v1n0.tuxfamily.org/tumblelog/post/368 source].

Ben Leslie mentioned on the android-porting list that he was able to get the 'Android' logo to appear on his Neo 1973.

=== Building the Koolu Android Source ===

# Configure your machine with the prerequisites documented in the [http://source.android.com/download#TOC-Setting-up-your-machine Setting up your machine] section of Google's build instructions.
# Install <tt>repo</tt> and download the source, as documented at http://trac.koolu.org/, '''but before running the <tt>make</tt> command in step 7, do the following:'''
# Install the toolchain provided by Koolu at http://trac.koolu.org/attachment/wiki/Toolchain/android-toolchain_20081019-koolu1_i386.deb.
# Create a <tt>buildspec.mk</tt> file at the top level of your Android source tree, and add the following line to it: <pre>TARGET_TOOLS_PREFIX := /opt/android-toolchain/bin/armv4t-android-eabi-</pre> as documented at http://trac.koolu.org/wiki/Toolchain.
# Now you can start the build with the following command: <pre>$ make TARGET_PRODUCT=freerunner</pre>
# After the build finishes you can put together a root file system by editing and running Sean McNeil's scripts, which are attached to [http://lists.openmoko.org/pipermail/community/2008-December/036982.html this message]. The first script (cp_android_OS) is used to copy the newly built files into a staging area. The second one (mkjffs2) makes a jffs2 image from the staging area. Be sure to edit the paths in the two files to match your environment.
# The output of the second script is a file, <tt>androidfs.jffs2</tt>, which may be flashed to your Freerunner.

==== Building an jffs2 image ====
You can use this script:
<pre>
#!/bin/sh

currentdir=`pwd`

ANDROID_OUT=out
ANDROID_DEVICE=freerunner
EXPORT_ROOT=$currentdir/build_jffs2_tmp

Usage()
{
echo "Usage: $0 release|debug jffs2filename"
}

BuildImage()
{

if [ -d $1 ]
then
echo "[INFO] Copying from... $1"

sudo rm -rf $EXPORT_ROOT
mkdir $EXPORT_ROOT
mkdir $EXPORT_ROOT/root

# Copy the image...
cd $1
tar cf - root | (cd $EXPORT_ROOT; sudo tar xf -)
tar cf - system | (cd $EXPORT_ROOT/root; sudo tar xf -)

# Change owner and permissions...
cd $EXPORT_ROOT
sudo chown -R root:root root
sudo chmod -R 777 root

cd $currentdir

# Make the JFFS2 file
mkfs.jffs2 --pad=0x700000 -o $2 -e 0x20000 -n -d$EXPORT_ROOT/root/
echo "[INFO] Image written to $2"

sudo rm -rf $EXPORT_ROOT
else
echo "$1 does not exist!"
fi
}

if [ $# != 2 ]
then
Usage
else

case $1 in
release)
BuildImage $ANDROID_OUT/target/product/$ANDROID_DEVICE $2
;;
debug)
BuildImage $ANDROID_OUT/debug/target/product/$ANDROID_DEVICE $2
;;
*)
Usage
esac
fi

</pre>

There is currently no documented way to build a Freerunner/Android kernel. [[User:Seanmcneil3|Sean McNeil]] has been releasing kernels at http://people.openmoko.org/sean_mcneil/. Most of the patches required to run Android have be incorporated into the <tt>andy-tracking</tt> kernel branch, which will eventually be the new stable kernel. Once all the patches are in the kernel, it should be possible to run Android with a stock kernel.

=== Windows Connectivity ===

It is possible to get Windows to at least recognize the Android "Ethernet Gadget" and charge the FreeRunner using the Android USB Windows driver (http://dl.google.com/android/android_usb_windows.zip) by modifying the android_usb.inf file in that package before attempting to install the driver. The following modifications are required:

Add the following to the [Google.NTx86] section of the android_usb.inf file:

<pre>
; Neo FreeRunner
%USB\VID_1457&PID_5117.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117
%USB\VID_1457&PID_5117&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_1457&PID_5117&MI_01
</pre>

and add the following to the to the [Strings] section of the android_usb.inf file:

<pre>
USB\VID_1457&PID_5117.DeviceDescRelease="Neo FreeRunner"
USB\VID_1457&PID_5117&MI_01.DeviceDescRelease="Neo FreeRunner Composite ADB Interface"
</pre>

The Windows version of adb does not appear to recognize the connected device yet but at least the FreeRunner charges and the device driver indicates that "This device is working properly."

= How to Help =

== Getting Started ==

You can start by following the instructions to download and build the Android source from scratch. Please see [http://source.android.com/download http://source.android.com/download] and follow the instructions for your architecture.

== Publicize Your Efforts ==

It's generally a good idea to make your efforts known via wiki systems, public mailing lists, forums, and publically open version control systems.

Always take credit for your work but please don't do it in the form of comments. Some code is already hard enough to read without comments polluting the text. The best thing to do is to create a patch and put a header with your information at the top. Collaboration systems such as git might already do this for you (??).

If you create something new and have the ability to designate the license for it, please consider license compatibility issues.

== Porting Strategy ==

* Analysis and leverage of the existing build system
** buid/core/combo/arm-linux.mk
*** -D__ARCH_ARM_4__ -D__ARCH_ARM_4T__
*** -march=armv4t -mcpu=arm920t
** fix various static references to 'armv5'
* Isolating ARMv5TE ISA dependent code
** e.g. grep -n -R -i "${armv5te_isa_pattern}" ~/android
* Abstracting
** ( C/C++ )
*** Use inlined functions / #ifdef statments to implement functions in a portable manner
*** For inlined assembler calls, it's acceptable for now to use generic C code instead, so long as later on we optimize it by hand.
** ( ASM )
*** Proprocessor statements based on ISA / architecture, e.g. #ifdef __ARCH_ARM_5__ ... #endif #ifdef __ARCH_ARM_4__ ... #endif
*** It's highly suggested that preprocessor statements should not be nested (i.e. make them mutually exclusive)
*** Some people have suggested that we should not do #ifdef's based on ARCH or ISA, but rather based on an AndroidConfig.h which would define macros like PLD(...) #ifdef HAVE_ARM_PLD pld #else ... #endif .

For each ARMv5TE instruction, one could potentially
* Implement the instruction using general registers instead of DSP calls (i.e. eabi / softfloat)
* If that is a) nondeterministic, or b) slow, then sections of code need to be analyzed and hand-optimized for the ARMv4T isa

== List of Unsupported Instructions ==

This is a list of opcodes, extracted from the Android source, that are unsupported for ARMv4T compliant processors (specifically the arm920t). The opcodes represent instructions available for ARMv5, ARMv5T, and ARMv5TE architectures, which are not present in the ARMv4T ISA. The list was obtained by exhaustively editing the recompiling the Android source code until it compiled without error.

Please keep in mind, that in some cases, translating these instructions into a sequence of ARMv4T instructions will be impossible and / or result in nondeterministic execution because of
* the requirement of additional context
* the tendencies of certain opcodes to change condition registers that may or may not be present in the arm920t core

=== Opcodes ===

{{scroll box|height=480px|text=
<TABLE BORDER="1">
<TR>
<TH>Opcode</TH>
<TH>Desription</TH>
<TH>[[http://www.arm.com/miscPDFs/14128.pdf PDF]] Page Number</TH>
<TH>C</TH>
<TH>ASM</TH>
</TR>
<TR>
<TH VALIGN="TOP">BLX(1)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>166</TD>
<TD>N/A (Unused in Android)</TD>
<TD>N/A (Unused in Android)</TD>
</TR>
<TR>
<TH VALIGN="TOP">BLX(2)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>168</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_BLX
... (inline asm) ...
#else
... (inline asm with equivalent blx code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_BLX
#define BLX(a) \
blx a
#else
#define BLX(a) \
mov pc,lr \
bx a
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">CLZ</TH>
<TD>Count Leading Zeros</TD>
<TD>175</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_CLZ
... (inline asm) ...
#else
... (inline asm with equivalent clz code, as shown to the right) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081029
<pre>
#ifdef HAVE_CLZ
#define CLZ(Rd,Rm) \
clz Rd,Rm
#else
#define CLZ(Rd,Rm) \
...
#endif
...
CLZ(Rd,Rm)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">LDRD</TH>
<TD>Load Registers Doubleword</TD>
<TD>200</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_LDRD
... (inline asm) ...
#else
... (inline asm with ldrd substituted) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_LDRD
#define LDRD(a,b) \
ldrd a,b
#else
#define LDRD(a,b) \
...
#endif
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">PLD</TH>
<TD>Preload Data</TD>
<TD>240</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove from inline assembly with something like
<pre>
#ifdef HAVE_PLD
... (inline asm) ...
#else
... (inline asm with pld removed) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Remove or substitute with a macro reference such as
<pre>
#ifdef HAVE_PLD
#define PLD(a,b) \
pld a,b
#else
#define PLD(a,b)
#endif
...
PLD(r0,#0)
</pre>
</TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLA<x><y></TH>
<TD>Signed Multiply-Accumulate</TD>
<TD>291</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAL<x><y></TH>
<TD>Signed Multiply Accumulate Long</TD>
<TD>298</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAW<y></TH>
<TD>Signed Multiply-Accumulate Word</TD>
<TD>302</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMUL<x><y></TH>
<TD>Signed Multiply</TD>
<TD>316</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULW<y></TH>
<TD>Signed Multiply Word</TD>
<TD>320</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QADD</TH>
<TD>Saturating Add</TD>
<TD>242</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDADD</TH>
<TD>Saturating Double and Add</TD>
<TD>249</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDSUB</TH>
<TD>Saturating Double and Subtract</TD>
<TD>251</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QSUB</TH>
<TD>Saturating Subtract</TD>
<TD>253</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">STRD</TH>
<TD>Store Registers Doubleword</TD>
<TD>349</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute different inline assembly code with something like
<pre>
#ifdef HAVE_STRD
... (inline asm) ...
#else
... (inline asm without strd) ...
#endif
</pre>
</TD>
<TD>
[[User:Cfriedt]] 20081028
Substitute with a macro reference such as
<pre>
#ifdef HAVE_STRD
#define STRD(a,b) \
strd a,b
#else
#define STRD(a,b) \
...
#endif
</pre>

</TD>
</TR>
</TABLE>
}}

=== Scanning for Files That Use the ARMv5TE ISA ===

Using the above list of opcodes, one can scan the Android source code for ARMv4T-incompatible instruction sequences.

'''Code:'''
{{scroll box|height=240px|text=
<pre>
#!/bin/sh

# $1 is the android directory

if [ $# -ne 1 ]; then
exit -1
fi

cd "${1}"

opcodes="blx clz ldrd pld smlabb smlabt smlatt
smlal smlawb smlawt smulbb smulbt smultt smulwb
smulwt qadd qdadd qdsub qsub strd"

for op in ${opcodes}; do

echo "* ${op} ====================================="

if [ ! -e .files.${op} ]; then

files="$(grep -R -i "${op} " * 2>/dev/null)"
files="$(echo $files | grep -v "^Binary file" | sed -e 's/:.*//')"
files="$(echo $files| grep -v "CREDIT\|README\|^$kernel/\|.git/$\|$\.txt$$" | sort -u)"

echo "${files}" > .files.${op}

else
files="$(cat .files.${op})"
fi

for fil in ${files}; do
lines="$(grep -n -i "${op} " ${fil} | sed -e 's/:.*//g' )"
lines="$(echo $lines | sed -e 's/ /,/g')"
echo "** ${fil}: lines {${lines}}"
done
done
</pre>
}}

=== Source Files in Android that Use the ARMv5TE ISA ===

The list of files below may or may not be complete. There might also be some assembly code that is generated with a python script (verification?).

{{scroll box|height=150px|text=
* blx =====================================
** bionic/libc/tools/gensyscalls.py: lines {168,186}
** bootloader/legacy/nandwrite/init.S: lines {77}
** bootloader/legacy/usbloader/init.S: lines {95}
** dalvik/vm/arch/arm/CallEABI.S: lines {239}
** dalvik/vm/arch/arm/CallOldABI.S: lines {145}
** development/emulator/qtools/thumbdis.cpp: lines {187,265}
** external/qemu/target-arm/translate.c: lines {1151,1971,2444}
** external/qemu/trace.c: lines {774,1353,1358}
** system/core/libpixelflinger/codeflinger/disassem.c: lines {416}
* clz =====================================
** development/emulator/qtools/armdis.cpp: lines {654}
** external/opencore/codecs_v2/audio/aac/dec/src/pv_normalize.h: lines {67,84}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/norm_l.h: lines {137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/normalize_amr_wb.h: lines {78,95}
** external/opencore/codecs_v2/audio/mp3/dec/src/pvmp3_normalize.h: lines {67,84}
** external/opencore/codecs_v2/video/avc_h264/dec/src/vlc.cpp: lines {23}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/vlc_encode_inline.h: lines {125,162,168,204,218}
** external/qemu/target-arm/translate.c: lines {1247}
** external/skia/libcorecg/Sk64.cpp: lines {340,341,343}
** external/skia/libcorecg/SkMatrix.cpp: lines {500,501}
** external/skia/libsgl/effects/SkColorMatrixFilter.cpp: lines {135}
** external/skia/libsgl/sgl/SkBitmap.cpp: lines {945,946,947}
** external/skia/libsgl/sgl/SkBitmapShader.cpp: lines {32,33,34}
** external/skia/libsgl/sgl/SkGraphics.cpp: lines {429,437}
* ldrd =====================================
** dalvik/vm/mterp/armv5/OP_AGET_WIDE.S: lines {28}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE.S: lines {37}
** dalvik/vm/mterp/armv5/OP_IGET_WIDE_QUICK.S: lines {10}
** dalvik/vm/mterp/armv5/OP_SGET_WIDE.S: lines {17}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2653,7464,8318,8390}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {40,41,42,43}
* pld =====================================
** bionic/libc/arch-arm/bionic/memcmp.S: lines {37,44,45,56,57,107,108,195,196}
** bionic/libc/arch-arm/bionic/memcmp16.S: lines {37,44,45,67,68,116,117,198,199}
** bionic/libc/arch-arm/bionic/memcpy.S: lines {55,56,57,145,266,293,320}
** bionic/libc/arch-arm/bionic/strlen.c: lines {59,65}
** bionic/libc/kernel/arch-arm/asm/arch/irqs.h: lines {162}
** external/elfutils/src/Makefile: lines {243}
** external/elfutils/src/Makefile.am: lines {32}
** external/elfutils/src/Makefile.in: lines {243}
** external/jpeg/jidctfst.S: lines {69,235,247}
** external/qemu/target-arm/translate.c: lines {1149}
** system/core/libpixelflinger/codeflinger/ARMAssembler.cpp: lines {368}
** system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp: lines {104,108,117}
** system/core/libpixelflinger/t32cb16blend.S: lines {111,112,134,143}
* smlabb =====================================
** external/jpeg/jidctfst.S: lines {110,115,155,156}
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {584,589}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {147,166}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {120,129}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {514,533}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {418,429}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {202}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {250}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {119,155,167,278,326,341}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {178,225,437,517}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {405,436}
* smlabt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {184}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {138}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h: lines {131,143,294,310}
* smlatt =====================================
** external/neven/Embedded/common/src/b_BasicEm/Math.c: lines {585,590}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {157}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {441}
* smlal =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4.h: lines {179,223,236,257,267}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4_gcc.h: lines {264,341}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {178,188,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9.s: lines {84,90,96,101,109,114,116,118,121,132,138,150,163,165,167,174,176,178}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9_gcc.s: lines {73,79,86,90,98,103,105,107,110,121,127,139,152,154,156,163,165,167}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.asm: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.s: lines {145,164,180,190,194,201,209,219,227,233,239,243,246}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18_gcc.s: lines {143,162,178,188,192,199,207,217,225,231,237,241,244}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.asm: lines {62,63,66,72,76,77,81,82,85,90,94,97,99,100,103,108,113,114,118,119,122,129,136,137,176,179,183,187,190,193}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.s: lines {67,68,71,77,81,82,86,87,90,95,99,102,104,105,108,113,118,119,123,124,127,134,141,142,181,184,188,192,195,198}
** external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window_gcc.s: lines {65,66,69,75,79,80,84,85,88,93,97,100,102,103,106,111,116,117,121,122,125,132,139,140,179,182,186,190,193,196}
** external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm.h: lines {148}
** external/qemu/trace.c: lines {813}
** frameworks/base/opengl/libagl/iterators.S: lines {66,67}
** frameworks/base/opengl/libagl/matrix.h: lines {67,68,96,126,127,282,283,314,315,316}
* smlawb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {203,259}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {166,416}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {93,109}
** frameworks/base/opengl/libagl/matrix.h: lines {163,203}
* smlawt =====================================
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {114}
** frameworks/base/opengl/libagl/matrix.h: lines {162,202,243,244}
* smulbb =====================================
** external/jpeg/jidctfst.S: lines {109,114,151,153}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {79}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {71,81}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {207,251,297,348,361,375,427,440,487}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {199,234,274,314,316,326,367,369,404}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {121,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {123,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {122,140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {132,134,138,164,177,191}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {127,129,150,163}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mult.h: lines {121,141}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {115,139,151,163,189,190,212}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {112,113,164,183,201,218,265}
** external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h: lines {250,457,531}
** external/skia/include/corecg/SkMath.h: lines {170}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {420,462}
** system/core/libpixelflinger/t32cb16blend.S: lines {39,66,74,82}
* smulbt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {115}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {109}
** system/core/libpixelflinger/codeflinger/texturing.cpp: lines {1091}
** system/core/libpixelflinger/t32cb16blend.S: lines {47,55}
* smultt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {131}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {100}
** frameworks/base/libs/audioflinger/AudioMixer.cpp: lines {467}
** frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp: lines {73}
* smulwb =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {221}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {373}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {222}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {283}
** external/opencore/codecs_v2/audio/sbc/enc/src/sbcenc_filter.h: lines {33}
** frameworks/base/opengl/libagl/matrix.h: lines {161,201,242}
* smulwt =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {202,240}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {385,415}
* qadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h: lines {64}
** external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h: lines {60}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {130,256}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {128,235}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_add.h: lines {122,137}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h: lines {123,145}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {71,102,152,176,192}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {91,115,148,202,234}
** external/openssl/crypto/bn/bn_prime.c: lines {454,455}
* qdadd =====================================
** external/opencore/codecs_v2/audio/aac/dec/src/calc_sbr_synfilterbank.cpp: lines {116,162}
** external/opencore/codecs_v2/audio/aac/dec/src/trans4m_freq_2_time_fxp.cpp: lines {472,494}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {212,356,370,385,435,449}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {200,315,321,331,368,371}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h: lines {122,142}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h: lines {133,136,140,172,186,201}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h: lines {128,131,158,172}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {116}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {184}
* qdsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {302}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {275}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h: lines {124,147}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {140}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {165}
* qsub =====================================
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h: lines {167}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h: lines {162}
** external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_sub.h: lines {121,138}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h: lines {88,127}
** external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h: lines {70,133}
* strd =====================================
** dalvik/vm/mterp/armv5/OP_APUT_WIDE.S: lines {31}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE.S: lines {39}
** dalvik/vm/mterp/armv5/OP_IPUT_WIDE_QUICK.S: lines {14}
** dalvik/vm/mterp/armv5/OP_SPUT_WIDE.S: lines {21}
** dalvik/vm/mterp/out/InterpAsm-armv5.S: lines {2834,7530,8331,8542}
** dalvik/vm/oo/Object.h: lines {589}
** external/opencore/fileformats/avi/parser/include/pv_avifile_streamlist.h: lines {179}
** external/opencore/fileformats/avi/parser/src/pv_avifile_streamlist.cpp: lines {153}
** system/core/libpixelflinger/rotate90CW_4x4_16v6.S: lines {47,52,56,60}
}}

=== Discussion ===
=== Notes ===
The file
<pre>
system/core/libpixelflinger/codeflinger/ARMAssembler.cpp
</pre>

will need special attention. It's responsible for dynamic generation of DSP code.

== Suggestions ==
* [[User:Cfriedt]] 20081024 I'm not sure how feasible this is, given that the [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#SMedia_3362_Documentation_.26_OpenGL_ES_Drivers SMedia 3362 is heavily NDA'd]. However, since the arm920t lacks a floating-point unit / DSP core, is it possible to use the SMedia chip for general-purpose math? This would help in the Android platform, at least, for things like audio and video codecs. Aside from an OpenGL ES driver, OpenMoko documentation for the SMedia would be highly appreciated.

= Important Links =
(Please Update Me)

== Documentation ==
* [http://source.android.com/documentation Android Documentation]
* [http://www.arm.com/documentation/ ARM Documentation], (keywords: armv4t, armv5t, armv5te, arm920t, arm926ej-s)
* [http://www.arm.com/miscPDFs/9658.pdf ARM Assembly Language Programming]
* [http://www.cse.unsw.edu.au/~cs3221/labs/assembler-intro.pdf An Introduction to the GNU Assembler]
* [http://www.heyrick.co.uk/assembler/apcsintro.html ARM Procedure Call Standard], [http://en.wikipedia.org/wiki/Calling_convention#ARM ARM Calling Conventions]

== Instruction Set References ==
* [http://www.arm.com/miscPDFs/14128.pdf ARM Architecture Reference Manual], The definitive ISA documentation
* [http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf ARM Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001l/QRC0001_UAL.pdf ARM and Thumb -2 Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0025b/DVI0025.pdf ARMv4T] (See section 1.4.13)
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0014a/DVI0014A_ARM10T_PO.pdf ARMv5T] (See section 4.16)
* [http://www.arm.com/pdfs/ARM-DSP.pdf ARM DSP Enhanced Instruction Set]
* [http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042c/IHI0042C_aapcs.pdf Procedure Call Standard for the ARM Architecture]

== Hardware Reference ==

* [[Neo1973 Hardware]]
* [[Neo FreeRunner GTA02 Hardware]]

== Communities ==
* [http://source.android.com/discuss Android Public Mailing Lists]
** Specifically, [http://groups.google.com/group/android-porting android-porting]
* [http://lists.openmoko.org/mailman/listinfo OpenMoko Mailing Lists]
** Specifically, [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel openmoko-kernel]
* [http://forum.koolu.org/viewforum.php?f=10 Android on FreeRunner] at KoolU.com
* [[Openmoko Local Groups]]
* [[Openmoko:Community_Portal]]

= See also =

* [[Debug_Board]]

= External Links =
== Youtube video /Android on FreeRunner ==

[http://tw.youtube.com/watch?v=m4NbsLmF9j0 Video 1]

[http://tw.youtube.com/watch?v=r6Op-7tNTiw Video 2]

== Headline text ==

[[Category:Distributions]]

Video Player

2008-12-02T15:52:33Z

Treviño: /* Playback helper script */

Not a proper 'app' page, just an overview

=FreeRunner=
It plays mpeg-4 320x240 stretched fullscreen, however other formats will require transcoding.

==Playback==
The default media player doesn't seem to handle video very well, but mplayer does OK.

=== Using standard Mplayer ===
It can be installed with the following command:
opkg install mplayer

=== Using the Glamo XV acceleration ===
TBD, refer to: http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/

=== Controlling MPlayer from the Touchscreen ===
Create a file in /home/root/.mplayer/input.conf with this content:
# Freerunner Optimizations
MOUSE_BTN0 vo_fullscreen
MOUSE_BTN0_DBL q
Now, you can toggle the fullscreen by tapping the screen and exit from mplayer by touble-tapping the LCD.
Accelerometers or hardware buttons could help more.

=== Playback helper script ===

Create a script named 'vidplay' in your home directory with the following commands:
#!/bin/sh
xrandr -display :0 --output default --mode 240x320
mplayer -vo fbdev "$1" > /dev/null
xrandr -display :0 --output default --mode 480x640
reset

Make the script executable:
chmod 755 /home/root/vidplay

Known issues with this approach:
*The output isn't in a proper window, so background stuff sometimes flickers through.
*When done on the local terminal the keyboard is obscured so you can't exit. SSH works quite well.
*240x320 mode has some quirks:
**The gamma/brightness/contrast is weird. Encoding adjustments into the media is a workaround.
**Vertical banding (as seen in landscape position) is quite noticeable.
*Using CTRL-C to exit vidplay doesn't reset the screen; use 'q' instead.

Despite these issues, it proves that the horsepower is there and it can be done.

=== Another derivated method : works like a charm for me ! ===
No ssh, no xrandr, no script needed, juste mplayer and qwerty keyboard :
Like it's said in the "Getting started with FreeRunner" wiki page, you have to install the full qwerty keyboard, see [http://www.ginguppin.de/node/15 these instructions].
After that, you can go to Terminal and type :
mplayer vid/my_video.avi
Mplayer starts in full screen, if your video is optimized like below 240x320 it's work like a charm and to quit just use the power button.

Only issue : You can't forward/backward/pause...

==Example - Big Buck Bunny==
===PC===
Download the source (no need to start with the giant full resolution version)
cd /tmp
wget http://proyectos.pixelamigo.com/open/movies/BigBuckBunny/unofficial_PSP/big_buck_bunny_480p_AVC_FW33.mp4

Test the video filter settings (-vf crop=...) often omitting the last "rotate=2" (Optional, but recommended for long videos).
mplayer big_buck_bunny_480p_AVC_FW33.mp4 -vf crop=720:480:-1:-1,scale=320:-2,rotate=2 -zoom

Transcode it
mencoder big_buck_bunny_480p_AVC_FW33.mp4 -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 \
-vf crop=720:480:0:0,scale=320:-2,eq2=1.2:0.5:-0.25,rotate=2 -oac mp3lame -lameopts br=64:cbr \
-o big_buck_bunny_320.avi

or if it doesn't work(for me the image and the colours aren't ok) replace scale=320:-2 by scale=320:240

=== FreeRunner===
Transfer the resulting 27M file from the PC to the FreeRunner's MicroSD card
scp user@192.168.0.200:/tmp/big_buck_bunny_320.avi /media/card

Play it
/home/root/vidplay /media/card/big_buck_bunny_320.avi

==Other Info==

To rotate the screen:
xrandr -o 0
xrandr -o 1

=Neo1973=

Video is problematic on [[Neo 1973]].

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

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

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

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

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

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

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

With sound, this drops to 18fps.

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

==Playback using 480x640 / 640x480==

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

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

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

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

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

=Frontend=
==gnome-mplayer==
'''Source Code released: No'''

As a nice GUI gnome-mplayer can be recommended.

On Debian you can install it from repository:
# apt-get install gnome-mplayer

<onlyinclude>
{{ApplicationBox|
Name=[[Video Player|mplayer]]|
Description=The popular command line video player.|
Screenshot=Mplayer.png|
Homepage=http://www.mplayerhq.hu|

TestedOn=Om 2008.8 (default repository)|
PackageName=mplayer|
Source Code released=No|

}}
</onlyinclude>

== DeforaOS Player ==
'''Source Code released: Yes'''

It provides another GUI to mplayer.

It was released first there:
http://people.defora.org/~khorben/share/Openmoko/deforaos-player_0.1.0_armv4t.ipk

<onlyinclude>
{{ApplicationBox|
Name=[[DeforaOS Player|deforaos-player]]|
Description=The DeforaOS media player, a frontend to mplayer|
Screenshot=Player.png|
Homepage=http://www.defora.org/os/project/display/336/Player|

TestedOn=Om 2008.8|
PackageName=deforaos-player|
Source Code released=Yes|

}}
</onlyinclude>

[[Category:Video Applications]]
[[Category:Debian]]
[[Category:Om 2008.8]]

Video Player

2008-12-02T15:52:05Z

Treviño: /* Controlling MPlayer from the Touchscreen */

User:Seanmcneil3

2008-12-02T03:12:50Z

Treviño: /* Images */

== Android on Freerunner ==

{{Languages|Android on Freerunner}}

Google has released their open source version of the Android phone software distribution. In order to use it on the Freerunner, a number of patches need to be applied and a compiler with armv4 java exception support needs to be used to compile the software.

== Compiler suite ==

Android is a little picky about the version of gcc compiler. It also requires some java exception support that isn't available for armv4 without a minor modification. The following tools are what I use to build Android:

=== Binutils 2.18 ===

At one time I had some armv5t code that was compiled into Android which would cause the linker to generate these blx instructions which fail on armv4. I'm not sure if this is still necessary, but I still have the following change applied to binutils:

<pre>
diff -urN binutils-2.18-orig/bfd/elf32-arm.c binutils-2.18/bfd/elf32-arm.c
--- binutils-2.18-orig/bfd/elf32-arm.c 2007-08-07 02:59:23.000000000 +0700
+++ binutils-2.18/bfd/elf32-arm.c 2008-03-15 11:30:17.000000000 +0700
@@ -3093,8 +3093,8 @@
static void check_use_blx(struct elf32_arm_link_hash_table *globals)
{
if (bfd_elf_get_obj_attr_int (globals->obfd, OBJ_ATTR_PROC,
- Tag_CPU_arch) > 2)
- globals->use_blx = 1;
+ Tag_CPU_arch) >= TAG_CPU_ARCH_V5T)
+ globals->use_blx = 0;
}

bfd_boolean
</pre>

configure --prefix={devel path}/android/cross --target=arm-eabi

=== gcc 4.2.4 with gcc41-java-arm4.patch ===

configure --prefix={devel path}/android/cross --target=arm-eabi --with-arch=armv4t --enable-shared --enable-threads --disable-nls --disable-libmudflap --enable-target-optspace --with-abi=aapcs --enable-multilib --disable-libssp --disable-libstdcxx --enable-languages=c,c++

=== java-6-sun ===

This is the standard Linux package available for most (all?) distributions.

== Patches ==

Coming soon. I've posted a number of them on the devel mailing list so far. Eventually, I expect to provide everything necessary for people to build Android for themselves.

== Images ==

I have placed an older 2.6.26 kernel with Android support at:

[http://people.openmoko.org/sean_mcneil/uImage-android uImage-android]

And also a stable-tracking testing 2.6.28 kernel image at:

http://people.openmoko.org/sean_mcneil/uImage-tracking uImage-tracking]

I have put up a jffs2 image that replaces rootfs on the Freerunner at:

[http://people.openmoko.org/sean_mcneil/androidfs.jffs2 androidfs.jffs2]

Warning!!! Installation of Android requires loading a new kernel and rootfs image onto your phone. I have not had time to produce a version that runs completely off an sdcard.

== Installation ==

As noted above, this installation requires you to wipe out the existing kernel and rootfs in NAND on your Freerunner. You also must have an SDCARD and it needs to be configured with two (2) primary partitions: First is VFAT/MSDOS (16 or 32) which acts as the /sdcard storage area for pictures, movies, music, etc. and the Second is an ext3 primary partition for use of internal Android /data area to store settings, caches, etc.

The first thing I suggest is to setup an SDCARD. You can flash the NAND first, but you must have an SDCARD with two partitions as stated before you'll be able to boot. I use a 2GB card which I have split in half. fdisk shows me:

/dev/mmcblk0p1 1 2454 996310 6 FAT16<br>
/dev/mmcblk0p2 2455 4908 996324 83 Linux

formatted as

sudo mkfs.vfat /dev/mmcblk0p1<br>
sudo mkfs.ext3 /dev/mmcblk0p2

There is no need to populate the ext3 partition at all. The VFAT partition can be populated with media content if you so desire.

With your SDCARD all set, you are ready to flash the kernel and rootfs:

sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a kernel -D uImage-android<br>
sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a rootfs -D androidfs.jffs2<br>

== Tools ==

To assist in debugging and to gain shell access to the phone with Android, you can

[http://people.openmoko.org/sean_mcneil/adb adb]

You should be able to connect to the phone as long as you start it up with the USB connected to your host. I don't think it will work if you plug it in after starting. Some helpful commands are:

ADBHOST=neo ./adb logcat - like a tail -f of the android log
ADBHOST=neo ./adb logcat -b radio - same as above for the radio logs
ADBHOST=neo ./adb shell - bring up a command shell to the phone
ADBHOST=neo ./adb kill-server - kill the background server on the host

Note: ADBHOST=neo assumes you have neo in your hosts file to point to the ip of the phone (192.168.0.202). Otherwise prefix the commands with "ADBHOST=192.168.0.202 ./adb [...]" It seems that simply adding IP to /etc/hosts doesn't work on Ubuntu, using IP address (192.168.0.202) instead neo will save your time. If you cannot to the device run "adb kill-server" before trying other commands.

== Known Issues ==

This version of the linux kernel will not successfully wake from suspend mode. Your battery life will be significantly lowered because of this and the phone will lock up unless you setup the phones screen timeout to never.

This version of the kernel also uses a keypad hack. The buttons layout is as follows:

Aux left-hand upper button is the "back" key.
Power button is:
menu button when pushed quickly,
end button when held for more than a second and released,
power-off if held for 10 seconds.

GTA03

2008-12-01T03:08:43Z

Treviño: /* GTA03 Specifications */

GTA03 is the codename of a phone that is currently in development by Openmoko. For more information about other phones in development, visit [[Phone Development]]. The GTA03 will be based on a more advanced system-on-a-chip of same family as the [[Neo FreeRunner]] ([[GTA02 revisions|GTA02]]). It will presumably differ from it by having EDGE and a camera. GTA03 will not include support for 3G networks.

{{Speculations}}

== GTA03 Specifications ==
The GTA03 will be based on the [[GTA02 revisions|GTA02]] introducing several major hardware changes

New:
* New case design
* New GSM chip (2.75/EDGE): [http://www.cinterion.com/en/ktcm/modules_terminals/gerneral_purpose/Scalable_platform/MC75i_TC63i_TC65i Cinterion, (Siemens) MC75i]
* New WiFi/Bluetooth chip: [http://www.marvell.com/press/pressNewsDisplay.do?releaseID=603 Marvell 88W8688]
* Different Battery ([[Wishlist/LiFePO4 Battery]] based? - for long life?)
* Camera
* SoC: [http://semicon.samsung.de/applicationprocessors/tracking/aboutS3C6410.aspx s3c6410]
* GPS: [http://www.u-blox.com/technology/u-blox5/index.html ANTARIS 5]
Removed:
* SMEDIA Glamo

== GTA03 Evaluation Board ==
* AUG.11.2008: the 25 first GTA03EVB arrived in office
* Aug.12.2008: U-boot ported to GTA03EVB (Matt)
* Aug.12.2008: The core can run at 533 MHz with 133MHz SDRAM
* Aug.12.2008: GTA03EVB Hardware Verification of the u-blox 5 Antaris
* Aug.12.2008: GPS performance tested
* Aug.18.2008: GTA03EVB Hardware Verification of the Siemens MC 75i EDGE MODEM

== Sources ==
* http://n2.nabble.com/Weekly-Engineering-News-33-2008-tp729555p729555.html
* [[MokoForesight]]

[[Category:GTA03]]

[[Category:GTA03]]

Flashing the GSM Firmware

2008-11-27T03:10:20Z

Treviño:

==Introduction==

This is a step-by-step description of how the firmware is upgraded on a Neo with FLUID running on the device. Note that this process tolerates almost no variations. Stray from the instructions at your own peril. Instructions based on a posting by Werner (http://lists.openmoko.org/pipermail/openmoko-devel/2008-April/002605.html), thanks.

Please note: Update to MOKO9-beta firmware isn't recommended by OM, and probably won't fix any recent issues like [http://docs.openmoko.org/trac/ticket/1024 #1024] et al.

Please see http://people.openmoko.org/joerg/calypso_moko_FW for more recent FW-images.
For now there is some moko10, which should fix #666, and also has a new command AT+CSIM.
This version is not supposed to fix [http://docs.openmoko.org/trac/ticket/1024 #1024]
We are planning to include this version, renamed to moko10, to the factory image of A7 run. Version string will change though.

We recommend you don't update by following this procedure, unless you feel very comfortable with commandline. Don't miss-spell any FLUID command!
There will be a SD-image shortly, that greatly simplifies the whole GSM-update process - we suggest everybody who's not feeling completely comfortable with the procedure described herein to wait for this improved method.

'''Warning: there are chances to _completely_ brick your GSM modem on messing around with FLUID! Please watch out for typos!'''

The GSM-firmware didn't differ from GTA01 to GTA02, as the GSM-hardware didn't either. This means you can flash MOKO10 (or any other recent GSM-FW) to GTA01 as well.
According to mwester, this worked for him to update from MOKO1 on a GTA01Bv4 to MOKO10b2, by following the steps described herein.

Any reports on successful update, as well as problems encountered, or SIMs seen to work after update, all highly appreciated. Please add to the "discussion" tab of this wikipage. Thanks!

==Phase 1: Preparations==

* Download and install a distribution to your device that gives you SSH access. We recommend the fso-console image:
<pre>
mickey@amethyst$ cd /tmp
mickey@amethyst$ wget http://people.openmoko.org/mickey/images/openmoko-fso-console-image-glibc-ipk--20081028-om-gta02.rootfs.jffs2.summary
mickey@amethyst$ dfu-util -a rootfs -R -D ./openmoko-fso-console-image-glibc-ipk--20081028-om-gta02.rootfs.jffs2.summary
mickey@amethyst$ wget http://people.openmoko.org/mickey/images/uImage-2.6.24+r10+gitr75999+54524f4531c8b262431b794fea610d81bb351c86-r10-om-gta02.bin
mickey@amethyst$ dfu-util -a kernel -R -D ./uImage-2.6.24+r10+gitr75999+54524f4531c8b262431b794fea610d81bb351c86-r10-om-gta02.bin
</pre>
* Install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk on your device:
<pre>
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk
</pre>
* Install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk on your device:
<pre>
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk
</pre>
* Download http://people.openmoko.org/joerg/calypso_moko_FW/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
and place it into the /home/root directory:
<pre>
root@om-gta02:~# cd $HOME
root@om-gta02:~# wget http://people.openmoko.org/joerg/calypso_moko_FW/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
</pre>

==Phase 2: The Lobotomy==

* Make sure '''nothing''' is accessing the GSM modem. If you're using the fso-console image from the link above, this will happen automagically on boot. On other systems, kill processes as you see fit.

* Powercycle the modem:
<pre>
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
root@om-gta02:~# s3c24xx-gpio b7=0
root@om-gta02:~# echo "AT@POFF" >/dev/ttySAC0
</pre>

* Launch the FLUID binary:
<pre>
root@om-gta02:~# cd /usr/sbin
root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe \
-oO -b 115200 \
-f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
</pre>
It should say something like this (takes a few seconds to load the file):
<pre>
FLUID Revision 2.27, ...
Bootloader: (reset target)
</pre>
(if this fails repeatedly, or flashing aborted and you have a broken and "bricked" gsm-firmware due to this, try -oo instead of -oO, to use the calypso ROM bootloader instead of the firmware bootloader. Also try without the 'FLUID_FLOWCONTROL=h' part, there are reports on ROM-bootloader not working with hardware-flowcontrol. Changing the -b to some lower baudrate might improve stability of flashing-process - the bootloader does autobaud, so you're free to use any rate)

* Start a second SSH session and start the modem:
<pre>
root@om-gta02:~# s3c24xx-gpio b7=1
</pre>

FLUID should now say something like this:

<pre>
(fluid, version 3) ok
Checksumming (269 * 8kB = 2152kB): ok
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok
Program: (34 sectors, 267*8k=2136k) (*******************) ok
</pre>

'''Note: If you get this instead: MESSAGE: File cmd.m0 not found, then you didn't do the ''cd /usr/sbin''. Please pay attention ;-)'''

If FLUID does nothing, curse your bad luck and repeat the reset sequence, this is the whole 'echo 0/1, b7=0/1 stuff'.

* To verify that everything went well, do this in either of the two sessions:
<pre>
root@om-gta02:~# cat /dev/ttySAC0 &
root@om-gta02:~# echo -en 'AT\r' >/dev/ttySAC0
root@om-gta02:~# echo -en 'AT+CGMR\r' >/dev/ttySAC0
+CGMR: "HW: GTA, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal_amd8_ts0-Moko10"
root@om-gta02:~# kill %1
</pre>

In some case you may receive this:

<pre>
(fluid, version 3) ok
Checksumming (269 * 8kB = 2152kB): ok
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok
Program: (0 sectors, 0*8k=0k) () ok
</pre>

If so reflash some older firmware that can be found here (http://people.openmoko.org/joerg/calypso_moko_FW/) -- but never downgrade to a version earlier than Moko6, or you will render the GSM unusable (certain internal data structures changed between Moko5 and Moko6).
Also PLEASE DON 'T USE moko9beta1, as there is at least one report on reflashing to another FW gets difficult from moko9b1.

==Troubleshooting==

Some users wasn't able to complete the upgrade since they got an error while the firmware was uploading in the GSM chip (like ''Flash operation timeout'').

However a solution [http://n2.nabble.com/problems-with-calypso-firmware-update-tp1565196p1566012.html has been found] and it allows to use again the GSM modem.

Use the following fluid command:

<pre>
FLUID_PORT=/dev/ttySAC0 fluid.exe -oO -b 115200 -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0
</pre>
(Without FLOWCONTROL and with -oo to choose the ROM bootloader)

Then on a ''second ssh session'' please use this instead of the gpio command:
<pre>
echo 0 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
echo 1 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on
</pre>
The firmware download should start now.

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

Windows

2008-11-22T15:09:56Z

Treviño: New page: * Neo 1973 and Windows * Flashing with dfu-util under Windows * Android - Windows Connectivity

* [[Neo 1973 and Windows]]
* [[Dfu-util-windows| Flashing with dfu-util under Windows]]
* [[Android#Windows_Connectivity|Android - Windows Connectivity]]

Keyboards

2008-11-22T14:59:24Z

Treviño: Redirecting to Keyboard Debate

#REDIRECT [[Keyboard_Debate]]

Keyboards

2008-11-22T14:59:02Z

Treviño: New page: ##REDIRECT Keyboard_Debate

##REDIRECT [[Keyboard_Debate]]

User talk:Seanmcneil3

2008-11-07T18:43:40Z

Treviño: /* Android and replying calls */

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So, what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer?!

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

User talk:Seanmcneil3

2008-11-07T18:42:58Z

Treviño:

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer...

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

User talk:Seanmcneil3

2008-11-07T18:42:04Z

Treviño: /* Replying calls */ new section

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Could you set-up a rootfs for running Android from MicroSD?

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

== Replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

So what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer...

User talk:Seanmcneil3

2008-11-06T00:20:51Z

Treviño:

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Could you set-up a rootfs for running Android from MicroSD?

== Android Misc requests ==

ssh ?

--

dilersam: thanks for having added more informations to the page. It helps a lot.

User talk:Seanmcneil3

2008-11-06T00:20:31Z

Treviño:

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android Misc requests ==

ssh ?

--

dilersam: thanks for having added more informations to the page. It helps a lot.

Talk:Community Updates

2008-11-03T15:06:48Z

Treviño: /* Flashing the Neo GSM modem */ new section

Add news to this page, and from time to time we will issue a community update.

How are newsletters organized elsewhere:
http://lists.openmoko.org/pipermail/community/2008-October/032628.html

[[/Archive 1]]

== Flashing the Neo GSM modem ==

[http://wiki.openmoko.org/wiki/GSM/Flashing This is a Wiki] that explains how to upgrade the GSM modem firmware of the Neo.

Recording audio

2008-10-31T16:43:11Z

Treviño:

Mixer settings for voice recording: It is required that DAI Mode (alsa control number 50) is "DAI 1" - only recording, or "DAI 2" - recording and playback simultaneously. "DAI 0" is only for playback. There's also "DAI 3", but I don't know what this is.

Depending on the recording source, Mic1 for headset or Mic2 for handset have to be set accordingly via the Mic Selection Mux, which is alsa control number 53. Also, set Capture Left Mux and Capture Right Mux (65, 64) to PGA.

Below is an alsa state file, which can be used to put the device into voice recording mode. It's advisable to have a programm connected to e.g. /dev/dsp, else the device might crash. Change settings via:

alsactl -f voice-recording.state restore

http://wildsau.enemy.org/~moko/voice-recording.state

arecord -D hw -f cd -v -t wav rec-$(date +%Y-%m-%d-%H-%M).wav

[[Category:Audio]]

Talk:Community Updates

2008-10-29T07:59:38Z

Treviño: /* From the stars */

Add news to this page, and from time to time we will issue a community update.

= Images =
* [[FDOM]]: David [http://lists.openmoko.org/pipermail/community/2008-October/034219.html released again], announcing that development moved to a new home. Mirrors added, more needed. FDOM now exists as an installer script: the FDOMizer. It is meant to be run over the 2008.10 image or over existing FDOM installation.
* Qt Extended 4.4.2 released. [http://qtextended.org/modules/mydownloads/index.php Downloads].
* Open Handset Alliance announces the launch of [http://source.android.com/ Android Open Source Project]. Koolu [http://koolu.com/ announces] that Koolu Beta port of Android for Freerunner will be available to download for existing Freerunner owners and installed on phones for sale in November 2008, contact Brian Code there. Sean McNeil [http://lists.openmoko.org/nabble.html#nabble-td1361683 has been working on it] too.

= Applications =
* [[Sephora]] settings manager 0.2 alpha 3 released, adds GERMAN localization.
* [[Mokoko]] yet another media player.
* Telephone auto-reply scripts were proposed. Kamil send one that replies with a "not available" SMS when one [http://lists.openmoko.org/pipermail/community/2008-October/034327.html flips the FreeRunner] face down. Alex showcased a project for a full [http://lists.openmoko.org/pipermail/community/2008-October/034409.html phone firewall] stack, with GUI.
* On the same thread, Mickey reminded about the power of ''oeventsd'' 's rules file. This is a user-tweakable rules engine using yaml-syntax to configure system-wide behaviour on DBus events (what a mouthful !). It was introduced in FSO Milestones 3 and needs user feedback, and [[OpenmokoFramework/Status Update 4#What.27s new since Milestone II| more documentation]] I guess.
* [http://lists.openmoko.org/nabble.html#nabble-td786719 fso-control]. A (suspend, reboot, shutdown) menu designed to pop up with the POWER button. Uses python, edje and frameworkd.

= Hardware =
* [http://www.opkg.org/specials/ Customize the case] look.

= Wiki and community =
* Academic projects at National Taipei University: [[The Bicycle Motion Information Displayer]], [[Business Card Exchange system]], [[Location-based mobile video streaming system]], [[Dancing With the Mobile Phone]]
* Following the three GSoC interns at OpenMoko Inc., [[Tsing Hua OpenLab]] held a workshop on 10/29.
* The [[Erlang]] wiki page deserves a special mention in this newsletter for a few reasons. First, it received some TLC this week and is now one of the best articles in our wiki. Second, Erlang is based on concurrent functional programming, an interesting paradigm that needs more advertising. Third, it's nice to think that around the FreeRunner's cradle, there is not only Nokia, Swisscom and Google's electromechanical avatar, but also a sign of Ericsson research. Fourth, [http://www.erlang.org Erlang] rocks for reliable soft real-time distributed telecoms applications and this is where the future is - see what [http://www.dash.net Dash] made of the Neo 1973 platform.

= From the stars =
Harald looked at [http://laforge.gnumonks.org/weblog/2008/10/20#20081020-nand_speed optimizing the NAND memory speed timings on the GTA02]:'' Some initial experiments show that the performance can be easily improved by 41%. However, the actual speed (6.59MBytes/sec) is still much lower than the theoretical maximum read performance of 15.64MBytes/sec. It seems there is more room for improvement inside the MTD layer of the Linux kernel.''

Tick merged the fix written by [[User:Treviño|Treviño]] that applied to qtopia-x11 the [[User:Mickey|Mickey Lauer]] suggestions for the 'Echo Bug’ {{Ticket|1267}} in the git around October 15th, it works, can use more field testing. See also the thread [http://lists.openmoko.org/pipermail/community/2008-October/033312.html Echo issue on OM2008.08 solved] on the community mailing list.

= Outside Openmoko =

= See also =
* John's team [http://lists.openmoko.org/pipermail/community/2008-October/034258.html status update] for first week. They already have one minute of boot time shaved (static /dev is a big gain) and stomped on the "echo" bug, working on {{Ticket|2071}}, python loader speed and resume visual feedback. Also [http://lists.openmoko.org/nabble.html#nabble-f528198 improved touch screen useability].

How are newsletters organized elsewhere:
http://lists.openmoko.org/pipermail/community/2008-October/032628.html

[[/Archive 1]]

Android

2008-10-28T13:46:18Z

Treviño: /* Current State */

{{Distributions|Android}}

= Updates =

* 20081021 [[User:Cfriedt]] Android -> FreeRunner updates on my [http://perpetual-notion.blogspot.com/search/label/android blog]
* 20081022 [[User:Cfriedt]] I was able to 'trivially' compile all of the Android source code without error for the ARMv4T architecture by removing v5TE instructions. Although it will definitely not run anything predictably, at least now that I know the build system will work with a few simple substitutions in build/core/combo/arm-linux.mk. At this point I am able to go ahead and re-implement v5TE instructions as v4T instruction sequences instead (or re-implement entire sections of assembly with hand-optimized v4T instructions).
* 20081023 [[User:Bricode]] To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw

= Introduction =
This page is dedicated to porting the [http://www.android.com Android OS] to the [[Neo 1973]] and [[Neo FreeRunner]] handsets. Since the Android OS was [http://source.android.com/posts/opensource publically released] on 20081021, [http://benno.id.au/blog/2007/11/21/android-neo1973 work] [http://perpetual-notion.blogspot.com/search/label/android is] [http://groups.google.com/group/android-porting currently underway] to port Android to the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

== Goals ==
# Systematically introduce patches for ARMv4T in the Android codebase
# Provide Neo1973 and Neo FreeRunner hardware-dependent patches in the Android codebase, leveraging the work already done by the Openmoko developers, without forcing Android-specific changes upstream
# Provide a useable Android filesystem and kernel on the [[Distributions]] page that conform to current Openmoko installation routines

== Early Attempts ==
As [http://benno.id.au Ben Leslie] had pointed out on his [http://benno.id.au/blog/2007/11/21/android-neo1973 blog] far before the source code was released, [http://www.android.com Android] was originally designed to work with the ARMv5TE [http://en.wikipedia.org/wiki/Instruction_set_architecture instruction set architecture] (ISA), which allows for [http://en.wikipedia.org/wiki/ARM_architecture#DSP_Enhancement_Instructions DSP enhanced instructions]. Contrary to the ARMv5TE ISA, the Neo1973 and FreeRunner handsets both feature an arm920t core, which comply to the ARMv4T ISA.

Before the source code was released, kernel trap handlers were implemented to 'emulate' the ARMv5TE ISA. Although the results worked in many cases, trapping is costly and performance suffered as a result. Moreover, without explicitly knowing which conditions were set by various instructions, such as Thumb Mode execution, the result became nondeterministic.

== Current State ==

With the release of the Android [http://source.android.com source code], the Open Source community is no longer limited to dealing with a binary-only product. The Open Handset Alliance (OHA) has let their source code become their product for everyone enrich and benefit from.

Currently, porting efforts are underway in many circles. Patches should be submitted via the [http://source.android.com/submit-patches official Android channels].

To track the status of which parts of the Android source tree contain ARMv5 specific code, I've created a table of where it is contained, and the status of patches. It can be found at: http://spreadsheets.google.com/pub?key=pzDEXnU19gkeTjpD28t-7fw [[User:Bricode]]

Sean McNail said that he was able to get Androind running (including telephony) in his Freerunner [http://3v1n0.tuxfamily.org/tumblelog/post/368 source].

Ben Leslie mentioned on the android-porting list that he was able to get the 'Android' logo to appear on his Neo 1973.

= How to Help =

== Getting Started ==

You can start by following the instructions to download and build the Android source from scratch. Please see [http://source.android.com/download http://source.android.com/download] and follow the instructions for your architecture.

== Publicize Your Efforts ==

It's generally a good idea to make your efforts known via wiki systems, public mailing lists, forums, and publically open version control systems.

Always take credit for your work but please don't do it in the form of comments. Some code is already hard enough to read without comments polluting the text. The best thing to do is to create a patch and put a header with your information at the top. Collaboration systems such as git might already do this for you (??).

If you create something new and have the ability to designate the license for it, please consider license compatibility issues.

== Porting Strategy ==

* Analysis and leverage of the existing build system
** buid/core/combo/arm-linux.mk
*** -D__ARCH_ARM_4__ -D__ARCH_ARM_4T__
*** -march=armv4t -mcpu=arm920t
** fix various static references to 'armv5'
* Isolating ARMv5TE ISA dependent code
** e.g. grep -n -R -i "${armv5te_isa_pattern}" ~/android
* Abstracting
** ( C/C++ )
*** Use inlined functions / #ifdef statments to implement functions in a portable manner
*** For inlined assembler calls, it's acceptable for now to use generic C code instead, so long as later on we optimize it by hand.
** ( ASM )
*** Proprocessor statements based on ISA / architecture, e.g. #ifdef __ARCH_ARM_5__ ... #endif #ifdef __ARCH_ARM_4__ ... #endif
*** It's highly suggested that preprocessor statements should not be nested (i.e. make them mutually exclusive)
*** Some people have suggested that we should not do #ifdef's based on ARCH or ISA, but rather based on an AndroidConfig.h which would define macros like PLD(...) #ifdef HAVE_ARM_PLD pld #else ... #endif .

For each ARMv5TE instruction, one could potentially
* Implement the instruction using general registers instead of DSP calls (i.e. eabi / softfloat)
* If that is a) nondeterministic, or b) slow, then sections of code need to be analyzed and hand-optimized for the ARMv4T isa

== List of Unsupported Instructions ==

This is a list of opcodes, extracted from the Android source, that are unsupported for ARMv4T compliant processors (specifically the arm920t). The opcodes represent instructions available for ARMv5, ARMv5T, and ARMv5TE architectures, which are not present in the ARMv4T ISA. The list was obtained by exhaustively editing the recompiling the Android source code until it compiled without error.

Please keep in mind, that in some cases, translating these instructions into a sequence of ARMv4T instructions will be impossible and / or result in nondeterministic execution because of
* the requirement of additional context
* the tendencies of certain opcodes to change condition registers that may or may not be present in the arm920t core

=== Opcodes ===

For now, so that the code is clearer, I would just suggest using C instead of assembly language so that less space is used.

{{scroll box|height=480px|text=
<TABLE BORDER="1">
<TR>
<TH>Opcode</TH>
<TH>Desription</TH>
<TH>[[http://www.arm.com/miscPDFs/14128.pdf PDF]] Page Number</TH>
<TH>C</TH>
<TH>ASM</TH>
</TR>
<TR>
<TH VALIGN="TOP">BLX(1)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>166</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">BLX(2)</TH>
<TD>Branch, Link, and Exchange</TD>
<TD>168</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">CLZ</TH>
<TD>Count Leading Zeros</TD>
<TD>175</TD>
<TD>
[[User:Cfriedt]] 20081026
<pre>
#include <stdint.h>

void clz( uint32_t * Rd, uint32_t * Rm )
{
uint32_t mask = 0x80000000;

// in case Rd == Rm
uint32_t dummy = 0;

if ( *Rm == 0 )
{

dummy = 32;

} else {

for ( dummy = 0 ;
dummy < 32 &&
( ! ( mask & (*Rm) ) ) ;
dummy++, mask >>= 1
);

}

(*Rd) = dummy;

}
</pre>
</TD>
<TD>
</TD>
</TR>

<TR>
<TH VALIGN="TOP">LDRD</TH>
<TD>Load Registers Doubleword</TD>
<TD>200</TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">PLD</TH>
<TD>Preload Data</TD>
<TD>240</TD>
<TD>Remove</TD>
<TD>Remove</TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLA<x><y></TH>
<TD>Signed Multiply-Accumulate</TD>
<TD>291</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAL</TH>
<TD>Signed Multiply Accumulate Long</TD>
<TD>296</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMLAW<x></TH>
<TD>Signed Multiply-Accumulate Word</TD>
<TD>302</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULL</TH>
<TD>Signed Multiply Long</TD>
<TD>318</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMUL<x><y></TH>
<TD>Signed Multiply</TD>
<TD>316</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">SMULW<y></TH>
<TD>Signed Multiply Word</TD>
<TD>320</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QADD</TH>
<TD>Saturating Add</TD>
<TD>242</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDADD</TH>
<TD>Saturating Double and Add</TD>
<TD>249</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QSUB</TH>
<TD>Saturating Subtract</TD>
<TD>253</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">QDSUB</TH>
<TD>Saturating Double and Subtract</TD>
<TD>251</TD>
<TD></TD>
<TD></TD>
</TR>
<TR>
<TH VALIGN="TOP">STRD</TH>
<TD>Store Registers Doubleword</TD>
<TD>349</TD>
<TD></TD>
<TD></TD>
</TR>
</TABLE>
}}

=== Scanning for Files That Use the ARMv5TE ISA ===

Using the above list of opcodes, one can scan the Android source code for ARMv4T-incompatible instruction sequences.

'''Code:'''
<pre>
opcodes="blx clz ldrd pld smlabb smlabt smlatt smlal smlawb smlawt smulbb smulbt smull smultt smulwb smulwt qadd qdadd qsub qdsub strd"

opcodePat="$(echo ${opcodes} | sed -e 's/ /\\\|/g')"

fileList="$(grep -R -i "$${opcodePat}$ " * 2>/dev/null | grep -v "^Binary file" | sed -e 's/:.*//' | grep -v "CREDITS\|README\|^$kernel/$\|$\.txt$$" | sort -u)"

for i in ${fileList}; do
echo "* ${i}"
done
</pre>

=== Source Files in Android that Use the ARMv5TE ISA ===

The list of files below may or may not be complete. There might also be some assembly code that is generated with a python script (verification?).

{{scroll box|height=150px|text=
* bionic/libc/arch-arm/bionic/memcmp.S
* bionic/libc/arch-arm/bionic/memcmp16.S
* bionic/libc/arch-arm/bionic/memcpy.S
* bionic/libc/arch-arm/bionic/strlen.c
* bionic/libc/kernel/arch-arm/asm/arch/irqs.h
* bionic/libc/tools/gensyscalls.py
* bootloader/legacy/nandwrite/init.S
* bootloader/legacy/usbloader/init.S
* dalvik/vm/arch/arm/CallEABI.S
* dalvik/vm/arch/arm/CallOldABI.S
* dalvik/vm/mterp/armv5/OP_AGET_WIDE.S
* dalvik/vm/mterp/armv5/OP_APUT_WIDE.S
* dalvik/vm/mterp/armv5/OP_IGET_WIDE.S
* dalvik/vm/mterp/armv5/OP_IGET_WIDE_QUICK.S
* dalvik/vm/mterp/armv5/OP_IPUT_WIDE.S
* dalvik/vm/mterp/armv5/OP_IPUT_WIDE_QUICK.S
* dalvik/vm/mterp/armv5/OP_SGET_WIDE.S
* dalvik/vm/mterp/armv5/OP_SPUT_WIDE.S
* dalvik/vm/mterp/out/InterpAsm-armv5.S
* dalvik/vm/oo/Object.h
* development/emulator/qtools/armdis.cpp
* development/emulator/qtools/thumbdis.cpp
* external/elfutils/src/Makefile
* external/elfutils/src/Makefile.am
* external/elfutils/src/Makefile.in
* external/freetype/include/freetype/config/ftconfig.h
* external/jpeg/jidctfst.S
* external/neven/Embedded/common/src/b_BasicEm/Math.c
* external/opencore/codecs_v2/audio/aac/dec/src/calc_sbr_synfilterbank.cpp
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_gcc.h
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4.h
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v4_gcc.h
* external/opencore/codecs_v2/audio/aac/dec/src/fxp_mul32_arm_v5.h
* external/opencore/codecs_v2/audio/aac/dec/src/pv_normalize.h
* external/opencore/codecs_v2/audio/aac/dec/src/trans4m_freq_2_time_fxp.cpp
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_gcc_v5.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/basic_op_arm_v5.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_add.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mac.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_msu.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_mult.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/l_sub.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mpy_32_16.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/mult.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_nb/common/include/norm_l.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/normalize_amr_wb.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_armv5.h
* external/opencore/codecs_v2/audio/gsm_amr/amr_wb/dec/src/pvamrwbdecoder_basic_op_gcc_armv5.h
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_16_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_dct_9_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.asm
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_mdct_18_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.asm
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window.s
* external/opencore/codecs_v2/audio/mp3/dec/src/asm/pvmp3_polyphase_filter_window_gcc.s
* external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm.h
* external/opencore/codecs_v2/audio/mp3/dec/src/pv_mp3dec_fxd_op_arm_gcc.h
* external/opencore/codecs_v2/audio/mp3/dec/src/pvmp3_normalize.h
* external/opencore/codecs_v2/audio/sbc/enc/src/sbcenc_filter.h
* external/opencore/codecs_v2/video/avc_h264/dec/src/vlc.cpp
* external/opencore/codecs_v2/video/m4v_h263/enc/src/dct_inline.h
* external/opencore/codecs_v2/video/m4v_h263/enc/src/fastquant_inline.h
* external/opencore/codecs_v2/video/m4v_h263/enc/src/vlc_encode_inline.h
* external/opencore/fileformats/avi/parser/include/pv_avifile_streamlist.h
* external/opencore/fileformats/avi/parser/src/pv_avifile_streamlist.cpp
* external/openssl/crypto/bn/bn_prime.c
* external/qemu/target-arm/translate.c
* external/qemu/trace.c
* external/skia/include/corecg/SkFixed.h
* external/skia/include/corecg/SkMath.h
* external/skia/libcorecg/Sk64.cpp
* external/skia/libcorecg/SkMatrix.cpp
* external/skia/libsgl/effects/SkColorMatrixFilter.cpp
* external/skia/libsgl/sgl/SkBitmap.cpp
* external/skia/libsgl/sgl/SkBitmapShader.cpp
* external/skia/libsgl/sgl/SkGraphics.cpp
* external/srec/config/en.us/dictionary/c0.6.ok
* frameworks/base/libs/audioflinger/AudioMixer.cpp
* frameworks/base/libs/audioflinger/AudioResamplerSinc.cpp
* frameworks/base/opengl/libagl/iterators.S
* frameworks/base/opengl/libagl/matrix.h
* system/core/include/private/pixelflinger/ggl_fixed.h
* system/core/libpixelflinger/codeflinger/ARMAssembler.cpp
* system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp
* system/core/libpixelflinger/codeflinger/disassem.c
* system/core/libpixelflinger/codeflinger/texturing.cpp
* system/core/libpixelflinger/rotate90CW_4x4_16v6.S
* system/core/libpixelflinger/t32cb16blend.S
}}

=== Discussion ===
=== Notes ===
* (ASM) In order to return from a subroutine, use methods that are known to work from ARMv4T onwards <pre>mov pc,lr ==> bx lr</pre>

== Suggestions ==
* [[User:Cfriedt]] 20081024 I'm not sure how feasible this is, given that the [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#SMedia_3362_Documentation_.26_OpenGL_ES_Drivers SMedia 3362 is heavily NDA'd]. However, since the arm920t lacks a floating-point unit / DSP core, is it possible to use the SMedia chip for general-purpose math? This would help in the Android platform, at least, for things like audio and video codecs. Aside from an OpenGL ES driver, OpenMoko documentation for the SMedia would be highly appreciated.

= Important Links =
(Please Update Me)

== Documentation ==
* [http://source.android.com/documentation Android Documentation]
* [http://www.arm.com/documentation/ ARM Documentation], (keywords: armv4t, armv5t, armv5te, arm920t, arm926ej-s)
* [http://www.arm.com/miscPDFs/9658.pdf ARM Assembly Language Programming]
* [http://www.cse.unsw.edu.au/~cs3221/labs/assembler-intro.pdf An Introduction to the GNU Assembler]
* [http://www.heyrick.co.uk/assembler/apcsintro.html ARM Procedure Call Standard], [http://en.wikipedia.org/wiki/Calling_convention#ARM ARM Calling Conventions]

== Instruction Set References ==
* [http://www.arm.com/miscPDFs/14128.pdf ARM Architecture Reference Manual], The definitive ISA documentation
* [http://www.simplemachines.it/doc/QRC0001H_rvct_v2.1_arm.pdf ARM Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001l/QRC0001_UAL.pdf ARM and Thumb -2 Instruction Set Quick Reference Card]
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0025b/DVI0025.pdf ARMv4T] (See section 1.4.13)
* [http://infocenter.arm.com/help/topic/com.arm.doc.dvi0014a/DVI0014A_ARM10T_PO.pdf ARMv5T] (See section 4.16)
* [http://www.arm.com/pdfs/ARM-DSP.pdf ARM DSP Enhanced Instruction Set]
* [http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042c/IHI0042C_aapcs.pdf Procedure Call Standard for the ARM Architecture]

== Hardware Reference ==

* [[Neo1973 Hardware]]
* [[Neo FreeRunner GTA02 Hardware]]

== Communities ==
* [http://source.android.com/discuss Android Public Mailing Lists]
** Specifically, [http://groups.google.com/group/android-porting android-porting]
* [http://lists.openmoko.org/mailman/listinfo OpenMoko Mailing Lists]
** Specifically, [http://lists.openmoko.org/mailman/listinfo/openmoko-kernel openmoko-kernel]
* [http://forum.koolu.org/viewforum.php?f=10 Android on FreeRunner] at KoolU.com
* [[Openmoko Local Groups]]
* [[Openmoko:Community_Portal]]

= See also =

* [[Debug_Board]]

= External Links =

[[Category:Distributions]]

Ipkg

2008-10-12T21:53:48Z

Treviño:

'''NB:''' Current (2008-04-04+) builds of Openmoko now come with the syntax compatible [[Opkg]] tool, not ipkg.

{{Todo|Integrate useful content into [[Opkg]] as a usage section.}}

The practical way to install software on Openmoko is with the [http://handhelds.org/moin/moin.cgi/Ipkg Ipkg package manager], possibly via the graphical Application Manager. Naturally, you need to have obtained an Openmoko system by other means initially.

In the shell, "opkg update" will update the list of available packages, "opkg upgrade" will download and install all packages that have a newer version available and "ipkg install new-app" will download and install "new-app".

Have a look at [[Users Repositories]] to get addresses of alternative software repositories, e.g. ScaredyCat's ipkg repository.

== History ==

Ipkg re-implements for embedded systems the functionality of Debian tools dpkg, apt, and apt-get. For example, it uses much less disk space for the package metadata.

== Installing Packages to the Memory Card ==

You can use ipkg to install packages to a folder on the memory card. To do this you'll need the following:

=== Ext2 Formatted Memory Card ===

By default, the memory card comes formated with VFAT (Windows Format). You need to re-format the card with EXT2. You will not be able to view the files on the card using a windows system after this.

To check if your card is using vfat or ext, run the 'mount' command, and look for: /dev/mmcblk0p1 on /media/card.

On the NEO, run the following:
''' This will erase everything on your memory card '''

umount /media/card
fdisk /dev/mmcblk0
t
83
w
mke2fs /dev/mmcblk0p1
mount /media/card

=== Entry in opkg.conf File ===

In your /etc/opkg.conf file, after "dest root /" add a new line:
dest card /media/card/opkg

Create /media/card/opkg folder
mkdir /media/card/opkg

=== Installing Packages on the Card ===

When installing a package, use the -d option to have the package installed into the "card" destination:
opkg install -d card python-core

This will put all files (binaries and libraries) on the card, under the folder specified in the ipkg.conf file.

=== Linking/Using Packages on the Card ===

Your system will not be able to see the packages that you just added to your card. There are two ways to remedy this.
The better solution is to use ipkg-link from the 'ipkg-utils' package, but 'better' is always subjective - YMMV.

==== 1: Ipkg Utils and ipkg-link ====

Ipkg-utils is a package that provides some additional functionality for ipkg. A very useful tool is ipkg-link, which creates symbolic links for packages installed in non-root locations (such as a card) back to the root file system.

To make this working with Opkg, you've simply to do:
ln -s /etc/opkg.conf /etc/ipkg.conf
ln -s /media/card/opkg/usr/lib/opkg /media/card/opkg/usr/lib/ipkg

To get ipkg-utils, run:
ipkg install ipkg-utils

To create symbolic links to your root system for a specific package, run: ipkg-link add <package>. For example, for python-core use:
ipkg-link add python-core

To create symbolic links for all packages installed in a location, run:
ipkg-link mount /media/card/ipkg

The ''ipkg-link remove'' and ''ipkg-link unmount'' commands remove the symlinks for a package or all packages.

There is a list of the options for the ipkg command under "How do I use it?" [http://handhelds.org/moin/moin.cgi/Ipkg here.]

==== 2: Adding the card PATH and LIB directories to your path ====
Another way to add bin and lib files to your system is by modifying your environment variables in /etc/profile as follows:

On the line that defines the PATH variable, add:
PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin:/media/card/ipkg/usr/bin

Then, before the 'export' line add:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/media/card/ipkg/usr/lib

Then modify the 'export' line and add LD_LIBRARY_PATH to the end.

This will let the system see the binary and library files, but it will not see other resources, such as images, configuration files, desktop files, etc. For this reason, ipkg-link is preferred.

FreeRunner/Buttons and LEDs

2008-09-18T04:24:23Z

Treviño: /* Leds */

This is the Software specification for the Openmoko Neo FreeRunner Button and LEDs.
''Note that this is a future specification which is not yet implemented in the software''

=Taxonomy=

==What's currently implemented==
/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/
/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/
/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/
Those are all userspace directories for controlling the LEDs. echo 0 > brightness will turn the LED off. echo 1 > brightness will turn it on.
trigger currently does nothing.

==Buttons==
* AUX = Button on the left side of the device, upper area
* POWER = Button on the right side of the device, center area (right below the USB socket)

==Leds==
{| border=1 cellspacing=0 cellpadding=5
| EVENT
|style="background:#FF0000;color:white;"| '''red'''
| behind AUX button
|-
| HEARTBEAT
|style="background:#FF8040;color:white;"| '''orange'''
| behind POWER button
|-
| WIRELESS / BLUETOOTH
|style="background:#0000FF;color:white;"| '''blue'''
| behind POWER button
|-
| MIXING TWO LEDS
|style="background:#80409F;color:white;"| '''purple'''
| behind POWER button if turning on the blue and the orang buttons together
|}

==Modes==
* OFF = Device has no power or has been shutdown
* ON = Device is fully powered
* ON+CHARGING = Device is fully powered and has been connected to a USB host or Openmoko charger.
* LOCK = Device is fully powered, but has screen lock displayed
* SUSPEND = Device has been suspended to low-power mode

=Basic Button Usage=

This is grouped by mode:

==Mode: OFF==

* To switch the device on: Press and hold POWER until the boot logo appears.
* To enter the "normal" (NAND) boot menu: Press and hold POWER, one second later press and hold AUX.
* To enter the "rescue" (NOR) boot menu: Press and hold AUX, then press and hold POWER.

==Mode: ON==

* To suspend the device: Press POWER.
* To shut down the device: Press and hold POWER for 4 seconds. If the device hangs, press and hold POWER for 8 seconds. If it still hangs, remove the battery and disconnect from USB.
* To go to the home screen: Press AUX.
* To display the profile screen: Press and hold AUX until it appears.

==Mode: SUSPEND==

* To wakeup the device: Press POWER.

=Basic LED Usage=

LEDs are very useful in broadcasting valuable basic status information to the user in a way that the user does not have to unlock the device, enable the screen or turning the screen saver off and subsequently search the screen for basic status information.

''This is grouped by mode:''

==Mode: OFF==

* All LEDs will be turned off.

==Mode: ON==

* HEARTBEAT will emit a short blink every 4 seconds.
* If Bluetooth is powered on, WIRELESS will emit a short blink every 2 seconds.
* If Wifi is powered on, WIRELESS will emit a long blink every 2 seconds.
* If Bluetooth and Wifi are powered on, WIRELESS will be lit continuosly.

==Mode: ON+CHARGING==

''Same as ON, with the exception of''
* HEARTBEAT will increase blinking as the charge level of the battery increases.
* HEARTBEAT will be continuosly lit, if the battery has been fully charged.

==Mode: SUSPEND==

* All LEDs will be turned off.

=Advanced Button/LED Usage=

* In ON-Mode, EVENT will blink every 2 seconds if there's an event that needs your attention.
* The more events, the faster EVENT will blink.
* Pressing AUX will acknowledge the event with the topmost priority and display it to you.
* EVENT will stop to blink once all events have been acknowledged.

=A first rules implementation=
A C implementation of these rules has been [http://lists.openmoko.org/pipermail/openmoko-devel/2008-July/003458.html done by smurfy - phil] and is available at http://www.smurfy.de/files/neo/openmoko-led-v1.tar.gz

=Python Script For Blinking Leds By Beats=
Reads beats from a file and blinks FreeRunners leds.

File format is human readable text, consisting of a simple sequence of integer quartet (4 numbers). The first number representing status of blue power-led, second means status of orange power-led and third means status of red aux-led. 0=OFF, 1=ON. (If blue=1 and orange=1 then power=lila. This has nothing to do with this python script or this file format.) The last number represents the duration in milliseconds to hold that situation of leds. Any non digit characters in the file count as a separators between numbers, but are otherwise ignored.

It requires packages python-core and python-re from opkg.
==== Led blinker ====

#!/usr/bin/python
"""Led Blinker Player

Usage: python leds.py [filename]
"""
import sys
import time
import re

def loadFromTextFile(filename):
infile = open(filename)
contents = infile.read()
return re.findall("(\d+)\D*(\d+)\D*(\d+)\D*(\d+)", contents)

def playNote(blue_value, orange_value, red_value, duration):
blue.write(str(blue_value) + "\n")
orange.write(str(orange_value) + "\n")
red.write(str(red_value) + "\n")
time.sleep(float(duration) / 1000.0)

def playFile(filename):
global blue, orange, red
notes = loadFromTextFile(filename)
blue = open("/sys/class/leds/gta02-power:blue/brightness", "w", 1)
orange = open("/sys/class/leds/gta02-power:orange/brightness", "w", 1)
red = open("/sys/class/leds/gta02-aux:red/brightness", "w", 1)

for first,second,third, duration in notes:
playNote(first,second,third,duration)

playNote(0, 0, 0, 0)
blue.close()
orange.close()
red.close()

if __name__ == "__main__":
playFile(sys.argv[1])

==== Example Beat ====
The following is an example "fireworks"-file that can be used to test the led blinker.

1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100

[[Category:Neo FreeRunner Hardware]]

Themes

2008-09-16T14:54:09Z

Treviño:

This page is a stub about making Openmoko pretty, waiting for openmono-look.org .

One may already [[Customize Application Icons]], change [[Ringtones]] and customize the windows decoration with [[Edje]].
But there is not much yet by way of ready-to-use themes for changing the look and feel of the phone with `opkg'.

== Where to find themes ==

A Tango variant for Illume based distros is at [http://52grad.de/.stuff/freerunner/].

A GTK theme for the tango theme is at [http://www.3v1n0.net/openmoko/moko-sun-gtkrc]

The [http://exchange.enlightenment.org/ Enlightenment exchange] repository has themes, modules and applications.

There are a few background images for the [[Display Locker]] screen in Om 2007.2.

== How to customize the boot screens ==

There are three steps: u-boot, kernel and X.

=== Changing the u-boot splash image ===

The u-boot splash image is on its own partition. According to ticket <strike>[http://docs.openmoko.org/trac/ticket/1735 1735]</strike>:
To replace the splash screen image on the device you need to convert the PNG file to a compressed raw frame buffer content and then flash this into the splash screen partition.
For the conversion, go to svn.openmoko.org/trunk/src/host/splash/ and run
./splashimg.pl boot_image.png | gzip -9 >new_splash.gz
If your update process runs under Linux (OE package ?) you'd then execute the following commands:
flash_eraseall /dev/mtd4
nandwrite -p /dev/mtd4 new_splash.gz
If you update through DFU, you would:
dfu-util -a splash -R -D new_splash.gz
Note the NOR also contains a copy of the splash screen. If you generate a new NOR image with "mknor", just specify the new image with -s boot_image.png, and it will put the "openmoko" text near the bottom of the screen.

=== Changing the Kernel's boot splash image ===

TBD

=== Changing X's startup ===

TBD

FreeRunner/Buttons and LEDs

2008-09-03T03:14:58Z

Treviño:

This is the Software specification for the Openmoko Neo FreeRunner Button and LEDs.
''Note that this is a future specification which is not yet implemented in the software''

=Taxonomy=

==What's currently implemented==
/sys/devices/platform/gta02-led.0/leds/gta02-aux:red/
/sys/devices/platform/gta02-led.0/leds/gta02-power:blue/
/sys/devices/platform/gta02-led.0/leds/gta02-power:orange/
Those are all userspace directories for controlling the LEDs. echo 0 > brightness will turn the LED off. echo 1 > brightness will turn it on.
trigger currently does nothing.

==Buttons==
* AUX = Button on the left side of the device, upper area
* POWER = Button on the right side of the device, center area (right below the USB socket)

==Leds==
{| border=1 cellspacing=0 cellpadding=5
| EVENT
|style="background:#FF0000;color:white;"| '''red'''
| behind AUX button
|-
| HEARTBEAT
|style="background:#FF8040;color:white;"| '''orange'''
| behind POWER button
|-
| WIRELESS
|style="background:#0000FF;color:white;"| '''blue'''
| behind POWER button
|}

==Modes==
* OFF = Device has no power or has been shutdown
* ON = Device is fully powered
* ON+CHARGING = Device is fully powered and has been connected to a USB host or Openmoko charger.
* LOCK = Device is fully powered, but has screen lock displayed
* SUSPEND = Device has been suspended to low-power mode

=Basic Button Usage=

This is grouped by mode:

==Mode: OFF==

* To switch the device on: Press and hold POWER until the boot logo appears.
* To enter the "normal" (NAND) boot menu: Press and hold POWER, one second later press and hold AUX.
* To enter the "rescue" (NOR) boot menu: Press and hold AUX, then press and hold POWER.

==Mode: ON==

* To suspend the device: Press POWER.
* To shut down the device: Press and hold POWER for 4 seconds. If the device hangs, press and hold POWER for 8 seconds. If it still hangs, remove the battery and disconnect from USB.
* To go to the home screen: Press AUX.
* To display the profile screen: Press and hold AUX until it appears.

==Mode: SUSPEND==

* To wakeup the device: Press POWER.

=Basic LED Usage=

LEDs are very useful in broadcasting valuable basic status information to the user in a way that the user does not have to unlock the device, enable the screen or turning the screen saver off and subsequently search the screen for basic status information.

''This is grouped by mode:''

==Mode: OFF==

* All LEDs will be turned off.

==Mode: ON==

* HEARTBEAT will emit a short blink every 4 seconds.
* If Bluetooth is powered on, WIRELESS will emit a short blink every 2 seconds.
* If Wifi is powered on, WIRELESS will emit a long blink every 2 seconds.
* If Bluetooth and Wifi are powered on, WIRELESS will be lit continuosly.

==Mode: ON+CHARGING==

''Same as ON, with the exception of''
* HEARTBEAT will increase blinking as the charge level of the battery increases.
* HEARTBEAT will be continuosly lit, if the battery has been fully charged.

==Mode: SUSPEND==

* All LEDs will be turned off.

=Advanced Button/LED Usage=

* In ON-Mode, EVENT will blink every 2 seconds if there's an event that needs your attention.
* The more events, the faster EVENT will blink.
* Pressing AUX will acknowledge the event with the topmost priority and display it to you.
* EVENT will stop to blink once all events have been acknowledged.

=A first rules implementation=
A C implementation of these rules has been [http://lists.openmoko.org/pipermail/openmoko-devel/2008-July/003458.html done by smurfy - phil] and is available at http://www.smurfy.de/files/neo/openmoko-led-v1.tar.gz

=Python Script For Blinking Leds By Beats=
Reads beats from a file and blinks FreeRunners leds.

File format is human readable text, consisting of a simple sequence of integer quartet (4 numbers). The first number representing status of blue power-led, second means status of orange power-led and third means status of red aux-led. 0=OFF, 1=ON. (If blue=1 and orange=1 then power=lila. This has nothing to do with this python script or this file format.) The last number represents the duration in milliseconds to hold that situation of leds. Any non digit characters in the file count as a separators between numbers, but are otherwise ignored.

It requires packages python-core and python-re from opkg.
==== Led blinker ====

#!/usr/bin/python
"""Led Blinker Player

Usage: python leds.py [filename]
"""
import sys
import time
import re

def loadFromTextFile(filename):
infile = open(filename)
contents = infile.read()
return re.findall("(\d+)\D*(\d+)\D*(\d+)\D*(\d+)", contents)

def playNote(blue_value, orange_value, red_value, duration):
blue.write(str(blue_value) + "\n")
orange.write(str(orange_value) + "\n")
red.write(str(red_value) + "\n")
time.sleep(float(duration) / 1000.0)

def playFile(filename):
global blue, orange, red
notes = loadFromTextFile(filename)
blue = open("/sys/class/leds/gta02-power:blue/brightness", "w", 1)
orange = open("/sys/class/leds/gta02-power:orange/brightness", "w", 1)
red = open("/sys/class/leds/gta02-aux:red/brightness", "w", 1)

for first,second,third, duration in notes:
playNote(first,second,third,duration)

playNote(0, 0, 0, 0)
blue.close()
orange.close()
red.close()

if __name__ == "__main__":
playFile(sys.argv[1])

==== Example Beat ====
The following is an example "fireworks"-file that can be used to test the led blinker.

1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100
1 0 0 100
1 0 1 100
1 1 0 100
0 1 0 100
0 1 1 100
0 0 1 100
1 1 1 100

[[Category:Neo FreeRunner Hardware]]

Video Player

2008-09-01T02:58:59Z

Treviño:

Not a proper 'app' page, just an overview

=FreeRunner=
It plays mpeg-4 320x240 stretched fullscreen, however other formats will require transcoding.

==Playback==
The default media player doesn't seem to handle video very well, but mplayer does OK.

=== Using standard Mplayer ===
It can be installed with the following command:
opkg install mplayer

=== Using the Glamo XV acceleration ===
TBD, refer to: http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/

=== Controlling MPlayer from the Touchscreen ===
Create a file in /home/root/.mplayer/input.conf with this content:
# Freerunner Optimizations
MOUSE_BTN0 vo_fullscreen
MOUSE_BTN0_DBL q
Now, you can toggle the fullscreen by tapping the screen and exit from mplayer by touble-tapping the LCD.
Accelerometers or hardware buttons could help more.

=== Playback helper script ===

Create a script named 'vidplay' in your home directory with the following commands:
#!/bin/sh
xrandr -display :0 --output default --mode 240x320
mplayer -vo fbdev "$1" > /dev/null
xrandr -display :0 --output default --mode 480x640
reset

Make the script executable:
chmod 755 /home/root/vidplay

Known issues with this approach:
*The output isn't in a proper window, so background stuff sometimes flickers through.
*When done on the local terminal the keyboard is obscured so you can't exit. SSH works quite well.
*240x320 mode has some quirks:
**The gamma/brightness/contrast is weird. Encoding adjustments into the media is a workaround.
**Vertical banding (as seen in landscape position) is quite noticeable.
*Using CTRL-C to exit vidplay doesn't reset the screen; use 'q' instead.

Despite these issues, it proves that the horsepower is there and it can be done.

=== Another derivated method : works like a charm for me ! ===
No ssh, no xrandr, no script needed, juste mplayer and qwerty keyboard :
Like it's said in the "Getting started with FreeRunner" wiki page, you have to install the full qwerty keyboard, see [http://www.ginguppin.de/node/15 these instructions].
After that, you can go to Terminal and type :
mplayer vid/my_video.avi
Mplayer starts in full screen, if your video is optimized like below 240x320 it's work like a charm and to quit just use the power button.

Only issue : You can't forward/backward/pause...

==Example - Big Buck Bunny==
===PC===
Download the source (no need to start with the giant full resolution version)
cd /tmp
wget http://mirror.botux.net/pub/peach.blender/psp/big_buck_bunny_480p_AVC_FW33.mp4

Transcode it
mencoder big_buck_bunny_480p_AVC_FW33.mp4 -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=720:480:0:0,rotate=2,scale=-2:320,eq=1.2:0.5:-0.25 -oac mp3lame -lameopts br=64:cbr -o big_buck_bunny_320.avi

=== FreeRunner===
Transfer the resulting 27M file from the PC to the FreeRunner's MicroSD card
scp user@192.168.0.200:/tmp/big_buck_bunny_320.avi /media/card

Play it
/home/root/vidplay /media/card/big_buck_bunny_320.avi

Now go outside and play; you've been spending too much time at the computer.
==Other Info==

To rotate the screen:
xrandr -o 0
xrandr -o 1

=Neo1973=

Video is problematic on [[Neo 1973]].

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

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

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

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

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

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

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

With sound, this drops to 18fps.

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

==Playback using 480x640 / 640x480==

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

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

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

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

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

[[Category:Openmoko]]

Backup

2008-08-31T23:36:15Z

Treviño: /* Backing up everything */

== Backing up just /home/root ==

To backup the home folder (all your files 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 bellow)
* 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 ===

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 NRF 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:

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

=== Backing-up flash images (alternative) ===

On the device:
mkdir /var/tmp/root
mount /dev/root /var/tmp/root

On your workstation:
ssh root@192.168.0.202 "mkfs.jffs2 -d /var/tmp/root -e 128 --pad --no-cleanmarkers" | pv -W > rootfs.jffs2
(The "| pv -W" is optional, it just gives you something to watch as the bytes fly by.)

On the device:
umount /var/tmp/root

=== 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 is 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/Pre-Flash_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>
[[category:Guides]]
[[category:Technical]]

Toolchain

2008-07-29T18:35:20Z

Treviño: /* Installing additional libraries into the toolchain */

{{Languages|Toolchain}}

= Introduction =

A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:

== Developing a single application ==

For this, you should use a prebuilt toolchain from the Openmoko project. Here you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. You might have heard about [[OpenEmbedded]], however as an application programmer, you should '''not''' be using [[OpenEmbedded]].

== System Integration and customizing a distribution ==

For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.

=Basic toolchain usage=

==Prerequisites==

You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.

Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').

A (partial) list of required packages -- please append as necessary:

* For most Linux version you might only need to install the packages
** autoconf, automake
** binutils, gcc, gcc-c++
** libtool
** ccache
** intltool

* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev \
ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools

* For Fedora-Core the following is required, while logged in as <tt>root</tt>:
yum install gcc gcc-c++ autoconf automake binutils libtool glib2-devel \
ccache libXrender-devel intltool GConf2-devel mtools
Fedora-Core does not appear to have <tt>libmokoui2</tt> available.

==Downloading and installing==

{{Note|Debian and Ubuntu i386 users (or others who can install a .deb) may wish to skip the below and instead use:
[http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html Openmoko application development in 5 minutes] by Andreas Dalsgaard.}}

The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/toolchains downloads.openmoko.org]:

* Creating a destination directory can be anywhere, but for example:

mkdir ~/sources
cd ~/sources

* Depending on your CPU type (x86_64 or i686) download the proper package:

wget http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
or
wget http://downloads.openmoko.org/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2

{{Note|Several people have had problems with the latest toolchain built 20080521. If you experience errors, try an older version. (as of July 23, 2008)}}

Next, you want to extract it on your filesystem. This toolchain is ''not'' relocatable, it needs to be installed into <tt>/usr/local/openmoko/</tt>.
Now you have the following options:

* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):

cd /
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2

* On Debian-based systems, you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:

bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2
gzip openmoko-*-arm-linux-gnueabi-toolchain.tar
fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz
sudo dpkg -i openmoko_*-arm-linux-gnueabi-toolchain*.deb

* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE:

bitbake meta-toolchain-openmoko

Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to source it.
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need
to start "sh" or "bash" first.

. /usr/local/openmoko/arm/setup-env

* At least, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make).

==Building OpenMoko Kernel from git repo using Toolchain==

git clone git://git.openmoko.org/git/kernel.git linux-2.6
cd linux-2.6
git checkout origin/stable
cp defconfig-gta02 .config
./build

Will fail with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"

to:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"

==Building a sample project==

In a chosen destination directory (in this example ~/):

* copy the downloaded sample application source:

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:

. /usr/local/openmoko/arm/setup-env

* You need to create a build configuration for this application. This also checks if all needed libraries, tools, etc.. is available on your system. If this fails see the notes about the needed packages in the section "Prerequisites" mentioned earlier.

om-conf openmoko-sample2

* Optionally now you can modify the source code in openmoko-sample2/src. Before the next step, go into the sample directory.

cd openmoko-sample2

* If you are using an older version of the toolchain, you may have to create the makefile by running "./autogen.sh". Otherwise, to build the application from the source code just type:

make

* If there are errors (i.e. "You need to install gnome-common from the GNOME CVS") deal with them. Also see "Troubleshooting" section at the end of this page for known issues.

If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.
om-conf --prefix=/usr/local/openmoko openmoko-sample2
cd openmoko-sample2
make install

==How to modify the sample project==

In order to build your own project by using openmoko-sample2 files, some changes are needed:

* copy the downloaded sample application source

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* rename the folder with the name of your project (in this example your-project-name) and delete old sample files

mv openmoko-sample2 your-project-name
cd your-project-name
cd src
rm *.c

* copy your sources (in this example your-sources) into src/

cp your-sources .
cd ..

* now in the main folder modify autogen.sh by updating the following lines

PKG_NAME="your-project-name"

* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)

AC_INIT(your-project-name, 0.0.1, http://www.openmoko.org/)
AC_CONFIG_SRCDIR(src/main.c)

* go into data/ folder and rename these files with the name of your project

cd data
mv openmoko-sample.png your-project-name.png
mv openmoko-sample.desktop your-project-name.desktop

* modify Makefile.am inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify Makefile.in inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify your-project-name.desktop by updating the following lines

Name=your-project-name
Encoding=UTF-8
Version=0.0.1
Type=Application
Exec=your-project-name

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

bin_PROGRAMS = your-project-name
your_project_name_SOURCES = \
main.c
your_project_name_LDADD = @DEPENDENCIES_LIBS@

* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names

==Packaging your application==

We have included a script to make an ipkg out of your application. Note that this is not needed to test your application on the Neo (for that you can just scp the resulting binary and data over), however it's very handy if you want to distribute your application to others.

om-make-ipkg openmoko-sample2

Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your
Neo and install it:

scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:
ssh root@192.168.0.202 opkg install openmoko-sample2_0.1_armv4t.ipk

Note that while you can redistribute the generated ipkg, be aware that this is a bare-bones ipk that contains no further information, i.e. you will lack library dependencies. See below how to fix this.

You can also supply the version number, a description, and an author / contacts string in a control file:

om-make-ipkg myapp myapp_control

A template of myapp_control:

Package: $appname
Version: 0.1
Description: package built by openmoko toolchain
Section: openmoko/applications
Priority: optional
Maintainer: $USER
Architecture: armv4t
Homepage: http://www.openmoko.org/
Depends:
Source: ${SRC}

==Where to go from here==

Using the external toolchain is an easy way to build applications for your Neo. If you are familiar with this procedure, you might also want to look into
* Using [[Qemu]] to test your applications in an emulated environment
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency
* Using [[OpenEmbedded]] to customize your Openmoko distribution image

=Advanced topics=
==Using toolchain provided libraries==
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

Sooner or later you will want to compile an application that has dependencies which can't be fulfilled by the precompiled toolchain, e.g. some obscure libraries.

In that case, feel free to request the inclusion of additional libraries into the next release of the OpenMoko toolchain. Until then, here is how you enhance your already installed toolchain. Say, we want to add the library called liburiparse:

cd ~/source
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2
./configure --host=arm-angstrom-linux-gnueabi \
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr
make
make install

That's it.

==Getting your application packaged by OE==

If you have written a cool application which you want to share with others, the best way to do that is to

# upload your application source code to a public location
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

* Some Versions of the Toolchain have corrupt .la files. If you compile an application using the Toolchain and you receive a '/space/fic/openmoko-daily/neo1973/work/armv4t-angstrom-linux-gnueabi/pango-1.18.3-r0/pango-1.18.3/pango/libpangoft2-1.0.la' error, you are affected. To fix that you should go to your "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib" directory and open the affected .la files and change "/space/fic..." to "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib". You have to fix more than one .la file. For the pango error you have to change "libpangocairo-1.0.la", but there are more corrupt .la files.

* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.

[[Category:Application Developer]]

Toolchain

2008-07-29T17:30:40Z

Treviño: /* Building a sample project */

{{Languages|Toolchain}}

= Introduction =

A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:

== Developing a single application ==

For this, you should use a prebuilt toolchain from the Openmoko project. Here you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. You might have heard about [[OpenEmbedded]], however as an application programmer, you should '''not''' be using [[OpenEmbedded]].

== System Integration and customizing a distribution ==

For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.

=Basic toolchain usage=

==Prerequisites==

You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.

Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').

A (partial) list of required packages -- please append as necessary:

* For most Linux version you might only need to install the packages
** autoconf, automake
** binutils, gcc, gcc-c++
** libtool
** ccache
** intltool

* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev \
ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools

* For Fedora-Core the following is required, while logged in as <tt>root</tt>:
yum install gcc gcc-c++ autoconf automake binutils libtool glib2-devel \
ccache libXrender-devel intltool GConf2-devel mtools
Fedora-Core does not appear to have <tt>libmokoui2</tt> available.

==Downloading and installing==

{{Note|Debian and Ubuntu i386 users (or others who can install a .deb) may wish to skip the below and instead use:
[http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html Openmoko application development in 5 minutes] by Andreas Dalsgaard.}}

The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/toolchains downloads.openmoko.org]:

* Creating a destination directory can be anywhere, but for example:

mkdir ~/sources
cd ~/sources

* Depending on your CPU type (x86_64 or i686) download the proper package:

wget http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
or
wget http://downloads.openmoko.org/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2

{{Note|Several people have had problems with the latest toolchain built 20080521. If you experience errors, try an older version. (as of July 23, 2008)}}

Next, you want to extract it on your filesystem. This toolchain is ''not'' relocatable, it needs to be installed into <tt>/usr/local/openmoko/</tt>.
Now you have the following options:

* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):

cd /
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2

* On Debian-based systems, you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:

bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2
gzip openmoko-*-arm-linux-gnueabi-toolchain.tar
fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz
sudo dpkg -i openmoko_*-arm-linux-gnueabi-toolchain*.deb

* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE:

bitbake meta-toolchain-openmoko

Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to source it.
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need
to start "sh" or "bash" first.

. /usr/local/openmoko/arm/setup-env

* At least, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make).

==Building OpenMoko Kernel from git repo using Toolchain==

git clone git://git.openmoko.org/git/kernel.git linux-2.6
cd linux-2.6
git checkout origin/stable
cp defconfig-gta02 .config
./build

Will fail with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"

to:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"

==Building a sample project==

In a chosen destination directory (in this example ~/):

* copy the downloaded sample application source:

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:

. /usr/local/openmoko/arm/setup-env

* You need to create a build configuration for this application. This also checks if all needed libraries, tools, etc.. is available on your system. If this fails see the notes about the needed packages in the section "Prerequisites" mentioned earlier.

om-conf openmoko-sample2

* Optionally now you can modify the source code in openmoko-sample2/src. Before the next step, go into the sample directory.

cd openmoko-sample2

* If you are using an older version of the toolchain, you may have to create the makefile by running "./autogen.sh". Otherwise, to build the application from the source code just type:

make

* If there are errors (i.e. "You need to install gnome-common from the GNOME CVS") deal with them. Also see "Troubleshooting" section at the end of this page for known issues.

If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.
om-conf --prefix=/usr/local/openmoko openmoko-sample2
cd openmoko-sample2
make install

==How to modify the sample project==

In order to build your own project by using openmoko-sample2 files, some changes are needed:

* copy the downloaded sample application source

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* rename the folder with the name of your project (in this example your-project-name) and delete old sample files

mv openmoko-sample2 your-project-name
cd your-project-name
cd src
rm *.c

* copy your sources (in this example your-sources) into src/

cp your-sources .
cd ..

* now in the main folder modify autogen.sh by updating the following lines

PKG_NAME="your-project-name"

* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)

AC_INIT(your-project-name, 0.0.1, http://www.openmoko.org/)
AC_CONFIG_SRCDIR(src/main.c)

* go into data/ folder and rename these files with the name of your project

cd data
mv openmoko-sample.png your-project-name.png
mv openmoko-sample.desktop your-project-name.desktop

* modify Makefile.am inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify Makefile.in inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify your-project-name.desktop by updating the following lines

Name=your-project-name
Encoding=UTF-8
Version=0.0.1
Type=Application
Exec=your-project-name

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

bin_PROGRAMS = your-project-name
your_project_name_SOURCES = \
main.c
your_project_name_LDADD = @DEPENDENCIES_LIBS@

* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names

==Packaging your application==

We have included a script to make an ipkg out of your application. Note that this is not needed to test your application on the Neo (for that you can just scp the resulting binary and data over), however it's very handy if you want to distribute your application to others.

om-make-ipkg openmoko-sample2

Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your
Neo and install it:

scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:
ssh root@192.168.0.202 opkg install openmoko-sample2_0.1_armv4t.ipk

Note that while you can redistribute the generated ipkg, be aware that this is a bare-bones ipk that contains no further information, i.e. you will lack library dependencies. See below how to fix this.

You can also supply the version number, a description, and an author / contacts string in a control file:

om-make-ipkg myapp myapp_control

A template of myapp_control:

Package: $appname
Version: 0.1
Description: package built by openmoko toolchain
Section: openmoko/applications
Priority: optional
Maintainer: $USER
Architecture: armv4t
Homepage: http://www.openmoko.org/
Depends:
Source: ${SRC}

==Where to go from here==

Using the external toolchain is an easy way to build applications for your Neo. If you are familiar with this procedure, you might also want to look into
* Using [[Qemu]] to test your applications in an emulated environment
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency
* Using [[OpenEmbedded]] to customize your Openmoko distribution image

=Advanced topics=
==Using toolchain provided libraries==
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

Sooner or later you will want to compile an application that has dependencies which can't be fulfilled by the precompiled toolchain, e.g. some obscure libraries.

In that case, feel free to request the inclusion of additional libraries into the next release of the OpenMoko toolchain. Until then, here is how you enhance your already installed toolchain. Say, we want to add the library called liburiparse:

cd ~/source
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2
./configure --host=arm-angstrom-linux-gnueabi \
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/
make
make install

That's it.

==Getting your application packaged by OE==

If you have written a cool application which you want to share with others, the best way to do that is to

# upload your application source code to a public location
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

* Some Versions of the Toolchain have corrupt .la files. If you compile an application using the Toolchain and you receive a '/space/fic/openmoko-daily/neo1973/work/armv4t-angstrom-linux-gnueabi/pango-1.18.3-r0/pango-1.18.3/pango/libpangoft2-1.0.la' error, you are affected. To fix that you should go to your "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib" directory and open the affected .la files and change "/space/fic..." to "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib". You have to fix more than one .la file. For the pango error you have to change "libpangocairo-1.0.la", but there are more corrupt .la files.

* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.

[[Category:Application Developer]]

Toolchain

2008-07-29T16:44:58Z

Treviño: /* Building a sample project */

{{Languages|Toolchain}}

= Introduction =

A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:

== Developing a single application ==

For this, you should use a prebuilt toolchain from the Openmoko project. Here you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. You might have heard about [[OpenEmbedded]], however as an application programmer, you should '''not''' be using [[OpenEmbedded]].

== System Integration and customizing a distribution ==

For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.

=Basic toolchain usage=

==Prerequisites==

You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.

Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').

A (partial) list of required packages -- please append as necessary:

* For most Linux version you might only need to install the packages
** autoconf, automake
** binutils, gcc, gcc-c++
** libtool
** ccache
** intltool

* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev \
ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools

* For Fedora-Core the following is required, while logged in as <tt>root</tt>:
yum install gcc gcc-c++ autoconf automake binutils libtool glib2-devel \
ccache libXrender-devel intltool GConf2-devel mtools
Fedora-Core does not appear to have <tt>libmokoui2</tt> available.

==Downloading and installing==

{{Note|Debian and Ubuntu i386 users (or others who can install a .deb) may wish to skip the below and instead use:
[http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html Openmoko application development in 5 minutes] by Andreas Dalsgaard.}}

The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/toolchains downloads.openmoko.org]:

* Creating a destination directory can be anywhere, but for example:

mkdir ~/sources
cd ~/sources

* Depending on your CPU type (x86_64 or i686) download the proper package:

wget http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
or
wget http://downloads.openmoko.org/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2

{{Note|Several people have had problems with the latest toolchain built 20080521. If you experience errors, try an older version. (as of July 23, 2008)}}

Next, you want to extract it on your filesystem. This toolchain is ''not'' relocatable, it needs to be installed into <tt>/usr/local/openmoko/</tt>.
Now you have the following options:

* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):

cd /
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2

* On Debian-based systems, you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:

bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2
gzip openmoko-*-arm-linux-gnueabi-toolchain.tar
fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz
sudo dpkg -i openmoko_*-arm-linux-gnueabi-toolchain*.deb

* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE:

bitbake meta-toolchain-openmoko

Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to source it.
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need
to start "sh" or "bash" first.

. /usr/local/openmoko/arm/setup-env

* At least, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make).

==Building OpenMoko Kernel from git repo using Toolchain==

git clone git://git.openmoko.org/git/kernel.git linux-2.6
cd linux-2.6
git checkout origin/stable
cp defconfig-gta02 .config
./build

Will fail with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"

to:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"

==Building a sample project==

In a chosen destination directory (in this example ~/):

* copy the downloaded sample application source:

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:

. /usr/local/openmoko/arm/setup-env

* You need to create a build configuration for this application. This also checks if all needed libraries, tools, etc.. is available on your system. If this fails see the notes about the needed packages in the section "Prerequisites" mentioned earlier.

om-conf openmoko-sample2

* Optionally now you can modify the source code in openmoko-sample2/src. Before the next step, go into the sample directory.

cd openmoko-sample2

* If you are using an older version of the toolchain, you may have to create the makefile by running "./autogen.sh". Otherwise, to build the application from the source code just type:

make

* If there are errors (i.e. "You need to install gnome-common from the GNOME CVS") deal with them. Also see "Troubleshooting" section at the end of this page for known issues.

If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.

PKG_CONFIG_PATH="PKG_CONFIG_PATH:/usr/lib/pkgconfig" om-conf --prefix=/usr/local/openmoko openmoko-sample2
cd openmoko-sample2
make install

==How to modify the sample project==

In order to build your own project by using openmoko-sample2 files, some changes are needed:

* copy the downloaded sample application source

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* rename the folder with the name of your project (in this example your-project-name) and delete old sample files

mv openmoko-sample2 your-project-name
cd your-project-name
cd src
rm *.c

* copy your sources (in this example your-sources) into src/

cp your-sources .
cd ..

* now in the main folder modify autogen.sh by updating the following lines

PKG_NAME="your-project-name"

* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)

AC_INIT(your-project-name, 0.0.1, http://www.openmoko.org/)
AC_CONFIG_SRCDIR(src/main.c)

* go into data/ folder and rename these files with the name of your project

cd data
mv openmoko-sample.png your-project-name.png
mv openmoko-sample.desktop your-project-name.desktop

* modify Makefile.am inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify Makefile.in inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify your-project-name.desktop by updating the following lines

Name=your-project-name
Encoding=UTF-8
Version=0.0.1
Type=Application
Exec=your-project-name

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

bin_PROGRAMS = your-project-name
your_project_name_SOURCES = \
main.c
your_project_name_LDADD = @DEPENDENCIES_LIBS@

* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names

==Packaging your application==

We have included a script to make an ipkg out of your application. Note that this is not needed to test your application on the Neo (for that you can just scp the resulting binary and data over), however it's very handy if you want to distribute your application to others.

om-make-ipkg openmoko-sample2

Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your
Neo and install it:

scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:
ssh root@192.168.0.202 opkg install openmoko-sample2_0.1_armv4t.ipk

Note that while you can redistribute the generated ipkg, be aware that this is a bare-bones ipk that contains no further information, i.e. you will lack library dependencies. See below how to fix this.

You can also supply the version number, a description, and an author / contacts string in a control file:

om-make-ipkg myapp myapp_control

A template of myapp_control:

Package: $appname
Version: 0.1
Description: package built by openmoko toolchain
Section: openmoko/applications
Priority: optional
Maintainer: $USER
Architecture: armv4t
Homepage: http://www.openmoko.org/
Depends:
Source: ${SRC}

==Where to go from here==

Using the external toolchain is an easy way to build applications for your Neo. If you are familiar with this procedure, you might also want to look into
* Using [[Qemu]] to test your applications in an emulated environment
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency
* Using [[OpenEmbedded]] to customize your Openmoko distribution image

=Advanced topics=
==Using toolchain provided libraries==
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

Sooner or later you will want to compile an application that has dependencies which can't be fulfilled by the precompiled toolchain, e.g. some obscure libraries.

In that case, feel free to request the inclusion of additional libraries into the next release of the OpenMoko toolchain. Until then, here is how you enhance your already installed toolchain. Say, we want to add the library called liburiparse:

cd ~/source
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2
./configure --host=arm-angstrom-linux-gnueabi \
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/
make
make install

That's it.

==Getting your application packaged by OE==

If you have written a cool application which you want to share with others, the best way to do that is to

# upload your application source code to a public location
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

* Some Versions of the Toolchain have corrupt .la files. If you compile an application using the Toolchain and you receive a '/space/fic/openmoko-daily/neo1973/work/armv4t-angstrom-linux-gnueabi/pango-1.18.3-r0/pango-1.18.3/pango/libpangoft2-1.0.la' error, you are affected. To fix that you should go to your "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib" directory and open the affected .la files and change "/space/fic..." to "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib". You have to fix more than one .la file. For the pango error you have to change "libpangocairo-1.0.la", but there are more corrupt .la files.

* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.

[[Category:Application Developer]]

Import Vcf Contacts

2008-07-27T03:02:14Z

Treviño: /* Import for ASU/Qtopia */

== Import for 2007.2 ==
=== Basic Informations ===

Neo FreeRunner uses Evolution data server (eds) to save contacts.
However, the specific version used differs from what is probably used on your desktop (if you have Evolution installed).

You ''cannot'' copy your addressbook.db from your desktop to Neo ([http://docs.openmoko.org/trac/ticket/1119 bug 1119]).

=== Import and Manage Scripts ===

If you want to import your old contacts to the Neo you could use this script:

[http://www.smurfy.de/files/neo/manage-contacts Manage Contacts script] [http://www.placard.fr.eu.org/~roland/tmp/manage-contacts.py mirror]

If you first want to remove all existing contacts you could use this script.

[http://www.smurfy.de/files/neo/remove_all_contacts remove all script]

If you have all contacts in seperate vcf files and just want to import all at once:

[http://www.smurfy.de/files/neo/ac Simple script]

[http://www.smurfy.de/files/neo/import_contacts Simple script for one big contactsfile]

(please add a .py after the filename, sorry my hoster gives an error if i link to .py files, even .py.txt)

=== Exporting old contacts to VCard format ===

To use the manage Script you need your Contacts in VCF format.

# on nokia phones i used the nokia phone manager (long time ago)
# on windows mobile phones you could use active sync to sync with Outlook and then use a Outlook export plugin to export as vcf
# on lg phones the backup function to memory card creates one file with multiple VCards.

=== Usage ===

The script is for the 2007.2 Version (default install on Neo FreeRunner), not for Qtopia

You need Python to use this script so do a

opkg install python-dbus

to install python and the python dbus module

==== Manage Contacts Script ====

'''This script needs all contacts in one big file'''

'''You also could run this script on a ssh session!'''

# Copy your big contacts file (contacts.txt) to your Neo
# Copy script to your Neo
# Connect via ssh to your Neo
# Fix special chars in your contacts file with you favorite text editor
# To import the file run on the SSH shell:

python manage-contacts.py load < contacts.txt

# For a backup your existing contacts on the Neo

python manage-contacts.py dump > contacts.txt

==== Simple Script ====

'''You must run the script in the OM Terminal, not over ssh'''

The script does a listdir and imports ALL files it found in that dir. (i'm a bad python programmer)

# Copy all vcf files to a separate directory on my freerunner
# Copy the ac script to the parent directory also on my freerunner
# Have the contacts program running (so you have eds running too)
# Go to the terminal on the freerunner and type in the vcf directory: "python ../ac" (root@om-gta02:~/vcf# python ../ac)
## Note: '''You must call the script in the OM terminal''' not via Bluetooth or USB or you get a dbus error.
# Done :D

==== Troubleshooting ====
* Make sure you have python and python-dbus installed
* Make sure you have no illegal chars (utf) in the filename and inside the vcf files. (I had problems with Ü,Ä etc)
** The characters seem to work if you convert them from =C3=A4 type of format to proper UTF-8, and the vcards also specify UTF-8 charset. you cannot use other charsets besides UTF-8 since they are delivered via DBus which does not allow others.
* Only vcf files should be in your current directory so do a ../ac.
* You must call the script in the OM terminal not via Bluetooth or USB. If you do so a dbus error occur

=== Authors ===
* Simple script by smurfy - phil <openmoko at smurfy.de>
* Manage Contacts script by Roland Mas <lolando at debian.org>
* Remove all Contacts script / simple script for one big file by Andreas Dalsgaard <andreas.dalsgaard at gmail.com>

Thanks to [[Import_Sim_Contacts]] for the original Python Script.

== Import for ASU/Qtopia ==
The Qtopia addressbook application suports import of VCF files out of the box:
LD_LIBRARY_PATH=/opt/Qtopia/lib /opt/Qtopia/bin/addressbook /home/root/addressbook.vcf

You will be asked if you want to import the contacts form addressbook.vcf (the contact name will be taken from the "N:" vCard field).

[[category:Openmoko]]
[[category:Documentation]]

GPS Problems

2008-07-16T01:45:25Z

Treviño: /* Possible SD Card Issue */

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

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

--[[User:Pthorin|Pthorin]] 05:11, 11 July 2008 (UTC) I tried it out once again after removing the front cover and got a fix quite fast, less than five minutes. Could there be an issue with the case blocking the signals? Could the snap/latch above the antenna be a problem?
|-
|iandouglas ||Yes|| No ||Spent over a half hour outdoors, the NMEA port on my Samsung Blackjack 2 found my position just fine, but also got the same 99.99,99.99,99.99*30 line as Pthorin when powering on the GPS unit, starting gpsd, then running gpspipe at the command line
|-
| genki || Yes || Yes || Same here. Does not get a fix without external antenna. GPS output is 99.99,99.99,99.99*30 as well
|-
| Ole || Yes || Yes || Tried 15min outside w/o external antenna. Did not get any activity on the SS tab. With external antenna from my window TTFS 33s. ||
|-
| Adsllc || Yes || No || Tried 15min outside one night. Got UTC time and a couple of satellites on the SS tab, but no fix. Reseated the GPS connector, still had no luck. Later I set it outside, did other stuff for 30 mins or so, then came back to see a successful fix and all tabs in the OM AGPS UI app working. Worked fine on a trip to the post office. Tried again later, no joy.

Tried another day - left it outside propped upright against the luggage rack of the car for 15 minutes+; zero satellites on AGPS UI. Picked it up, pressed "run" then "Cold reset". BAM - it saw its first satellite about 10 seconds later. It still took around 5 minutes to get a fix, but it's a lot better than nothing.

I was doing a lot of screwing around before my first success (which did involve a Cold reset), so it's hard to assign causation. The second time seemed to be pretty solid cause/effect.

If anyone confirms this as a fix/workaround, please make it more prominent on this page.
|-
| Bumbl || Yes || No || Tried outside and never got to see a single satellite. I even went on the highest point nearby but it got no satellite although I tried for 45min.
|-
|Dummy ||?|| ? ||
|-
| Sitwon || Yes || No || Tried three different times in two different locations. Followed all the advice I could find on wiki & lists. Left it pointed up for 30-45min and have never gotten a single satellite to connect. :,(

Edit: Tried again w/ no MicroSD card, TTFF=21s indoors.
|-
| banahogg || Yes || No || Left pointed up in a mug as recommended. After ~30min, one satellite showed up in signal screen. Three after 60min, but no lock. Three other GPS systems locked on from the same location in at most 10 minutes.
|}

{|border="3"
|+'''Success stories'''
!Username||Checked outside?||External antenna?||Note
|-
|[[User:TimoJyrinki|timo]] || Yes || No || 11-07: Spent over a half hour outdoors in an open area without nearby buildings. Zero good fixes, no time gotten, GPS output scrolled along with same numbers for the whole time. When I played some more, very rarely I noticed that in the AZ tab a satellite blob had appeared, always at 0 degrees at the top of the picture. But still no fixes at all or anything. [postscript: I probably moved around a bit, ie. had Neo in my hand]
''12-07 update'': Was able to get a fix in (completely) another location. Looks like the signal may be non-existent in many situations even in seemingly very open places, and together with the shaky software it may be sometimes really hard to say if there is a hw problem...

''13-07 update'': Enabled the assistive data for the GPS, didn't touch to AGPS UI which always clears all data, got a fix in just a couple of minutes (maybe less, didn't look) and the fix stayed completely properly for the duration of my car trip. If someone codes also "agps daemon" to support Neo by saving data before gps chip is turned off, this'd be just great (considering the small antenna etc.).
|}

== Solved problems ==

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

=== Basic GPS debugging ===

It could be that your GPS device is functioning properly, but needs to be "coaxed" into getting an initial fix.

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

* However, you might not obtain a lock if the orientation or position of your phone continuously changes. It needs to be stationary long enough to download a frame of data from one of the satellites. Frames are 1500 bits and take 30 seconds to broadcast. The first 6 seconds of the frame contains clock data; the remainder describes the satellite position. Downloading this data can take a surprisingly long time for two reasons.
*# The GPS reception is sensitive to the orientation of the phone. When you move the phone, it can corrupt part of the current frame.
*# GPS signals reflect off buildings, interfering with reception in seemingly random ways. If local objects cause signal reflections between you and the satellites, the data may repeatedly fail to download; try facing a different direction (and then holding still) after a few minutes without a lock.
* Is your unit obtaining signal at all? Check using the AGPS test program "Openmoko AGPS UI". Click "Power On" to begin the test.
** The "ss" button lists satellites and signal strengths; pressing the "dBm" or "C/N0" button at the bottom of the screen cycles through different scales; a signal between 130dBM and 150dBm should be adequate for a lock, assuming the Neo obtains a consistent signal (lower numbers / taller bars are better).
** It may take a few minutes for the first satellite to appear in this display. You'll need multiple satellite signals to get a lock.
** Before getting a lock, the "UTC" field in the "run" tab should start displaying the current time. This value is obtained via the GPS antenna; it may take a few minutes for this field to become populated.

Finally, there is probably room for improvement in the way GPS fixes are currently obtained. GPS devices can obtain fixes at least three different ways. The least sophisticated method downloads a set of current satellite orbits by downloading frames. If part of a frame is corrupted, the GPS device must wait 30 seconds for it to be retransmitted.

A slightly more sophisticated approach uses an initial estimate of the current time and your position to obtain a lock more quickly. Finally, instead of downloading orbit and position data from the satellites, some modern GPS devices simply recalculate the information locally. Some (or all?) of these optimizations are supported by the Freerunner's GPS device, though the software installed at the factory does not seem to make use of them.

==== More Info to get a fix ====
I'd like to stress what is written above, it really helped. I put my FR on a table outside, standing vertically with something to hold it upright, switched to the SS display, clicked the db button, waited about 2 mins to get a bar, then turned it around its vertical axis slowly watching the bar go up and down. When it was facing the right way for a maximum bar length I left it like this, without touching it for about 10 mins, and it was able to find the other satellites and get a fix. It is important to not touch it or move it once it gets the first satellite. However it did lock up solid after about 30 minutes, and power button did not reset, needed to remove the battery which of course lost the fix.

==== Comment on possible software solution ====

I tested the FR outside with internal antenna and did not see a single sat for
15min. With external antenna I have a TTFS of 33s.
If I plug out the external after the fix is stable,
it almost instantly gets lost.
I still see one to three sats but get no fix.

So apparently the information obtain through the external antenna
is not enough to assist the internal antenna in getting a fix.
Orbit and positon data should be known to the device by then?
If you download this data from the internet or recalculate it locally,
in what way would this be superior to what I tested?

=== Information about faulty antennas ===

* If you list your problems above, note if you've tried unplugging and replugging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this may differ on freerunner, pictures appreciated)
Also note that there is a trac ticket for this issue: [http://docs.openmoko.org/trac/ticket/1542 #1542]

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

=== MicroSD Card Issue ===

[http://lists.openmoko.org/pipermail/community/2008-July/021774.html This thread] indicates that the problem might be interference from the SD card slot, and recommends trying without the SD card inserted. A [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003777.html software workaround] is under testing...

[[Category:GPS]]

Neo FreeRunner Hardware Issues

2008-07-16T01:43:05Z

Treviño: /* Active Issues */

This is a community-written page that discusses '''hardware issues''' with the Freerunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from [[Openmoko]] employees would be greatly appreciated.

Also please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds.

=== Active Issues ===

==== GPS Slow TTFF ====

Issue: The GPS signal is degraded to the point where the unit cannot reliably get a "cold-start" fix. See [[GPS_Problems]].

Reason #1: For some reason, the [http://lists.openmoko.org/pipermail/community/2008-July/021774.html MicroSD controller] on the Freerunner is interfering with GPS reception.

Reason #2: Poor soldering and/or mechanical deformation of the internal GPS antenna connector on some devices. See [[FreeRunner_GPS_antenna_repair_SOP]]

Affects: unknown percentage of devices

Status: [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003777.html Software workaround] found; hardware fix under investigation.

Workarounds: Remove the microSD card. Use an external GPS antenna. Supplying almanac data and approximate coordinates in software (so that the chip can perform a "warm" acquisition) may also help.

==== Poor Audio Quality ====

Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.

There are three related aspects to this issue:
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]

Affects: all devices but only some users (depending on many factors)

Status: Under investigation. There is a possibility that the quality can be made "good enough" through software (mixer settings).

Workarounds: Using a bluetooth headset is a possibility.

==== PMU/Charger Issues ====

Issue: The device may fail to turn on if the battery is deeply discharged, or may fail to charge the battery properly. See for example this thread on the [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-June/003326.html kernel list].

Affects: Unknown. Some discussions on the mailing list may refer to pre-production devices.

Status: Fixed with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here]

Workarounds: See http://lists.openmoko.org/pipermail/community/2008-July/021556.html

==== Some SIMs Don't Work ====

Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html

Recent investigations suggest that this is related to the voltage specification of the SIM - "2.9V" works while "1.8V" may have problems.

Note that there have also been a couple of reports where the failure to register was caused by an incorrectly-mounted SD card (which in turn prevented the SIM from making proper electrical contact).

Note also that there was a related issue with certain AT&T SIMs in early Neo1973 devices. The Freerunner is shipping with a newer GSM firmware in which the original Neo1973 issue has been fixed.

Affects: Only a subset of users (details unknown).

Status: Under investigation

Workarounds: It may be possible to obtain a different model of SIM from your GSM carrier.

==== Empty NOR Flash ====

Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]

Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.

Status: Unknown

Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.

==== Debug board has wrong vendor/product ID ====

Issue: A debug board is not reporting the expected USB Vendor/Product ID.

Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.

Status: Unknown

Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.

=== Known/Accepted Issues ===

This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.

* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)

=== Resolved Issues ===

These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.

* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.
* Battery life - At this time it appears that the Freerunner battery life will be acceptable once suspend/resume support has been implemented in software.

[[Category:GTA02 Hardware]]

FreeRunner: Selected Blogs and Articles

2008-07-16T01:27:47Z

Treviño: /* English */

{|align=right
|__TOC__
|}

This page contains references to personal blog entries and reflections of the mind about FreeRunner. Please see [[Press_Coverage]] for more official pieces of information.

Newest on top.

== Languages ==

=== English ===

==== July 2008 ====
* jThinks: [http://jthinks.com/index.php/freerunner-at-last/ Freerunner, at last]
* Holden's Blog: [http://blog.holdenkarau.com/2008/07/unboxing-openmokofreerunner-including.html Unboxing the OpenMoko/FreeRunner including the spares kit, debug board]
* Wolfmans Howlings: [http://blog.wolfman.com/articles/2008/07/11/openmoko-freerunner-first-impressions OpenMoko Freerunner first impressions]
* Free Software Foundation (John Sullivan): [http://www.fsf.org/blogs/community/5-reasons-to-avoid-iphone-3g 5 reasons to avoid iPhone 3G]
* Joseph Reeves: [http://blogs.thehumanjourney.net/finds/entry/20080710 FreeRunner retail unboxing]
* Ars Technica: [http://arstechnica.com/reviews/os/open-moko-software.ars Ars Technica First Look at OpenMoko]
* Juan Lucas Domínguez Rubio: [http://gvsigmobileonopenmoko.wordpress.com/2008/07/02/first-experience-with-openmoko/ First experience with Openmoko]
* Philipp Kern: [http://www.philkern.de/weblog/en/neo_freerunner.html Neo Freerunner: First impressions]

==== May 2008 ====

* Kevin Dean: [http://www.monochromementality.com/index.php/blog/show/Day-One-Openmoko-Freerunner.html Day One: Openmoko Freerunner]

==== Earlier ====
* Michael Shiloh: [http://gettingstartedopenmoko.wordpress.com/ Getting Started with OpenMoko] (many blog entries in this dedicated blog)

[[Category:Community]]

Neo FreeRunner Hardware Issues

2008-07-15T18:43:35Z

Treviño: /* PMU/Charger Issues */

This is a community-written page that discusses '''hardware issues''' with the Freerunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from [[Openmoko]] employees would be greatly appreciated.

Also please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds.

=== Active Issues ===

==== GPS Slow TTFF ====

Issue: The GPS signal is degraded to the point where the unit cannot reliably get a "cold-start" fix. See [[GPS_Problems]].

Reason #1: For some reason, the [http://lists.openmoko.org/pipermail/community/2008-July/021774.html MicroSD controller] on the Freerunner is interfering with GPS reception.

Reason #2: Poor soldering and/or mechanical deformation of the internal GPS antenna connector on some devices. See [[FreeRunner_GPS_antenna_repair_SOP]]

Affects: unknown percentage of devices

Status: Under investigation. Openmoko has not yet made an official statement regarding this problem.

Workarounds: Remove the microSD card. Use an external GPS antenna. Supplying almanac data and approximate coordinates in software (so that the chip can perform a "warm" acquisition) may also help.

==== Poor Audio Quality ====

Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.

There are three related aspects to this issue:
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]

Affects: all devices but only some users (depending on many factors)

Status: Under investigation. There is a possibility that the quality can be made "good enough" through software (mixer settings).

Workarounds: Using a bluetooth headset is a possibility.

==== PMU/Charger Issues ====

Issue: The device may fail to turn on if the battery is deeply discharged, or may fail to charge the battery properly. See for example this thread on the [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-June/003326.html kernel list].

Affects: Unknown. Some discussions on the mailing list may refer to pre-production devices.

Status: Fixed with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches]

Workarounds: See http://lists.openmoko.org/pipermail/community/2008-July/021556.html

==== Some SIMs Don't Work ====

Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html

Recent investigations suggest that this is related to the voltage specification of the SIM - "2.9V" works while "1.8V" may have problems.

Note that there have also been a couple of reports where the failure to register was caused by an incorrectly-mounted SD card (which in turn prevented the SIM from making proper electrical contact).

Note also that there was a related issue with certain AT&T SIMs in early Neo1973 devices. The Freerunner is shipping with a newer GSM firmware in which the original Neo1973 issue has been fixed.

Affects: Only a subset of users (details unknown).

Status: Under investigation

Workarounds: It may be possible to obtain a different model of SIM from your GSM carrier.

==== Empty NOR Flash ====

Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]

Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.

Status: Unknown

Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.

==== Debug board has wrong vendor/product ID ====

Issue: A debug board is not reporting the expected USB Vendor/Product ID.

Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.

Status: Unknown

Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.

=== Known/Accepted Issues ===

This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.

* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)

=== Resolved Issues ===

These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.

* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.
* Battery life - At this time it appears that the Freerunner battery life will be acceptable once suspend/resume support has been implemented in software.

[[Category:GTA02 Hardware]]

FreeRunner: Selected Blogs and Articles

2008-07-15T14:56:11Z

Treviño: /* July 2008 */

{|align=right
|__TOC__
|}

This page contains references to personal blog entries and reflections of the mind about FreeRunner. Please see [[Press_Coverage]] for more official pieces of information.

Newest on top.

== Languages ==

=== English ===

==== July 2008 ====
* Holden's Blog: [http://blog.holdenkarau.com/2008/07/unboxing-openmokofreerunner-including.html Unboxing the OpenMoko/FreeRunner including the spares kit, debug board]
* Wolfmans Howlings: [http://blog.wolfman.com/articles/2008/07/11/openmoko-freerunner-first-impressions OpenMoko Freerunner first impressions]
* Free Software Foundation (John Sullivan): [http://www.fsf.org/blogs/community/5-reasons-to-avoid-iphone-3g 5 reasons to avoid iPhone 3G]
* Joseph Reeves: [http://blogs.thehumanjourney.net/finds/entry/20080710 FreeRunner retail unboxing]
* Ars Technica: [http://arstechnica.com/reviews/os/open-moko-software.ars Ars Technica First Look at OpenMoko]
* Juan Lucas Domínguez Rubio: [http://gvsigmobileonopenmoko.wordpress.com/2008/07/02/first-experience-with-openmoko/ First experience with Openmoko]
* Philipp Kern: [http://www.philkern.de/weblog/en/neo_freerunner.html Neo Freerunner: First impressions]

==== May 2008 ====

* Kevin Dean: [http://www.monochromementality.com/index.php/blog/show/Day-One-Openmoko-Freerunner.html Day One: Openmoko Freerunner]

==== Earlier ====
* Michael Shiloh: [http://gettingstartedopenmoko.wordpress.com/ Getting Started with OpenMoko] (many blog entries in this dedicated blog)

[[Category:Community]]

Userspace root image

2008-07-14T23:24:25Z

Treviño: /* Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) */

== Creating a root filesystem from scratch ==

To create a root file system image for storage in NAND flash, we use the mkfs.jffs2 program contained in the Debian package ''mtd-tools''.

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

is a typical command. It creates a FS image for our erase block size of 16k, padded to 0x700000 bytes in length from the files contained in the ''/tmp/jffsroot'' directory and stores the FS image in ''rootfs.jffs2''.

== Using pre-created root fs image ==

=== Prebuilt ===

See [[Repositories]] and update the list if you have more information.

=== OpenEmbedded ===

OpenEmbedded will itself create a jffs2 image at the end of the build process.

Once the build server is running, it will create root filesystem images for us.

=== demo JFFS2 root image ===

Check the [[Flashing openmoko]] page for pre-built root images. Please note that this image may take long to boot the first time, since this boot finishes the installation process.

=== Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) ===
export loop=$(losetup -f)
losetup $loop <rootfs.jffs2>
modprobe block2mtd block2mtd=$loop,131072
modprobe jffs2
modprobe mtdblock
mkdir <mountpoint>
mount -t jffs2 -o ro /dev/mtdblock0 <mountpoint>

Based on this [http://www.internettablettalk.com/forums/showthread.php?p=192475#post192475 script by fanoush].

=== Mounting the JFFS2 image on a loop back device (Kernel Memory MTD Emulation) ===

As mounting the JFFS2 image from /dev/loop0 device is not supported, use the mtdram device as described in http://www.handhelds.org/hypermail/familiar/62/6232.html

(On Fedora the first module to load is mtd, not mtdcore and you need to set e.g. vmalloc=256m as a kernel boot parameter for this to work.)

modprobe mtdcore
modprobe jffs2
modprobe mtdram total_size=59024 # default is 4 MByte - set to max. available size
modprobe mtdchar
modprobe mtdblock

Using ''total_size=59024'' will set the filesystem size to the available space on /dev/mtd4 of the GTA1 device. So when you copy the image back it will be about 58 MB. You can set this to smaller values though.

Be careful to really use the mtd-ram-disk (maybe there is a real Flash-device somewhere in your development system)

So check for that looking into /proc/mtd:
cat /proc/mtd
# dev: size erasesize name
# mtd0: 039a4000 00020000 "mtdram test device"

Then write the image to that device and mount it:

dd if=<rootfs.jffs2> of=/dev/mtd0
mount -t jffs2 /dev/mtdblock0 <mountpoint>

The image is an Little Endian jffs2 image. To mount it on Big Endian architectures (like PowerPC) it'll have to be converted:

jffs2dump -l -c -e <rootfs.jffs2.be> <rootfs.jffs2> # only needed on non little endian archs

==== create the new image ====
To get the changed image back there are two ways. The obvious one is to unmount it and copy the data back from the MTD block device (the image will be 58 MB):

umount /dev/mtdblock0
dd if=/dev/mtdblock0 of=<rootfs.jffs2>

You can also create a new image using the mounted file system and the method described [[Userspace_root_image#Creating_a_root_filesystem_from_scratch | above]] (the image will have the size of its data):

mkfs.jffs2 --pad=0x700000 -o new_rootfs.jffs2 -e 0x4000 -n -d <mountpoint>

== Flashing a root filesystem into NAND ==

See [[U-boot#Writing_rootfs_to_NAND]]

== Converting a GTA02 image for GTA01 ==

The techniques on this page may be used to convert a GTA02 (Freerunner) image for use on a GTA01, provided that it is small enough to fit into the GTA01's flash.

The steps I used are shown below (corrections welcome). Please read all of this page before executing these commands, in particular the warning to make sure that /dev/mtd0 does not map to a real flash device on your system.

modprobe jffs2
modprobe mtdchar
modprobe mtdblock
modprobe mtdram erase_size=128 total_size=262144
dd if=gta02_image.jffs2 of=/dev/mtd0
mount -t jffs2 -o ro /dev/mtdblock0 /mnt
mkfs.jffs2 --little-endian -e 16 -x lzo --pad -n -r /mnt -o for_gta01.jffs2

To clean up when you're done:
umount /mnt
rmmod mtdram

{{Languages|Userspace_root_image}}
[[Category:Openmoko]]
[[Category:Guides]]

Userspace root image

2008-07-14T19:42:48Z

Treviño:

== Creating a root filesystem from scratch ==

To create a root file system image for storage in NAND flash, we use the mkfs.jffs2 program contained in the Debian package ''mtd-tools''.

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

is a typical command. It creates a FS image for our erase block size of 16k, padded to 0x700000 bytes in length from the files contained in the ''/tmp/jffsroot'' directory and stores the FS image in ''rootfs.jffs2''.

== Using pre-created root fs image ==

=== Prebuilt ===

See [[Repositories]] and update the list if you have more information.

=== OpenEmbedded ===

OpenEmbedded will itself create a jffs2 image at the end of the build process.

Once the build server is running, it will create root filesystem images for us.

=== demo JFFS2 root image ===

Check the [[Flashing openmoko]] page for pre-built root images. Please note that this image may take long to boot the first time, since this boot finishes the installation process.

=== Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) ===
losetup $(losetup -f) <rootfs.jffs2>
modprobe block2mtd block2mtd=$(losetup -f),131072
modprobe jffs2
modprobe mtdblock
mkdir <mountpoint>
mount -t jffs2 -o ro /dev/mtdblock0 <mountpoint>

Based on this [http://www.internettablettalk.com/forums/showthread.php?p=192475#post192475 script by fanoush].

=== Mounting the JFFS2 image on a loop back device (Kernel Memory MTD Emulation) ===

As mounting the JFFS2 image from /dev/loop0 device is not supported, use the mtdram device as described in http://www.handhelds.org/hypermail/familiar/62/6232.html

(On Fedora the first module to load is mtd, not mtdcore and you need to set e.g. vmalloc=256m as a kernel boot parameter for this to work.)

modprobe mtdcore
modprobe jffs2
modprobe mtdram total_size=59024 # default is 4 MByte - set to max. available size
modprobe mtdchar
modprobe mtdblock

Using ''total_size=59024'' will set the filesystem size to the available space on /dev/mtd4 of the GTA1 device. So when you copy the image back it will be about 58 MB. You can set this to smaller values though.

Be careful to really use the mtd-ram-disk (maybe there is a real Flash-device somewhere in your development system)

So check for that looking into /proc/mtd:
cat /proc/mtd
# dev: size erasesize name
# mtd0: 039a4000 00020000 "mtdram test device"

Then write the image to that device and mount it:

dd if=<rootfs.jffs2> of=/dev/mtd0
mount -t jffs2 /dev/mtdblock0 <mountpoint>

The image is an Little Endian jffs2 image. To mount it on Big Endian architectures (like PowerPC) it'll have to be converted:

jffs2dump -l -c -e <rootfs.jffs2.be> <rootfs.jffs2> # only needed on non little endian archs

==== create the new image ====
To get the changed image back there are two ways. The obvious one is to unmount it and copy the data back from the MTD block device (the image will be 58 MB):

umount /dev/mtdblock0
dd if=/dev/mtdblock0 of=<rootfs.jffs2>

You can also create a new image using the mounted file system and the method described [[Userspace_root_image#Creating_a_root_filesystem_from_scratch | above]] (the image will have the size of its data):

mkfs.jffs2 --pad=0x700000 -o new_rootfs.jffs2 -e 0x4000 -n -d <mountpoint>

== Flashing a root filesystem into NAND ==

See [[U-boot#Writing_rootfs_to_NAND]]

== Converting a GTA02 image for GTA01 ==

The techniques on this page may be used to convert a GTA02 (Freerunner) image for use on a GTA01, provided that it is small enough to fit into the GTA01's flash.

The steps I used are shown below (corrections welcome). Please read all of this page before executing these commands, in particular the warning to make sure that /dev/mtd0 does not map to a real flash device on your system.

modprobe jffs2
modprobe mtdchar
modprobe mtdblock
modprobe mtdram erase_size=128 total_size=262144
dd if=gta02_image.jffs2 of=/dev/mtd0
mount -t jffs2 -o ro /dev/mtdblock0 /mnt
mkfs.jffs2 --little-endian -e 16 -x lzo --pad -n -r /mnt -o for_gta01.jffs2

To clean up when you're done:
umount /mnt
rmmod mtdram

{{Languages|Userspace_root_image}}
[[Category:Openmoko]]
[[Category:Guides]]