SAE Technical Paper Series 1996
DOI: 10.4271/960623
|View full text |Cite
|
Sign up to set email alerts
|

ERCOS: An Operating System for Automotive Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0
3

Year Published

1997
1997
2010
2010

Publication Types

Select...
5
2

Relationship

2
5

Authors

Journals

citations
Cited by 22 publications
(13 citation statements)
references
References 10 publications
0
10
0
3
Order By: Relevance
“…An experimental implementation of the message operations send and receive has shown an overhead of 0.625 s and 0.750 s, respectively. This implementation has been carried out in the framework of ERCOS [24] under the assumption that the message length is equal to the word length of the processor.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…An experimental implementation of the message operations send and receive has shown an overhead of 0.625 s and 0.750 s, respectively. This implementation has been carried out in the framework of ERCOS [24] under the assumption that the message length is equal to the word length of the processor.…”
Section: Discussionmentioning
confidence: 99%
“…Although conceptually simple, the cyclic executive approach suffers from a number of drawbacks [18]; it uses resources inefficiently, it does not easily cater to sporadic jobs, and it gives poor support to more flexible and adaptive requirements. A more appropriate scheme, using priority-based scheduling of application tasks [4], is currently been used (or evaluated) in a number of application domains, for example, in avionics [2] or automotive electronics [24]. Both preemptive and nonpreemptive (cooperative) methods are under consideration.…”
mentioning
confidence: 99%
“…For example, a task can be released earlier, execute initial code and then voluntarily suspend itself until the beginning of its LET. This is a form of cooperative scheduling [11]. Taking into account internal task structure has been shown to improve scheduling margins.…”
Section: Conclusion and Related Workmentioning
confidence: 98%
“…Dabei wird der Cluster mit der kleinsten Deadline oder Periode auf die Task mit der höchsten Priorität abgebildet. Kommunikation zwischen Clustern muss in bestimmten Fällen durch doppelt gepufferte Interprozesskommunikation (IPC) [22] abgesichert werden, um die Semantik des Modells in der Implementierung zu erhalten. Die auf der Implementierungsebene auftretenden Verzögerungen werden dabei auf Modellebene durch die logisch gezeiteten Verzögerungen an den Clustergrenzen abgebildet.…”
Section: Verwandte Ansätze Und Beiträge Von Automodeunclassified