TRIOZ OSEK RTOS is a OSEK compliant real time operating system  (RTOS) which is pre-configured using an OSEK Implementation Language (OIL) file as  per user application needs. OSEK is an open standard, of which the detailed specification can  found at www.OSEK-VDX.org . The acronym OSEK stands for Open System and the corresponding interface for automotive electronics.  The objectives of  OSEK specifiations is to represent a uniform environment which supports efficient utilization of resources for automotive control unit application software. This allows the applications written on any OSEK compliant OS to be uniform.

More than 94% of the vehicles globally runs on OSEK Operating systems in their vehicles. The prominent users of OSEK RTOS includes BMW, VOLVO, GM, Dalmier and more.

Trioz OSEK RTOS is compliance with ECC1, BCCI OSEK standards. We are very close to complete our compliance for BCC2 & ECC2 OSEK Standards. For details about OSEK Standards Please visit www.OSEK-VDX.org

Trioz OSEK RTOS enables and ensures users on all other RTOS features like Portable, ROMable, Scalable , Preemptive and Non-preemptive, Multitasking, Deterministic,Task Stack, Services, Interrupt management, Robust and Reliable

Detailed Features of Trioz OSEK RTOS:

1. Task Management - N number of tasks

2. Resource Management - Maximum of 8 resources per tasks with PCP (Priority Ceiling Protocol support)

3. Event Management

4. Alarms and Counters

5. Dual Scheduler ( Pre-emption & Non Pre-emption)

6. Interrupt Management – Category 1 & 2


Technical Specification of Trioz OSEK RTOS :

1. Foot Print – 10kb for 64 task

2. Context Switch Time – 150 Micro Seconds For PIC 18F452 having 4Mhz Clock Frequency

Limitations of Trioz OSEK RTOS :

1.application mode is not supported

2. Not fully complaints to BCC2 & ECC2

For more information about TRIOZ OSEK RTOS limitation please download the TRIOZ OSEK RTOS Limitation document


TRIOZ OSEK RTOS State of the Art Analysis

The TRIOZ OSEK RTOS is a real-time operating system to be used in automotive applications. The complexity of automotive applications varies considerably from simple control functions in the field of body electronics to high-end applications. TRIOZ OSEK RTOS can be easily ported to any ECU embedded system. The task switching time must be known, in order to calculate the worst case execution time (WCET) which is the most important factor.

Achieve efficiencies in programming your embedded communications and control systems by using the TRIOZ OSEK RTOS. TRIOZ OSEK RTOS describe a small, real-time operating system (RTOS) ideal for most embedded systems that are statically defined. TRIOZ OSEK RTOS has standard API's for developing the RTOS application. Please download the TRIOZ OSEK RTOS user manual and API manual for more details.

Configuring the TRIOZ OSEK RTOS by using System Generatoror

TRIOZ OSEK RTOS provides a convenient and easy way of configuring and RTOS features using System Generator Utility.  The System Generator provides means to take up the user RTOS configuration using a GUI( Graphical User Interface). This inturn is used to generate oil.h & oilc files which is used with the application file to generate a static Trioz OSEK RTOS Kernel. The OIL file provide the definition of the whole system, including all objects in OSEK. In OIL files, each task is defined by its task name, priority, alarms, resources,and the amount osf stack space needed and how it scheduled other objects are defined in the same way in OSEK.Please download a detailed document of System Generetor Document here...