- AUTOSAR Builder
- RT Builder
- Customers Portal
Tool Suite Overview
Open and flexible Solution for Designing, Verifying and Configuring AUTOSAR Applications and Systems
AUTOSAR Builder is a comprehensive software platform for system and
ECU design. It enables also to import Model-Based Design legacy
description and to generate Autosar compliant C code, ready to be
embededded on target ECUs. The AUTOSAR Builder tool suite includes:
AUTOSAR Authoring Tool (AAT) with an ECU extract capability and a SWC Conformance Validator
Generic ECU Configuration Editor (GCE) with a Configuration Code Generator
RTE Generator (RTEG)
AUTOSAR Simulation (ASIM) covering the VFB level, the ECU level and soon the Network level.
AUTOSAR Re-targeting Tool (ART) to migrate a Model Based Design description from Simulink to AUTOSAR.
AUTOSAR Builder is
based on Artop (www.artop.org). Artop is
an open AUTOSAR tool environment that is available free of
charge. It enables to build your own tools and integrate with
tools from other tool vendors. The AUTOSAR Builder plug-in
tool suite addresses
the successive steps in the different phases of the AUTOSAR design
enables engineers to easily undertake the various associated design
The AUTOSAR Builder plug-in tool suite includes an AUTOSAR Authoring Tool (AAT), ECU Extract, Software Component Conformance Validation Tool (SCVT), Generic ECU Configuration Editor (GCE) and AUTOSAR RM for AUTOSAR BSW requirement management.
AAT: AUTOSAR Authoring Tool
Based on a substantial subset of the AUTOSAR meta-model, the AAT facilitates the creation of AUTOSAR SW-C, ECU and System descriptions at the applications level. It represents the description data organized in templates and ARPackages. For each AUTOSAR element the properties are shown in Forms and 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 realize the tedious task of creating AUTOSAR standard descriptions.
EEX: ECU Extract
ECU Extract (EEX) is a companion feature of the AAT module, which allows the user to extract a single ECU specific description from the overall vehicle description, in complete compliance with the AUTOSAR methodology and specification.
ART: AUTOSAR Retargeting Tool for Automatic Code Generation
The new ART module delivers substantial productivity benefits through the automatic generation of AUTOSAR-compliant C code that is ready to be embedded on target ECUs, from both new and legacy MATLAB/Simulink models using RTW.
The ART methodology is a two-fold process – import and generate. The importation process directly integrates MATLAB/Simulink models into AUTOSAR Builder enabling mapping between systems/sub-systems and SW-C/runnables. Once the mapping between the top level ARElements, which describe the AUTOSAR application and Simulink elements is complete, the new ART module automatically generates the SW-C templates and re-targeted AUTOSAR C code ready to be embedded on target ECUs.
In conjunction with AUTOSAR Builder’s companion ASIM simulation module, which provides a validation and verification solution for AUTOSAR systems, the new ART module can be used to provide a guarantee of the correctness of the AUTOSAR architecture coming from MATLAB/Simulink, through a VFB simulation of the entire architecture. The simulation can re-use existing MATLAB/Simulink test cases imported into the ART project workspace to automatically test the functional application mapped to the AUTOSAR architecture
ASIM: Validation & Verification of AUTOSAR Systems on a PC
ASIM for AUTOSAR Builder provides a comprehensive, PC-based solution for validating and verifying AUTOSAR systems early in the development cycle. It solves the difficult challenges of validating and verifying an AUTOSAR-compliant system design, enabling design issues to be identified and addressed early in the development cycle, improving quality, saving time and reducing costs.
ASIM for AUTOSAR Builder operates at the Virtual Functional Bus (VFB) and ECU levels. Network level simulation is under development.
ASIM for AUTOSAR Builder’s VFB-level simulation capability facilitates the validation and verification of AUTOSAR Software Components (SWCs) independently of any hardware constraints and topology mapping. It focuses on the higher level of functional behaviour of applications within the context of three layers of abstraction – the interface definition, behaviour definition and implementation definition. For the interface definition layer, the ports and associated interfaces of an SWC that enable communication with other SWCs and underlying Basic Software (BSW) services are validated and verified. For the behavioural layer, the “runnables” in terms of real-time properties and execution semantics such as scheduling, triggering and activation sources are validated and verified. The implementation layer deals with the validation and verification of resource consumption.
ASIM for AUTOSAR Builder’s ECU-level simulation capability facilitates the validation and verification of specific ECU implementations as part of a hardware topology. The use of AUTOSAR’s underlying standard BSW services, such as the ECU State Manager, the NVRAM Manager and the Communication Manager, by an SWC to fulfil specific tasks can significantly affect the functional behaviour of the SWC requesting them as well as highlight non-functional flaws due to implementation artefacts. ECU-level simulation enables their impact to be thoroughly assessed.ASIM for AUTOSAR Builder’s Network-level simulation will facilitate the validation and verification of multiple SWCs and ECUs within the context of an entire system topology including network data.
SCVT: Software Component Conformance Validation Tool
Functioning at the applications level, the SCVT verifies 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.
GCE: Generic ECU Configuration Editor
The 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; it 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.
AUTOSAR-RM is a dedicated plug-in built upon Geensys’s requirement management tool Reqtify; AUTOSAR-RM helps navigate the multi-level, highly populated, AUTOSAR requirements. Furthermore, it extracts and consolidates - for a dedicated AUTOSAR development project - the requirements, and only those, which are mandatorily relevant to the project. Next steps in the requirement management process are fulfilled by Reqtify which ensures traceability automation, coverage assessment and impact analysis of requirement changes along the entire development cycle.
AUTOSAR Builder 2010-1a