User:PXROS HIGHTEC/sandbox/PXROS-HR

PXROS-HR
Developer	HighTec EDV Systeme
Written in	C, C++ and assembly
OS family	Real-time operating system
Initial release	1983; 41 years ago, PXROS
Marketing target	Embedded, Functional safety,Industry and Automotive
Available in	English
Platforms	TriCore, AURIX
Kernel type	Real-time micro-kernel
Preceded by	PXROS
Official website	PXROS-HR

PXROS-HR is an object oriented real-time operating system (RTOS) with a very modern micro-kernel and outstanding features, especially suited for deployment on advanced multi-core MCUs. The latest version of PXROS-HR improves the concepts of encapsulation and robustness by using fine granular hardware protection mechanisms (MPU), available in modern micro-controllers like the AURIX.

The PXROS-HR operating-system for TriCore has been officially safety approved. HighTec received the certificate confirming the fitness of PXROS-HR for safety-related applications up to SIL 2 (IEC61508).

PXROS-HR is developed with the HighTec C/C++ compiler for TriCore/AURIX and best suited for industrial applications, as well as automotive applications where safety is key. The RTOS integrates with Infineon's MCAL and SafeTlib software frameworks, while being non-AUTOSAR based and highly optimized for the TriCore architecture, providing multi-core support for the AURIX family.^[1]

RTOS Introduction ^[2]

PXROS-HR (High Reliability) is the successor of the original real-time micro-kernel PXROS, that was first developed in 1983, which is in successful use since 1985 on thousands of different applications/devices in the field. There were three very important design goals set for the original PXROS, which were fully achieved:

Excellent interrupt behavior (no interrupt locking!)
Philosophy of OS leads to a good structure and architectural clearness
Extreme robust behavior under heavy load
One of the most important principles underlying PXROS is encapsulation of information and activity.

Both help to improve the reliability and protection against unintended or malicious interference. Activities (tasks in the sense of processes) live in capsules and can only communicate by exchanging message objects and signals. Processes of this kind only know the objects needed to fulfill their task and behave in a such way that the rest of the system is affected to the least possible extent. For example, they should never use hard interrupts locks, because this might destroy assumptions regarding timing behavior in other places. Resources should only be used in such a way, that a local bottleneck has no global effects.

The PXROS-API offers the complete set of services required to achieve the above mentioned goals. This API also allows to emulate the APIs of many other OSs. In PXROS-HR the principles of encapsulation are ensured in the form of automatic run-time checks performed by the AURIX MPU. The AURIX MPU behaves like an address comparator for checking address boundaries. PXROS-HR manages the AURIX MPU and ensures that an illegal data access by a task will be immediately detected at run-time by the MPU, and any error propagation will be prevented. If a task is scheduled, PXROS-HR will switch the MPU configuration of the corresponding task.

In addition, PXROS-HR allows reloading and debugging tasks at run-time without stopping a running application. This encapsulation enables customers to perform a save function integration and to mix safety and non safety related software on a single AURIX without risk, since there is no error propagation.