Install HowTo - Software Distribution 2.10

Introduction

This document describes how to install the Axis Developer Board/Device Server Software Distribution release 2.10 that is a part of the Software Developer Kit (SDK).

Requirements

  • OS: Any fairly new Linux distribution should work 1)
  • Ethernet network interface
  • Root access
  • gcc C compiler
  • GNU make version 3.80 or 3.81
  • GNU wget
  • awk (or gawk)
  • bc
  • byacc (or yacc if byacc is a link to it)
  • lex or flex
  • perl
  • sed
  • tar
  • zlib 2)
  • md5sum
  • curses or ncurses 3)
  • bison
  • which

Installation process

The software distribution consists of an install package and several distributed packages. It can be installed two ways, normal_installation and tarball_installation. The difference between the methods is how the distributed packages are accessed as both methods require the install package. Normal installation requires an Internet connection on the computer that the software distribution will be installed on. On the other hand, with the tarball installation, you download an additional tarball that includes all distributed packages to be used on a target computer that doesn't have an Internet connection.

Normal installation

The normal installation downloads the required software packages during the install process. This reduces the amount of space the installed software distribution will occupy as well as the amount of downloaded content. An Internet connection is required on the computer intended for the installation.

Download the install package

Download the install package devboard-R2_10.tar.gz from http://www.axis.com/products/dev_sdk/download_dist.php. The package contains, among other things, the configure script for installing the software distribution.

Extract the install package

Unpack the downloaded devboard-R2_10.tar.gz which creates a devboard-R2_10 directory.

tar xfz devboard-R2_10.tar.gz

Run configure script

Enter the newly created devboard-R2_10 directory and run the configure script. This will download and install the tools and source code needed to configure the software distribution.

./configure

The configure script will ask which product to build firmware for. The selection you make determines which configuration files will be used. Choose the product that most closely resembles your hardware. Alternatively, you may set the product type by setting the DEV_BOARD_PRODUCT variable prior to running the configure script.

The next question deals with if you would like to configure the product or keep the default configuration. In most cases, it is recommended to configure the software distribution since the default configuration only includes a subset of all available packages. By entering y, the selection of packages can be configured before being downloaded, saving time, disk space, and bandwidth.

Note: You will get this question only the first time the software distribution is installed. Of course, the software distribution can be configured later.

If you chose to configure the software distribution, go to the configuration_of_the_software_distribution chapter, otherwise jump to the build_the_firmware_image chapter.

The configure script can be run non-interactively by redirecting its input from /dev/null. In this case, you will not be able to configure the selection of packages. However, you can still choose which product to use, by setting the DEV_BOARD_PRODUCT variable prior to running the script.

DEV_BOARD_PRODUCT=<product name> ./configure </dev/null

Tarball installation

The tarball installation involves using two tarballs, and in contrast to the normal installation, no Internet connection is required on the target computer. The first tarball is the same package as used in the normal installation, and the second includes all the packages contained in the software distribution.

Download the install package and the tarball

Download the install package devboard-R2_10.tar.gz and devboard-R2_10-distfiles.tar.gz from http://www.axis.com/products/dev_sdk/download_dist.php The devboard-R2_10.tar.gz package contains, among other things, the configure script that is needed for installing the software distribution. The devboard-R2_10-distfiles.tar.gz contains all the packages that comprise the software distribution.

Extract tar files

Extract the devboard-R2_10.tar.gz and the devboard-distfiles-R2_10.tar.gz files. This will create two directories devboard-R2_10 and distfiles. The distfiles directory contains all packages that are needed for the installation. Now, make a symbolic link in the devboard-R2_10 directory pointing to the distfiles directory. By doing this the install procedure will find the required packages locally. Consequently, the packages do not have be fetched from the Axis repository.

tar xvfz devboard-R2_10.tar.gz
tar xvfz devboard-R2_10-distfiles.tar.gz
cd devboard-R2_10
ln -s ../distfiles

Run configure script

Enter the newly created devboard-R2_10 directory and run the configure script. This will install the tools and source code needed to configure the software distribution.

./configure

The configure script will ask which product to build firmware for. Select the product that most closely resembles your hardware. This selection determines which configuration files will be used. Alternatively, you may set the product type by setting the DEV_BOARD_PRODUCT variable prior to running the configure script.

The next question deals with if you would like to configure the product or keep to the default configuration. In most cases, it is recommended to configure the software distribution since the default configuration only includes a subset of all available packages. By entering y the selection of packages can be configured before the packages are installed.

Note: You will get this question only the first time you install the software distribution. Of course,the software distribution can be configured later.

If you chose to configure the software distribution, go to the configuration_of_the_software_distribution chapter, otherwise jump to the build_the_firmware_image chapter.

The configure script can be run non-interactively, by redirecting its input from /dev/null. In this case, you will not be able to configure the selection of packages. However, you can still choose which product to use, by setting the DEV_BOARD_PRODUCT variable prior to running the script.

DEV_BOARD_PRODUCT=<product name> ./configure </dev/null

Configuration and building of the firmware

Configuration of the software distribution

To select which packages to include in the firmware, change the configuration by running make with any of the configuration targets menuconfig, xconfig or config. This will bring up a configuration utility that enables you to generate a custom configuration. The recommended method to use is 'make menuconfig', which will bring up a graphical menu in your shell. The menu is categorically organized, which makes the selection of packages fairly easy and logical. 'make xconfig' is an X windows based application that works in a similar manner as menuconfig. 'make config' is text based and will traverse through all configuration options one at a time.

make menuconfig

or

make xconfig

or

make config

Use your preferred method and configure the software distribution according to your needs. Don't forget to save the configuration when prompted before exiting the configuration utility.

Run the configure script to install the packages required by the configuration. The configure script will also generate the top-level Makefile that is used in the next step.

./configure

Build the firmware image

Your software distribution should now be correctly installed and it's now time to build the firmware images. Run make, get a cup of coffee, and sit back and wait for the firmware image process to finish.

make

Updating the software distribution from 2.01 to 2.10

As a result of the changes between the 2.01 and the 2.10 release, upgrading is not recommended. Instead, install 2.10 as described above in a fresh directory and then transfer the changes made in the earlier installation to the new one.


While every care has been taken in the preparation of this document, Axis Communications AB cannot be held responsible for any technical errors. If you do detect any inaccuracies or omissions, please inform us at: AXIS Online Helpdesk4)

1) Strictly POSIX compliant system shells isn't supported, see Build system not fully posix compliant
2) e.g. zlib1g and zlib1g-dev
3) e.g. libncurses5 and libncurses5-dev
4) For product category, please select “System-on-Chips & Device Servers”.
 
axis/install-howto-2_10.txt · Last modified: 2011/05/20 07:50 by jesper
 
All text is available under the terms of the GNU Free Documentation License (see Copyrights for details).