Embest AM3517 Specifications download pdf (Page 55)

Page | 49

cp /media/cdrom/linux/tools/mkfs.ubifs /home/embest/tools

cp /media/cdrom/linux/tools/ubinize /home/embest/tools

cp /media/cdrom/linux/tools/ ubinize.cfg /home/embest/tools

4.5.3 Adding environment variable

After installation of the above tools, those tools can be added into

environment variable with the following command:

export PATH=/home/embest/arm-2009q1/bin:/home/embest/tools:$PATH

Note:

 Users can add this to the .barsrc file, allowing the environment variable to be

finished as the system starts.

4.5.4 System complation

Preparation

The source code of each part of the system is under the linux/source

directory of the CD. Users can copy it to the system and unzip it before

developing. For example:

mkdir /home/embest/work

cd /home/embest/work

tar xvf /media/cdrom/linux/source/ x-loader-03.00.00.04.tar.bz2

tar xvf /media/cdrom/linux/source/ u-boot-03.00.00.04.tar.bz2

tar xvf /media/cdrom/linux/source/ linux-03.00.00.04.tar.bz2

sudo tar xvf /media/cdrom/linux/source/rootfs.tar.bz2

When the above steps are finished, the current directory will contain the

three directories: linux-2.6.22-omap, u-boot-1.3.3 and x-load-1.41.

x-loader image generation

The DevKit8200 supports MMC/SD boot or NAND boot. The burned x-loader

image files are different for each different boot mode, and the corresponding

methods for mapping will differ too.

We will introduce the generation of x-loader image files under the different

boot modes.

1. To generate the x-loader image file MLO used for SD card

start-up

1 2 ... 50 51 52 53 54 55 56 57 58 59 60 ... 97 98

No comments

Embest AM3517 Specifications Page 55