ArmadeusWiki - User contributions [en]

Adeos

2008-06-05T23:02:44Z

FredericB: Added: how to select the kernel version

How to install Adeos on your board 
 
The purpose of Adeos is to provide a flexible environment for sharing hardware resources among multiple operating systems, or among multiple instances of a single OS.

 
==Get Adeos==

First create a working directory
$ cd armadeus
$ mkdir patches/adeos
$ cd patches/adeos

Adeos is provided as a linux kernel patch. Thus, you have to carefully select a patch matching the kernel version running on the board. 
On April 2008, the status was the following :
* Adeos patches was provided for the kernels
** 2.6.24
** 2.6.20
** 2.6.19
* Kernels ported for the board:
** 2.6.24
** 2.6.23
** 2.6.23.18

The latest kernel matching is the 2.6.24.
So you have to make sure this kernel will be run on the board. 
To do this, at the root of the armadeus project :
$ make menuconfig

Then select :
Target options > Armadeus Device Support > Linux > Linux kernel version

Download the adeos patch from [http://download.gna.org/adeos/patches/v2.6/arm/ this page].

For instance :
$ wget http://download.gna.org/adeos/patches/v2.6/arm/adeos-ipipe-2.6.24-arm-1.9-01.patch

==Install Adeos==

Go to the linux kernel directory

$ cd ../../..
$ cd armadeus/buildroot/build_arm/linux-2.6.XX.YY

And apply the patch with the ''-p1'' option.

$ patch -p1 < ../../../patches/adeos/adeos-ipipe-2.6.XX-arm-1.9-01.patch

Now, let's see if everything went fine. Run the command:
$ find . -name '*.rej'
If you get any results, it means that some errors occurred while trying to patch. In a such case,
you will have to apply the changes manually. 
These pages can help you to do the job:
* [http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html]
* [http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html] (''French'')

==Configure Adeos==

Adeos is now installed, let's configure it a bit.

In the kernel directory, run the command
$ make menuconfig

And select the following options

Kernel Features --->
[*] Interrupt Pipeline
(4) Max domains
[ ] Maintain code compatibility with older releases

Optionally, you can also enable ipipe debugging

Kernel hacking --->
[*] I-pipe debugging
[*] Check for illicit cross-domain calls (NEW)
[*] Latency tracing
[*] Enable tracing on boot (NEW)
[*] Instrument function entries (NEW)
[*] Trace IRQs-off times (NEW)
(14) Depth of trace log (14 => 16Kpoints, 15 => 32Kpoints) (NEW)
[*] Use vmalloc'ed trace buffer (NEW)
[*] Enable panic back traces (NEW)

Well, it's now time for compilation !

$ cd ../../../..
$ cd armadeus
$ make

Then check that your kernel size is lower than 1.5 Mb
$ ls -lh buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin
-rw-r--r-- 1 creber users 1.4M 2008-04-05 23:29 buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin

If the test is OK, you're ready to [[Target_Software_Installation | transfer ]] the kernel to the board.

==Test==

To validate your Adeos installation, boot the target an run the command

dmesg | grep I-pipe

You should get an output similar to :

I-pipe 1.9-01: pipeline enabled.

==Links==
* A page describing how to use the ipipe tracer option. [http://www.xenomai.org/index.php/I-pipe:Tracer http://www.xenomai.org/index.php/I-pipe:Tracer]

[[Category:Software]]
[[Category:Virtualization]]
[[Category:Real-Time]]

Xenomai

2008-06-04T23:48:24Z

FredericB: Page creation. This is a draft. I submit the page now since few guys need to progress on the Xenomai side.

'''Under Construction''' [[Image:Construction.png]]

 How to manually install Xenomai on your board 
 
 
 
 

==What is Xenomai==

Xenomai is a real time co-kernel which cooperate with Linux via Adeos. 
Hard real time applications can be developped and run on the Armadeus
board. Thanks to Adeos, Xenomai will receive the interrupts first and decide
to handle them or not. If not, they will then be transfered to the regular
Linux kernel. Also, Xenomai provides a framework to develop applications which
can be easily moved between the Real Time Xenomai environment and the regular
Linux system. Moreover, Xeno provides a set of APIs (called "skins") that
emulate traditional RTOSes such as VxWorks and pSOS and implement other APIs
such as POSIX. Thus, porting third party real time applications to Xenomai is
a fairly simple process.

==Explanation of the process used to install & deploy xenomai==

Because Xenomai has not (''yet'') been integrated into the project, we will
have to install it manually.

The main steps are
* Installation of Adeos, an interupt pipeline
* Create the Xenomai project directories used for this tutorial
* Download Xenomai, extract & patch the sources
* Prepare the Armadeus linux kernel to support Xenomai
* Compile Xenomai
* Deploy user space Xenomai applications into the target root file system
* Validate the installation

Namming conventions :
In this document, the following naming conventions will be applied :

* Xeno or xeno will be used to reference Xenomai
* $ARMASEUS_ROOT will be used to reference the root directory of the xenomai project

==Install Adeos==

First of all, you need to deploy a working Adeos on your board.
This can easily be done by following [[Adeos | these instructions]].

==Create our Xenomai project folder architecture==

Xenomai will create some files to be deployed. By default, the command
''make install'' will copy the files into the following directories :
* ''/usr/xenomai/*'' contain test programs, includes, ...
* ''/usr/share/xenomai/*'' contain the documentation.

To have a clean but integrated folder architecture, we will create some specific
directories to install theses files. Later, we will copy them into the board's
root filesystem so Xenomai testing programs will be available on the apf.

Also, because Xenomai documentation installed is quite huge (several Mb), we
will avoid to copy it on the board.

$ mkdir $ARMADEUS_ROOT/xenomai
$ mkdir $ARMADEUS_ROOT/xenomai/root_dir
$ mkdir $ARMADEUS_ROOT/xenomai/root_dir/xenodoc

''$ARMADEUS_ROOT/xenomai/root_dir/usr'' will contain all Xenomai target specific
files. This directory will be transfered to the board.

''$ARMADEUS_ROOT/xenomai/root_dir/xenodoc'' will contain Xenomai documentation
that won't be transfered to the board.

==Download & patch==

Well, let's start by downloading Xenomai sources.

$ cd $ARMADEUS_ROOT/xenomai
$ wget http://download.gna.org/xenomai/stable/xenomai-2.4.3.tar.bz2
$ tar xvjf xenomai-2.4.3.tar.bz2

To compile Xenomai-2.4.3 with the current uClibc used within the Armadeus project
(uClibc-0.9.29), we will have to patch :
* Xenomai sources (See [[https://mail.gna.org/public/xenomai-help/2008-03/msg00043.html | here]])
* uClibc sources (See [[http://sourceforge.net/mailarchive/forum.php?thread_name=4803E169.30708%40free.fr&forum_name=armadeus-forum | this thread]])

To patch Xenomai sources :

$ cd $ARMADEUS_ROOT/xenomai/xenomai-2.4.3
$ wget https://mail.gna.org/public/xenomai-help/2008-03/bin5IoYobpAwu.bin
$ patch -p0 < bin5IoYobpAwu.bin
patching file src/skins/posix/thread.c

To patch uClibc : 
This patch has been inserted into the Armadeus project, starting from revision
799. Update your svn tree to make sure it will be applied.

==Compilation==

===Xenomai kernel space support===

Xenomai is a co-kernel cooperating with Linux. This suite is made of two parts :
* The Xenomai kernel: It is provided as a patch to the regular Linux kernel and
can be compiled as a full part of the kernel or as a regular module.
* Xenomai user space data: This set of file contains:
** header files used to compile Xenomai applications
** Binary files to validate and measure the performace of Xenomai

This section describe how to compile the kernel space for Xenomai.

Here we will patch the Armadeus linux kernel to add Xenomai features.
This is automatically done via the Xenomai script ''prepare-kernel.sh''

$ cd $ARMADEUS_ROOT/xenomai/xenomai-2.4.3
$ ./scripts/prepare-kernel.sh --linux=$ARMADEUS_ROOT/buildroot/build_arm/linux-2.6.24.3/ --arch=arm

* ''--linux'' is used to specify which kernel we want to patch
* ''--arch'' is used to specify for which platform we want to patch (arm in our case)

Let's configure the Xenomai kernel :

cd $ARMADEUS_ROOT
$ make linux-menuconfig

You should see the new entry :
Real-time sub-system --->

Enter in it and check the following to compile Xenomai as a part of the Linux
kernel :
[*] Xenomai
<*> Nucleus
[*] Pervasive real-time support in user-space
[ ] Interrupt shield support
[*] Priority coupling support
[*] Optimize as pipeline head
(32) Number of pipe devices
(512) Number of registry slots
(128) Size of the system heap (Kb)
(32) Size of the private stack pool (Kb)
[*] Statistics collection
[ ] Debug support
[ ] Shared interrupts
Timing --->
Scalability --->
Machine --->
Interfaces --->
Drivers --->

Additionaly, to enable / disable the different available skins, go into "''Interfaces --->''" :
<*> Native API --->
<*> POSIX API --->
< > pSOS+ emulator --->
< > uITRON API --->
< > VRTX emulator --->
< > VxWorks emulator --->
< > RTAI emulator --->
<*> Real-Time Driver Model --->

Finally, compile Xenomai :
$ make

===Xenomai User Space support===

Because we need to cross compile Xenomai applications for ARM, we will use the
cross compilations tools provided by Armadeus/buildroot. 

Let's update our PATH accordingly :
$ export PATH=$ARMADEUS_ROOT/buildroot/build_arm/staging_dir/bin:$PATH

We are now ready to start the user space compilation.

First, let's configure Xeno and create the makefiles :
$ cd $ARMADEUS_ROOT/xenomai/xenomai-2.4.3
$ ./configure --enable-arm-mach=imx --host=arm-linux --datarootdir=/xenodoc

* ''--enable-arm-mach'' : We want to build Xeno for the ARM Imx architecture
* ''--host'' : Prefix used for all compilation tools
* ''--datarootdir'' :

Finally, compile user space utilities.
$ make

==Deploy==

First, install xenomai data in $ARMADEUS_ROOT/xenomai/root-dirs/target
$ cd $ARMADEUS_ROOT/xenomai/xenomai-2.4.3
$ make DESTDIR=$ARMADEUS_ROOT/xenomai/root-dir install

This command will install all Xenomai data in $ARMADEUS_ROOT/xenomai/root-dir.
Have a look in this directory. Note that it contains two sub directories,
''xenodoc'' and ''usr''. ''xenodoc'' contains all documentation regarding
Xenomai. As said previously, we will not copy xenodoc on the board.
Instead, we will only transfert the required files to run Xeno applications
on the apf. These files are located under ''usr/xenomai''.

Before modifying the board's root filesystem, we will first make a backup of it.
$ cp -R $ARMADEUS_ROOT/buildroot/project_build_arm/armadeus/root $ARMADEUS_ROOT/buildroot/project_build_arm/armadeus/root.orig

We can now copy Xeno data to the board's root filesystem:
$ cp -R $ARMADEUS_ROOT/xenomai/root-dir/usr/* $ARMADEUS_ROOT/buildroot/project_build_arm/armadeus/root/usr/

And generate the target filesystem
$ cd $ARMADEUS_ROOT
$ make

You can now [[Target_Software_Installation | transfer]] the rootfs and the kernel
on the apf.

==Validate the installation==

Boot the apf and logon as root. 

You can double check Xeno is installed correctly :

$ dmesg | grep Xenomai
I-pipe: Domain Xenomai registered.
Xenomai: hal/arm started.
Xenomai: real-time nucleus v2.4.3 (Back to Shalla-Bal) loaded.
Xenomai: starting native API services.
Xenomai: starting POSIX services.
Xenomai: starting RTDM services.

We will now update our environment to add xenomai features. On the apf,
run the following commands:
$ export LD_LIBRARY_PATH=/usr/xenomai/lib:$LD_LIBRARY_PATH
$ export PATH=/usr/xenomai/bin:$PATH

to make the change permanentrly, add to /usr/xenomai/lib $ARMADEUS_ROOT/buildroot/project_build_arm/armadeus/root/etc/ld.so.conf

So we can run the performance test provided by Xenomai:
$ xeno-test

==Links==
* [http://www.xenomai.org] Xenomai main page

[[Category:Software]]
[[Category:Real-Time]]

Adeos

2008-04-07T21:27:00Z

FredericB: removing Xenomai references in the Test section (xenomai should be installed at this stage)

How to install Adeos on your board 
 
The purpose of Adeos is to provide a flexible environment for sharing hardware resources among multiple operating systems, or among multiple instances of a single OS.

 
==Get Adeos==

First create a working directory
$ cd armadeus
$ mkdir patches/adeos
$ cd patches/adeos

Adeos is provided as a linux kernel patch. Thus, you have to carefully select a patch matching the kernel version running on the board. 
On April 2008, the status was the following :
* Adeos patches was provided for the kernels
** 2.6.24
** 2.6.20
** 2.6.19
* Kernels ported for the board:
** 2.6.24
** 2.6.23
** 2.6.23.18

The latest kernel matching is the 2.6.24.
So you have to make sure this kernel will be run on the board. 
Then download the adeos patch from [http://download.gna.org/adeos/patches/v2.6/arm/ this page].

For instance :
$ wget http://download.gna.org/adeos/patches/v2.6/arm/adeos-ipipe-2.6.24-arm-1.9-01.patch

==Install Adeos==

Go to the linux kernel directory

$ cd ../../..
$ cd armadeus/buildroot/build_arm/linux-2.6.XX.YY

And apply the patch with the ''-p1'' option.

$ patch -p1 < ../../../patches/adeos/adeos-ipipe-2.6.XX-arm-1.9-01.patch

Now, let's see if everything went fine. Run the command:
$ find . -name '*.rej'
If you get any results, it means that some errors occurred while trying to patch. In a such case,
you will have to apply the changes manually. 
These pages can help you to do the job:
* [http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html]
* [http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html] (''French'')

==Configure Adeos==

Adeos is now installed, let's configure it a bit.

In the kernel directory, run the command
$ make menuconfig

And select the following options

Kernel Features --->
[*] Interrupt Pipeline
(4) Max domains
[ ] Maintain code compatibility with older releases

Optionally, you can also enable ipipe debugging

Kernel hacking --->
[*] I-pipe debugging
[*] Check for illicit cross-domain calls (NEW)
[*] Latency tracing
[*] Enable tracing on boot (NEW)
[*] Instrument function entries (NEW)
[*] Trace IRQs-off times (NEW)
(14) Depth of trace log (14 => 16Kpoints, 15 => 32Kpoints) (NEW)
[*] Use vmalloc'ed trace buffer (NEW)
[*] Enable panic back traces (NEW)

Well, it's now time for compilation !

$ cd ../../../..
$ cd armadeus
$ make

Then check that your kernel size is lower than 1.5 Mb
$ ls -lh buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin
-rw-r--r-- 1 creber users 1.4M 2008-04-05 23:29 buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin

If the test is OK, you're ready to [[Target_Software_Installation | transfer ]] the kernel to the board.

==Test==

To validate your Adeos installation, boot the target an run the command

dmesg | grep I-pipe

You should get an output similar to :

I-pipe 1.9-01: pipeline enabled.

==Links==
* A page describing how to use the ipipe tracer option. [http://www.xenomai.org/index.php/I-pipe:Tracer http://www.xenomai.org/index.php/I-pipe:Tracer]

[[Category:Software]]
[[Category:Virtualization]]
[[Category:Real-Time]]

MemberList

2008-04-07T21:14:21Z

FredericB:

==Here is the list of the (active) members and their skills==

This list is maintained by the users themself.

*0: Novice
*1: Notions. At least one successfull experiment
*2: Confirmed
 

{| border="1" cellpadding="5" cellspacing="0" summary="Signal connections"
|- style="background:#efefef;"
! '''Name / IRC Nickname''' || '''Linux Apps'''|| '''Linux Drivers'''|| '''FPGA''' || '''Board Design''' || '''Projet/Domain'''
|----------------
|[[User:Salocin68|Nicolas Colombain / Salocin]] || 1 || 1 || 1 || 2 || domotics
|----------------
|[[User:JulienB|Julien Boibessot / Artemys]] || 2 || 2 || 0 || 1 || multimedia
|----------------
|[[User:JeanBaptisteM|Jean-Baptiste Mayer / JiBee]] || 2 || 1 || 1 || 1 || robotics
|----------------
|[[User:NicolasA|Nicolas Aguirre]] || 2 || 0 || 1 || 1 || multimedia
|----------------
|[[User:BenoitC|Benoît Canet]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:SonZerro|Sonzerro]] || 0 || 0 || 1 || 2 || domotics
|----------------
|[[User:HenriG|Henri Geist]] || 1 || 1 || 0 || 1 || robotics
|----------------
|[[User:BorredonB|Bernard Borredon]] || 2 || 1 || 0 || 1 || domotics
|----------------
|[[User:ThomasB|Thomas Bores]] || 2 || 0 || 0 || 1 || Entertainment
|----------------
|[[User:FabriceM|Fabrice Mousset / KroMignon]] || 1 || 1 || 2 || 1 || Domotics & multimedia
|----------------
|[[User:AmineH|Amine EL HEDADI]] || 2 || 2 || 0 || 0 || domotics & robotics
|----------------
|[[User:PhilippeM|Philippe Monteil]] || 2 || 0 || 0 || 0 || multimedia
|----------------
|[[User:CedricZ|Cédric Zmyj]] || 0 || 0 || 0 || 0 || domotics & robotics
|----------------
|[[User:JeanMichelN|Jean Michel Naimo / jeanmi12 ]] || 2 || 1 || 1 || 1 || Domotics & entertainment
|----------------
|[[User:OlivierC|Olivier Coutanceau]] || 1 || 0 || 0 || 0 || multimedia
|----------------
|[[User:ArnaudC|Arnaud COFFINET]] || 0 || 0 || 1 || 2 || multimedia & domotics
|----------------
|[[User:SylvainP|Sylvain PARRINO]] || 2 || 1 || 0 || 0 || robotics
|----------------
|[[User:AurelienH|Aurélien HIRON]] || 2 || 0 || 0 || 1 || robotics
|----------------
|[[User:GuillaumeT|Guillaume TRANNOY]] || 0 || 0 || 0 || 2 || domotics & robotics
|----------------
|[[User:JulienN|Julien NICOLAS / jujun]] || 2 || 1 || 0 || 1 || multimedia & network
|----------------
|[[User:StephaneF|Stéphane Falck]] || 0 || 0 || 0 || 0 || multimedia & robotics & domotics
|----------------
|[[User:GillesD|Gilles DUSSIN/ Sellig]] || 1 || 0 || 1 || 1 || robotics
|----------------
|[[User:MaximeL|Maxime Liron]] || 0 || 0 || 0 || 0 || domotics, robotics & multimedia
|----------------
|[[User:NicolasC|Nicolas CHARLERY/ realniko]] || 2 || 0 || 0 || 0 || electronic
|----------------
|[[User:BenoitJ|Benoit JESTER]] || 0 || 0 || 0 || 0 || robotics
|----------------
|[[User:FabienM|Fabien MARTEAU/ FabM]] || 1 || 1 || 1 || 1 || robotics,domotics
|----------------
|[[User:XavierA|Xavier AZNAR]] || 1 || 1 || 0 || 0 || environment, entertainment, domotic
|----------------
|[[User:AlbericA|Albéric AUBLANC / PoueT]] || 2 || 0 || 1 || 0 || domotics & multimedia, robotics, entertainment,
|----------------
|[[User:FredericB| Frédéric Blain / creber]] || 2 || 1 || 0 || 0 || system, domotics
|----------------
|}

==Links==
* [[Members | Geographical position of the members]]

[[Category:Association]]

User:FredericB

2008-04-07T16:51:57Z

FredericB: Page Creation

Salut,

Je suis Frédéric Blain, 25 ans, habitant en région parisienne. 
Je travail dans le domaine de l'informatique embarqué depuis peu et je me suis inscrit à l'association
principalement dans un but pédagogique. Ainsi, je souhaite me familiariser avec Linux en embarqué
et jouer avec les diverses possibilités offertes par la carte (I/O, touchscreen, ...)

Sur [[ArmadeusWiki:Community_Portal | IRC]], vous pouvez me contacter sous le pseudonyme creber.

Talk:Adeos

2008-04-07T11:30:33Z

FredericB: Reply to JulienB

Merci FredericB pour avoir créé cette page ! 
Si tu veux que les patches kernel s'applique automatiquement, tu peux aussi les mettre dans:
buildroot/target/device/armadeus/linux/kernel-patches/2.6.24.3/

----

Salut Julien 
Merci pour l'info ! 
Pour le moment je travaille sur l'integration de xenomai sur l'apf. 
Mon but est de comprendre comment tout cela fonctionne (Je débute complétement sur le sujet)
et de documenter le tout sur le wiki. 
Une fois que je serais arrivé à un résultat concluant, on pourra peut etre essayer
d'intégrer Adeos + Xenomai dans le projet Armadeus (Avec une option dans make menuconfig)
(Il est probable que je demande ton aide pour ca d'ailleur)

Adeos

2008-04-07T06:36:03Z

FredericB: Grammar correction

How to install Adeos on your board 

 
==Get Adeos==

First create a working directory
$ cd armadeus
$ mkdir patches/adeos
$ cd patches/adeos

Adeos is provided as a linux kernel patch. Thus, you have to carefully select a patch matching the kernel version running on the board. 
On April 2008, the status was the following :
* Adeos patches was provided for the kernels
** 2.6.24
** 2.6.20
** 2.6.19
* Kernels ported for the board:
** 2.6.24
** 2.6.23
** 2.6.23.18

The latest kernel matching is the 2.6.24.
So you have to make sure this kernel will be run on the board. 
Then download the adeos patch from [http://download.gna.org/adeos/patches/v2.6/arm/ this page].

For instance :
$ wget http://download.gna.org/adeos/patches/v2.6/arm/adeos-ipipe-2.6.24-arm-1.9-01.patch

==Install Adeos==

Go to the linux kernel directory

$ cd ../../..
$ cd armadeus/buildroot/build_arm/linux-2.6.XX.YY

And apply the patch with the ''-p1'' option.

$ patch -p1 < ../../../patches/adeos/adeos-ipipe-2.6.XX-arm-1.9-01.patch

Now, let's see if everything went fine. Run the command:
$ find . -name '*.rej'
If you get any results, it means that some errors occurred while trying to patch. In a such case,
you will have to apply the changes manually. 
These pages can help you to do the job:
* [http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html]
* [http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html] (''French'')

==Configure Adeos==

Adeos is now installed, let's configure it a bit.

In the kernel directory, run the command
$ make menuconfig

And select the following options

Kernel Features --->
[*] Interrupt Pipeline
(4) Max domains
[ ] Maintain code compatibility with older releases

Optionally, you can also enable ipipe debugging

Kernel hacking --->
[*] I-pipe debugging
[*] Check for illicit cross-domain calls (NEW)
[*] Latency tracing
[*] Enable tracing on boot (NEW)
[*] Instrument function entries (NEW)
[*] Trace IRQs-off times (NEW)
(14) Depth of trace log (14 => 16Kpoints, 15 => 32Kpoints) (NEW)
[*] Use vmalloc'ed trace buffer (NEW)
[*] Enable panic back traces (NEW)

Well, it's now time for compilation !

$ cd ../../../..
$ cd armadeus
$ make

Then check that your kernel size is lower than 1.5 Mb
$ ls -lh buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin
-rw-r--r-- 1 creber users 1.4M 2008-04-05 23:29 buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin

If the test is OK, you're to [[Target_Software_Installation | transfer ]] the kernel to the board.

==Tets==

To validate your Adeos installation, boot the target an run the command

dmesg | grep I-pipe

You should get an output similar to :

I-pipe 1.9-01: pipeline enabled.
I-pipe: Domain Xenomai registered.

==Links==
* A page describing how to use the ipipe tracer option. [http://www.xenomai.org/index.php/I-pipe:Tracer http://www.xenomai.org/index.php/I-pipe:Tracer]

[[Category:Software]]
[[Category:Real-Time]]

Adeos

2008-04-06T22:45:36Z

FredericB: Adding Testing section + minor changes

How to install Adeos on your board 

 
==Get Adeos==

First create a working directory
$ cd armadeus
$ mkdir patches/adeos
$ cd patches/adeos

Adeos is provided as a linux kernel patch. Thus, you have to carefully select a patch matching the kernel version running on the board. 
On April 2008, the status was the following :
* Adeos patches was provided for the kernels
** 2.6.24
** 2.6.20
** 2.6.19
* Kernels ported for the board:
** 2.6.24
** 2.6.23
** 2.6.23.18

The latest kernel matching is the 2.6.24.
So you have to make sure this kernel will be run on the board. 
Then download the adeos patch from [http://download.gna.org/adeos/patches/v2.6/arm/ this page].

For instance :
$ wget http://download.gna.org/adeos/patches/v2.6/arm/adeos-ipipe-2.6.24-arm-1.9-01.patch

==Install Adeos==

Go to the linux kernel directory

$ cd ../../..
$ cd armadeus/buildroot/build_arm/linux-2.6.XX.YY

And apply the patch with the ''-p1'' option.

$ patch -p1 < ../../../patches/adeos/adeos-ipipe-2.6.XX-arm-1.9-01.patch

Now, let's see if everything went fine. Run the command:
$ find . -name '*.rej'
If you get any results, it means that some errors occurred while trying to patch. In a such case,
you will have to apply the changes manually. 
These pages can help you to do the job:
* [http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html]
* [http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html] (''French'')

==Configure Adeos==

Adeos is now installed, let's configure it a bit.

In the kernel directory, run the command
$ make menuconfig

And select the following options

Kernel Features --->
[*] Interrupt Pipeline
(4) Max domains
[ ] Maintain code compatibility with older releases

Optionally, you can also enable ipipe debugging

Kernel hacking --->
[*] I-pipe debugging
[*] Check for illicit cross-domain calls (NEW)
[*] Latency tracing
[*] Enable tracing on boot (NEW)
[*] Instrument function entries (NEW)
[*] Trace IRQs-off times (NEW)
(14) Depth of trace log (14 => 16Kpoints, 15 => 32Kpoints) (NEW)
[*] Use vmalloc'ed trace buffer (NEW)
[*] Enable panic back traces (NEW)

Well, it's now time for compilation !

$ cd ../../../..
$ cd armadeus
$ make

Then check that your kernel size is lower than 1.5 Mb
$ ls -lh buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin
-rw-r--r-- 1 creber users 1.4M 2008-04-05 23:29 buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin

If the test is OK, you're to [[Target_Software_Installation | transfer ]] the kernel to the board.

==Tets==

To validate your Adeos installation, boot the on target an run the command

dmesg | grep I-pipe

You should get an output similar to :

I-pipe 1.9-01: pipeline enabled.
I-pipe: Domain Xenomai registered.

==Links==
* A page describing how to use the ipipe tracer option. [http://www.xenomai.org/index.php/I-pipe:Tracer http://www.xenomai.org/index.php/I-pipe:Tracer]

[[Category:Software]]
[[Category:Real-Time]]

Setup

2008-04-06T00:20:21Z

FredericB: Adding Adeos entry

On this page, you will find all the usefull informations you need to configure your Armadeus board for optimum usage.

==First StartUp==
Just got your Armadeus board and want to start playing with it ? So follow this quick list to setup your environment accordingly: 
*1. Connect your APF to your custom development board or to your DevLight ( This will be further refered to "the Target") --->> [[Image:Apf_on_devlight.png]] 
*2. Connect your PC (= the Host) to your development system with a null-modem RS232 cable 
*3. Connect the power supply on your system ('''+5Vdc on a Devlight. + is in the middle of the connector, - on the side''') 
*4. [[Communicate | Establish the communication between your Host and your APF]] 
*5. Verify your APF by starting Linux: In U-Boot console, type "boot". Several informations will be displayed on your terminal like on this [[Linux start screenshot | screenshot ]] 
*6. If Linux has successfully started, you can proceed with the toolchain installation. See Basics below 

==Basics==
* [[Toolchain]]: How to install the development environment for the Armadeus boards
* [[Communicate]]: How to communicate with your board from the Host
* [[Target Software Installation]]: How to install U-Boot, Linux and your Rootfs on your board

==Intermediate==
* [[Network Configuration]]: how to configure Host and Target network (NFS, TFTP)
* [[Serial Transfer]]: how to transfer files between your Host and your Armadeus board with the RS232 link (if you don't have Ethernet)
* [[MultiMediaCard]]: how to use MMC/SD cards on Linux with your Armadeus board

 TO BE REMOVED FROM THIS PAGE:
* [[FrameBuffer]]: how to configure and use the framebuffer for new LCDs
* [[BackLight| How to control the backlight of you graphical LCD (if it supports it)]]
* [[GPIO Driver]]: how to configure the GPIO driver
* [[Boa]]: How install and configure the boa Web server on your board
* [[USB Gadget]]: how to configure your Armadeus board to use it as a USB device (aka Gadget in Linux language)
* [[DAC|Digital to Analog Convertion]]: how to configure and use the DAC on your board
* [[ADC max1027|Analog to Digital Converter]]: how to install and use the on board ADC (max1027)
* [[PWM]]: how to use the i.MX integrated PWM
* [[RTC]]: how to use an external Real Time Clock (Maxim DS1374)
* [[Watchdog]]: how to configure and use the i.MX integrated Watchdog
* [[TV Output]]: How to use the SVideo output of the APF9328DevFull
* [[USB Host]]: How to use the ISP176x USB Host controller of the APF9328DevFull
* [[TSC2102 Linux driver| TSC2102 Linux driver details ]]: How to configure and use the touchscreen controller
* [[Adeos]]: How to install Adeos on your board

==Advanced==
* [[BootLoader]]: (U-Boot useful tips)
* [[BootStrap]]: Install U-Boot from scratch or recover your U-Boot if it was corrupted

[[Image:FrenchFlag.png]][[Configuration| Cette page en Français]]

Adeos

2008-04-06T00:16:24Z

FredericB: Page creation

How install Adeos on your board 

 
==Get Adeos==

First create a working directory
$ cd armadeus
$ mkdir patches/adeos
$ cd patches/adeos

Adeos is provided as a linux kernel patch. Thus, you have to carefully select a patch matching the kernel version running on the board. 
On April 2008, the status was the following :
* Adeos patches was provided for the kernels
** 2.6.24
** 2.6.20
** 2.6.19
* Kernels ported for the board:
** 2.6.24
** 2.6.23
** 2.6.23.18

The latest kernel matching is the 2.6.24.
So you have to make sure this kernel will be run on the board. 
Then download the adeos patch from [http://download.gna.org/adeos/patches/v2.6/arm/ this page].

For instance :
$ wget http://download.gna.org/adeos/patches/v2.6/arm/adeos-ipipe-2.6.24-arm-1.9-01.patch

==Install Adeos==

Go to the linux kernel directory

$ cd ../../..
$ cd armadeus/buildroot/build_arm/linux-2.6.XX.YY

And apply the patch with the ''-p1'' option.

$ patch -p1 < ../../../patches/adeos/adeos-ipipe-2.6.XX-arm-1.9-01.patch

Now, let's see if everything went fine. Run the command:
$ find . -name '*.rej'
If you get any results, it means that some errors occured while trying to patch. In a such case,
you will have to apply the changes manually. 
These pages can help you:
* [http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-6.html]
* [http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html http://www.tuxfinder.com/french/HOWTOhtml/Kernel-HOWTO-5.html] (''French'')

==Configure Adeos==

Adeos is now install, let's configure it a bit.

In the kernel directory, run the command
$ make menuconfig

And select the following options

Kernel Features --->
[*] Interrupt Pipeline
(4) Max domains
[ ] Maintain code compatibility with older releases

Optionally, you can also enable ipipe debugging

Kernel hacking --->
[*] I-pipe debugging
[*] Check for illicit cross-domain calls (NEW)
[*] Latency tracing
[*] Enable tracing on boot (NEW)
[*] Instrument function entries (NEW)
[*] Trace IRQs-off times (NEW)
(14) Depth of trace log (14 => 16Kpoints, 15 => 32Kpoints) (NEW)
[*] Use vmalloc'ed trace buffer (NEW)
[*] Enable panic back traces (NEW)

Well, it's now time for compilation !

$ cd ../../../..
$ cd armadeus
$ make

Then check that your kernel size is lower than 1.5 Mb
$ ls -lh buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin
-rw-r--r-- 1 creber users 1.4M 2008-04-05 23:29 buildroot/binaries/armadeus/linux-kernel-2.6.XX.Y-arm.bin

And [[Target_Software_Installation | Transfer ]] the kernel to the board.

==Links==
* A page describing how to use the ipipe tracer option. [http://www.xenomai.org/index.php/I-pipe:Tracer http://www.xenomai.org/index.php/I-pipe:Tracer]

Boa

2008-03-31T21:14:47Z

FredericB: Reflect the new location for boa in "make menuconfig"

How install and configure the boa Web server on your board 

[[Image:boa.png|right]]
 
==Install==

$ cd armadeus
$ make menuconfig

* Select: ''Package Selection for the Target -> Networking -> Boa''
* Save the configuration

Then we can create the binaries and the default filesystem. This will be usefull
later to perform the configuration :

$ make

 
==Configure==

=== Generalities ===

To apply a permanent configuration, be sure to not change anything on the board filesystem. 
That would be erased the next time you flash the fs. Instead, do all changes on the filesystem
located on the host, i.e. on ''buildroot/project_build_arm/armadeus/root/''

The boa configuration file is located in ''/etc/boa/boa.conf'' on the card 
This means that to permanently change the configuration, you need to edit the file
''buildroot/project_build_arm/armadeus/root/etc/boa/boa.conf'' '''on the host'''

=== Create a Dummy page ===

By default, DocumentRoot is set to /var/www, so let's add a dummy file here to test
our configuration :

$ mkdir buildroot/project_build_arm/armadeus/root/var/www
$ vi buildroot/project_build_arm/armadeus/root/var/www/index.html

And fill the file with :

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
</body>
</html>

=== Enable hostname resolution ===

Boa has to be able to resolve the hostname to work, so let's do :

$ echo "127.0.0.1 `cat buildroot/project_build_arm/armadeus/root/etc/hostname`" >> buildroot/project_build_arm/armadeus/root/etc/hosts

=== Create the access log directory ===

By default, boa logs will be stored in /var/log/boa/ on the card.
If you did not change this setting, you will need to perform the following :

$ls -l buildroot/project_build_arm/armadeus/root/var/log/

If this is a link to /tmp, then

$ rm -f buildroot/project_build_arm/armadeus/root/var/log/ && mkdir buildroot/project_build_arm/armadeus/root/var/log/

Then, create the boa directory :
$ mkdir buildroot/project_build_arm/armadeus/root/var/log/boa

 

-----
Why shoud I delete the symbolink link ? 
This is because during the filesystem creation, mkfs.jffs2 will keep the link from ''/var/log'' to ''/tmp'' on the board.
Thus, once on the board, you will have :

# ls -l /var/log
lrwxrwxrwx 1 root root 4 Apr 15 2007 /var/log -> /tmp

With a such behavior, even if you fill the directory ''buildroot/project_build_arm/armadeus/root/var/log/'' on your host
(which actually fill /tmp on your host), nothing will be saved once the filesystem will be flashed on your board.

 
 

== Test the result ==

Create the final rootfs :

$ make

Then [[Target_Software_Installation | update the rootfs]] on your board. 

And start boa

$ boa

To access to your web page, use a browser:
http://''<your IP Address>''/

You sould see the page ! 
If not, check the file ''/var/log/boa/error_log'' on your board

 
 

== Working with cgi ==

First, check the boa.conf file. 
Once more, you should use the one located on your host before changing anything.

$ vi buildroot/project_build_arm/armadeus/root/etc/boa/boa.conf

Be sure to have an uncommented line like this :

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/

Now; let's write a dummy cgi :

$ mkdir buildroot/project_build_arm/armadeus/root/usr/lib/cgi-bin
$ vi buildroot/project_build_arm/armadeus/root/usr/lib/cgi-bin/get_ipconfig.sh

And add the following :

#!/bin/sh
echo -e "Content-type: text/html\r\n\r\n";
echo -e `/sbin/ifconfig eth0 | grep 'inet addr'`;

The script have to be executable:

$ chmod a+x buildroot/project_build_arm/armadeus/root/usr/lib/cgi-bin/get_ipconfig.sh

Then change your index.html page to add a link to the cgi:

$ vi buildroot/project_build_arm/armadeus/root/var/www/index.html

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
<nowiki> </nowiki>
<nowiki> </nowiki>
<nowiki><a href=http://<Your IP Address>/cgi-bin/get_ipconfig.sh> Get the board ip config </a></nowiki>
<nowiki> </nowiki>
</body>
</html>

Create the new root fs :
$ make

Finally, [[Target_Software_Installation | Transfer the rootfs]] to the board & flash it.

You can now access to the new web page and click on the cgi link !

==Links==
* [http://www.boa.org The Boa Web page]

Communicate with your board from a Linux Host (Basics)

2008-03-31T08:24:57Z

FredericB: Adding USB <-> Serial converter troubleshooting section (for the issue with ttybrl)

==RS232 configuration==
We suggest you to use '''Kermit''' as Terminal emulator for RS232 connection. Minicom was sadly reported to have problems when communicating with U-Boot (ZModem data transfer).
If you just need a simple serial console and not to transfer data then '''GTKTerm''' is the perfect choice ! (package gtkterm in Ubuntu)

===Kermit installation===
* On *Ubuntu / Debian:
# apt-get install ckermit
or use Synaptic graphical package manager.

* On Fedora:
# rpm -q ckermit

===Kermit configuration===
* Edit/Create .kermrc file in your $HOME directory and put in it:
set line /dev/ttyS0
set speed 115200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000
set send pack 1000
set window 5
set transmit linefeed on
* In this example, we assume that your serial port is ttyS0 (first serial port). Change this to correct value if necessary.
* If you use an ''USB <-> Serial'' converter then serial port would surely be named like that: ttyUSB0
** If ''USB <-> Serial'' converter doesn't seem to work, run the ''demsg'' command. You should read [http://ubuntuforums.org/archive/index.php/t-392791.html this thread] if you see some disconnection data like this :
[ 2445.568000] usb 1-1.4: new full speed USB device using uhci_hcd and address 22
...
[ 2446.964000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 2446.964000] ftdi_sio 1-1.4:1.0: device disconnected

* If you get an error message such:
$ kermit -c
/dev/ttyS0
?SET SPEED has no effect without prior SET LINE
check that you have read/write rights on /dev/ttyS0 (ie your serial port)

===Kermit usage===
* To launch it:
$ kermit -c
* To switch from terminal mode to command mode:
CTRL + \ then c
* To switch from command mode to terminal mode:
C-Kermit>c then ENTER

==TFTP server==
In order to send your image files (U-Boot, Linux, RootFS or Firmware) with higher speed to your Armadeus board, you can use the Ethernet link and a TFTP server.
Once the server started, the files located in the server shared directory (''/tftpboot'' by default) will be accessible from the U-Boot TFTP client.

===TFTP server installation===
* On *Ubuntu / Debian:
# sudo apt-get install tftpd xinetd
or use Synaptic 
* On Fedora:
# rpm -q tftpd xinetd

* Then create the directory that will contain all the files that the server will export (you have to be root to do that):
# mkdir /tftpboot
# chmod 777 /tftpboot

===Server configuration===
* Edit or create the configuration file ''/etc/xinetd.d/tftp'' and modify/add it the following lines:
# default: off
# description: The tftp server serves files using the trivial file transfer
# protocol. The tftp protocol is often used to boot diskless
# workstations, download configuration files to network-aware printers,
# and to start the installation process for some operating systems.
service tftp
{
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot
# disable = yes
}

* Restart xinetd service:
# killall -HUP xinetd
* Put some files in ''/tftpboot''

==Links==
* [http://www.columbia.edu/kermit/ Kermit Homepage]
* [http://www.jls-info.com/julien/linux/ GTKTerm Homepage]

Boa

2007-04-19T20:07:58Z

FredericB:

How install and configure the boa Web server on your board 

 
 
==Install==

$ cd armadeus
$ make menuconfig

* Select: ''Package Selection for the Target -> Other stuffs -> Boa''
* Save the configuration

Then we can create the binaries and the default filesystem. This will be usefull
later to perform the configuration :

$ make

 
 
==Configure==

 

=== Generalities ===

To apply a permanent configuration, be sure to not change anything on the board filesystem. 
That would be erased the next time you flash the fs. Instead, do all changes on the filesystem
located on the host, i.e. on ''buildroot/build_arm_nofpu/root/''

The boa configuration file is located in ''/etc/boa/boa.conf'' on the card 
This means that to permanently change the configuration, you need to edit the file
''buildroot/build_arm_nofpu/root/etc/boa/boa.conf'' '''on the host'''

 
 

=== Create a Dummy page ===

By default, DocumentRoot is set to /var/www, so let's add a dummy file here to test
our configuration :

$ mkdir buildroot/build_arm_nofpu/root/var/www
$ vi buildroot/build_arm_nofpu/root/var/www/index.html

And fill the file with :

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
</body>
</html>

 
 

=== Enable hostname resolution ===

Boa has to be able to resolve the hostname to work, so let's do :

$ echo "127.0.0.1 `cat buildroot/build_arm_nofpu/root/etc/hostname`" >> buildroot/build_arm_nofpu/root/etc/hosts

 
 

=== Create the access log directory ===

By default, boa logs will be stored in /var/log/boa/ on the card.
If you did not change this setting, you will need to perform the following :

$ls -l buildroot/build_arm_nofpu/root/var/log/

If this is a link to /tmp, then

$ rm -f buildroot/build_arm_nofpu/root/var/log/ && mkdir buildroot/build_arm_nofpu/root/var/log/

Then, create the boa directory :
$ mkdir buildroot/build_arm_nofpu/root/var/log/boa

 

-----
Why shoud I delete the symbolink link ? 
This is because during the filesystem creation, mkfs.jffs2 will keep the link from ''/var/log'' to ''/tmp'' on the board.
Thus, once on the board, you will have :

# ls -l /var/log
lrwxrwxrwx 1 root root 4 Apr 15 2007 /var/log -> /tmp

With a such behavior, even if you fill the directory ''buildroot/build_arm_nofpu/root/var/log/'' on your host
(which actually fill /tmp on your host), nothing will be saved once the filesystem will be flashed on your board.
 
-----

 
 

== Test the result ==

Create the final rootfs :

$ make

Then [[Target_Software_Installation | update the rootfs]] on your board. 

And start boa

$ boa

To access to your web page, use a browser:
http://''<your IP Address>''/

You sould see the page ! 
If not, check the file ''/var/log/boa/error_log'' on your board

 
 

== Working with cgi ==

First, check the boa.conf file. 
Once more, you should use the one located on your host before changing anything.

$ vi buildroot/build_arm_nofpu/root/etc/boa/boa.conf

Be sure to have an uncommented line like this :

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/

Now; let's write a dummy cgi :

$ mkdir buildroot/build_arm_nofpu/root/usr/lib/cgi-bin
$ vi buildroot/build_arm_nofpu/root/usr/lib/cgi-bin/get_ipconfig.sh

And add the following :

#!/bin/sh
echo -e "Content-type: text/html\r\n\r\n";
echo -e `/sbin/ifconfig eth0 | grep 'inet addr'`;

The script have to be executable:

$ chmod a+x buildroot/build_arm_nofpu/root/usr/lib/cgi-bin/get_ipconfig.sh

Then change your index.html page to add a link to the cgi:

$ vi buildroot/build_arm_nofpu/root/var/www/index.html

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
<nowiki> </nowiki>
<nowiki> </nowiki>
<nowiki><a href=http://<Your IP Address>/cgi-bin/get_ipconfig.sh> Get the board ip config </a></nowiki>
<nowiki> </nowiki>
</body>
</html>

Create the new root fs :
$ make

Finally, [[Target_Software_Installation | Transfer the rootfs]] to the board & flash it.

You can now access to the new web page and click on the cgi link !

Setup

2007-04-19T20:07:34Z

FredericB:

On this page, you will find all the usefull informations you need to configure your Armadeus board for optimum usage.

==First StartUp==
Just got your Armadeus board and want to start play with it ? Then follow this quick list to setup your envt accordingly: 
*1. Connect your APF to your development board or to a Devlight --->> [[Image:Apf_on_devlight.png]] 
*2. Connect the Host (your PC) to your development system with a crossover RS232 cable 
*3. Power up the system ('''+5Vdc on a Devlight + is in the middle of the connector''') 
*4. Establish the communication between your Host and your APF: See [[Communicate]] 
*5. Verify your APF by starting Linux: In uBoot, type "boot". Several informations will be displayed on your console like on the screenshot [[Linux start screenshot]] 
*6. If Linux has successfully started, you can proceed with the toolchain installation. See Basics below 

==Basics==
* [[Toolchain]]: How to install the development environment for the Armadeus boards
* [[Communicate]]: How to communicate with the Armadeus boards from the Host
* [[Target Software Installation]]: How to install, uBoot, Linux and your RootFS on the Armadeus boards

==Packages and Modules==
* [[FrameBuffer]]: how to configure and use the framebuffer for new LCDs
* [[GPIO Driver]]: how to configure the GPIO driver
* [[Network Configuration]]: how to configure Host and Target network (NFS, TFTP)
* [[Boa]]: How install and configure the boa Web server on your board
* [[Serial Transfer]]: how to transfer files between your Host and your Armadeus board with the RS232 link (if you don't have Ethernet)
* [[USB Gadget]]: how to configure your Armadeus board to use it as a USB device (aka Gadget in Linux language)
* [[MultiMediaCard]]: how to use MMC/SD cards on Linux with your Armadeus board
* [[DAC|Digital to Analog Convertion]]: how to configure and use the DAC on your board
* [[FPGA loader]]: how to upload a new firmware from Linux
* [[ADC max1027|Analog to Digital Converter]]: how to install and use the on board ADC (max1027)
* [[PWM]]: how to use the i.MX integrated PWM
* [[RTC]]: how to use an external Real Time Clock (Maxim DS1374)
* [[Watchdog]]: how to configure and use the i.MX integrated Watchdog

==Advanced==
* [[BootLoader]]: (U-Boot useful tips)
* [[BootStrap]]: communicate and test your board when no software is installed on it

[[Image:FrenchFlag.png]][[Configuration| Cette page en Français]]

Boa

2007-04-19T20:05:15Z

FredericB: corrections for a better rendering

How install and setup boa on your board 

 
 
==Install==

$ cd armadeus
$ make menuconfig

* Select: ''Package Selection for the Target -> Other stuffs -> Boa''
* Save the configuration

Then we can create the binaries and the default filesystem. This will be usefull
later to perform the configuration :

$ make

 
 
==Configure==

 

=== Generalities ===

To apply a permanent configuration, be sure to not change anything on the board filesystem. 
That would be erased the next time you flash the fs. Instead, do all changes on the filesystem
located on the host, i.e. on ''buildroot/build_arm_nofpu/root/''

The boa configuration file is located in ''/etc/boa/boa.conf'' on the card 
This means that to permanently change the configuration, you need to edit the file
''buildroot/build_arm_nofpu/root/etc/boa/boa.conf'' '''on the host'''

 
 

=== Create a Dummy page ===

By default, DocumentRoot is set to /var/www, so let's add a dummy file here to test
our configuration :

$ mkdir buildroot/build_arm_nofpu/root/var/www
$ vi buildroot/build_arm_nofpu/root/var/www/index.html

And fill the file with :

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
</body>
</html>

 
 

=== Enable hostname resolution ===

Boa has to be able to resolve the hostname to work, so let's do :

$ echo "127.0.0.1 `cat buildroot/build_arm_nofpu/root/etc/hostname`" >> buildroot/build_arm_nofpu/root/etc/hosts

 
 

=== Create the access log directory ===

By default, boa logs will be stored in /var/log/boa/ on the card.
If you did not change this setting, you will need to perform the following :

$ls -l buildroot/build_arm_nofpu/root/var/log/

If this is a link to /tmp, then

$ rm -f buildroot/build_arm_nofpu/root/var/log/ && mkdir buildroot/build_arm_nofpu/root/var/log/

Then, create the boa directory :
$ mkdir buildroot/build_arm_nofpu/root/var/log/boa

 

-----
Why shoud I delete the symbolink link ? 
This is because during the filesystem creation, mkfs.jffs2 will keep the link from ''/var/log'' to ''/tmp'' on the board.
Thus, once on the board, you will have :

# ls -l /var/log
lrwxrwxrwx 1 root root 4 Apr 15 2007 /var/log -> /tmp

With a such behavior, even if you fill the directory ''buildroot/build_arm_nofpu/root/var/log/'' on your host
(which actually fill /tmp on your host), nothing will be saved once the filesystem will be flashed on your board.
 
-----

 
 

== Test the result ==

Create the final rootfs :

$ make

Then [[Target_Software_Installation | update the rootfs]] on your board. 

And start boa

$ boa

To access to your web page, use a browser:
http://''<your IP Address>''/

You sould see the page ! 
If not, check the file ''/var/log/boa/error_log'' on your board

 
 

== Working with cgi ==

First, check the boa.conf file. 
Once more, you should use the one located on your host before changing anything.

$ vi buildroot/build_arm_nofpu/root/etc/boa/boa.conf

Be sure to have an uncommented line like this :

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/

Now; let's write a dummy cgi :

$ mkdir buildroot/build_arm_nofpu/root/usr/lib/cgi-bin
$ vi buildroot/build_arm_nofpu/root/usr/lib/cgi-bin/get_ipconfig.sh

And add the following :

#!/bin/sh
echo -e "Content-type: text/html\r\n\r\n";
echo -e `/sbin/ifconfig eth0 | grep 'inet addr'`;

The script have to be executable:

$ chmod a+x buildroot/build_arm_nofpu/root/usr/lib/cgi-bin/get_ipconfig.sh

Then change your index.html page to add a link to the cgi:

$ vi buildroot/build_arm_nofpu/root/var/www/index.html

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
<nowiki> </nowiki>
<nowiki> </nowiki>
<nowiki><a href=http://<Your IP Address>/cgi-bin/get_ipconfig.sh> Get the board ip config </a></nowiki>
<nowiki> </nowiki>
</body>
</html>

Create the new root fs :
$ make

Finally, [[Target_Software_Installation | Transfer the rootfs]] to the board & flash it.

You can now access to the new web page and click on the cgi link !

Boa

2007-04-19T19:59:54Z

FredericB: Page creation

How install and setup boa on your board 

 
 
==Install==

$ cd armadeus
$ make menuconfig

* Select: ''Package Selection for the Target -> Other stuffs -> Boa''
* Save the configuration

Then we can create the binaries and the default filesystem. This will be usefull
later to perform the configuration :

$ make

 
 
==Configure==

 

=== Generalities ===

To apply a permanent configuration, be sure to not change anything on the board filesystem. 
That would be erased the next time you flash the fs. Instead, do all changes on the filesystem
located on the host, i.e. on ''buildroot/build_arm_nofpu/root/''

The boa configuration file is located in ''/etc/boa/boa.conf'' on the card 
This means that to permanently change the configuration, you need to edit the file
''vi buildroot/build_arm_nofpu/root/etc/boa/boa.conf'' '''on the host'''

 
 

=== Create a Dummy page ===

By default, DocumentRoot is set to /var/www, so let's add a dummy file here to test
our configuration :

$ mkdir buildroot/build_arm_nofpu/root/var/www
$ vi buildroot/build_arm_nofpu/root/var/www/index.html

And fill the file with :

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
</body>
</html>

 
 

=== Enable hostname resolution ===

Boa has to be able to resolve the hostname to work, so let's do :

$ echo "127.0.0.1 `cat buildroot/build_arm_nofpu/root/etc/hostname`" >> buildroot/build_arm_nofpu/root/etc/hosts

 
 

=== Create the access log directory ===

By default, boa logs will be stored in /var/log/boa/ on the card.
If you did not change this setting, you will need to perform the following :

$ls -l buildroot/build_arm_nofpu/root/var/log/

If this is a link to /tmp, then

$ rm -f buildroot/build_arm_nofpu/root/var/log/ && mkdir buildroot/build_arm_nofpu/root/var/log/

Then, create the boa directory :
$ mkdir buildroot/build_arm_nofpu/root/var/log/boa

 

-----
Why delete the symbolink link ?
This is because during the filesystem creation, mkfs.jffs2 will keep the link from ''/var/log'' to ''/tmp'' on the board.
Thus, once on the board, you will have :

# ls -l /var/log
lrwxrwxrwx 1 root root 4 Apr 15 2007 /var/log -> /tmp

With a such behavior, even if you fill the directory ''buildroot/build_arm_nofpu/root/var/log/'' on your host
(which actually fill /tmp on your host), nothing will be saved once the filesystem will be flashed on your board.
 
-----

 
 

== Test the result ==

Create the final rootfs :

$ make

Then [[Target_Software_Installation | update the rootfs]] on your board. 

And start boa

$boa

To access to your web page, use a browser:
http://''<your IP Address>''/

You sould see the page ! 
If not, check the file ''/var/log/boa/error_log'' on your board

 
 

== Working with cgi ==

First, check the boa.conf file. 
Once more, you should use the one located on your host before changing anything.

$ vi buildroot/build_arm_nofpu/root/etc/boa/boa.conf

Be sure to have an uncommented line like this :

ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/

Now; let's write a dummy cgi :

$ mkdir buildroot/build_arm_nofpu/root/usr/lib/cgi-bin
$ vi buildroot/build_arm_nofpu/root/usr/lib/cgi-bin/get_ipconfig.sh

And add the following :

#!/bin/sh
echo -e "Content-type: text/html\r\n\r\n";
echo -e `/sbin/ifconfig eth0 | grep 'inet addr'`;

The script have to be executable:

$ chmod a+x buildroot/build_arm_nofpu/root/usr/lib/cgi-bin/get_ipconfig.sh

Then change your index.html page to add a link to the cgi:

$ vi buildroot/build_arm_nofpu/root/var/www/index.html

<html>
<head>
<title> Welcome on the Armadeus Board </title>
</head>
<body>
<nowiki><h1> Welcome on the Armadeus Board </h1></nowiki>
<nowiki> </nowiki>
<nowiki> </nowiki>
<nowiki><a href=http://<Your IP Address>/cgi-bin/get_ipconfig.sh> Get the board ip config </a></nowiki>
<nowiki> </nowiki>
</body>
</html>

Create the new root fs :
$ make

Finally, [[Target_Software_Installation | Transfer the rootfs]] to the board & flash it.

You can now access to the new web page and click on the cgi link !