DaVinci Developer 4.0.22 SP2

Contains the complete installation of DaVinci Developer 4.0.22 (SP2). For the operation a license of version 4.0 or higher is necessary. In case an according license is already activated on your PC no further renewal of this activation is necessary. This release is only relevant for AUTOSAR 4. AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.


This release will upgrade existing DaVinci DEV 3.x workspaces to a newer format.

For creating/updating projects with DaVinci Configurator, the latest service pack of the according DaVinci Configurator 5 version is required.

With SP2, the following changes become effective:

Usability Enhancements

  • Multiple elements can be selected and moved to another package in the Object Browser
  • Platform development functions can be assigned to multiple elements at once
  • Instead of converting a DaVinci DEV 3.x workspace the referenced ARXML files are loaded if it is referenced by a DEV 4.x workspace
  • DaVinci DEV reports if elements in the same package have the same name but are of different types and does not silently ignore one of the elements
  • System properties like "Extract Version" and the DPA file path are available in the root composition's properties dialog

Fixed Issues

  • Loading a workspace failed with an exception if it includes variation points
  • Multiple component prototypes with identical names could be created
  • A package configured as default package could be deleted
  • Select and New buttons were disabled in the Per-Instance Memory editor
  • An invalid ARXML file was saved when configuring or importing a data mapping with complex application data types
  • It was not possible to create a new data mapping if the workspace did not already contain a data mapping
  • Component prototypes of type complex device driver were not imported
  • Opening the admin data editor failed with a File Load exception
  • The 'Create PortPrototype from Signal' command was not executed
  • Service needs were not imported from ARXML files
  • Files containing references to an element moved to another package were not saved, resulting in "unresolved references" when opening the workspace again
  • The "substitute missing objects" import option was ignored during ARXML import
  • Changing the zoom factor on the Graphic ribbon had no effect
  • Command line tool DVImEx.exe did not report that it can't handle DaVinci DEV 3.x workspaces but failed with code 0x80004003
  • Command line tool DVImEx.exe aborted with "values are restricted to types representing a config type"
  • Existing CompuScale was not updated correctly during ARXML import
  • Validation messages of the pre-generation model check were not shown when generating the Contract Phase header or implementation template files
  • Data mappings were not written to the workspace file
  • DaVinci DEV created ARXML files with an AUTOSAR version which is not supported by the used DaVinci Configurator yet
  • Invalid ARXML files, caused by various incorrect element references, were created, e.g. when configuring a mode access
  • DaVinci Configurator was not able to detect all modified files after DaVinci DEV saved its workspace
  • Consistency check message #40242 'invalid queue length' was shown (DaVinci DEV 3.x did not report that message)
  • Data type mapping sets were not imported
  • Invalid ARXML files containing too long short names were created
  • Invalid ARXML files containing elements of later AUTOSAR versions were created
  • Files with duplicate element names were created, e.g. for connections
  • Additionally merged issues from service packs of previous releases:
    • Explicit platform development function annotations defined with DaVinci Developer were not visible in DaVinci Configurator
    • Compatibility check of constants wasn't correct if both ConstValueSpecs were of type application
    • DCF workspace of a DPA project contained obsolete proprietary communication objects that result in duplicate short-names errors
    • When exporting an ApplicationDataType array the DynamicArraySizeProfile: 'None' was falsely exported
    • Special import (Overwrite import mode preset) aborts with the error "The transformation of this item is not supported" if any component type is specified in the import file
    • When using Data-Transformation an obsolete check throws #40402 "Multiple operation mappings of network signal" if a signal was multiply mapped to a client ECU delegation port
    • If the workspace referenced a platform development function file the project update aborts with (FatalError: 0xC0500001 - Reason: Could not load the workspace)
    • The inplace attribute wasn't shown when showing the End-To-End transformation technology (e.g. from Signal large data)
    • The ECU communication wasn't updated correctly, if a signal was moved from one PDU to another PDU
    • The predefined application and service port interface files contained objects with identical UUIDs
    • The transformer settings at a port prototype Com-Spec were lost
    • The category of a AppValueSpecification wasn't correctly imported/exported which causes data loss on roundtrip
    • The consistency check #40314 and #40316 referenced obsolete AUTOSAR constraints
    • If the range of a CompuScale wasn't set (Category LINEAR or SCALE_LINEAR) it was always imported as default with 0..255
    • Project update aborted with error: "Unable to find ECU-Project for update. (code 0xC0500012)" if the ECU-Project has a different name than the DPA Project
    • Project update aborted with error: "Internal exception occurred: Object reference not set to an instance of an object. (code 0x80004003)" if substitute missing objects was used and the ECU Top-Level Composition wasn't part of the input files
    • The import of a tx "Ack Only" runnable data access was invalid and results in check #30058 "Incompatible runnable data access detected."
    • Texttable couldn't be mapped on a boolean implementation type and results in consistency check #40338 "Inconsistent data type mappings"
    • Creating a new Application Constant from within the Reference Constant dialog resulted in a wrong created data type
    • SWC import throws error "could not access element" if the service dependency (e.g. a diagnostic control IO need) referenced another element (e.g. a diagnostic event need).
    • ARXML import removed a Runnable Data Access if a referencing Variable Data Prototype was renamed in the imported ARXML file
    • Description for nested data types was incorrectly stored when saving a workspace.
    • An invalid Port Terminator was not removed by the workspace check
    • If a Port Interface had several Data Elements, the multi-edit function for Com-Spec settings on a SWC was not working
    • DCF workspace with a single tx ack only runnable access couldn't be opened anymore
    • DCF workspace with an unnamed runnable mode switch point couldn't be opened anymore


  • The GUI is not always updated immediately when editing the model in different editors. Close and re-open the editor or view to update the displayed data.
  • Some standard functionality like Copy&Paste, Drag&Drop is not available in all views


Size : 221.43 MB
MD5 hash : 38173530fb2d7f04973b0fef25408d6b
Download now Previous