SOFTWARE TOOLS: Geensys' AUTOSAR Builder is first to comply with ARTOP specs - Embedded.com

SOFTWARE TOOLS: Geensys’ AUTOSAR Builder is first to comply with ARTOP specs

Stuttgart, Germany – Geensys has just released its AUTOSAR Builder, which it claims is the first AUTOSAR development tool to provide compliance with ARTOP ” the new AUTOSAR Tool Platform being established by the ARTOP User Group (ARTOP-UG) and recently launched to the AUTOSAR community.

Geensys is a founding Design Member of the ARTOP-UG, a group of licensed users of the AUTOSAR standard with a special interest in AUTOSAR compliant development tools, along with BMW Car IT, Continental and PSA Peugeot Citroen.

ARTOP UG's aim is to improve the quality and interoperability of AUTOSAR development tools and help eliminate the time lag between the release of new versions of the AUTOSAR standard and the availability of development tools that support the new specifications.

ARTOP-UG plans to achieve this through the creation of an infrastructure platform of the common base functionality and core features that need to be implemented in all development tools used to design and configure AUTOSAR-compliant systems and ECUs.

To accelerate ARTOP-UG's aims and objectives, Geensys has donated the code for the AUTOSAR TDK foundation of its AUTOSAR Builder development tool to the ARTOP-UG to form the basis of the ARTOP infrastructure platform, which itself sits on top of the Eclipse environment.

The Geensys donation helps to avoid redundant development of the non-competitive infrastructure platform by different tool vendors and supports a development process that allows for well-tested tools for all steps of the AUTOSAR methodology.

ARTOP Release 1.0 will provide support for AUTOSAR Release 3.0 although subsequent versions will contain support for other AUTOSAR Metamodel releases as well as support for handling different versions simultaneously. With ARTOP providing the basic building blocks that are typically required for realising AUTOSAR-related development tools, tool vendors can concentrate on developing the differentiating features and functionality of their tools that give them competitive advantage in the market.

AUTOSAR Builder provides an ARTOP-compliant design environment into which a suite of open-interface plug-in tools can be integrated for the creation of automotive electronics systems and ECUs compliant with AUTOSAR Release 3.0.

The AUTOSAR Builder tool suite addresses the successive steps in the different phases of the AUTOSAR design process and enables engineers to easily undertake the various associated design tasks.

It includes an AUTOSAR Authoring Tool (AAT), ECU Extract, Software Component Conformance Validation Tool (SCVT), Generic ECU Configuration Editor (GCE) and a soon to be announced system simulation plug-in for AUTOSAR applications.

The AUTOSAR Authoring Tool (AAT) is based on a substantial subset of the AUTOSAR meta-model, the AAT facilitates the creation of AUTOSAR Software Component (SW-C), ECU and System descriptions at the applications level. It represents the description data organised in templates and ARPackages.

For each AUTOSAR element the properties are shown in Forms. The Graphical Editor allows the elements to be displayed as diagrams as well as enabling the creation of new elements. Rule checking of all standard descriptions for AUTOSAR systems with automatic error correction prevents engineers from entering inconsistent or invalid data and notifies them of potential or committed errors.

The AAT provides practical assistance to the user to realise the tedious task of creating AUTOSAR standard descriptions. ECU Extract is a companion feature of the AAT that allows the user to extract a single ECU specific description from the overall vehicle description, in complete compliance with the AUTOSAR methodology and specification.

The Software Component Conformance Validation Tool (SCVT) functions at the applications level toverify the description of SW-Cs. It provides analysis based on description rules for SW-Cs, static analysis of application code and RTE code generated at the Contract Phase, verifying the coherence between SW-C descriptions and the associated code. It also provides reports on the analysis/validation of the code.

The Generic ECU Configuration Editor (GCE) facilitates the creation and configuration of Basic Software module parameters based on the AUTOSAR standard and methodology. It ensures strict conformance to the AUTOSAR specification and validation of all AUTOSAR rules and requirements.

The GCE is implemented as three separate plug-ins: The ECU Parameter Definition (EPD) plug-in is used to create or modify ECU parameter definitions and can also be used to create XML format parameter definitions for any other software module other than AUTOSAR BSW; the BSW Module Description (BMD) plug-in is used to create or modify BSW module definitions and configurations, by BSW vendors; and the ECU Parameter Configuration (EPC) plug-in is used to create or modify ECU parameter configurations and to integrate BSW module configurations, by system integrators.

To learn more, go to www.geensys.com

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.