Contains the complete installation of DaVinci Developer 4.3.18. For the operation a license of version 4.3 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 Version 4.3 Build 18, 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.3 is only available as a 64-bit executable, i.e. Windows 32-bit is no longer supported.
Application data type VAL_BLK is now supported by converting it into an array of uint8 during import
The 'IsService' flag of port interfaces can now be modified in the properties dialog and changed during import
Unresolved file references are now reported in the Action Log and the File Browser in case the .dpa references files which don't exist
Connectors can now be merged individually in comparison mode
Definition of Tx Acknowledgement on Sender-ComSpec has been simplified
The 'Create Port from Signal' function generated a data constr with an invalid range [0,0] in case the signal didn't reference a data constr and the encoding of the base type was 'boolean'
DaVinci DEV crashed when checking a workspace with unresolved references, e.g. when a port prototype's port interface is missing
The obsolete option 'Find unused elements after import' is now removed from the import dialogs
Check messages 40248/40249 were shown because of an incorrectly calculated init value
Check message 40248 was shown because the calculated physical init value was wrong if the physical value was greater than an unsigned 32bit integer
Exception was thrown when trying to open the port access view in the component type editor
Import of Nv Data Interfaces threw an exception if a port interface of another type (e.g. sender receiver) already existed and the child items had the same name
Import of a com axis data type failed with an exception if the com axis data type didn't specify a value for min axis points or max axis points
The unit reference of an application value specification was stored at the wrong AUTOSAR attribute
The name of a package wasn't updated on import when an import file contains the package name in a different upper/lower case spelling
Exception was thrown when trying to delete a port prototype from the ECU-SW Composition