DaVinci Developerの概要

• 2019-09-25 Vector Testing Symposium 2019 | Chennai, India
• 2019-10-16 ウェブセミナー: Steuergeräte gegen Cyber-Angriffe schützen – Mehr Schutz und...
• 2019-10-23 - 2019-10-24 Vector Technology Days 2019
• 2019-10-29 ウェブセミナー: VectorCAST: Wie man Safety-Probleme und Security-Lücken in...
• 2019-10-29 ウェブセミナー: VectorCAST: How to avoid Safety Defects and Security...
• 2019-11-06 ウェブセミナー: Protect ECUs Against Cyber Attacks – More Protection and Faster...
• 2019-11-11 ウェブセミナー: Using AUTOSAR Basic Software for Safety-Related ECUs According to...
• 2019-11-14 ウェブセミナー: Security Mechanisms for Embedded Automotive Systems
• 2019-11-25 ウェブセミナー: The Vector Embedded Ethernet Stack and Its Use Cases in Motor...

Released: 2017-04-06

NOTE

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

Due to an architectural enhancement in the ARXML processing the performance and memory usage differs from the previous Service-Pack.

Depending on the use-case and data structures this can also result in a slower loading and saving performance or an increased memory usage, this will be optimized again with upcoming versions

Tool features

• AUTOSAR 4.3.0 is now supported.
• Calibration element prototype mappings are now supported
• SwcToECUMapping is now exported as part of the SystemElement
• Category Tag for ApplicationValueSpecifications is now exported
• Top-down definition of DTCStatusChangedNotification service need is now supported
• The parameter 'TransformationErrorHandling' is now supported in the Port-API options of Port-Prototypes

Usability enhancements

• 'Graphic settings' are now accessible via the context menu
• To reduce the memory consumption of signals not actually received/sent by the ECU Instance are now ignored during ARXML import
• The specific Transformer Type is now displayed in the data mapping view and signal selection dialog
• CompuMethod consistency check has been improved to check for unique identifiers and multiple identical ranges
• Compatibility check for constants has been extended for to show more detailed information
• Additional check was implemented to ensure that an axis, that is referenced by a characteristic table (CT), is used elsewhere within the corresponding software component
• When changing the CompuMethod Category in the GUI to a non-TextTable the tool now queries if the defined enumerators should be removed

Fixed issues

• Depending on the FlexNet environment the application may hanged-up at startup during license query
• Create Port Prototypes created a Base-Type with invalid Native Declaration 'int16' instead of 'sint16'
• End-to-End Transformer settings at receiver ComSpec were not editable when using in modal properties dialog
• 'Generate Contract Phase / Component Implementation Templates' aborted if there are model consistency warnings
• Existing wait-points were not removed when changing the port access to none
• When creating an implementation data type of category array, the attribute 'size handling' was not persisted
• Compu-Scales were not correctly updated if they didn't specify symbol, label or constant
• Import of Variant Clusters is now rejected with a specific error message since this is not supported
• Consistency message #40405 'CompuScale without label' was falsely shown if the Compu-Scale defined a symbol and/or constant but not a label
• NvM Port Assignment disappeared from the list after renaming but it still existed
• Create Port from Signal didn't consider CompuMethod to create arrays and records
• Assignment of a NvMBlockNeed to a PIM didn't remove existing assignments when using the PIM-page
• When the NvBlockNeed-Page was opened within a standalone dialog, the action bitmap-buttons didn't appear
• Exporting a NVMBlockNeed had duplicated the port assignment
• Changing the service need attribute 'Cycling writing period' is only saved if another attribute had been changed too
• Wrong service need type had been created for DcmDiagIOControlNeed, DcmDiagSecurityNeed, DltUserNeed
• Multiply used RecordLayout-Annotations were not detected by the consistency check
• Existing service needs were falsely reset to default during ARXML import of a Nv software component
• Since AUTOSAR version 4.2.2 double underscores can be used in Short-Names but DaVinci DEV didn't accepted this in GUI and ARXML import/export

Released: 2016-11-29

NOTE

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

Tool features

• Preparation for upcoming AUTOSAR 4.3.0 schema version files. Currently no new features are supported.
• Support for 64 bit COM signals according to AUTOSAR 4.2.2 has been added

Usability enhancements

• Additional consistency check has been implemented to ensure that different ranges of a Compu-Method don't overlap
• Additionally merged usability enhancements from service packs of previous releases:
  • Create port with data-type from signal now suppresses transformed signals
  • Delete of End-to-End connections with multi-select is now supported
  • ArrayElement-ReferenceName is now configurable

Fixed issues

• Data type mapping check didn't support integer data types which require more than 32 bit
• DaVinci CFG5 threw "unsupported merge/communication scenario" error message if data mapping was done in CFG5 at atomic ports and the same signal was mapped to the same port for different variants
• Consistency check for application data types that references compu methods of type "BitfieldTextTable" was wrong
• Bitfield dialog showed "out of range" on correctly defined bitfield values
• Rte code generation failed with error 40170 "Multiple mappings for network signal" if the same data mapping was done in DaVinci CFG5 at atomic ports of different component prototypes
• References to record elements stored in external files were not resolved when loading a workspace
• Compu method could be deleted but was used within the ISignal network representation
• Project update aborted if an E2E protection with same name is defined in different E2E protection sets and the E2E protection specifies an E2E ISignal IPDU
• Additionally merged issues from service packs of previous releases:

• • Consistency check 40454 didn't consider array element mapping according to AUTOSAR Constr_1004
  • Delegation ports with several data mappings for different variants weren't supported
  • Communication and data mapping was lost after import of an ECU-Extract having several clusters with the same name
  • "Adapt structure of record type" function created non-matching init value for nested complex data-types
  • AR3 to AR4 workspace conversion showed the error message 40338 inconsistent data type mappings when using real data-types
  • Loading a workspace with external DCF references failed with message "Item with name is read-only" if the loaded DCF referenced another DCF with custom generic attributes
  • Existing Type-Reference couldn't be selected as Inter-Runnable-Variable data-type
  • ARXML export duplicated the data mapping if the signal was mapped and the signal was part of a signal group
  • Constant reference wasn't imported correctly for calibration parameters with 'per instance' scope
  • Create port from signal group didn't consider the variant assignment
  • The separate variant assignment for group signal mappings wasn't deactivated if the signal group is already mapped

Released 2016-09-26

NOTE

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

Tool features

• Various Diff/Merge extensions to support sub-elements e.g. internal behavior
• Software Component Prototypes are now allowed to have the same name in different compositions
• Variant I-Signal groups with the same triggering and System-Signal group are now supported

Usability enhancements

• DaVinciDEV.exe command line parameters can now be displayed using /help switch
• Additionally merged usability enhancements from service packs of previous releases:
  • Tool version check is now skipped for workspaces without having a ECU-Project
  • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
  • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• The "Uses Tx Acknowledge" check box value couldn't be changed
• Additionally merged issues from service packs of previous releases:
  • Signal's init/invalid value was always "" in the properties dialog
  • Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
  • Data-Mapping couldn't handle mapped ports without port-interfaces
  • Connections were deleted during ARXML import even if the import mode preset should avoid that
  • The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
  • Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
  • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
  • Create port from signal didn't create correct init values in all cases
  • Init value constant contained duplicate record elements after merge
  • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)

Release: 2016-11-07

NOTE

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

With Service Pack 3 (Update to 3.12 Build 30), the following changes become effective:

Tool features

• Various Diff/Merge extensions to support sub-elements e.g. internal behavior
• Software Component Prototypes are now allowed to have the same name in different compositions

Usability enhancements

• Create port with data-type from signal now suppresses transformed signals
• Delete of End-to-End connections with multi-select is now supported
• ArrayElement-ReferenceName is now configurable
• Additionally merged usability enhancements from service packs of previous releases:
  • Tool version check is now skipped for workspaces without having a ECU-Project
  • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
  • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• Consistency check 40454 didn't consider array element mapping according to AUTOSAR Constr_1004
• Delegation ports with several data mappings for different variants weren't supported
• Communication and data mapping was lost after import of an ECU-Extract having several clusters with the same name
• "Adapt structure of record type" function created non-matching init value for nested complex data-types
• AR3 to AR4 workspace conversion showed the error message 40338 inconsistent data type mappings when using real data-types
• Loading a workspace with external DCF references failed with message "Item with name is read-only" if the loaded DCF referenced another DCF with custom generic attributes
• Existing Type-Reference couldn't be selected as Inter-Runnable-Variable data-type
• ARXML export duplicated the data mapping if the signal was mapped and the signal was part of a signal group
• Constant reference wasn't imported correctly for calibration parameters with 'per instance' scope
• Create port from signal group didn't consider the variant assignment
• The separate variant assignment for group signal mappings wasn't deactivated if the signal group is already mapped
• Additionally merged issues from service packs of previous releases:
  • Signal's init/invalid value was always "" in the properties dialog
  • Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
  • Data-Mapping couldn't handle mapped ports without port-interfaces
  • Connections were deleted during ARXML import even if the import mode preset should avoid that
  • The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
  • Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
  • When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
  • Contract phase generation couldn't be used at the ECU-Project
  • Crash during SWC check on runnable data accesses by value has been fixed
  • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
  • Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
  • In some cases a double click on a .dcf file started the wrong DaVinci Developer version
  • Create port from signal didn't create correct init values in all cases
  • Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
  • A component type DCF file accidently contained data constr elements
  • Init value constant contained duplicate record elements after merge
  • GUI crashed when calling "Show in other views" on a found object
  • Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
  • Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
  • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
  • Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

NOTE

This release is only relevant for AUTOSAR 4.

AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

Tool features

• Various Diff/Merge extensions to support sub-elements e.g. internal behavior
• Software Component Prototypes are now allowed to have the same name in different compositions

Usability enhancements

• Tool version check is now skipped for workspaces without having a ECU-Project
• Additionally merged usability enhancements from service packs of previous releases:
  • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
  • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• Signal's init/invalid value was always "" in the properties dialog
• Option 'delete unreferenced files' deleted files which were still in use if the filename only differs in character case
• Data-Mapping couldn't handle mapped ports without port-interfaces
• Connections were deleted during ARXML import even if the import mode preset should avoid that
• The import mode preset generic attribute definition of new workspaces was wrong if they were created through DaVinci Configurator 5
• Consistency message 40368 "Inconsistent NvM block needs (RAM Block Status Control)" was shown although the model is correct
• Additionally merged issues from service packs of previous releases:
  • When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
  • Contract phase generation couldn't be used at the ECU-Project
  • Crash during SWC check on runnable data accesses by value has been fixed
  • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
  • Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
  • In some cases a double click on a .dcf file started the wrong DaVinci Developer version
  • Create port from signal didn't create correct init values in all cases
  • Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
  • A component type DCF file accidently contained data constr elements
  • Init value constant contained duplicate record elements after merge
  • GUI crashed when calling "Show in other views" on a found object
  • Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
  • Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
  • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
  • Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

Released: 2016-08-09

NOTE

This release is only relevant for AUTOSAR 4.

AUTOSAR 3 is supported by DaVinci Developer Version 3.7 or previous releases.

With Service Pack 5 (Update to 3.10 Build 50) the following changes become effective:

Tool features

• Additionally merged tool features from service packs of previous releases:
  • Various Diff/Merge extensions to support sub-elements e.g. internal behavior

Usability enhancements

• Additionally merged usability enhancements from service packs of previous releases:
  • Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
  • The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• Additionally merged issues from service packs of previous releases:
  • When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
  • Contract phase generation couldn't be used at the ECU-Project
  • Crash during SWC check on runnable data accesses by value has been fixed
  • Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
  • Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
  • In some cases a double click on a .dcf file started the wrong DaVinci Developer version
  • Create port from signal didn't create correct init values in all cases
  • Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
  • A component type DCF file accidently contained data constr elements
  • Init value constant contained duplicate record elements after merge
  • GUI crashed when calling "Show in other views" on a found object
  • Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
  • Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
  • Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
  • Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component

Released: 2016-08-09

Tool features

• AUTOSAR 3 ECU-C synchronization now supports application refs of OS resources if the OS applications use exclusive areas as interruption mechanism
• Various Diff/Merge extensions to support sub-elements e.g. internal behavior

Usability enhancements

• Consistency check 40269 has be enhanced to accept a data length of 0 for Intra-ECU End-to-End Protection
• The ImportModePreset is now respected when importing the DataMapping so that the mapping of a Delegation-Port with 'keep' will not be deleted

Fixed issues

• When importing a Calibration Software Component the constant-reference in the role of an init-value wasn't set
• Contract phase generation couldn't be used at the ECU-Project
• Crash during SWC check on runnable data accesses by value has been fixed
• Inter-Runnable-Variables and Port Accesses weren't merged correctly which lead into multiple definitions
• Error 'XML parser error code 0x800C0006 in file .' was displayed when opening a DCF workspace with relative paths to a DPA file
• In some cases a double click on a .dcf file started the wrong DaVinci Developer version
• Create port from signal didn't create correct init values in all cases
• Saving a workspace aborted with "invalid argument" error if the ECU-Extract contained incorrect E2E connections
• A component type DCF file accidently contained data constr elements
• Init value constant contained duplicate record elements after merge
• GUI crashed when calling "Show in other views" on a found object
• Search function didn't find all objects of type "Blueprint" or "Blueprint Mapping Set"
• Loading a DCF workspace crashed if the .dcf file contained an absolute file reference with more than 260 characters
• Port interfaces were are not updated correctly when overwriting a sender receiver port interface with a mode switch interface (or vice versa)
• Deleting a runnable caused an error during workspace saving if a Calibration Parameter or Per-Instance Memory exists at the software component