What it is
POSIX is the portable operating-system interface published as IEEE 1003.1 and, under the same text, as The Open Group Base Specifications. It fixes the source-level contract between an application and a Unix-like operating system: the functions, headers, and behaviors a program may rely on so the same source can be rebuilt on another conforming system.
IEEE 1003.13, the companion real-time profiles standard, defines smaller slices of that contract. PSE51, the minimal real-time system profile, is the subset AUTOSAR Adaptive names as its minimum operating-system profile: a threaded run-time, without assuming a general file system or a multi-user command environment. Conformance claims still start from that PSE51 floor, and every extra interface has to be named separately.
Who it applies to
The standard applies to application software that runs on an operating system, which in an E/E vehicle means the HPC application processor and the AUTOSAR Adaptive platform hosted on it. Classic AUTOSAR applications, which run as tasks under AUTOSAR OS, follow a different operating-system contract.
Architects use POSIX when they select that operating system and record the profile application code may depend on. Platform and basic-software teams use it when they integrate the operating system under Execution Management. Application teams use it whenever they call a thread, timer, signal, or I/O function and need the call to exist on the production image as well as on the development machine.
What it covers
IEEE 1003.1 specifies the operating-system behavior visible to application source. That includes thread and process services, synchronization, signals, clocks and timers, and the inter-process and I/O facilities that belong to the base standard. Linux and commercial real-time operating systems implement overlapping portions of this surface and then add extensions of their own.
PSE51 keeps a minimal real-time subset of the same family. Options differ, so a function can be standard POSIX and still lie outside PSE51, and a function can work on a desktop Linux image and still be a non-POSIX extension.
| Document | Role in an automotive stack |
|---|---|
| IEEE 1003.1 | Base POSIX interfaces for portable application source |
| IEEE 1003.13, PSE51 | Minimal real-time profile Adaptive cites as the operating-system floor |
| Operating-system manual | Which of those interfaces, and which extensions, this ECU actually provides |
The list that binds a vehicle program is the chosen profile read together with that operating-system manual.
How it fits with other documents
AUTOSAR Adaptive places its service layer on this operating-system floor. Execution Management starts and stops application processes. Communication and persistency are Adaptive services that assume an operating system able to host them. Application and platform code still call POSIX threads, clocks, and synchronization directly.
On a Classic microcontroller the matching contract is AUTOSAR OS, with tasks and interrupt service routines in the OSEK/VDX tradition. Both can appear in one vehicle and meet on the network, each processor keeping its own execution model.
ISO 26262 and the automotive cybersecurity standards apply to the same ECU and leave the operating-system interface to POSIX and to the supplier manual. Scheduling behavior, user permissions, and any shell or file system beyond PSE51 become inputs to those analyses: they describe how software runs, and what a fault or an intrusion can reach.
In practice
Record the supported profile in the ECU interface agreement before application code spreads. For an Adaptive HPC, state PSE51 as the minimum and list every additional POSIX option and vendor extension the program allows. Code that needs files, sockets, or several processes belongs to that extra list. Those facilities sit outside a strict reading of the minimal profile, including on a development board whose Linux image happens to provide them.
Review thread priorities, clock selection, and signal handlers together with watchdog and startup timing. When software moves from another vehicle computer, compare profiles before comparing feature lists. At each platform baseline, confirm the current edition of IEEE 1003.1 and IEEE 1003.13 and the operating-system vendor’s conformance statement. Editions are revised over time, and the interfaces your source calls have to stay aligned with the edition you specified.