Mittwoch, 10. Februar 2010

start using the OKL4 SDK

I just starting playing around with the okl4 (http://wiki.ok-labs.com/).

I was facing some problems, so after the first step is done - the delivered versatile platform compiles - I would like to give you the "How to build the OKL4 3.0 for the versatile platform from the arm926ejs SDK HOWTO":

- Because of some problems with self build cross compilers I also decided to use prebuild binaries. -

1)

Download the needed packages:

* The SDK - sdk-arm926ejs-3.0.tar.gz (http://wiki.ok-labs.com/downloads/release-3.0/sdk-arm926ejs-3.0.tar.gz)
* The NICTA tool chain - arm-linux.3.4.4.tar.gz (http://ertos.nicta.com.au/downloads/tools/arm-linux-3.4.4.tar.gz)
* The cross compiler - arm-linux-gnueabi-4.2.4.tar.gz (http://wiki.ok-labs.com/downloads/release-3.0/arm-linux-gnueabi-4.2.4.tar.gz)

2)

Extract them.

On my system I create this structure:

* arm-linux
* arm-linux-gnueabi
* sdk

3)

Configure the makefiles.

You may have found different notes saying to export OKL4_SDK_ROOT. However, I like relative paths, so the settings in the makefiles for this are good enough for me.

What's not ok is the used toolchains:

For the soc makefile I changed it to:

TOOLPREFIX=$(OKL4_SDK_ROOT)/../arm-linux/bin/arm-linux-

For e.g. the singlecell makefile (in singlecell/hello/Makefile), change it to:

TOOLPREFIX?=$(OKL4_SDK_ROOT)/../arm-linux-gnueabi/bin/arm-unknown-linux-gnueabi-

4)

Call "make all" in the soc/versatile folder followed by "make install". Than you should be able to call "make" in the singlecell example.

Andreas