Openmoko - User contributions [en]

U-Boot

2007-08-21T21:59:10Z

Xkr47: Added new troubleshooting section

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

== Phase0 Quick Start ==
* Make sure that your phone has had the battery and USB cable removed for at least 30 seconds.
* Connect the Neo (ie not Debug Board) to a Linux host with the USB cable.
* Hold in the AUX button on power-up to access the boot menu.
* 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 ==

The GTA01 uses 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
* Support for downloading programs via S3C2410 USB Device Controller

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

== Bootloader source code ==

The current bootloader patches can be found at http://svn.openmoko.org/trunk/src/target/u-boot/patches/.

Untar the sources, apply the patch. run "make gta01bv3_config" (or gta01bv2_config, or whatever hardware revision you have), run "make". You will get a resulting "u-boot.bin" image, which you can directly flash (either using existing bootloader or [[sjf2410-linux]]) into NAND.

== Bootloader binary ==

The latest bootloader binary builds can be found at http://buildhost.openmoko.org/tmp/deploy/images/ . It should be written to the NAND flash address 0x00000000 (size 0x30000)

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

=== GTA01 ===

Doing bootloader development on the GTA01 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

==== 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/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.

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

=== Adding items to the boot menu ===

You can add items to the boot menu by setting environment variables. The canonical form is ''menu_<number> <Title>: U-Boot-Commands''

For example the following command will add a boot menu entry that switches to autofast charging and turns off the backlight:
setenv menu_6 Autofast-Charge and Backlight Off: neo1973 charger autofast\; neo1973 backlight off
saveenv

== 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, enable the CONFIG_USB_ACM (Device Drivers -> USB support -> USB Modem (CDC ACM) support).

Use your favourite terminal emulator (minicom, cu, zc, screen ...) to access it like any other serial port. If you don't have a favorite, try just: (cu is in the taylor-uucp package)
cu -l /dev/ttyACM0

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

# lsusb -d 1457:5119
Bus 005 Device 079: ID 1457:5119

Second, lets 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 set
<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 ===

==== Auto-boot ====

Auto-boot executes the command[s] specified in the ''bootcmd'' environment variable. The default configuration is:
<pre>
GTA01Bv3 # printenv
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
</pre>

This basically tells us that it will load the content of the NAND partition '''kernel''' to memory address 0x32000000 and then try to boot it.

==== Environment ====

u-boot is configured to manage a non-volatile environment that is stored in NAND flash. You can use the commands to read/alter/store the environment in the following example:
<pre>
GTA01Bv2 # printenv
baudrate=115200
bootargs=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
usbtty=cdc_acm
bootdelay=10
stdout=serial
stderr=serial
stdin=serial
mtdparts=mtdparts=neo1973-nand:0x00030000(u-boot),0x0000c000(u-boot_env),0x00200000(kernel),0x00130000(splash),0x03c94000(rootfs)
mtdids=nand0=neo1973-nand
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
pcf50606_int1=0x40
filesize=160C000
partition=nand0,0
mtddevnum=0
mtddevname=u-boot

Environment size: 670/16380 bytes
GTA01Bv3 # setenv bootdelay 10
GTA01Bv3 # printenv bootdelay
bootdelay=10
GTA01Bv3 # saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
GTA01Bv3 #
</pre>

Note: When setting multiple commands, e.g. for bootcmd, you need to escape the ';', for instance

<pre>
GTA01Bv3 # setenv bootcmd mmcinit\; ext2load mmc 0 0x32000000 uImage\; bootm 0x32000000
</pre>

==== MMC/SD ====

in order to initialize a MMC/SD card, you have to use the ``mmcinit'' command.
<pre>
GTA01Bv3 # mmcinit
trying to detect SD Card...
MMC found. Card desciption is:
Manufacturer ID = 58d564
HW/FW Revision = 3 8
Product Name = 21DN!@X�
Serial Number = 445303
Month = 5
Year = 2000
READ_BL_LEN=15, C_SIZE_MULT=7, C_SIZE=3197
size = 4208984064
GTA01Bv3 #
</pre>

afterwards, you can read ext2 filesystems like:
<pre>
GTA01Bv3 # ext2ls mmc 0
<DIR> 1024 .
<DIR> 1024 ..
<DIR> 12288 lost+found
1544788 uImage
</pre>

==== NAND ====

<pre>
GTA01Bv3 # help nand
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read[.jffs2] - addr off size
nand write[.jffs2] - addr off size - read/write `size' bytes starting
at offset `off' to/from memory address `addr'
nand erase [clean] [off size] - erase `size' bytes from
offset `off' (entire device if not specified)
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off - mark bad block at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
</pre>

===== Loading Kernel from NAND =====

<pre>
GTA01Bv3 # nand read 0x32000000 kernel

NAND read: device 0 offset 212992, size 2097152 ... 2097152 bytes read: OK
GTA01Bv3 # bootm 0x32000000
## Booting image at 32000000 ...
Image Name: OpenMoko Kernel Image Neo1973
Created: 2007-02-15 23:54:18 UTC
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 1546258 Bytes = 1.5 MB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel ...
</pre>

===== Writing new bootloader to NAND =====

The following set of commands loads the file u-boot.bin from ext2/mmc and flashes it into the
bootloader flash partition:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 u-boot.bin
GTA01Bv3 # nand erase u-boot
GTA01Bv3 # nand write.e 0x32000000 u-boot ${filesize}
</pre>

===== Writing kernel to NAND =====

The following set of commands loads the file uImage from ext2/mmc and flashes it into the
kernel flash partition:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 uImage
GTA01Bv3 # nand erase kernel
GTA01Bv3 # nand write.e 0x32000000 kernel ${filesize}
</pre>

===== Writing rootfs to NAND =====

The following set of commands loads the file rootfs.jffs2 from ext2/mmc and flashes it into the
rootfs flash partition:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 rootfs.jffs2
GTA01Bv3 # nand erase rootfs
GTA01Bv3 # nand write.e 0x32000000 rootfs ${filesize}
</pre>

Please note that this will only work with root file system sizes that are smaller than the amount of memory above 0x32000000, which in the case of 64MB SDRAM is something like 32MB.

==== Neo1973 related commands ====

Our version of u-boot supports a couple of Neo1973 specific commands:
<pre>
GTA01Bv2 # help neo1973
neo1973 neo1973 info - display phone informantion
neo1973 power-off - switch off the phone
neo1973 charger status - display charger status
neo1973 charger autofast - enable automatic fast (500mA) charging
neo1973 charger !autofast - disable automatic fast (500mA) charging
neo1973 charger fast - enable fast (500mA) charging
neo1973 charger off - disable charging
neo1973 backlight (on|off) - switch backlight on or off
neo1973 vibrator (on|off) - switch vibrator on or off
neo1973 udc pullup (on|off) - switch pull-up on or off
</pre>

What's the udc?

===== Timeouts =====

The boot menu timeout can be changed using
<pre>
setenv boot_menu_timeout=[seconds?]
</pre>

Also, by changing bootdelay you can have more time to take control of u-boot:
<pre>
setenv bootdelay=[seconds]
</pre>

===== Power-off =====

Using
neo1973 power-off

you can switch the device off from the bootloader prompt.

===== Battery charger related =====

For a detailed description of the charger basics, see [[Neo1973 Battery Charger]].

====== Inquiring the charger state ======

You can get the current charger status by issuing
neo1973 charger status

The following modes are possible:

* idle - no charging
* trickle - FIXME
* pre - Slow (100mA) charging, works in hardware.
* fast_cccv - Fast (500mA) charging, using Constant-Current followed by Constant Voltage (Li-Ion)

====== Disabling battery charging ======

You can disable battery charging (until the next reboot) by issuing
neo1973 charger off

====== Forcing fast charge ======

Using
neo1973 charger fast
you can force the PMU to try to do a fast (500mA) charge of the battery. It will abort if the battery is in over temperature or some other error condition occurs.

====== Enabling / Disabling automatic fast charge ======

Autofast is a feature of the PCF50606 PMU. It means that the fast_cccv mode will be automatically selected if a charger with suitable voltage is plugged in, and the battery not in over temperature condition.

{{warning|This is potentially dangerous. Only enable autofast if you ARE SURE that you can draw 500mA from the USB connector. This is the case with a wall outlet charger, or if you are attached to a self-powered hub or a desktop PC root hub. Bus powered hubs and some laptops only provide 100mA on their USB ports and can thus not support fast charging}}

You can enable or disable autofast by
neo1973 charger autofast
and
neo1973 charger !autofast
respectively.

===== Backlight =====

You can switch the backlight on and off by using
neo1973 backlight on
and
neo1973 backlight off
respectively.

===== Vibrator =====

You can switch the vibrator on and off by using
neo1973 vibrator on
and
neo1973 vibrator off
respectively.

==== S3C2410 specific commands ====

<pre>
GTA01Bv2 # help s3c2410
s3c2410 speed get - display current PLL speed config
s3c2410 speed list - display supporte PLL speed configs
s3c2410 speed set - set PLL speed
GTA01Bv2 # s3c2410 speed list
50 MHz
101 MHz
202 MHz
266 MHz
GTA01Bv2 # s3c2410 speed get
FCLK = 202 MHz, HCLK = 101 MHz, PCLK = 50 MHz
GTA01Bv2 # s3c2410 speed set 101
GTA01Bv2 # s3c2410 speed get
FCLK = 101 MHz, HCLK = 50 MHz, PCLK = 50 MHz
</pre>

===== 266MHz clock =====

You can re-configure the [[S3C2410]] PLL to generate a 266 MHz core cpu clock (rather than the 200MHz default) by using
GTA01Bv2 # s3c2410 speed set 266
and
GTA01Bv2 # s3c2410 speed set 202
respectively.

{{warning|The old hardware (Phase 0 - GTA01Bv3) only runs stable at 266MHz if you do not attach anything (esp. the FPC / [[Debug Board]] to the Debug Port}}

==== TFTP on QT2410 ====

The QT2410 cs8900a Ethernet can be used to download images via network.

First, you have to make sure that ''ipaddr'', ''serverip'', ''ethaddr' and ''netmaskk'' are set correctly in the environment:

<pre>
QT2410 # printenv
ethaddr=00:01:02:03:04:05
netmask=255.255.255.0
ipaddr=192.168.100.100
serverip=192.168.100.1
</pre>

===== TFTP kernel download =====

<pre>
QT2410 # tftpboot 0x32000000
*** Warning: no boot file name; using 'C0A86464.img'
TFTP from server 192.168.100.1; our IP address is 192.168.100.100
Filename 'C0A86464.img'.
Load address: 0x32000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
##########################################
done
Bytes transferred = 1544788 (179254 hex)
</pre>

you can then commence booting via
<pre>
QT2410# bootm 0x32000000
</pre>

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

=== 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!

The problem disappeared at least for me by the command below on the host side. Please note that if you have usb keyboard or mouse then the command might cause trouble.. I only have PS/2 so I couldn't test it.

rmmod uhci_hcd ; modprobe uhci_hcd

{{Languages|Bootloader}}

[[Category:Software]]
[[Category:Guides]]

USB Networking

2007-08-11T21:05:18Z

Xkr47: Added steps to run desktop apps on the neo display

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

= Desktop side =

== Manual method ==

Modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

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

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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

===Remote apps on neo===

To get desktop apps to show up on your neo, first log in to the phone

ssh -l root 192.168.0.202

Then once inside, run:

DISPLAY=:0 xhost +192.168.0.200

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

DISPLAY=moko:0 xclock

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

DISPLAY=:0 xhost -192.168.0.200


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

USB Networking

2007-08-11T19:02:27Z

Xkr47: /* Manual method */ Removed unnecessary kernel config option CONFIG_USB_NET_CDC_SUBSET

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

= Desktop side =

== Manual method ==

Modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDCETHER
Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

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

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

U-Boot

2007-08-11T18:50:08Z

Xkr47: /* Using usbtty from Linux */ Added linux kernel config option for CDC ACM. Also noted that "cu" is in the taylor-uucp package.

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

== Phase0 Quick Start ==
* Make sure that your phone has had the battery and USB cable removed for at least 30 seconds.
* Connect the Neo (ie not Debug Board) to a Linux host with the USB cable.
* Hold in the AUX button on power-up to access the boot menu.
* Set the console to USB.
* Connect to /dev/ttyACM0 with a terminal program on the Linux host
* 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 ==

The GTA01 uses 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
* Support for downloading programs via S3C2410 USB Device Controller

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

== Bootloader source code ==

The current bootloader patches can be found at http://svn.openmoko.org/trunk/src/target/u-boot/patches/.

Untar the sources, apply the patch. run "make gta01bv3_config" (or gta01bv2_config, or whatever hardware revision you have), run "make". You will get a resulting "u-boot.bin" image, which you can directly flash (either using existing bootloader or [[sjf2410-linux]]) into NAND.

== Bootloader binary ==

The latest bootloader binary builds can be found at http://buildhost.openmoko.org/tmp/deploy/images/ . It should be written to the NAND flash address 0x00000000 (size 0x30000)

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

=== GTA01 ===

Doing bootloader development on the GTA01 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

==== 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/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.

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

=== Adding items to the boot menu ===

You can add items to the boot menu by setting environment variables. The canonical form is ''menu_<number> <Title>: U-Boot-Commands''

For example the following command will add a boot menu entry that switches to autofast charging and turns off the backlight:
setenv menu_6 Autofast-Charge and Backlight Off: neo1973 charger autofast\; neo1973 backlight off

== 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, enable the CONFIG_USB_ACM (Device Drivers -> USB support -> USB Modem (CDC ACM) support).

Use your favourite terminal emulator (minicom, cu, zc, screen ...) to access it like any other serial port. If you don't have a favorite, try just: (cu is in the taylor-uucp package)
cu -l /dev/ttyACM0

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

# lsusb -d 1457:5119
Bus 005 Device 079: ID 1457:5119

Second, lets 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 set
<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 ===

==== Auto-boot ====

Auto-boot executes the command[s] specified in the ''bootcmd'' environment variable. The default configuration is:
<pre>
GTA01Bv3 # printenv
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
</pre>

This basically tells us that it will load the content of the NAND partition '''kernel''' to memory address 0x32000000 and then try to boot it.

==== Environment ====

u-boot is configured to manage a non-volatile environment that is stored in NAND flash. You can use the commands to read/alter/store the environment in the following example:
<pre>
GTA01Bv2 # printenv
baudrate=115200
bootargs=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
usbtty=cdc_acm
bootdelay=10
stdout=serial
stderr=serial
stdin=serial
mtdparts=mtdparts=neo1973-nand:0x00030000(u-boot),0x0000c000(u-boot_env),0x00200000(kernel),0x00130000(splash),0x03c94000(rootfs)
mtdids=nand0=neo1973-nand
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock4 console=ttySAC0,115200 console=tty0 loglevel=8 dyntick=enable lpj=252416
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000
pcf50606_int1=0x40
filesize=160C000
partition=nand0,0
mtddevnum=0
mtddevname=u-boot

Environment size: 670/16380 bytes
GTA01Bv3 # setenv bootdelay 10
GTA01Bv3 # printenv bootdelay
bootdelay=10
GTA01Bv3 # saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
GTA01Bv3 #
</pre>

Note: When setting multiple commands, e.g. for bootcmd, you need to escape the ';', for instance

<pre>
GTA01Bv3 # setenv bootcmd mmcinit\; ext2load mmc 0 0x32000000 uImage\; bootm 0x32000000
</pre>

==== MMC/SD ====

in order to initialize a MMC/SD card, you have to use the ``mmcinit'' command.
<pre>
GTA01Bv3 # mmcinit
trying to detect SD Card...
MMC found. Card desciption is:
Manufacturer ID = 58d564
HW/FW Revision = 3 8
Product Name = 21DN!@X�
Serial Number = 445303
Month = 5
Year = 2000
READ_BL_LEN=15, C_SIZE_MULT=7, C_SIZE=3197
size = 4208984064
GTA01Bv3 #
</pre>

afterwards, you can read ext2 filesystems like:
<pre>
GTA01Bv3 # ext2ls mmc 0
<DIR> 1024 .
<DIR> 1024 ..
<DIR> 12288 lost+found
1544788 uImage
</pre>

==== NAND ====

<pre>
GTA01Bv3 # help nand
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read[.jffs2] - addr off size
nand write[.jffs2] - addr off size - read/write `size' bytes starting
at offset `off' to/from memory address `addr'
nand erase [clean] [off size] - erase `size' bytes from
offset `off' (entire device if not specified)
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off - mark bad block at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
</pre>

===== Loading Kernel from NAND =====

<pre>
GTA01Bv3 # nand read 0x32000000 kernel

NAND read: device 0 offset 212992, size 2097152 ... 2097152 bytes read: OK
GTA01Bv3 # bootm 0x32000000
## Booting image at 32000000 ...
Image Name: OpenMoko Kernel Image Neo1973
Created: 2007-02-15 23:54:18 UTC
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 1546258 Bytes = 1.5 MB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel ...
</pre>

===== Writing new bootloader to NAND =====

The following set of commands loads the file u-boot.bin from ext2/mmc and flashes it into the
bootloader flash partition:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 u-boot.bin
GTA01Bv3 # nand erase u-boot
GTA01Bv3 # nand write.e 0x32000000 u-boot ${filesize}
</pre>

===== Writing kernel to NAND =====

The following set of commands loads the file uImage from ext2/mmc and flashes it into the
kernel flash partition:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 uImage
GTA01Bv3 # nand erase kernel
GTA01Bv3 # nand write.e 0x32000000 kernel ${filesize}
</pre>

===== Writing rootfs to NAND =====

The following set of commands loads the file rootfs.jffs2 from ext2/mmc and flashes it into the
rootfs flash partition:

<pre>
GTA01Bv3 # ext2load mmc 0 0x32000000 rootfs.jffs2
GTA01Bv3 # nand erase rootfs
GTA01Bv3 # nand write.e 0x32000000 rootfs ${filesize}
</pre>

Please note that this will only work with root file system sizes that are smaller than the amount of memory above 0x32000000, which in the case of 64MB SDRAM is something like 32MB.

==== Neo1973 related commands ====

Our version of u-boot supports a couple of Neo1973 specific commands:
<pre>
GTA01Bv2 # help neo1973
neo1973 neo1973 info - display phone informantion
neo1973 power-off - switch off the phone
neo1973 charger status - display charger status
neo1973 charger autofast - enable automatic fast (500mA) charging
neo1973 charger !autofast - disable automatic fast (500mA) charging
neo1973 charger fast - enable fast (500mA) charging
neo1973 charger off - disable charging
neo1973 backlight (on|off) - switch backlight on or off
neo1973 vibrator (on|off) - switch vibrator on or off
</pre>

===== Timeouts =====

The boot menu timeout can be changed using
<pre>
setenv boot_menu_timeout=[seconds?]
</pre>

Also, by changing bootdelay you can have more time to take control of u-boot:
<pre>
setenv bootdelay=[seconds]
</pre>

===== Power-off =====

Using
neo1973 power-off

you can switch the device off from the bootloader prompt.

===== Battery charger related =====

For a detailed description of the charger basics, see [[Neo1973 Battery Charger]].

====== Inquiring the charger state ======

You can get the current charger status by issuing
neo1973 charger status

The following modes are possible:

* idle - no charging
* trickle - FIXME
* pre - Slow (100mA) charging, works in hardware.
* fast_cccv - Fast (500mA) charging, using Constant-Current followed by Constant Voltage (Li-Ion)

====== Disabling battery charging ======

You can disable battery charging (until the next reboot) by issuing
neo1973 charger off

====== Forcing fast charge ======

Using
neo1973 charger fast
you can force the PMU to try to do a fast (500mA) charge of the battery. It will abort if the battery is in over temperature or some other error condition occurs.

====== Enabling / Disabling automatic fast charge ======

Autofast is a feature of the PCF50606 PMU. It means that the fast_cccv mode will be automatically selected if a charger with suitable voltage is plugged in, and the battery not in over temperature condition.

{{warning|This is potentially dangerous. Only enable autofast if you ARE SURE that you can draw 500mA from the USB connector. This is the case with a wall outlet charger, or if you are attached to a self-powered hub or a desktop PC root hub. Bus powered hubs and some laptops only provide 100mA on their USB ports and can thus not support fast charging}}

You can enable or disable autofast by
neo1973 charger autofast
and
neo1973 charger !autofast
respectively.

===== Backlight =====

You can switch the backlight on and off by using
neo1973 backlight on
and
neo1973 backlight off
respectively.

===== Vibrator =====

You can switch the vibrator on and off by using
neo1973 vibrator on
and
neo1973 vibrator off
respectively.

==== S3C2410 specific commands ====

<pre>
GTA01Bv2 # help s3c2410
s3c2410 speed get - display current PLL speed config
s3c2410 speed list - display supporte PLL speed configs
s3c2410 speed set - set PLL speed
GTA01Bv2 # s3c2410 speed list
50 MHz
101 MHz
202 MHz
266 MHz
GTA01Bv2 # s3c2410 speed get
FCLK = 202 MHz, HCLK = 101 MHz, PCLK = 50 MHz
GTA01Bv2 # s3c2410 speed set 101
GTA01Bv2 # s3c2410 speed get
FCLK = 101 MHz, HCLK = 50 MHz, PCLK = 50 MHz
</pre>

===== 266MHz clock =====

You can re-configure the [[S3C2410]] PLL to generate a 266 MHz core cpu clock (rather than the 200MHz default) by using
GTA01Bv2 # s3c2410 speed set 266
and
GTA01Bv2 # s3c2410 speed set 202
respectively.

{{warning|The old hardware (Phase 0 - GTA01Bv3) only runs stable at 266MHz if you do not attach anything (esp. the FPC / [[Debug Board]] to the Debug Port}}

==== TFTP on QT2410 ====

The QT2410 cs8900a Ethernet can be used to download images via network.

First, you have to make sure that ''ipaddr'', ''serverip'', ''ethaddr' and ''netmaskk'' are set correctly in the environment:

<pre>
QT2410 # printenv
ethaddr=00:01:02:03:04:05
netmask=255.255.255.0
ipaddr=192.168.100.100
serverip=192.168.100.1
</pre>

===== TFTP kernel download =====

<pre>
QT2410 # tftpboot 0x32000000
*** Warning: no boot file name; using 'C0A86464.img'
TFTP from server 192.168.100.1; our IP address is 192.168.100.100
Filename 'C0A86464.img'.
Load address: 0x32000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
##########################################
done
Bytes transferred = 1544788 (179254 hex)
</pre>

you can then commence booting via
<pre>
QT2410# bootm 0x32000000
</pre>

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

=== 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>

{{Languages|Bootloader}}

[[Category:Software]]
[[Category:Guides]]

USB Networking

2007-08-11T16:59:23Z

Xkr47: /* Manual method */ Added list of kernel config options needed to get the usbnet drivers needed

= Neo1973 side =

By default Neo1973 has usb0 interface working due to Ethernet gadget (g_ether) compiled into kernel.

= Desktop side =

== Manual method ==

Modprobe usbnet module and configure usb0 interface (as root):
<pre>
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:

1. ping the Neo with
# ping -I usb0 192.168.0.202
2. add a route to your Neo:
# /sbin/route add -host 192.168.0.202/32 dev usb0
3 log in to the Neo
# ssh root@192.168.0.202

If you don't have the necessary modules to get usb0 going, make sure you have the following kernel options enabled:
* CONFIG_USB_USBNET
* CONFIG_USB_NET_CDC_SUBSET
* CONFIG_USB_NET_CDCETHER
All three options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

== Automatic method ==

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

'''For Debian or similar distros:'''
Edit /etc/network/interfaces file ():
<pre>
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
</pre>

'''For Red Hat or similar distros'''
Edit /etc/sysconfig/network-scripts/net.hotplug:

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

Add the following:
<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
exit 0
;;
</pre>

'''For Gentoo or similar distros:'''

* Edit /etc/conf.d/net by adding:
<pre>
# Neo1973
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
</pre>
* Create a new init script:
<pre>
# cd /etc/init.d
# ln -s net.lo net.usb0
</pre>

And now when you connect phone (which has 192.168.0.202 IP) it gets connection to world automatically.

'''For MacOS X:'''

there are no files to edit since hotplugging configuration is done automatically by default. Of course, the interface has been initialized once. Install the AJZaurusUSB driver as described on [[MacOS_X]] and then open System Preferences / Networks which will show the new interface. Configure for Manual DHC with Host address 192.168.0.200 and Gateway 192.168.0.202.

= Connecting to phone =

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

===SSH Extras===

If you get fed up with typing root@192.168.0.202, on your PC edit /etc/hosts and add an entry for 'phone'

192.168.0.202 phone

then edit ~/.ssh/config (or create it) and add

host phone
user root

then all you need to do is type

# ssh phone

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

===SSH Keys===

To generate ssh keys for use as a login mechanism type

ssh-keygen -t rsa

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

# mkdir ~/.ssh

then from your PC copy the '''.pub''' file to the phone.

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

You should now be able to ssh directly into the phone.

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

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

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

===GUI on desktop through SSH===

If you need to get the GUI on the phone onto the desktop via usb, you can use ssh as follows

ssh -l root -X -v 192.168.0.202

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


{{Languages|USB Networking}}

[[Category:Hardware]]
[[Category:Implemented]]

Getting Started with your Neo 1973

2007-08-11T16:55:28Z

Xkr47: /* By using Ethernet emulation over a USB cable */ Added link to USB_Networking for instructions how to get the cdc module into the kernel

Some first steps guide for those who have just received their first Neo1973 hardware

== Hardware ==

=== Inserting the battery ===

Remove the back cover by puting your fingernail in the small recess on the top of the Neo, and pull gently (see just the first step of [[Disassembling Neo1973]]).

See notes below on inserting the SIM, the SD card, and the battery (this page needs to be reorganized).

=== Powering up the phone ===
[[Image:Neo1973_uboot_splash.jpg|200px|thumb|bootloader splash screen]]
Just hitting the power button (depending on your [[u-boot]] version you have to press for >= 5 seconds) should get the phone first into the bootloader, then boot the kernel, and get into X/OpenMoko. The shipped battery typically has enough charge to boot up directly without charging through the usb cable first.

Once you have pressed the power button sufficiently long, the vibrator makes a short pulse and the screen backlight turns on. You can now release the power button and watch the phone booting.

If the battery is not sufficiently charged, the phone will not turn on, even if the usb cable is plugged in.

=== Flashing the Neo1973 GTA01Bv4 ===
The GTA01Bv4 devices that are currently shipping do not boot out of the box. Flashing the phone with the latest kernel and [[Userspace root image|supporting file system ("rootfs")]] is required before the phone will successfully boot.

Read more information at about [[Flashing openmoko]]. MacOS X users please also refer to [[MacOS_X]].

=== Powering down the phone ===

==== While in bootloader mode, or if the phone has crashed ====

If you press the power button for 9 seconds, the phone will switch off. You can notice this by the backlight going dark.

==== While running a full linux system with userspace ====

In this mode, a power-button press of 5 seconds will be sufficient. After this, the init process will take care of safely shutting down the phone, which might take up to 20 extra seconds. The X server should get killed, you should drop back to a (garbled) console, and it should finally switch off - much like a regular Linux PC.

=== Battery charging ===

The [[Neo1973]] supports two charging modes: One 100mA charge mode (called pre-charge) and 500mA (called fast charge). Charging is always done via the USB socket. You can use any USB-A to USB-mini-B cable to connect the phone to any USB host.

==== While in u-boot ====

While you are in u-boot mode, the phone only charges with 100mA by default. (This will change in one of the future revisions).

However, using the u-boot console you can manually enable fast charging. See [[U-boot#Battery_charger_related]] for more information.

==== While in Linux ====

As soon as the phone is connected via USB cable, it will charge. However, the default charging current is only 100mA, way too little if you want to operate the phone and charge at the same time.

If your USB upstream port is capable of supplying 500mA, then it will configure the Neo1973 accordingly and use 500mA charging mode. You can notice this by the following line in the kernel log (/var/log/messages) of the laptop/desktop your Neo1973 is hooked up to
usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet

=== Inserting the SIM card (optional) ===

The slot is found just under the battery. The card holder has arrows indicating which way to push it to unlock it - make sure you don't open it with force when it's locked or it may break. Insert the SIM so that the pads make contact and push the holder firmly until it makes a click, then lock it - otherwise the card will not be detected.

To check if the SIM card is inserted correctly in Linux, you can have a look in gsmd logs or use the instructions detailed in the [[Manually using GSM]] page and issue the ''AT+CIMI'' command.

=== Using your micro-SD card ===

You should have received a memory card with your phone. You might want to copy some mp3 (or better Ogg Vorbis) files to it to try media playback.

Open the SIM card holder (see above) and gently slide the micro-SD shield toward the battery contacts. Lift up the shield and insert the card, contacts first and away from the shield side. Rotate it shut and gently slide the shield away from the battery contacts to lock it closed.

The card should automatically be available under /media/card the next time you boot. You can test it and your audio drivers at the same time by playing an mp3 from it. See [[Neo1973 Audio Subsystem]].

A small video howto (SIM and microSD) is available on google video: http://video.google.de/videoplay?docid=-8343770443102960945

== Getting shell access on the phone ==

=== By using the terminal emulator and on-screen keyboard ===

"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.

With newer images, the keyboard comes up when you tap the white box in the top bar.

You can choose between different keyboard layouts and the stroke recognizer by dragging from the white box and releasing it to the right of the box.

From the desktop, choose "Active tasks->rxvt" to get a root shell.

[[Terminal]] is in the top level menu in recent images.

=== By using Ethernet emulation over a USB cable ===

The standard Neo1973 Linux [[kernel]] has support for the "cdc_ether USB gadget", i.e. a standard implementation of how to emulate an Ethernet device over USB.

The following description is for generic *NIX system. For setting up connectivity specifically on a MacOS X machine, refer to [[MacOS_X]] (because there is no usb0 and you need a special kernel driver first).

As soon as the kernel is up and running, and you have the phone connected via USB, you should get a '''usb0''' device on your host.

The Phone will have the IPv4 address 192.168.0.202/24. You can run `ifconfig` in the terminal on the phone to verify this (this is optional, just check it if it doesn't work given the instructions below)

If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear. If not, see [[USB_Networking]] for more details.

On the '''host PC''', you should then configure your interface to 192.168.0.200 by using
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then you should be able to
# ping 192.168.0.202

and last, but not least
# ssh root@192.168.0.202

Once you press 'enter' (empty password), you should now have a root login.

See [[USB_Networking]] for more details, including instructions on how to automatically setup masquerading so that your phone can get access to the internet through the host PC.

=== By using the debug board/serial/JTAG ===

Please see [[Debug Board#Usage_Instructions]]

== Getting access to the bootloader console ==

Please see [[u-boot#Using_usbtty_from_Linux]]

== Using Audio ==
=== Enable Internal Speaker and Mic in Phone Calls ===
If you got no Speaker and Mic during a Call you need to load the "gsmhandset.state" alsa-configfile

alsactl -f /etc/alsa/gsmhandset.state restore

Maybe you need to load another .state file for playing mp3 or a BT-Headset see in /etc/alsa/

To hear something you can find an .au file (or convert a .wav into an .au by using the sox tool):

sox ringtone_thereisnophone.wav -t raw -r 8012 -u -b -c 1 rigtone_thereisnophone.au

copy it to the device and run

cat ringtone_thereisnophone.au > /dev/dsp

== Useful commands in Linux ==

=== Suspending ===

Writing "mem" into ''/sys/power/state'' tells Linux to suspend - it will enter a low power mode where only the GSM and RAM are powered up and the CPU sleeps. It will persist in this state until a wake-up event arrives. Some currently enabled wake-up events are: AUX or POWER key press, USB cable detect.

If you're connected over ssh, sshd will stop responding when the OS suspends, so to avoid locking up your ssh client, use the command
# (sleep 1; echo mem > /sys/power/state) & exit

=== Initial backup ===

After getting your new Neo1973 booted for the first time you might want to make a back up of the original flash chip contents on your PC, before you overwrite the flash with a custom image or just update to a newer build.

{{note|For phase 0 developers only (GTA01Bv4 shippment 0, '''not > 0 '''): This is a good idea because there are parts in the root filesystem that can't be distributed over internet so they are only found in the shipped ROM (see the [[GPS]] driver).}}

One easy way to back up all of the Flash, that doesn't require installing any special software, is with ''netcat'' over the [[USB Networking|USB ethernet]]. The following commands can be used for that.
{|
! On the host !! On the target
|-
|<pre>
$ netcat -l -p 20000 > mtdblock0
$ netcat -l -p 20000 > mtdblock1
$ netcat -l -p 20000 > mtdblock2
$ netcat -l -p 20000 > mtdblock3
$ netcat -l -p 20000 > mtdblock4
</pre>
|<pre>
# cat /dev/mtdblock0 | nc 192.168.0.200 20000
# cat /dev/mtdblock1 | nc 192.168.0.200 20000
# cat /dev/mtdblock2 | nc 192.168.0.200 20000
# cat /dev/mtdblock3 | nc 192.168.0.200 20000
# cat /dev/mtdblock4 | nc 192.168.0.200 20000
</pre>
|}

This stores the five NAND partitions in files named mtdblock*. Knowing the partition layout (u-boot "mtdparts" command or Linux dmesg) you can restore the whole flash with it.

=== Setting date and time ===

To set the date and time you need to open a terminal or ssh to the device. To set the date and time to August 9 19:02 2007 type:

# date -s 080919022007

The screensaver might turn on as you execute this command - just tap the screen to get back.

Now, you need to synchronize the time with the hardware date/time by typing:

# hwclock --systohc

=== Where to from here ===

You'll probably want to play with some of the interesting hardware in this device. Obviously, you can explore the applications available through the touch-screen interface. But for those who prefer doing things more in the raw from a shell prompt, you can [[Manually_using_GSM | manually use GSM]], [[Manually_using_SMS | manually use SMS]], or you can start playing with the [[GPS]].

{{Languages|Getting_Started_with_your_Neo1973}}

[[Category:Documentation]]
[[Category:Neo1973_Phase_1_related]]

Customizing the Openmoko Distribution

2007-08-11T16:21:31Z

Xkr47: /* First steps */ added suggestion that the DISTRO_EXTRA_RDEPENDS has a bug

== What's the goal? ==

The goal of this page is to teach you how to take an application that you've coded (or the sample app) and properly get it included in your rootfs. This article is a bit of an aggregate page, it's going to take information from [[MokoMakefile]], [[User:CesarB/Using a local overlay|Using a local overlay]], [[Building a hello world application]], and [[Create a package from existing sources]]. So as you can see the goal is for it to be a very thorough introduction, and will take you from "Idea to Inclusion" of your application.

== Setting Up the OpenMoko Environment ==

{| border="1" cellspacing="0" cellpadding="5"
|*If you already have the environment setup then it is imperative that you update your Makefile.
Do this by running:
<pre>make update-makefile</pre>
|}

This part of the tutorial is going to be pretty basic. I absolutely love [[MokoMakefile]], it's fantastic, the creator has done and continues to do a fantastic job with this. I see absolutely no reason not to use it I put my OpenMoko development directory in /home/bryce/mokodev/ and that works great for me. You can feel free to do the same or put it anywhere else in your user directory (or anywhere on your system if you're feeling daring and a little nutty).

To get your environment setup please get it setup according to [[MokoMakefile]] however if you do have the build environment setup manually and you're sure you know what you're doing then feel free to go forward with this.

== Setting Up a Local Overlay ==
If you're at the point for setting up a local overlay this means a couple things. First: You've had a brilliant idea for an application that you just need to have on the OpenMoko platform. Second: You realize that this killer app of yours needs to be done properly and you're not going to do anything silly like include it in the actual tree for the OpenMoko distro because it would probably end up just getting overwritten eventually, or you just realize that it's bad practice!

If you're wondering why and what a local overlay is then let me take this time to explain it to you. A local overlay is where you, as a developer keep your local files in an OE style setup so that you can simply pull your updated code into the tree. You add your overlay tree into the bitbake setup so that when you call bitbake it will pull your own or your customized packages before going to the OE or OpenMoko trees.This keeps everything nice and organized for you and also allows you to build/rebuild/include you apps by using the [[MokoMakefile]]

Thank you to [[User:CesarB]] for this part of the wiki.

To create a local overlay:

* Create a "local" directory and its subdirectories

mkdir local local/conf local/classes local/packages

* Copy <code>site.conf</code> from the openmoko tree to <code>local/conf</code>

cp oe/conf/site.conf local/conf/site.conf

* Edit the site.conf you copied to add the new tree as a source for bitbake recipes.

Change the current <code>BBFILES</code> to look like this:
BBFILES := "${OMDIR}/openembedded/packages/*/*.bb ${OMDIR}/oe/packages/*/*.bb ${OMDIR}/local/packages/*/*.bb"
Change your <code>BBFILE_COLLECTIONS</code> line to look like this:
BBFILE_COLLECTIONS = "upstream local overlay"
Add this line:
BBFILE_PATTERN_overlay = "^${OMDIR}/local/"
Add this line:
BBFILE_PRIORITY_overlay = "20"

The <code>BBFILE_PRIORITY</code> should be greater than all the other <code>BBFILE_PRIORITY</code> variables on the same file.

* Change your <code>BBPATH</code> environment variable to add the new tree ''before'' the two others in your <code>setup-env</code> file.<code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/build:${OMDIR}/local:${OMDIR}/oe:${OMDIR}/openembedded"

== Using Your New Local Overlay ==

=== Changing files in conf/ ===

To change a file in conf/, just copy the file to the overlay tree (preserving the directory structure) and edit it.

=== Changing files in classes/ ===

To change a file in classes/, just copy the file to the overlay tree and edit it.

=== Changing packages ===

Changing a package's recipe is a bit more complex. You have to copy over (or symlink) not only the .bb file for the package, but also ''all'' the files it includes with <code>require</code>, and the <code>FILESDIR</code> directories (all directories referred to by <code>FILESDIR</code>, usually named either ''package''-''version'' or <code>files</code>). If you forget one of them, the build will give an error (either when parsing the recipe in the case of <code>require</code>, or when trying to build in the case of the <code>FILESDIR</code> directories).

=== Adding a new package ===

You can add a new package (or a recipe for a new version of a package) to the overlay tree simply by creating it on the overlay tree.

== Your First Application ==

I know that I said I'd have a GDK application in here, however, I'd really like to get this whole course done first and have you guys starting to code instead of just looking at what I've written!

This will be a very simple CLI hello world.

=== Before We Code ===

Like a good coder you want to make sure that you're not just doing things, but that you're doing them the right way!

Now change directories into your <code>local/packages</code> directory.The following commands expect you'll be in that directory so don't change unless you know what you're doing!

You'll want to make a directory with the name of your application, and a subdirectory called files.
mkdir myhelloworld myhelloworld/files
Now you'll want to create two files in the <code>files</code> directory
touch myhelloworld/files/README.txt myhelloworld/files/myhelloworld.c
And finally you'll want to create a bitbake file.
touch myhelloworld/myhelloworld.bb

Alrighty now all your necessary files are created so lets go over this real quick.
<pre>
$HOME
+- $OMDIR (contains the official openmoko tree)
| +- local/
| +- packages/
| +- myhelloworld/
| +- myhelloworld.bb
| +- files/
| +- myhelloworld.c
| +- README.txt
</pre>

That should be your structure, if it's not you should go and fix it up.
=== Filling the Files ===

So you've got your sample files all laid out now it's time to make them actually do something.

myhelloworld.c
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
printf("Ello Poppet!\n");
return 0;
}
</pre>

README.txt
<pre>
This is a command line application. It prints a simple Hello World! To stdout.
</pre>

myhelloworld.bb
<pre>
DESCRIPTION = "A killer hello world application"
AUTHOR = "Bryce Leo"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://myhelloworld.c \
file://README.txt "

S = "${WORKDIR}/myhelloworld/"

do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/myhelloworld.c -o myhelloworld
}

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/myhelloworld
install -m 0755 ${S}/myhelloworld ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/myhelloworld
}

</pre>

=== Your First Compilation ===

This is where the [[MokoMakefile]] comes in very very handy. Change to your ${OMDIR} directory, You'll know it by the fact that it is where <code>Makefile</code> resides.
make build-package-myhelloworld

(make sure you run make openmoko-devel-image at least once before building your own packages)

This should all come back and not return any error messages, The output should end in something similar to
<pre>
NOTE: package myhelloworld-1.0: completed
NOTE: build 200707291926: completed
Build statistics:
Attempted builds: 1
</pre>

Now that no errors were thrown we are happily done!

== Adding Your Application to the Image ==

So you've had an idea, you've setup the build environment, you've setup your local overlay, you've laid out your application tree, you've put code into those fantastic files of yours and now it compiles.There's only one thing left to do. Add that application to your image.

Now lets go over in words and whys what we're about to do. First we need to make modify the <code>${OMDIR}/build/conf/local.conf</code>. We add in the variable <code>DISTRO_EXTRA_RDEPENDS</code> and set its value to include <code>myhelloworld</code>. If you'd like to include other packages from your own overlay or the OM tree just add them inseparated by spaces. After this gets added as a dependency to build the Distro (in this case OpenMoko). Now we have to re-build the task-base package. This essentially just generates an ipk file that will "Merge machine and distro options to create a basic machine task/package." It pretty much builds a file with a list of packages to be installed that are required for the distro to work correctly. So then you just go through and make <code>openmoko-devel-image, build-qemu, flash-qemu-local,</code> and <code>run-qemu</code>. Then calibrate your stylus, head over to the terminal, and run your application!

=== Modifying Your local.conf ===
Now, go into your build config directory <code>${OMDIR}/build/conf/</code> and now you'll be editing <code>local.conf</code>
Add this line to you <code>local.conf</code>
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
With this line you can also include other applications from the OE tree. For instance my <code>local.conf</code> looks like this.
<pre>
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS += "lua dillo myhelloworld"
</pre>

Now that you've fixed your <code>local.conf</code> it's time to go through all the necessary tasks to add and re-build you image and have your sweet package included.

=== Building ===
Now come the easy part thanks to [[MokoMakefile]].

make rebuild-package-task-base
make openmoko-devel-image
make build-qemu
make flash-qemu-local

Now all you have to do is run qemu.
make run-qemu

From here after you calibrate your stylus, you click on the Menu in the top right, click down to terminal, then just run your program.
<pre>
root@fic-gta02:/$ myhelloworld
Ello Poppet!
</pre>

==Adding Python scripts as applications==
This is for adding python scripts/packages to the image for your own use.
===First steps===
First, you need to modify the <code>local.conf</code> file as described above. You need to modify
DISTRO_EXTRA_RDEPENDS += "myhelloworld"
to
DISTRO_EXTRA_RDEPENDS += "myhelloworld python"

--[[User:Xkr47|xkr47]] 18:21, 11 August 2007 (CEST) Hmm surely the new line should be DISTRO_EXTRA_RDEPENDS += "pyhelloworld python" instead since the package we create below is pyhelloworld..

This is because python is not included by default in the openmoko image. Or you can use <code>python-pygtk2</code> if you wish.

Next, you need to perform these actions from the <code>$OMDIR/local</code> directory.

mkdir packages/pyhelloworld packages/pyhelloworld/files

touch packages/pyhelloworld/files/pyhello packages/pyhelloworld/README.txt

touch packages/pyhelloworld/pyhelloworld.bb

===Filling in the files===
Now, edit <code>packages/pyhelloworld/files/pyhello</code> to contain:
<pre>
#!/usr/bin/python

print "hello world!"
print "shutting down now. Farewell oh cruel, cruel world!"
</pre>

Next up, is editing <code>packages/pyhelloworld/files/README.txt</code> to say:

This is the most awesome helloworld application ever. Know why? It has SNAKES!

Kidding aside, next is the all important <code> packages/pyhelloworld/pyhelloworld.bb:</code>
<pre>
DESCRIPTION = "A pythonic hello world application"
AUTHOR = "Tyler Laing"
HOMEPAGE = ""
SECTION = "console/applications"
PRIORITY = "optional"
LICENSE = "MIT"
#DEPENDS = ""
#RDEPENDS = ""
#RRECOMMENDS = ""
#RCONFLICTS = ""
#SRCDATE = "20070729"
#PV = "0.1"
#PR = "r0"
SRC_URI = "file://pyhello \
file://README.txt "

S = "${WORKDIR}/pyhelloworld/"

do_install() {
install -m 0755 -d ${D}${bindir} ${D}${docdir}/pyhelloworld
install -m 0755 ${WORKDIR}/pyhello ${D}${bindir}
install -m 0644 ${WORKDIR}/README.txt ${D}${docdir}/pyhelloworld
}

</pre>

I'll explain each of the parts right here, for future reference.

====Meanings of variables in .bb files====

$WORKDIR = $OMDIR/local/packages/<application directory>
$bindir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/bin
$docir = $OMDIR/build/tmp/work/armv4t-linux/<application directory>/image/usr/share/doc
$D = $OMDIR/build/

====Final steps====
Complete the last steps as per the above instructions, from the point of altering <code>DISTRO_EXTRA_RDEPENDS</code>.

And your done!

[[Category:Applications]]
[[Category:OpenMoko]]
[[Category:Developer]]

Disassembling Neo 1973

2007-08-11T07:46:17Z

Xkr47: /* Back side of Neo1973 */ Added comment about the different logo in GTA01Bv4

{{note| The [[Disassembling Neo1973 | Disassembling the Neo1973 page]] shows how to open up the GTA01Bv3 hardware revision. Future hardware revisions may require updates to this page. However, both GTA01B4 (currently shipping) and [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]] (the version to be released in October) share the same case. }}

== Back side of Neo1973 ==
The picture below is from the GTA01Bv3 model. The GTA01Bv4 has the OpenMoko logo + OPENMOKO text below instead.

[[Image:Gta01b v3 case back white.jpg|700px]]

== Opening back cover ==

To remove the back cover, put your fingernail in the small recess on the top of the Neo, and pull gently.

{{note| the back is not hinged, as it may appear in this picture; lift both sides away equally to avoid breaking the small tabs.}}

[[Image:Gta01b v3 case back open white.jpg|700px]]

Please note the 27 x 9 x 6 mm space above the sim & memory cards after inserting the battery. This could maybe be of some use for 3rd party electronics.

[[Image:Gta01b v4 space next to battery.jpg|700px]]

{{note| In order to remove the front cover, you now need to remove the two Torx screws (T6x40)}}

== Carefully remove top cover ==
[[Image:Gta01b v3 case side opening white.jpg|700px]]

To remove the top cover, after removing the two Torx screws, ''carefully'' squeeze the end of the supplied guitar pick between the cover and the case at the bottom of the device, and then slide the pick up to the top on one side (do not twist the pick). As you slide the pick along, the case retaining clips should come apart with a snapping sound. Repeat the procedure for the other side of the device. To unclip the last remaining large retaining clip at the top, slide the pick all the way to the top (this can be difficult) and then press it in at the centre. By ''careful'' application of force the clip will detach and the cover can then be removed.

== Top case lid removed ==
[[Image:Gta01b v3 case top open white.jpg|700px]]

Visible in this image, from the right, going clockwise.

*The blocky device at the far right is the GPS antenna.
**To the left of this, there are two gold pads, which are where the earpiece speaker connects.
*The [[Debug Board]] connector.
*At the left, the black semicircular device is the GSM antenna.
**Immediately to its right, the small circular black/gold object is the microphone
*At the top right, the ''Aux button''
*Right below it seems to be a small battery. It can also be seen on the picture below.

In the middle is the touchscreen LCD, the touchscreen printed wire can be seen beginning at the bottom left of this, through the glass.

== Lifting the PCB on the left side ==
{{note|You have to bend the plastic case a bit outwards until the headphone jack on the left side of the device becomes loose}}
[[Image:Gta01b v3 case top open pcb lift white.jpg|700px]]

== Removing PCB from case frame ==
{{note|Since the PCB now is loose on one side, you can carefully pull the USB socket and GPS antenna connector out of the right side of the case, and then flip the PCB upwards}}
[[Image:Gta01b v3 case top open pcb lifted.jpg|700px]]

This shows:
*At the top on a green board, the bluetooth module, and the square bluetooth antenna.
*The headset jack is to the right of this.
**Immediately below the headset jack is the [[Neo1973 Battery]] connector.
**Below the [[Neo1973 Battery]] connector, the two gold pads feed the vibrator motor.
*To the right of the headset jack is the left speaker connector.

On the other side of the PCB, going from bottom-right corner down-left.

*The small circular connector is the GSM connector to which an external aerial can be connected with the back removed, or with an alternative back.

*To the left of this is the right speaker connector.
*One of the button switches.
*USB port.
*Micro-SD slot
*SIM slot - overlaying the Micro-SD slot when present.
*Gold GPS antenna connector.
**Immediately above this with the grey wire connection is the connection to the built in GPS antenna.

On the case picture below, you can see the left and right speakers under the translucent plastic, and the vibrator motor in the middle.

== Empty case frame ==

[[Image:Gta01b v3 case empty white.jpg|700px]]

You can actually see the two stereo speakers beneath the translucent cover, and next to it the small vibrator motor.

Next to the top of the picture is a hole near the speaker.
The external GSM antenna connector is accessed through this hole.

== GSM Antenna ==

[[Image:Gta01b v3 gsm antenna.jpg|700px]]


{{Languages|Disassembling_Neo1973}}

[[Category:Neo1973 Phase 1 related]]
[[Category:Neo1973 Phase 0 related]]

Disassembling Neo 1973

2007-08-11T07:39:57Z

Xkr47: /* Opening back cover */ Added picture with battery inserted and noted that a small hole for 3rd party use remains

{{note| The [[Disassembling Neo1973 | Disassembling the Neo1973 page]] shows how to open up the GTA01Bv3 hardware revision. Future hardware revisions may require updates to this page. However, both GTA01B4 (currently shipping) and [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]] (the version to be released in October) share the same case. }}

== Back side of Neo1973 ==
[[Image:Gta01b v3 case back white.jpg|700px]]

== Opening back cover ==

To remove the back cover, put your fingernail in the small recess on the top of the Neo, and pull gently.

{{note| the back is not hinged, as it may appear in this picture; lift both sides away equally to avoid breaking the small tabs.}}

[[Image:Gta01b v3 case back open white.jpg|700px]]

Please note the 27 x 9 x 6 mm space above the sim & memory cards after inserting the battery. This could maybe be of some use for 3rd party electronics.

[[Image:Gta01b v4 space next to battery.jpg|700px]]

{{note| In order to remove the front cover, you now need to remove the two Torx screws (T6x40)}}

== Carefully remove top cover ==
[[Image:Gta01b v3 case side opening white.jpg|700px]]

To remove the top cover, after removing the two Torx screws, ''carefully'' squeeze the end of the supplied guitar pick between the cover and the case at the bottom of the device, and then slide the pick up to the top on one side (do not twist the pick). As you slide the pick along, the case retaining clips should come apart with a snapping sound. Repeat the procedure for the other side of the device. To unclip the last remaining large retaining clip at the top, slide the pick all the way to the top (this can be difficult) and then press it in at the centre. By ''careful'' application of force the clip will detach and the cover can then be removed.

== Top case lid removed ==
[[Image:Gta01b v3 case top open white.jpg|700px]]

Visible in this image, from the right, going clockwise.

*The blocky device at the far right is the GPS antenna.
**To the left of this, there are two gold pads, which are where the earpiece speaker connects.
*The [[Debug Board]] connector.
*At the left, the black semicircular device is the GSM antenna.
**Immediately to its right, the small circular black/gold object is the microphone
*At the top right, the ''Aux button''
*Right below it seems to be a small battery. It can also be seen on the picture below.

In the middle is the touchscreen LCD, the touchscreen printed wire can be seen beginning at the bottom left of this, through the glass.

== Lifting the PCB on the left side ==
{{note|You have to bend the plastic case a bit outwards until the headphone jack on the left side of the device becomes loose}}
[[Image:Gta01b v3 case top open pcb lift white.jpg|700px]]

== Removing PCB from case frame ==
{{note|Since the PCB now is loose on one side, you can carefully pull the USB socket and GPS antenna connector out of the right side of the case, and then flip the PCB upwards}}
[[Image:Gta01b v3 case top open pcb lifted.jpg|700px]]

This shows:
*At the top on a green board, the bluetooth module, and the square bluetooth antenna.
*The headset jack is to the right of this.
**Immediately below the headset jack is the [[Neo1973 Battery]] connector.
**Below the [[Neo1973 Battery]] connector, the two gold pads feed the vibrator motor.
*To the right of the headset jack is the left speaker connector.

On the other side of the PCB, going from bottom-right corner down-left.

*The small circular connector is the GSM connector to which an external aerial can be connected with the back removed, or with an alternative back.

*To the left of this is the right speaker connector.
*One of the button switches.
*USB port.
*Micro-SD slot
*SIM slot - overlaying the Micro-SD slot when present.
*Gold GPS antenna connector.
**Immediately above this with the grey wire connection is the connection to the built in GPS antenna.

On the case picture below, you can see the left and right speakers under the translucent plastic, and the vibrator motor in the middle.

== Empty case frame ==

[[Image:Gta01b v3 case empty white.jpg|700px]]

You can actually see the two stereo speakers beneath the translucent cover, and next to it the small vibrator motor.

Next to the top of the picture is a hole near the speaker.
The external GSM antenna connector is accessed through this hole.

== GSM Antenna ==

[[Image:Gta01b v3 gsm antenna.jpg|700px]]


{{Languages|Disassembling_Neo1973}}

[[Category:Neo1973 Phase 1 related]]
[[Category:Neo1973 Phase 0 related]]

File:Gta01b v4 space next to battery.jpg

2007-08-11T07:38:13Z

Xkr47: GTA01Bv4 with battery inserted leaves a little hole (27 x 9 x 6 mm) for 3rd party stuff

GTA01Bv4 with battery inserted leaves a little hole (27 x 9 x 6 mm) for 3rd party stuff

Userspace root image

2007-08-10T15:25:56Z

Xkr47: /* demo JFFS2 root image */ Removed old demo rootfs link and added a link to the "Flashing openmoko" page instead which lists more recent guidelines

== 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 int 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 ==

=== 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 (MTD RAM) device ===

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

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 /dev/mtdblock0 <mountpoint>

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

[[Category:Software]]
[[Category:Guides]]

Getting Started with your Neo 1973

2007-08-10T15:21:29Z

Xkr47: /* Flashing the Neo1973 GTA01Bv4 */ Added link to Userspace_root_image

Some first steps guide for those who have just received their first Neo1973 hardware

== Hardware ==

=== Inserting the battery ===

Remove the back cover (see just the first step of [[Disassembling Neo1973]]).

See notes below on inserting the SIM, the SD card, and the battery (this page needs to be reorganized).

=== Powering up the phone ===
[[Image:Neo1973_uboot_splash.jpg|200px|thumb|bootloader splash screen]]
Just hitting the power button (depending on your [[u-boot]] version you have to press for >= 5 seconds) should get the phone first into the bootloader, then boot the kernel, and get into X/OpenMoko. The shipped battery typically has enough charge to boot up directly without charging through the usb cable first.

Once you have pressed the power button sufficiently long, the vibrator makes a short pulse and the screen backlight turns on. You can now release the power button and watch the phone booting.

If the battery is not sufficiently charged, the phone will not turn on, even if the usb cable is plugged in.

=== Flashing the Neo1973 GTA01Bv4 ===
The GTA01Bv4 devices that are currently shipping do not boot out of the box. Flashing the phone with the latest kernel and [[Userspace root image|supporting file system ("rootfs")]] is required before the phone will successfully boot.

Read more information at about [[Flashing openmoko]].

=== Powering down the phone ===

==== While in bootloader mode, or if the phone has crashed ====

If you press the power button for 9 seconds, the phone will switch off. You can notice this by the backlight going dark.

==== While running a full linux system with userspace ====

In this mode, a power-button press of 5 seconds will be sufficient. After this, the init process will take care of safely shutting down the phone, which might take up to 20 extra seconds. The X server should get killed, you should drop back to a (garbled) console, and it should finally switch off - much like a regular Linux PC.

=== Battery charging ===

The [[Neo1973]] supports two charging modes: One 100mA charge mode (called pre-charge) and 500mA (called fast charge). Charging is always done via the USB socket. You can use any USB-A to USB-mini-B cable to connect the phone to any USB host.

==== While in u-boot ====

While you are in u-boot mode, the phone only charges with 100mA by default. (This will change in one of the future revisions).

However, using the u-boot console you can manually enable fast charging. See [[U-boot#Battery_charger_related]] for more information.

==== While in Linux ====

As soon as the phone is connected via USB cable, it will charge. However, the default charging current is only 100mA, way too little if you want to operate the phone and charge at the same time.

If your USB upstream port is capable of supplying 500mA, then it will configure the Neo1973 accordingly and use 500mA charging mode. You can notice this by the following line in the kernel log (/var/log/messages) of the laptop/desktop your Neo1973 is hooked up to
usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet

=== Inserting the SIM card (optional) ===

The slot is found just under the battery. The card holder has arrows indicating which way to push it to unlock it - make sure you don't open it with force when it's locked or it may break. Insert the SIM so that the pads make contact and push the holder firmly until it makes a click, then lock it - otherwise the card will not be detected.

To check if the SIM card is inserted correctly in Linux, you can have a look in gsmd logs or use the instructions detailed in the [[Manually using GSM]] page and issue the ''AT+CIMI'' command.

=== Using your micro-SD card ===

You should have received a memory card with your phone. You might want to copy some mp3 (or better Ogg Vorbis) files to it to try media playback.

Open the SIM card holder (see above) and gently slide the micro-SD shield toward the battery contacts. Lift up the shield and insert the card, contacts first and away from the shield side. Rotate it shut and gently slide the shield away from the battery contacts to lock it closed.

The card should automatically be available under /media/card the next time you boot. You can test it and your audio drivers at the same time by playing an mp3 from it. See [[Neo1973 Audio Subsystem]].

A small video howto (SIM and microSD) is available on google video: http://video.google.de/videoplay?docid=-8343770443102960945

== Getting shell access on the phone ==

=== By using the terminal emulator and on-screen keyboard ===

"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.

With newer images, the keyboard comes up when you tap the white box in the top bar.

You can choose between different keyboard layouts and the stroke recognizer by dragging from the white box and releasing it to the right of the box.

From the desktop, choose "Active tasks->rxvt" to get a root shell.

[[Terminal]] is in the top level menu in recent images.

=== By using Ethernet emulation over a USB cable ===

The standard Neo1973 Linux [[kernel]] has support for the "cdc_ether USB gadget", i.e. a standard implementation of how to emulate an Ethernet device over USB.

As soon as the kernel is up and running, and you have the phone connected via USB, you should get a '''usb0''' device on your host.

The Phone will have the IPv4 address 192.168.0.202/24. You can run `ifconfig` in the terminal on the phone to verify this (this is optional, just check it if it doesn't work given the instructions below)

If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear.

On the '''host PC''', you should then configure your interface to 192.168.0.200 by using
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then you should be able to
# ping 192.168.0.202

and last, but not least
# ssh root@192.168.0.202

Once you press 'enter' (empty password), you should now have a root login.

See [[USB_Networking]] for more details, including instructions on how to automatically setup masquerading so that your phone can get access to the internet through the host PC.

=== By using the debug board/serial/JTAG ===

Please see [[Debug Board#Usage_Instructions]]

== Getting access to the bootloader console ==

Please see [[u-boot#Using_usbtty_from_Linux]]

== Using Audio ==
=== Enable Internal Speaker and Mic in Phone Calls ===
If you got no Speaker and Mic during a Call you need to load the "gsmhandset.state" alsa-configfile

alsactl -f /etc/alsa/gsmhandset.state restore

Maybe you need to load another .state file for playing mp3 or a BT-Headset see in /etc/alsa/

To hear something you can find an .au file (or convert a .wav into an .au by using the sox tool):

sox ringtone_thereisnophone.wav -t raw -r 8012 -u -b -c 1 rigtone_thereisnophone.au

copy it to the device and run

cat ringtone_thereisnophone.au > /dev/dsp

== Useful commands in Linux ==

=== Suspending ===

Writing "mem" into ''/sys/power/state'' tells Linux to suspend - it will enter a low power mode where only the GSM and RAM are powered up and the CPU sleeps. It will persist in this state until a wake-up event arrives. Some currently enabled wake-up events are: AUX or POWER key press, USB cable detect.

If you're connected over ssh, sshd will stop responding when the OS suspends, so to avoid locking up your ssh client, use the command
# (sleep 1; echo mem > /sys/power/state) & exit

=== Initial backup ===

After getting your new Neo1973 booted for the first time you might want to make a back up of the original flash chip contents on your PC, before you overwrite the flash with a custom image or just update to a newer build.

{{note|For phase 0 developers only (GTA01Bv4 shippment 0, '''not > 0 '''): This is a good idea because there are parts in the root filesystem that can't be distributed over internet so they are only found in the shipped ROM (see the [[GPS]] driver).}}

One easy way to back up all of the Flash, that doesn't require installing any special software, is with ''netcat'' over the [[USB Networking|USB ethernet]]. The following commands can be used for that.
{|
! On the host !! On the target
|-
|<pre>
$ netcat -l -p 20000 > mtdblock0
$ netcat -l -p 20000 > mtdblock1
$ netcat -l -p 20000 > mtdblock2
$ netcat -l -p 20000 > mtdblock3
$ netcat -l -p 20000 > mtdblock4
</pre>
|<pre>
# cat /dev/mtdblock0 | nc 192.168.0.200 20000
# cat /dev/mtdblock1 | nc 192.168.0.200 20000
# cat /dev/mtdblock2 | nc 192.168.0.200 20000
# cat /dev/mtdblock3 | nc 192.168.0.200 20000
# cat /dev/mtdblock4 | nc 192.168.0.200 20000
</pre>
|}

This stores the five NAND partitions in files named mtdblock*. Knowing the partition layout (u-boot "mtdparts" command or Linux dmesg) you can restore the whole flash with it.

=== Setting date and time ===

To set the date and time you need to open a terminal or ssh to the device. To set the date and time to August 9 19:02 2007 type:

# date -s 080919022007

The screensaver might turn on as you execute this command - just tap the screen to get back.

Now, you need to synchronize the time with the hardware date/time by typing:

# hwclock --systohc

=== Where to from here ===

You'll probably want to play with some of the interesting hardware in this device. Obviously, you can explore the applications available through the touch-screen interface. But for those who prefer doing things more in the raw from a shell prompt, you can [[Manually_using_GSM | manually use GSM]], [[Manually_using_SMS | manually use SMS]], or you can start playing with the [[GPS]].

{{Languages|Getting_Started_with_your_Neo1973}}

[[Category:Documentation]]
[[Category:Neo1973_Phase_1_related]]

User:Xkr47

2007-08-10T06:34:47Z

Xkr47:

Me:
* Happy and Proud OpenMoko GTA01Bv04 owner since 2007-08-09 ^^
* [http://xkr47.outerspace.dyndns.org/ my homepage]
* [http://sourceforge.net/people/viewprofile.php?user_id=66259 my computer-related skills]
* [http://www.google.com/search?q=xkr47+OR+jberlin%40niksula+OR+jberlin%40cc+OR+outerspace.dyndns.org my internet resumé]

Wishlist for my openmoko:

* basic telephony
* automatic [[Screen Saver|screensaver]] & locker
** require code/password/gesture to unlock
* [[Messages|SMS sending and reception]]
* SMS mirroring to home server
* remote GUI app connected to home server when SMS arrives / phone is ringing / other important event (battery low) in case I can't hear the phone when it's in my backpack
* MMS sending & reception - outgoing pics taken with external USB-connected digital camera
* Integration with local public transportation services which provides clickable maps --> GPS can be used to automatically "go home from wherever I happen to be"
* ssh client
* "Status" app or [[Today|similar]] with multiple small windows aka gadgets / widgets that report different stats e.g. ssh (for irc), SMS, missed calls, next calendar entries, profile, tv programme etc, [http://en.wikipedia.org/wiki/Digital_video_recorder DVR] status
* Switch to "status" app automatically if user idles long enough
* [[Calendar]]
* automatic (weekly or calender-based) and [[Clock|manual alarm clock]]
* [[Profiles|Profile]] changes:
** programmable - time, location & calendar based
** manual profile override with timeout - cinema, sleep, meeting
* allow use of event (incoming phone call, sms message etc) metadata (who called, what time) to override profile settings
* screensaver that shuts the screen completely off, not just the backlight
** one click in screensaver mode -> screen in "on" mode but backlight still off, tune X color settings so that the contrast is increased to improve readbility
** second click -> backlight on as well, color settings back to normal
* SMS writing with [[Applications#Finger-Based_Applications | fingers]] - maybe some basic 123 456 789 *0# [[Input Method|onscreen keyboard]] with [http://en.wikipedia.org/wiki/T9_(predictive_text) T9] or similar
* one-click publishing of pictures taken with external digital camera to home web server

Hopefully my skills will let me implement at least some of these :)

Feel free to comment anything on the [[User_talk:Xkr47|talk page]].

User:Xkr47

2007-08-10T06:33:20Z

Xkr47:

Me:
* Happy oldschool OpenMoko GTA01Bv04 owner ^^
* [http://xkr47.outerspace.dyndns.org/ my homepage]
* [http://sourceforge.net/people/viewprofile.php?user_id=66259 my computer-related skills]
* [http://www.google.com/search?q=xkr47+OR+jberlin%40niksula+OR+jberlin%40cc+OR+outerspace.dyndns.org my internet resumé]
*

Wishlist for my openmoko:

* basic telephony
* automatic [[Screen Saver|screensaver]] & locker
** require code/password/gesture to unlock
* [[Messages|SMS sending and reception]]
* SMS mirroring to home server
* remote GUI app connected to home server when SMS arrives / phone is ringing / other important event (battery low) in case I can't hear the phone when it's in my backpack
* MMS sending & reception - outgoing pics taken with external USB-connected digital camera
* Integration with local public transportation services which provides clickable maps --> GPS can be used to automatically "go home from wherever I happen to be"
* ssh client
* "Status" app or [[Today|similar]] with multiple small windows aka gadgets / widgets that report different stats e.g. ssh (for irc), SMS, missed calls, next calendar entries, profile, tv programme etc, [http://en.wikipedia.org/wiki/Digital_video_recorder DVR] status
* Switch to "status" app automatically if user idles long enough
* [[Calendar]]
* automatic (weekly or calender-based) and [[Clock|manual alarm clock]]
* [[Profiles|Profile]] changes:
** programmable - time, location & calendar based
** manual profile override with timeout - cinema, sleep, meeting
* allow use of event (incoming phone call, sms message etc) metadata (who called, what time) to override profile settings
* screensaver that shuts the screen completely off, not just the backlight
** one click in screensaver mode -> screen in "on" mode but backlight still off, tune X color settings so that the contrast is increased to improve readbility
** second click -> backlight on as well, color settings back to normal
* SMS writing with [[Applications#Finger-Based_Applications | fingers]] - maybe some basic 123 456 789 *0# [[Input Method|onscreen keyboard]] with [http://en.wikipedia.org/wiki/T9_(predictive_text) T9] or similar
* one-click publishing of pictures taken with external digital camera to home web server

Hopefully my skills will let me implement at least some of these :)

Feel free to comment anything on the [[User_talk:Xkr47|talk page]].

Flashing the Neo 1973

2007-08-10T06:22:02Z

Xkr47: /* Preparing the device for DFU mode */

This describes how to update your openmoko to the latest software. We'll update the kernel, the root filesystem and optionally u-boot.

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

== Files to download ==

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

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

Necessary files are at:
*http://buildhost.openmoko.org/tmp/deploy/images/

*http://chooseopen.com/openmoko/build/ (Unofficial, temporary location of more current builds.)

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

== Preparing the device for DFU mode ==

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

* Unplug all usb devices from the host.
* Hold [[Neo1973 AUX Button]] while pressing POWER button.
* The uboot menu should appear.
* Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

Note: Some devices have been reported to turn off after a short period of inactivity while on the uboot menu. To avoid this, simply press the AUX button every 30 seconds or so.

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

== Actually flashing things into the device ==

Double check that u-boot matches your hardware version. Flashing u-boot is really a critical part. You probably only want to do that on phase0 phones.

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

Note: Option -a also accepts symbolic names ("u-boot", "u-boot_env", "kernel", "splash", "rootfs")

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

To update u-boot:

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

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

To update the kernel:
./dfu-util -a 3 -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin

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

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

If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first:

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

Old versions of uboot are buggy: You may have to press the aux button few times so that machine does not sleep while flashing. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase clean rootfs . Unfortunately, old versions of uboot are not really usable, because they fail to enable high 64MB of RAM, and you get nasty crashes after kernel boots.

Good luck!

== Troubleshooting notes ==

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

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

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

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

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

[[Category:OpenMoko| ]]

Flashing the Neo 1973

2007-08-10T06:20:48Z

Xkr47: /* Putting the device into DFU mode */ Added comment that no menu option selection is necessary to proceed with the flashing

This describes how to update your openmoko to the latest software. We'll update the kernel, the root filesystem and optionally u-boot.

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

== Files to download ==

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

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

Necessary files are at:
*http://buildhost.openmoko.org/tmp/deploy/images/

*http://chooseopen.com/openmoko/build/ (Unofficial, temporary location of more current builds.)

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

== Preparing the device for DFU mode ==

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

* Unplug all usb devices from the host.
* Hold [[Neo1973 AUX Button]] while pressing POWER button.
* The uboot menu should appear.
* Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

Note: Some devices have been reported to turn off after a short period of inactivity while on the uboot menu. To avoid this, simply press the AUX button every 30 seconds or so.

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

== Actually flashing things into the device ==

Double check that u-boot matches your hardware version. Flashing u-boot is really a critical part. You probably only want to do that on phase0 phones.

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

Note: Option -a also accepts symbolic names ("u-boot", "u-boot_env", "kernel", "splash", "rootfs")

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

To update u-boot:

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

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

To update the kernel:
./dfu-util -a 3 -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin

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

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

If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first:

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

Old versions of uboot are buggy: You may have to press the aux button few times so that machine does not sleep while flashing. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase clean rootfs . Unfortunately, old versions of uboot are not really usable, because they fail to enable high 64MB of RAM, and you get nasty crashes after kernel boots.

Good luck!

== Troubleshooting notes ==

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

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

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

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

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

[[Category:OpenMoko| ]]

Flashing the Neo 1973

2007-08-10T06:14:56Z

Xkr47: /* Files to download */ Added note about the system possibly booting up fine even when kernel <-> rootfs version mismatch

This describes how to update your openmoko to the latest software. We'll update the kernel, the root filesystem and optionally u-boot.

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

== Files to download ==

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

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

Necessary files are at:
*http://buildhost.openmoko.org/tmp/deploy/images/

*http://chooseopen.com/openmoko/build/ (Unofficial, temporary location of more current builds.)

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

== Putting the device into DFU mode ==

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

* Unplug all usb devices from the host.
* Hold [[Neo1973 AUX Button]] while pressing POWER button.
* The uboot menu should appear.
* Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

Note: Some devices have been reported to turn off after a short period of inactivity while on the uboot menu. To avoid this, simply press the AUX button every 30 seconds or so.

== Actually flashing things into the device ==

Double check that u-boot matches your hardware version. Flashing u-boot is really a critical part. You probably only want to do that on phase0 phones.

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

Note: Option -a also accepts symbolic names ("u-boot", "u-boot_env", "kernel", "splash", "rootfs")

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

To update u-boot:

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

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

To update the kernel:
./dfu-util -a 3 -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin

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

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

If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first:

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

Old versions of uboot are buggy: You may have to press the aux button few times so that machine does not sleep while flashing. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase clean rootfs . Unfortunately, old versions of uboot are not really usable, because they fail to enable high 64MB of RAM, and you get nasty crashes after kernel boots.

Good luck!

== Troubleshooting notes ==

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

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

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

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

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

[[Category:OpenMoko| ]]

Flashing the Neo 1973

2007-08-10T06:12:01Z

Xkr47: /* Files to download */ engrish

This describes how to update your openmoko to the latest software. We'll update the kernel, the root filesystem and optionally u-boot.

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

== Files to download ==

The rootfs & kernel images you download need to match. The loadable modules for the kernel are in /lib/modules/ on the rootfs partition - if you get the wrong combination, you will get some error messages during bootup that it cannot access /lib/modules/x.y.z-moko123 - in this case swap either the kernel or the rootfs to match the other's version. Unfortunately the rootfs filename does not seem to tell what kernel version it is compatible with.

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

Necessary files are at:
*http://buildhost.openmoko.org/tmp/deploy/images/

*http://chooseopen.com/openmoko/build/ (Unofficial, temporary location of more current builds.)

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

== Putting the device into DFU mode ==

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

* Unplug all usb devices from the host.
* Hold [[Neo1973 AUX Button]] while pressing POWER button.
* The uboot menu should appear.
* Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

Note: Some devices have been reported to turn off after a short period of inactivity while on the uboot menu. To avoid this, simply press the AUX button every 30 seconds or so.

== Actually flashing things into the device ==

Double check that u-boot matches your hardware version. Flashing u-boot is really a critical part. You probably only want to do that on phase0 phones.

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

Note: Option -a also accepts symbolic names ("u-boot", "u-boot_env", "kernel", "splash", "rootfs")

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

To update u-boot:

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

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

To update the kernel:
./dfu-util -a 3 -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin

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

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

If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first:

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

Old versions of uboot are buggy: You may have to press the aux button few times so that machine does not sleep while flashing. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase clean rootfs . Unfortunately, old versions of uboot are not really usable, because they fail to enable high 64MB of RAM, and you get nasty crashes after kernel boots.

Good luck!

== Troubleshooting notes ==

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

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

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

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

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

[[Category:OpenMoko| ]]

Flashing the Neo 1973

2007-08-10T06:11:22Z

Xkr47: /* Files to download */ Added comment that kernel version must match the rootfs kernel modules and some elaboration.

This describes how to update your openmoko to the latest software. We'll update the kernel, the root filesystem and optionally u-boot.

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

== Files to download ==

The rootfs & kernel images you download need to match. The loadable modules for the kernel are on the rootfs partition in /lib/modules/ - if you get the wrong combination, you will get some error messages during bootup that it cannot access /lib/modules/x.y.z-moko123 - in this case swap either the kernel or the rootfs to match the other's version. Unfortunately the rootfs filename does not seem to tell what kernel version it is compatible with.

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

Necessary files are at:
*http://buildhost.openmoko.org/tmp/deploy/images/

*http://chooseopen.com/openmoko/build/ (Unofficial, temporary location of more current builds.)

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

== Putting the device into DFU mode ==

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

* Unplug all usb devices from the host.
* Hold [[Neo1973 AUX Button]] while pressing POWER button.
* The uboot menu should appear.
* Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

Note: Some devices have been reported to turn off after a short period of inactivity while on the uboot menu. To avoid this, simply press the AUX button every 30 seconds or so.

== Actually flashing things into the device ==

Double check that u-boot matches your hardware version. Flashing u-boot is really a critical part. You probably only want to do that on phase0 phones.

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

Note: Option -a also accepts symbolic names ("u-boot", "u-boot_env", "kernel", "splash", "rootfs")

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

To update u-boot:

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

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

To update the kernel:
./dfu-util -a 3 -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin

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

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

If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first:

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

Old versions of uboot are buggy: You may have to press the aux button few times so that machine does not sleep while flashing. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase clean rootfs . Unfortunately, old versions of uboot are not really usable, because they fail to enable high 64MB of RAM, and you get nasty crashes after kernel boots.

Good luck!

== Troubleshooting notes ==

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

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

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

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

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

[[Category:OpenMoko| ]]

Getting Started with your Neo 1973

2007-08-09T23:11:35Z

Xkr47: /* Setting date and time */ added comment about screensaver possibly turning on when changing time

Some first steps guide for those who have just received their first Neo1973 hardware

== Hardware ==

=== Inserting the battery ===

Remove the back cover (see just the first step of [[Disassembling Neo1973]]).

See notes below on inserting the SIM, the SD card, and the battery (this page needs to be reorganized).

=== Powering up the phone ===
[[Image:Neo1973_uboot_splash.jpg|200px|thumb|bootloader splash screen]]
Just hitting the power button (depending on your [[u-boot]] version you have to press for >= 5 seconds) should get the phone first into the bootloader, then boot the kernel, and get into X/OpenMoko. The shipped battery typically has enough charge to boot up directly without charging through the usb cable first.

Once you have pressed the power button sufficiently long, the vibrator makes a short pulse and the screen backlight turns on. You can now release the power button and watch the phone booting.

If the battery is not sufficiently charged, the phone will not turn on, even if the usb cable is plugged in.

=== Flashing the Neo1973 GTA01Bv4 ===
The GTA01Bv4 devices that are currently shipping do not boot out of the box. Flashing the phone with the latest kernel and supporting file system ("rootfs") is required before the phone will successfully boot.

Read more information at about [[Flashing openmoko]].

=== Powering down the phone ===

==== While in bootloader mode, or if the phone has crashed ====

If you press the power button for 9 seconds, the phone will switch off. You can notice this by the backlight going dark.

==== While running a full linux system with userspace ====

In this mode, a power-button press of 5 seconds will be sufficient. After this, the init process will take care of safely shutting down the phone, which might take up to 20 extra seconds. The X server should get killed, you should drop back to a (garbled) console, and it should finally switch off - much like a regular Linux PC.

=== Battery charging ===

The [[Neo1973]] supports two charging modes: One 100mA charge mode (called pre-charge) and 500mA (called fast charge). Charging is always done via the USB socket. You can use any USB-A to USB-mini-B cable to connect the phone to any USB host.

==== While in u-boot ====

While you are in u-boot mode, the phone only charges with 100mA by default. (This will change in one of the future revisions).

However, using the u-boot console you can manually enable fast charging. See [[U-boot#Battery_charger_related]] for more information.

==== While in Linux ====

As soon as the phone is connected via USB cable, it will charge. However, the default charging current is only 100mA, way too little if you want to operate the phone and charge at the same time.

If your USB upstream port is capable of supplying 500mA, then it will configure the Neo1973 accordingly and use 500mA charging mode. You can notice this by the following line in the kernel log (/var/log/messages) of the laptop/desktop your Neo1973 is hooked up to
usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet

=== Inserting the SIM card (optional) ===

The slot is found just under the battery. The card holder has arrows indicating which way to push it to unlock it - make sure you don't open it with force when it's locked or it may break. Insert the SIM so that the pads make contact and push the holder firmly until it makes a click, then lock it - otherwise the card will not be detected.

To check if the SIM card is inserted correctly in Linux, you can have a look in gsmd logs or use the instructions detailed in the [[Manually using GSM]] page and issue the ''AT+CIMI'' command.

=== Using your micro-SD card ===

You should have received a memory card with your phone. You might want to copy some mp3 (or better Ogg Vorbis) files to it to try media playback.

Open the SIM card holder (see above) and gently slide the micro-SD shield toward the battery contacts. Lift up the shield and insert the card, contacts first and away from the shield side. Rotate it shut and gently slide the shield away from the battery contacts to lock it closed.

The card should automatically be available under /media/card the next time you boot. You can test it and your audio drivers at the same time by playing an mp3 from it. See [[Neo1973 Audio Subsystem]].

A small video howto (SIM and microSD) is available on google video: http://video.google.de/videoplay?docid=-8343770443102960945

== Getting shell access on the phone ==

=== By using the terminal emulator and on-screen keyboard ===

"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.

With newer images, the keyboard comes up when you tap the white box in the top bar.

You can choose between different keyboard layouts and the stroke recognizer by dragging from the white box and releasing it to the right of the box.

From the desktop, choose "Active tasks->rxvt" to get a root shell.

[[Terminal]] is in the top level menu in recent images.

=== By using Ethernet emulation over a USB cable ===

The standard Neo1973 Linux [[kernel]] has support for the "cdc_ether USB gadget", i.e. a standard implementation of how to emulate an Ethernet device over USB.

As soon as the kernel is up and running, and you have the phone connected via USB, you should get a '''usb0''' device on your host.

The Phone will have the IPv4 address 192.168.0.202/24. You can run `ifconfig` in the terminal on the phone to verify this (this is optional, just check it if it doesn't work given the instructions below)

If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear.

On the '''host PC''', you should then configure your interface to 192.168.0.200 by using
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then you should be able to
# ping 192.168.0.202

and last, but not least
# ssh root@192.168.0.202

Once you press 'enter' (empty password), you should now have a root login.

See [[USB_Networking]] for more details, including instructions on how to automatically setup masquerading so that your phone can get access to the internet through the host PC.

=== By using the debug board/serial/JTAG ===

Please see [[Debug Board#Usage_Instructions]]

== Getting access to the bootloader console ==

Please see [[u-boot#Using_usbtty_from_Linux]]

== Using Audio ==
=== Enable Internal Speaker and Mic in Phone Calls ===
If you got no Speaker and Mic during a Call you need to load the "gsmhandset.state" alsa-configfile

alsactl -f /etc/alsa/gsmhandset.state restore

Maybe you need to load another .state file for playing mp3 or a BT-Headset see in /etc/alsa/

To hear something you can find an .au file (or convert a .wav into an .au by using the sox tool):

sox ringtone_thereisnophone.wav -t raw -r 8012 -u -b -c 1 rigtone_thereisnophone.au

copy it to the device and run

cat ringtone_thereisnophone.au > /dev/dsp

== Useful commands in Linux ==

=== Suspending ===

Writing "mem" into ''/sys/power/state'' tells Linux to suspend - it will enter a low power mode where only the GSM and RAM are powered up and the CPU sleeps. It will persist in this state until a wake-up event arrives. Some currently enabled wake-up events are: AUX or POWER key press, USB cable detect.

If you're connected over ssh, sshd will stop responding when the OS suspends, so to avoid locking up your ssh client, use the command
# (sleep 1; echo mem > /sys/power/state) & exit

=== Initial backup ===

After getting your new Neo1973 booted for the first time you might want to make a back up of the original flash chip contents on your PC, before you overwrite the flash with a custom image or just update to a newer build.

{{note|For phase 0 developers only (GTA01Bv4 shippment 0, '''not > 0 '''): This is a good idea because there are parts in the root filesystem that can't be distributed over internet so they are only found in the shipped ROM (see the [[GPS]] driver).}}

One easy way to back up all of the Flash, that doesn't require installing any special software, is with ''netcat'' over the [[USB Networking|USB ethernet]]. The following commands can be used for that.
{|
! On the host !! On the target
|-
|<pre>
$ netcat -l -p 20000 > mtdblock0
$ netcat -l -p 20000 > mtdblock1
$ netcat -l -p 20000 > mtdblock2
$ netcat -l -p 20000 > mtdblock3
$ netcat -l -p 20000 > mtdblock4
</pre>
|<pre>
# cat /dev/mtdblock0 | nc 192.168.0.200 20000
# cat /dev/mtdblock1 | nc 192.168.0.200 20000
# cat /dev/mtdblock2 | nc 192.168.0.200 20000
# cat /dev/mtdblock3 | nc 192.168.0.200 20000
# cat /dev/mtdblock4 | nc 192.168.0.200 20000
</pre>
|}

This stores the five NAND partitions in files named mtdblock*. Knowing the partition layout (u-boot "mtdparts" command or Linux dmesg) you can restore the whole flash with it.

=== Setting date and time ===

To set the date and time you need to open a terminal or ssh to the device. To set the date and time to August 9 19:02 2007 type:

# date -s 080919022007

The screensaver might turn on as you execute this command - just tap the screen to get back.

Now, you need to synchronize the time with the hardware date/time by typing:

# hwclock --systohc

=== Where to from here ===

You'll probably want to play with some of the interesting hardware in this device. Obviously, you can explore the applications available through the touch-screen interface. But for those who prefer doing things more in the raw from a shell prompt, you can [[Manually_using_GSM | manually use GSM]], [[Manually_using_SMS | manually use SMS]], or you can start playing with the [[GPS]].

{{Languages|Getting_Started_with_your_Neo1973}}

[[Category:Documentation]]
[[Category:Neo1973_Phase_1_related]]

Getting Started with your Neo 1973

2007-08-09T23:06:16Z

Xkr47: /* By using the terminal emulator and on-screen keyboard */ Keyboard layout changing and link to Terminal app

Some first steps guide for those who have just received their first Neo1973 hardware

== Hardware ==

=== Inserting the battery ===

Remove the back cover (see just the first step of [[Disassembling Neo1973]]).

See notes below on inserting the SIM, the SD card, and the battery (this page needs to be reorganized).

=== Powering up the phone ===
[[Image:Neo1973_uboot_splash.jpg|200px|thumb|bootloader splash screen]]
Just hitting the power button (depending on your [[u-boot]] version you have to press for >= 5 seconds) should get the phone first into the bootloader, then boot the kernel, and get into X/OpenMoko. The shipped battery typically has enough charge to boot up directly without charging through the usb cable first.

Once you have pressed the power button sufficiently long, the vibrator makes a short pulse and the screen backlight turns on. You can now release the power button and watch the phone booting.

If the battery is not sufficiently charged, the phone will not turn on, even if the usb cable is plugged in.

=== Flashing the Neo1973 GTA01Bv4 ===
The GTA01Bv4 devices that are currently shipping do not boot out of the box. Flashing the phone with the latest kernel and supporting file system ("rootfs") is required before the phone will successfully boot.

Read more information at about [[Flashing openmoko]].

=== Powering down the phone ===

==== While in bootloader mode, or if the phone has crashed ====

If you press the power button for 9 seconds, the phone will switch off. You can notice this by the backlight going dark.

==== While running a full linux system with userspace ====

In this mode, a power-button press of 5 seconds will be sufficient. After this, the init process will take care of safely shutting down the phone, which might take up to 20 extra seconds. The X server should get killed, you should drop back to a (garbled) console, and it should finally switch off - much like a regular Linux PC.

=== Battery charging ===

The [[Neo1973]] supports two charging modes: One 100mA charge mode (called pre-charge) and 500mA (called fast charge). Charging is always done via the USB socket. You can use any USB-A to USB-mini-B cable to connect the phone to any USB host.

==== While in u-boot ====

While you are in u-boot mode, the phone only charges with 100mA by default. (This will change in one of the future revisions).

However, using the u-boot console you can manually enable fast charging. See [[U-boot#Battery_charger_related]] for more information.

==== While in Linux ====

As soon as the phone is connected via USB cable, it will charge. However, the default charging current is only 100mA, way too little if you want to operate the phone and charge at the same time.

If your USB upstream port is capable of supplying 500mA, then it will configure the Neo1973 accordingly and use 500mA charging mode. You can notice this by the following line in the kernel log (/var/log/messages) of the laptop/desktop your Neo1973 is hooked up to
usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet

=== Inserting the SIM card (optional) ===

The slot is found just under the battery. The card holder has arrows indicating which way to push it to unlock it - make sure you don't open it with force when it's locked or it may break. Insert the SIM so that the pads make contact and push the holder firmly until it makes a click, then lock it - otherwise the card will not be detected.

To check if the SIM card is inserted correctly in Linux, you can have a look in gsmd logs or use the instructions detailed in the [[Manually using GSM]] page and issue the ''AT+CIMI'' command.

=== Using your micro-SD card ===

You should have received a memory card with your phone. You might want to copy some mp3 (or better Ogg Vorbis) files to it to try media playback.

Open the SIM card holder (see above) and gently slide the micro-SD shield toward the battery contacts. Lift up the shield and insert the card, contacts first and away from the shield side. Rotate it shut and gently slide the shield away from the battery contacts to lock it closed.

The card should automatically be available under /media/card the next time you boot. You can test it and your audio drivers at the same time by playing an mp3 from it. See [[Neo1973 Audio Subsystem]].

A small video howto (SIM and microSD) is available on google video: http://video.google.de/videoplay?docid=-8343770443102960945

== Getting shell access on the phone ==

=== By using the terminal emulator and on-screen keyboard ===

"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.

With newer images, the keyboard comes up when you tap the white box in the top bar.

You can choose between different keyboard layouts and the stroke recognizer by dragging from the white box and releasing it to the right of the box.

From the desktop, choose "Active tasks->rxvt" to get a root shell.

[[Terminal]] is in the top level menu in recent images.

=== By using Ethernet emulation over a USB cable ===

The standard Neo1973 Linux [[kernel]] has support for the "cdc_ether USB gadget", i.e. a standard implementation of how to emulate an Ethernet device over USB.

As soon as the kernel is up and running, and you have the phone connected via USB, you should get a '''usb0''' device on your host.

The Phone will have the IPv4 address 192.168.0.202/24. You can run `ifconfig` in the terminal on the phone to verify this (this is optional, just check it if it doesn't work given the instructions below)

If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear.

On the '''host PC''', you should then configure your interface to 192.168.0.200 by using
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then you should be able to
# ping 192.168.0.202

and last, but not least
# ssh root@192.168.0.202

Once you press 'enter' (empty password), you should now have a root login.

See [[USB_Networking]] for more details, including instructions on how to automatically setup masquerading so that your phone can get access to the internet through the host PC.

=== By using the debug board/serial/JTAG ===

Please see [[Debug Board#Usage_Instructions]]

== Getting access to the bootloader console ==

Please see [[u-boot#Using_usbtty_from_Linux]]

== Using Audio ==
=== Enable Internal Speaker and Mic in Phone Calls ===
If you got no Speaker and Mic during a Call you need to load the "gsmhandset.state" alsa-configfile

alsactl -f /etc/alsa/gsmhandset.state restore

Maybe you need to load another .state file for playing mp3 or a BT-Headset see in /etc/alsa/

To hear something you can find an .au file (or convert a .wav into an .au by using the sox tool):

sox ringtone_thereisnophone.wav -t raw -r 8012 -u -b -c 1 rigtone_thereisnophone.au

copy it to the device and run

cat ringtone_thereisnophone.au > /dev/dsp

== Useful commands in Linux ==

=== Suspending ===

Writing "mem" into ''/sys/power/state'' tells Linux to suspend - it will enter a low power mode where only the GSM and RAM are powered up and the CPU sleeps. It will persist in this state until a wake-up event arrives. Some currently enabled wake-up events are: AUX or POWER key press, USB cable detect.

If you're connected over ssh, sshd will stop responding when the OS suspends, so to avoid locking up your ssh client, use the command
# (sleep 1; echo mem > /sys/power/state) & exit

=== Initial backup ===

After getting your new Neo1973 booted for the first time you might want to make a back up of the original flash chip contents on your PC, before you overwrite the flash with a custom image or just update to a newer build.

{{note|For phase 0 developers only (GTA01Bv4 shippment 0, '''not > 0 '''): This is a good idea because there are parts in the root filesystem that can't be distributed over internet so they are only found in the shipped ROM (see the [[GPS]] driver).}}

One easy way to back up all of the Flash, that doesn't require installing any special software, is with ''netcat'' over the [[USB Networking|USB ethernet]]. The following commands can be used for that.
{|
! On the host !! On the target
|-
|<pre>
$ netcat -l -p 20000 > mtdblock0
$ netcat -l -p 20000 > mtdblock1
$ netcat -l -p 20000 > mtdblock2
$ netcat -l -p 20000 > mtdblock3
$ netcat -l -p 20000 > mtdblock4
</pre>
|<pre>
# cat /dev/mtdblock0 | nc 192.168.0.200 20000
# cat /dev/mtdblock1 | nc 192.168.0.200 20000
# cat /dev/mtdblock2 | nc 192.168.0.200 20000
# cat /dev/mtdblock3 | nc 192.168.0.200 20000
# cat /dev/mtdblock4 | nc 192.168.0.200 20000
</pre>
|}

This stores the five NAND partitions in files named mtdblock*. Knowing the partition layout (u-boot "mtdparts" command or Linux dmesg) you can restore the whole flash with it.

=== Setting date and time ===

To set the date and time you need to open a terminal or ssh to the device. To set the date and time to August 9 19:02 2007 type:

# date -s 080919022007

Now, you need to synchronize the time with the hardware date/time by typing:

# hwclock --systohc

=== Where to from here ===

You'll probably want to play with some of the interesting hardware in this device. Obviously, you can explore the applications available through the touch-screen interface. But for those who prefer doing things more in the raw from a shell prompt, you can [[Manually_using_GSM | manually use GSM]], [[Manually_using_SMS | manually use SMS]], or you can start playing with the [[GPS]].

{{Languages|Getting_Started_with_your_Neo1973}}

[[Category:Documentation]]
[[Category:Neo1973_Phase_1_related]]

Getting Started with your Neo 1973

2007-08-09T16:02:11Z

Xkr47: /* Powering up the phone */ added note that battery typically has enough charge when shipped to boot up.

Some first steps guide for those who have just received their first Neo1973 hardware

== Hardware ==

=== Inserting the battery ===

Remove the back cover (see just the first step of [[Disassembling Neo1973]]).

See notes below on inserting the SIM, the SD card, and the battery (this page needs to be reorganized).

=== Powering up the phone ===
[[Image:Neo1973_uboot_splash.jpg|200px|thumb|bootloader splash screen]]
Just hitting the power button (depending on your [[u-boot]] version you have to press for >= 5 seconds) should get the phone first into the bootloader, then boot the kernel, and get into X/OpenMoko. The shipped battery typically has enough charge to boot up directly without charging through the usb cable first.

Once you have pressed the power button sufficiently long, the vibrator makes a short pulse and the screen backlight turns on. You can now release the power button and watch the phone booting.

If the battery is not sufficiently charged, the phone will not turn on, even if the usb cable is plugged in.

=== Flashing the Neo1973 GTA01Bv4 ===
The GTA01Bv4 devices that are currently shipping do not boot out of the box. Flashing the phone with the latest kernel and supporting file system ("rootfs") is required before the phone will successfully boot.

Read more information at about [[Flashing openmoko]].

=== Powering down the phone ===

==== While in bootloader mode, or if the phone has crashed ====

If you press the power button for 9 seconds, the phone will switch off. You can notice this by the backlight going dark.

==== While running a full linux system with userspace ====

In this mode, a power-button press of 5 seconds will be sufficient. After this, the init process will take care of safely shutting down the phone, which might take up to 20 extra seconds. The X server should get killed, you should drop back to a (garbled) console, and it should finally switch off - much like a regular Linux PC.

=== Battery charging ===

The [[Neo1973]] supports two charging modes: One 100mA charge mode (called pre-charge) and 500mA (called fast charge). Charging is always done via the USB socket. You can use any USB-A to USB-mini-B cable to connect the phone to any USB host.

==== While in u-boot ====

While you are in u-boot mode, the phone only charges with 100mA by default. (This will change in one of the future revisions).

However, using the u-boot console you can manually enable fast charging. See [[U-boot#Battery_charger_related]] for more information.

==== While in Linux ====

As soon as the phone is connected via USB cable, it will charge. However, the default charging current is only 100mA, way too little if you want to operate the phone and charge at the same time.

If your USB upstream port is capable of supplying 500mA, then it will configure the Neo1973 accordingly and use 500mA charging mode. You can notice this by the following line in the kernel log (/var/log/messages) of the laptop/desktop your Neo1973 is hooked up too
usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet

=== Inserting the SIM card (optional) ===

The slot is found just under the battery. The card holder has arrows indicating which way to push it to unlock it - make sure you don't open it with force when it's locked or it may break. Insert the SIM so that the pads make contact and push the holder firmly until it makes a click, then lock it - otherwise the card will not be detected.

To check if the SIM card is inserted correctly in Linux, you can have a look in gsmd logs or use the instructions detailed in the [[Manually using GSM]] page and issue the ''AT+CIMI'' command.

=== Using your micro-SD card ===

You should have received a memory card with your phone. You might want to copy some mp3 (or better Ogg Vorbis) files to it to try media playback.

Open the SIM card holder (see above) and gently slide the micro-SD shield toward the battery contacts. Lift up the shield and insert the card, contacts first and away from the shield side. Rotate it shut and gently slide the shield away from the battery contacts to lock it closed.

The card should automatically be available under /media/card the next time you boot. You can test it and your audio drivers at the same time by playing an mp3 from it. See [[Neo1973 Audio Subsystem]].

A small video howto (SIM and microSD) is available on google video: http://video.google.de/videoplay?docid=-8343770443102960945

== Getting shell access on the phone ==

=== By using the terminal emulator and on-screen keyboard ===

"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.

With newer images, the keyboard comes up when you tap the white box in the top bar.

From the desktop, choose "Active tasks->rxvt" to get a root shell.

Terminal is in the top level menu in recent images.

=== By using Ethernet emulation over a USB cable ===

The standard Neo1973 Linux [[kernel]] has support for the "cdc_ether USB gadget", i.e. a standard implementation of how to emulate an Ethernet device over USB.

As soon as the kernel is up and running, and you have the phone connected via USB, you should get a '''usb0''' device on your host.

The Phone will have the IPv4 address 192.168.0.202/24. You can run `ifconfig` in the terminal on the phone to verify this (this is optional, just check it if it doesn't work given the instructions below)

If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear.

On the '''host PC''', you should then configure your interface to 192.168.0.200 by using
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then you should be able to
# ping 192.168.0.202

and last, but not least
# ssh root@192.168.0.202

Once you press 'enter' (empty password), you should now have a root login.

See [[USB_Networking]] for more details, including instructions on how to automatically setup masquerading so that your phone can get access to the internet through the host PC.

=== By using the debug board/serial/JTAG ===

Please see [[Debug Board#Usage_Instructions]]

== Getting access to the bootloader console ==

Please see [[u-boot#Using_usbtty_from_Linux]]

== Using Audio ==
=== Enable Internal Speaker and Mic in Phone Calls ===
If you got no Speaker and Mic during a Call you need to load the "gsmhandset.state" alsa-configfile

alsactl -f /etc/alsa/gsmhandset.state restore

Maybe you need to load another .state file for playing mp3 or a BT-Headset see in /etc/alsa/

== Useful commands in Linux ==

=== Suspending ===

Writing "mem" into ''/sys/power/state'' tells Linux to suspend - it will enter a low power mode where only the GSM and RAM are powered up and the CPU sleeps. It will persist in this state until a wake-up event arrives. Some currently enabled wake-up events are: AUX or POWER key press, USB cable detect.

If you're connected over ssh, sshd will stop responding when the OS suspends, so to avoid locking up your ssh client, use the command
# (sleep 1; echo mem > /sys/power/state) & exit

=== Initial backup ===

After getting your new Neo1973 booted for the first time you might want to make a back up of the original flash chip contents on your PC, before you overwrite the flash with a custom image or just update to a newer build.

{{note|For phase 0 developers only (GTA01Bv4 shippment 0, '''not > 0 '''): This is a good idea because there are parts in the root filesystem that can't be distributed over internet so they are only found in the shipped ROM (see the [[GPS]] driver).}}

One easy way to back up all of the Flash, that doesn't require installing any special software, is with ''netcat'' over the [[USB Networking|USB ethernet]]. The following commands can be used for that.
{|
! On the host !! On the target
|-
|<pre>
$ netcat -l -p 20000 > mtdblock0
$ netcat -l -p 20000 > mtdblock1
$ netcat -l -p 20000 > mtdblock2
$ netcat -l -p 20000 > mtdblock3
$ netcat -l -p 20000 > mtdblock4
</pre>
|<pre>
# cat /dev/mtdblock0 | nc 192.168.0.200 20000
# cat /dev/mtdblock1 | nc 192.168.0.200 20000
# cat /dev/mtdblock2 | nc 192.168.0.200 20000
# cat /dev/mtdblock3 | nc 192.168.0.200 20000
# cat /dev/mtdblock4 | nc 192.168.0.200 20000
</pre>
|}

This stores the five NAND partitions in files named mtdblock*. Knowing the partition layout (u-boot "mtdparts" command or Linux dmesg) you can restore the whole flash with it.

=== Where to from here ===

You'll probably want to play with some of the interesting hardware in this device. Obviously, you can explore the applications available through the touch-screen interface. But for those who prefer doing things more in the raw from a shell prompt, you can [[Manually_using_GSM | manually use GSM]], [[Manually_using_SMS | manually use SMS]], or you can start playing with the [[GPS]].

{{Languages|Getting_Started_with_your_Neo1973}}

[[Category:Documentation]]
[[Category:Neo1973_Phase_1_related]]

Openmoko Local Groups: Helsinki

2007-08-07T04:59:48Z

Xkr47: += xkr47

See [[Talk:OpenMoko_Local_Groups:_Helsinki|discussion]]

{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
|-
|Mikko Rauhala
|Sysadmin, networking, programming, propaganda
|Awaiting GTA01Bv4, Neo Advanced
|Pihlajisto, Helsinki
|Speaking about OpenMoko at FUUG cruise (tba) and Linux theme night (Nov. 14th)
|-
|[[User:csnellman|Carl Snellman]]
|Programming
|Application development/Location based services
|Helsinki (currently @ Palo Alto, CA, USA)
|-
|[[User:raynet|Allan Savolainen]]
|Sysadmin, networking, programming
|Development; Location Aware Applications, Interaction with cars (OBD-II)
|Near Lahti, office in Helsinki
|-
|[[User:Xkr47|Jonas Berlin]]
|Sysadmin, networking, programming
|Userspace-level framework & application hacking; communicating with other computers over bluetooth & gprs
|Perkkaa, Espoo
|}
[[Category:OpenMoko_Local_Groups:_Helsinki]]

User:Xkr47

2007-08-06T06:48:23Z

Xkr47: talk page link

Me:
* relationship with openmoko: [[Buying_Interest_List|phase 1 customer]]
* [http://xkr47.outerspace.dyndns.org/ my homepage]
* [http://sourceforge.net/people/viewprofile.php?user_id=66259 my computer-related skills]
* [http://www.google.com/search?q=xkr47+OR+jberlin%40niksula+OR+jberlin%40cc+OR+outerspace.dyndns.org my internet resumé]
*

Wishlist for my openmoko:

* basic telephony
* automatic [[Screen Saver|screensaver]] & locker
** require code/password/gesture to unlock
* [[Messages|SMS sending and reception]]
* SMS mirroring to home server
* remote GUI app connected to home server when SMS arrives / phone is ringing / other important event (battery low) in case I can't hear the phone when it's in my backpack
* MMS sending & reception - outgoing pics taken with external USB-connected digital camera
* Integration with local public transportation services which provides clickable maps --> GPS can be used to automatically "go home from wherever I happen to be"
* ssh client
* "Status" app or [[Today|similar]] with multiple small windows aka gadgets / widgets that report different stats e.g. ssh (for irc), SMS, missed calls, next calendar entries, profile, tv programme etc, [http://en.wikipedia.org/wiki/Digital_video_recorder DVR] status
* Switch to "status" app automatically if user idles long enough
* [[Calendar]]
* automatic (weekly or calender-based) and [[Clock|manual alarm clock]]
* [[Profiles|Profile]] changes:
** programmable - time, location & calendar based
** manual profile override with timeout - cinema, sleep, meeting
* allow use of event (incoming phone call, sms message etc) metadata (who called, what time) to override profile settings
* screensaver that shuts the screen completely off, not just the backlight
** one click in screensaver mode -> screen in "on" mode but backlight still off, tune X color settings so that the contrast is increased to improve readbility
** second click -> backlight on as well, color settings back to normal
* SMS writing with [[Applications#Finger-Based_Applications | fingers]] - maybe some basic 123 456 789 *0# [[Input Method|onscreen keyboard]] with [http://en.wikipedia.org/wiki/T9_(predictive_text) T9] or similar
* one-click publishing of pictures taken with external digital camera to home web server

Hopefully my skills will let me implement at least some of these :)

Feel free to comment anything on the [[User_talk:Xkr47|talk page]].

IPhone (GTA01)

2007-07-09T07:04:16Z

Xkr47: Added release date

== Comparison between Apple iPhone and the "Open Source iPhone" Neo1973 ([http://wiki.openmoko.org/wiki/Neo1973#Phase_1_.28GTA01Bv4.29 (GTA01Bv4]) running OpenMoko Linux ==
{{Note|The Neo1973 revision this page is about is the [[Neo1973#Phase_1_.28GTA01Bv4.29|GTA01Bv4-revision]] that is announced for July 2007. For the later Neo1973 revision see [[IPhone|GTA02]]}}
Apple announced their [http://www.apple.com/iphone/technology/specs.html iPhone] at MacWorld 2007. It is fairly similar to the [http://lists.openmoko.org/pipermail/community/2007-January/001006.html FIC Neo1973] announced in the fall of 2006.

iPhone UI Demo on youtube http://youtube.com/watch?v=YgW7or1TuFk

{| border="1"
!Feature
!iPhone
!Neo1973
|-
|Announced
|2007-01-09
|2006-11-07
|-
|Dimensions [http://www.sizeasy.com/page/comp/153 visual comparison]
|115 x 61 x 11.6 mm
|120.7 x 62 x 18.5 mm
|-
|Weight
|135 g
|184 g
|-
|Screen
|3.5" 320x480 at 160 ppi, multi-touch
|2.8" 480x640 at 285 ppi, [http://lists.openmoko.org/pipermail/community/2006-December/000576.html maybe multi-touch later]
|-
|Storage
|4 or 8 GiB
|64 MB (expandable with [http://lists.openmoko.org/pipermail/community/2007-February/003156.html 2 GB microSD] - 512 MB microSD included in Standard Kit, 2 * 512 MB included in Advanced Kit)
|-
|CPU
|Possibly Marvell XScale PXA3xx family or [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S™] (with Coprocessor) (Source: [http://www.bitsundso.de/ Bits und so Podcast] [http://www.bitsundso.de/bus20/54/ #20], 8'40" to 9'30" [german language])
|Samsung s3c2410 SoC @ 266 MHz ([http://lists.openmoko.org/pipermail/announce/2007-January/000000.html Source])
|-
|RAM
|
|128MB
|-
|Wireless
|GSM, WiFi (b/g), EDGE, Bluetooth 2.0 EDR
|Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR in [[Neo1973|GTA01B_v04 and GTA02]]; WiFi: not in GTA01B_v4 but GTA02
|-
|Wireless Carrier
|Locked to Apple-selected carrier
|Unlocked - any GSM provider
|-
|Embedded devices
|2 mpix camera, 4 buttons (power, volume, ringer, main menu), [http://en.wikipedia.org/wiki/Accelerometer accelerometer], ambient light sensor, proximity sensor
|GPS, 2 buttons in [[Neo1973|GTA01B_v04 and GTA02]]
|-
|Operating system
|OS X ([http://www.macworld.co.uk/ipod-itunes/news/index.cfm?newsid=16927 an optimised but full version of OS X])
|[[OpenMoko]] Linux (Source code available)
|-
|Software
|Basic PDA + PMP software included. Software can only be created by authorized companies ([http://apple.slashdot.org/article.pl?sid=07/01/12/0430200&from=rss Source])
|Basic PDA included. Software can be created by normal users.
|-
|Video
|Playback and No recording(?)
|No recording. Maybe playback
|-
|Audio
|Playback and recording, stereo speaker
|Playback and recording, including playback of audio files via GSM and recording/playback of voice calls. [http://www.theinquirer.net/default.aspx?article=35590 2x1 watt stereo speaker] [http://gnumonks.org/~laforge/weblog/2007/01/24/ comment on performance], 2.5 mm jack
|-
|Connectors
|USB 2.0 on proprietary iPod connector
|Standard USB 1.1 (unpowered), with a Mini-B receptor (can be connected via adapter to both host and client devices), [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connector]] inside case in all versions and Debug Board v2 (JTAG and serial console) in Advanced version
|-
|Opening case
|[http://www.anandtech.com/printarticle.aspx?i=3026 voids warranty]
|[http://lists.openmoko.org/pipermail/announce/2007-June/000013.html Advanced version] comes with guitar pick and Torx T6 screwdriver so you can [[Disassembling Neo1973|open case]].
|-
|Battery
|Up to 5 hours Talk / Video / Browsing. Up to 16 hours Audio playback. Non-replaceable battery
|replaceable 1.2 Ah battery charged via USB - "We really have no idea how long it will last you because this is the first phone where you are in total control. Blast everything: GSM, GPS, Bluetooth, backlight, etc... and you should get about four hours, though." [http://www.openmoko.com/products-neo-base-00-stdkit.html quote (click on Battery menu link)]. (2 batteries included in Advanced version)
|-
|Ready for use
|Yes - Software still incomplete
|Yes
|-
|Ready for sale
|US: June 15, 2007, EU: 2007Q4, Asia: 2008
|July 9, 2007. Buy: https://direct.openmoko.com/
|-
|Price
|USD 499 for 4GiB version, 599 for 8GiB (2 year contract required)
|[[Neo1973_Hardware#GTA01Bv4|Phase 1 device (GTA01B_v04)]]: USD 300 (base model), USD 450 including additional development hardware [[Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|Phase 2 device (GTA02)]]: USD 450 (base), USD 600 (including development hardware)
|-
|Community
|?
|IRC: #openmoko on freenode.net [http://lists.openmoko.org/pipermail/community/ Discussion list], [[Main_Page|Wiki]], [http://lists.openmoko.org/mailman/listinfo/announce Be informed when it is sold]
|}
{{Languages|iPhone}}

IPhone (GTA01)

2007-07-09T06:59:04Z

Xkr47: Two batteries in adv version

== Comparison between Apple iPhone and the "Open Source iPhone" Neo1973 ([http://wiki.openmoko.org/wiki/Neo1973#Phase_1_.28GTA01Bv4.29 (GTA01Bv4]) running OpenMoko Linux ==
{{Note|The Neo1973 revision this page is about is the [[Neo1973#Phase_1_.28GTA01Bv4.29|GTA01Bv4-revision]] that is announced for July 2007. For the later Neo1973 revision see [[IPhone|GTA02]]}}
Apple announced their [http://www.apple.com/iphone/technology/specs.html iPhone] at MacWorld 2007. It is fairly similar to the [http://lists.openmoko.org/pipermail/community/2007-January/001006.html FIC Neo1973] announced in the fall of 2006.

iPhone UI Demo on youtube http://youtube.com/watch?v=YgW7or1TuFk

{| border="1"
!Feature
!iPhone
!Neo1973
|-
|Announced
|2007-01-09
|2006-11-07
|-
|Dimensions [http://www.sizeasy.com/page/comp/153 visual comparison]
|115 x 61 x 11.6 mm
|120.7 x 62 x 18.5 mm
|-
|Weight
|135 g
|184 g
|-
|Screen
|3.5" 320x480 at 160 ppi, multi-touch
|2.8" 480x640 at 285 ppi, [http://lists.openmoko.org/pipermail/community/2006-December/000576.html maybe multi-touch later]
|-
|Storage
|4 or 8 GiB
|64 MB (expandable with [http://lists.openmoko.org/pipermail/community/2007-February/003156.html 2 GB microSD] - 512 MB microSD included in Standard Kit, 2 * 512 MB included in Advanced Kit)
|-
|CPU
|Possibly Marvell XScale PXA3xx family or [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S™] (with Coprocessor) (Source: [http://www.bitsundso.de/ Bits und so Podcast] [http://www.bitsundso.de/bus20/54/ #20], 8'40" to 9'30" [german language])
|Samsung s3c2410 SoC @ 266 MHz ([http://lists.openmoko.org/pipermail/announce/2007-January/000000.html Source])
|-
|RAM
|
|128MB
|-
|Wireless
|GSM, WiFi (b/g), EDGE, Bluetooth 2.0 EDR
|Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR in [[Neo1973|GTA01B_v04 and GTA02]]; WiFi: not in GTA01B_v4 but GTA02
|-
|Wireless Carrier
|Locked to Apple-selected carrier
|Unlocked - any GSM provider
|-
|Embedded devices
|2 mpix camera, 4 buttons (power, volume, ringer, main menu), [http://en.wikipedia.org/wiki/Accelerometer accelerometer], ambient light sensor, proximity sensor
|GPS, 2 buttons in [[Neo1973|GTA01B_v04 and GTA02]]
|-
|Operating system
|OS X ([http://www.macworld.co.uk/ipod-itunes/news/index.cfm?newsid=16927 an optimised but full version of OS X])
|[[OpenMoko]] Linux (Source code available)
|-
|Software
|Basic PDA + PMP software included. Software can only be created by authorized companies ([http://apple.slashdot.org/article.pl?sid=07/01/12/0430200&from=rss Source])
|Basic PDA included. Software can be created by normal users.
|-
|Video
|Playback and No recording(?)
|No recording. Maybe playback
|-
|Audio
|Playback and recording, stereo speaker
|Playback and recording, including playback of audio files via GSM and recording/playback of voice calls. [http://www.theinquirer.net/default.aspx?article=35590 2x1 watt stereo speaker] [http://gnumonks.org/~laforge/weblog/2007/01/24/ comment on performance], 2.5 mm jack
|-
|Connectors
|USB 2.0 on proprietary iPod connector
|Standard USB 1.1 (unpowered), with a Mini-B receptor (can be connected via adapter to both host and client devices), [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connector]] inside case in all versions and Debug Board v2 (JTAG and serial console) in Advanced version
|-
|Opening case
|[http://www.anandtech.com/printarticle.aspx?i=3026 voids warranty]
|[http://lists.openmoko.org/pipermail/announce/2007-June/000013.html Advanced version] comes with guitar pick and Torx T6 screwdriver so you can [[Disassembling Neo1973|open case]].
|-
|Battery
|Up to 5 hours Talk / Video / Browsing. Up to 16 hours Audio playback. Non-replaceable battery
|replaceable 1.2 Ah battery charged via USB - "We really have no idea how long it will last you because this is the first phone where you are in total control. Blast everything: GSM, GPS, Bluetooth, backlight, etc... and you should get about four hours, though." [http://www.openmoko.com/products-neo-base-00-stdkit.html quote (click on Battery menu link)]. (2 batteries included in Advanced version)
|-
|Ready for use
|Yes - Software still incomplete
|Yes
|-
|Ready for sale
|US: June 15, 2007, EU: 2007Q4, Asia: 2008
|Buy: https://direct.openmoko.com/
|-
|Price
|USD 499 for 4GiB version, 599 for 8GiB (2 year contract required)
|[[Neo1973_Hardware#GTA01Bv4|Phase 1 device (GTA01B_v04)]]: USD 300 (base model), USD 450 including additional development hardware [[Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|Phase 2 device (GTA02)]]: USD 450 (base), USD 600 (including development hardware)
|-
|Community
|?
|IRC: #openmoko on freenode.net [http://lists.openmoko.org/pipermail/community/ Discussion list], [[Main_Page|Wiki]], [http://lists.openmoko.org/mailman/listinfo/announce Be informed when it is sold]
|}
{{Languages|iPhone}}

IPhone (GTA01)

2007-07-09T06:52:42Z

Xkr47: /* Comparison between Apple iPhone and the "Open Source iPhone" Neo1973 ([http://wiki.openmoko.org/wiki/Neo1973#Phase_1_.28GTA01Bv4.29 (GTA01Bv4]) running OpenMoko Linux */ added info about bonus mem

== Comparison between Apple iPhone and the "Open Source iPhone" Neo1973 ([http://wiki.openmoko.org/wiki/Neo1973#Phase_1_.28GTA01Bv4.29 (GTA01Bv4]) running OpenMoko Linux ==
{{Note|The Neo1973 revision this page is about is the [[Neo1973#Phase_1_.28GTA01Bv4.29|GTA01Bv4-revision]] that is announced for July 2007. For the later Neo1973 revision see [[IPhone|GTA02]]}}
Apple announced their [http://www.apple.com/iphone/technology/specs.html iPhone] at MacWorld 2007. It is fairly similar to the [http://lists.openmoko.org/pipermail/community/2007-January/001006.html FIC Neo1973] announced in the fall of 2006.

iPhone UI Demo on youtube http://youtube.com/watch?v=YgW7or1TuFk

{| border="1"
!Feature
!iPhone
!Neo1973
|-
|Announced
|2007-01-09
|2006-11-07
|-
|Dimensions [http://www.sizeasy.com/page/comp/153 visual comparison]
|115 x 61 x 11.6 mm
|120.7 x 62 x 18.5 mm
|-
|Weight
|135 g
|184 g
|-
|Screen
|3.5" 320x480 at 160 ppi, multi-touch
|2.8" 480x640 at 285 ppi, [http://lists.openmoko.org/pipermail/community/2006-December/000576.html maybe multi-touch later]
|-
|Storage
|4 or 8 GiB
|64 MB (expandable with [http://lists.openmoko.org/pipermail/community/2007-February/003156.html 2 GB microSD] - 512 MB microSD included in Standard Kit, 2 * 512 MB included in Advanced Kit)
|-
|CPU
|Possibly Marvell XScale PXA3xx family or [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S™] (with Coprocessor) (Source: [http://www.bitsundso.de/ Bits und so Podcast] [http://www.bitsundso.de/bus20/54/ #20], 8'40" to 9'30" [german language])
|Samsung s3c2410 SoC @ 266 MHz ([http://lists.openmoko.org/pipermail/announce/2007-January/000000.html Source])
|-
|RAM
|
|128MB
|-
|Wireless
|GSM, WiFi (b/g), EDGE, Bluetooth 2.0 EDR
|Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR in [[Neo1973|GTA01B_v04 and GTA02]]; WiFi: not in GTA01B_v4 but GTA02
|-
|Wireless Carrier
|Locked to Apple-selected carrier
|Unlocked - any GSM provider
|-
|Embedded devices
|2 mpix camera, 4 buttons (power, volume, ringer, main menu), [http://en.wikipedia.org/wiki/Accelerometer accelerometer], ambient light sensor, proximity sensor
|GPS, 2 buttons in [[Neo1973|GTA01B_v04 and GTA02]]
|-
|Operating system
|OS X ([http://www.macworld.co.uk/ipod-itunes/news/index.cfm?newsid=16927 an optimised but full version of OS X])
|[[OpenMoko]] Linux (Source code available)
|-
|Software
|Basic PDA + PMP software included. Software can only be created by authorized companies ([http://apple.slashdot.org/article.pl?sid=07/01/12/0430200&from=rss Source])
|Basic PDA included. Software can be created by normal users.
|-
|Video
|Playback and No recording(?)
|No recording. Maybe playback
|-
|Audio
|Playback and recording, stereo speaker
|Playback and recording, including playback of audio files via GSM and recording/playback of voice calls. [http://www.theinquirer.net/default.aspx?article=35590 2x1 watt stereo speaker] [http://gnumonks.org/~laforge/weblog/2007/01/24/ comment on performance], 2.5 mm jack
|-
|Connectors
|USB 2.0 on proprietary iPod connector
|Standard USB 1.1 (unpowered), with a Mini-B receptor (can be connected via adapter to both host and client devices), [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connector]] inside case in all versions and Debug Board v2 (JTAG and serial console) in Advanced version
|-
|Opening case
|[http://www.anandtech.com/printarticle.aspx?i=3026 voids warranty]
|[http://lists.openmoko.org/pipermail/announce/2007-June/000013.html Advanced version] comes with guitar pick and Torx T6 screwdriver so you can [[Disassembling Neo1973|open case]].
|-
|Battery
|Up to 5 hours Talk / Video / Browsing. Up to 16 hours Audio playback. Non-replaceable battery
|replaceable 1.2 Ah battery charged via USB - "We really have no idea how long it will last you because this is the first phone where you are in total control. Blast everything: GSM, GPS, Bluetooth, backlight, etc... and you should get about four hours, though." [http://www.openmoko.com/products-neo-base-00-stdkit.html quote (click on Battery menu link)]
|-
|Ready for use
|Yes - Software still incomplete
|Yes
|-
|Ready for sale
|US: June 15, 2007, EU: 2007Q4, Asia: 2008
|Buy: https://direct.openmoko.com/
|-
|Price
|USD 499 for 4GiB version, 599 for 8GiB (2 year contract required)
|[[Neo1973_Hardware#GTA01Bv4|Phase 1 device (GTA01B_v04)]]: USD 300 (base model), USD 450 including additional development hardware [[Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|Phase 2 device (GTA02)]]: USD 450 (base), USD 600 (including development hardware)
|-
|Community
|?
|IRC: #openmoko on freenode.net [http://lists.openmoko.org/pipermail/community/ Discussion list], [[Main_Page|Wiki]], [http://lists.openmoko.org/mailman/listinfo/announce Be informed when it is sold]
|}
{{Languages|iPhone}}

IPhone (GTA01)

2007-07-09T06:44:39Z

== Comparison between Apple iPhone and the "Open Source iPhone" Neo1973 ([http://wiki.openmoko.org/wiki/Neo1973#Phase_1_.28GTA01Bv4.29 (GTA01Bv4]) running OpenMoko Linux ==
{{Note|The Neo1973 revision this page is about is the [[Neo1973#Phase_1_.28GTA01Bv4.29|GTA01Bv4-revision]] that is announced for July 2007. For the later Neo1973 revision see [[IPhone|GTA02]]}}
Apple announced their [http://www.apple.com/iphone/technology/specs.html iPhone] at MacWorld 2007. It is fairly similar to the [http://lists.openmoko.org/pipermail/community/2007-January/001006.html FIC Neo1973] announced in the fall of 2006.

iPhone UI Demo on youtube http://youtube.com/watch?v=YgW7or1TuFk

{| border="1"
!Feature
!iPhone
!Neo1973
|-
|Announced
|2007-01-09
|2006-11-07
|-
|Dimensions [http://www.sizeasy.com/page/comp/153 visual comparison]
|115 x 61 x 11.6 mm
|120.7 x 62 x 18.5 mm
|-
|Weight
|135 g
|184 g
|-
|Screen
|3.5" 320x480 at 160 ppi, multi-touch
|2.8" 480x640 at 285 ppi, [http://lists.openmoko.org/pipermail/community/2006-December/000576.html maybe multi-touch later]
|-
|Storage
|4 or 8 GiB
|64 MB (expandable with [http://lists.openmoko.org/pipermail/community/2007-February/003156.html 2 GB microSD])]
|-
|CPU
|Possibly Marvell XScale PXA3xx family or [http://www.arm.com/products/CPUs/ARM1176.html ARM1176JZF-S™] (with Coprocessor) (Source: [http://www.bitsundso.de/ Bits und so Podcast] [http://www.bitsundso.de/bus20/54/ #20], 8'40" to 9'30" [german language])
|Samsung s3c2410 SoC @ 266 MHz ([http://lists.openmoko.org/pipermail/announce/2007-January/000000.html Source])
|-
|RAM
|
|128MB
|-
|Wireless
|GSM, WiFi (b/g), EDGE, Bluetooth 2.0 EDR
|Quad-band GSM, GPRS Class12/CS4 2.5G (Not EDGE), Bluetooth 2.0 EDR in [[Neo1973|GTA01B_v04 and GTA02]]; WiFi: not in GTA01B_v4 but GTA02
|-
|Wireless Carrier
|Locked to Apple-selected carrier
|Unlocked - any GSM provider
|-
|Embedded devices
|2 mpix camera, 4 buttons (power, volume, ringer, main menu), [http://en.wikipedia.org/wiki/Accelerometer accelerometer], ambient light sensor, proximity sensor
|GPS, 2 buttons in [[Neo1973|GTA01B_v04 and GTA02]]
|-
|Operating system
|OS X ([http://www.macworld.co.uk/ipod-itunes/news/index.cfm?newsid=16927 an optimised but full version of OS X])
|[[OpenMoko]] Linux (Source code available)
|-
|Software
|Basic PDA + PMP software included. Software can only be created by authorized companies ([http://apple.slashdot.org/article.pl?sid=07/01/12/0430200&from=rss Source])
|Basic PDA included. Software can be created by normal users.
|-
|Video
|Playback and No recording(?)
|No recording. Maybe playback
|-
|Audio
|Playback and recording, stereo speaker
|Playback and recording, including playback of audio files via GSM and recording/playback of voice calls. [http://www.theinquirer.net/default.aspx?article=35590 2x1 watt stereo speaker] [http://gnumonks.org/~laforge/weblog/2007/01/24/ comment on performance], 2.5 mm jack
|-
|Connectors
|USB 2.0 on proprietary iPod connector
|Standard USB 1.1 (unpowered), with a Mini-B receptor (can be connected via adapter to both host and client devices), [[Neo1973_Hardware#Changes_from_GTA01Bv3|exposed I2C, SPI and debug board connector]] inside case in all versions and Debug Board v2 (JTAG and serial console) in Advanced version
|-
|Opening case
|[http://www.anandtech.com/printarticle.aspx?i=3026 voids warranty]
|[http://lists.openmoko.org/pipermail/announce/2007-June/000013.html Advanced version] comes with guitar pick and Torx T6 screwdriver so you can [[Disassembling Neo1973|open case]].
|-
|Battery
|Up to 5 hours Talk / Video / Browsing. Up to 16 hours Audio playback. Non-replaceable battery
|replaceable 1.2 Ah battery charged via USB - "We really have no idea how long it will last you because this is the first phone where you are in total control. Blast everything: GSM, GPS, Bluetooth, backlight, etc... and you should get about four hours, though." [http://www.openmoko.com/products-neo-base-00-stdkit.html quote (click on Battery menu link)]
|-
|Ready for use
|Yes - Software still incomplete
|Yes
|-
|Ready for sale
|US: June 15, 2007, EU: 2007Q4, Asia: 2008
|Buy: https://direct.openmoko.com/
|-
|Price
|USD 499 for 4GiB version, 599 for 8GiB (2 year contract required)
|[[Neo1973_Hardware#GTA01Bv4|Phase 1 device (GTA01B_v04)]]: USD 300 (base model), USD 450 including additional development hardware [[Neo1973#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|Phase 2 device (GTA02)]]: USD 450 (base), USD 600 (including development hardware)
|-
|Community
|?
|IRC: #openmoko on freenode.net [http://lists.openmoko.org/pipermail/community/ Discussion list], [[Main_Page|Wiki]], [http://lists.openmoko.org/mailman/listinfo/announce Be informed when it is sold]
|}
{{Languages|iPhone}}

Advertising

2007-07-05T21:25:07Z

Xkr47: /* Video */ added missing 12th video ad by Adam

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

=== Printed Advertisement ===
...

== Video ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Disassembling Neo 1973

2007-05-05T15:26:57Z

Xkr47: /* Top case lid removed */ Added guess that there is a battery next to the aux button

{{note| The [[Disassembling Neo1973 | Disassembling the Neo1973 page]] shows how to open up the GTA01Bv3 hardware revision. Future hardare revisions may require updates to this page.}}

== Back side of Neo1973 ==
[[Image:Gta01b v3 case back white.jpg|700px]]

== Opening back cover ==

To remove the back cover, put your fingernail at the small recession on top of Neo, and pull a bit.

[[Image:Gta01b v3 case back open white.jpg|700px]]

{{note| You now need to remove the two Torx screws (T6x40)}}

== Carefully remove top cover ==
[[Image:Gta01b v3 case side opening white.jpg|700px]]

To remove the top cover, after removing the two torx screws, ''carefully'' squeeze the end of the supplied guitar pick between the cover and the case at the bottom of the device, and then slide the pick up to the top on one side (do not twist the pick). As you slide the pick along, the case retaining clips should come apart with a snapping sound. Repeat the procedure for the other side of the device. To unclip the last remaining large retaining clip at the top, slide the pick all the way to the top (this can be difficult) and then press it in at the centre. By ''careful'' application of force the clip will detach and the cover can then be removed.

== Top case lid removed ==
[[Image:Gta01b v3 case top open white.jpg|700px]]

Visible in this image, from the right, going clockwise.

*The blocky device at the far right is the GPS antenna.
**To the left of this, there are two gold pads, which are where the earpiece speaker connects.
*The [[Debug Board]] connector.
*At the left, the black semicircular device is the GSM antenna.
**Immediately to its right, the small circular black/gold object is the microphone
*At the top right, the ''Aux button''
*Right below it seems to be a small battery. It can also be seen on the picture below.

In the middle is the touchscreen LCD, the touchscreen printed wire can be seen beginning at the bottom left of this, through the glass.

== Lifting the PCB on the left side ==
{{note|You have to bend the plastic case a bit outwards until the headphone jack on the left side of the device becomes loose}}
[[Image:Gta01b v3 case top open pcb lift white.jpg|700px]]

== Removing PCB from case frame ==
{{note|Since the PCB now is loose on one side, you can carefully pull the USB socket and GPS antenna connector out of the right side of the case, and then flip the PCB upwards}}
[[Image:Gta01b v3 case top open pcb lifted.jpg|700px]]

This shows:
*At the top on a green board, the bluetooth module, and the square bluetooth antenna.
*The headset jack is to the right of this.
**Immediately below the headset jack is the [[Neo1973 Battery]] connector.
**Below the [[Neo1973 Battery]] connector, the two gold pads feed the vibrator motor.
*To the right of the headset jack is the left speaker connector.

On the other side of the PCB, going from bottom-right corner down-left.

*The small circular connector is the GSM connector to which an external ariel can be connected with the back removed, or with an alternative back.

*To the left of this is the right speaker connector.
*One of the button switches.
*USB port.
*Micro-SD slot
*SIM slot - overlaying the Micro-SD slot when present.
*Gold GPS antenna connector.
**Immediately above this with the grey wire connection is the connection to the built in GPS antenna.

On the case picture below, you can see the left and right speakers under the translucent plastic, and the vibrator motor in the middle.

== Empty case frame ==

[[Image:Gta01b v3 case empty white.jpg|700px]]

You can actually see the two stereo speakers beneath the translucent cover, and next to it the small vibrator motor.

Next to the top of the picture is a hole near the speaker.
The external GSM antenna connector is accessed through this hole.

== GSM Antenna ==

[[Image:Gta01b v3 gsm antenna.jpg|700px]]

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

User talk:Technil

2007-03-27T08:56:41Z

Xkr47:

Hey there. I probably won't have too much to say until I get the phone in late march sometime.. I have interest in working on:

- '''A cycle computer using GPS'''. Here is some info about power usage of the GPS:

Excerpted from "GPS time synch" thread on [http://lists.openmoko.org/mailman/listinfo/community Community Digest]

>> Based on ballpark estimates from other similar devices, it's probably
>> around 70mW.
>> This will really hurt if you keep it on all the time, fortunately, for
>> most applications, you probably don't need to.
>> If it works at 2s on, 30s off, as seems likely, this alone drains
>> 1/30th of the battery per day, which isn't bad. Especially as you can
>> probably back off a little if the phone has been stationary for
>> several minutes.
>>
>> Does GPS work well in such a mode? I seem to remember from various
>> handheld units that it can take quite a while (minutes) to sync up to
>> a given satellite. (For all I know, you *can* operate this way, I'm
>> completely clueless on the subject.)

70mW.. Here is the [http://wiki.openmoko.org/wiki/Neo1973_Battery Neo1973 Battery info].
For the sampling needed to get accurate speeds distance etc.. I don't think using AGPS and sleeping the GPS intermittently will be feasible.. so we need to know how long we can use the GPS continuously and not cripple the phone with power consumption. A dyanmo or supplemantary power source on the bike is another option but would need a regulator and dock of some sort.

The Battery is a Li-Ion 3.7V at 1200mAh or roughly 4.4 Wh. If we only let GPS use 1/4 of the battery power, that gives us 1.1Wh or 0.3 Ah at 3.7V. At 0.070 W (the "guess" on the power draw for the GPS) the current draw indicates that the GPS should work for a little bit less than 16 Hours.. Plenty even for two days of extended touring. I'm guessing this would involve probably turning off the backlight, powering down BT and cellular radios and the like, otherwise the radios and screen will drain the battery long before we can keep the device on for 16 hours.

- '''A high quality multi-purpose calculator.''' maybe [http://qalculate.sourceforge.net/ Qalculate]? it is GTK+ 2.4 needs scrollkeeper, libglade 2, as well as a build of libqalculate. Looks like OE has libglade and scrollkeeper, and Open Moko is GTK. So I guess I should get my OE environment all set up and do a test build. [http://www.handhelds.org/hypermail/gpe/24/2411.html this thread] on GPE maybe of importance looks like a problem with libm. This may be of use.. [http://www.openembedded.org/user-manual&dpage=commonuse_prebuilt_toolchain toolchain stuff] text input might be slow, but probably no slower than a graphing calculator.

- '''Messing around with speex on SIP / IAX clients.''' Lowly GPRS... :P

--[[User:Xkr47|xkr47]] 10:56, 27 March 2007 (CEST) Thx for the gprs class info on [[Neo1973 Hardware]]. :) But one more to go.. Do you know the GPRS capability class also? It has been guessed on IRC that it would be GPRS Class B, i.e. no grps traffic while a voice call is active.. If this is true, do you know whether you can still use GPRS when someone is calling you, but before answering the phone? It could be nice to use in countries where there are cheap MSISDN <-> owner mapping services online, it could be used to (automatically or by buttonpress) look up who's calling if the number is not previously known before deciding whether to answer :)

Neo 1973 hardware

2007-03-27T08:48:47Z

Xkr47: /* CALYPSO digital baseband */ removed question as it's now answered

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

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

== Physical Dimensions ==
* 120.7 x 62 x 18.5 mm (4.75 x 2.44 x 0.728 inch)
* 184 +/- 5 g (6.5 ounces)

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

* Product Homepage: [http://www.samsung.com/products/semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/S3C2410.htm S3C2410.htm]
* User Manual: [http://www.samsung.com/Products/Semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/2410UserManual.pdf 2410UserManual.pdf]
* BSDL File: [http://www.samsung.com/Products/Semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/S3C2410_BGA_BSDLJTAGFILE.bsd S3C2410_BGA_BSDLJTAGFILE.bsd]
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA01Bv3/gpio.txt

=== Flash ===
64MB Samsung NAND flash (K9F1208U0B) attached to S3C2410 NAND controller.

* Product Homepage: [http://www.samsung.com/products/semiconductor/NANDFlash/SLC_SmallBlock/512Mbit/K9F1208U0B/K9F1208U0B.htm K9F1208U0B.htm]
* Data Sheet: [http://www.samsung.com/Products/Semiconductor/NANDFlash/SLC_SmallBlock/512Mbit/K9F1208U0B/ds_k9f1208x0b_rev03.pdf ds_k9f1208x0b_rev03.pdf]
* Connected to: S3C2410 NAND controller

This is the only flash memory in the device. The S3C2410 boots directly from nand, using the [[S3C2410 Steppingstone]].

We only use free software, no proprietary flash file systems. For a full description of how it is used, see [[NAND bad blocks]]

=== RAM ===
128MB SDRAM (2x Samsung K4M511633C) attached to S3C2410 SDRAM controller
* Product Homepage: [http://www.samsung.com/Products/Semiconductor/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M511633C/K4M511633C.htm K4M511633C.htm]
* Data Sheet: [http://www.samsung.com/Products/Semiconductor/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M511633C/ds_k4m511633c.pdf ds_k4m511633c.pdf]
* Connected to: S3C2410

=== GSM/GPRS ===
The GSM/GPRS modem is Texas Instruments Calypso based.

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

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

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

==== TRF6151 RF Transceiver ====
Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] 
Quad-band support 
GPRS Class12/CS4 

=== [[Hardware:AGPS|AGPS]] ===
Hammerhead AGPS from Global Locate.

* Product Homepage: [http://www.globalocate.com/SEMICONDUCTORS/SEMI_HAMMER_Frameset.htm Hammerhead]
* Connected to: S3C2410 UART2 (full-uart, RxD, TxD, CTS, RTS) /dev/ttySAC1 in userspace
* Driver: Implemented as plugin for the gpsd daemon ([[gpsd]])
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch
* Externally-accessible GPS antenna connector of type MMCX

This will not have a working driver till at least mid April.

=== microSD-Card ===
The Neo1973 has one microSD aka Transflash slot.
It should support SDHC, but this has not been tested. If this works, cards >2G should work with no problems. As there are no microSD cards over 2G at the moment, it hasn't been tested. MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].
* Connected to: S3C2410 MMC/SD controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c_mci.patch
* [[Supported microSD cards]]
* Specifications: [http://www.sdcard.org/confirm/confirm_memorycard.aspx SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]

=== LCD Display Module (LCM) ===
This is a 2.8" diagonal (1.7" x 2.27") 480x640 toppoly (tpo) TD028TTEC1 module, using a Toshiba JBT6K74 TFT LCD Driver Chipset.
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch
* Connected to: S3C2410 Display Controller and S3C2410 SPI Interface channel 1

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

==== Stylus ====

Seemingly identical to [http://cgi.ebay.com/4in1-PDA-Stylus-LED-Light-Torch-Laser-Pointer-Pen-h7_W0QQitemZ280089656134QQihZ018QQcategoryZ48677QQrdZ1QQcmdZViewItem this one on ebay]

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

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

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

=== USB Host ===
The USB Host controller is inside the S3C2410
* Driver: Stock Linux kernel ohci_hcd

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

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

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

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

* Product Homepage: [http://www.national.com/pf/LM/LM4857.html LM4857.html]
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4857.pdf LM4857.pdf]
* Connects to: S3C2410 I2C (Control)

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

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

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

=== Power Management ===
A Philips PCF50606 is used for power management.

* Data Sheet: [http://www.nxp.com/acrobat/literature/9397/75009763.pdf PCF50606/605]
* User Manual: [http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf pcf50606.pdf]
* Connected to: S3C2410 via I2C, client address is 0x08.
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-pcf50606.patch

=== Battery ===
The [[Neo1973 Battery]] is compatible with a Nokia BL5C battery.
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.

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

== History ==
=== GTA01 ===
This is the most simple, non-bluetooth version of the prototype.

==== GTA01v3 ====
First generation of prototypes that was given to internal OpenMoko software developers.

Unfortunately not useful at all due to non-working touchscreen.

* ATAG_REVISION: 0x0000130

==== GTA01v4 ====
Second generation of prototypes that was given to Harald + Mickey.

Unfortunately still not useful due to half-working touchscreen.

* ATAG_REVISION: 0x00000140

=== GTA01B ===
This is the bluetooth-enabled fork of GTA01

==== GTA01Bv2 ====
This is the first produced version of the bluetooth-enabled version.

* ATAG_REVISION: 0x00000220

==== GTA01Bv3 ====
This is the second produced version of the bluetooth-enabled version. It contains mainly GPS-related fixes.

* ATAG_REVISION: 0x00000230

This is the version that is shipped in Phase 0

===== GTA01Bv3 Errata =====
====== PMU unable to resume from suspend ======
Due to use of wrong GPIO/EINT pin, the PMU cannot wake-up the phone after suspend. This means, specifically, '''the following events can not bring the phone back from suspend-to-ram''':
* PMU RTC Alarm
* Power button press
* Charger events (charger insertion/removal/error)
* Low battery

====== Stand-by time extremely low ======
This is due to a design bug resulting in at least 30mA additional standby current, since we cannot properly switch off the power supply to the S3C2410 PLL's. There is nothing we can do to change this with post-production fixes. GTA01Bv4 will address this issue.

====== GSM doesn't resume phone from suspend ======
The GSM modem currently doesn't signalize a wakeup interrupt to the S3C2410 in case there's some noteworthy event, such as incoming call, loss of network, incoming SMS or the like.

This is a serious issue, but can be fixed with a GSM Modem Firmware update.

====== GSM Sidetone too loud ======
The local feedback sidetone (see [http://en.wikipedia.org/wiki/Sidetone]) is too loud. This will be addressed in a GSM firmware update

====== Bad block ======
Due to an error in the production process, the factory-programmed NAND bad block information has been lost. This means that some blocks in the flash will wear out rapidly, which might become as bad as rendering the device unusable.

==== GTA01Bv4 ====
This is the version that will be shipped in Phase 1

===== Changes from GTA01Bv3 =====
# Fix all Errata items from GTA01Bv3
# Add I2C, SPI and one irq and wakeup capable GPIO pin to debug port plus have test pads for all these signals (for soldering wires directly on the pcb)
# Fix a number of production related details and minor hardware details that are not user-visible

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

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

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

[[Category:Hardware]]
{{Languages|Neo1973_Hardware}}

Wishlist/Neo1973 P0 Review

2007-03-13T21:52:51Z

Xkr47: /* Connecting */ added comment about potentially bogus command

This is a page for those with P0 hardware to share their impressions of the device, and to respond to questions that may be raised about it.

See also [[Neo1973 Phase 0]] -- Information for Phase 0 device owners

[[Neo1973_Hardware#GTA01Bv3]] -- Hardware in Phase 0 phone

= Pictures =

Found on IRC, pictures by:
*Koen provided these [http://www.flickr.com/photos/koenkooi/sets/72157594573486523/ pictures, of the assembled and partially dissasembled phone].
*Rod Whitby [http://www.flickr.com/photos/rwhitby/sets/72157594574977123/ has posted pictures of his Neo1973 test rig]
*Hrw [http://flickr.com/photos/hrwandil/413643600/ Size comparison between nokia 6210, neo1973, SE k750i]
*alphaone [http://sicherheitsschwankung.de/gallery/v/openmoko/ comparison of several phones running openmoko]

* picture of the inside of the front and back cases, with a ruler for scale, also pcb back and front with ruler, to make it easier for people considering building hardware modifications.

=Wishlist=

== Benchmarks ==

* microSD read/write speeds with various cards
** at the moment this probably [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=245 crashes] Neo1973: latest u-boot should fix this problem, test should be possible now
* internal NAND read/write speeds
* some benchmarks
<pre>dd bs=1024 count=10240 if=/dev/zero | time gzip -9 > /dev/null
10240+0 records in
10240+0 records out
real 0m 4.94s
user 0m 3.73s
sys 0m 0.58s</pre>
<pre>time dd if=/dev/urandom bs=1024 count=10240 of=/dev/zero
10240+0 records in
10240+0 records out
real 0m 34.95s
user 0m 0.01s
sys 0m 34.69s

and another device:
10240+0 records in
10240+0 records out
real 0m 37.01s
user 0m 0.03s
sys 0m 36.42s</pre>
<pre>time dd if=/dev/zero bs=1024 count=102400 of=/dev/zero
real 0m 2.23s
user 0m 0.12s
sys 0m 2.08</pre>

**scp via SSH to the SD card is running with 300kb/s

== Input events dumps ==
* raw dump from s3c2410-ts device as you touch (click)/gesture/hold down with fingers/stylus
** raw dump when doing fake double-touch: one finger down and then tap with second finger or make gesture with second finger
** corresponding events in X11

== Hardware Information ==

=== USB ===

<pre>
root@fic-gta01:~$ lsusb
Bus 1 Device 2: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 1 Device 1: ID 0000:0000
root@fic-gta01:~$ lsusb -v

Bus 1 Device 2: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a12 Cambridge Silicon Radio, Ltd
idProduct 0x0001 Bluetooth Dongle (HCI mode)
bcdDevice 19.58
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 177
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
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 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1

Bus 1 Device 1: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.20-moko8 ohci_hcd
iProduct 2 S3C24XX OHCI
iSerial 1 s3c24xx
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x0012
No power switching (usb 1.0)
No overcurrent protection
bPwrOn2PwrGood 2 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0x00
Hub Port Status:
Port 1: 0000.0103 power enable connect
Port 2: 0000.0100 power
root@fic-gta01:~$
</pre>

=== CPU ===

<pre>Processor : ARM920T rev 0 (v4l)
BogoMIPS : 100.96
Features : swp half thumb
CPU implementer : 0x41
CPU architecture: 4T
CPU variant : 0x1
CPU part : 0x920
CPU revision : 0
Cache type : write-back
Cache clean : cp15 c7 ops
Cache lockdown : format A
Cache format : Harvard
I size : 16384
I assoc : 64
I line length : 32
I sets : 8
D size : 16384
D assoc : 64
D line length : 32
D sets : 8

Hardware : GTA01
Revision : 0230
Serial : 0000000000000000</pre>

=== GSM Modem ===

* <tt>ATI3</tt> & <tt>ATI9</tt> & <tt>AT&V</tt> output from GSM modem
** All those commands give an error, but see [[Hardware:AT_Commands]] for other results.
** Oh, how unfortunate. TI's Calypso is not PnP (ATI9) :-) --[[User:Csdexter|@Dexter]] 15:39, 8 March 2007 (CET)

=== Bluetooth ===

Basic info:
<pre>
root@fic-gta01:~$ hciconfig hci0 -a
hci0: Type: USB
BD Address: 00:06:6E:14:13:CA ACL MTU: 384:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:943 acl:0 sco:0 events:33 errors:0
TX bytes:459 acl:0 sco:0 commands:32 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0x120112
Service Classes: Networking, Object Transfer
Device Class: Computer, Handheld
HCI Ver: 2.0 (0x3) HCI Rev: 0x7a6 LMP Ver: 2.0 (0x3) LMP Subver: 0x7a6
Manufacturer: Cambridge Silicon Radio (10)
</pre>

Commands:
<pre>
root@fic-gta01:~$ hciconfig hci0 commands
hci0: Type: USB
BD Address: 00:06:6E:14:13:CA ACL MTU: 384:8 SCO MTU: 64:8
Commands: Octet 0 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 1 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 2 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 3 = 0x03 (Bit 0 1)
Octet 4 = 0xfe (Bit 1 2 3 4 5 6 7)
Octet 5 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 6 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 7 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 8 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 9 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 10 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 11 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 12 = 0xf3 (Bit 0 1 4 5 6 7)
Octet 13 = 0x0f (Bit 0 1 2 3)
Octet 14 = 0xf8 (Bit 3 4 5 6 7)
Octet 15 = 0xff (Bit 0 1 2 3 4 5 6 7)
Octet 16 = 0x3f (Bit 0 1 2 3 4 5)
'Inquiry' 'Inquiry Cancel' 'Periodic Inquiry Mode'
'Exit Periodic Inquiry Mode' 'Create Connection' 'Disconnect'
'Add SCO Connection' 'Cancel Create Connection'
'Accept Connection Request' 'Reject Connection Request'
'Link Key Request Reply' 'Link Key Request Negative Reply'
'PIN Code Request Reply' 'PIN Code Request Negative Reply'
'Change Connection Packet Type' 'Authentication Requested'
'Set Connection Encryption' 'Change Connection Link Key'
'Master Link Key' 'Remote Name Request' 'Cancel Remote Name Request'
'Read Remote Supported Features' 'Read Remote Extended Features'
'Read Remote Version Information' 'Read Clock Offset'
'Read LMP Handle' 'Hold Mode' 'Sniff Mode' 'Exit Sniff Mode'
'Park State' 'Exit Park State' 'QoS Setup' 'Role Discovery'
'Switch Role' 'Read Link Policy Settings' 'Write Link Policy Settings'
'Read Default Link Policy Settings'
'Write Default Link Policy Settings' 'Flow Specification'
'Set Event Mask' 'Reset' 'Set Event Filter' 'Flush' 'Read PIN Type'
'Write PIN Type' 'Create New Unit Key' 'Read Stored Link Key'
'Write Stored Link Key' 'Delete Stored Link Key' 'Write Local Name'
'Read Local Name' 'Read Connection Accept Timeout'
'Write Connection Accept Timeout' 'Read Page Timeout'
'Write Page Timeout' 'Read Scan Enable' 'Write Scan Enable'
'Read Page Scan Activity' 'Write Page Scan Activity'
'Read Inquiry Scan Activity' 'Write Inquiry Scan Activity'
'Read Authentication Enable' 'Write Authentication Enable'
'Read Encryption Mode' 'Write Encryption Mode' 'Read Class Of Device'
'Write Class Of Device' 'Read Voice Setting' 'Write Voice Setting'
'Read Automatic Flush Timeout' 'Write Automatic Flush Timeout'
'Read Num Broadcast Retransmissions'
'Write Num Broadcast Retransmissions' 'Read Hold Mode Activity'
'Write Hold Mode Activity' 'Read Transmit Power Level'
'Read Synchronous Flow Control Enable'
'Write Synchronous Flow Control Enable'
'Set Host Controller To Host Flow Control' 'Host Buffer Size'
'Host Number Of Completed Packets' 'Read Link Supervision Timeout'
'Write Link Supervision Timeout' 'Read Number of Supported IAC'
'Read Current IAC LAP' 'Write Current IAC LAP'
'Read Page Scan Period Mode' 'Write Page Scan Period Mode'
'Read Page Scan Mode' 'Write Page Scan Mode'
'Set AFH Channel Classification' 'Read Inquiry Scan Type'
'Write Inquiry Scan Type' 'Read Inquiry Mode' 'Write Inquiry Mode'
'Read Page Scan Type' 'Write Page Scan Type'
'Read AFH Channel Assessment Mode' 'Write AFH Channel Assessment Mode'
'Read Local Version Information' 'Read Local Supported Commands'
'Read Local Supported Features' 'Read Local Extended Features'
'Read Buffer Size' 'Read Country Code' 'Read BD ADDR'
'Read Failed Contact Counter' 'Reset Failed Contact Counter'
'Get Link Quality' 'Read RSSI' 'Read AFH Channel Map' 'Read BD Clock'
'Read Loopback Mode' 'Write Loopback Mode'
'Enable Device Under Test Mode' 'Setup Synchronous Connection'
'Accept Synchronous Connection' 'Reject Synchronous Connection'
</pre>

Features:
<pre>
root@fic-gta01:~$ hciconfig hci0 features
hci0: Type: USB
BD Address: 00:06:6E:14:13:CA ACL MTU: 384:8 SCO MTU: 64:8
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO> <broadcast encrypt>
<EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <inquiry with RSSI>
<extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave>
<AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
<AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>
<EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>
</pre>

== System information ==

* <tt>dmesg</tt> dump
<pre>
<4>CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0003177
<4>Machine: GTA01
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 32768
<7> DMA zone: 256 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 32512 pages, LIFO batch:7
<7> Normal zone: 0 pages used for memmap
<4>CPU S3C2410A (id 0x32410002)
<4>S3C2410: core 202.666 MHz, memory 101.333 MHz, peripheral 50.666 MHz
<6>S3C24XX Clocks, (c) 2004 Simtec Electronics
<4>CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
<4>CPU0: D VIVT write-back cache
<4>CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
<4>CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
<4>Built 1 zonelists. Total pages: 32512
<5>Kernel command line: rootfstype=jffs2 root=/dev/mtdblock4 console=tty0 mtdparts=neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash),0x03d1c000(rootfs)
<4>irq: clearing pending ext status 000000a0
<4>irq: clearing subpending status 00000002
<4>PID hash table entries: 512 (order: 9, 2048 bytes)
<4>timer tcon=00500000, tcnt a4ed, tcfg 00000200,00000000, usec 00001e51
<4>Console: colour dummy device 80x30
<4>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<4>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Memory: 128MB = 128MB total
<5>Memory: 126720KB available (2824K code, 255K data, 104K init)
<7>Calibrating delay loop... 100.96 BogoMIPS (lpj=252416)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<4>S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
<4>Registering sysclass
<4>DMA channel 0 at c8800000, irq 33
<4>DMA channel 1 at c8800040, irq 34
<4>DMA channel 2 at c8800080, irq 35
<4>DMA channel 3 at c88000c0, irq 36
<6>NET: Registered protocol family 16
<4>S3C2410 Power Management, (c) 2004 Simtec Electronics
<4>S3C2410: Initialising architecture
<4> 0: xdreq0, channels 0---
<4> 1: xdreq1, channels -1--
<4> 2: sdi, channels 0-23
<4> 3: spi0, channels -1--
<4> 4: spi1, channels ---3
<4> 5: uart0, channels 0---
<4> 6: uart1, channels -1--
<4> 7: uart2, channels ---3
<4> 8: timer, channels 0-23
<4> 9: i2s-sdi, channels -12-
<4>10: i2s-sdo, channels --2-
<4>11: <NULL>, channels ----
<4>12: <NULL>, channels ----
<4>13: <NULL>, channels ----
<4>14: usb-ep1, channels 0---
<4>15: usb-ep2, channels -1--
<4>16: usb-ep3, channels --2-
<4>17: usb-ep4, channels ---3
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>NET: Registered protocol family 2
<4>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<4>TCP established hash table entries: 4096 (order: 2, 16384 bytes)
<4>TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
<6>TCP: Hash tables configured (established 4096 bind 2048)
<6>TCP reno registered
<6>JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<4>GTA01 Backlight Driver Initialized.
<4>Console: switching to colour frame buffer device 80x58
<6>fb0: s3c2410fb frame buffer device
<6>s3c2410-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2410
<6>s3c2410-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2410
<4>RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
<4>S3C24XX NAND Driver, (c) 2004 Simtec Electronics
<6>s3c2410-nand s3c2410-nand: Tacls=3, 29ns Twrph0=7 69ns, Twrph1=3 29ns
<6>NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
<7>Bad block table found at page 131040, version 0x01
<7>Bad block table found at page 131008, version 0x01
<5>5 cmdlinepart partitions found on MTD device neo1973-nand
<5>Creating 5 MTD partitions on "neo1973-nand":
<5>0x00000000-0x00040000 : "u-boot"
<5>0x00040000-0x00044000 : "u-boot_env"
<5>0x00044000-0x00244000 : "kernel"
<5>0x00244000-0x002e4000 : "splash"
<5>0x002e4000-0x04000000 : "rootfs"
<6>s3c2410-nand s3c2410-nand: clock idle support enabled
<6>s3c24xx-spi-gpio s3c24xx-spi-gpio.1: registering c001f248: jbt6k74
<3>jbt_init: entering
<3>jbt_probe: entering
<3>jbt6k74_enter_state: entering(old_state=0, new_state=2)
<3>standby_to_sleep: entering
<3>sleep_to_normal: entering
<3>jbt_init_regs: entering
<3>jbt6k74_display_onoff: entering
<5>usbmon: debugfs is not available
<6>usbcore: registered new interface driver libusual
<7>gta01_udc_command(2)
<4>ether gadget: using random self ethernet address
<4>ether gadget: using random host ethernet address
<6>usb0: Ethernet Gadget, version: May Day 2005
<6>usb0: using s3c2410_udc, OUT ep2-bulk IN ep1-bulk STATUS ep3-bulk
<6>usb0: MAC 2e:a9:0b:ec:cf:6f
<6>usb0: HOST MAC 62:c2:cc:8b:e8:c4
<6>usb0: RNDIS ready
<7>gta01_udc_command(1)
<6>mice: PS/2 mouse device common for all mice
<6>input: GTA01 Buttons as /class/input/input0
<6>wake enabled for irq 50
<6>wake enabled for irq 51
<6>s3c2410 TouchScreen successfully loaded
<6>input: s3c2410 TouchScreen as /class/input/input1
<6>i2c /dev entries driver
<6>s3c2410-i2c s3c2410-i2c: slave address 0x10
<6>s3c2410-i2c s3c2410-i2c: bus frequency set to 98 KHz
<6>s3c2410-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
<4>pcf50606_init: entering, calling i2c_add_driver
<4>pcf50606_attach_adapter: entering, calling i2c_probe
<4>pcf50606_detect: entering
<4>pcf50606_irq: entering(irq=60, pcf=c0555e00): scheduling work
<3>PCF50606: IRQ 1 cannot be enabled as wake-upsource in this hardware revision!<7>pcf50606 0-0008: rtc intf: sysfs
<7>pcf50606 0-0008: rtc intf: proc
<7>pcf50606 0-0008: rtc intf: dev (254:0)
<6>pcf50606 0-0008: rtc core: registered pcf50606 as rtc0
<6>input: FIC Neo1973 PMU events as /class/input/input2
<6>Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC).
<4>pcf50606_work: INT1=0x40 INT2=0x0c INT3=0x00:SECOND CHGFOK CHGERR
<6>ASoC version 0.13.3
<6>wm8753: WM8753 Audio Codec 0.16
<6>asoc: WM8753 HiFi <-> s3c24xx-i2s mapping ok
<6>asoc: WM8753 Voice <-> Bluetooth mapping ok
<6>ALSA device list:
<6> #0: neo1973 (WM8753)
<6>TCP cubic registered
<6>NET: Registered protocol family 1
<6>usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet
<3>ep_disable: ep3-bulk
<4>Empty flash at 0x018c7c8c ends at 0x018c7e00
<7>udc: enabling fast charge
<4>VFS: Mounted root (jffs2 filesystem).
<6>Freeing init memory: 104K
<4>pcf50606_irq: entering(irq=60, pcf=c0555e00): scheduling work
<4>pcf50606_work: INT1=0x40 INT2=0x04 INT3=0x00:SECOND CHGFOK
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<6>gta01-pm-bt gta01-pm-bt.0: FIC GTA01 (Neo1973) Bluetooth Power Management: starting
<6>Bluetooth: Core ver 2.11
<6>NET: Registered protocol family 31
<6>Bluetooth: HCI device and connection manager initialized
<6>Bluetooth: HCI socket layer initialized
<6>Bluetooth: L2CAP ver 2.8
<6>Bluetooth: L2CAP socket layer initialized
<6>Bluetooth: HIDP (Human Interface Emulation) ver 1.1
<6>s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
<6>s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
<6>s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
<6>usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 2 ports detected
<6>Bluetooth: RFCOMM socket layer initialized
<6>Bluetooth: RFCOMM TTY layer initialized
<6>Bluetooth: RFCOMM ver 1.8
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
</pre>

* <tt>pstree -Gupl</tt> output after all standard processes have started
* <tt>ps</tt> output after startup:
<pre> PID Uid VmSize Stat Command
1 root 584 S init [5]
2 root SWN [ksoftirqd/0]
3 root SW [watchdog/0]
4 root SW< [events/0]
5 root SW< [khelper]
10 root SW< [kthread]
56 root SW< [kblockd/0]
57 root SW< [ksuspend_usbd]
60 root SW< [khubd]
62 root SW< [kseriod]
73 root SW< [kapmd]
77 root SW [pdflush]
78 root SW [pdflush]
79 root SW< [kswapd0]
80 root SW< [aio/0]
117 root SW [mtdblockd]
137 root SW< [s3c24xx-spi-gpi]
168 root SW< [kmmcd]
187 root SWN [jffs2_gcd_mtd4]
227 root 452 S < udevd --daemon
848 root SW< [krfcommd]
950 daemon 380 S /sbin/portmap
986 root 624 S /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22
995 root 480 S /usr/sbin/apmd -P /etc/apm/apmd_proxy --proxy-timeout 30
1005 messageb 712 S /usr/bin/dbus-daemon --system
1013 root 632 S /sbin/syslogd -n -C 64 -m 20
1015 root 628 S /sbin/klogd -n
1034 root 736 S /sbin/hcid -f /etc/bluetooth/hcid.conf
1037 root 484 S /sbin/sdpd
1040 root 492 S /bin/hidd --server
1051 root 540 S /sbin/getty 38400 tty1
1057 root 696 S xinit /etc/X11/Xsession -- /usr/bin/Xfbdev :0 -br -pn -screen 480x640x1
1076 root 3540 S < /usr/bin/Xfbdev :0 -br -pn -screen 480x640x16
1081 root 692 S /bin/sh /etc/X11/Xsession
1086 root 716 S /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
1090 root 580 S run-parts /etc/X11/Xsession.d
1094 root 1624 S /usr/libexec/gconfd-2
1097 root 2160 S matchbox-window-manager -use_titlebar no -use_cursor no
1098 root 2252 S rxvt
1100 root 2420 S /usr/bin/settings-daemon
1101 root 848 S sh
1103 root 3072 S matchbox-desktop --icon-size 100 --icon-padding 60 --font sans-16 --tit
1104 root 2152 S matchbox-panel --orientation north -b /usr/share/openmoko/pixmaps/openm
1105 root 2112 S matchbox-panel --orientation south -b /usr/share/openmoko/pixmaps/openm
1106 root 2040 S mb-applet-menu-launcher
1107 root 1376 S mb-applet-launcher -o -1 -l mbterm.png mb-applet-xterm-wrapper.sh
1108 root 1900 S mbinputmgr
1109 root 1372 S mb-applet-launcher -na -l --title Screen Rotator /usr/share/pixmaps/xra
1110 root 1436 S mb-applet-battery
1115 root 1836 S matchbox-keyboard
1117 root 552 S logread -f
1145 root 1016 S /usr/sbin/dropbear -r /etc/dropbear/dropbear_rsa_host_key -p 22
1146 root 880 S -sh
1149 root 784 R ps</pre>
(From [http://pastebin.ca/385957 here].)

= Connecting =

By default Neo1973 has usb0 interface working. Under Linux you need to <tt>modprobe usbnet</tt> and configure usb0 interface:
<pre>
ifconfig usb 192.168.0.200 netmask 255.255.255.0
</pre>
--[[User:Xkr47|xkr47]] 22:52, 13 March 2007 (CET) should that perhaps be "ifconfig usb0 ..."

Then <tt>ssh root@192.168.0.202</tt> with empty password to get into phone.

= Dialing =

Dialing currently works only [[Manually_using_GSM|manually]].

= Audio =

Wishlist:
*How is the frequency characteristics (roughly) of the two Neo1973 speakers? And how's the sound with the bundled ear plugs? You may play this [http://www.dr-lex.34sp.com/macast/mp3test.html#Sweeps 20-16000 Hz exponential sweep (MP3)] to test.
*A real [http://freshmeat.net/projects/signalgenerator/ signal generator] would be better than signals recorded into a lossy format. Many people are reporting audible glitches in the above sweeps (more noticeable in linear sweeps)
See [[Neo1973_Audio_Subsystem#Phase0_Quick_Start]]

= MicroSD =

MicroSD card quickstart is:
<pre>
modprobe s3cmci
fdisk /dev/mmcblk0 (and create Linux partition)
mke2fs -j /dev/mmcblk0p1
mount -t ext3 /dev/mmcblk0p1 /media/card
</pre>

Note that without u-boot fix accessing too much will [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=245 crash] Neo1973.

[[Category:Ideas]]

Neo 1973 GTA01 Power Management

2007-02-19T22:12:26Z

Xkr47: /* Approximate power draw of various subsystems. Estimated from datasheets. */ Added comment that 3500 is probably in mWh

== Voltages ==

=== VB ===

* Battery terminal voltage
* Used by
** [[LM4857]] Amplifier
** [[PCF50606]] PMU
** LCM Backlight
** U7607 AVDD regulator
** U7608 VTXCO_2V8 regulator

=== CORE_1V8 ===
This is the S3C2410 Core Voltage

* Generated by PMU DCUD

=== IO_3V3 ===

* Generated by PMU DCDE
* Used by
** Vibrator
** FLASH_3V3 (see below)
** Touch panel transistors
** S3C2410 VDDA_ADC
** S3C2410 VDDOP
** S3C2410 VDDMOP
** S3C2410 nBATT_FLT
** U1502 (latch for GSM UART)
** S3C2410 EXTCLK ???
** SDRAM

=== GL_3V3 ===

* Generated by PMU DCDF

* Used by
** AGPS

* Controlled by
** PMU

==== PM Driver ====

* Switch on/off if GPS is used or not

==== Initial state ====

* disabled by u-boot PMU initialization

=== CODEC_3V3 ===

* Generated by PMU IOVDD

* Used for
** Audio Codec (digital and analog)

* Controlled by
** PMU Driver

==== PM Driver ====

* mostly included in ASoC, right?
* switch on, only if Audio path is required.

==== Initial state ====

* disabled by PMU initialization in u-boot

=== LCM_3V3 ===

* Generated by PMU LPVDDD

* Used by
** Headset/GSM Uart Latch
** LCM

==== PM Driver ====

* check whether we really need to switch this off, since LCM has sophisticated PM features

==== Initial state ====

* enabled by u-boot PMU initialization

=== BT_3V15 ===

* Generated by PMU D1REG

==== PM Driver ====

* has to be powered up before Bluetooth can be used
* Bluetooth device automatically enumerates at bus

==== Initial state ====

* disabled by u-boot PMU initialization

=== GL_2V5 ===

* Generated by PMU D2REG

* Used by
** AGPS

* Controlled by
** PMU Driver

==== PM Driver ====

* switch on only in case GPS is enabled

==== Initial state ====

* disable by u-boot GPIO initialization

=== USER1 ===

FIXME: no idea what this is for

* Generated by PMU D3REG

==== PMU Driver ====

* permanently disabled

==== Initial state ====

* disabled by PMU initialization in u-boot

=== FLASH_3V3 ===

* Derived from IO_3V3

* Used by
** NAND Flash

* Controlled by
** SD_EN GPIO

==== PM Driver ====

* do we really want to switch it on/off before every flash access?
* if we go to standby, IO_3V3 will be switched off, thus FLASH_3V3 is off, too

==== Initial state ====

* on, enabled by u-boot GPIO initialization

=== AVDD ===

* Generated by U6707

* Used by
** AGPS

* Controlled by
** EN_AGPS3V GPIO

==== PM Driver ====

* Switch on only if GPS enabled

=== VTCXO_2V8 ===

* Generated by U7608

* Used by
** AGPS

* Controlled by
** EN_GPS2V8 GPIO

==== PM Driver ====

* enable only if GPS is used.

==== Initial State ====

* disabled by u-boot GPIO initialization

=== SD_3V3 ===

* Derived from IO_3V3

* Used by
** microSD slot

* Controlled by
** SD_ON GPIO

==== PM Driver ====

* we don't want to switch this off while mounted, do we?

==== Initial state ====

* probably disabled, unless somebody uses 'mmcinit' from u-boot
* but we can't disable it without disabling NAND.
* result: enabled by u-boot GPIO initialization

== Kernel API ==

== Userspace API ==

== Approximate power draw of various subsystems. Estimated from datasheets.==

The battery has a total of 1200mAh, at 3.6V. This is approximately 3500mAh (--[[User:Xkr47|xkr47]] 23:12, 19 February 2007 (CET) surely this should be 3500'''mWh'''?), once power supply losses are taken into account.

* LCD
** 200mW with backlight at full brightness
** 40mW with backlight at 10%
*** Based on similar 2.8" LCDs.
* CPU
** 320mW @ 200MHz
** 450mW @ 266MHz
** 140mW @ 200MHz idle.
** 50mW @ 12MHz (slow mode)
*** These include fudge factors for RAM and other systems, from the CPU datasheet.
* Bluetooth ?
* GSM ?
* GPS
** 25mA
*** Based on comparison with a broadly similar (though not as fully featured chip [http://www.maxim-ic.com/appnotes.cfm/an_pk/3447 from Maxim]

USB seems unlikely to work in slow mode. The LCD controller is unknown - the product notes say that it has RAM, which may imply it can self-refresh.

This would imply that with the CPU constantly on in low power mode, GPS and GSM blipping on and off, and display off, the worst case power consumption is probably around 70mW, leading to a battery life of 2 days.
If the CPU is turned off, battery life rises significantly.

With everything on, playing video with sound, for example should get well over 4 hours.

Applications

2007-02-19T20:02:45Z

Xkr47: added template links

== Overview ==
Although [[OpenMoko]] is designed for smartphones that use a stylus, it would be foolish to expect people to only operate their handsets with stylus. For this reason, some core phone-related applications will be developed with finger (as opposed to stylus navigation) in mind.

{{note| Applications listed on this page are listing in order of priority and by phase. 0th phase is for the developers preview release in February, 1st phase is for March. 2nd phase is September... when we are ready for mass market appeal.}}

== General Principles ==
* All modifications are saved instantenously, there should never be a save command.
* Make sure users can't make interface operation errors, or that the effects are easily reversible, instead of just notifying them of the potential consequences of their actions.
* When you open a document you should be returned to the place where you were working when you last closed or save it (this is our concept of sessions).
* Label buttons with adjectives, which describe the state of the object affected
* Designers should seek an efficient monotonous solution to gain benefits, including ease of learning, simplicity of implementation, minimization of documentation, and lowered maintenance costs.
* Whenever you find yourself specifying an error message, please stop; then redesign the interface so that the condition that generated the error message doesn't arise.
* If the user gets no utility from a process, there is no reason to tell them that it is happening.

{{note|Innovation usually happens at the bottom. What we need to do is provide consistent ways to develop and deploy appliations.}}

==Finger-Based Applications ==

([[Sample Native-Finger Application|template]] for new native-finger applications)

=== 0th Phase ===
* [[Dialer]]
* [[Main Menu]]

=== 1st Phase ===
* [[Music Player]]
* [[Screen Saver]]
* [[Dialer]] with [[Least Cost Routing]] for international calling
* [[Headset Emulator]]

=== 2nd Phase ===
* [[Clocks]]
* [[GPS Navigation]]
* [[Calculator]]
* [[Unit Converter]]
* [[Game]]
* [[Guitar Tuning]]
* [[Code Memo]]
* [[Video Player]]

==Stylus-Based Applications ==

([[Sample Native-Stylus Application|template]] for new native-stylus applications)

=== 0th Phase ===
* [[Top Panel]]
* [[Footer]] with embedded [[History|Task Manager]]
* [[Contacts]]
* [[Calendar]]

=== 1st Phase ===
* [[Messages]]
* [[Application Manager]]
* [[Today]]
* [[Feed Reader]]
* [[Preferences]]
* [[Help Viewer]]

=== 2nd Phase ===
* [[Search]]
* [[Media Player]]
* [[Sketchbook]]
* [[Picture Viewer]]
* [[File Browser]]
* [[Terminal]]
* [[IM]]
* [[Web Browser]]
* [[Reader]]
* [[System Info]]

== Panel Applications ==

Panel Applications are individual executables residing in the [[Top Panel]]. They usually indicate their status and offer a pop-up menu. We are not yet sure whether there is enough screen real estate for this huge number of panel applications.

([[Sample Panel Application|template]] for new panel applications)

=== 0th Phase ===
* [[GSM & GPRS Connection Status]]
* [[Battery Monitor]]
* [[Clock]]

=== 1st Phase ===
* [[GPS Connection Status]]
* [[Bluetooth Connection Status]]
* [[USB Connection Status]]

=== 2nd Phase ===
* [[Search]]
* [[IM Presence]]
* [[Screen Grabber]]

Wish List - Hardware

2007-02-19T19:54:22Z

Xkr47: /* USB 2.0 */ OTG already supported?

===Hardware enhancements===

Some small hardware enhancement could be cheap, but very useful. Please add your ideas/wishes here:
 
=====Video-capable camera=====
*preferably in rotatable turret set into top of unit, so it can face in either direction, making it useful for video conferencing. For a phone to stand a chance in the modern market it will need a camera else it is likely that it won't be bought.

=====Integrated WiFi hardware=====
*To sync data
*To access Internet when WiFi is available (at home, work, school, friends)
*For VoIP (this uses much power but maybe the user have the charger connected)
**I'm willing to port [http://yate.null.ro/ Yate] to it if the Internet connectivity issue is solved --[[User:Csdexter|@Dexter]] 13:58, 16 February 2007 (CET)
*for videoconferencing (as with AccessGrid)
*Even 802.11b 11Mbps -only would do -- the point is being able to connect it to the Internet without incurring the (sometimes huge) costs of GPRS or (even worse) HSCSD.
*To save power have WiFi able to wake up and check for a designated SSID then sleep again if not found (i.e. I'm not home) or wake up by GPS location (only come up at home and in the office)
*Variable TX power, to the minimum needed to connect to the AP.
*Some sort of caching (encrypted?) internet proxy that can store and forward packets. Instead of having the radio constantly on, it turns the radio on every 30s, for just long enough to register with the AP, and ask the proxy if it has new packets for it.
** An optimisation might be if the hardware, and the AP can do broadcast packets. The receiver is only turned on for .5s/30s, to recieve a broadcast packet saying 'you've got packets' without registering with the AP, or transmitting at all. The GPS synchronises the timing.
**This slows the initial connection to the phone, but most tcp/ip applications will not time out in 30s.

=====LED=====
*A blinking LED would be cheap and low power, good for informing the user about new SMS/Email....
**An alternative to this would be for one segment of the LCD to be seperately backlit. There are many LEDs in the backlight, all normally on. This has the advantage that you can display reasonable amounts of information on the bit of the screen that's illuminated.
**The disadvantage is the field of view is smaller, and it's dimmer than a bare LCD, as the LCD absorbs some light.
**This also requires the CPU and LCD to be somewhat active, to keep it refreshed.

*Note: the LED and button ideas could be combined: illuminated buttons
*A yellow LED for GSM/GPRS Tx burst, a blue one for Bluetooth/WiFi Tx burst, a green one for non-urgent notifications (sleep state, missed call etc.) and a red one for urgent notifications (battery almost drained out, new SMS etc.). All of this could be done in one, multicoloured (RGB) LED, similar to the nice one on the Yaesu VX-7R.

=====D-Pad and Buttons=====
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)

=====Accelerometer=====
This enables the phone to sense where 'down' is - to enable various options.

*[[Wishlist:3D Viewport|3D Viewport]]
*[[Wishlist:Auto Align Map|Auto Align Map]]
*[[Wishlist:Computer Mouse|Computer Mouse]]
*[[Wishlist:Determine Position|Determine Position]]
*[[Wishlist:Distance Measuring|Distance Measuring]]
Change playlists when I'm jogging vs walking. (there ia an mp3 player on the market that does this).
*Can't the GPS information be used for that purpose? It should be possible to derive the phone's velocity from the change in coordinates over time, so such a playlist profile switcher should be a possibility even now already. [[User:Abraxa|Abraxa]] 00:09, 18 February 2007 (CET)
**Yeah in my opinion that is a very cool idea. But for that case the device should be much lighter. I wouldn't go jogging with a device with this size.--[[User:Denis std|denis_std]] 01:01, 18 February 2007 (CET)

=====SIR transceiver=====
*Could be used to detect when to turn off the display (if the low power IR signal is reflected) and activate the key lock. And could be used as a remote. iPhone has a proximity sensor.
*FIR would be nice as well, but I would settle for SIR if it would be added. Linux already has a working IrDA stack so the standard part would be satisfied. I would be more than glad to write lirc thingies for OpenMoko then :)

=====Standard 3.5mm jack=====
*I think everyone interested (and knowledgeable) enough to buy a Neo can make a 2.5mm male to 3.5mm female adaptor cable in under 1/2h and under 10EUR :-)

Certainly - now make it light, small, pretty, durable, tangle-free.
I want a 3.5mm jack. The only problem is - are headsets widely available in the same format as 2.5mm. --[[User:Speedevil|Speedevil]] 14:28, 16 February 2007 (CET)

=====Multitouch screen=====

=====Multi I/O adapter=====
*VGA, standard Jack (line in & out), standard USB

=====MMC/SD/SDIO slot (rather than?) miniSD or microSD=====
*Cheaper, more durable cards in a widely accepted format.
*Cards are harder to lose
*Wider selection of accesories, including SDIO accessories.
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)
*Only because CF takes too much room (or CF would be the wish, instead)

=====[[Expansion Back]]=====
* Replacement backs with additional features
* I believe this would be a great idea, if put into practice. It would solve the ''extensibility'' need, usually associated with Open Source projects. It would allow for lots of other devices and for functionality to be developed and put into use without making it a burden for FIC.
** With extra card slots and small footprint hard drive (if possible), Neo might become a nice ''image tank'' for photographers - --[[User:Cedel|cedel]] 18:34, 19 February 2007 (CET)

=====Thumb keyboard or keyboard attachment accessory=====
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).
*cheap clippable miniusb keyboard

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

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

=====EDGE support=====

=====Ability to insert more than one Sim-Card and (if possible) connect to more than one network at the same time=====

* This could be achieved via a specialist dual sim card kit (currently on market)- where two sims are trimmed and combined on one card, software support for dual sims would need providing...
* What about twin-SIMs (SIMs with 2 phone lines registered on them)? Conventional GSM phones have an option to switch between the two, older ones use # (long press before dialling) to do that. I'm guessing Calypso should support it, we just need to provide an interface for it :-) --[[User:Csdexter|@Dexter]] 11:34, 19 February 2007 (CET)

=====RFID tag=====
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]
*Advantages of a RFID tag? I would see a lot privacy problems
**The tag could be switched on or off. A nice feature would be a module able to clone tags. This would unfortunately probably be rather expensive.
**What about an RFID Reader which could be used to locate items with RFID tags (IE: in your house) [[User:Alexpb|Alexpb]]
***That would be a nice feature--[[User:Denis std|denis_std]] 08:33, 17 February 2007 (CET)
***Most tags can only be located within 10cm or so. Essentially no cheap tags can be located over several metres.--[[User:Speedevil|Speedevil]] 13:17, 18 February 2007 (CET)

===== USB 2.0 =====
* Powered
* Host Mode / Device Mode
* OTG (is this maybe supported already ?)

=====UMTS support=====

=====Dump the '''''egg-shaped''''' case design and go '''''rectangular''''' for more screen space=====
*I'm all for devices that look great and have great features - aside from that I really like the current design. Thus I'd like to comment that the design change request is probably not the majority's opinion. [[User:Abraxa|Abraxa]] 00:00, 18 February 2007 (CET)

=====A standard slip-on or clip-on template (possibly with buttons) to make the touch-screen blind accessible=====

=====Speakerphone functionality=====

=====Reposition Speakers=====
* putting the two speakers on opposite sides of the screen would make the stereo sound much more effective

The screen is 2.8" across.
That's not especially effective.
Also, the speaker noise does come out the side - look at the grills in the pictures. --[[User:Speedevil|Speedevil]] 06:19, 16 February 2007 (CET)

=====Small metal frame for protection (like Siemens M65, only with more style)=====

=====Free GPIO ports on a connector to allow easy, simple hardware extensions=====

=====Video acceleration=====
Hardware acceleration for video playback.

=====3D acceleration=====
3D hardware acceleration for 3D games, GUIs, etc. (maybe a PowerVR MBX Lite ?).

=====Alcohol Sensor=====
Alcohol sensor adjacent to microphone. It doesn't have to be accurate, just has to detect any amount of alcohol on the speaker's breath. I understand this is a very narrow market, but alcohol is on every parent's mind.

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

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

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

=====EPD=====

Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, flexible, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].

=====FM/Digital Radio(DAB) Reciever=====

A nice feature would be a radio reciever: FM or even better: [http://en.wikipedia.org/wiki/Digital_Audio_Broadcasting Digital Audio Broadcast] (Digital Radio)

=====V12 Embedded power source=====

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

=====Thermometer=====

An electronic thermometer might become handy for some users.

Maybe we could even integrate a [http://www.maxim-ic.com/ds2490 DS2490 usb-to-1wire chip] (about 15x10mm) in the phone along with a [http://www.maxim-ic.com/ds18s20 DS1820 1wire temperature sensor] and possibility (by internal or external connector) to add [http://www.maxim-ic.com/1-Wire.cfm further 1wire devices] like humidity sensors, secure authentication, buttons, keypads etc? The Linux kernel already happens to have a ds2490 driver.. This of course would require there to be a free internal usb port to connect the ds2490 to..

Wish List - Hardware

2007-02-19T19:51:02Z

Xkr47: /* Thermometer */ added 1wire possibility

===Hardware enhancements===

Some small hardware enhancement could be cheap, but very useful. Please add your ideas/wishes here:
 
=====Video-capable camera=====
*preferably in rotatable turret set into top of unit, so it can face in either direction, making it useful for video conferencing. For a phone to stand a chance in the modern market it will need a camera else it is likely that it won't be bought.

=====Integrated WiFi hardware=====
*To sync data
*To access Internet when WiFi is available (at home, work, school, friends)
*For VoIP (this uses much power but maybe the user have the charger connected)
**I'm willing to port [http://yate.null.ro/ Yate] to it if the Internet connectivity issue is solved --[[User:Csdexter|@Dexter]] 13:58, 16 February 2007 (CET)
*for videoconferencing (as with AccessGrid)
*Even 802.11b 11Mbps -only would do -- the point is being able to connect it to the Internet without incurring the (sometimes huge) costs of GPRS or (even worse) HSCSD.
*To save power have WiFi able to wake up and check for a designated SSID then sleep again if not found (i.e. I'm not home) or wake up by GPS location (only come up at home and in the office)
*Variable TX power, to the minimum needed to connect to the AP.
*Some sort of caching (encrypted?) internet proxy that can store and forward packets. Instead of having the radio constantly on, it turns the radio on every 30s, for just long enough to register with the AP, and ask the proxy if it has new packets for it.
** An optimisation might be if the hardware, and the AP can do broadcast packets. The receiver is only turned on for .5s/30s, to recieve a broadcast packet saying 'you've got packets' without registering with the AP, or transmitting at all. The GPS synchronises the timing.
**This slows the initial connection to the phone, but most tcp/ip applications will not time out in 30s.

=====LED=====
*A blinking LED would be cheap and low power, good for informing the user about new SMS/Email....
**An alternative to this would be for one segment of the LCD to be seperately backlit. There are many LEDs in the backlight, all normally on. This has the advantage that you can display reasonable amounts of information on the bit of the screen that's illuminated.
**The disadvantage is the field of view is smaller, and it's dimmer than a bare LCD, as the LCD absorbs some light.
**This also requires the CPU and LCD to be somewhat active, to keep it refreshed.

*Note: the LED and button ideas could be combined: illuminated buttons
*A yellow LED for GSM/GPRS Tx burst, a blue one for Bluetooth/WiFi Tx burst, a green one for non-urgent notifications (sleep state, missed call etc.) and a red one for urgent notifications (battery almost drained out, new SMS etc.). All of this could be done in one, multicoloured (RGB) LED, similar to the nice one on the Yaesu VX-7R.

=====D-Pad and Buttons=====
*Adding a D-pad (to the bottom of the phone) and 2 to 4 buttons (to the top) would provide some tactile input controls, in addition to the touchscreen. They could be used as shortcut keys in the menu, or playback control when playing media. When the phone is held sideways, they can be used as games controls. (With touchscreen alone, gameplay options are limited)

=====Accelerometer=====
This enables the phone to sense where 'down' is - to enable various options.

*[[Wishlist:3D Viewport|3D Viewport]]
*[[Wishlist:Auto Align Map|Auto Align Map]]
*[[Wishlist:Computer Mouse|Computer Mouse]]
*[[Wishlist:Determine Position|Determine Position]]
*[[Wishlist:Distance Measuring|Distance Measuring]]
Change playlists when I'm jogging vs walking. (there ia an mp3 player on the market that does this).
*Can't the GPS information be used for that purpose? It should be possible to derive the phone's velocity from the change in coordinates over time, so such a playlist profile switcher should be a possibility even now already. [[User:Abraxa|Abraxa]] 00:09, 18 February 2007 (CET)
**Yeah in my opinion that is a very cool idea. But for that case the device should be much lighter. I wouldn't go jogging with a device with this size.--[[User:Denis std|denis_std]] 01:01, 18 February 2007 (CET)

=====SIR transceiver=====
*Could be used to detect when to turn off the display (if the low power IR signal is reflected) and activate the key lock. And could be used as a remote. iPhone has a proximity sensor.
*FIR would be nice as well, but I would settle for SIR if it would be added. Linux already has a working IrDA stack so the standard part would be satisfied. I would be more than glad to write lirc thingies for OpenMoko then :)

=====Standard 3.5mm jack=====
*I think everyone interested (and knowledgeable) enough to buy a Neo can make a 2.5mm male to 3.5mm female adaptor cable in under 1/2h and under 10EUR :-)

Certainly - now make it light, small, pretty, durable, tangle-free.
I want a 3.5mm jack. The only problem is - are headsets widely available in the same format as 2.5mm. --[[User:Speedevil|Speedevil]] 14:28, 16 February 2007 (CET)

=====Multitouch screen=====

=====Multi I/O adapter=====
*VGA, standard Jack (line in & out), standard USB

=====MMC/SD/SDIO slot (rather than?) miniSD or microSD=====
*Cheaper, more durable cards in a widely accepted format.
*Cards are harder to lose
*Wider selection of accesories, including SDIO accessories.
*Make externally available so that larger length SDIO cards can be used (thinking about SDIO WLAN here)
*Only because CF takes too much room (or CF would be the wish, instead)

=====[[Expansion Back]]=====
* Replacement backs with additional features
* I believe this would be a great idea, if put into practice. It would solve the ''extensibility'' need, usually associated with Open Source projects. It would allow for lots of other devices and for functionality to be developed and put into use without making it a burden for FIC.
** With extra card slots and small footprint hard drive (if possible), Neo might become a nice ''image tank'' for photographers - --[[User:Cedel|cedel]] 18:34, 19 February 2007 (CET)

=====Thumb keyboard or keyboard attachment accessory=====
*Could be slide out or clamshell (hinge on long side) design with an external OLED. The keyboard should be protected when not in use.
*Could be a clip on keyboard that attaches to the serial port or communicates by bluetooth (not preferred for permanent keyboard users).
*cheap clippable miniusb keyboard

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

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

=====EDGE support=====

=====Ability to insert more than one Sim-Card and (if possible) connect to more than one network at the same time=====

* This could be achieved via a specialist dual sim card kit (currently on market)- where two sims are trimmed and combined on one card, software support for dual sims would need providing...
* What about twin-SIMs (SIMs with 2 phone lines registered on them)? Conventional GSM phones have an option to switch between the two, older ones use # (long press before dialling) to do that. I'm guessing Calypso should support it, we just need to provide an interface for it :-) --[[User:Csdexter|@Dexter]] 11:34, 19 February 2007 (CET)

=====RFID tag=====
* Implementation/Cooperation with: [http://www.rfidguardian.org/ RFID-Guardian]
*Advantages of a RFID tag? I would see a lot privacy problems
**The tag could be switched on or off. A nice feature would be a module able to clone tags. This would unfortunately probably be rather expensive.
**What about an RFID Reader which could be used to locate items with RFID tags (IE: in your house) [[User:Alexpb|Alexpb]]
***That would be a nice feature--[[User:Denis std|denis_std]] 08:33, 17 February 2007 (CET)
***Most tags can only be located within 10cm or so. Essentially no cheap tags can be located over several metres.--[[User:Speedevil|Speedevil]] 13:17, 18 February 2007 (CET)

===== USB 2.0 =====
* Powered
* Host Mode / Device Mode
* OTG

=====UMTS support=====

=====Dump the '''''egg-shaped''''' case design and go '''''rectangular''''' for more screen space=====
*I'm all for devices that look great and have great features - aside from that I really like the current design. Thus I'd like to comment that the design change request is probably not the majority's opinion. [[User:Abraxa|Abraxa]] 00:00, 18 February 2007 (CET)

=====A standard slip-on or clip-on template (possibly with buttons) to make the touch-screen blind accessible=====

=====Speakerphone functionality=====

=====Reposition Speakers=====
* putting the two speakers on opposite sides of the screen would make the stereo sound much more effective

The screen is 2.8" across.
That's not especially effective.
Also, the speaker noise does come out the side - look at the grills in the pictures. --[[User:Speedevil|Speedevil]] 06:19, 16 February 2007 (CET)

=====Small metal frame for protection (like Siemens M65, only with more style)=====

=====Free GPIO ports on a connector to allow easy, simple hardware extensions=====

=====Video acceleration=====
Hardware acceleration for video playback.

=====3D acceleration=====
3D hardware acceleration for 3D games, GUIs, etc. (maybe a PowerVR MBX Lite ?).

=====Alcohol Sensor=====
Alcohol sensor adjacent to microphone. It doesn't have to be accurate, just has to detect any amount of alcohol on the speaker's breath. I understand this is a very narrow market, but alcohol is on every parent's mind.

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

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

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

=====EPD=====

Or electronic paper display, EPD is used in many new devices such as the new Motorola motofone, sonys new e-reader and Irex's iliad. The technology provides thin, flexible, power saving screens using new eink technology. This technology could cut the weight of the phone and its power usage. For more info see: [http://www.eink.com eink's website].

=====FM/Digital Radio(DAB) Reciever=====

A nice feature would be a radio reciever: FM or even better: [http://en.wikipedia.org/wiki/Digital_Audio_Broadcasting Digital Audio Broadcast] (Digital Radio)

=====V12 Embedded power source=====

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

=====Thermometer=====

An electronic thermometer might become handy for some users.

Maybe we could even integrate a [http://www.maxim-ic.com/ds2490 DS2490 usb-to-1wire chip] (about 15x10mm) in the phone along with a [http://www.maxim-ic.com/ds18s20 DS1820 1wire temperature sensor] and possibility (by internal or external connector) to add [http://www.maxim-ic.com/1-Wire.cfm further 1wire devices] like humidity sensors, secure authentication, buttons, keypads etc? The Linux kernel already happens to have a ds2490 driver.. This of course would require there to be a free internal usb port to connect the ds2490 to..

D-Bus

2007-02-19T19:35:15Z

Xkr47: added link to Dbus device API

D-Bus is a message bus system, a simple way for applications to talk to one another.

In OpenMoko we will use it for IPC.

See [http://www.freedesktop.org/wiki/Software/dbus dbus homepage]

Also see [[Dbus device API]]

Wishlist/Synchronized High Quality Recording

2007-02-19T19:14:03Z

Xkr47: add note that HighQualityRecordings article seems similar

{{Wishlist}}
{{note|This article seems similar to [[HighQualityRecordings]]}}

== The problem ==

If you do a phone interview the sound quality of interviewed will be limited by the sound quality of the phone. This can be improved by having a high quality recording done locally in both ends, followed by mixing the 2 high quality recordings. One of the problems by doing this is to synchronize the high quality recordings, so they start at the same time.

== The idea ==

Both the interviewer (here after Alice) and the interviewee (here after Bob) have a smartphone (or PC) that runs the Synchronized High Quality Recording program.

When Alice starts the interview she presses a button. This sends a signal (e.g. DTMF tones) to Bob's phone and then both phones starts a high quality recording exactly at the same time (the signal works like a clacker when filming). Alice will hear Bob in the normal phone quality, but Bob's phone will record the high quality.

When Alice ends the interview she presses a button. This sends a signal to Bob's phone to end the recording.

After the interview is done, Bob will have to send his recording to Alice. This can be done through the Internet.

The format of the recording could include the low quality audio from the other end. In a stero sound file the high quality recording would be in the left channel and the low quality in the right channel. This will make it easy to do the final mixing.

== Applications ==

Podcasters can use this to virtually have people in the studio.

It may be usable for keeping a record of a teleconference.

It may be usable for making a radio theater without needing to have the actors come in.

Inspired by an idea from [http://12078.net/grcnews/article.php?group=grc.thinktank&id=1861 www.grc.com newsgroups].

[[Category:ideas]]

Talk:History

2007-02-19T18:57:49Z

Xkr47: wiki formatting

--[[User:Caowai song|Chaowei.Song]] 01:32, 14 September 2006 (UTC)

Q1:At the [[View_Active_Applications|View Active Applications]], there is a application area, what will be display on this area? The original application view?

([[User:Sean | Sean Moss-Pultz]])

A: Correct. This is the just the orginal application (grayed-out perhaps) and shifted to the right by around 200 pixels. The specifics will be up the graphics designers.

([[User:Mickey | Mickey]])

Q2: Usability-wise, it might be better to donate all the screen space to show thumbnails for the different applications and just highlight the current application "thumbnail".

----

--[[User:Xkr47|xkr47]] 19:57, 19 February 2007 (CET)

Q: I think the wording in "I want to be able to quickly switch between previously run applications" is perhaps slightly misleading, perhaps "currently running applications" would be clearer?

Talk:History

2007-02-19T18:55:42Z

Xkr47:

--[[User:Caowai song|Chaowei.Song]] 01:32, 14 September 2006 (UTC)

Q1:At the [[View_Active_Applications|View Active Applications]], there is a application area, what will be display on this area? The original application view?

([[User:Sean | Sean Moss-Pultz]])

A: Correct. This is the just the orginal application (grayed-out perhaps) and shifted to the right by around 200 pixels. The specifics will be up the graphics designers.

([[User:Mickey | Mickey]])

Q2: Usability-wise, it might be better to donate all the screen space to show thumbnails for the different applications and just highlight the current application "thumbnail".

I think the wording in "I want to be able to quickly switch between previously run applications" is perhaps slightly misleading, perhaps "currently running applications" would be clearer?

Wishlist/Graphics Tablet

2007-02-19T15:55:42Z

Xkr47: potential use case: the gimp

{{Wishlist}}
The Neo1973 has a touchscreen. The touchscreen can be used to control a pointer on the screen. Using communication to a PC the touchscreen can control the pointer on the PC. The communication can be either USB or Bluetooth. Using this it should be possible to emulate a simple graphics tablet.

-- [[User:Xkr47|xkr47]]: yeah, I think it could be nice to use with [http://www.gimp.org/ The Gimp] :)

== Option: Display screen on smartphone ==

Depending on the bandwidth it may be possible to replicate either part of or a scaled down version of the PC's screen directly on the smartphone. To do this the driver must be a bit more advanced. It might consist of 2 parts: The graphics tablet driver and a facility to transfer the screen. VNC or FreeNX might solve this.

== Option: Pressure sensitivity ==

The Neo1973 has a screen that is capable of multitouch, only the driver is missing. If multitouch is available, then pressure sensitivity may be possible: The harder you press the finger, the bigger the area your finger covers. If the sensitivity is really good you may be able to use a brush directly on the screen. The physical brush will also provide the tilt functionality.

Cite? It's been stated that later versions may do multitouch, where is it metioned that this one can, which would be great?
--[[User:Speedevil|Speedevil]] 15:05, 19 February 2007 (CET)

[[Category:ideas]]

User talk:Minime

2007-02-19T14:27:56Z

Xkr47: oops cannot link to categories :P

-- [[User:Xkr47|xkr47]]: Hi. You created a new Category:Wishlist, but there exists one Category:Ideas already which has been widely used and I think is pretty much the same.. I think either is enough, so maybe we could all use Category:Ideas? What do you think? Btw full list of categories can be seen [[Special:Categories|here]].

User talk:Minime

2007-02-19T14:25:50Z

Xkr47:

-- [[User:Xkr47|xkr47]]: Hi. You created a new [[Category:Wishlist]], but there exists one [[Category:Ideas]] already which has been widely used and I think is pretty much the same.. I think either is enough, so maybe we could all use Category:Ideas? What do you think? Btw full list of categories can be seen [[Special:Categories|here]].

I2C

2007-02-19T08:18:55Z

Xkr47: added links

I2C is a simple communication standard intended to move small amounts of data a few inches between chips.
See [http://en.wikipedia.org/wiki/i2c wikipedia].

We currently use the following addresses on the I2C bus:
{|
| '''Device''' || '''I2C address'''
|-
| [[PCF50606]] || 0001 000x
|-
| [[WM8753L]] || 0011 010x
|-
| [[LM4857]] || 1111 100x
|}

Note that I2C addresses are 7 bit. The last bit, which is not part of the address, indicates whether this is a read or write operation. So "0001 000x" is 0x8, not 0x10.

WM8753L

2007-02-19T08:18:28Z

Xkr47: redirect to WM8753

#REDIRECT [[WM8753]]

Building OpenMoko 2007.1 from scratch

2007-02-17T21:00:42Z

Xkr47: Added link to "How to run OpenMoko Apps on PC"

{|align=right
|__TOC__
|}

This is a guide describing how to set up a running OpenMoko
system from scratch.

If you just want to run OpenMoko applications on your PC, just perform the
"Obtaining OpenMoko SVN tree" step below and then go to
[[How to run OpenMoko Apps on PC]].

Do not treat this as a linear script! There are various configuration items you
need to set (or skip, as it may be), operations that depend on how your
host(s) is/are set up, and also on the hardware revision of the target platform
(i.e., the phone).

Instead, look at each step, read the instructions, copy and paste what
makes sense for you, and adapt what you disagree with. Links to original and
background material in the Wiki are included wherever useful.

== Preparation ==

=== Roles ===

The build process may spread over multiple machines. They have the following
roles:

;'''BUILD''': build host, with quick access to the files and CPU power. Must have Internet access.
;'''LAB''': lab machine connected to the debug board (serial and JTAG) and to USB on the Neo (since this will probably be just a single machine, the roles are not further divided)
;'''CARD''': machine with a USB-attached SD/MMC card reader

All machines are assumed to share the same filesystem layout. At the beginning of
each of the sections below, the respective role is indicated. "('''all''')" is for
settings that apply to all machines, or that - for simplicity - can be
applied to all of them.

=== Directory layout ===
'''(Roles: all)'''

<pre>
$OMDIR (/home/moko) base directory for the whole tree
openmoko/ files from OpenMoko subversion (SVN) repository
openembedded/ files from OpenEmbedded (OE) Monotone repository
sources/ cached downloads of OE
build/ OE build directory
</pre>

=== Environment variables ===
'''(Roles: all)'''

For simplicity, we just set these environment variables on all hosts
involved. If you're not comfortable with this, feel free to weed out the ones
you don't need.

Our base directory (configure this for local arrangements):

export OMDIR=/home/moko

The search path for BitBake files. Note that the order is of vital
importance.

export BBPATH=$OMDIR/build:$OMDIR/openmoko/trunk/oe:$OMDIR/openembedded

=== Permissions ===
'''(Role: BUILD)'''

In order to perform the build process, you have to obtain the following
permissions:

* write access to the OpenMoko SVN repository (in principle, it should be possible to simplify this to read access. For further study.)

=== Build host prerequisites ===
'''(Role: BUILD)'''

There must be at least 7 GB of free space on $OMDIR.

In addition to the traditional development tools (gcc, patch, etc.), the
following packages must be installed on the build host:

;subversion: version control system used by OpenMoko and others
;quilt: patch management system used by the Linux kernel and others
;monotone: version control system used by OpenEmbedded. This should be a recent version, e.g., 0.32, although also 0.31 should work.
;diffstat: the OE build process wants this
;texi2html: this too
;git: version control system used by the Linux kernel and others. Do not confuse this with the "GNU Interactive Tools"

Furthermore, the following package can be installed optionally:
;psyco: Python just-in-time compiler. Speeds up OpenEmbedded builds (with BitBake) considerably. Strongly recommended.

Gentoo users can obtain all this with (note that, at the time of writing, Monotone 0.32 isn't available without setting the ~x86 keyword):

<pre>
echo 'dev-util/monotone ~'`readlink /etc/make.profile | awk -F / '{print $6}'`\
>>/etc/portage/package.keywords
emerge -u subversion quilt monotone diffstat texi2html dev-util/git psyco
</pre>

[http://www.openembedded.org/wiki/OEandYourDistro Instructions for installing prerequisites in other distributions]

If the local user name does not match the user name with which you access SVN, you can put your username in the url you use to checkout, eg. svn+ssh://joe@stuff.org/svn/stuff.

=== Lab host prerequisites ===
'''(Role: LAB)'''

The following package must be installed on the lab host:
;xc: a simple communications program for the serial port

Gentoo users can obtain this with:
emerge -u xc

Note that similar communications programs, such as "cu" or "minicom", may be used as well.

=== Assumptions ===
'''(Roles: LAB, CARD)'''

We make the following assumptions about hardware setup and devices:

* the serial console of the Neo phone is connected to /dev/ttyS0 on '''LAB''' (see [[Debug_Board]])
* the JTAG [[wiggler]] is connected to /dev/parport0 on '''LAB'''. See [[Debug Board]] and [[Connecting_GTA01Bv2_with_Debug_Board]]
* cards inserted in the SD/MMC card reader appear as /dev/uba on '''CARD''' and can be mounted on /mnt/tmp (we'll specify the mount point explicitly, so the directory has to be there, but we don't need to specify the mount point in /etc/fstab). If in doubt,
mkdir -p /mnt/tmp

== Obtaining Sources and build system ==

=== OpenEmbedded build: initial downloads ===

First, we obtain a snapshot of the OpenEmbedded-based tree used by OpenMoko, plus the OE build tool called BitBake.

==== Obtaining OpenMoko SVN tree ====
'''(Role: BUILD)'''

Obtain revision 1004 of the OpenMoko tree. This is a "known to be good", version (provided the fixes below are applied). Unfortunately, at some places, "current" versions of upstream packages may get included, thus the build may still fail. If it does, you may wish to inform the authorities.

The checkout should take about 45 minutes over an Internet connection with a round-trip time to svn.openmoko.org of 350 ms.

<pre>
cd $OMDIR
svn co -r 1004 http://svn.openmoko.org/ openmoko
</pre>

==== Installing BitBake ====
'''(Role: BUILD)'''

Install version 1.6 of BitBake, the build tool of OE. (This is quick.)

<pre>
svn co http://svn.berlios.de/svnroot/repos/bitbake/branches/bitbake-1.6/ bitbake
cd bitbake
./setup.py install
cd ..
</pre>

==== Obtaining OpenEmbedded snapshot ====
'''(Role: BUILD)'''

Obtain a snapshot of the Monotone repository of OpenEmbedded, then update it
to the latest version, and finally check out our "known to be good" revision.
We extract things into $OMDIR/openembedded. OE.mtn.bz2 is about 100 MB.

<pre>
wget http://www.openembedded.org/snapshots/OE.mtn.bz2
bunzip2 OE.mtn.bz2
mtn --db=OE.mtn pull monotone.openembedded.org org.openembedded.dev
mtn --db=OE.mtn checkout --branch=org.openembedded.dev \
-r f499733e6db527846e1a48cf70f9862d6b3798ae openembedded
</pre>

{{note|For advanced users: if you ever want to update to the latest version of the repository, you would do a "pull" (see above), followed by:
cd $OMDIR/openembedded && mtn update}}

Set up the directories for the cache of upstream files and all material
related to local builds, then put our configuration file there (see also
[[OpenMoko#Setting_up_an_OpenMoko_SDK]]):

<pre>
mkdir -p sources build/conf
cat <<EOF >build/conf/local.conf
MACHINE = "fic-gta01"
DISTRO = "openmoko"
BUILD_ARCH = "`uname -m`"
EOF
</pre>

=== OpenEmbedded build: fixes ===
'''(Role: BUILD)'''

There are unfortunately some problems in the build process.
The following fixes work around them:

cd $OMDIR/sources
mkdir -p ../build/tmp/stamps/armv4t-linux

* upstream moves old packages away, gratuitously breaking downstreams

wget http://ftp.mozilla.org/pub/mozilla.org/js/older-packages/js-1.5.tar.gz
touch ../build/tmp/stamps/armv4t-linux/js-1.5-r0.do_fetch

* us2.samba.org mirror has vanished

wget http://us4.samba.org/samba/ftp/stable/samba-3.0.14a.tar.gz
touch ../build/tmp/stamps/armv4t-linux/samba-3.0.14a-r15.do_fetch

* ghastly patch with CRLF and trailing blanks

perl -pi.orig -e 's/ *$//;s/\r//g' \
../openembedded/packages/gcc/gcc-4.1.1/gcc-4.1.1-pr13685-1.patch

== Building ==

=== OpenEmbedded build ===
'''(Role: BUILD)'''

openmoko/trunk/oe/conf/site.conf expects the OpenMoko-specific OE packages in $OMDIR/oe

cd $OMDIR
ln -s openmoko/trunk/oe .

We're now ready to run the build. This will take a while.

cd $OMDIR/build
bitbake openmoko-devel-image

Note that the build will stop several times to ask for SVN access and whether
to accept certificates. If you're not quick enough to respond, the underlying
session may time out. In this case, just restart "bitbake
openmoko-devel-image" and it will pick up from where it left off.

The whole build process involves numerous downloads, takes about 7 hours
on an Athlon 64 3200+ (about 1.5h of delays were caused by ftp.debian.org not
working properly during this test run), and ends with a message like this:

Build statistics:
Attempted builds: 4

== Installation ==

=== Flash boot loader into NAND ===
'''(Role: LAB)'''

As a first step, we transfer the u-boot bootloader into NAND Flash, through
the JTAG interface. We use JTAG, since this is the most basic way for doing
this, ensuring that we only depend on as little to work on the Neo as
possible.

For this, the u-boot image for the right board version and the desired
build date must be chosen. E.g., an image built for a gta01bv2 board on
February 3, 2007 at 13:40:41 would be called
u-boot_nand-gta01bv2-20070203134041.bin

The name is composed as follows:
;u-boot: the name of the component
;nand: it is it be loaded from NAND (not directly from RAM, see also [[Bootloader#Using_JTAG_to_boot_from_RAM]])
;gta01bv2: the hardware revision of the board
;20070203134041: the build date and time
;.bin: this is a binary suitable for flashing/loading

If this is the first build, there will only be one image for each board
version, thus we can use wildcards. Change the gta01bv2 below to gta01v3 or
gta01v4, if necessary.

See also: [[Sjf2410-linux]]

<pre>
cd $OMDIR/build/tmp/deploy/images

( echo 0; echo 0; echo 0; echo 3; ) |
./sjf2410 -b -f `echo u-boot_nand-gta01bv2-*.bin`
</pre>

This will take approximately 12 minutes.

=== Copy kernel and root FS to microSD card ===
'''(Role: CARD)'''

There are several ways to provide the Neo with its kernel and the root file
system. (See [[Bootloader]] for some of them.)
The most self-contained way is to put everything into NAND Flash.
To transfer the files to the Neo, we first place them on the microSD card.

Memory cards, including microSD, usually come pre-formatted with VFAT. We
prefer ext2 (e.g., because we may want to store a real Linux file system on the
card as well). The following steps are needed to convert the card from VFAT to
ext2:
<pre>
sfdisk -c /dev/uba 1 83
mke2fs -m0 /dev/uba1
tune2fs -c0 -i0 /dev/uba1
</pre>

Next, we copy the kernel uImage and the root file system image to the card.
As discussed in the previous section, we can use wildcards if this is our
first build.
<pre>
cd $OMDIR/build/tmp/deploy/images
mount /dev/uba1 /mnt/tmp
cp uImage-2.6-moko7-r1-fic-gta01-*.bin /mnt/tmp/uImage
cp openmoko-devel-image-fic-gta01-*.rootfs.jffs2 /mnt/tmp/rootfs.jffs2
umount /mnt/tmp
</pre>

Now, insert the microSD card into the Neo, but don't power it on yet.
(If you did anyway, don't worry. We'll power cycle it later.)

=== Serial console ===
'''(Role: LAB)'''

We use a serial console connecting through the debug board. This example uses
"xc", which is a small and simple communications program. Many people prefer
"cu" or the considerably more bloated "minicom", which will work as well.

* Prepare xc configuration
<pre>
cat <<EOF >$HOME/xc.init
set bps 115200
terminal
EOF
</pre>

* Connect to the target
xc -l /dev/ttyS0 -t

=== Start the Neo and enter the boot prompt ===
'''(Role: LAB)'''

Our first interaction with the target. If this doesn't work, please check
that the debug board is connected properly to the serial port.

Disconnect power and USB from the phone, wait a couple of minutes, then connect power.
You may have to press and hold the power button on the Neo for a few seconds to turn it on.
The power button is located next to the USB port.

Some people have observed stability issues if the device was reset without
power cycling or if USB was not disconnected when power cycling, yet details of what is really happening aren't very clear yet.

On the serial console, a message like this should appear:
<pre>
U-Boot 1.2.0 (Feb 3 2007 - 13:07:21)
Press any key to enter the boot prompt:
GTA01Bv2 #
</pre>

Note that the boot prompt changes with the hardware revision you have. If the
message does not appear after a few seconds, try power cycling again.

If xc responds to pressing a button with
"Verify that you are trying to use a valid and operational tty port."
the port may be stuck, waiting for DCD to be asserted. The quickest way to
get out of this situation is to disconnect the serial cable from the debug
board, run the following command
while ! stty -F /dev/ttyS0 clocal; do : ; done

stick something metallic, e.g., a paper clip or a screwdriver, into the plug on the cable,
and keep on fumbling with
it until DCD gets set and the loop above stops spitting out error messages.

=== Flash kernel and root FS into NAND ===
'''(Role: LAB)'''

We now load the kernel and the root FS from the microSD card into memory and
subsequently transfer them to NAND Flash. All this is done by entering
commands at the boot prompt.

Each time we want to write new data to the NAND Flash, we first have to erase
the previous content. We do this individually for each partition. While it would
also be possible to erase some or all relevant partitions in one step, this would
require the user to look up addresses from the partition table and to perform
calculations which are inconvenient at best.

See also: [[U-boot]]

* Initialize the SD/MMC interface. The "Product Name" shown will be just binary garbage. This is expected behaviour.

GTA01Bv2 # mmc

* Load the uImage file into memory. "ext2load" stores the number of bytes read as a hexadecimal number in the environment variable "filesize".

GTA01Bv2 # ext2load mmc 0 0x32000000 uImage

* Erase the kernel partition and write the uImage from memory to NAND Flash

GTA01Bv2 # nand erase kernel
GTA01Bv2 # nand write.e 0x32000000 kernel ${filesize}

* The root file system is next. We need to specify the correct size, which is shown at the end of "ext2load", e.g., "0x1608000)" in this case:

GTA01Bv2 # ext2load mmc 0 0x32000000 rootfs.jffs2
23101440 (0x1608000) bytes read
GTA01Bv2 # nand erase rootfs
GTA01Bv2 # nand write.e 0x32000000 rootfs ${filesize}

=== Configure the boot loader ===
'''(Role: LAB)'''

Last but not least, we have to set up the boot loader to automatically boot
from Flash. For this, we use the default environment settings, which we obtain
by erasing the old content of the environment, and letting u-boot restore the
settings after a restart.

Before touching the environment, you may have to update the environment offset.
Please see [[Migration_to_bad_block_tolerant_builds#Partition_sizing]] for details.
(We may simplify this particularly awkward and error-prone procedure in the
future.)

* First, remove erase the old environment:
GTA01Bv2 # nand erase env

* We reset to force the boot loader to use the default settings.
GTA01Bv2 # reset

Wait until the "U-Boot [...]" message, then hit a key. It will display
*** Warning - bad CRC or NAND, using default environment

* Re-generate the partition information in the environment variable "mtdparts":

GTA01Bv2 # dynpart

* Save the restored settings in NAND
GTA01Bv2 # saveenv

* Power cycle to boot the Neo (see remarks above)

== END ==

'''Congratulations !''' You've just completed level 1 of the OpenMoko adventure.

How to run OpenMoko Apps on PC

2007-02-17T20:53:21Z

Xkr47: /* Set up the environment */ fixed typo

===Install dependencies===

* use aptitude, apt-get, urpmi, or whatever your distro supports
* you will probably need
** gtk-dev
** pango-dev
** atk-dev
** qmake from Qt4 (libqt4-dev on Debian) -- this is optional and required only if you do not use auto-tools method

* Under ubuntu: apt-get install libgtk2.0-dev pulls in everything necessary

===Build the binaries===
====Build using GNU auto-tools====

=====Set up the environment=====

export OPENMOKODIR=<svn-checkout>/src/target/OM-2007
cd $OPENMOKODIR/openmoko-libs
./autogen.sh
make
sudo make install

This will install the libraries in /usr/local/lib. If you prefer a non-system location, edit autogen.sh (and remember that an SVN update may undo that) to add a "--prefix=MYDIR" option for where you want to put the compiled stuff. You can the run "make install" without sudo. One approach is to put stuff at the source root, by appending the option: "--prefix=$OPENMOKODIR".

=====Compiling sample apps=====

cd $OPENMOKODIR/examples/...
./autogen.sh
make
sudo make install

If you used --prefix in the previous step to place the libraries elsewhere, make sure you edit autogen.sh to reflect that. I guess the proper way to do this is to set the PKG_CONFIG_PATH variable. You can of course drop the sudo then.

...
export PKG_CONFIG_PATH=$OPENMOKODIR/lib/pkgconfig
./configure ...

====Build using QMake (the mickeyl way)====
{{Note|qmake is Mickey's preferred build tool, it probably doesn't work if you're not him. Please use autotools...}}

=====Build everything in one run using Qmake=====

cd <svn-checkout>/src/target/OM-2007
. ./makevars.sh
qmake
make

Now the applications should be found in ./bin.

===Run the examples===

====Set your theme to OpenMoko====

Edit $HOME/.gtkrc-2.0 to something like that:

include "<PATH-to-svn-checkout>/src/target/OM-2007/artwork/themes/openmoko-standard/gtk-2.0/gtkrc"

==== Naked execution ====

bin/openmoko-stylus-demo
bin/openmoko-finger-demo
bin/openmoko-chordmaster

==== Execution within Xoo ====

Adjust svn://src/target/OM-2007/devel/scripts/launch-xoo to your needs (you may need to build some dependencies forehand)
Then set DISPLAY=:1 and run the examples

Openmoko:Searching

2007-02-17T17:26:57Z

Xkr47: Added link to wikipedia

See [http://en.wikipedia.org/wiki/Wikipedia:Searching Wikipedia searching help]

User:Xkr47

2007-02-17T16:44:32Z

Xkr47: links

User:Xkr47

2007-02-17T16:25:39Z

Xkr47: links

Me:
* relationship with openmoko: [[Buying_Interest_List|phase 1 customer]]
* [http://xkr47.outerspace.dyndns.org/ my homepage]
* [http://sourceforge.net/people/viewprofile.php?user_id=66259 my computer-related skills]
* [http://www.google.com/search?q=xkr47+OR+jberlin%40niksula+OR+jberlin%40cc+OR+outerspace.dyndns.org my internet resumé]
*

Wishlist for my openmoko:

* basic telephony
* automatic [[Screen Saver|screensaver]] & locker
** require code/password/gesture to unlock
* [[Messages|SMS sending and reception]]
* SMS mirroring to home server
* remote GUI app connected to home server when SMS arrives / phone is ringing / other important event (battery low) in case I can't hear the phone when it's in my backpack
* MMS sending & reception - outgoing pics taken with external USB-connected digital camera
* Integration with local public transportation services which provides clickable maps --> GPS can be used to automatically "go home from wherever I happen to be"
* ssh client
* "Status" app or [[Today|similar]] with multiple small windows aka gadgets / widgets that report different stats e.g. ssh (for irc), SMS, missed calls, next calendar entries, profile, tv programme etc, [http://en.wikipedia.org/wiki/Digital_video_recorder DVR] status
* Switch to "status" app automatically if user idles long enough
* [[Calendar]]
* automatic (weekly or calender-based) and [[Clock|manual alarm clock]]
* [[Profiles|Profile]] changes:
** programmable - time, location & calendar based
** manual profile override with timeout - cinema, sleep, meeting
* allow use of event (incoming phone call, sms message etc) metadata (who called, what time) to override profile settings
* screensaver that shuts the screen completely off, not just the backlight
** one click in screensaver mode -> screen in "on" mode but backlight still off, tune X color settings so that the contrast is increased to improve readbility
** second click -> backlight on as well, color settings back to normal
* SMS writing without stylus - maybe some basic 123 456 789 *0# onscreen keyboard with [http://en.wikipedia.org/wiki/T9_(predictive_text) T9] or similar
* one-click publishing of pictures taken with external digital camera to home web server

Hopefully my skills will let me implement at least some of these :)