Openmoko - User contributions [en]

U-Boot

2009-04-06T10:07:09Z

Noo: /* Using usbtty from Linux */

{{Languages|Bootloader}}

[[Image:GTA01-U-Boot.JPG|thumb|300px|u-boot menu on Neo1973]] [[Image:Neo1973 uboot splash closeup.jpg|thumb|300px|u-boot splash screen on Neo1973]]

The bootloader used on the smartphones is called '''U-Boot'''. It takes care of device functionality until Openmoko is booted. This includes [[USB DFU]] for [[Flashing the Neo FreeRunner]], a splash screen, a boot menu, a console for [[bootloader commands]], configuration via [[bootloader environment]], and loading a [[kernel]].

There are various [[bootloader versions]] available. Newer yet is [[Qi]].

== Booting into U-boot ==

* Make sure that your phone has had the battery and USB cable removed for at least 30 seconds.
* Hold in the AUX button on power-up to access the boot menu.
* Connect the Neo (ie not Debug Board) to a Linux host with the USB cable.
* Set the console to USB.
* Connect to /dev/ttyACM0 with a terminal program on the Linux host (you might need to chown uucp.uucp /dev/ttyACM0 )
* Note that the cdc_acm /dev/ttyACM0 access disappears as soon as the Neo boots, and is replaced by the cdc_ether usb0 network access.
* You're now at the bootloader prompt.
* Set the bootdelay uboot environment variable to -1 if you want it to always halt at the bootloader on power-up.

== General ==

All versions of the OM smartphone use the [http://u-boot.sourceforge.net/ u-boot] bootloader.

More information on u-boot can be found at
* http://www.denx.de/wiki/DULG
* http://www.gumstix.org/tikiwiki/tiki-index.php?page=U-Boot
* http://linuxdevices.com/articles/AT5085702347.html

Additions to the vanilla u-boot already implemented include:
* Support for boot from NAND flash using [[S3C2410 Steppingstone]]
* Support for S3C2410 NAND flash
* Support for downloading programs via S3C2410 USB Device Controller
* Support to display bootup logo / status on S3C2410 Framebuffer

However, u-boot still doesn't support many of the features that GTA01 needs, such as
* Support for reading kernel/initrd from SD/Transflash

[[User:HaraldWelte|HaraldWelte]] is working on those issues, and in fact most of them have already been implemented.

== Bootloader source code ==

The current bootloader source can be found at http://git.openmoko.org/?p=u-boot.git;a=shortlog;h=stable .

To get u-boot by git:

git clone git://git.openmoko.org/git/u-boot.git openmoko/u-boot

To build u-boot:
* Clone the git tree and check out the stable branch
* Set the CROSS_COMPILE environment variable to specify the prefix to your toolchain binaries
* Run "make gta02v5_config" (or gta01bv4_config, or whatever hardware revision you have)
* Run "make u-boot.udfu". This will give you an image which you can install with dfu-util, or which you can upload into memory via JTAG (with a debug board)

== Bootloader binary ==

The latest bootloader binary builds can be found under http://downloads.openmoko.org/distro/unstable/daily/ .

All versions of the GTA02 (Neo FreeRunner) that have been sold to the public are version 5 hardware, so look for a file with "gta02" and "v5" in the name, for example:
uboot-gta02v5-latest.bin

The file should be written to the NAND flash address 0x00000000 (size 0x30000) (the first [[Partitions|partition]]).

== Bootloader development ==

=== QT2410 ===
If you want to do bootloader development on the QT2410, it's easier to work with a bootloader image that can be downloaded via USB into RAM instead of flashing.

To do so, you need to edit the u-boot/include/configs/qt2410.h file, and change the "if 0" in Line 32 into a "if 1", then recompile with "make".

The resulting "u-boot.bin" is _NOT SUITABLE_ for NAND flash, but only for direct execution from within ram, e.g. by using the [[s3c2410_boot_usb]] program.

=== Neo 1973 ===

Doing bootloader development on the [[Neo 1973]] is a bit more tricky. First, we don't have any NOR flash. Second, there is no other way to boot _but_ from NAND. Therefore, we also don't have a USB downloader like the QT2410.

The main problem is: The [[S3C2410 Steppingstone]] unconditionally copies the first 4k of flash into its internal SRAM. That SRAM segment stays unconditionally mapped at physical address zero. How do we get around this

=== Neo FreeRunner ===
{{main|Neo_FreeRunner_Memory_Mapping}}

==== Using JTAG to boot from RAM ====

So how can we boot from RAM? We use JTAG / OpenOCD to:

* Reset and halt the cpu at PC=0
<pre>
> reset halt
target halted in ARM state due to debug request, current mode: Supervisor
cpsr: 0x400000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
</pre>

* Download a small piece of code for low-level SDRAM timing initialization (overwrite 4k SRAM of steppingstone)
<pre>
> load_binary /space/misc/gta01/u-boot.git/board/gta01/lowlevel_foo.bin 0
downloaded 332 byte in 0s 21899us
</pre>

* Assert a break point at address 0x33f80000 (which indicates that the low-level code has finished)
<pre>
> bp 0x33f80000 4 hw
breakpoint added at address 0x33f80000
</pre>

* Run the code up to the break point
<pre>
> resume
Target 0 resumed
> Target 0 halted
target halted in ARM state due to breakpoint, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x33f80000
MMU: disabled, D-Cache: disabled, I-Cache: enabled
</pre>

* Download the u-boot RAM image to 0x33f80000
<pre>
> load_binary /space/misc/gta01/u-boot.git/u-boot.bin 0x33f80000
downloaded 135692 byte in 6s 567264us
</pre>

* Resume processing
<pre>
> resume
Target 0 resumed
</pre>

At this point, the display backlight gets bright and we see the following familiar prompt on the serial console:
<pre>
U-Boot 1.1.6 (Jan 13 2007 - 23:44:23)

DRAM: 128 MB
NAND: 64 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
GTA01Bv2 #
</pre>

== Creating bootable images ==

U-boot needs bootable images (such as kernels, but also initrd and others) in form of a so-called ''uImage''. In order to create a ''uImage'' from e.g. a ''vmlinux'' kernel image, you can proceed as follows:

<pre>
objcopy -O binary -R .note -R .comment -S vmlinux linux.bin
gzip -9 linux.bin
u-boot/tools/mkimage -A arm -O linux -T kernel -C gzip -a 30008000 -e 30008000 -n "Kernel Image QT2410" -d linux.bin.gz uImage
</pre>

== Boot menu ==
[[Image:Neo1973 uboot menu.jpg|thumb|400px|u-boot boot menu on Neo1973]]

As of the Phase-0 release, our u-boot version now features an on-screen boot menu. The items are defined by [[bootloader environment#menu|menu entries in the environment]].

=== Accessing the boot menu ===

You can access the boot menu by pressing and holding the [[Neo1973 AUX Button]] together with the power button while switching the phone on.

=== Using the boot menu ===

By pressing the [[Neo1973 AUX Button]] you can cycle through the menu items. Use the ''POWER'' button to select one item.

== Bootloader prompt ==

=== Accessing the bootloader prompt ===
The bootloader prompt is available either on the serial console (via [[Debug Board]]), or as virtual USB Serial device (USB CDC_ACM).
Whether the serial port or usb is used depends on the u-boot environment variables '''stdin''', '''stdout''' and '''stderr'''.

Whether or not you use usbtty, the first couple of messages will always be displayed on the serial console.

The bootloader is currently configured to wait for three seconds. If a key press on the '''stdin''' is received within those three seconds, auto-boot is aborted.

==== Using usbtty from Linux ====

Just by connecting the phone in u-boot mode to your Linux pc should make it detect a [[CDC ACM]] device, and you should get a new tty device called /dev/ttyACM0. If not, check that module cdc_acm is loaded or CONFIG_USB_ACM=y (Device Drivers -> USB support -> USB Modem (CDC ACM) support). (Instructions for MacOS users are [[MacOS_X#USB_Serial|here]])

Use your favourite terminal emulator (minicom, cu, zc, screen ...) to access it like any other serial port. Clear any modem intialisation strings (minicom).

You can adapt the instructions for USB-serial from the [[MacOS_X#USB_Serial|Mac OS]] page.
If you don't have a favorite, try just "cu -l dev/ttyACM0". It is in the taylor-uucp package, use "apt-get install cu" if it is not yet installed

Enter Bootprompt with:
<pre>
cu -l /dev/ttyACM0
</pre>
You might need to
chown uucp.uucp /dev/ttyACM0
to get the necessary rights (even as root, must be done each time).

A nice alternative for cu is Werner Almesberger's [[NeoCon|neocon]].

First, you should try to check whether the USB device shows up in 'lsusb' while you're running in u-boot mode:

<pre>
# lsusb -d 1457:5119
Bus 005 Device 079: ID 1457:5119
</pre>
'''Note''': The Neo Freerunner (GTA02) has the ID 1d50:5119

Second, let's see some more details about the available endpoints and configurations:

<pre>
# lsusb -v -d 1457:5119
Bus 005 Device 079: ID 1457:5119
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x1457
idProduct 0x5119
bcdDevice 0.00
iManufacturer 1 Openmoko, Inc
iProduct 2 Neo1973 Bootloader U-Boot 1.2.0-g6c7cac8c-dirty-moko3
iSerial 3 0000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4 TTY via USB
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 6 Control Interface
CDC Header:
bcdCDC 0.6e
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
CDC ACM:
bmCapabilities 0x00
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 5 Bulk Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 7 USB Device Firmware Upgrade
Device Status: 0x0001
Self Powered
</pre>

Next, you can access it using your favourite terminal program.

Then, if the environment is not set correctly, you will need to use the current console (e.g. serial console) to change the [[bootloader environment#console|console entries in the environment]]:
<pre>
GTA01Bv2 # setenv stderr usbtty
GTA01Bv2 # setenv stdout usbtty
GTA01Bv2 # setenv stdin usbtty
</pre>

==== Typical u-boot prompt ====

<pre>
U-Boot 1.2.0-moko1 (Feb 16 2007 - 00:36:13)

DRAM: 128 MB
NAND: 64 MiB
Found Environment offset in OOB..
Video: 640x480x8 31kHz 59Hz
USB: S3C2410 USB Deviced
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
GTA01Bv3 #
</pre>

=== Commands on the bootloader prompt ===

:''See [[bootloader commands]].''

=== What if I borked my bootloader environment and don't get a prompt anymore? ===
{{Note|This solution applies to a changed u-boot environment which prevents NAND u-boot to successfully boot. The Debian u-boot configuration script may be a cause of this issue.}}
Found a solution here:
[[http://markmail.org/message/gqypwiohdet6x4am?q=almesberger+partition&page=1&refer=xbamkzwwsaobv7wa]]

It works the following way:
* Get the devirginator:
svn co http://svn.openmoko.org/trunk/src/host/devirginator
cd devirginator
* Read the u-boot environment from the device:
dfu-util -a u-boot_env -R -U env.in
* Create a file that contains everything you want to change in your u-boot environment or get it by issuing the following command:
wget http://svn.openmoko.org/trunk/src/host/devirginator/environment.in
* Now let devirginator generate a new u-boot_env partition for us, - that contains the partition table from our u-boot_env, - and all changes we wanted to make; Note that the -D GTA02 is needed for the neo FreeRunner only, and has to come before the other options.
./envedit.pl -D GTA02 -i env.in -f environment.in -o env.out
* On my box the partition layout didn't seem to match the idea of envedit.pl, so it issued 2 warnings:
warning: environment is 262144 bytes, expected 16384
CRC error: expected 0xc33e35fc, got 0x93097bfb
* In this case jut add an additional argument to the command line - that has to be the 1st argument, though, and that contains the size information we got from the warning:
./envedit.pl -s 262144 -D GTA02 -i env.in -f environment.in -o env.out
* Now the perl script should produce no more output anything but write a new u-boot_env partition that we can upload to the device by:
dfu-util -a u-boot_env -R -D env.out

== Device Firmware Upgrade ==

Our version of u-boot also implements [[USB DFU]]. This can be useful to
load files and kernel for quick testing.

To find out whether your version of u-boot supports this, use the output of
$ lsusb -v -d 1457:5119
while the phone is in u-boot mode.

If it supports DFU, you should see the following snippet towards the end of the output:
<pre>
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
</pre>

For information on how to do firmware upgrades, please see [[dfu-util]]. For neo 1973 you may see [[Flashing the Neo 1973#Actually_flashing_things_into_the_device]], and for the FreeRunner : [[Flashing the Neo FreeRunner]].

=== Booting files over DFU ===

To load a file at memory address 0x32000000:
<pre>
dfu-util -a 0 -D fileToLoad -R
</pre>

After that, send 'bootm 0x32000000' to u-boot or 'bootelf 0x32000000' if
its an elf file.

Simple python script that can boot an ELF image - avoiding a ACM bug that breaks on large packets.

<pre>
#!/usr/bin/python
import sys
import os
import time

cmd1 = "neo backlight off\n"
cmd2 = "bootelf 0x32000000\n"

def output(tty, str):
for x in str:
tty.write(x)
tty.flush()

if len(sys.argv) == 2:
print "Loading %s..." % sys.argv[1]

loadfile = "dfu-util -a 0 -D %s -R" % sys.argv[1]

os.system(loadfile)

time.sleep(3)

tty = open("/dev/ttyACM0", "a")

output(tty, cmd1)
output(tty, cmd2)

tty.close()
else:
print "Usage: %s elffile" % sys.argv[0]
print ""
sys.exit(2)
</pre>

== Troubleshooting ==

=== USB connectivity problems ===

I once got errors like this (in dmesg or /var/log/messages) on the host side while connecting the neo in u-boot:

usb 2-1: device descriptor read/64, error -110
usb usb2: Controller not stopped yet!

or

hub 4-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 4-1: USB disconnect, address 2

A possible solution is given below. Please note that if you have a usb keyboard or mouse then the command might cause trouble.

rmmod uhci_hcd ; modprobe uhci_hcd

Another option is to plug the FR into a different USB port on the host, preferably one on the Motherboard not the hub.

Disconnecting the Neo's USB while powering up may prevent this problem in the future.

== Related pages ==

See [[Flashing the Neo 1973]] and [[Flashing the Neo FreeRunner]] for instructions on using dfu-util to install a new bootloader in your phone.

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

Android on Freerunner

2009-04-01T10:20:29Z

Noo:

{{Languages|Android on Freerunner}}

{|align=right
|__TOC__
|}
[[Image:Freerunner-android-01.png]]
= Introduction =
This page is dedicated to the installation of [[Android]] (an [[Open Handset Alliance]] Project) on the [[Neo 1973]] and [[Neo FreeRunner]] handsets.

You can find other information, such as porting, development and day to day usage here : [[Android]]

== Before you start ==

=== Using this guide ===

*1

If you see a command like this, you must run it as root

#

If you see one like this, you can run it as a regular user

$

*2

When you see these commands

adb

dfu-util

it is assumed that you have them installed on your system and inside your /usr/bin. This may not be the case, you may just have downloaded the binary. If so, you need to change to the directory you downloaded the binary too then issue the same commands adding a ./ before it eg.

./adb

./dfu-util

*3

adb connects to Android but you need to have made sure you have set it up first. Make sure your FreeRunner was booted while being plugged in to a USB port. Then following run the following commands:

# ifconfig usb0 192.168.0.200 netmask 255.255.255.0
# adb kill-server
# ADBHOST=192.168.0.202 adb devices

You should now have no trouble using adb.

=== Registering with the GSM network ===

Before you install Android on your FreeRunner you should check, using the operating system it came with, that your sim card will register with your network.

The version of internal [[GSM]] [[firmware]] that comes preloaded on the FreeRunner has compatibility issues with a feature on newer [[sim]] cards. This effects [[3G]], o2 sims and possibly others. if you have one of those you will probably need to upgrade your GSM firmware to get the sim to register with the network. Doing that first means you know it's working before you install Android.

[http://wiki.openmoko.org/wiki/GSM/Flashing GSM/Flashing]

To flash your GSM firmware you will need to have [[USB]] networking setup between your desktop and the OM distribution installed on your FreeRunner. However, your FreeRunner does not need internet access as you can download the GSM firmware files on your desktop PC and transfer them to your FreeRunner using [http://unixhelp.ed.ac.uk/CGI/man-cgi?scp+1 scp]

[http://wiki.openmoko.org/wiki/Usb_networking USB Networking]

== Configuring the Bootloader ==

There are two bootloaders you can use to boot Android; [http://wiki.openmoko.org/wiki/Qi Qi] and [http://wiki.openmoko.org/wiki/Uboot Uboot]. Uboot comes installed on the FreeRunner, Qi is a replacement and is thought to be superior. However there have been, and probably still are, problems when using Qi and Android so Uboot is recommended at this point.

You can download images for them both here:

[http://people.openmoko.org/andy/ Andy Tracking Images] (For Qi on the FreeRunner grab the image starting qi-s3c2442)

[http://downloads.openmoko.org/distro/unstable/daily/om-gta02/20090330/ Latest Uboot]

The Android kernel image can be more than 2MB in size. The UBoot environment that comes with your FreeRunner is only able to boot a kernel 2MB in size or less. To use a kernel larger than 2MB you need to:

* Change to the [http://wiki.openmoko.org/wiki/Qi Qi Bootloader]. It supports 2MB kernels out of the box.

* Adjust your [[Uboot]] environment to [http://meinopenmoko.blogspot.com/2008/12/prepare-uboot-to-boot-android.html support a Kernel of more than 2 MB]

In your Boot-prompt type:
setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\; nand read.e 0x32000000 kernel 0x300000\; bootm 0x32000000
saveenv

== Installing Android on the Internal Flash ==

=== Preparing the SD Card ===

The [[SD]] Card in your FreeRunner needs to be configured with two 2 primary partitions before Android will boot. First a VFAT/MSDOS (16 or 32) which acts as the '/sdcard' storage area (for pictures, movies, music, etc). Second an ext3 primary partition which Android uses as '/data' with in which it stores settings, caches, etc.

==== On Linux ====

Insert the Mico SD Card from your FreeRunner into your Linux desktop then bring up a Terminal and type

$ dmesg | grep sd

You will get an output like this, in this instance we can see that the SD Card has been assigned the device name 'sde'

...
sd 9:0:0:0: [sde] Attached SCSI removable disk
...

Now, as root, use 'fdisk' to partition the device.

# fdisk /dev/sde

Pressing 'p' will show you the current partitions on the SD Card 'd' will delete them and 'n' will create a new one. Create a primary partition for your media. Then another primary partition for Android to store its data on.

On a 1Gig card I used 768MB for the first partition ('+768MB' in fdisk) and the remainder for Android data. Here is fdisk's partition output:

Device Boot Start End Blocks Id System
/dev/sde1 1 769 750513+ 83 Linux
/dev/sde2 770 1016 241072 83 Linux

Now all that's left to do is format the partitions with the appropriate filesystem But first hit 'w' in fdisk to write the changes to the SD Card.

Then format like this:

# mkfs.vfat -v -n and-media -F 32 /dev/sde1
# mkfs.ext3 -v -L and-data /dev/sde2

That's it, you can now remove the SD card from your desktop. If you re-insert it you will have two new usb disk devices.
{{Note|After Android has booted you will only be able to access the 'data' partition as root.}}There is no need to populate the ext3 partition at all. The VFAT partition can be populated with media content (ring tones etc.) if you so desire. {{Note|It can be worth reformatting the data partition when you upgrade the Android OS on your phone. Old settings can result in problems, wifi for example. But remember that formatting the Data partition will result in your preferences, text messages and contacts etc. being erased.}}

==== On FreeRunner (2008.x) ====

The SD card can be formatted from within an existing 2008.x installation on your FreeRunner.
SSH as root into the FreeRunner and use 'fdisk' to partition the device.

# fdisk /dev/mmcblk0

After this create the partitions as described in the step above.

To format the new vfat partition you will need dosfstools which can be downloaded from

[http://members.shaw.ca/mmontour/neo/dosfstools_2.11-r0_armv4t.ipk dosfstools_2.11-r0_armv4t.ipk]

Use any SCP client to copy this file to your FreeRunner and install using

opkg install dosfstools_2.11-r0_armv4t.ipk

Once the installation is complete format the partitions:

# mkfs.vfat -v -n and-media /dev/mmcblk0p1
# mkfs.ext3 -v -L and-data /dev/mmcblk0p2

NOTE: In case you are unable to format the partitions because they are already mounted for some reason you can get a list of process IDs that are using it by running:

# fuser -m /media/card

Then kill all the processes that were using the card and try formatting again.

==== On other OS's ====

There are no open source or free partition editors on Windows or Mac that can manage an ext3 partition. If you do not have Linux installed you can use the [http://gparted.sourceforge.net/ GParted] bootable CD. This CD will boot into a graphical environment with which you can partition your SD Card. You may have to boot with the SD Card inserted for GParted to recognize it as a drive.

=== Downloading Android Images ===

Next, Grab yourself the latest Android images. There are two parts you need to flash, the kernel (uImage*.bin) and the root fs (android*.jffs2). [http://www.koolu.com/ Koolu] release images and you can get them here:

[http://freerunner.android.koolu.com/release-files Release files (Android FreeRunner)]

Koolu are not the only people working on porting Android to the FreeRunner and although collaboration is hopefully on the way, there are other places to get images:

Michael Trimarchi's (panicking) images are the most up to date and functional:

[http://panicking.kicks-ass.org/download/ Michael Trimarchi's images with latest fixes]
[http://www.fragcom.de/android/ Mirror]

Sean McNeil has placed an older 2.6.26 kernel and root fs at:

[http://people.openmoko.org/sean_mcneil/ Sean McNeil images]

=== Flashing the FreeRunner ===

==== On Linux ====

To flash your FreeRunner, replace what ever phone stack you have on there at the moment with Android, first download [http://wiki.openmoko.org/wiki/Dfu-util dfu-util], this is the program that will flash your phone.

Once you have that installed (whether by simply downloading the binary or installing an rpm) Open up a terminal and cd to where you downloaded the images too eg.

# cd /home/joe/Downloads

Plug your FreeRunner into a USB port and boot it into the nand boot loader; Hold down the aux button and then the power button until nor appears.

{{Note|The FreeRunner will only stay in in the nand bootloader state for about 30 seconds with no activity.}}Now Flash the kernel image (you will need to be root) with this command:

# dfu-util -a kernel -R -D uImage-moredrivers-GTA02.bin

and finally the root fs with this one:

# dfu-util -a rootfs -R -D androidfs-koolu-beta3.jffs2

{{Note|The './' part assumes you are using the binary download and that it was downloaded to the same place as your images. If you are, remember to make the dfu-util binary executable.}}If you find that dfu-util complains about there being more than one USB device available it might be because you have a webcam or some other device plugged in. If you can not remove the other device follow this procedure:

Unplug your FreeRunner and run the command

# dfu-utils --list

This will list the other connected usb devices. Now plug your FreeRunner back in and run the command again, the new device will be your FreeRunner. You can now go ahead and flash with the added command '-d FREERUNNER_DEVICE' eg.

# dfu-util -d 0x1d50:0x5119 -a rootfs -R -D freerunner-v13.jffs2

== Installing Android on an SD card ==

=== Images ===

There are currently a few prebuilt images:
[http://activationrecord.net/radekp/openmoko/android/ Radek Polak's SD card images] (install on ext3, first partition on SD must be FAT16)

=== Using jffs2 images ===

You can also boot from the SD Card using the pre built images like so :-
* Mount the image using [http://wiki.openmoko.org/images/8/82/Mntjffs.sh this] script like so
sudo ./Mntjffs.sh freerunner-v5.jffs2 image/
* Then copy (cp -R) the files in directory image/ to any of the first three partitions on the SD Card (if using Qi) eg cp -R /your-path/image/* /media/android/
* cd /media/android.
* wget http://activationrecord.net/radekp/openmoko/android/init.rc .
* mkdir boot
* copy the kernel here and name it uImage-GTA02.bin

Some notes about booting android from sdcard :

=== Setup ===

* Build android from source. See [http://trac.koolu.org/ koolu website] for directions.
* Use the first script in [http://lists.openmoko.org/pipermail/community/2008-December/036982.html this mail] (adapt to your filesystem) to stage your android install.
* copy the contents of this directory on a ext3 partition on your sdcard.
* add a /boot directory on your sdcard.
* copy the uImage-android kernel (see above) and copy it inside your /boot with the exact name '''uImage-GTA02.bin'''
* I changed the init.rc (in your root on the sd) to remove mounts that could be problematic (/data for example) :
<pre>
--- filesystem/root/init.rc 2008-12-15 17:51:14.000000000 +0100
+++ phyce.init.rc 2008-12-19 15:56:25.000000000 +0100
@@ -24,7 +24,7 @@
mkdir /sqlite_stmt_journals 01777 root root
mount tmpfs tmpfs /sqlite_stmt_journals size=4m

- mount rootfs rootfs / ro remount
+ mount rootfs rootfs / rw remount

write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
@@ -38,14 +38,14 @@
# mount yaffs2 mtd@system /system ro remount

# We chown/chmod /data again so because mount is run as root + defaults
- mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev
- chown system system /data
- chmod 0771 /data
+# mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev
+# chown system system /data
+# chmod 0771 /data

# Same reason as /data above
- mount yaffs2 mtd@cache /cache nosuid nodev
- chown system cache /cache
- chmod 0770 /cache
+# mount yaffs2 mtd@cache /cache nosuid nodev
+# chown system cache /cache
+# chmod 0770 /cache
</pre>

* Install [[Qi]] on you NAND flash. You can still boot whatever distro you've got on internal flash using the NOR bootloader. You should try the magic file in /boot to show kernel messages.
* boot the GTA02, and pray.

== Remote access to Android (adb) ==

Although this is not technically part of installing Android it is very useful to have set up. Android Debug Bridge (adb) is a versatile tool that lets you manage the state of a device, in this case, your FreeRunner.

Some ways you can use adb include:

* Run shell commands on the phone.
* Copy files from your desktop to the phone and Vice-versa.

You can find out about it on the [http://developer.android.com/guide/developing/tools/adb.html Android developers page] and a page on this wiki [[Android debug bridge]]

However if you would just like a very quick getting started guide, read on. You can download a binary from [http://people.openmoko.org/sean_mcneil/adb here]. Then if you like copy it to /usr/bin (and don't forget to make it executable).

First you must boot Android while it is plugged in to a USB port, you can unplug it and re-plug it all you like after that but for the USB connection to work it must be connected at boot time.

Next issue this command to set up USB networking...

# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then this one because it helps make sure everything works nicely...

# adb kill-server

Followed by this to find your phone...

ADBHOST=192.168.0.202 adb devices

{{Note|Remember that if you didn't copy adb to /usr/bin you will need to run these commands from the directory you downloaded it too and put ./ in front of adb.}}Now you are free to remotely connect to your Android phone, here are a couple of commands you might find useful

*Copy a file to your SD card:

# adb push YOUR_FILE /sdcard/

*Copy a log file from your phone to your computer:

# adb logcat -d > android.log

*If you just want to log in to the Android shell:

# adb shell

== Troubleshooting ==
=== SD card won't mount ===

There should be a /sdcard directory on your FreeRunner, for some reason this does not always get created (the command is in the 'init.rc' but does not always work). To create the correct dir on your FreeRunner and so enable your SD card, do the following.

* Plug your FreeRunner into a USB port, boot Android and then enter these commands:

# ifconfig usb0 192.168.0.200 netmask 255.255.255.0
# adb kill-server
# ADBHOST=192.168.0.202 adb devices
# adb shell mount -o remount,rw /dev/root /
# adb shell

# mkdir /sdcard
# exit

* Then reboot your FreeRunner

= See also =
* [[Android|Main Android page on this wiki]]
* [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial Video of usability]

[[Category:Distributions]]
[[Category:Flashing Openmoko]]

Openmoko Local Groups: Ulm

2008-10-24T15:02:00Z

Noo: /* Participants */

== Participants ==
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Has Device
!Other
|-
|[[User:lokolb|Lorenz Kolb]]
|Embedded Engineering
|P1 owner
|Ulm
|[[Image: MokoBox.jpg|center]]
|possibly some development, not defined closer, yet
|-
|[[User:Mark|Mark]]
|
|waiting for GTA02
|near Ulm
|
|
|-
|[[User:Lollisoft|Lothar Behrens]]
|
|Got my GTA02 and be happy
|near Ulm (more far, Lenningen)
|[[Image: Moko.jpg|center]]
|
|-
|[[User:JubJub|Sebastian]]
|
|waiting for GTA02
|near Ulm (Aalen)
|
|
|-
|[[User:Noo|Manuel]]
|Ulm
|has got his GTA02:-)
|
|-
|...
|
|
|
|
|
|}

=== Meetings, Events ===
Meeting language is German or English ;-)
{|border=1
!Date
!Location
!Topic
!Who
|-
|???
|...
|...
|???
|-
|}

[[Category:Openmoko Local Groups]]

User:Noo

2008-10-24T15:01:22Z

Noo: New page: I'm not well in programming, i think, although i made some experiences with php, python(-django) and a little bit cpp. My interests are in and about open-source and linux os.

I'm not well in programming, i think, although i made some experiences with php, python(-django) and a little bit cpp.

My interests are in and about open-source and linux os.

User:MrNoo

2008-10-24T14:59:37Z

Noo:

I'm not well in programming, i think, although i made some experiences with php, python(-django) and a little bit cpp.

My interests are in and about open-source and linux os.

User:MrNoo

2008-10-24T14:56:57Z

Noo: New page: I'm not well in programming, i think.

I'm not well in programming, i think.

Openmoko Local Groups: Ulm

2008-10-24T14:55:17Z

Noo: /* Participants */

== Participants ==
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Has Device
!Other
|-
|[[User:lokolb|Lorenz Kolb]]
|Embedded Engineering
|P1 owner
|Ulm
|[[Image: MokoBox.jpg|center]]
|possibly some development, not defined closer, yet
|-
|[[User:Mark|Mark]]
|
|waiting for GTA02
|near Ulm
|
|
|-
|[[User:Lollisoft|Lothar Behrens]]
|
|Got my GTA02 and be happy
|near Ulm (more far, Lenningen)
|[[Image: Moko.jpg|center]]
|
|-
|[[User:JubJub|Sebastian]]
|
|waiting for GTA02
|near Ulm (Aalen)
|
|
|-
|[[User:MrNoo|Manuel]]
|Ulm
|has got his GTA02:-)
|
|-
|...
|
|
|
|
|
|}

=== Meetings, Events ===
Meeting language is German or English ;-)
{|border=1
!Date
!Location
!Topic
!Who
|-
|???
|...
|...
|???
|-
|}

[[Category:Openmoko Local Groups]]