Openmoko - User contributions [en]

Flashing the Neo 1973

2007-08-06T10:45:04Z

Cayco: /* Actually flashing things into the device */

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

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.*-moko10-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-06T10:44:28Z

Cayco: /* Actually flashing things into the device */

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

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.*-moko10-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).

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

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

Mac OS X

2007-08-03T13:08:10Z

Cayco: /* Bluetooth */

Welcome to the OpenMoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 (and maybe other OM devices) with Mac.

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

Here is a detailled instruction:
# download AJZaurusUSB-0.5.2 from http://www.dsitri.de/wiki.php?page=AJZaurusUSB&referer=OpenMoko%20Flasher
# install
# reboot your Mac so that the driver becomes active (you do not yet need to configure the network interface)
# download OpenMoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher&referer=OpenMoko%20Flasher
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# open the Console application and show the console.log
# Now, on your OpenMoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Flash
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# if it fails (console.log should show the reasons), unplug the OpenMoko shortly and replug
# if it successfully flashed, you should be able to boot the OpenMoko and continue configuring AJZaurusUSB

= Connecting to your device =

== USB ==

You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

MacOS X does not provide such a driver for RNDIS/Ethernet Gadget. But you can use an open source (GPL) universal driver http://www.dsitri.de/wiki.php?page=AJZaurusUSB which is developed for handheld devices like iPAQ, Sharp Zaurus, and Motorola A760. Download it and install according to manual found inside of the package.

After reboot, you should have a new Ethernet interface in your System Preferences/Network. Set up the network manually for that interface by using these addresses:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.201
Subnet: 255.255.255.0
Router: 192.168.0.202
</pre>
This might conflict with some WLAN routers which also use the 192.168.0.0 network.

You should be able to connect to your Neo! Try using ping 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.

NOTE: it appears that after each reboot of the OpenMoko you get a new interface on the Mac (this is under investigation).

== Telnet, ssh, SMB ==

To Be Done.

=== ssh ===

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

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

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

== Bluetooth ==

To Be Done.

== WiFi ==

To Be Done.

= Synchronizing =

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

= Sharing connection =

== Mac as a server ==

Here is described how to enable your Mac to serve as a internet router for your OpenMoko device.

=== Bluetooth ===

This could help:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking

http://www.macosxhints.com/article.php?story=20051220221237711

=== USB ===

If you install AJZaurusUSB driver you should be able to set up your Mac as a router (not tested).

== Neo1973 as a server ==

To Be Done.

= Developing software =

== Using virtualization software==

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

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

== Natively ==

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

[[Category:Developer software]]

Talk:Mac OS X

2007-08-03T13:01:30Z

Cayco:

cayco: NOTE: it appears that after each reboot of the OpenMoko you get a new interface on the Mac (this is under investigation). - I am experiencing the same behaviour.

Mac OS X

2007-08-03T12:44:38Z

Cayco: /* USB */

Welcome to the OpenMoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 (and maybe other OM devices) with Mac.

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

Here is a detailled instruction:
# download AJZaurusUSB-0.5.2 from http://www.dsitri.de/wiki.php?page=AJZaurusUSB&referer=OpenMoko%20Flasher
# install
# reboot your Mac so that the driver becomes active (you do not yet need to configure the network interface)
# download OpenMoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher&referer=OpenMoko%20Flasher
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# open the Console application and show the console.log
# Now, on your OpenMoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Flash
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# if it fails (console.log should show the reasons), unplug the OpenMoko shortly and replug
# if it successfully flashed, you should be able to boot the OpenMoko and continue configuring AJZaurusUSB

= Connecting to your device =

== USB ==

You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

MacOS X does not provide such a driver for RNDIS/Ethernet Gadget. But you can use an open source (GPL) universal driver http://www.dsitri.de/wiki.php?page=AJZaurusUSB which is developed for handheld devices like iPAQ, Sharp Zaurus, and Motorola A760. Download it and install according to manual found inside of the package.

After reboot, you should have a new Ethernet interface in your System Preferences/Network. Set up the network manually for that interface by using these addresses:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.201
Subnet: 255.255.255.0
Router: 192.168.0.202
</pre>
This might conflict with some WLAN routers which also use the 192.168.0.0 network.

You should be able to connect to your Neo! Try using ping 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.

NOTE: it appears that after each reboot of the OpenMoko you get a new interface on the Mac (this is under investigation).

== Telnet, ssh, SMB ==

To Be Done.

=== ssh ===

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

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

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

== Bluetooth ==

To Be Done.

== WiFi ==

To Be Done.

= Synchronizing =

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

= Sharing connection =

== Mac as a server ==

Here is described how to enable your Mac to serve as a internet router for your OpenMoko device.

=== Bluetooth ===

This could help: http://www.macosxhints.com/article.php?story=20051220221237711

=== USB ===

If you install AJZaurusUSB driver you should be able to set up your Mac as a router (not tested).

== Neo1973 as a server ==

To Be Done.

= Developing software =

== Using virtualization software==

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

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

== Natively ==

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

[[Category:Developer software]]

Customizing the Openmoko Distribution

2007-08-03T10:35:44Z

Cayco: /* Your First Compilation */

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

This is because python is not included by default in the openmoko image. Or you can use <code>python-gtk</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 applicaiton"
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]]

Mac OS X

2007-08-02T07:14:33Z

Cayco: /* USB */ fixed formatting

Welcome to the OpenMoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 (and maybe other OM devices) with Mac.

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

This can be done by Dfu-util manually. A precompiled version (Universal Binary??? for OS X 10.4) can be found here: -link to be provided-

There is (well, will be) a OpenMoko Flasher application that wraps dfu-util with a nice GUI.

= Connecting to your device =

== USB ==

You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection. MacOS X does not provide such a driver for RNDIS/Ethernet Gadget. A universal driver for devices like the OpenMoko coming from the Linux on iPAQ and Sharp Zaurus projects is http://www.dsitri.de/wiki.php?page=AJZaurusUSB Download it and install according to manual found inside of the package.

Up to and including release 0.5.1 you need to patch the following file (before rebooting!) /System/Library/Extensions/AJZaurusUSB.kext/Contents/Info.plist

<pre>
<key>OpenMoko</key>
<dict>
<key>CFBundleIdentifier</key>
<string>net.lucid-cake.driver.AJZaurusUSB</string>
<key>IOClass</key>
<string>net_lucid_cake_driver_AJZaurusUSB</string>
<key>IOProbeScore</key>
<string>90000</string>
<key>IOProviderClass</key>
<string>IOUSBDevice</string>
<key>defaultIP</key>
<string>192.168.0.202</string>
<key>idProduct</key>
<integer>20770</integer>
<key>idVendor</key>
<integer>5207</integer>
</dict>
</pre>

After reboot, you should have a new ethernet interface in your System Prefereces. Set up the network manually for that interface and then set up your network manualy on the Neo1973. You should be able to connect to your Neo! Try using ping.

== Telnet, ssh, SMB ==

To Be Done.

== Bluetooth ==

To Be Done.

== WiFi ==

To Be Done.

= Synchronizing =

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

= Sharing connection =

== Mac as a server ==

Here is described how to enable your Mac to serve as a internet router for your OpenMoko device.

=== Bluetooth ===

This could help: http://www.macosxhints.com/article.php?story=20051220221237711

=== USB ===

If you install AJZaurusUSB driver you should be able to set up your Mac as a router (not tested).

== Neo1973 as a server ==

To Be Done.

= Developing software =

== Using virtualization software==

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

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

== Natively ==

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

[[Category:Developer software]]

Mac OS X

2007-07-31T07:31:34Z

Cayco: /* Natively */

Welcome to the OpenMoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 (and maybe other OM devices) with Mac.

= Connecting to your device =

== USB ==

You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection. The only driver I know is http://www.dsitri.de/wiki.php?page=AJZaurusUSB Download it and install according to manual foung inside of the package.

You should have new ethernet interface in your System Prefereces. Set up network manually for that interface and then set up your network manualy on the Neo1973. You should be able to connect to your Neo!

== Bluetooth ==

To Be Done.

== WiFi ==

To Be Done.

= Synchronizing =

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

= Sharing connection =

== Mac as a server ==

Here is described how to enable your Mac to serve as a internet router for your OpenMoko device.

=== Bluetooth ===

This could help: http://www.macosxhints.com/article.php?story=20051220221237711

=== USB ===

If you install AJZaurusUSB driver you should be able to set up your Mac as a router (not tested).

== Neo1973 as a server ==

To Be Done.

= Developing software =

== Using virtualization software==

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

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

== Natively ==

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

Mac OS X

2007-07-31T07:23:01Z

Cayco:

Openmoko under QEMU on MacOSX

2007-07-28T21:18:11Z

Cayco: /* Building dfu-util */

Warning: this is draft!

I try to put here my notes on setting up OpenMoko environment (Qemu and MokoMakefile) on Mac OS X.

= Introduction =

Some time ago I ask if anyone has ever set up OpenMoko environment on MacOS X. No one has answered that he did but several people were interested. So I deceided to wrote some directions on how to do that.

As for now I was not successful but I am still trying ;)

= Setting up environment =

== Prequisites ==

Install fink and darwinports (both have neccesary packages).

Follow instructions on:
http://www.openembedded.org/wiki/BuildOnOSX
to set up OE environment.

It is neccessary to create new disk image, just as BuildOnOSX says.

If you're compiilng something connected with X11 be sure to install X11devel package from your MacOS X CD1.

You can get mentioned packages using darwinports:

<pre>
sudo port install quilt
sudo port install py-psyco
sudo port install cogito
sudo port install gawk
fink install sed
</pre>

Then get Q[kju] project: http://www.kju-app.org/proj/wiki/CompilingQ into /Volumes/OE/Q but do not compile it yet (run only "prepare the sources"). This will be needed for compiling Neo1973 emulator.

Set up environment as described in MokoMakefile:

<pre>
cd /Volumes/OE
mkdir moko; cd moko
wget http://www.rwhitby.net/files/openmoko/Makefile

make setup
</pre>

= Making developers image =

<pre>
make openmoko-devel-image
</pre>

I had problems with bitbake - it does not run correctly with psyco (I got "Illegal instruction error" and make exited with error 132) so I had to disable it: I run bitbake -d openmoko-devel-image in MokoMakefile.

Also, I ended up with:

<pre>
ERROR: Error in executing: /Volumes/OE/moko/openembedded/packages/quilt/quilt-native_0.45.bb
ERROR: Exception:exceptions.UnboundLocalError Message:local variable 'md5data' referenced before assignment
</pre>

I found out that I did not have md5sum which is used by bitbake. I found it in testutils packages from fink. Installing it did not help... I got pissed and temporarily changed

vim /Volumes/OE/moko/bitbake/lib/bb/fetch/wget.py +114

so it look like this

<pre>
# supposedly complete.. write out md5sum
md5data = ""
if bb.which(data.getVar('PATH', d), 'md5sum'):
try:
md5pipe = os.popen('md5sum ' + dl)
md5data = (md5pipe.readline().split() or [ "" ])[0]
md5pipe.close()
except OSError:
md5data = ""

# verify the md5sum
#if not verify_md5sum(wanted_md5sum, md5data):
# raise MD5SumError(uri)
</pre>

As you can see there I disabled md5sum verification.

If you have error like this

<pre>

| checking for sed... /usr/bin/sed
| checking whether /usr/bin/sed understands (foo|bar)... no
| configure: error:
| Sorry, you have a version of sed which doesn't understand constructs
| of the form (foo|bar). quilt needs it. If you have access to
| a version of sed which does understand such constructs, you can supply
| its path with the '--with-sed=' option.
</pre>

Install GNU sed from fink.

Now you should have:

<pre>
| libbb.h:53:22: error: features.h: No such file or directory
</pre>

while compiling ipkg. Run following patches in folder:

<pre>
cd /Volumes/OE/moko/build/tmp/work/i386-darwin/ipkg-native-0.99.163-r1/ipkg-0.99.163/
</pre>

apply this patch

<pre>
perl -pi -e 's,struct errlist\*,extern struct errlist\*,g' ipkg.h.in
perl -pi -e 's,#include "libbb.h",#include "libbb.h"\nstruct errlist\* error_list;,g' libbb/error_msg.c

### fix endian.h include in md5.c
perl -pi -e 's,#include \<endian.h\>,#ifndef __APPLE__\n# include \<endian.h\>\n#else\n# include \<machine/endian.h\>\n#endif,g' md5.c

### fix vfs.h include in ipkg_utils.c
perl -pi -e 's,#include \<sys/vfs.h\>,#ifndef __APPLE__\n# include \<sys/vfs.h\>\n#else\n# include \<sys/mount.h\>\n#endif,g' ipkg_utils.c

### remove un-needed features.h include from libbb/libbb.h
perl -pi -e 's,#include \<features.h\>,#ifndef __APPLE__\n# include \<features.h\>\n#endif,g' libbb/libbb.h

### dirname already defined OS X
perl -pi -e 's,char \*dirname $char \*path$;,#ifndef __APPLE__\nchar \*dirname $char \*path$;\n#endif,g' libbb/libbb.h

### Use fink dir for etc
perl -pi -e 's,/etc,%p/etc,g' args.h

### Add define for strndup
perl -pi -e "s,#include \"xsystem.h\",#include \"xsystem.h\"\n\n#ifndef HAVE_STRNDUP\nstatic void\*\nstrndup $const char \*src\, size_t n$\n\{\n size_t i;\n char \*dst;\n\n if $src == NULL$\n return NULL;\n\n dst = $char*$ malloc $n + 1$;\n if $dst != NULL$ \{\n for $i = 0; i \< n \&\& src\[i\]; i++$\n dst\[i\] = src\[i\];\n dst\[i\] = '\\\0';\n \}\n\n return dst;\n\}\n#endif,g" ipkg_conf.c
</pre>

Now I get:

<pre>

| Extracting /Volumes/OE/moko/build/tmp/work/i386-darwin/ipkg-native-0.99.163-r1/ipkg-0.99.163/libbb/.libs/libbb.a
| gcc -dynamiclib ${wl}-flat_namespace ${wl}-undefined ${wl}suppress -o .libs/libipkg.0.0.0.dylib .libs/libipkg_la-args.o .libs/libipkg_la-libipkg.o .libs/libipkg_la-user.o .libs/libipkg_la-ipkg_cmd.o .libs/libipkg_la-ipkg_configure.o .libs/libipkg_la-ipkg_download.o .libs/libipkg_la-ipkg_install.o .libs/libipkg_la-ipkg_upgrade.o .libs/libipkg_la-ipkg_remove.o .libs/libipkg_la-ipkg_conf.o .libs/libipkg_la-ipkg_utils.o .libs/libipkg_la-pkg.o .libs/libipkg_la-pkg_depends.o .libs/libipkg_la-pkg_extract.o .libs/libipkg_la-hash_table.o .libs/libipkg_la-pkg_hash.o .libs/libipkg_la-pkg_parse.o .libs/libipkg_la-pkg_vec.o .libs/libipkg_la-file_util.o .libs/libipkg_la-ipkg_message.o .libs/libipkg_la-md5.o .libs/libipkg_la-sprintf_alloc.o .libs/libipkg_la-str_util.o .libs/libipkg_la-xregex.o .libs/libipkg_la-xsystem.o .libs/libipkg_la-conffile.o .libs/libipkg_la-conffile_list.o .libs/libipkg_la-nv_pair.o .libs/libipkg_la-nv_pair_list.o .libs/libipkg_la-pkg_dest.o .libs/libipkg_la-pkg_dest_list.o .libs/libipkg_la-pkg_src.o .libs/libipkg_la-pkg_src_list.o .libs/libipkg_la-str_list.o .libs/libipkg_la-void_list.o .libs/libipkg.lax/libbb.a/libbb_la-all_read.o .libs/libipkg.lax/libbb.a/libbb_la-ask_confirmation.o .libs/libipkg.lax/libbb.a/libbb_la-concat_path_file.o .libs/libipkg.lax/libbb.a/libbb_la-copy_file.o .libs/libipkg.lax/libbb.a/libbb_la-copy_file_chunk.o .libs/libipkg.lax/libbb.a/libbb_la-error_msg.o .libs/libipkg.lax/libbb.a/libbb_la-error_msg_and_die.o .libs/libipkg.lax/libbb.a/libbb_la-gz_open.o .libs/libipkg.lax/libbb.a/libbb_la-last_char_is.o .libs/libipkg.lax/libbb.a/libbb_la-make_directory.o .libs/libipkg.lax/libbb.a/libbb_la-messages.o .libs/libipkg.lax/libbb.a/libbb_la-mode_string.o .libs/libipkg.lax/libbb.a/libbb_la-parse_mode.o .libs/libipkg.lax/libbb.a/libbb_la-perror_msg.o .libs/libipkg.lax/libbb.a/libbb_la-perror_msg_and_die.o .libs/libipkg.lax/libbb.a/libbb_la-safe_strncpy.o .libs/libipkg.lax/libbb.a/libbb_la-time_string.o .libs/libipkg.lax/libbb.a/libbb_la-unarchive.o .libs/libipkg.lax/libbb.a/libbb_la-unzip.o .libs/libipkg.lax/libbb.a/libbb_la-verror_msg.o .libs/libipkg.lax/libbb.a/libbb_la-vperror_msg.o .libs/libipkg.lax/libbb.a/libbb_la-wfopen.o .libs/libipkg.lax/libbb.a/libbb_la-xfuncs.o .libs/libipkg.lax/libbb.a/libbb_la-xreadlink.o -L/Volumes/OE/moko/build/tmp/staging/i386-darwin/lib -install_name /Volumes/OE/moko/build/tmp/staging/i386-darwin/lib/libipkg.0.dylib -Wl,-compatibility_version -Wl,1 -Wl,-current_version -Wl,1.0
| ld: multiple definitions of symbol _error_list
| .libs/libipkg_la-args.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-libipkg.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-user.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_cmd.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_configure.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_download.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_install.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_upgrade.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_remove.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_conf.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_utils.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_depends.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_extract.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-hash_table.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_hash.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_parse.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_vec.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-file_util.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_message.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-sprintf_alloc.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-str_util.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-xregex.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-xsystem.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-conffile.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-conffile_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-nv_pair.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-nv_pair_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_dest.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_dest_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_src.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_src_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-str_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-void_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg.lax/libbb.a/libbb_la-error_msg.o definition of _error_list in section (__DATA,__common)
| /usr/bin/libtool: internal link edit command failed
| make[3]: *** [libipkg.la] Error 1
| make[2]: *** [all-recursive] Error 1
| make[1]: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed: /Volumes/OE/moko/build/tmp/work/i386-darwin/ipkg-native-0.99.163-r1/temp/log.do_compile.16640
NOTE: package ipkg-native-0.99.163-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package ipkg-native-0.99.163: failed
ERROR: Build of openmoko-devel-image failed
make: *** [openmoko-devel-image] Error 1
</pre>

= Patching qemu-neo1973 =

The main idea is to get patches for gcc-4.x from Q project and apply it to qemu-neo1973 branch. I'm still working on it.

= Building emulator =

TODO

= Building dfu-util =

First install libusb: sudo port install libusb

Get dfu-util: svn co http://svn.openmoko.org/trunk/src/host/dfu-util/

run ./autogen.sh

Then, for some reason, my libusb lib was not detected. I needed to set my paths by hand:

comment out line 18 and 19 in configure ac:

#PKG_CHECK_MODULES(USB, libusb >= 0.1.4,,
# AC_MSG_ERROR([*** Required libusb >= 0.1.4 not installed ***]))

and add libusb libs manually to line 20, so it looks like:

LIBS="$LIBS -L/opt/local/lib -lusb -Wl,-framework -Wl,IOKit -Wl,-framework -Wl,CoreFoundation -Wl,-prebind -I/opt/local/include"

run ./configure

goto src and:

comment out dfu static because this is not supported on Mac:

dfu_util_static_LDFLAGS = #-static

add lib by hand:

DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir) -I/opt/local/include -L/opt/local/lib -lusb -Wl,-framework -Wl,IOKit -Wl,-framework -Wl,CoreFoundation -Wl,-prebind -I/opt/local/include

(I know that this is totaly unpure, dirty hack, yet it works).

Run make in src dir. You should have working binary - I don't know if this works on the real phone because I do not have one yet. Can anyone confirm?

[[Category:Developer software]]
[[Category:Guides]]
[[Category:InProgress]]

Openmoko under QEMU on MacOSX

2007-07-28T21:14:37Z

Cayco:

Warning: this is draft!

I try to put here my notes on setting up OpenMoko environment (Qemu and MokoMakefile) on Mac OS X.

= Introduction =

Some time ago I ask if anyone has ever set up OpenMoko environment on MacOS X. No one has answered that he did but several people were interested. So I deceided to wrote some directions on how to do that.

As for now I was not successful but I am still trying ;)

= Setting up environment =

== Prequisites ==

Install fink and darwinports (both have neccesary packages).

Follow instructions on:
http://www.openembedded.org/wiki/BuildOnOSX
to set up OE environment.

It is neccessary to create new disk image, just as BuildOnOSX says.

If you're compiilng something connected with X11 be sure to install X11devel package from your MacOS X CD1.

You can get mentioned packages using darwinports:

<pre>
sudo port install quilt
sudo port install py-psyco
sudo port install cogito
sudo port install gawk
fink install sed
</pre>

Then get Q[kju] project: http://www.kju-app.org/proj/wiki/CompilingQ into /Volumes/OE/Q but do not compile it yet (run only "prepare the sources"). This will be needed for compiling Neo1973 emulator.

Set up environment as described in MokoMakefile:

<pre>
cd /Volumes/OE
mkdir moko; cd moko
wget http://www.rwhitby.net/files/openmoko/Makefile

make setup
</pre>

= Making developers image =

<pre>
make openmoko-devel-image
</pre>

I had problems with bitbake - it does not run correctly with psyco (I got "Illegal instruction error" and make exited with error 132) so I had to disable it: I run bitbake -d openmoko-devel-image in MokoMakefile.

Also, I ended up with:

<pre>
ERROR: Error in executing: /Volumes/OE/moko/openembedded/packages/quilt/quilt-native_0.45.bb
ERROR: Exception:exceptions.UnboundLocalError Message:local variable 'md5data' referenced before assignment
</pre>

I found out that I did not have md5sum which is used by bitbake. I found it in testutils packages from fink. Installing it did not help... I got pissed and temporarily changed

vim /Volumes/OE/moko/bitbake/lib/bb/fetch/wget.py +114

so it look like this

<pre>
# supposedly complete.. write out md5sum
md5data = ""
if bb.which(data.getVar('PATH', d), 'md5sum'):
try:
md5pipe = os.popen('md5sum ' + dl)
md5data = (md5pipe.readline().split() or [ "" ])[0]
md5pipe.close()
except OSError:
md5data = ""

# verify the md5sum
#if not verify_md5sum(wanted_md5sum, md5data):
# raise MD5SumError(uri)
</pre>

As you can see there I disabled md5sum verification.

If you have error like this

<pre>

| checking for sed... /usr/bin/sed
| checking whether /usr/bin/sed understands (foo|bar)... no
| configure: error:
| Sorry, you have a version of sed which doesn't understand constructs
| of the form (foo|bar). quilt needs it. If you have access to
| a version of sed which does understand such constructs, you can supply
| its path with the '--with-sed=' option.
</pre>

Install GNU sed from fink.

Now you should have:

<pre>
| libbb.h:53:22: error: features.h: No such file or directory
</pre>

while compiling ipkg. Run following patches in folder:

<pre>
cd /Volumes/OE/moko/build/tmp/work/i386-darwin/ipkg-native-0.99.163-r1/ipkg-0.99.163/
</pre>

apply this patch

<pre>
perl -pi -e 's,struct errlist\*,extern struct errlist\*,g' ipkg.h.in
perl -pi -e 's,#include "libbb.h",#include "libbb.h"\nstruct errlist\* error_list;,g' libbb/error_msg.c

### fix endian.h include in md5.c
perl -pi -e 's,#include \<endian.h\>,#ifndef __APPLE__\n# include \<endian.h\>\n#else\n# include \<machine/endian.h\>\n#endif,g' md5.c

### fix vfs.h include in ipkg_utils.c
perl -pi -e 's,#include \<sys/vfs.h\>,#ifndef __APPLE__\n# include \<sys/vfs.h\>\n#else\n# include \<sys/mount.h\>\n#endif,g' ipkg_utils.c

### remove un-needed features.h include from libbb/libbb.h
perl -pi -e 's,#include \<features.h\>,#ifndef __APPLE__\n# include \<features.h\>\n#endif,g' libbb/libbb.h

### dirname already defined OS X
perl -pi -e 's,char \*dirname $char \*path$;,#ifndef __APPLE__\nchar \*dirname $char \*path$;\n#endif,g' libbb/libbb.h

### Use fink dir for etc
perl -pi -e 's,/etc,%p/etc,g' args.h

### Add define for strndup
perl -pi -e "s,#include \"xsystem.h\",#include \"xsystem.h\"\n\n#ifndef HAVE_STRNDUP\nstatic void\*\nstrndup $const char \*src\, size_t n$\n\{\n size_t i;\n char \*dst;\n\n if $src == NULL$\n return NULL;\n\n dst = $char*$ malloc $n + 1$;\n if $dst != NULL$ \{\n for $i = 0; i \< n \&\& src\[i\]; i++$\n dst\[i\] = src\[i\];\n dst\[i\] = '\\\0';\n \}\n\n return dst;\n\}\n#endif,g" ipkg_conf.c
</pre>

Now I get:

<pre>

| Extracting /Volumes/OE/moko/build/tmp/work/i386-darwin/ipkg-native-0.99.163-r1/ipkg-0.99.163/libbb/.libs/libbb.a
| gcc -dynamiclib ${wl}-flat_namespace ${wl}-undefined ${wl}suppress -o .libs/libipkg.0.0.0.dylib .libs/libipkg_la-args.o .libs/libipkg_la-libipkg.o .libs/libipkg_la-user.o .libs/libipkg_la-ipkg_cmd.o .libs/libipkg_la-ipkg_configure.o .libs/libipkg_la-ipkg_download.o .libs/libipkg_la-ipkg_install.o .libs/libipkg_la-ipkg_upgrade.o .libs/libipkg_la-ipkg_remove.o .libs/libipkg_la-ipkg_conf.o .libs/libipkg_la-ipkg_utils.o .libs/libipkg_la-pkg.o .libs/libipkg_la-pkg_depends.o .libs/libipkg_la-pkg_extract.o .libs/libipkg_la-hash_table.o .libs/libipkg_la-pkg_hash.o .libs/libipkg_la-pkg_parse.o .libs/libipkg_la-pkg_vec.o .libs/libipkg_la-file_util.o .libs/libipkg_la-ipkg_message.o .libs/libipkg_la-md5.o .libs/libipkg_la-sprintf_alloc.o .libs/libipkg_la-str_util.o .libs/libipkg_la-xregex.o .libs/libipkg_la-xsystem.o .libs/libipkg_la-conffile.o .libs/libipkg_la-conffile_list.o .libs/libipkg_la-nv_pair.o .libs/libipkg_la-nv_pair_list.o .libs/libipkg_la-pkg_dest.o .libs/libipkg_la-pkg_dest_list.o .libs/libipkg_la-pkg_src.o .libs/libipkg_la-pkg_src_list.o .libs/libipkg_la-str_list.o .libs/libipkg_la-void_list.o .libs/libipkg.lax/libbb.a/libbb_la-all_read.o .libs/libipkg.lax/libbb.a/libbb_la-ask_confirmation.o .libs/libipkg.lax/libbb.a/libbb_la-concat_path_file.o .libs/libipkg.lax/libbb.a/libbb_la-copy_file.o .libs/libipkg.lax/libbb.a/libbb_la-copy_file_chunk.o .libs/libipkg.lax/libbb.a/libbb_la-error_msg.o .libs/libipkg.lax/libbb.a/libbb_la-error_msg_and_die.o .libs/libipkg.lax/libbb.a/libbb_la-gz_open.o .libs/libipkg.lax/libbb.a/libbb_la-last_char_is.o .libs/libipkg.lax/libbb.a/libbb_la-make_directory.o .libs/libipkg.lax/libbb.a/libbb_la-messages.o .libs/libipkg.lax/libbb.a/libbb_la-mode_string.o .libs/libipkg.lax/libbb.a/libbb_la-parse_mode.o .libs/libipkg.lax/libbb.a/libbb_la-perror_msg.o .libs/libipkg.lax/libbb.a/libbb_la-perror_msg_and_die.o .libs/libipkg.lax/libbb.a/libbb_la-safe_strncpy.o .libs/libipkg.lax/libbb.a/libbb_la-time_string.o .libs/libipkg.lax/libbb.a/libbb_la-unarchive.o .libs/libipkg.lax/libbb.a/libbb_la-unzip.o .libs/libipkg.lax/libbb.a/libbb_la-verror_msg.o .libs/libipkg.lax/libbb.a/libbb_la-vperror_msg.o .libs/libipkg.lax/libbb.a/libbb_la-wfopen.o .libs/libipkg.lax/libbb.a/libbb_la-xfuncs.o .libs/libipkg.lax/libbb.a/libbb_la-xreadlink.o -L/Volumes/OE/moko/build/tmp/staging/i386-darwin/lib -install_name /Volumes/OE/moko/build/tmp/staging/i386-darwin/lib/libipkg.0.dylib -Wl,-compatibility_version -Wl,1 -Wl,-current_version -Wl,1.0
| ld: multiple definitions of symbol _error_list
| .libs/libipkg_la-args.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-libipkg.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-user.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_cmd.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_configure.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_download.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_install.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_upgrade.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_remove.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_conf.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_utils.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_depends.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_extract.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-hash_table.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_hash.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_parse.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_vec.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-file_util.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-ipkg_message.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-sprintf_alloc.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-str_util.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-xregex.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-xsystem.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-conffile.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-conffile_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-nv_pair.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-nv_pair_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_dest.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_dest_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_src.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-pkg_src_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-str_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg_la-void_list.o definition of _error_list in section (__DATA,__common)
| .libs/libipkg.lax/libbb.a/libbb_la-error_msg.o definition of _error_list in section (__DATA,__common)
| /usr/bin/libtool: internal link edit command failed
| make[3]: *** [libipkg.la] Error 1
| make[2]: *** [all-recursive] Error 1
| make[1]: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed: /Volumes/OE/moko/build/tmp/work/i386-darwin/ipkg-native-0.99.163-r1/temp/log.do_compile.16640
NOTE: package ipkg-native-0.99.163-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package ipkg-native-0.99.163: failed
ERROR: Build of openmoko-devel-image failed
make: *** [openmoko-devel-image] Error 1
</pre>

= Patching qemu-neo1973 =

The main idea is to get patches for gcc-4.x from Q project and apply it to qemu-neo1973 branch. I'm still working on it.

= Building emulator =

TODO

= Building dfu-util =

First install libusb: sudo port install libusb

Get dfu-util: svn co http://svn.openmoko.org/trunk/src/host/dfu-util/

run ./autogen.sh

Then, for some reason, my libusb lib was not detected. I needed to set my paths by hand:

comment out line 18 and 19 in configure ac:

#PKG_CHECK_MODULES(USB, libusb >= 0.1.4,,
# AC_MSG_ERROR([*** Required libusb >= 0.1.4 not installed ***]))

and add libusb libs manually to line 20, so it looks like:

LIBS="$LIBS -L/opt/local/lib -lusb -Wl,-framework -Wl,IOKit -Wl,-framework -Wl,CoreFoundation -Wl,-prebind -I/opt/local/include"

run ./configure

goto src and:

comment out dfu static because this is not supported on Mac:

dfu_util_static_LDFLAGS = #-static

add lib by hand:

DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir) -I/opt/local/include -L/opt/local/lib -lusb -Wl,-framework -Wl,IOKit -Wl,-framework -Wl,CoreFoundation -Wl,-prebind -I/opt/local/include

(I know that this is totaly unpure, dirty hack, yet it works).

Run make in src dir. You should have library - I don't know if this works because I do not have phone yet. Can anyone confirm?

[[Category:Developer software]]
[[Category:Guides]]
[[Category:InProgress]]

External Feeds

2007-07-22T19:33:35Z

Cayco:

There are a number of blogs written by people in the [[OpenMoko]] community that are not part of the official feed, however can be accessed individually with the URLs below:

{| border="1"
! Blog Name !! Author !! Description !! Feed
|-
|devzero.net || [[User:Jgm|Jim McDonald]] || Application development (focused on messaging) || http://beta.blogger.com/feeds/6353086131724697255/posts/summary/-/openmoko
|-
|unethicalblogger.com || R. Tyler Ballance || Porting Mono to OpenMoko || http://unethicalblogger.com/blog_categories/openmoko/feed
|-
|openmoko.org.pl || [[User:Cayco|Krzysztof Kajkowski]] || First polish OpenMoko site (mostly blogs) || http://www.openmoko.org.pl/rss.xml
|-
|}

[[Category:Information]]

External Feeds

2007-07-22T19:31:55Z

Cayco:

There are a number of blogs written by people in the [[OpenMoko]] community that are not part of the official feed, however can be accessed individually with the URLs below:

{| border="1"
! Blog Name !! Author !! Description !! Feed
|-
|devzero.net || [[User:Jgm|Jim McDonald]] || Application development (focused on messaging) || http://beta.blogger.com/feeds/6353086131724697255/posts/summary/-/openmoko
|-
|unethicalblogger.com || R. Tyler Ballance || Porting Mono to OpenMoko || http://unethicalblogger.com/blog_categories/openmoko/feed
|-
openmoko.org.pl || Krzysztof Kajkowski || First polish OpenMoko site (mostly blogs) || http://www.openmoko.org.pl/rss.xml
|-
|}

[[Category:Information]]

Openmoko under QEMU on MacOSX

2007-07-21T10:37:51Z

Cayco:

Openmoko Local Groups: Warsaw

2007-07-13T16:43:03Z

Cayco:

Witajcie na warszawskiej stronie projektu OpenMoko!

{|border=1
!Imię i nazwisko
!Umiejętności
!stopień zainteresowania
!Inne
|-
| Krzysztof Kajkowski
|Administracja Linux/Unix, Python, C/C++, Java, bash i parę innych; ostatnio grzebię w MacOS X
|Jestem na liście już od dawna, Neo1973 kupiłem pierwszego dnia
|A widziałeś już http://www.openmoko.org.pl ?
|}

Zobacz [[Talk:OpenMoko_Local_Groups:_Warsaw|rozmowy]]

Talk:Openmoko Local Groups: Warsaw

2007-07-13T16:42:38Z

Cayco:

Czy ktoś tu jeszcze oprócz mnie jest?

Openmoko Local Groups: Warsaw

2007-07-13T16:42:31Z

Cayco:

Witajcie na warszawskiej stronie projektu OpenMoko!

{|border=1
!Imię i nazwisko
!Umiejętności
!stopień zainteresowania
!Inne
|-
| Krzysztof Kajkowski
|Administracja Linux/Unix, Python, C/C++, Java, bash i parę innych; ostatnio grzebię w MacOS X
|Jestem na liście już od dawna, Neo1973 kupiłem pierwszego dnia
|A widziałeś już http://www.openmoko.org.pl ?
|}

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

Openmoko Local Groups

2007-07-13T16:36:30Z

Cayco:

__TOC__
'''OpenMoko Local Groups...'''

* can be used for developers to meet and get to know each other
* can be used for developing
* may provide the room for real-life discussions away from mailinglists/wiki
* can support early support handling their GTA01Bv4 and exchange experiences
* fasten the community's cohesion
* give motivation

==EU==
===UK===
==== [[OpenMoko_Local_Groups: Birmingham|Birmingham]] ====

=== Germany ===
==== [[OpenMoko_Local_Groups: Berlin|Berlin]] ====

=== Poland ===
==== [[OpenMoko_Local_Groups: Warsaw|Warsaw]] ====

==USA==
===Oregon===
==== [[OpenMoko_Local_Groups: Eugene|Eugene]] ====
[[Category:Community]]
[[Category:Neo1973 Phase 1 related]]
===California===
==== [[OpenMoko_Local_Groups: San Francisco|San Francisco]] ====
[[Category:Community]]
[[Category:Neo1973 Phase 1 related]]

Openmoko under QEMU on MacOSX

2007-07-12T12:20:38Z

Cayco:

Openmoko under QEMU on MacOSX

2007-07-12T07:43:29Z

Cayco:

Openmoko under QEMU on MacOSX

2007-07-12T06:43:19Z

Cayco:

Openmoko under QEMU on MacOSX

2007-07-11T17:41:22Z

Cayco:

Openmoko under QEMU on MacOSX

2007-07-11T07:52:31Z

Cayco:

Warning: this is draft!

I try to put here my notes on setting up OpenMoko environment (Qemu and MokoMakefile) on Mac OS X.

Here goes my mail to openmoko mailing list in which I described common problem while compiling qemu on Mac:

<pre>
There was some discussion on the lists some time ago and I wanted to
check if anything has changed.

I've made some quick research on subject of developing OpenMoko apps
on MacOS X. It appears that we could run MakoMakefile:

http://www.quantum-step.com/download/OpenMoko-Edition/oe

That's great!

I checked if there is any possibility to run QEMU's Neo1973 port on
Mac but it seems not possible right now. Compiling it as written on
http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU does not work
because it requires gcc-3.3 which seems to be broken on MacOS -
http://lists.macosforge.org/pipermail/macports-users/2007-February/001593.html

Compiling ends up with error: gcc-3.3: installation problem, cannot
exec `cc1': No such file or directory

Compiling neo1973 qemu with gcc-4.0: ./configure
--target-list=arm-softmmu --cc=/usr/bin/gcc-4.0 --disable-gcc-check

gives you:
dyngen.c: In function 'gen_code':
dyngen.c:1853: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1854: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1858: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1872: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1915:2: error: #error unsupport object format
dyngen.c:1849: warning: unused variable 'type'
make: *** [dyngen] Error 1

But there is project: http://www.kju-app.org/kju/ that manages to
compile and run (very well) qemu under MacOS X. They are using
standart XCode Developer Tools so this could mean gcc-4.0.

I would be great if someone with grater knowledge on the subject could
combine kju and neo1973 emulators to make such emulator possible. What
do you think?

</pre>

== Experiments ==

Here you may find my experiments while I was trying trying to run openmoko emulator on my Mac.

=== Prequisites ===
I followed instructions in:
http://www.openembedded.org/wiki/BuildOnOSX

Get Q[kju]: http://www.kju-app.org/proj/wiki/CompilingQ into /Volumes/OE/Q but do not compile it yet (run only "prepare the sources")

Set up environment as described in MokoMakefile:

<pre>

sudo port install quilt
sudo port install py-psyco

cd /Volumes/OE
mkdir moko; cd moko
wget http://www.rwhitby.net/files/openmoko/Makefile

make setup

</pre>

=== Patching qemu-neo1973 ===

The main idea is to get patches for gcc-4.x from Q project and apply it to qemu-neo1973 branch. I'm still working on it.

=== Building emulator ===

TODO

=== Building environment ===

<pre>
make openmoko-devel-image
</pre>

Openmoko under QEMU on MacOSX

2007-07-11T07:29:02Z

Cayco:

Warning: this is draft!

I try to put here my notes on setting up OpenMoko environment (Qemu and MokoMakefile) on Mac OS X.

Here goes my mail to openmoko mailing list in which I described common problem while compiling qemu on Mac:

<pre>
There was some discussion on the lists some time ago and I wanted to
check if anything has changed.

I've made some quick research on subject of developing OpenMoko apps
on MacOS X. It appears that we could run MakoMakefile:

http://www.quantum-step.com/download/OpenMoko-Edition/oe

That's great!

I checked if there is any possibility to run QEMU's Neo1973 port on
Mac but it seems not possible right now. Compiling it as written on
http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU does not work
because it requires gcc-3.3 which seems to be broken on MacOS -
http://lists.macosforge.org/pipermail/macports-users/2007-February/001593.html

Compiling ends up with error: gcc-3.3: installation problem, cannot
exec `cc1': No such file or directory

Compiling neo1973 qemu with gcc-4.0: ./configure
--target-list=arm-softmmu --cc=/usr/bin/gcc-4.0 --disable-gcc-check

gives you:
dyngen.c: In function 'gen_code':
dyngen.c:1853: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1854: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1858: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1872: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1915:2: error: #error unsupport object format
dyngen.c:1849: warning: unused variable 'type'
make: *** [dyngen] Error 1

But there is project: http://www.kju-app.org/kju/ that manages to
compile and run (very well) qemu under MacOS X. They are using
standart XCode Developer Tools so this could mean gcc-4.0.

I would be great if someone with grater knowledge on the subject could
combine kju and neo1973 emulators to make such emulator possible. What
do you think?

</pre>

== Experiments ==

Here you may find my experiments while I was trying trying to run openmoko emulator on my Mac.

=== Prequisites ===
I followed instructions in:
http://www.openembedded.org/wiki/BuildOnOSX

Get Q[kju]: http://www.kju-app.org/proj/wiki/CompilingQ into /Volumes/OE/Q but do not compile it yet (run only "prepare the sources")

Set up environment as described in MokoMakefile:

<pre>

sudo port install quilt

cd /Volumes/OE
mkdir moko; cd moko
wget http://www.rwhitby.net/files/openmoko/Makefile

make setup

</pre>

=== Patching qemu-neo1973 ===

The main idea is to get patches for gcc-4.x from Q project and apply it to qemu-neo1973 branch. I'm still working on it.

=== Building emulator ===

TODO

=== Building environment ===

<pre>
make openmoko-devel-image
</pre>

Openmoko under QEMU on MacOSX

2007-07-10T18:07:15Z

Cayco:

Warning: this is draft!

I try to put here my notes on setting up OpenMoko environment (Qemu and MokoMakefile) on Mac OS X.

Here goes my mail to openmoko mailing list in which I described common problem while compiling qemu on Mac:

<pre>
There was some discussion on the lists some time ago and I wanted to
check if anything has changed.

I've made some quick research on subject of developing OpenMoko apps
on MacOS X. It appears that we could run MakoMakefile:

http://www.quantum-step.com/download/OpenMoko-Edition/oe

That's great!

I checked if there is any possibility to run QEMU's Neo1973 port on
Mac but it seems not possible right now. Compiling it as written on
http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU does not work
because it requires gcc-3.3 which seems to be broken on MacOS -
http://lists.macosforge.org/pipermail/macports-users/2007-February/001593.html

Compiling ends up with error: gcc-3.3: installation problem, cannot
exec `cc1': No such file or directory

Compiling neo1973 qemu with gcc-4.0: ./configure
--target-list=arm-softmmu --cc=/usr/bin/gcc-4.0 --disable-gcc-check

gives you:
dyngen.c: In function 'gen_code':
dyngen.c:1853: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1854: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1858: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1872: error: 'struct relocation_info' has no member named 'r_offset'
dyngen.c:1915:2: error: #error unsupport object format
dyngen.c:1849: warning: unused variable 'type'
make: *** [dyngen] Error 1

But there is project: http://www.kju-app.org/kju/ that manages to
compile and run (very well) qemu under MacOS X. They are using
standart XCode Developer Tools so this could mean gcc-4.0.

I would be great if someone with grater knowledge on the subject could
combine kju and neo1973 emulators to make such emulator possible. What
do you think?

</pre>

== Experiments ==

Here you may find my experiments while I was trying trying to run openmoko emulator on my Mac.

=== Prequisites ===
I followed instructions in:
http://www.openembedded.org/wiki/BuildOnOSX

Get Q[kju]: http://www.kju-app.org/proj/wiki/CompilingQ into /Volumes/OE/Q but do not compile it yet (run only "prepare the sources")

Set up environment as described in MokoMakefile:

<pre>
cd /Volumes/OE
mkdir moko; cd moko
wget http://www.rwhitby.net/files/openmoko/Makefile

make setup

</pre>

=== Patching qemu-neo1973 ===

The main idea is to get patches for gcc-4.x from Q project and apply it to qemu-neo1973 branch. I'm still working on it.

=== Building emulator ===

TODO

=== Building environment ===

TODO

Press Coverage

2007-05-29T11:39:30Z

Cayco: added link for polish article

{|align=right
|__TOC__
|}
[http://www.google.com/trends?q=openmoko%2Cneo1973&ctab=1&geo=all&date=all OpenMoko and Neo1973 on google trends.]

This site contains the press coverage about OpenMoko and the Neo 1973 sorted by language and date. Newest on top.

== Languages ==

=== English ===
==== May 2007 ====
* [http://blogs.sun.com/brewin/entry/fic_and_openmoko_thank_you blog.SUN.com] FIC and OpenMoko - Thank You
* [http://www.pikesoft.com/blog/index.php?itemid=174 PikeSoft.com] JavaFX Mobile: a new smartphone OS contender
* [http://www.sfgate.com/cgi-bin/blogs/sfgate/detail?blogid=19&entry_id=16310 SFGate.com] Here comes the Sun Conference
* [http://www.linuxdevices.com/news/NS7539760574.html LinuxDevices.com] Sun beams Linux/Java at mobile phon

==== April 2007 ====
* [http://www.palminfocenter.com/news/9371/openmoko-running-on-a-palm-tx/ Palm Infocenter] OpenMoko running on a palm TX
* [http://jaidev.info/home/blog/archives/2007/04/13/openmoko.html JaidevInfo] OpenMoko
* [http://www.wirelessweek.com/newsletter.aspx?id=137388 Wirelessweek.com] Democracy Hits the Mobile Phone
* [http://elearner.edublogs.org/2007/04/11/technologies-is-that-a-word/ Edublogs.org] Technologies is that a word?
* [http://www.linuxdevices.com/news/NS4777580627.html Linuxdevices.com] 200 million Linux phones to ship by 2012
* [http://arstechnica.com/news.ars/post/20070415-palm-embracing-linux-in-the-hopes-of-being-relevant-again.html Ars Technica] Palm embracing Linux in the hopes of being relevant again] (Mentions Neo1973 in passing)

==== March 2007 ====
* [http://www.smartdevicecentral.com/article/OpenMokos+Open+Source+Phone/202546_1.aspx smartdevicecentral.com] OpenMoko's open source phone
* [http://www.zdnetasia.com/news/communications/0,39044192,61996003,00.htm zdnet asia] Passing mention in an article on the Iphone.
* [http://www.wikio.com/news/Sean+Moss-Pultz wikio.com] Sean Moss-Pultz News
* [http://www.edparsons.com/?p=438 edparsons.com] iPhone chipping away at the walls
* [http://blogs.pcworld.co.nz/pcworld/techsploder/2007/03/openmoko_makes_total_sense.html blogs.pcworld.co.nz] OpenMoko makes total sense
* [http://www.totalueberwachung.de/blog/articles/2007/03/08/neo1973-arrived totalueberwachung.de] Neo1973 arrived
* [http://www.makuchaku.info/blog/im-gonna-get-this-one makuchaku.info] I'm gonna get this one
* [http://www.kitenet.net/~joey/blog/entry/openmoko_and_n800.html kitenet.net] OpenMoko and n800
* [http://dominion.kabel.utwente.nl/koen/cms/the-neo1973-unboxed dominion.kabel.utwente.nl] The Neo1973 unboxed
* [http://atulchitnis.net/diary/showentry/421 atulchitnis.net] An OpenMoko Phone arrives
* [http://blog.matthewgast.com/2007/03/03/good-luck-openmoko blog.matthewgast.com] Good luck OpenMoko
* [http://vaandoo.blogspot.com/2007/03/openmoko-neo1973-opensource-software.html vaandoo.blogspot.com] OpenMoko Neo1973 opensource software
* [http://www.linuxdevices.com/news/NS7653749655.html linuxdevices.com] OpenMoko update; Neo1973 on sale in March
* [http://www.ministryoftech.com/2007/03/05/the-5-hottest-phones-for-linux-fanatics/ ministryoftech.com] Brief line-up of the 5 hottest phones for Linux fans
* [http://voxilla.com/soapvox/2007/03/01/industry-disruption-really-168 voxilla.com] Article about ETel Sean Moss-Pultz presentation
* [http://blog.wired.com/gadgets/2007/03/eight_great_lin.html blog.wired.com] Gadget Lab: Eight Great Linux Smartphones
* [http://gigaom.com/2007/03/01/openmoko-phone/ gigaom.com] OpenMoko Open-Source Mobile, coming soon - Interview with Sean Moss-Pultz
* [http://www.oreillynet.com/etel/blog/2007/03/openmoko_1.html www.oreillynet.com] ETel coverage
* [http://gordoncook.net/wp/?p=146 gordoncook.net] Short history of Neo1973 and other stuff
* [http://www.engadget.com/2007/03/03/openmoko-details-pricing-availability-for-neo1973/ engadget.com] OpenMoko details pricing, availability for Neo1973
* [http://www.uberpulse.com/us/2007/03/fic_wants_to_rewrite_the_rules_with_open_moko_mobile_phone.php www.uberpulse.com] Some images from ETel

==== February 2007 ====
* [http://www.scullen.ca/2007/02/15/forget-about-the-iphone-neo1973-is-far-more-exciting/ scullen.ca] Forget about the iPone, Neo1973 is far more exciting
* [http://www.mobileread.com/forums/showpost.php?p=59124&postcount=4 mobileread.com] Show post
* [http://www.pdasnews.com/articles/2568/1/ pdasnews.com] Linux-powered iPhone killer available online in March
* [http://www.belutz.net/2007/02/05/openmoko/ belutz.net] OpenMoko
* [http://www.mail-archive.com/community@lists.openmoko.org/msg03686.html mail-archive.com] OpenMoko community mail archive
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena maclife.com] Is there a crowd in the touch screen phone arena
* [http://gopaultech.com/2007/02/fic-neo1973-linux-smartphone/ gopaultech.com] FIC Neo1973 Linux smartphone
* [http://www.volweb.cz/horvitz/os-info/news-feb07-014.html volweb.cz] Open-source smartphone, with WiFi in version 2
* [http://www.oreillynet.com/etel/blog/2007/02/etel_coverage_openmoko_opens_t.html oreillynet.com] ETel coverage OpenMoko opens
* [http://www.mobilewhack.com/openmoko-neo1973-open-source-phone/ mobilewhack.com] OpenMoko Neo1973 open source phone
* [http://www.engadget.com/2007/02/19/what-tech-would-the-presidents-rock-in-2007/ engadget.com] What tech would the presidents rock in 2007
* [http://www.tuxmachines.org/node/13602 tuxmachines.org] What participation culture
* [http://www.vanille-media.de/site/index.php/category/opensource/openmoko/ vanille-media.de] Opensource OpenMoko
* [http://www.joetech.com/2007/02/15/openmoko-open-source-cell-phone/ joetech.com] OpenMoko open source cell phone
* [http://www.makezine.com/blog/archive/2007/02/openmoko_open_s.html makezine.com] OpenMoko open
* [http://www.linuxdevices.com/news/NS9706477996.html linuxdevices.com] Announce of the Openembedded booth at FOSDEM in Brussels.
* [http://www.linuxdevices.com/news/NS2657814070.html linuxdevices.com] Quick interview with Sean and some pictures
* [http://gizmodo.com/gadgets/smartphones/first-look-the-antiiphone-openmokos-neo1973-236841.php gizmodo.com] Photos and comments on hardware and software
* [http://www.onecompare.com/mobile-news/article-asp~aid~244~pub~56321102~story~openmoko-launch-the-official-portal-for-development-of-the-openmoko-platform onecompare.com] Short news article
* [http://crunchgear.com/2007/02/15/openmokos-open-source-mobile-os crunchgear.com] Holding the phone upside down
* [http://www.slashgear.com/openmoko-and-fic-neo1973-updates-153926.php slashgear.com] Video interview and many pictures
* [http://www.djlosch.com/article_Comparison%3A_iPhone_vs_A1200_vs_Neo1973 djlosch.com] Article comparing the Neo to the iPhone and A1200
* [http://popsci.typepad.com/popsci/2007/02/up_close_and_pe.html popsci.typepad.com] Screenshot of Linux booting on the Neo
* [http://video.google.de/videoplay?docid=-3742589179435830945&q=Openmoko video.google.com] Presentation of OpenMoko at the FOSDEM
* [http://www.manilastandardtoday.com/?page=business6_feb27_2007 manilastandardtoday.com] Tale of two phones
* [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone blog.printf.net] OLPC and older Neo1973.
* [http://mako.cc/copyrighteous/freesoftware/20070228-00.html mako.cc] OLPC and older Neo1973 again.
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena MacLife] Is Three a Crowd among Touch-Screen Phones?

==== January 2007 ====
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html blogs.ft.com] OpenMoko harks back to hello moto
* [http://opensource.sfsu.edu/node/258 opensource.sfsu.edu] Can you hear me now?
* [http://losca.blogspot.com/2007/01/maemo-nokia-n800-has-competitor-in.html losca.blogspot.com] Maemo Nokia n800 has competitor in openness - OpenMoko
* [http://21talks.net/voip/openmoko 21talks.net] OpenMoko: Not as sexy as the iPhone, but it’s a Linux phone
* [http://www.linuxinfusion.com/openmoko-schedule-announced linuxinfusion.com] OpenMoko schedule announced
* [http://users.livejournal.com/_paladine_/tag/smartphone users.livjournal.com] The Worlds First Opensource Linux Smartphone
* [http://www.nungee.com/2007/01/25/openmoko/ nungee.com] OpenMoko
* [http://www.sda-asia.com/sda/features/psecom,id,880,srn,2,channel,developer,nodeid,21,_language,Singapore.html sda-asia.com] OpenMoko Offers Open-source Smart phone T
* [http://www.regdeveloper.co.uk/2007/01/15/open_phone/ regdeveloper.co.uk] Open Phone
* [http://www.product-reviews.net/2007/01/17/fic-neo1973-smartphone-open-source-phone/ product-reviews.net] FIC Neo1973 smartphone open source phone
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php gizmodo.com] OpenMoko smartphone did they have a time machine or what
* [http://www.oreillynet.com/conferences/blog/2007/01/openmoko_workshop_added_to_ete.html oreillynet.com] OpenMoko workshop added to ETel
* [http://www.gadgetell.com/2007/01/openmoko-gets-interviewed-about-new-open-source-fic-neo1973/ gadgetell.com] OpenMoko gets interviewed about new open source FIC Neo1973
* [http://www.slashgear.com/openmoko-interface-im-loving-it-173496.php slashgear.com] OpenMoko interface I'm loving it
* [http://www.gadgetorama.com/news/news_details.php?gorid=2008 gadgetorama.com] OpenMoko news details
* [http://tech.cybernetnews.com/2007/01/17/openmoko-vs-iphone-did-apple-copy/ tech.cybernetnews.com] OpenMoko vs iPhone did Apple copy
* [http://techtrails.blogspot.com/2007/01/open-phones-with-open-moko-while.html techtrails.blogspot.com] Open phones with OpenMoko while
* [http://blogger.xs4all.nl/jurjen1/archive/2007/01/17/174341.aspx bloger.xs4all.nl] OpenMoko open source mobile phone
* [http://www.ringnokia.com/2007/01/i_am_highly_cur.html ringnokia.com] I'm highly curious
* [http://www.oreillynet.com/etel/blog/2007/01/iclone_1.html oreillynet.com] iClone
* [http://forums.scotsnewsletter.com/index.php?showtopic=17685 forums.scotsnewsletter.com] Show topic
* [http://understandinglimited.com/2007/01/15/iphone/ understandinglimited.com] iPhone and OpenMoko
* [http://robertogaloppini.net/2007/01/12/openmoko-the-integrated-os-mobile-communications-platform-2/ robertogaloppini.net] OpenMoko the intergrated OS mobile communications platform
* [http://www.funambol.com/blog/capo/2007/01/apple-please-do-not-forget-developers.html funambol.com] Apple please do not forget developers
* [http://chopey.blogspot.com/2007/01/iphone-or-not-to-iphone.html chopey.blogspot.com] iPhone or not to iPhone
* [http://opendotdotdot.blogspot.com/2007/01/openmoko.html opendotdotdot.blogspot.com] OpenMoko
* [http://www.e-pcmag.gr/forum/index.php?showtopic=19505 e-pcmag.gr] Show topic
* [http://www.costpernews.com/2007/01/12/anything-you-can-do-we-can-do-better/ costpernews.com] Anything you can do we can do better
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs OpenMoko - the Open Alternative
* [http://lwn.net/Articles/217020/rss lwn.net] An OpenMoko update
* [http://www.networkworld.com/news/2007/010907-moss-pultz.html networkworld.com] Q&A Building a new open source phone platform
* [http://www.networkcomputing.com/showArticle.jhtml?articleID=196802226 networkcomputing.com] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.osweekly.com/index.php?option=com_content&task=view&id=2420&Itemid=449 osweekly.com] Mobile Devices Adopt Open Source
* [http://www.linuxdevices.com/news/NS8591201260.html linuxdevices.com] Linux phone market open up?
* [http://www.pcmag.com/article2/0,1895,2080727,00.asp pcmag.com] Cell phone open up
* [http://sonyericssonz558i.blogurple.com/2007/01/06/23/ sonyericssonz558i.blogurple.com] Sony Ericsson Z558i
* [http://www.sannes.org/?p=5 sannes.org] An Open mobile phone that does what you want
* [http://popsci.typepad.com/ces2007/2007/01/opensource_stri.html Popsci.com] Open Source Strikes Again
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php Gizmodo.com] OpenMoko interface compared to iPhone
* [http://www.linuxjournal.com/xstatic/abstracts/upfront Linux Journal] Doc Searls in the feb 2007 issue
* [http://www.osdir.com/Article9642.phtml OSDir.com] Mobile Linux for the Mobile Fan] -> [http://www.madpenguin.org/cms/?m=show&id=7710 MadPenguin] Mobile Linux for the Mobile Fan
* [http://www.usnews.com/usnews/biztech/davesdownload/archive/070112/a_populist_challenge_to_apples.htm US News] A Populist Challenge to Apple's iPhone
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs OpenMoko: The open alternative
* [http://www.informationweek.com/news/showArticle.jhtml?articleID=196802206&subSection=All+Stories InformationWeek] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.theregister.co.uk/2007/01/15/open_phone/ The Register] Open Phones with Open Moko
* [http://techreport.com/onearticle.x/11589 The Tech Report] OpenMoko offers open-source smart phone
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html Financial Times] OpenMoko harks back to Hello Moto
* [http://hardware.slashdot.org/article.pl?sid=07/01/20/1551200 Slashdot] OpenMoko Schedule Announced
* [http://www.youtube.com/watch?v=jRvtAAXTIlg Youtube] Interview with Sean Moss-Pultz ([http://www.monoploid.be/dl/openmoko_sean_interview.ogm mirror in Ogg format])
* [http://www.libervis.com/article/forget_iphone_hail_openmoko_the_true_revolution Libervis.com] Forget iPhone, hail OpenMoko, the true revolution
* [http://gizmodo.com/gadgets/smartphones/sizemodo-iphone-vs-openmoko-neo1073-229294.php Gizmodo]iPhone vs. Openmoko Neo1973] (please, don't mind the typo i n the title)

==== December 2006 ====
* [http://www.pikesoft.com/blog/index.php?itemid=133 pikesoft.com] Cheap, totally open Linux phone will ship next month
* [http://www.cdrinfo.com/Sections/News/Details.aspx?NewsId=19254 cdrinfo.com] FIC to release Linux based Smartphone

==== November 2006 ====
* [http://www.ministryoftech.com/2006/11/09/fic-neo1973-smartphone-with-linux-based-openmoko-open-source-platform/ ministryoftech.com] FIC Neo1973 smartphone with linux-based OpenMoko open source platform
* [http://www.mobiletechnews.com/info/2006/11/09/124614.html mobiletechnews.com] OpenMoko Linux mobile platform and Neo1973 smartphone announced
* [http://news.softpedia.com/news/FIC-Neo1973-for-all-the-Linux-Lovers-out-There-40344.shtml news.softpedia.com] FIC Neo1973 for all the Linux lovers out there
* [http://www.openembedded.org/openmoko-fic-choosing-openembedded openembedded.org] OpenMoko FIC choosing openembedded
* [http://news.com.com/2300-1037_3-6134795-1.html news.com.com] FIC's Linux handset
* [http://www.slashphone.com/77/5784.html slashphone.com] OpenMoko Announces Open Source Mobile Communications Platform
* [http://www.arm.com/iqonline/news/marketnews/15616.html arm.com] Open Linux Based, ARM Powered Mobile In Wings
* [http://news.com.com/Second+open+Linux+handset+unveiled/2100-1039_3-6133974.html news.com.tw] Second open Linux handset unveiled
* [http://www.infoworld.com/article/06/11/08/HNlinuxphone_1.html?COMMERCIAL%20LINUX infoworld.com] FIC debuts open Linux-based smartphone
* [http://www.michaeldolan.com/431 michaeldolan.com] A must have: OpenMoko cell phone with GPS and...apt-get
* [http://nandz.blogspot.com/2006/11/my-dream-phone.html nandz.blogspot.com] My dream phone
* [http://www.linuxdevices.com/news/NS2986976174.html linuxdevices.com] Cheap, hackable Linux smartphone due soon
* [http://www.linuxdevices.com/news/NS7056478804.html linuxdevices.com] First OpenMoKo phone taps dual-licensed SyncML stack
* [http://lwn.net/Articles/208298/ lwn.net] The OpenMoko open phone
* [http://www.theinquirer.net/default.aspx?article=35590 theinquirer.net] A truly open Linux phone with GPS debuts

=== German ===

==== April 2007 ====
* [http://www.pro-linux.de/news/2007/11133.html pro-linux] - OpenMoko produziert erste Muster
* [http://www.golem.de/0704/51970.html golem.de] - Open-Source-Handy vor Produktionsbeginn

==== March 2007 ====
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express] - Das neue Projekt zur Entwicklung eines Telefons mit freier Software
* [http://www.pro-linux.de/news/2007/10966.html pro-linux] - OpenMoko sucht Unterstützung

==== February 2007 ====
* [http://www.digital-living-magazin.de/index.php?pid=17&art=2050&cid=DLnewsletter digital-living-magazin.de] - Linux erobert Mobilfunkmarkt
* [http://www.heise.de/tr/artikel/85138 Technology Review] - Open-Source-Handy, nächster Versuch
* [http://www.pro-linux.de/news/2007/10833.html pro-linux] - OpenMoko-Quellcode angekündigt
* [http://www.heise.de/newsticker/meldung/85354 heise online] - OpenMoko: Linux-Plattform für Handys freigegeben
* [http://www.mobile2day.de/news/news_details.html?nd_ref=6870&n_multi=0&nf_id=0&nt_id=0&f_date_m=01&f_date_y=2007&t_date_m=04&t_date_y=2007&from=archive Mobile2Day] - OpenMoko bringt Details zum Neo1973

==== November 2006 ====

* [http://golem.de/0611/48824.html golem.de] - OpenMoko kündigt Open-Source-Handy an
* [http://www.heise.de/newsticker/meldung/80714 heise online] - Smartphone mit offener Linux-Plattform
* [http://www.pro-linux.de/news/2006/10448.html pro-linux] - Offenes Linux-Smartphone »OpenMoko« für Januar 2007 angekündigt

=== Scandinavian ===
* [http://www.amobil.no/nyhet/mobiltelefoner/openmoko_klart_for_verden/36554 Amobil.no] OpenMoko klart for verden
* [http://www.nyteknik.se/art/48697 NyTeknik] Snart är den öppna Linuxtelefonen här (Swedish) (Translation: this article states free release to selected developers Feb 11, commercial release to developers March 11, and main release to market Sep 11. See also [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html])

=== French ===
* [http://linuxfr.org/2006/11/08/21596.html LinuxFR] OpenMoko : sortie en janvier d'un téléphone-GPS enfin libre!

=== Chinese ===
* [http://people.debian.org.tw/~chihchun/2007/05/25/talk-of-openmoko-is-online/ debian.org.tw] Video of OpenMoko at TOSSUG in Taipei
* [http://people.debian.org.tw/~chihchun/2007/05/17/openmoko-at-tossug/ debian.org.tw] OpenMoko at TOSSUG
* [http://magicdesign.blogspot.com/2007/05/free-your-phoneopenmoko.html MagicDesign] Free your phone OpenMoko
* [http://people.debian.org.tw/~chihchun/2007/04/30/have-fun-with-openmokoneo1973/ Debian.org.tw] Have fun with OpenMoko Neo1973
* [http://orzlab.blogspot.com/ Orzlab] When Java meets OpenMoko
* [http://blog.footoo.org/?p=115 FooToo.org] Install OpenMoko Emulator
* [http://www.jollen.org/blog/2007/01/openmoko_announce.html Jollen.org] OpenMoko Kick-Off
* [http://zh.wikipedia.org/wiki/OpenMoko Wikipedia.org] OpenMoko Chinese Wiki
* [http://tw.myblog.yahoo.com/champ_yen/article?mid=211&prev=212&next=-1 Yahoo.com.tw] Forget about iPhone, Hail OpenMoko
* [http://www.jollen.org/blog/2006/11/mobile_20_openmoko_linux_smart.html Jollen.org] OpenMoko Linux Smartphone
* [http://blog.roodo.com/ystuan/archives/2733869.html Roodo.com] OpenMoko

=== Polish ===

* [http://www.studencka.pl/artykuly.php?AID=770 Gazeta Studencka] Polish article (in biggest free students newspaper) by Krzysztof Kajkowski

User:Cayco

2007-02-20T08:38:46Z

Cayco:

'''Name:''' Krzysztof Kajkowski; '''Location:''' Warsaw, Poland.

Talk to me at my [[User_talk:Cayco|talk page]].

==Summary==
* experienced sys admin - Linux, Unix
* python, perl, ruby, C/C++, Java, bash, SQL - less or more I know them all ;)
* I have same spare time after receiving my MSc

==Academic==
* MSc at Warsaw University of Technology - 2006. My thesis was about codecs comparison in remote CCTV transmissions
* BSc at Warsaw University of Technology - 2004. My thesis: "Seanux. Remote system for video surveillance". I have made my own distro ;)

==OpenMoko==
* I announced myself as the first Polish translator
* I am willing to test software and development tools for some bugs as I have proffessional experience in that matter
* also I would like to do some minor programming
* In spare time I add content to my polish portal: [http://www.openmoko.org.pl openmoko.org.pl]

==Other==
* Please visit my homepage: [http://www.cayco.pl www.cayco.pl]