Embedded systems placed in vehicles are usually called electronic control units (ECUs), which are responsible for safety, comfort and basic operational functionalities. Nowadays more and more functionalities are developed, therefore several cooperative ECUs are placed in a vehicle. Evidently beside these increasing functionalities, the complexity of the integrated software increases as well, therefore a deliberate and clean software architecture is necessary. The product of this concept is the AUTOSAR standard, which defines restrictions regarding the real-time scheduling of the software running on ECUs. An embedded operating system is responsible for such tasks.
In this document I present the requirements on developers defined by different standards. I will give an overview of embedded operating systems available on the market, which are complying automotive standards, and choose a compatible one with the target platform. I integrate this system into a so-called Test Software, which hasn't included operating system so far, and in which I am able to test the main features of the system. Thereafter I replace the existing OS with the chosen one in a real automotive project.
I will make measurements with different settings on the previous and the new operating system (memory usage, context switching time), and evaulate the results.
Finally I will make a guide for setting up and using the chosen operating system.