Openmoko - User contributions [en]

Customizing the Openmoko Distribution

2007-09-14T18:09:36Z

Cbrake: replace PACKAGE_INSTALL with IMAGE_INSTALL

== 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 set up 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 it 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 set up, please get it set up according to [[MokoMakefile]]. However, if you do have the build environment set up 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 of 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 your 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 local/packages/images local/packages/tasks

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

cp build/conf/site.conf local/conf/site.conf

* Edit the local/conf/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. Bitbake only seems to use the first site.conf file it finds. <code>setup-env</code> is created by [[MokoMakefile]] automatically and is located in your <code>${OMDIR}</code> directory.

export BBPATH="${OMDIR}/local:${OMDIR}/build:${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.

=== Creating your own images ===

To create you own images we'll use the base openmoko .bb files and modify them to suit. Where you see ''scaredycat'' replace this with something to identify your own images.

edit local/packages/images/scaredycat-openmoko-devel-image.bb and paste this:

<pre>
require scaredycat-openmoko-image.bb

IMAGE_INSTALL += "task-openmoko-debug"

</pre>

then edit local/packages/images/scaredycat-openmoko-image.bb

<pre>
#------------------------------------------------------
# OpenMoko Image Recipe
#------------------------------------------------------

export IMAGE_BASENAME = "${PN}"
export IMAGE_LINGUAS = ""

export IMAGE_INSTALL = "\
${MACHINE_TASK_PROVIDER} \
task-openmoko-linux \
task-openmoko-net \
task-openmoko-ui \
task-openmoko-base \
task-openmoko-phone \
task-openmoko-games \
task-openmoko-pim \
task-openmoko-scaredycat \
"

inherit image

LICENSE = MIT

ROOTFS_POSTPROCESS_COMMAND += 'date "+%m%d%H%M%Y" >${IMAGE_ROOTFS}/etc/timestamp'

</pre>

edit packages/tasks/task-openmoko-scaredycat.bb - this is where we put the things we want to include in our image, above and beyond the standard image. This example includes '''[http://wiki.openmoko.org/wiki/Scummvm scummvm]''' and '''[http://www.handhelds.org/moin/moin.cgi/kbdd kbdd]'''. If you modify this file, make sure you update the '''PR''' by incrementing the number each time.

<pre>
DESCRIPTION = "OpenMoko: Scaredycat Additions"
SECTION = "openmoko/base"
LICENSE = "original"
PR = "r2"

inherit task

RDEPENDS_task-openmoko-scaredycat = "\
scummvm \
kbdd \
"

</pre>

==== Actually building your image ====

To build you image, which will be located with your other images, do the following:

# cd build ; . ../setup-env ; bitbake scaredycat-openmoko-devel-image

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

Minimo

2007-09-14T13:41:06Z

Cbrake: add note that adding programs to image should be done with custom image rather than DISTRO_EXTRA_RDEPENDS

[[Image:Minimo-slashdot.jpeg|thumb|minimo in QEMU displaying it.slashdot.org]]
[[Image:GTA01-minimo.JPG|thumb|minimo on GTA01 displaying www.heise.de]]

= Installing Minimo web browser =

[http://www.mozilla.org/projects/minimo/develop.html Minimo] is a Mozilla based web browser. It features full [http://en.wikipedia.org/wiki/Ajax_%28programming%29 AJAX] support and other goodies. Currently stock OpenMoko build doesn't include Minimo. Here are instructions on how to run minimo in Xephyr PC environment and how to use other third party packages too.

* [http://bec-systems.com/web/content/view/79/9/ Instructions for including new OpenEmbedded packages to your project]

These instructions should be updated to use a custom image rather than DISTRO_EXTRA_RDEPENDS -- see link above.

== Setup build environment ==

If you have built your OpenMoko using MokoMakefile some of these steps might not be familiar to you.

Assume your OpenMoko root is at ~/workspace/moko

First setup build environment variables:
<pre>
moo@hacker:~/workspace/moko/build$ . ../setup-env
</pre>

Then checkout minimo from OpenEmbedded repository:
<pre>
moo@hacker:~/workspace/moko/build$ bitbake minimo
</pre>

Edit local.conf and add minimo to build dependencies list.

<pre>
MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "minimo"
</pre>

After local.conf has added new packages, one must refresh bitbake tasks.

<pre>
bitbake task-base -crebuild
</pre>

Now, you should be able to rebuild root fs using MokoMakefile.

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

The default OpenMoko distribution lacks ''/etc/resolv.conf'' file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

<pre>
moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf
</pre>

== In chroot'ed environment ==

Following instructions in [[Getting OpenMoko working on host with Xephyr]] to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start OpenMoko session, minimo can run as is.

<pre>
/ $ minimo
</pre>
{{Languages|Minimo}}

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

Minimo

2007-09-14T13:07:13Z

Cbrake: updated howto for adding packages to an openembedded image

[[Image:Minimo-slashdot.jpeg|thumb|minimo in QEMU displaying it.slashdot.org]]
[[Image:GTA01-minimo.JPG|thumb|minimo on GTA01 displaying www.heise.de]]

= Installing Minimo web browser =

[http://www.mozilla.org/projects/minimo/develop.html Minimo] is a Mozilla based web browser. It features full [http://en.wikipedia.org/wiki/Ajax_%28programming%29 AJAX] support and other goodies. Currently stock OpenMoko build doesn't include Minimo. Here are instructions on how to run minimo in Xephyr PC environment and how to use other third party packages too.

* [http://bec-systems.com/web/content/view/79/9/ Instructions for including new OpenEmbedded packages to your project]

== Setup build environment ==

If you have built your OpenMoko using MokoMakefile some of these steps might not be familiar to you.

Assume your OpenMoko root is at ~/workspace/moko

First setup build environment variables:
<pre>
moo@hacker:~/workspace/moko/build$ . ../setup-env
</pre>

Then checkout minimo from OpenEmbedded repository:
<pre>
moo@hacker:~/workspace/moko/build$ bitbake minimo
</pre>

Edit local.conf and add minimo to build dependencies list.

<pre>
MACHINE = "qemux86"
DISTRO = "openmoko"
BUILD_ARCH = "i686"
INHERIT += " devshell"
SRCDATE_eds-dbus = "now"
DISTRO_EXTRA_RDEPENDS = "minimo"
</pre>

After local.conf has added new packages, one must refresh bitbake tasks.

<pre>
bitbake task-base -crebuild
</pre>

Now, you should be able to rebuild root fs using MokoMakefile.

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

The default OpenMoko distribution lacks ''/etc/resolv.conf'' file which is used to configure system DNS look-up. Without this file, failing domain name look-up prevents web browsing. The easiest way to fix is to copy the host system resolv.conf to the rootfs.

<pre>
moo@hacker:~/workspace/moko$ cp /etc/resolv.conf rootfs/etc/resolv.conf
</pre>

== In chroot'ed environment ==

Following instructions in [[Getting OpenMoko working on host with Xephyr]] to get yourself chroot'ed into OpenMoko environment.

Start Xephyr. You don't need to start OpenMoko session, minimo can run as is.

<pre>
/ $ minimo
</pre>
{{Languages|Minimo}}

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

Openmoko Local Groups: Cleveland

2007-08-31T10:26:08Z

Cbrake: clean up table

Are there any other OpenMoko community members located in North East Ohio (Akron, Canton, Cleveland)?

{|border=1
!Name
!Skills
!Interest
!Location
!Has Device
!Has Debug Board
|-
|[[User:cbrake]]
|Programming, Embedded Systems dev
|Embedded Sys dev, using the NEO as a phone
|Akron, OH
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:davioh]]
|Programming,
|runing business applications, using the NEO as a phone
|Akron, OH
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-

[[Category:Community]]

Openmoko Local Groups: Cleveland

2007-08-23T17:11:53Z

Cbrake: update cleveland group with table

Are there any other OpenMoko community members located in North East Ohio (Akron, Canton, Cleveland)?
* [[User:cbrake]]

{|border=1
!Name
!Skills
!Interest
!Location
!Has Device
!Has Debug Board
|-
|[[User:cbrake]]
|Programming, Embedded Systems dev
|Embedded Sys dev, using the NEO as a phone
|Akron, OH
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-

[[Category:Community]]

Openmoko Local Groups: Cleveland

2007-08-04T18:41:18Z

Cbrake:

Are there any other OpenMoko community members located in North East Ohio (Akron, Canton, Cleveland)?
* [[User:cbrake]]

[[Category:Community]]

Openmoko Local Groups: Cleveland

2007-08-04T18:40:55Z

Cbrake: cbrake is located in Cleveland area

Are there any other OpenMoko community members located in North East Ohio (Akron, Canton, Cleveland)?
* [[User:cbrake]]

[[Category:Community]]

Neo 1973 OpenOCD

2007-04-11T13:31:39Z

Cbrake: restore last good version of this page and discard bogus GPS data

== About OpenOCD ==

[http://openocd.berlios.de/ OpenOCD] is a 100% free software On-chip-debugger for commonly-found ARM JTAG probes such as [[wiggler]], chamaeleon, jtag-key and others.

It provides a human-readable telnet interface for manually halting/resuming the target device, reading/writing registers and memory, etc.

In addition, it provides a RDI (remote debugger interface) on a TCP port. This interface can be used by gdb (the GNU Debugger).

The GTA01 development team uses OpenOCD with a [[wiggler]] compatible probe as their ICE solution.

== Getting OpenOCD ==

=== Debian Package ===

We now have a Debian binary package of OpenOCD, available from http://people.openmoko.org/laforge/dpkg. Installing this package is the preferred method to install OpenOCD on your development machine like

dpkg --install openocd_82-1_i386.deb

=== Source Code ===

OpenOCD Revision 82 and later have been proven to work with our [[QT2410]] and [[Neo1973]] target board and wiggler as well as Amontect JTAGkey and JTAGkey tiny. You can e.g. check rev. 130 out of the OpenOCD subversion via

svn co -r 130 http://svn.berlios.de/svnroot/repos/openocd/trunk

== Configuration ==

[[User:HaraldWelte]] has provided a [http://people.gta01.hmw-consulting.de/laforge/misc/openocd.cfg openocd.cfg configuration file] for use of OpenOCD with wiggler and the QT2410 target board.

== Using OpenOCD ==

We cannot provide a full manual for OpenOCD, but please check
[[Bootloader#Using_JTAG_to_boot_from_RAM]] and [[NAND bad blocks#JTAG_.2F_OpenOCD_.2F_u-boot_RAM_based]], as well as the [[Neo1973 OpenOCD#Using OpenOCD telnet interface]] section below.

== Known Bugs and Troubleshooting ==

=== CP15 register read/write of ARM920T core not working ===

This has been reported upstream. Bugfix pending.

=== Did you turn it on ? ===

An easily made but devastating mistake is to forget to actually activate the CPU. Just connecting power is not enough !
Press and hold the power button until the boot loader does its count-down, or, in case there is no runnable boot loader,
the CPU keeps itself busy.

=== number of discovered devices in JTAG chain doesn't match configuration ===

You get something like:
Error: jtag.c:1224 jtag_examine_chain(): number of discovered devices in JTAG chain (51) doesn't match configuration (1)

This seems like a libftdi initialization bug. Sometimes the FT2232 doesn't get completely reset into a sane state at startup of OpenOCD. Please unplug the USB cable from the [[Amontec JTAGkey]] / [[Debug Board]] and re-plug. It should immediately work the next time. Bugfix would be appreciated a lot!

=== JTAG communication failure ===

Another common error is this one:
JTAG communication failure, check connection, JTAG interface, target power etc.

Also this one is fixed by unplugging and re-plugging USB.

== OpenOCD and [[Debug Board]] ==

=== libftdi-0.8 ===

If you want to use OpenOCD with our Debug Board v2, and want to use the serial port simultaneously with OpenOCD, you '''need libftdi-0.8 or later'''. Chances are high that your distribution still ships an earlier version of libftdi, so you might want to download it from http://www.intra2net.com/de/produkte/opensource/ftdi/ and build yourself.

=== openocd.cfg ===

This is an openocd.cfg that is known to work with [[Debug Board]], [[Neo1973 Hardware#GTA01Bv3]] and OpenOCD 130:
<pre>
telnet_port 4444
gdb_port 3333
interface ft2232
jtag_speed 0
ft2232_vid_pid 0x1457 0x5118
ft2232_layout "jtagkey"
reset_config trst_and_srst
jtag_device 4 0x1 0xf 0xe
daemon_startup attach
target arm920t little reset_run 0 arm920t
working_area 0 0x200000 0x4000 backup
run_and_halt_time 0 5000
</pre>

=== Using OpenOCD telnet interface ===

The telnet interface can be accessed using
telnet localhost 4444

it provides a plethora of functions for debugging. You might be interested in
<pre>
reset
reset halt
resume
poll
reg
load_binary
mdw
mww
</pre>

=== Using OpenOCD and gdb for remote debugging ===

First, you will need a suitable cross-gdb (a gdb that runs on your host architecture, e.g. i386, but works with code for arm). In OpenEmbedded, you can build such a cross-gcc by using
bitbake gdb-cross

If you want to debug the kernel, you can then start this gdb with
$ arm-linux-gdb vmlinux

which will give you something like
<pre>
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-linux --target=arm-linux"...
(gdb)
</pre>

We now need to connect to the OpenOCD daemon, which is done using the '''target remote''' command. In this particular example, we did already halt the target by issuing '''halt''' on the '''telnet''' command line

<pre>
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
warning: shared library handler failed to enable breakpoint
0xc0129b8c in memmove () at include/asm/current.h:9
9 {
(gdb)
</pre>

User:Cbrake

2007-03-08T13:08:20Z

Cbrake:

Cliff Brake
Embedded Linux developer/consultant
http://bec-systems.com