|
Title
|
|
|
|
Migrating from a proprietary RTOS to the OSEK standard using a wrapper
|
|
|
Author
|
|
|
|
|
|
|
Abstract
|
|
|
|
| The drive towards standardization in the automotive sector puts a lot of pressure on software suppliers to comply with standards such as OSEK and AUTOSAR. However, many of these suppliers have a vested interest in proprietary software and are seeking ways to migrate their existing code base to comply with these standards. This paper reports on a feasibility study to migrate an automotive off-highway application to the OSEK-OS using a wrapper around the proprietary real-time operating system (RTOS). Besides investigating whether this is feasible, we also assess the performance impact in terms of computation time and memory consumption, as this is critically important for real-time systems. Finally some pitfalls are given when porting a given application to OSEK-compliant RTOS. As such, we evaluate the typical trade-offs one has to make when adopting an incremental migration strategy towards a standard compliant interface. |
|
|
|
Language
|
|
|
|
English
|
|
|
Source (book)
|
|
|
|
Solutions on Embedded Systems
|
|
|
Source (series)
|
|
|
|
Lecture notes in electrical engineering
|
|
|
Publication
|
|
|
|
2011
|
|
|
ISSN
|
|
|
|
1876-1100
|
|
|
ISBN
|
|
|
|
978-94-007-0637-8
|
|
|
DOI
|
|
|
|
10.1007/978-94-007-0638-5_17
|
|
|
Volume/pages
|
|
|
|
81
(2011)
, p. 241-254
|
|
|
Full text (Publisher's DOI)
|
|
|
|
|
|