Changes between Version 4 and Version 5 of ALOELinuxGuide
- Timestamp:
- 05/12/09 19:31:35 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ALOELinuxGuide
v4 v5 14 14 If you downloaded ALOE from source, take a look at the 'examples' directory. There you will see the implementation of 3 ALOE objects (source, decimator and sink) and another folder called ''repository''. This directory is where Manager Daemons will look for configuration files, waveform definitions files and executables (and more things...). This path will be passed as the first argument to the ALOE launcher. 15 15 16 You will see that this directory as, among others, the following '''mandatory''' subdirectories:16 You will see that this directory has, among others, the following '''mandatory''' subdirectories: 17 17 * logs: Here waveform's modules will store their logs, in per-waveform sub-directories. 18 18 * reports: This is where statistics value reports are written … … 25 25 Also during the installation, the default repository folder has been set to one provided in the source package, relative to the path where you untar'd it. 26 26 27 So, launching ALOE is as easy as going to the source directory and type: 28 27 29 {{{ 28 runph phal-repositories30 runph 29 31 }}} 30 31 You just got into the ALOE environment! By the moment, you can't do anything because you need to download an application first. This will be explained in the following section.32 32 33 33 [[BR]] … … 35 35 More optional arguments can be passed to runph in the shell. The command accepts the following arguments: 36 36 {{{ 37 runph [repository_path] -c [platform_cfg_file] -i [xitf_cfg_file] -p [priority] -d [debug_level][--daemon] [-o output_file]37 runph [repository_path] -c [platform_cfg_file] -i [xitf_cfg_file] -p [priority] [--daemon] [-o output_file] 38 38 }}} 39 39 Where: … … 42 42 * ''-i [xitf_cfg_file]'': Configuration file for external interfaces, see Customizing your Platform. ''Default'': /usr/local/etc/xitf.conf 43 43 * ''-p [priority]'': Needs root privileges. Kernel priority level for waveform processes, see Performance Notes. ''Default'': 20 44 * ''-d [debug_level]'': Sets platform debug level. Currently only 2 modes are supported, level=0 or level!=0, where the first means normal operation and the second prevents EXEC daemon to kill processes which violated real time policies. ''Default'': 045 44 * ''--daemon'': Run PHAL in background. You should specify an output file (for standard output) so you can track what's happening. Also '''cmdman''' daemon should be launched as a daemon preventing to read from input (see below, Launching ALOE as a Daemon). ''Default'': Foreground. 46 45 * ''-o [output_file]'': File to redirect standard output. ''Default'': None, terminal stdout. … … 49 48 [[BR]] 50 49 51 == Downloading a waveform: Wimax ==52 53 You can download Wimax waveform latest version from our repository: Remember that you will be prompted for a valid username.54 55 {{{56 svn checkout http://flexnets.upc.edu/svn/phal-apps/trunk/wimax57 }}}58 59 This will download all the files to a directory called wimax. You can enter there and compile your files as usually, paying attention on '''linking them to the ALOE SW API Library''' (see DeveloperGuide).60 61 [[BR]]62 63 50 == Running a waveform: Basic ALOE commands == 64 51 65 ALOE can be controlled from a text console typing commands. Basically, running a waveform compromises 3 steps: ''loading'', ''initializing'' and ''running''. You will do such by typing the appropriate commands in the input console. In the next example, we will load, initialize and run the example waveform Wimax:52 ALOE can be controlled from a text console by typing commands. Basically, running a waveform compromises 3 steps: ''loading'', ''initializing'' and ''running''. You will do such by typing the appropriate commands in the input console. In the next example, we will load, initialize and run the example waveform. 66 53 67 Once ALOE has been started with the appropriate arguments (see first section), we will load the waveform by typing in the prompt:54 Once ALOE has been started (by default typing {{{ runph }}} from the source directory, we will load the waveform by typing in the prompt: 68 55 {{{ 69 runph$: phload wimax56 runph$: phload example 70 57 }}} 71 58 72 59 then initialize: 73 60 {{{ 74 runph$: phinit wimax61 runph$: phinit example 75 62 }}} 76 63 77 64 and finally run: 78 65 {{{ 79 runph$: phrun wimax66 runph$: phrun example 80 67 }}} 81 68 82 69 Now the waveform is running. We can see current processes information typing: 83 70 {{{ 84 runph$: execinfo wimax 71 runph$: execinfo example 72 }}} 73 74 Or the available statistics 75 {{{ 76 runph$: statls example 85 77 }}} 86 78 87 79 You also can pause the execution or run a finite number of steps, type: 88 80 {{{ 89 runph$: phpause wimax90 runph$: phrun wimax100081 runph$: phpause example 82 runph$: phrun example 1000 91 83 }}} 92 84 … … 108 100 * ''output_file'': File to redirect standard output. 109 101 * ''report_file'': File where save hw info reports 110 * ''debug_level'': Debug level111 102 * ''priority'': Priority level for objects 112 103
