AUTOSAR development: Requirements and system-level design
Technical Session 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.
Beyond hardware: Automotive standards drive software reuse
Technical Session Growing complexity of software in automotive electronic control units has forced the industry to invest into software standardization activities such as AUTOSAR and GENIVI. These standards aim at enabling higher reuse of software at all levels of the software supply chain. In this changing environment semiconductor companies that in the past supplied hardware only are now also becoming an important part of the automotive software supply chain. In parallel each automotive segment has brought forward more demanding requirements: the ISO 26262 norm defines new requirements for functional safety, powertrain applications demand higher than ever MCU performance, and lower power consumption is needed in body and comfort applications. In this presentation Dr. Both will present the processes, competencies, product and service offerings Freescale has developed to meet these challenges.
Software development and virtual validation
Technical Session 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.
GENIVI and available components for IVI systems design
Technical Session This session will cover the work of the GENIVI organization, and range and scope of GENIVI components available for IVI systems design. Some are mature and released, while others are still in the specification and development stage. The GENIVI development process and technology roadmap will also be outlined. IVI and adjacent technology implementation architectures will be covered, using reference to the Mentor IVI Linux design solution.
Project experience: AUTOSAR 4.x processes at Volvo and BMW
Technical Session In this session you will learn about AUTOSAR processes at specific OEMs, e.g. how they deploy the AUTOSAR 4.0 specifications in their car projects, how they develop ECU’s in AUTOSAR 4.0, and how they are processing their software design on particular platforms. You will see which problems came up, how they have been solved and what we learned in these customer projects.