Difference between revisions of "Xenomai"

From ArmadeusWiki
Jump to: navigation, search
m (Links)
(Going further)
Line 173: Line 173:
  
 
==Going further==
 
==Going further==
* [[Xenomai:examples usage | Examples usage]]
+
* [[Xenomai:examples usage | Using Armadeus Xenomai custom examples]]
* [[Xenomai:Blinking LEDs | first tutorial]]  
+
* [[Xenomai:Blinking LEDs | Xenomai tutorial (blinking LED)]]
  
 
==Links==
 
==Links==

Revision as of 09:06, 15 February 2010

Page under construction... Construction.png Informations on this page are not guaranteed !!

What is Xenomai ?

Xenomai is a real time co-kernel which cooperate with Linux via Adeos. With its help hard real time applications can be developped and run on the Armadeus boards.

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 Xenomai

The main steps are:

  • selection of Xenomai package on the Buildroot menuconfig,
  • selection of Xenomai features in Kernel menuconfig,
  • compilation of the new version,
  • validation of the Xenomai behaviour.

Selecting Xenomai package

  • First of all, you need to select Xenomai package on buildroot menu:
 $ make menuconfig
Package Selection for the target --->
    [*] Xenomai
  • If you plan to use xeno-test (Xenomai performance tool) then CONFIG_ASH_GETOPTS should be activated in busybox:
 $ make busybox-menuconfig
Shells  --->
        Choose your default shell (ash)  --->
    --- ash
    ---   Ash Shell Options
          ...
          [*]   Builtin getopt to parse positional parameters 

Xenomai kernel space support

In a first time for having kernel patched with Xenomai and Adeos patch, you must type :

 $ make

After a moment you will be asked for some Xenomai options:

Xenomai (XENOMAI) [Y/n/?] (NEW)

Stop the building process with Ctrl-C command. We will preferably configure the Xenomai kernel from menuconfig:

 $ make linux26-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 everything:

 $ make

Deploy

You can now 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.

Now we can run the performance test provided by Xenomai:

 $ xeno-test

Deinstalling or disabling Xenomai

There are two parts needed for disabling Xenomai features

Kernel

For disabling kernel part, two solutions are available

  • The first solution is to unselect kernel's features :
 $ make linux26-menuconfig

And disable following options:

Real-time sub-system --->
    [ ] Xenomai

and

Kernel Features ---> 
    [ ] Interrupt pipeline
  • The second solution is to destroy the kernel tree :
 $ make linux26-dirclean

Userspace / package

For disabling userspace/package part :

 $ make menuconfig

and disable Xenomai

Package Selection for the target ---> 
    [ ] Xenomai

then use the dirclean command:

 $ make xenomai-dirclean

Going further

Links