How to Install the Developer Board Software

Description

This document describes how to install the latest Developer Board Software. The document Getting Started Guide to AXIS Developer Board may be of some interest if the unit is not up and running yet.

Requirements

System requirements:

OS: Any fairly new Linux distribution should work - installation has at least been tested with distributions with Redhat and Debian.
You must be able to become root user during some stages of the installation.
gcc C compiler.
GNU make
GNU wget
awk
bc
byacc (or yacc if byacc is a link to it)
lex or flex
perl
sed
tar
zlib
md5sum
Ethernet network interface.
CRIS cross-compiler
pmake
curses
bison

CRIS cross-compiler:

To compile code to be executed on Axis ETRAX processors the CRIS cross-compiler is required. Both the source code and distributions are available in the download section: http://developer.axis.com/download/compiler/. The documentation is bundled together with the compiler and the tools. Refer to the README file for more detailed information

SDK sources:

Download the SDK sources in the download section: http://developer.axis.com/download.

Process

Ungzip and untar the downloaded gzipped tar archive in your home directory by typing:

cd <SDK destination path>
tar zxfv <path to compressed downloaded SDK sources>/<SDK>.tar.gz

Example: cd /home/me/theLatestAxisSDK
tar zxfv /tmp/devboard-RX_YY.tar.gz

Type the following to run the install script:

./install <product>

Example: ./install devboard_82+        (Configures the default configuration for Developer Board 82+/Device Server 83+)
                or
                ./install                            (Prompts which product to build)

The product name is optionally given when invoking the install-script, otherwise prompted for when running the script without any arguments. The script will, when invoked, reset the current configuration (if existing) to a default configuration for the product chosen.

The next step is to configure the product, if a configuration other than the default one is needed. This is done by making one of the xconfig, gconfig, config, menuconfig targets (similar to the config of the kernel):

Example: make menuconfig

Now, to fetch the packages configured and to generate the top-level Makefile; Run configure:

Example: ./configure

There are some other options available to the configure script, execute ./configure --help (or -h) to read more about theese configure options.

Finally the build:

Example: make

Notes

Read the RELEASEfile included in the release for information about the release.

It can be convenient to source the tools directory supplied within the SDK package to easily access the tools needed for e.g. boot loading images or building packages separately etc. To do so, execute the init_env script:

cd <SDK destination path>
. ./init_env

It might be that some shells does not accept . ./init_env, in that case try source ./init_env instead.

To be able to see the boot log from the developer board connect the serial port (refer to Getting started guide for information about how to do so).