Contains the complete installation of DaVinci Developer 3.10.50 (SP5). For the operation a license of version 3.10 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.
With Service Pack 5 (Update to 3.10 Build 50) the following changes become effective:
Additionally merged tool features from service packs of previous releases:
Various Diff/Merge extensions to support sub-elements e.g. internal behavior
Additionally merged usability enhancements from service packs of previous releases:
Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted
Additionally merged issues from service packs of previous releases:
When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
Contract phase generation couldn't be used at the ECU-Project
Crash during SWC check on runnable data accesses by value has been fixed
Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
In some cases a double click on a .dcf file started the wrong DaVinci Developer version
Create port from signal didn't create correct init values in all cases
Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
A component type DCF file accidentally contained data constr elements
Init value constant contained duplicate record elements after merge
GUI crashed when calling "Show in other views" on a found object
Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component