Install howto - Software Distribution 2.01

Introduction

This document describes how to install or upgrade to the Axis Developer Board/Device server (SDK) release 2.01.

Requirements

  • OS: Any fairly new Linux distribution should work.
  • Ethernet network interface.
  • Ability to become root (some installation stages require 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
  • md5sum
  • pmake
  • curses or ncurses
  • bison
  • which

Installation process

This software can be installed in two different ways, normal installation and tarball installation. The normal installation requires an Internet connection on the host that the SDK will be installed on. The tarball installation on the other hand does not require an Internet connection but instead you will have to download (or otherwise obtain) the fairly large tarball which contains all packages included in the SDK.

Normal installation method

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_01.tar.gz, from http://www.axis.com/products/dev_sdk/download_dist.php. This package include scripts needed for installing the SDK.

Extract the install package

Extract the devboard-R2_01.tar.gz archive. This will create a directory named devboard-R2_01.

tar -xvzf devboard-R2_01.tar.gz

Install a basic selection of packages

Enter the newly created “devboard-R2_01” directory and run the install script. This will download and install tools and source code needed to configure the SDK in the next step.

First you will be confronted with a question if you would like to copy distribution files from an earlier SDK installation. Provided that you have a fairly new SDK release, copying files will reduce the number of packages needed to be downloaded. If unsure, just skip this step.

At the end of the install script you will be asked which product to use. This selection determines which configuration files to be used. Select a product that resembles your hardware.

./install

Continue with the Configuration and building of the firmware chapter.

Tarball installation method

The tarball installation method does not require an Internet connection on the computed intended for the installation. Instead all packages are downloaded at once as a huge tarball.

Download the install package and the tarball

Downloaded both the devboard-R2_01.tar.gz and devboard-R2_01-distfiles.tar.gz from http://www.axis.com/products/dev_sdk/download_dist.php. Extract the devboard-R2_01.tar.gz file. This will create a directory named devboard-R2_01. Then extract the devboard-distfiles-R2_01.tar.gz. This will create a folder named distfiles which contain all packages needed for the installation. Make a symbolic link inside the devboard-R2_01 folder pointing to this distfiles directory.

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

Install a basic selection of packages

Enter the newly created “devboard-R2_01” directory and run the install script. This will install tools and source code needed to configure the SDK in the next step.

First you will be confronted with a question if you would like to copy distribution files from an earlier SDK installation. Since you already copied the files when installing the second tarball answer “n” here.

At the end of the install script you will be asked which product to use. This selection determines which configuration files to be used. Select a product that resembles your hardware.

./install

Continue with the Configuration and building of the firmware chapter.

Configuration and building of the firmware

Configuration (Optional, but recommended)

To be able to control which packages to include, run any of the configuration targets (menuconfig, xconfig, config) to generate a custom configuration.

In most cases this is recommended to run these configuration targets since the default configuration only includes a subset of all available packages. Configure the SDK according to your needs or skip this step to use the default configuration.

make menuconfig 

or

make config

or

make xconfig

Install required packages

Install all packages needed for your configuration. This is performed by the configure script that also generates the top-level Makefile, used in the next step.

./configure

Build image

Now your SDK tree should be complete for your current configuration. To build the images run make.

make

For further guidance on how to work with your SDK, e.g., adding custom applications, consult the documentation page on http://developer.axis.com.

Update to SDK 2.01 from SDK 2.00

Caution :!:

This method overwrites some files. All changes made in any of the followings files will be lost:

  • configure
  • flashit
  • flashitall
  • install
  • kflash
  • ktest
  • All product specific configuration files: (<product>/defconfig, <product>/kernelkonfig, <product>/kernelkonfig-2.6)

Moreover, the update will relocate links pointing to files and directories. This implies that changes made in these files or directories will not be present in the new file or directory. However, the old files or directories will not be overwritten.

Download and unpack the new devboard file

Download and unpack the devboard-R2_01.tar.gz file.

tar -xfz devboard-R2_01.tar.gz

Copy new devboard files to SDK directory

Copy (or move) the files found in the devboard-R2_01 directory into the SDK directory you would like to upgrade.

cp devboard-R2_01/* <SDK directory>

Run the install script

Run the install script. This will download tools and source code needed to configure the SDK in the next step. When the script asks if you would like to copy distribution files answer no. At the end of the install script you will be asked which product to use. This selection determines which configuration files to be used. Select a product that resembles your hardware.

./install

Configuration (Optional)

Run the configure script with the -up (upgrade and pretend) option to produce a list of packages that would be upgraded in the case of running the configure script with the -u option. This can be valuable if you would like to know which packages an upgrade would affect.

./configure -up

Upgrade

Run the configure script with the -u option to upgrade all upgradeable packets.

./configure -u
 
axis/install-howto-2_01.txt · Last modified: 2011/05/20 07:52 by jesper
 
All text is available under the terms of the GNU Free Documentation License (see Copyrights for details).