
Installation Notes for Axis Developer Board/Device Server SDK
Release 2.01
     _________________________________________________________

   Table of Contents
   1. Introduction
   2. Requirements
   3. Installation process

        3.1. Automatic installation

              3.1.1. Unpack tar file
              3.1.2. Run install script
              3.1.3. Configuration (Optional, but recommended)
              3.1.4. Download and install packages
              3.1.5. Build image

        3.2. Tarball installation

              3.2.1. Download the tarballs
              3.2.2. Run install script
              3.2.3. Configuration (Optional, but recommended)
              3.2.4. Install packages
              3.2.5. Build image

   4. Update to SDK 2.01 from SDK 2.00

        4.1. Download and unpack the new devboard file
        4.2. Copy new devboard files to SDK directory
        4.3. Run the install script
        4.4. Configuration overview (Optional)
        4.5. Upgrade

1. Introduction

   This document describes how to install or upgrade the Axis
   Developer Board/Device server (SDK) to release 2.01. For more
   information about the development environment please visit
   http://developer.axis.com/doc/index.html.
     _________________________________________________________

2. 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
     * GNU wget
     * CRIS cross-compiler (Can be found in the download section
       on http://developer.axis.com).
     * 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
     _________________________________________________________

3. Installation process

   This software can be installed in two different ways,
   automatic installation and installation from a tarball.
     _________________________________________________________

3.1. Automatic installation

   Download the software from the developer site:
   http://developer.axis.com. An Internet connection is required
   on the computer intended for the installation.
     _________________________________________________________

3.1.1. Unpack tar file

   Download and unpack the devboard-R2_01.tar.gz file. The
   devboard-R2_01.tar.gz file contains basic scripts needed for
   installing the SDK.

"tar -xvfz devboard-R2_01.tar.gz"
     _________________________________________________________

3.1.2. Run install script

   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"
     _________________________________________________________

3.1.3. 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, it is recommended to configure the SDK 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")
     _________________________________________________________

3.1.4. Download and install packages

   Download and 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"
     _________________________________________________________

3.1.5. Build image

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

"make"
     _________________________________________________________

3.2. Tarball installation

   A tarball installation involves using two tarballs where the
   user has to extract these tarballs. This method does not
   require an Internet connection on the computed intended for
   the installation, but you still need access to the tarballs.
     _________________________________________________________

3.2.1. Download the tarballs

   Make sure that you have downloaded both devboard-R2_01.tar.gz
   and devboard-R2_01-distfiles.tar.gz. Unpack the
   devboard-R2_01.tar.gz file. Then unpack the
   devboard-distfiles-R2_01.tar.gz. This will create two
   directories named devboard-R2_01 and distfiles. The distfiles
   directory contains all packages needed for the installation.
   Then make a symbolic link inside the devboard-R2_01 folder
   pointing to this distfiles directory. By doing this the
   install procedure will find the required packages locally,
   consequently the packages does not have be fetched from
   http://developer.axis.com/download/distribution.

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

3.2.2. Run install script

   If you have not already entered the newly created
   "devboard-R2_01" directory do so, then 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 all the files you need (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"
     _________________________________________________________

3.2.3. 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, it is recommended to configure the SDK 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")
     _________________________________________________________

3.2.4. Install 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"
     _________________________________________________________

3.2.5. 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.
     _________________________________________________________

4. 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.
     _________________________________________________________

4.1. Download and unpack the new devboard file

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

"tar -xvfz devboard-R2_01.tar.gz"
     _________________________________________________________

4.2. 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>"
     _________________________________________________________

4.3. 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"
     _________________________________________________________

4.4. Configuration overview (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"
     _________________________________________________________

4.5. Upgrade

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

"./configure -u"
