Contains the complete installation of DaVinci Developer 3.3.31 (SP2).
For the operation a license of version 3.3 or higher is necessary. In case an according license is already activated on your PC no further renewal of this activation is necessary. For the code generation the MICROSAR RTE 2.22 is required.
With Service Pack 2 (Update to 3.3 Build 31), the following changes become effective:
Cross-Importer is now available to import AUTOSAR 3 software components into an AUTOSAR 4 workspace.
End-to-End protection resynchronization flags are now supported for AUTOSAR schema 3.2.2 and 3.2.1.
Calibration communication specifications are now supported on Compositions, too.
Constant selection dialog now additionally displays the constant value.
Workspace format has now to be chosen explicitly when creating a new workspace.
Some consistency checks have been enhanced to detect usage of identical names that lead into Rte generation errors.
XML-Importer Output messages have been improved to display more context information.
Separate consistency message details dialog has been replaced by an in-place display in the messages tab.
"Save As..." did not work if .dev workspace file was set to read-only.
Consistency check ID 20013 was thrown on invalid argument prototype which was not visible in the GUI.
Cryptic open workspace message was shown in the action log when using DCF workspace in a DPA project.
Item information was missing in the data type unit check message.
Find functionality did not fully support AUTOSAR 4 types.
Obsolete menu entries appeared in AUTOSAR 4 design mode.
AUTOSAR 4 PARAMETER-PROVIDE-COM-SPEC was is not exported.
COM-Callbacks could not be configured depending on the 'enabledUpdate' setting.
Several problems concerning missing elements have been fixed in the AUTOSAR 4 import/export.
Crash in converting old .dev workspace fixed if inconsistent objects exist.
AUTOSAR 4 EcuAbstraction- or ComplexDeviceDriver were imported as services even if they used application ports.
AUTOSAR 4 import with "Substitute missing objects" didn't work with mode declarations.
For AUTOSAR 4 design the following functionality is currently not available:
Create Port Prototype from data mapping based on a given signal.
Adapt Data Type for Data Element based on a given signal.