Evaluation Environment for AUTOSAR-Autocode in Motor Control ...
Evaluation Environment for AUTOSAR-Autocode in Motor Control ...
Evaluation Environment for AUTOSAR-Autocode in Motor Control ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 3<br />
MEDC17<br />
<strong>AUTOSAR</strong> is a new standard, which is described <strong>in</strong> the previous chapter. The currently<br />
from BOSCH developed and used environment <strong>for</strong> software of motor control<br />
units is called MEDC17. It is not a standard as <strong>AUTOSAR</strong>, but just an environment<br />
consist<strong>in</strong>g of a software architecture and application software together with a build<br />
environment. The control unit, which is fabricated from BOSCH and <strong>for</strong> which the<br />
software is developed, has the same name. If it is not explicitly said, <strong>in</strong> this work with<br />
“MEDC17” is only the software part meant.<br />
MEDC17 provides another approach than <strong>AUTOSAR</strong>. First MEDC17 just provides<br />
support <strong>for</strong> the architecture and development of software <strong>for</strong> one control unit. It does<br />
not handle so much features, which can be used by the Application Software (ASW),<br />
than <strong>AUTOSAR</strong>. However, on the other hand MEDC17 supports the development<br />
process of BOSCH with some mechanisms like e.g. the automatically generation of<br />
documentation. This mechanisms have no counterpart with<strong>in</strong> the <strong>AUTOSAR</strong> standard.<br />
Due to secrecy, this chapter just takes a facile overview about what is necessary to<br />
understand the later described work. Some comparisons to <strong>AUTOSAR</strong> are made <strong>in</strong><br />
this chapter, but even if MEDC17 is described after <strong>AUTOSAR</strong>, MEDC17 is the older<br />
one.<br />
3.1 ERCOSEK<br />
MEDC17 is based on the embedded operat<strong>in</strong>g system ERCOSEK, which was developed<br />
and distributed by ETAS. ERCOSEK is an OSEK–OS compliant operat<strong>in</strong>g system.<br />
Some mechanisms of OSEK–OS are described <strong>in</strong> section 2.3.<br />
The OSEK standard specifies extended tasks, but they are optional <strong>for</strong> an OSEK<br />
compliant operat<strong>in</strong>g system. ERCOSEK is one of these, which do not support extended<br />
tasks. So just basic tasks can be used. On the other hand extended task are also<br />
undesired because of the resource overhead they cause.<br />
Not every feature of ERCOSEK is used <strong>in</strong> MEDC17. Additionally, MEDC17 has a<br />
fixed configured operat<strong>in</strong>g system and it is very unusual to change the configuration,<br />
especially <strong>for</strong> every auto build.<br />
25
Change language