1 / 12

Target Mapping in a Multi-core Environment Results and Plans Erik Kamsties, Burkhard Igel

International Workshop on Challenges in Methodology, Representation, and Tooling for Automotive Embedded Systems, Berlin 2012. Target Mapping in a Multi-core Environment Results and Plans Erik Kamsties, Burkhard Igel FH Dortmund. Overview. Background AMALTHEA What is Target Mapping?

linda-cochran
Download Presentation

Target Mapping in a Multi-core Environment Results and Plans Erik Kamsties, Burkhard Igel

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. International Workshop on Challenges in Methodology, Representation, and Tooling for Automotive Embedded Systems, Berlin 2012 Target Mapping in a Multi-core Environment Results and Plans Erik Kamsties, Burkhard Igel FH Dortmund

  2. Overview • Background AMALTHEA • What is Target Mapping? • Details and Results • Multi-core CPU Target Platform • Damos and SCT Modeling • Projection of models • AUTOSAR • Tools • Case Study

  3. AMALTHEA Overview on Work Packages WP 5 WP 1 Continuous design flowand methodology WP 6 Dissemination and exploitation Target mapping WP 3 Definition of DSLs WP 2 Demonstrator Continuous tool chain platform WP 4 WP 7 Project management

  4. What is Target Mapping? Definition: Target mapping is the AUTOSAR-conformant projection of models of an automotive software system on a multi-core target platform. WP3 roadmap: • Select and utilize a multi-core platform for automotive systems • Select and extend a modeling technique and a respective tool for describing parallel systems • Develop a design flow to project models (2) to a target platform (1) • AUTOSAR conformance shall be ensured in the design flow (3).

  5. Multi-core CPU Target Platform • Requirements • Number and type of cores (>= 2 cores, symmetric cores) • Automotive I/Os: CAN, Flexray • Open/free tool chain • Popular multi-core CPUs for automotive embedded systems • Freescale MPC 55xx, 56xx series • Infineon TriCore, AURIX (multi-core TriCore) • Renesas ? • Within AMALTHEA: • Adopting codegenerator to chosenplatform

  6. Damos Modeling • Damos • part of Yakindu (open source, Eclipse-based tool chain, developed by itemis) • is a data flow-oriented modeling environment • includes a block diagram editor, simulator and C code generator • Within AMALTHEA • Partitioning data flow models, mapping to runnables/tasks • Generating AUTOSAR compatible C code (.arx files)

  7. SCT Modeling • SCT • part of Yakindu (open source, Eclipse-based tool chain, developed by itemis) • based on finite automata • includes hierarchical state chart editor (based on Harel statecharts), simulator and C code generator • Within AMALTHEA • Partitioning, mapping to runnables/tasks • Generating AUTOSAR compatible C code (.arx files)

  8. Projection of Models to the Platform itemis: AUTOSAR-conformantextensionofDamos TA/HSR: Refinementofagglomeration FhDO: PartitioningofDamosmodels FhDO: Metamodel, methods, andtool clab: AUTOSAR, scheduling, tracing ifak: scheduling, tracing TA/HSR: Generating a mapping BHTC: Prototypicalimplementationandevaluationoftargethardwareplatform t itemis: extensionofcodegenerator

  9. AUTOSAR • Within AMALTHEA, the overall goal is to support an AUTOSAR conformant model-based software development • Derived requirements • A model (e.g. Damos) describes the behavior of a software component (architectural modeling in not considered in WP3) • The code generator shall produce the respective AUTOSAR files (this implies that the meta model of the modeling technique is aligned to AUTOSAR) • AUTOSAR-OS has to be used • Regarding target mapping, the current version 4.0 R3 • permits only local instead of global scheduling • the schedulers of the different cores are required to be independent of each other • atomic software components (SWCs) can be mapped to cores only 1:1 • if memory protection boundary is used for a set of SWCs, all these SWCs must be mapped to the same core • Bottom line: current version 4.0 R3 is overly restrictive regarding multi-core aspects  extensions are required

  10. Tools • Yakindu Damos and SCT • Extending embedded code generators towards multi-core • The Damos code generator was adapted to the Arduino platform and a respective hardware model was created in order to collect experiences about generating hardware-dependent code. • Timing Architects Simulator/Optimizer • Early evaluation of performance attributes (e.g., real-time requirements) based on models of the software and the selected HW platform • For the mapping of tasks to cores a solution based on genetic algorithms is extended towards considering communication based influences and scheduling effects. • Tools for Creating Modeling Tools (DSLs) • Xtext/Xtend are employed

  11. Case Studies • Industrial case study 1: HVAC on the BHTC “Rapid Control Prototyping Box” • Utilizing MPC5668G evaluation board, redesign of current RCP box • Adaptation of Matlab tool chain (providing hardware abstraction layer, adaptation of Matlab/Simulink code generator templates) • Comparison of Matlab baseline and new open source tool chain • Case Study 2: Multi-OS on a multi-core system

  12. Links to MAENAD, SAFE, TIMMO-2-USE • MAENAD: • It is commonly accepted that parallelism which is introduced by multi-core processors should be addressed on higher level of design. Abstractions in modeling are sought which represent parallelism in systems. • SAFE • Multi-core processors are • beneficial, because they easily allow for redundancy (e.g., MPC 56xx lock-step mode) • introduce a number of issues, e.g. shared resources may lead to timing problems • TIMMO-2-USE • Timing information is required for the latter steps of the target mapping process (e.g., timing properties of the different tasks)

More Related