MICROSEK
Main Characteristics
The MICROSEK product is compliant with the Osek/Vdx international standard.
Certifiable against the CENELEC EN 50128 international standard. The MICROSEK product has been developed following a rigorous and safe Software Life Cycle defined by the CENELEC standard that is applied in the railway field.
Integrated with the MICROSUITE Host Tool.
MICROSEK is delivered with an integrated toolset suitable for the configuration and development of user applications.
OSEK OS Services
Task Management (Creation, Termination, Full/Non Preemptive scheduling policy). The OS subsystem provides both task types required by the Osek/Vdx standard: the Basic and the Extended Task. The Extended task can use the OS services provided for task synchronization.
Task Synchronization (Resource Access synchronization, Events).
The OS subsystem provides services for the Resource Access Synchronization based on the priority ceiling protocol. Event services are provided for suspending the calling task until a specified event arrives.
Interrupt Management (Enabling, Disabling).
The OS subsystem supports two interrupt categories: one is more efficient and does not introduce overhead permitting the use of few services; the other one can use the major part of the system services but introduces a small overhead.
Alarm Management (Absolute/Relative/Periodic/Non Periodic Alarm)
MICROSEK OS provides functionalities for Alarm Management. An alarm is a service that activates a user provided action (Task activation, Callback, Event signalling) when the specified time period expires.
Error Management (Local/Centralized Error Management).
A dedicated Hook routine can be configured to provide a user defined centralized error management.
Hook routines availability (Startup/Shutdown/Task Switching).
During the system configuration phase the user can specify the hook routines to be called by the OS subsystem when the internal Startup, Shutdown or Task Switching functionalities are activated.
Availability
Processor
|
Development Environment |
Janus (ARM7) |
Wind River system © |
Micronas CDC16xxF/CDC32xxG |
WDC C-Compiler, WinIDEA, GreenHills Multi2000 © |
Motorola 68K |
Microtec © |
ST10 (Under Dvelopment) |
TASKING |
MICROSUITE
The MicroSuite tool is an integrated toolset that provides the user with all the major functionalities necessary for the Development, Configuration, Debugging and Testing of the software application.
The tool is completely independent of the used (cross or native) software development environment.
The user - in order to build a full application - must only provide the object libraries containing the low level drivers, a boot procedure and the specific algorithms to be executed as code of the configured tasks. All the remaining actions are executed by the tool under user control. eg.: Starting from the application graphical design - where the developer can choose which and how many resources the application needs - the tool automatically generates the configuration data and the ‘makefile’ directive file useful for the final application building.
The main functionalities provided by the tool are:
Project Management: The tool provides the user with the right function to logically integrate a System Configuration, Source files and Libraries into a logical container called ‘Project’. The Project can be seen as a specific final application
Project Configuration Control: This feature is useful for the source files organization and maintenance. Once the project where the user wants to work is selected, the tool provides the user with a set of functionalities necessary for the management of the project resource versions (Save, Retrieve, Check, Delete, etc).
The tool must be configured with the name of the Configuration Control Tool installed on the machine.
OSEK Resource Graphical Configuration (OIL): Starting from an existing resource configuration, this functionality generates an OIL file compliant with the standard Osek OIL V. 2.3. files inserted into the project can be modified by using the configured Editor. The name of the Source File Editor, installed on the machine, must be configured during the parameters initialization phase of the MICROSUITE configuration.
Source Code Compilation: All the source files inserted into the project are automatically compiled by the tool. The name of the source file compiler to be used for program compilation has to be configured during the parameters initialization phase of the MICROSUITE configuration.
Application Building: All of the generated object files and the libraries provided by the user are automatically linked together by the tool in order to produce the final executable application. The name of the linker must be configured during the parameters initialization phase of the MICROSUITE configuration.
Application Debugging: Once the final executable application has been generated, the tool provides the user with the functionality for activating a debugging session. The name of the Debugger Tool must be configured during the parameters initialization phase of the MICROSUITE configuration.
Visualization of Diagnostic and Monitoring application Data: This is a graphical functionality useful for the behaviour analysis of the real-time application to be tested (under test).
Application Simulation: This is an integrated graphical functionality useful for the debugging/run of the user application directly on the PC Host machine. Due to the large difference between the target and the PC machine, only a limited subset of the application functionalities can be tested on the Host machine.
Special points of interest:
- OSEK Compliance
- CENELEC EN50128 Certificability
- Integrated Host toolset.
- Real-Time
- Resource Configuration and Scalability
- Easily portable
|
OSEK Compliance
OSEK OS is compliant to Release 2.2 of the OSEK Standard for the BCC1 and ECC1 Class.
|
|