English
MIPI C-PHY v1.2 D-PHY v2.1 TX 3 trios/4 Lanes in TSMC (16nm, 12nm, N7, N6, N5, N3E)
Standardizing data interchanges among design tools in the ECU development process: Pt. 1 - Models, formats, and data management
By Joachim Stroop, dSPACE GmbH
automotivedesignline.com (December 18, 2008)
Development tools that can process automotive electronics system models and description formats are becoming established. This article discusses the potential uses of data interchange in an AUTOSAR tool chain example.
The challenges in developing electronics systems for vehicles are greater than ever. Standards such as those of ASAM e.V. or the AUTOSAR initiative help to create a reliable basis for everyone involved in the development process. Among other things, there is an increasing need for system models and description formats that will cover all the aspects of an electronic control unit (ECU) or of an ECU network. While definition work on such formats is still going on, development tools that can process them are also becoming established. One example is the SystemDesk architecture design tool from dSPACE.
This article focuses on the question of what role these architecture-oriented tools play in the development process—for example, how they interact with tools for creating function models and how they integrate into various version control systems.
Introduction
With considerable commitment from numerous companies in the automotive industry, the AUTOSAR initiative has set out to pioneer a whole new basis for developing ECU software. The aim is to make software development much more efficient and flexible by using a standardized software architecture and standard data interchange formats for formal system models and for configuration data. The results of standardization work have now achieved high maturity, and further activities are planned.
At the same time, development tools that support the AUTOSAR standards and the proposed development methods are already available. These include SystemDesk and the AUTOSAR extension to TargetLink® the production code generator from dSPACE, and the configuration tool tresos® from Elektrobit (EB). These tools are already being used in industry's AUTOSAR projects. Experience gathered from these projects and further developments to the AUTOSAR standards will be worked into future versions of the tools.
automotivedesignline.com (December 18, 2008)
Development tools that can process automotive electronics system models and description formats are becoming established. This article discusses the potential uses of data interchange in an AUTOSAR tool chain example.
The challenges in developing electronics systems for vehicles are greater than ever. Standards such as those of ASAM e.V. or the AUTOSAR initiative help to create a reliable basis for everyone involved in the development process. Among other things, there is an increasing need for system models and description formats that will cover all the aspects of an electronic control unit (ECU) or of an ECU network. While definition work on such formats is still going on, development tools that can process them are also becoming established. One example is the SystemDesk architecture design tool from dSPACE.
This article focuses on the question of what role these architecture-oriented tools play in the development process—for example, how they interact with tools for creating function models and how they integrate into various version control systems.
Introduction
With considerable commitment from numerous companies in the automotive industry, the AUTOSAR initiative has set out to pioneer a whole new basis for developing ECU software. The aim is to make software development much more efficient and flexible by using a standardized software architecture and standard data interchange formats for formal system models and for configuration data. The results of standardization work have now achieved high maturity, and further activities are planned.
At the same time, development tools that support the AUTOSAR standards and the proposed development methods are already available. These include SystemDesk and the AUTOSAR extension to TargetLink® the production code generator from dSPACE, and the configuration tool tresos® from Elektrobit (EB). These tools are already being used in industry's AUTOSAR projects. Experience gathered from these projects and further developments to the AUTOSAR standards will be worked into future versions of the tools.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
Related Articles
- Managing the complexity of embedded software development through design automation tools
- Managing design data - consider the whole product
- Integrated Power Management, Leakage Control and Process Compensation Technology for Advanced Processes
- Take control of design data management
- From a Lossless (~1.5:1) Compression Algorithm for Llama2 7B Weights to Variable Precision, Variable Range, Compressed Numeric Data Types for CNNs and LLMs
New Articles
- Quantum Readiness Considerations for Suppliers and Manufacturers
- A Rad Hard ASIC Design Approach: Triple Modular Redundancy (TMR)
- Early Interactive Short Isolation for Faster SoC Verification
- The Ideal Crypto Coprocessor with Root of Trust to Support Customer Complete Full Chip Evaluation: PUFcc gained SESIP and PSA Certified™ Level 3 RoT Component Certification
- Advanced Packaging and Chiplets Can Be for Everyone
Most Popular
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- System Verilog Assertions Simplified
- Smart Tracking of SoC Verification Progress Using Synopsys' Hierarchical Verification Plan (HVP)
- Dynamic Memory Allocation and Fragmentation in C and C++
- Synthesis Methodology & Netlist Qualification