`Installation procedure How to run the tool Demo of the basic features`

You can download Ocarina from https://github.com/OpenAADL/ocarina/releases on your laptop/machine. Ocarina is available for Mac and Linux targets.

The Unix tar xvfz ocarina-2017.1-suite-linux-x86_64-20170204.tgz command run on a Linux station will open the tar.gz file at the location where your want to install ocarina.

How to run the tool

In the sequel, we assume ocarina is installed in your home, in a folder called ocarina-2017. To launch the tool, update your shell PATH variable to point to the bin folder of ocarina, and then ocarina can be called as any shell command, as shown above where ocarina is called with -v option to show its version number.

Note that ocarina may produce source code from an AADL mode for you. Such source code can be models to be run with analaysis tools, but also C or Ada source code to be complied and run on a target, such as Linux, RTEMS, ... In that case, we assume you also have installed the needed tools, i.e. compilers, emulators, analysis tools.

In the sequel, we will show you how to generate C code for a Linux target and then, we assume that we have installed a C compiler.

Demo of the basic features

The objective of this demo is to discover the use of the tool.

Download the files from there and save them in a specific folder. The function of each of this file is:
- tictac.aadl contains the AADL model to handle. In this example, the AADL model is composed to two periodic threads, called tic and tac, with a respective period of 1 second and 500 millisecond. These threads are declared in a process binded to a processor with a fixed priority scheduler. Notice the following property of the processor:
```
  Deployment::Execution_Platform => native;
```
  which means that the target will be the current working machine, i.e. a Linux station. Ocarina is able to generate code for a different target of your current working station, i.e. source code that have to be compiled latter with a cross-compiler.
- tictac.c contains the subprograms which are the entry point the tic and tac threads. Here, the code of the threads is written in C and just displays a string on the screen at each thread release.
- scenario.aadl finally drives ocarina work. This file may contain parameters to ocarina in order to specify how and what to do with the model.
Now, call ocarina as follow:
```
ocarina -x scenario.aadl
```
This calls ocarina with any parameter values expressed in scenario.aadl. In this example, Ocarina will produce the C source code in a folder called root_impl.
Move to the root_impl folder and compile the generated code with:
```
make
```
This will produce an executable called node_a in the folder root_impl/node_a
Now you can launch and test the node_a executable on your Linux station and see the expected output on the screen.
From the AADL model, Ocarina produces various elements in C to run the program with an middleware called PolyORB-HI. In the root_impl/node_a folder, open the files activity.h, activity.c, deployment.h and deployement.c. Can you explain the function of the elements generated in these files?
Remove "with Deployment;" and "Deployment::Execution_Platform=>native" from processor type cpu, and then call Ocarinas as follow:
```
  
ocarina -aadlv2 -g cheddar tictac.aadl
```
It generated Cheddar model from the tictac AADL.

(return back to home page)

`Installation procedure How to run the tool Demo of the basic features`

Installation procedure

How to run the tool

Demo of the basic features

(return back to home page)