DaVinci Developer 4.2.28 SP1

Categoria : Service Pack
Dimensioni : 235.49 MB
Hash MD5 : 3fcb3975533616c8a24a06c926f50c3e

Contains the complete installation of DaVinci Developer 4.2.28 (SP1). For the operation a license of version 4.2 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.

NOTE

This release is only relevant for AUTOSAR 4.
AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

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.1 is only available as a 64-bit executable, i.e. Windows 32-bit is no longer supported.

Usability enhancements

  • ARXML import and workspace loading performance has been increased
  • The text of consistency check 40116 now shows the component type where the runnable name clash occurred
  • Find results view now offers a delete command
  • Performance of whole workspace check has been increased
  • Keyboard shortcuts for find (Ctrl-F) and properties (Alt-Enter) are now supported
  • The HTML report now contains the description of internal behavior elements
  • The error message when entering an invalid A2L display format string was improved

Fixed issues

  • Since comparison mode cannot handle duplicate UUIDs, starting of the comparison is now prevented if duplicate UUIDs exist
  • Error message "Could not delete item" appeared in on ARXML import if SerivceNeeds or RoleBasePortAssignments of service were modified by the import
  • The workspace option "Delete Unreferenced DCF Files" was ignored and the unreferenced files still remain existent
  • DVImEx command line didn't support all element types, e.g. SwAddrMethod
  • End-to-End protections were not stored in the ECU-Project if the E2EProtectionSet was contained in a read-only file
  • It wasn't possible to rename a Component-Type or Port-Prototype if the new name only differed in the upper/lower case
  • Waiting accesses were falsely imported as polling
  • Runnables referring a selected platform function were not shown in the find result view
  • Data elements were shown twice if they were also referenced by an invalidation policy
  • DVImEx command line help didn't display the -p option to import packages from file
  • Async return mode unexpectedly changed from 'POLLING' to 'NONE' when importing with overwrite option
  • In some cases, the implicit function mappings were not computed correctly for port-prototypes and exclusive areas
  • Data mappings were not imported during project update if a signal or signal group was transformed by a transformer
  • DiagEventNeed's Debounce Algorithm wasn't correctly stored or exported to ARXML
  • ARXML import failed with 'Error while deserializing file...' if the file contains duplicate elements with lists of primitive types
  • Files without content were not removed from dcf file list
  • The 'Propagate alive timeout' functionality only updated the ECU delegation ports but not the connected ports within the ECU-SW Composition
  • DVImEx command line reported error 'object reference not set to an instance of an object' if the file contained a port interface mapping set and the elements were imported into default packages
  • Obsolete default import options could be configured and were applied on import although they weren't supported anymore
  • The GUI didn't always resemble the correct read-only state for child items when the parent and child items were loaded from different files
  • Invalid package names were not reported by the consistency check 40065
  • Port-Interface could be deleted even if an interface mapping existed
  • Error dialog occurred when saving the workspace if a file from a different drive was added in the file browser
  • Children of complex data types with category 'VALUE' weren't imported correctly
  • During DaVinci Configurator project update the unresolved references dialog accidently appeared
  • DCF file with duplicate file refs was created if a component type was imported with the same name than an existing component type file.
  • Error dialog was shown when modifying a component type if no implementation name or package was set
  • Renaming of an ARXML didn't work in the file browser
  • 'Sort Ports Ascending' command was disabled in Graphic Ribbon Tab if multiple ports were selected
  • If a data type with circular references was selected the application froze in an endless loop
  • Comparison mode wasn't started correctly when using DaVinci Configurator Pro older than version 5.17

 

Scarica ora pagina precedente