Dates and Events: |
OSADL Articles:
2023-11-12 12:00
Open Source License Obligations Checklists even better nowImport the checklists to other tools, create context diffs and merged lists
2022-07-11 12:00
Call for participation in phase #4 of Open Source OPC UA open62541 support projectLetter of Intent fulfills wish list from recent survey
2022-01-13 12:00
Phase #3 of OSADL project on OPC UA PubSub over TSN successfully completedAnother important milestone on the way to interoperable Open Source real-time Ethernet has been reached
2021-02-09 12:00
Open Source OPC UA PubSub over TSN project phase #3 launchedLetter of Intent with call for participation is now available |
Real Time Linux Workshops
1999 - 2000 - 2001 - 2002 - 2003 - 2004 - 2005 - 2006 - 2007 - 2008 - 2009 - 2010 - 2011 - 2012 - 2013 - 2014 - 2015
13th Real-Time Linux Workshop from October 20 to 22 at the Faculty of Electrical Engineering, Czech Technical University in Prague
Announcement - Hotels - Directions - Agenda - Paper Abstracts - Presentations - Registration - Abstract Submission - Sponsoring - Gallery
Migrating a OSEK runtime environment to the OVERSEE platform
Andreas Platschek, OpenTech EDV-Research, Austria
Georg Schiesser, OpenTech EDV-Research, Austria
As virtualization techniques are being used in the automotive industry, in order to save hardware, reduce power consumption and allow the reuse of legacy applications, as well as allow the fast development and integration of new applications, the need for a runtime environment that is suitable and in wide use in the automotive industry emerges. The requirements for such an runtime environment are defined in the most widely used specification in this industry - OSEK/VDX.
One key feature the OVERSEE project is taking advantage of, is that co-locating a OSEK runtime environment and a full-featured GPOS GNU/Linux eliminates many limitations of OSEK/VDX by the extension through virtualization and notably allowing to mitigate some of the serious shortcomings in the security area by resolving these issues at the architectural level rather than trying to patch up the limited OSEK OS. This may well constitute a general trend to specialize operating systems and operate powerful hardware as an assortment of specialized FLOSS systems collaborating to provide different services, including full backwards compatibility to legacy operating systems.
Currently, several FLOSS implementation of this specification are available under different FLOSS license models and with a different degree of compliance. This paper gives an overview of the available implementations, a rational for the chosen implementation as well as a description of the efforts for the migration to XtratuM.