DaVinci Developer 4.9.22

Contains the complete installation of DaVinci Developer 4.9.22. For operation a license of version 4.9 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 4.9, the following changes become effective:

Tool features

  • Variant port connections are now supported; in postbuild-selectable projects a connection can now be assigned to a specific variant
  • The category of an NvBlockServiceNeed can now be configured; with this the use of an 'NvBlockComponent' or direct access via 'Service' can be expressed
  • Flat instance descriptors are imported and stored in the workspace to support the RTE Implementation Plugin (RIPS) feature
  • DVWspChecker optionally aborts if the workspace contains unresolved references
  • Rule based value specifications now support text value specifications

Usability enhancements

  • Check message #40369 "Inconsistent NvM port prototypes (API config class)" now contains additional information to identify the erroneous element more easily

Fixed issues

  • "Adapt Connected Port Prototypes" didn't allow to adapt ports in the software design hierarchy (top-down), e.g. for sender delegation ports
  • The DataConstraint properties dialog showed a value of "0" even though the value was not specified
  • The ModeRequestTypeMaps dialog showed the element name instead of the package path in the package column
  • ApplicationValueSpecifications of type "boolean" were interpreted as strings
  • The model check was aborted when a data type did not reference a base type
  • Duplicate UUIDs were exported for array application data types
  • Predefined service port interfaces contained invalid UUIDs
  • "Adapt Data Element to match Signal" did not adapt the init value
  • The ComSpec's queue length was not saved when the type was unqueued instead of queued
  • Deleting a port prototype did not cleanup related runnable trigger events
  • System and extraction version were not updated during project update
  • Text table value pairs were missing from the text table mapping dialog
  • ARXML import threw an exception when the same port interface with a different type already existed in the workspace

 

Tamaño : 250.67 MB
Resumen MD5 : ff71baa1a0f9ee3359525d1781487905
Descargar ahora pagina anterior