|
|
Requirements
|
Instructions for meeting the basic requirements of different Linux distributionsIn the first step you have to install the GNU C cross-compiler for the CRIS processor architecture on your host machine.Red Hat Fedora Core 3 and 4Red Hat Fedora Core 3 and 4 have all the requirements in their basic installation. You just have to install the CRIS cross-compiler and pmake. Download these files:
su
Password: your_root_password rpm -U pmake-1.45-16.i386.rpm rpm -U cris-dist-1.63-1.i386.rpm Debian SargeDownload these files:
su
Password: your_root_password dpkg -i pmake_1.98-3_i386.deb dpkg -i cris-dist_1.63-1_i386.deb Linux Slackware 10.2 and 11.0Download these files:
su
Password: your_root_password installpkg pmake-1.45-i386-16fib.tgz installpkg cris-dist-1.63-1.i386-1fib.tgz Ubuntu 5.10 Breezy Badger - 6.06 Dapper Drake - 6.10 Edgy EftInstall these packages:
sudo apt-get install make
sudo apt-get install gcc sudo apt-get install libc6-dev sudo apt-get install libncurses5-dev sudo apt-get install zlib1g-dev sudo apt-get install flex sudo apt-get install bison Press Enter every time the following message appears: Do you want to continue [Y/n]? On Ubuntu 6.10 Edgy Eft the symbolic link /bin/sh points to /bin/dash instead of /bin/bash as in previous versions, so you might run into some errors when installing the SDK. To avoid these, enter:
sudo ln -sf /bin/bash /bin/sh
before using the SDK, and:
sudo ln -sf /bin/dash /bin/sh
to go back. Download these files:
sudo -s
Password: your_root_password dpkg -i pmake_1.98-3_i386.deb dpkg -i cris-dist_1.63-1_i386.deb WindowsThere is no SDK available that will run on Windows directly. But if you install the VMWare Player, you are able to run a virtual Linux on your Windows system.
The preconfigured sudo password on this installation is ubuntu. Download the tarballsThe tarball installation involves two tarballs (Tar-GZip archives) which the user has to extract. This method does not require an Internet connection on the computer intended for the installation, but you still need access to the tarballs. Create a new directory folder in your home directory, i.e. LB1
mkdir LB1
Download both devboard-R2_01.tar.gz and devboard-R2_01-distfiles.tar.gz and copy them to this new folder.
Unpack the devboard-R2_01.tar.gz file. Then unpack the devboard-R2_01-distfiles.tar.gz. This will create a work directory called devboard-R2_01 and a folder named distfiles-R2_01, which contain all packages required for installation. Then create a symbolic link called distfiles inside the devboard-R2_01 folder pointing to this distfiles-R2_01 directory.
tar xvfz devboard-R2_01.tar.gz
tar xvfz devboard-R2_01-distfiles.tar.gz cd devboard-R2_01 ln -s ../distfiles-R2_01 distfiles Run install scriptRun the Install script inside the newly created devboard-R2_01 directory. This will install tools and the source code required to configure the SDK in the next step.
./install
At the end of the Install script you will be asked which product you want to use. This selection determines the choice of configuration files to be used.
Alternatives:
1. devboard_82 - "Axis Developer Board 82/83" 2. devboard_82+ - "Axis Developer Board 82+/83+" 3. devboard_lx - "Axis Developer Board LX" 4. devboard_lx_ide - "Axis Developer Board LX IDE" 5. fox - "FOX BOARD by ACME systems (www.acmesystems.it) with MCM4+16" 6. lb1 - "LinuxBoard by ipcas GmbH (www.ipcas.de) with LX100" 7. mcm_2_8 - "Custom designs with MCM2+8, no additional memory" 8. mcm_4_16 - "Custom designs with MCM4+16, no additional memory" * Specify product (default: 6. lb1): Select product number 6 or press Enter. Configuration (optional)To be able to control the choice of packages to include, run any of the configuration targets (menuconfig, xconfig, config) to generate a custom configuration. In most cases it 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. You will always be able to change the configuration later on.
make menuconfig (or make config or make xconfig)
Install packagesInstall all packages required for your configuration. This is performed by the Configure script that also generates the top-level makefile, used in the next step. It is important to run configure after every modification of the configuration.
./configure
Create imageNow your SDK tree should be complete for your current configuration. To create the images, run make.
make
This will generate the firmware image called fimage.
During the make process you might be asked the following question: Write the "fimage" into the LinuxBoxThere are three ways to write the new fimage to the device:
Web updateThe default IP address of the device is 192.168.0.90. If you are in the same sub-net (or simply want to add a second IP address to your Ethernet adapter), you can access the web page of the LinuxBox there. If you are using a proxy server, make sure this address is excluded from proxy use. On the main page there is a link where you can upload our new image file. The upload section is password protected: The default user name is root, the password is pass.
FTP updateThe default IP address of the device is 192.168.0.90. If you are in the same sub-net (or simply want to add a second IP address to your Ethernet adapter), you can access the FTP server of the device there. There are two special files that enable the complete reprogramming of the flash memory. The two files are:
It is possible to use any FTP client to connect to the LinuxBox with the following credentials: username root and password pass.
$ ftp 192.168.0.90
Connected to 192.168.0.90 220 LinuxBoard by ipcas GmbH release 2.01 (Mar 01 2007) ready Name (192.168.0.90): root 331 User name okay, need password Password: pass 230 User logged in, proceed Remote system type is UNIX ftp> bin Using binary mode to transfer files ftp> put fimage flash_all local: fimage remote: flash_all 227 Entering Passive Mode (192,168,0,90,12,0) 150 Shutting down processes Preparing system for upgrade ... LAN update
This upload method requires the installation of the SDK. The LAN update is the only method that works even if there is no image or only a corrupt one in the LinuxBox. The tool that is used requires root rights, therefore, you should perform the update in a root terminal (e.g. through sudo -s). To rewrite the entire flash memory, enter:
cd ~/LB1/devboard-R2_01
. init_env boot_linux -f -i image_filename –d eth0
Please note that you have to insert a blank between . and init_env.
Using internal boot loader: INTERNAL_NW - Network boot (default).
Starting boot... We're doing a flash write, this may take up to a few minutes...
...
0x80360000: Writing 0x00010000 bytes 0x80370000: Writing 0x00010000 bytes 0x80380000: No need to write 0x80390000: No need to write 0x803a0000: Writing 0x00010000 bytes 0x80000000: Verifying...OK JUMP 0x00000000 END Exiting with code 0 To access the Reset and Load buttons, you have to remove the lid on the right side of the device. ![]() Changing kernel optionsTo change, add, or remove options from the Linux Kernel, run:
cd ~/LB1/devboard-R2_01
. init_env make menuconfig –C os/linux (or make config or make xconfig)
Subsequently, it is necessary to set the kernel configuration file in the device configuration. For this just run:
make menuconfig (or make config or make xconfig)
Select the menu General Configuration -> Kernel configuration file and type os/linux/.config. You need to do this only once. |
||||||||||




