Additional Topics

This section contains additional topics of the project migration for reference.

Input Files

Input files that were configured in the <Display> section of the DPA file are preserved and copied (in case a destination directory was provided as parameter for the migration tool, otherwise these files are not touched) to Input/Preprocessing for future reference (e.g. as CLI parameters), although they are not used directly by the DaVinci Configurator Classic Version 6.

Communication Extract

The DaVinci Configurator Classic Version 6 does not need to know any longer if a file contains communication extract data. In DaVinci Configurator Classic Version 5, the communication extract (<OEMCommunicationExtract>) was only loaded, if a DvDeveloper workspace was present, otherwise the ECU extract (<ECUEX>) was loaded into the model. In a migrated project, the same ARXML files are loaded, therefore either the communication extract or the ECU extract is referenced as harmonizedExtract in the ArxmlProjectContent.json:

{
    "harmonizedExtract": {
        "fileList": [
            "../Output/Config/EcuExtract/Communication.arxml"
        ]
    }
}

GenData Paths

In contrast to other directory configuration entries, the folders for <GenData> and <GenDataVtt> remain unchanged, if their configured value in the DPA file deviates from the default values (.\Appl\GenData or .\Appl\GenDataVtt). This allows an easier further processing of the generated files.

Script Locations

Script locations were configured in the DPA file in the <Misc> section of the <ToolSettings> in a setting named com.vector.cfg.automation.scripting.SearchLocations. Differing from what was described earlier, they are not located in Misc.json, but in General.json in a simplified JSON array scriptLocations:

{
    "scriptLocations": [
        "$(ProjectFolder)/scripts/build/libs/script.jar",
        "$(ProjectFolder)/scripts/build/libs/script2.jar"
    ]
}

User Code Block Data

User code block data files (with the file extensions .c.ucb and .h.ucb) are copied to the destination directory (if it was provided as program parameter).

Acknowledgement Data

Existing acknowledgements.dc files are not preserved unchanged in XML format, but are converted to JSON format and referenced from the .dvjson file, see also section [_content_of_setting_file_acknowledgements.json].

Replacement of Variables

Some configuration entries in the DPA file can contain variables like $(DpaProjectFolder). As there is no DPA file in DaVinci Configurator Classic Version 6 any longer and the term SIP has been replaced, the variables $(SipRootPath), $(DpaProjectFolder), $(DpaProjectFile) are replaced by $(BswRootPath), $(ProjectFolder), $(ProjectFile).

IDE and Editor Support

EditorConfig helps developers define and maintain consistent coding styles between different editors and IDEs. The file .editorconfig is created in the destination directory with DaVinci Configurator Classic Version 6 settings for ARXML and JSON files. ARXML Files with model parts that are editable in DaVinci Configurator Classic Version 6, are formatted according to the rules in this .editorconfig.

New Configuration Entries

Origin Tracing

The project migration tool also adds configuration entries to the JSON files that were introduced in the DaVinci Configurator Classic Version 6, for example for the origin tracing in General.json:

{
    "folders": {
        ...
        "trace": "../Output/Trace"
    }
}

LdCom Derivation Version

The LdCom derivation version was not available in the DPA of the DaVinci Configurator Classic Version 5, but in DaVinci Configurator Classic Version 6 it is configured in Ifp.json. Its value depends on the existence of LdCom in the initial ecuc and the AUTOSAR version of the harmonized extract.

Sample entry in Ifp.json:

{
    "derivation": {
        "ldCom": {
            "derivationVersion": "AR_4_4"
        }
    }
}