DaVinci Configurator Pro - Configuring AUTOSAR Basic Software

Option Continuous Integration (CI) provides an integration pipeline for automatic integration of Application Software (ASW) packages, controlled by a Gradle-based build system.

ASW developers and integrators benefit from shorter integration cycles.

Provides App Packages for Automatic Integration

• ECU ASW can be divided in different app packages, depending on function or feature development scope
• For each app package, integration decisions can be frontloaded via formalized integration instructions
• Prepares baseline with root configuration
• Provides a DaVinci project as basis for automatic integration of app packages
• Root configuration includes BSW configuration and may also include already integrated SWCs, available to all app packages

Performs Efficient, Stable and Reproducible Asw Integrations Automatically

• Integration pipeline automatically maps one or many app packages on MICROSAR basic software
• Provides automatic workaround for issues that result from isolation of SWCs, e.g. missing init values
• Standard workflow supports build for vVIRTUALtarget pro and vVIRTUALtarget basic emulation and provides build system integration for hardware target
• Customization of different integration steps possible
• Same pipeline configuration can be used for local execution on user’s PC, and for central execution on a build server
• Debugging and re-execution of builds via back-in-time feature
• Integration pipeline executes only steps, which need to be executed
• Starting re-build of previous builds from any intermediate step allows fast re-build, even with modified input data
• Detailed breakdown with all steps and status messages as well as possibility to analyze the intermediate step results reduces finding times in case of failed builds

Use in Different Build System Set-Ups

• Integrating option CI into existing build system for automatization of ASW mapping and BSW configuration
• Using option CI as primary build routine and extending integration pipeline by own Gradle® build steps
• Use CI tools like Jenkins to run the integration pipeline in scheduled ways, or as reaction on user commits
• Applicable for all MICROSAR 4 projects (release 22 or later)

The integration pipeline is able to call various other Vector tools. To benefit from the full functionality of option CI, further tool licenses may be required.

Please see the DaVinci Configurator Pro system requirements for details.

• Customized editors for integrating SWCs
• Assistance functions, e.g. to automatically link SWCs or to simplify task assignments of SWCs

Note: These functions are also enabled via a DaVinci Developer license. If you have a DaVinci Developer license, you do not need Option RTE for DaVinci Configurator Pro.

• Conveniently create BSWMD files with module, container and parameter definitions
• SDK (Software Development Kit) for developing your own validation rules and generators for C-code or SWC descriptions in ARXML format

• Develop System Description Scripts (Python 2.7)

  • Correction of input data at the level of System Description
  • Automatic execution of scripts during project update
  • Signature of the script files for execution with DaVinci Configurator Pro

• Develop Automation Scripts (Groovy)

  • Automation of various actions like editing of parameters, access to validation results or execution of solving actions
  • Assistant for easy setup of script projects
  • Debugging of scripts with tools like IntelliJ IDEA

  • Execution of script tasks via the user interface or via command line

• Note: The Option WF is only required for creation of scripts.
  Execution of scripts is possible with DaVinci Configurator Pro even without Option WF.