OKL4 Release 3.0

This page describes the OKL4 3.0 release series. To view other releases, check out PreviousReleases. For more information on the naming of versions, see VersioningPolicy.

Downloads

SDK

Binary software development kits for OKL4, supporting a system on a chip allowing you to develop for your target platform without downloading the full source.

• ARM926ejs 3.0

• ARM1136js 3.0

• ARM920t 3.0

• XScale 3.0

Source

• OKL4 3.0

• OK Linux 2.6.24.9-patch.4

Poky Linux

Patch for the Poky Linux distribution to add support for OKL4. The SDK Tutorial: Linux has the information on how to build and run Poky Linux.

• Poky Linux Patch

Documentation

Reference

• OKL4 Microkernel reference manual

• Elfweaver reference manual

• OKL4 Library reference manual

• SoC Developers manual

• Overview of the OKL4 3.0 API

Tutorial

• SDK Tutorial: Hello World

• SDK Tutorial: Linux

Toolchains

All the SDKs in this release need a GCC cross compiler that supports EABI.

• arm-linux-gnueabi-4.2.4.tar.gz (68 MB)

To build such a cross compiler get the latest version of Crosstool 0.43 and apply the Crosstool EABI patch. Then build the toolchain with:

# sh demo-arm-softfloat.sh 

Simulators

To test images built using the SDK or the complete source tarball you can use one of the following simulators depending on which platform you are using.

Skyeye (for Gumstix)

A binary version of the Skyeye 1.2.1n simulator available to simulate the Gumstix platform. You will need the skyeye.conf file as well. To simulate use:

# skyeye -c skyeye.conf -e image.sim

Qemu (for KZM and Versatile)

A source copy of the Qemu 0.9.1 simulator is available to simulate the KZM and Versatile platforms. It is built with the following commands:

# ./configure --target-list=arm-softmmu --disable-sdl --static --disable-gfx-check
# make

Using the SDK

To use the SDK extract the tarball and set the OKL4_SDK_ROOT environment variable to point to that directory:

# tar zxf sdk-xscale.tar.gz
# export OKL4_SDK_ROOT=/path/to/sdk

From your project directory or from one of the examples you can use make to build your project. There are two variables that can be passed to make, KERNEL and BUILD. KERNEL can be set to micro or nano and defines which kernel the project object files are linked against. BUILD can be set to benchmark, debug, debug_no_console, production or tracebuffers and defines the level of debug support provided in the kernel. For example, to build and then link the hello world example against the nano kernel compiled for benchmarking you would use:

# cd $OKL4_SDK_ROOT/okl4/xscale/examples/singlecell
# make KERNEL=nano BUILD=benchmark

The image that is built can be found in the build directory which depends on the KERNEL and BUILD variables:

build.<KERNEL>-<BUILD>/images/image.elf

XScale

The XScale SDK supports the Gumstix platform. To simulate an image with Skyeye use:

# skyeye -c skyeye.conf -e build.<KERNEL>-<BUILD>/images/image.elf

ARM1136js

The ARM1136js SDK supports the KZM platform. To simulate an image linked against the OKL4 Microkernel use:

# qemu-system-arm -M kzm -nographic -start-addr 0x86800000 -kernel build.micro-<BUILD>/images/image.elf

whereas for an image linked against the OKL4 Nano use:

# qemu-system-arm -M kzm -nographic -kernel build.nano-<BUILD>/images/image.elf

ARM926ejs

The ARM926ejs SDK supports the Versatile platform. To simulate an image linked against the micro kernel use:

# qemu-system-arm -M versatileab -start-addr 0x07900000 -nographic -kernel build.micro-<BUILD>/images/image.elf

whereas for an image linked against the nano kernel use:

# qemu-system-arm -M versatileab -start-addr 0x04100000 -nographic -kernel build.nano-<BUILD>/images/image.elf