Accelerating With AUTOSAR - ETAS
Accelerating With AUTOSAR - ETAS
Accelerating With AUTOSAR - ETAS
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
10 <strong>ETAS</strong> IS COMMITTED TO <strong>AUTOSAR</strong><br />
<strong>Accelerating</strong><br />
<strong>With</strong> <strong>AUTOSAR</strong><br />
From start to finish –<br />
first steps to <strong>AUTOSAR</strong> production ECU – with <strong>ETAS</strong> solutions along the way<br />
In a significant expansion of its <strong>AUTOSAR</strong> portfolio, <strong>ETAS</strong> also relies on the ECU-related technical<br />
skills and domain-specific expertise of the Bosch Group. In the area of model-based development of<br />
<strong>AUTOSAR</strong>-conformant ECU software, <strong>ETAS</strong> tools and basic software support a multitude of tasks.<br />
The consistent openness of <strong>ETAS</strong> <strong>AUTOSAR</strong> solutions facilitates their easy integration into existing<br />
development environments.<br />
Besides the established, <strong>AUTOSAR</strong>conformant<br />
development tools for<br />
automotive embedded software –<br />
such as ASCET and INTECRIO – <strong>ETAS</strong><br />
offers a comprehensive portfolio of<br />
<strong>AUTOSAR</strong>-conformant authoring and<br />
configuration tools, basic software<br />
and services for the development of<br />
<strong>AUTOSAR</strong>-conformant projects.<br />
<strong>AUTOSAR</strong> architecture tool<br />
<strong>With</strong> the <strong>AUTOSAR</strong> authoring tool<br />
from <strong>ETAS</strong> (working title ISOLAR-A),<br />
a cutting-edge architecture tool has<br />
become available that helps meet<br />
many demands for the seamless<br />
collaboration between OEMs and<br />
software and/or ECU manufacturers.<br />
OEM-typical tasks, such as the design,<br />
visualization, and validation of an<br />
By Dr. Ulrich Freund and Bernhard Reckels, <strong>ETAS</strong><br />
entire vehicle system, as well as the<br />
definition of functionalities and communications<br />
relationships between<br />
the software components, comprise<br />
typical requirements for a modern<br />
<strong>AUTOSAR</strong> architecture tool. As part<br />
of their contribution, suppliers and/<br />
or OEMs ensure the availability of<br />
software components in a manner<br />
commensurate with the respective<br />
vehicle domain. The inclusion of<br />
suppliers aids the cooperation both in<br />
this early phase and in the case of<br />
subsequent modifications.<br />
Quite often, the partitioning of the<br />
system into individual ECUs and<br />
networks is directed by the OEM. It<br />
may, however, also occur in close<br />
coordination with the ECU manufac-<br />
turers. This gives rise to additional<br />
demands the tool must meet. During<br />
this phase, all major demands imposed<br />
by the overall system on networks,<br />
individual ECUs and manufacturers<br />
are specified. The result is a<br />
design specification for each ECU<br />
manufacturer that is more explicit<br />
than any textual description.<br />
Aside from the OEM’s top-down<br />
specifications with the suppliers, the<br />
tool-based cooperation provides the<br />
benefits of improved bottom-up<br />
support, which allows modifications<br />
occasioned by ECU integration to<br />
flow back into the OEM’s overall<br />
system without hindrance. In this<br />
way, a tool such as ISOLAR-A facilitates<br />
not only system partitioning<br />
and early validation of the overall system<br />
but also the consistent consideration<br />
of subsequent changes.<br />
However, <strong>AUTOSAR</strong> standardization<br />
notwithstanding, still needed are<br />
shared open interfaces that would<br />
allow the tools to be deployed in a<br />
variety of development environments.<br />
The tool ISOLAR-A therefore builds<br />
strictly upon the <strong>AUTOSAR</strong> Tool Platform<br />
Artop, skirts proprietary solutions<br />
or databases, and can be easily<br />
integrated and operated in any desirable<br />
file-based environments and<br />
software configuration and version<br />
management system (SCM). Artop<br />
also allows the flexible augmentation<br />
of customer-specific development<br />
setups.<br />
Modeling and code generation tool<br />
For many years, the ASCET product<br />
family name has been synonymous<br />
with highly efficient, safe modelbased<br />
software development, and<br />
the high-quality, automatic generation<br />
of production code that is certified<br />
as per IEC 61508 and ISO/DIS<br />
26262. Deployed all over the world,<br />
ASCET meets specific auto industry<br />
demands. These address the development<br />
of complex, hard real-time<br />
capable embedded software that is<br />
memory-optimized for the attendant<br />
hardware. On the other hand, they<br />
stipulate development safety and<br />
processes.<br />
The use of ASCET V6.1 permits<br />
the direct application of individual<br />
<strong>ETAS</strong> IS COMMITTED TO <strong>AUTOSAR</strong><br />
THE CHALLENGE<br />
The <strong>AUTOSAR</strong>-conformant development<br />
of electronic control<br />
units needs to overcome numerous<br />
hurdles.<br />
THE SOLUTION<br />
<strong>ETAS</strong> offers a consistent <strong>AUTOSAR</strong>conformant<br />
tool chain, which is<br />
successfully deployed in systems<br />
design from simulation to prototyping<br />
to series production ECU.<br />
In addition, <strong>ETAS</strong> supplies CUBAS,<br />
the complete and proven <strong>AUTOSAR</strong><br />
Basic Software. The portfolio is<br />
augmented by competent services<br />
in the <strong>AUTOSAR</strong> area, e.g., for<br />
consulting and specific project<br />
support.<br />
THE BENEFIT<br />
The powerful <strong>AUTOSAR</strong> solutions<br />
from <strong>ETAS</strong> provide consistent<br />
support from initial steps to the<br />
completed <strong>AUTOSAR</strong> production<br />
ECU.<br />
11
12 <strong>ETAS</strong> IS COMMITTED TO <strong>AUTOSAR</strong><br />
Authoring and Mapping<br />
■ Designing <strong>AUTOSAR</strong> interfaces for application<br />
software components (SWCs)<br />
■ Composing SWCs<br />
■ Integrating SWCs and compositions on the<br />
Virtual Function Bus (VFB)<br />
■ Assigning SWCs to ECUs (mapping)<br />
■ Network description, plus import of FIBEX,<br />
DBC, and LDF formats<br />
■ Assigning data elements to signals<br />
(buses, etc.)<br />
■ Configuration and generation of Runtime<br />
Environment (RTE)<br />
Basic Software Configuration/Generation<br />
■ Konfiguration und Generierung der CUBAS-<br />
■Softwaremodule Configuration and und generation des RTA-OS of CUBAS<br />
software modules and RTA-OS<br />
■■ New Components<br />
Tools for <strong>AUTOSAR</strong> component development.<br />
<strong>AUTOSAR</strong> interface concepts, such<br />
as Sender-Receiver, Client-Server, or<br />
Calibration Interfaces, for the modeling<br />
of <strong>AUTOSAR</strong>-conformant specifications.<br />
<strong>AUTOSAR</strong>- and ASCET-specific<br />
modeling concepts are fully integrated<br />
in the development user interface<br />
and can be used concurrently.<br />
In this way, the easy migration of<br />
existing models into an <strong>AUTOSAR</strong>-oriented<br />
software architecture is<br />
comfortably supported. From these<br />
<strong>AUTOSAR</strong> Software Components<br />
(SWC), MISRA-C-compliant, production-ready<br />
C code components and<br />
<strong>AUTOSAR</strong> XML description files can<br />
be automatically generated.<br />
As a matter of course, the generated<br />
<strong>AUTOSAR</strong> C code comes with the<br />
SWC Description<br />
SWC Description<br />
xy<br />
SWC 1 ... SWC n SWC 1 ...<br />
<strong>AUTOSAR</strong><br />
BSW<br />
xy<br />
<strong>AUTOSAR</strong><br />
RTA-RTE<br />
<strong>AUTOSAR</strong> Basic Software<br />
CUBAS (ICC3 Level)<br />
appropriate access macros. The<br />
macros of the compiler abstraction<br />
are configurable. In addition, the import<br />
of existing <strong>AUTOSAR</strong> XML description<br />
files is supported by ASCET<br />
and facilitates their seamless integration<br />
in <strong>AUTOSAR</strong> development<br />
processes.<br />
Basic software plus configuration and<br />
generation tools<br />
For many years, <strong>ETAS</strong> has been collecting<br />
an immense knowledge related<br />
to automotive operating systems.<br />
These experiences are reflected<br />
in both the <strong>AUTOSAR</strong> operating<br />
system RTA-OS and the real-time environment<br />
RTA-RTE. Complemented<br />
by the <strong>AUTOSAR</strong> Basic Software<br />
CUBAS – which is developed and<br />
ASCET<br />
<strong>AUTOSAR</strong><br />
Code generation<br />
ECU Network<br />
ASCET<br />
SWC n<br />
<strong>AUTOSAR</strong><br />
RTA-OS ASCET Function Model<br />
deployed by the Bosch Group – <strong>ETAS</strong><br />
offers a comprehensive portfolio of<br />
operating system software modules.<br />
Optimized for memory usage and<br />
runtime requirements, and proven in<br />
numerous projects, the CUBAS modules<br />
are being further developed in<br />
accordance with the <strong>AUTOSAR</strong><br />
roadmap. The configuration of the<br />
ECU basic software can be effected<br />
by means of another tool called<br />
ISOLAR-B. It accomplishes this purpose<br />
by making use of the <strong>AUTOSAR</strong><br />
ECU Extract provided by ISOLAR-A.<br />
Going beyond their usefulness for<br />
production ECUs, the operating system<br />
RTA-OS and RTA-RTE Runtime<br />
Environment can be used for function<br />
validation already during the early<br />
<strong>AUTOSAR</strong><br />
Authoring<br />
Behavior<br />
Modeling<br />
Behavior<br />
Modeling<br />
<strong>AUTOSAR</strong><br />
Mapping<br />
phases of development. Using the<br />
INTECRIO prototyping environment<br />
in conjunction with RTA-RTE and<br />
RTA-OS opens the door to virtual<br />
(PC-based) prototyping of <strong>AUTOSAR</strong><br />
SWCs and non-<strong>AUTOSAR</strong> SWCs<br />
from a variety of sources. For purposes<br />
of real-time behavior analysis<br />
and monitoring, RTA-TRACE slips<br />
neatly into place.<br />
Services<br />
In addition to its product portfolio,<br />
<strong>ETAS</strong> provides a broad spectrum of<br />
services covering all aspects of<br />
<strong>AUTOSAR</strong>. The coverage of training<br />
classes ranges from <strong>AUTOSAR</strong> basics<br />
to <strong>AUTOSAR</strong> Basic Software CUBAS,<br />
to <strong>AUTOSAR</strong>-conformant tools such<br />
as ISOLAR, INTECRIO, or ASCET.<br />
Code<br />
Generation<br />
Code<br />
Generation<br />
<strong>AUTOSAR</strong><br />
Configuration<br />
<strong>AUTOSAR</strong><br />
RTE<br />
Configuration<br />
<strong>ETAS</strong> is Premium Member of the <strong>AUTOSAR</strong> Development Partnership<br />
■■ <strong>ETAS</strong> Basic Software and Tools<br />
■■ Third Party Offer<br />
<strong>ETAS</strong> Solution Setup Services support<br />
the setup and rollout process of the<br />
<strong>AUTOSAR</strong> Basic Software CUBAS as<br />
well as <strong>ETAS</strong> tools on the customer’s<br />
premises. This facilitates the smooth<br />
interaction between <strong>ETAS</strong> tools and<br />
the customer-specific development<br />
environment, and/or tools from thirdparty<br />
vendors. The Integration Services<br />
for MCAL modules, boot loader<br />
or customer-specific <strong>AUTOSAR</strong> modules<br />
further enhance the portfolio<br />
with services with a direct relation to<br />
embedded software.<br />
Customization Services, i.e., the development<br />
of customer-specific extensions<br />
or adaptation of existing<br />
<strong>ETAS</strong> tools, as well as the custom<br />
development of <strong>AUTOSAR</strong> modules<br />
RTE<br />
OS<br />
Generator<br />
BSW<br />
Generators<br />
<strong>ETAS</strong> IS COMMITTED TO <strong>AUTOSAR</strong><br />
SWC.c<br />
ASW<br />
SWC.c<br />
RTE.c<br />
OS.c<br />
BSW.c<br />
SW<br />
Integration<br />
Make/Build<br />
(e.g., Complex Driver) are also<br />
offered. Also available are <strong>AUTOSAR</strong>conformant,<br />
microcontroller-specific<br />
boot loaders and OS ports.<br />
Operational support for the use of<br />
segments or the entire <strong>AUTOSAR</strong> tool<br />
chain round out the comprehensive<br />
<strong>ETAS</strong> portfolio.<br />
Prototyping Target<br />
PC<br />
ECU<br />
ECU<br />
13<br />
<strong>AUTOSAR</strong>-conformant tools from <strong>ETAS</strong>.