Thread: How to get this to work on an ARM processor?

Sounds about right.

OBD GPS Logger has been tested on x86_64, x86, and PPC [so far]. I strongly suspect there's no reason it can't work on ARM too.

Sheevaplug - that means you won't be needing the GUI? Probably makes life easier. The GUI is the only C++ thing in the codebase, too - the rest of it should work with just about any old C compiler you can hunt down.

If you want the GPS logging working [I assume you do], you'll want to get gpsd installed too. obdgpslogger links against libgps [from gpsd] to get the gps data.

Unless you enable dbus [it's off by default, for this application you don't want it], obdgpslogger depends on nothing other than libgps, it calls nothing that isn't in standard libc - it *should* be as simple to build as anything out there. Even if you can't get gpsd working, obdgpslogger will gracefully fallback to not linking with gpsd, and just log obd data.

Are you cross-compiling, or building directly on the device? If you're building directly on the device [much, much, much easier if you can], you'll need gcc and ideally cmake. If you can't get cmake, then I'll write you a couple custom makefiles to get the job done.

Gary (-;

Also, I just checked out that SheevaPlug. I want one! Looks Sweet :-)

Gary (-;

And if you really have trouble, I should be getting my sheeva by the end of the week. Next weekend I'll be able to give some pretty serious help. ;-)
Plus Friday is the last day of school for me.

I'll give it a go! I haven't had a chance to really focus on this but last time I tried to cmake, it told me it didn't know what that command was and I was lost.

Originally Posted by cgalpin

Paul, how do you know yours is coming? Did you get an email letting you know? I have not heard back since I ordered.

I got an email saying:

We just wanted to update you and let you know that your order ****** has shipped via FedEx Ground Service.
Here is your Tracking Number (if available): ***************

Thanks for shopping at GlobalScale Technologies.

GlobalScale Technologies Customer Service

Yeah, for awhile they were running a backorder. I took mine about 6 weeks to arrive and I finally got an email telling me it had shipped and when it would arrive. It also said they had stopped taking orders for awhile until they caught up.

last time I tried to cmake, it told me it didn't know what that command was

Yeah, you need the cmake package installed for that to work.

I've just been browsing the sheeva development stuff; quick question, do you use a cross-compiler, or are you doing something different? If you're using a cross-compiler, cmake gracefully supports what they call "toolchain" files. I can write one for you so that you can compile obdgpslogger on your PC [with your sheeva toolchain installed] using the cmake you already have on that PC.

Gary (-;

OK, cross-compiling happy fun time. I'm going to assume you're using Linux as your development desktop, since those are the tools provided by plugcomputing:

1) Download the relevant development kit from plugcomputing. Specifically, go to resources->downloads, click on Compilers, then download "SHEEVAPLUG HOST SW SUPPORT PACKAGE FOR LINUX"

2) Extract it all. I'm going to set up some "standards" for you to adhere to now that will work for you:

Code:

unzip SheevaPlug_Host_SWsupportPackageLinuxHost.zip
cd LinuxHost
bzip2 -cd ./gcc.tar.bz2 | tar -xvf-
sudo mv gcc /usr/local/sheeva-toolchain
gzip -cd "./Linux Host Filesystem - rootfs.tar.bz2" | tar -xvf-
sudo mv rootfsv1.0 /usr/local/sheeva

2a) Make sure you have cmake installed. If you're using ubuntu, "sudo apt-get install cmake".

You now have all the tools you need to cross-compile stuff for sheeva. Now to try compiling.

3) Make sure you have the latest svn of obdgpslogger, as I've added a Sheeva toolchain file to it:

Code:

svn co svn://svn.icculus.org/obdgpslogger/trunk obdgpslogger

4) Set your environment to let cmake find the sheeva toolchain:

Code:

PATH=/usr/local/sheeva-toolchain/bin:$PATH; export PATH

5) And build!

Code:

mkdir build; cd build
cmake -DCMAKE_TOOLCHAIN_FILE=../cmakemodules/Toolchain-sheeva.cmake ..
make

See what happens. Assuming all goes to plan, you will find the important binary you need in ../bin:

Code:

$ file ../bin/obdgpslogger
../bin/obdgpslogger: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.14, not stripped

Well, that was easy. [comparatively :-D]

Gary (-;