franciscoalecrim.com

Hi all,

+

I tested SDIO GPS with a OMAP1710 and it works. Many phones and internet tablets are based on this platform. The steps below show the procedures I’ve done:

== KERNEL SIDE ==

Compile a new kernel from linux-omap with some additional features activated.

Device Drivers  ---><*> MMC/SD card support  --->   SDIO UART/GPS class support

Boot your device with this feature.

Maemo-omap1710:~# modprobe sdio_uart

Plug your SDIO card and the message below will be printed.

mmc_slot (GPIO 193) is now openmmci-omap mmci-omap.1: cover is now closedmmci-omap mmci-omap.1: command timeout (CMD8)mmc0: new SDIO card at address f111

The entry /dev/ttySDIO0 should be created.

== USER SIDE ==

I’m using GPSd to test it. Download the last version, compile and install on my device using scratchbox.

Start the GPS daemon

Maemo-omap1710:~# gpsd -N -n -D 2 /dev/ttySDIO0 &Maemo-omap1710:~# gpsd: launching (Version 2.34)gpsd: listening on port 2947gpsd: running with effective group ID 0gpsd: running with effective user ID 0gpsd: opening GPS data source at '/dev/ttySDIO0'gpsd: speed 4800, 8N1gpsd: garmin_gps not active.gpsd: gpsd_activate(1): opened GPS (4)gpsd: SiRF packet seen when NMEA expected.gpsd: FV  0x06: Firmware version: MEW-05-00-030627Wgpsd: FV  0x06: Firmware version: 2.4.02.02 0800003f21

Get you position:

Maemo-omap1710:~# gpspipe -rgpsd: client connect on 7gpsd: client(0) turned on raw modeGPSD,R=1$GPRMC,000004,V,0000.0000,S,00000.0000,W,0.0000,0.000,090602,,*3C$GPGSA,A,1,,,,,,,,,,,,,,,,*32$GPRMC,000005,V,0000.0000,S,00000.0000,W,0.0000,0.000,090602,,*3D$GPGSA,A,1,,,,,,,,,,,,,,,,*32$GPRMC,000006,V,0000.0000,S,00000.0000,W,0.0000,0.000,090602,,*3E$GPGSA,A,1,,,,,,,,,,,,,,,,*32$GPRMC,000007,V,0000.0000,S,00000.0000,W,0.0000,0.000,090602,,*3F$GPGSA,A,1,,,,,,,,,,,,,,,,*32$GPRMC,000008,V,0000.0000,S,00000.0000,W,0.0000,0.000,090602,,*30$GPGSA,A,1,,,,,,,,,,,,,,,,*32

The filesystem used is based on Maemo.

You configured the ARM cross compiler and now you can compile your ARM kernel more fast using distcc.

Follow the instructions below.

Requirement:

* Configure DISTCC

* Configure ARM toolchain

After requirements:
”’You need to execute the instructions in all machines available for DISTCC_HOSTS.”’

=== ALL DISTCC_HOSTS MACHINES ===

* Directing ARM compilation to distcc

for a in /opt/cs-gcc/bin/arm-none-* ; do sudo ln -s /usr/bin/distcc `echo $a | cut -f5 -d/  | sed -e 's/none-eabi/linux/'` ; done

* Edit /etc/init.d/distcc

Change from: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11"      to: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/opt/cs-gcc/bin/"

* Restart distcc service

  /etc/init.d/distcc restart

* After all machines configured then you can your kernel

make ARCH=arm omap_h3_1710_defconfigmake ARCH=arm cleanmake ARCH=arm -j12

That’s all!!

Many phones are based on OMAP 1710. Search “OMAP 1710″ on google and you will find them.

The instructions below show you how you could configure a compiler for OMAP 1710 and compile a kernel using this compiler.

Instructions
Get CodeSourcery toolchain ==> arm-2005q3-2-arm-none-eabi
* On what system will your program run? ARM EABI
* On what system will you run the tools? IA32 GNU/Linux
* Download

Untar on /opt/cs-gcc

make -p /opt/cs-gcccp TOOLCHAIN_PATH/arm-2005q3-2-arm-none-eabi-i686-pc-linux-gnu.tar.bz2 /opt/cs-gcctar -xvjf arm-2005q3-2-arm-none-eabi-i686-pc-linux-gnu.tar.bz2

Create links from arm-none-eabi-* to arm-linux-*

cd /opt/cs-gcc/binfor a in arm-none-* ; do ln -s $a $(echo $a | sed -e 's/none-eabi/linux/') ; done

Compile your kernel

cd linux-omap-2.6 make ARCH=arm clean make ARCH=arm omap_h3_1710_defconfigmake ARCH=arm 

References:
* http://linux.omap.com/pipermail/linux-omap-open-source/2004-November/002175.html
* http://people.via.ecp.fr/~clem/nist/qt-notes.php