The AUTOSAR standard is founded on the ability to bring software vendors together to co-operate so they can efficiently produce ECU software. The software is made up of applications, software components (SW-Cs), hardware support through MCAL and the ECUs custom device drivers, which are all joined together by the basic software (BSW). Capital VSTAR adheres very closely to the AUTOSAR methodology and includes native support for the AUTOSAR model. Tool features like configuration splitability greatly simplifies the separation of concern between ECU SW developers.

The configuration of the AUTOSAR BSW enables the correct execution of applications in the vehicle system, where data and resources may be either on the same ECU or on distributed ECUs around the vehicle or even in the cloud. The definition of the application’s data and execution requirements, as well as the data exchanged with the system, is described in the configurations provided by the application and network design tools. Capital VSTAR Integrator fuses the input data from these sources and, through the rules-based generation process, the tool resolves the system dependencies and generates the basic software configuration. For the parts of the ECU configuration that cannot be described in the exchange format, and to complete possibly missing data from upstream tooling, our solution provides additional wizards, smart panels, and guided workflow to help engineers finalize the ECU configuration. It also has the necessary features to do application authoring in case applications are provided without the required AUTOSAR descriptions. In the situation that software components (SW-C) are to be coded by hand or by a tool that does not support AUTOSAR, the Capital VSTAR run-time environment generates the SW-C API based on the provided SW-C description.