Home Technical Events IESF Automotive (Detroit, MI)Technical Focus Areas IESF Focus: Network Design, Integration and AUTOSAR

IESF Focus: Network Design, Integration and AUTOSAR

Thursday, June 14, 2012, 7:30AM to 7:00PM, Dearborn, MI

See an AUTOSAR 4.0 system design being built at IESF 2012!

This track provides insight into how an AUTOSAR-based methodology can be used throughout the entire V-cycle from design to configuration to implementation and test.

The AUTOSAR standard benefits automotive electronic and SW designers by increasing productivity and improving quality of designs. However, the standard doesn’t necessarily simplify the design process. Development of SW, electronics, and communication systems is a process spanning multiple abstraction levels by distributed development teams across an organization.

Topics covered include:

SW development
ECU SW implementation

Configuration & basic software integration
Testing of prototype ECUs

Don't miss these Network Design, Integration and AUTOSAR General Sessions

Approaches to Early Validation of AUTOSAR Functions
Serge Leef, Vice President and General Manager, System Level Engineering Division, Mentor Graphics
Mecel Enables Volvo Cars to Become First OEM to Introduce AUTOSAR 4.0
Rolf Hagstedt, Business Manager PICEA, Mecel AB Jörgen Tryggvesson, Product Line Manager PICEA, Mecel AB

Now in its 12th year, the Integrated Electrical Solutions Forum (IESF) will deliver more than 40 information-packed sessions addressing design challenges and solutions in the automotive, truck, off-highway and military vehicle industries. Attend FREE by registering now!

Network Design, Integration and AUTOSAR sessions at IESF 2012

12:50PM - 1:25PM	AUTOSAR Development (Part 1): Requirements and system-level design Presented By: Hans-Jürgen Mantsch, Automotive Networking, Mentor Graphics This session focuses on the first steps in the development of an AUTOSAR example system, starting from requirements, defining the SW architecture and the ECU/network topology, allocating SW to ECUs, and ending with communication design. We will see how Volcano VSA is used to architect the system, allocate functionality, and design the communication matrix. This includes validation against timing requirements and consistency checking of the entire design before generating AUTOSAR ECU extracts, which will be the input to next phase of the design process. In addition, this session shows how the Volcano VSx tool chain can be used in large projects with distributed, iterative development and gradually increasing functionality, leading up to increased efficiency of development throughout the supply chain.

12:50PM - 1:25PM

AUTOSAR Development (Part 1): Requirements and system-level design

Presented By: Hans-Jürgen Mantsch, Automotive Networking, Mentor Graphics

This session focuses on the first steps in the development of an AUTOSAR example system, starting from requirements, defining the SW architecture and the ECU/network topology, allocating SW to ECUs, and ending with communication design. We will see how Volcano VSA is used to architect the system, allocate functionality, and design the communication matrix. This includes validation against timing requirements and consistency checking of the entire design before generating AUTOSAR ECU extracts, which will be the input to next phase of the design process. In addition, this session shows how the Volcano VSx tool chain can be used in large projects with distributed, iterative development and gradually increasing functionality, leading up to increased efficiency of development throughout the supply chain.

1:30PM - 2:05PM	AUTOSAR Development (Part 2): SW development and virtual validation Presented By: Joachim Langenwalter, Director - Automotive Networking, Mentor Graphics Application SW development in an AUTOSAR context means that algorithms are partitioned into connected SW components, which in turn contain executable functions (called runnable entities in AUTOSAR). This structured definition of how the application SW is partitioned and executed enables simple relocation and reuse of application SW components inside or between ECUs. It also includes what can be called virtual validation – execution and verification of the SW components individually or in a system using a typical PC. However, to reach these benefits the application SW components require a detailed model description that can only be designed with appropriate tools. In this session we will see how to refine the system-level design from the previous session into detailed SW implementation for a selected set of SW components. We will define the internal structure of SW components and execute the SW components on top of a real AUTOSAR operating system in order to verify functional correctness.

1:30PM - 2:05PM

AUTOSAR Development (Part 2): SW development and virtual validation

Presented By: Joachim Langenwalter, Director - Automotive Networking, Mentor Graphics

Application SW development in an AUTOSAR context means that algorithms are partitioned into connected SW components, which in turn contain executable functions (called runnable entities in AUTOSAR). This structured definition of how the application SW is partitioned and executed enables simple relocation and reuse of application SW components inside or between ECUs. It also includes what can be called virtual validation – execution and verification of the SW components individually or in a system using a typical PC. However, to reach these benefits the application SW components require a detailed model description that can only be designed with appropriate tools. In this session we will see how to refine the system-level design from the previous session into detailed SW implementation for a selected set of SW components. We will define the internal structure of SW components and execute the SW components on top of a real AUTOSAR operating system in order to verify functional correctness.

2:10PM - 2:45PM	AUTOSAR Development (Part 3): ECU design and configuration using AUTOSAR Basic Software Presented By: Niklas Amberntsson, Automotive Networking, Mentor Graphics After the system-level design is completed and the SW development is at least initiated, the ECU design and configuration can start. The task is to configure the AUTOSAR Basic SW (BSW) modules to operate according to the needs of the application SW. The AUTOSAR BSW provides a complete embedded SW platform, with services such as task scheduling, memory protection, NVRAM management, communication, diagnostics, cryptographic services, etc. – more of less every service the application SW of an automotive ECU needs. Configuring an ECU’s BSW can be complex and error prone unless supported by adequate tooling and the appropriate methodology. In this session we will see how to configure the BSW of the ECU according to the needs of the application, using input from the previous design steps. We will demonstrate the power of a top-down development approach combined with design automation for the ECU configuration task.

2:10PM - 2:45PM

AUTOSAR Development (Part 3): ECU design and configuration using AUTOSAR Basic Software

Presented By: Niklas Amberntsson, Automotive Networking, Mentor Graphics

After the system-level design is completed and the SW development is at least initiated, the ECU design and configuration can start. The task is to configure the AUTOSAR Basic SW (BSW) modules to operate according to the needs of the application SW. The AUTOSAR BSW provides a complete embedded SW platform, with services such as task scheduling, memory protection, NVRAM management, communication, diagnostics, cryptographic services, etc. – more of less every service the application SW of an automotive ECU needs. Configuring an ECU’s BSW can be complex and error prone unless supported by adequate tooling and the appropriate methodology. In this session we will see how to configure the BSW of the ECU according to the needs of the application, using input from the previous design steps. We will demonstrate the power of a top-down development approach combined with design automation for the ECU configuration task.

3:10PM - 3:45PM	AUTOSAR Development (Part 4): Early testing of AUTOSAR-based ECUs and subsystems Presented By: Joachim Langenwalter, Director - Automotive Networking, Mentor Graphics One of the AUTOSAR standard’s key points is to enable reuse of application SW, which leads to shorter development time and enables early validation of software components in the virtual environment. But when it comes to validation in the physical environment, connecting to real sensors/actuators, and communicating with real ECUs, the availability of the ECU HW is often a limiting factor, especially given the fact that the HW development is typically initiated by an ECU supplier company only after being nominated for a project. In addition to the virtual validation of software components provided by Mentor Graphics’ VSI tool, an interesting and fully compatible alternative or next step is to use a rapid prototyping ECU such as the MBtech Virtual AUTOSAR Platform (VAP): a highly configurable system based on industry PC standards and equipped with AUTOSAR BSW and tooling from Mentor. The VAP can be used to validate the complete ECU’s functionality, from its application SW via the AUTOSAR BSW to real sensor/actuator or communication interfaces. In this session we will see how the VAP prototype ECU can be used for proof of concept, validating ECU configurations and integration with real ECUs.

3:10PM - 3:45PM

AUTOSAR Development (Part 4): Early testing of AUTOSAR-based ECUs and subsystems

Presented By: Joachim Langenwalter, Director - Automotive Networking, Mentor Graphics

One of the AUTOSAR standard’s key points is to enable reuse of application SW, which leads to shorter development time and enables early validation of software components in the virtual environment. But when it comes to validation in the physical environment, connecting to real sensors/actuators, and communicating with real ECUs, the availability of the ECU HW is often a limiting factor, especially given the fact that the HW development is typically initiated by an ECU supplier company only after being nominated for a project. In addition to the virtual validation of software components provided by Mentor Graphics’ VSI tool, an interesting and fully compatible alternative or next step is to use a rapid prototyping ECU such as the MBtech Virtual AUTOSAR Platform (VAP): a highly configurable system based on industry PC standards and equipped with AUTOSAR BSW and tooling from Mentor. The VAP can be used to validate the complete ECU’s functionality, from its application SW via the AUTOSAR BSW to real sensor/actuator or communication interfaces. In this session we will see how the VAP prototype ECU can be used for proof of concept, validating ECU configurations and integration with real ECUs.

Conference guide

Supporting Organization

Media Sponsor

Premier Partner