Gumstix User Wiki - User contributions [en]

Qtopia platform howto

2009-10-15T20:55:47Z

Jsarao:

we need qtopia to find the compiler (symlinks & path)

$ cd path-to/gumstix-oe/tmp/cross/bin ; for f in arm-angstrom-linux-gnueabi-*; do n=$(echo $f|cut -b 28-); ln -s $f arm-linux-$n; done
$ PATH=$PATH:path-to/gumstix-oe/tmp/cross/bin/ ; export PATH

download and unpack

$ wget ftp://ftp.trolltech.com/qtopia/source/qtopia-opensource-src-4.3.1.tar.gz
$ tar xfzv qtopia-opensource-src-4.3.1.tar.gz

configure, make and make install

$ mkdir qtopia-platform ; cd qtopia-platform
$ ../qtopia-opensource-4.3.1/configure -separate-debug-info -little-endian -edition platform -xplatform arm -arch arm -no-telephony -prefix /qtopia
$ make ; make install

tar image and move it to gumstix

$ cd image ; tar cfv ~/qtopia-platform.tar .

gumstix: $ mkdir /media/cf/qtopia ; tar xvf qtopia-platform.tar -C /media/cf/qtopia ; ln -s /media/cf/qtopia/ /qtopia

qtopia needs libstdc++, move it to your gumstix's /lib or somewhere it can be found

$ cd path-to/gumstix-oe/tmp/staging/arm-angstrom-linux-gnueabi/lib/
$ tar cfv ~/libstdc++.tar libstdc++.so*

libstdc++.so
libstdc++.so.6
libstdc++.so.6.0.8

gumstix: $ tar xvf libstdc++.tar -C /lib

set variables for qtopia & run

$ export QWS_MOUSE_PROTO='LinuxTP:/dev/input/touchscreen0'
$ /qtopia/bin/qpe -qws &

calibrate touchscreen

$ /qtopia/bin/qcop service send Launcher "execute(QString)" "calibrate" &

'''incomplete''' touchscreen and keyboard not working. mouse works

[[Category:How_to_-_general]]

Qtopia platform howto

2009-10-15T20:55:19Z

Jsarao:

Category:How to - i2c

2009-10-15T20:53:05Z

Jsarao: add category yags

==Background==

I2c is a 2-wire serial 8 bit communications protocol from the old days. It is mainly used to communicate between on-board components when the design does not allow for a data and address bus. Typical components are elapsed timer chips, ee-proms, FRAM's, A/D and D/A chips. Some cpu's have the I2c hardware shift registers built in.

The 2 wires are the SCL or clock wire and the SDL or data wire. The clock high to low transition is used to signal that the data wire has a stable 1/0 data value and that the receiver should shift this into the data results register. The clock line is high when the bus is idle. A special high to low transition on the clock line followed by a high to low transition on the data line signals the start of a message sequence. the end of a message sequence is a low to high transition in the data line followed by a low to high transition in the SCL line. An important aspect of this communication standard is that each device is assigned a unique 7 bit address, (oh yea the 8th bit is the Read/write indicator to complete the byte). The device address is the first byte sent in any communication. Subsequent bytes of a message depend on the device you are talking to.

Because of patents that have since expired, other companies had to use slightly differnet ways to do the same thing so a very similar serial communicatinos method called SPI uses 4 wires and another called TWI uses the same 2 wires.

==Further information==

Another source of I2C information can be found [http://www.gumstix.net/wiki/index.php?title=I%C2%B2C here].

[[Category:How_to_-_general]]

Category:How to - bluetooth

2009-10-15T20:51:39Z

Jsarao:

== Essentials ==

Install the basic bluetooth stuff with

ipkg install bluez-utils

First off, I had to move the "sleep 1" from after "sdptool add ..." to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.

== Networking: pan access point ==

ipkg install dnsmasq

/etc/dnsmasq.conf needs to contain (among other things it comes with):

interface=bnep0
dhcp-range=10.0.1.10,10.0.1.200,2h

/etc/network/interfaces:

allow-hotplug bnep0
iface bnep0 inet static
address 10.0.1.1
netmask 255.255.255.0
network 10.0.1.0

/etc/default/bluetooth:

PAND_ENABLE=true
PAND_OPTIONS="--listen --role NAP"

/etc/network/if-up.d/btap

#!/bin/sh
iptables -A POSTROUTING -t nat -j MASQUERADE -s 10.0.1.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -P FORWARD ACCEPT

You may need to re-run pand or re-run the post-up script.

== Networking: pan client ==

/etc/network/interfaces:

allow-hotplug bnep0
iface bnep0 inet dhcp

/etc/default/bluetooth:

PAND_ENABLE=true
PAND_OPTIONS="--role PANU --search"

For some reason pan can't find my access point so I have to hardcode it

PAND_OPTIONS="-c 00:0B:5D:44:33:22"

== Dialup networking: server ==

ipkg install pppd

ipkg install (some kernel modules iirc)

I'm not sure if both the bridging and masquerading scripts are required. The pan0 device would need to be created in advance (with brctl iirc)

/etc/default/bluetooth:

DUND_ENABLE=true
DUND_OPTIONS="--master --channel 3 --auth --encrypt --secure --pppd /bin/mypppd"

/bin/mypppd:

#!/bin/sh
LEASES=/var/run/mypppd.leases
grep -q $DUN_BDADDR $LEASES || echo $DUN_BDADDR >>$LEASES
LOCAL=192.168.32.10
REMOTE=192.168.42.`grep -n $DUN_BDADDR $LEASES | cut -d : -f1`
pppd $LOCAL:$REMOTE $*

/etc/ppp/peers/dun:

460800
crtscts
debug
local
noipdefault
passive
connect "/etc/ppp/peers/at-command.pl"
noauth
nodefaultroute
noipx
noaccomp
nobsdcomp
nodeflate
ms-dns 198.60.22.2

/etc/ppp/peers/at-command.pl:

#!/usr/bin/perl

$/ = "\r";
while(<STDIN>)
{
$_ = uc;
if(/^ATD/) {
print "CONNECT\r\n";
exit(0);
} elsif(/^AT/) {
print "OK\r\n";
}
}

/etc/ppp/ip-up.d/09nat

iptables -F -t nat

echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_dynaddr

iptables -t nat -A POSTROUTING -s 192.168.42.0/24 -j MASQUERADE
iptables -t nat -A POSTROUTING -s 10.0.1.0/24 -j MASQUERADE
iptables -P FORWARD ACCEPT

/etc/ppp/ip-up.d/10bridge

#!/bin/sh
brctl addif pan0 $2

== Dialup networking: client ==

== GPS repeater ==

Install gpsd and configure it for your gps connection.

In /etc/init.d/bluetooth, change

$RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &
to
$RFCOMM_EXEC -r watch 0 1 sh -c "gpspipe -r >/dev/rfcomm0" &

Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:

$RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &

but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.

== Keyboard or mouse ==

Put your keyboard or mouse in pairing mode and run:

hidd --search

The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth

HIDD_ENABLE=true
HIDD_OPTIONS="--master --server"

== Voice audio ==

Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.

== High-fidelity audio ==

You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.

Install the packages you'll need:

ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay

Edit /etc/bluetooth/audio.service to enable autostart:

[Bluetooth Service]
Identifier=audio
Name=Audio service
Description=Bluetooth Audio service
Autostart=true

Reboot now if you had to change this.

You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need "8888" but most need "0000" for the pin:

passkey-agent --default 0000 &

put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:

hcitool scan

edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:

pcm.itech {
type bluetooth
device "00:0D:3C:8A:13:06"
}

now try playing something to it:

madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech

you can also live-encode the line in source to a2dp:

arecord -c 2 -f s16 -r 44100 | aplay -D itech

unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.

== Debugging connection problems ==

The best way to figure out what is happening is to use hcidump.

ipkg install bluez-hcidump

In a separate window, or in the background, start the dump:

hcidump -XV

And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.

==Bluetooth advice from Australia==
===kick-start===
The Infineon v1.01 modules require a once-only 'kick-start' to become operational at a speed of 921600.
We have found the kick-start procedure below must be adhered to exactly, in order for the module to properly invoke the 'infineon manufacturer mode' function (that changes the speed) within hciattach.

The kick-start procedure is as follows-
<pre>
/etc/init.d/S30bluetooth stop

echo \"AF1 out\" > /proc/gpio/GPIO12
echo \"GPIO out clear\" >/proc/gpio/GPIO7
sleep 1
echo \"GPIO out set\" >/proc/gpio/GPIO7
sleep 1
echo \"AF1 in\" > /proc/gpio/GPIO42
echo \"AF2 out\" > /proc/gpio/GPIO43
echo \"AF1 in\" > /proc/gpio/GPIO44
echo \"AF2 out\" > /proc/gpio/GPIO45
/usr/sbin/hciattach -s 115200 ttyS1 gumstix 115200
/etc/init.d/S30bluetooth stop
echo \"AF1 out\" > /proc/gpio/GPIO12
echo \"GPIO out clear\" >/proc/gpio/GPIO7
sleep 1
echo \"GPIO out set\" >/proc/gpio/GPIO7
sleep 1
echo \"AF1 in\" > /proc/gpio/GPIO42
echo \"AF2 out\" > /proc/gpio/GPIO43
echo \"AF1 in\" > /proc/gpio/GPIO44
echo \"AF2 out\" > /proc/gpio/GPIO45
/usr/sbin/hciattach -s 115200 ttyS1 gumstix 921600 <-- (Infineon Manufacturer Mode is invoked here, within hciattach)
/etc/init.d/S30bluetooth stop
echo \"AF1 out\" > /proc/gpio/GPIO12
echo \"GPIO out clear\" >/proc/gpio/GPIO7
sleep 1
echo \"GPIO out set\" >/proc/gpio/GPIO7
sleep 1
echo \"AF1 in\" > /proc/gpio/GPIO42
echo \"AF2 out\" > /proc/gpio/GPIO43
echo \"AF1 in\" > /proc/gpio/GPIO44
echo \"AF2 out\" > /proc/gpio/GPIO45
/usr/sbin/hciattach -s 921600 ttyS1 gumstix 921600 <-- (Will now connect at 921600 using this command only)
</pre>
--------------------------------------------------------------------------------------------------------------------------------------------------------------

===BlueZ utilities===
The BlueZ utilities version we were using was too old- V2.24, and it did not contain the appropriate 'infineon manufacturer mode' functions required to change the speed of the module. It gave the following output when trying to bring up the module-

----Read wrong response size: 4
----0x04 0xff 0x01 0x00

We upgraded to BlueZ V3.24 and this solved the above problem, however
we had to comment out the following lines in the 'gumstix_reset'
function of 'hciattach.c'-

<pre>
//system("echo clear > /proc/gpio/GPIO12");
//system("echo set > /proc/gpio/GPIO12");
</pre>

We felt these were more appropriate in S30Bluetooth.
--------------------------------------------------------------------------------------------------------------------------------------------------------------

===HCIATTACH commands===
The Bluetooth appears to be on ttyS1, where previously it was present on ttyS3.
Thus the following changes needed to be made to /etc/default/bluetooth-

HCIATTACH_TTY=ttyS1

...and we also had to put in new speed parameters to bring the module up properly after a kick-start-

HCIATTACH_START_SPEED=921600
HCIATTACH_SPEED=921600
--------------------------------------------------------------------------------------------------------------------------------------------------------------
===Configure extra GPIOs===
Lastly, some extra GPIOs needed to be configured as appropriate. We only discovered this when we looked at the Open Embedded version of /etc/init.d/bluetooth and discovered that it had some mysterious extra GPIOs being set, that were not present in the buildroot script or any documentation. These are the following-

<pre>
echo AF1 out > /proc/gpio/GPIO12
sleep 1
echo GPIO out clear >/proc/gpio/GPIO7
sleep 1
echo GPIO out set >/proc/gpio/GPIO7
sleep 1
echo "AF1 in" > /proc/gpio/GPIO42 #(Not present in buildroot)
echo "AF2 out" > /proc/gpio/GPIO43 #(Not present in buildroot)
echo "AF1 in" > /proc/gpio/GPIO44 #(Not present in buildroot, not documented)
echo "AF2 out" > /proc/gpio/GPIO45 #(Not present in buildroot, not documented)
</pre>

The last two GPIOs (44/45) do not seem to be documented anywhere?- http://docwiki.gumstix.org/Gumstix_UARTs
--------------------------------------------------------------------------------------------------------------------------------------------------------------

All of these changes were required to make the modules work properly.

We have also identified that the new v1.01 infineon module has improved pairing ability over its predecessor. Its predecessor required that a passkey be entered every time the unit connects to a paired device. The new module only requires a passkey once, and subsequent connection attempts are automatically connected, as they should be.

Tomas Targownik

[[Category:How_to_-_general]]

Category:How to - bluetooth

2009-10-15T20:49:01Z

Jsarao:

Build Environment Ubuntu 9.04

2009-10-08T17:33:10Z

Jsarao:

This is based on the set-up for Ubuntu 8.10 with file modifications as described [http://www.nabble.com/Ubuntu-8.10-and-Open-Embeded-td21136352.html on this thread]. gumstix-oe version is 318.

== Setup Build Environment ==
1) Get Ubuntu linux 9.04, and install it on your computer; you can install a vmware version of Ubuntu too, but it will be slow during the building process.

Reconfigure sh to point to bash, not dash:

sudo dpkg-reconfigure dash

Answer no when asked whether you want to install dash as /bin/sh.

2) Install (build-essential, help2man, diffstat, texi2html, texinfo, libncurses5-dev, cvs, gawk, python-dev, python-pysqlite2, python-psyco, ckermit, lrzsz, subversion) by using apt-get. i.e:
sudo apt-get update
sudo apt-get install build-essential help2man diffstat texi2html texinfo libncurses5-dev cvs gawk
sudo apt-get install python-dev python-pysqlite2 python-psyco ckermit lrzsz subversion

See [[Bitbake_on_Ubuntu|Bitbake On Ubuntu]] for directions on how to setup Bitbake.

3) Download the source from svn, caching the source code
mkdir ~/gumstix
cd ~/gumstix
<nowiki>svn co https://gumstix.svn.sourceforge.net/svnroot/gumstix/trunk gumstix-oe</nowiki>
cat gumstix-oe/extras/profile >> ~/.bashrc
sudo groupadd oe
sudo usermod -a -G oe YOUR_CURRENT_USERNAME
sudo mkdir /usr/share/sources
sudo chgrp oe /usr/share/sources
sudo chmod 0775 /usr/share/sources
sudo chmod ug+s /usr/share/sources

4) Downgrade to gcc-4.1 and g++-4.1 and change the links:

sudo aptitude install gcc-4.1 g++-4.1
sudo ln -sf /usr/bin/gcc-4.1 /usr/bin/gcc
sudo ln -sf /usr/bin/g++-4.1 /usr/bin/g++

Check the links are correct using:

ls -l /usr/bin/gcc
ls -l /usr/bin/g++

5) Log out and log in again.

6) Build the basic image, it will fail with an error in dbus:

bitbake gumstix-basic-image

Edit <code>gumstix/gumstix-oe/tmp/work/i686-linux/dbus-native-1.0.1-r0/dbus-1.0.1/dbus/dbus-sysdeps-unix.c</code>

Add this struct,

<code><pre>
struct ucred {
unsigned int pid;
unsigned int uid;
unsigned int gid;
};
</pre></code>

after the macros.

7) Build the basic image, it will fail with an error in sumversion:

bitbake gumstix-basic-image

Edit <code>gumstix/gumstix-oe/tmp/work/gumstix-custom-verdex-angstrom-linux-gnueabi/gumstix-kernel-2.6.21-r1/linux-2.6.21/scripts/mod/sumversion.c</code>

Add this line,

#include <limits.h>

after all of the other includes.

8) Build the basic image again. If it fails with an error in gconf-dbus, do the following:

a. download file http://download.gnome.org/sources/GConf-dbus/2.16/GConf-dbus-2.16.0.tar.gz

b. move and rename this file to:
/usr/share/sources/trunk_developer.imendio.com_.svn.gconf-dbus_606_.tar.gz

9) Build the basic image again, this time it should work:

bitbake gumstix-basic-image

10) If everything builds ok, it could be a good idea to modify the dbus-sysdeps-unix.c and sumversion.c files in their respective packages in /usr/share/sources as otherwise everytime you do a rebuild they will be wiped. Note that dbus-sysdeps-unix.c is found in package dbus-1.0.1.tar.gz, and sumversion.c is found in package linux-2.6.21.tar.bz2.

[[Category:How_to_-_general]]
[[Category:How_to_-_Ubuntu]]

Talk:Build Environment Ubuntu 9.04

2009-10-08T17:31:40Z

Jsarao:

Since this is the page for building things in Ubuntu 9.04, shouldn't step 1) be "Get Ubuntu linux 9.04" instead of "Get Ubuntu linux 8.10"?
:why my page for 8.10 was deleted? is it the same for 9.04?

'''Modify Step 3?'''

from: sudo usermod -a -G oe ''YOUR_CURRENT_USERNAME''

to: sudo usermod -a -G oe ''$USER''

'''Bitbake Step'''

How about a step for getting bitbake?
Option 1) sudo apt-get bitbake
Option 2) pull bitbake from repository
Option 3) See [[Bitbake_on_Ubuntu|Bitbake On Ubuntu]] for directions on how to setup Bitbake.

Talk:Build Environment Ubuntu 9.04

2009-10-08T17:24:47Z

Jsarao:

Talk:Build Environment Ubuntu 9.04

2009-10-08T17:22:58Z

Jsarao:

Talk:USB

2009-05-14T23:57:37Z

Jsarao:

This looks like it should just be combined with the article "USB on the 24-Pin Flex Connector" (http://www.gumstix.net/wiki/index.php?title=USB_24_Pin). -jsarao

Talk:USB

2009-05-14T23:56:38Z

Jsarao: New page: This looks like it should just be combined with [USB_24_Pin|USB on the 24-Pin Flex Connector]. -jsarao

This looks like it should just be combined with [USB_24_Pin|USB on the 24-Pin Flex Connector]. -jsarao

Talk:USB hub

2009-05-14T23:49:41Z

Jsarao:

How is this a "How To"? -jsarao

Talk:USB hub

2009-05-14T23:49:26Z

Jsarao: New page: How is this a "How To"?

How is this a "How To"?