DaVinci Developer 3.13.75 SP7

Categoria : Service Pack
Tamanho : 173.78 MB
MD5 hash : 3d8ec717f167dcbd8f932453fc9dc638

Contains the complete installation of DaVinci Developer 3.13.75 (SP7). For the operation a license of version 3.13 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.


Tool features

  • 1:N Sender/Receiver communication without unique init values is now supported

  • ApplValSpecification of category 'Boolean' is now supported instead of using an Enum type

Usability enhancements

  • The consistency check for double data-mapped signals is now available for Client/Server and Trigger ports as well
  • A new consistency check #40490 has been added to ensure that a valid input variable type is set at the Application Axis
  • Propagation of init values to connected ports was enhanced for textual and reference values
  • Check message #40453 has been improved because an invalid constant reference was reported, but it wasn't possible to associate it to an object for nested constants

Fixed issues

  • In some cases the GUI created a PortAPIOption at the port prototype although it wasn't configured
  • The data mapping view falsely showed that a signal was assigned to multiple frames if the signal was part of a signal pdu which was part of a secure pdu
  • Stable ARXML writing order couldn't be ensured for postbuild variant projects
  • Consistency checks didn't detect invalid configured values of Record- and Array-Element constants
  • In case of connected PR-Ports containing multiple data elements the PortInterface Mapping information wasn't generated correctly in the Rte
  • Project update didn't finish in case of a pdu reference loop
  • Check message text #40320 was misleading for a compu-method of category 'Linear'
  • Variant signals are not displayed in the Data Mapping view if the ECU-Extract contained multiple ecu instances where a subset contained identically named communication connectors
  • The Data Exchange Analysis didn't handle ModeAccess and ModeSwitchAccess
  • The trigger interface dialog didn't perform standard checks like missing short name
  • External Trigger mapping consistency checks were incomplete
  • The check message #40438 wasn't removed from the messages tab after the condition has been solved and a new check was executed
  • In rare cases the composition port connections couldn't be found during a consistency check and were not checked
  • An invalid ARXML file was created if a PR port was mapped to an NvBlockDescriptor and the ARXML file was stored in version 4.0.x
  • Multiple delegation ports were created by the ARXML import if multiple operation mappings existed for the same client/server port
  • Consistency check didn't remove invalid operation mappings if a client/server port prototype was deleted which was mapped to a signal
  • Create Port Prototypes created variable element prototypes without the 'queued' flag for Tp transmitted signals
  • Create Port Prototypes derived faulty Record Init Values for Signal Groups
  • Mapping a data element prototype with an application record to a implementation record element was not correctly saved and corrupted after reload
  • Editing an init value at a port prototype caused a long GUI update when using large Array Init Values
  • Exception was thrown when closing the unresolved references dialog with cancel
  • Import option dialog hid in the background when working with other tools while running the DaVinci ARXML import
  • Large constants couldn't be displayed in the preview edit box
  • Data mapping view was unexpectedly scrolled after an update when having many data mapping displayed

 

More about DaVinci Developer...

Transferir agora página anterior