Contains the complete installation of DaVinci Developer 4.4.32 (SP2). For the operation a license of version 4.4 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 2 (Update to 4.4.32 SP2), the following changes become effective:
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. DaVinci Developer 4.4 SP2 is only available as a 64-bit executable, i.e. Windows 32-bit is no longer supported.
End-to-End Protection Configuration details are read-only if they are pre-configured in the DPA project's input files
Port Interface Mappings could not be evaluated by Cfg5 because they contained references of the wrong type
Adding a new Port Interface Mapping corrupted existing mappings
Init values of PR port prototypes were removed during ARXML import
The command line export did not export data mappings
ARXML export did not write references to the Mode Declaration Group Prototype at Mode Com Specs for AUTOSAR versions >= 4.1.2
Special diagnostic import deleted swc implementation settings like "Supports multiple instantiation"
Invalid ARXML files with empty XML tags were created, e.g. if a Data Type's "Type Emitter" was not specified
Connector names derived from data mappings could become too long, resulting in an invalid ARXML file
AUTOSAR 4.4 files were rejected as invalid if they contained AUTOSAR 4.4 specific elements
DEV crashed when selecting "Open Item..." in the "Exchange Data" grid of the Data Exchange Analysis view
Init values were reset when the component type realization was changed, e.g. from Application to Composition
Number formats 'binary', 'octal' and 'hexadecimal' were imported as is, resulting in incorrect model check messages
ARXML import created superfluous DataWriteCompletedEvents
"Create Port Prototypes" did not create Trigger Port Prototypes for Signals with size "0"
Complex to primitive Port Interface Mappings were stored incorrectly, resulting in error #56116 "Data Prototype Mapping inconsistent" in Cfg5.