DaVinci Developer
AUTOSAR 소프트웨어 컴포넌트 설계

DaVinci Developer - AUTOSAR 소프트웨어 컴포넌트 설계

DaVinci Developer는 AUTOSAR ECU의 소프트웨어 컴포넌트 (SWC)를 설계하기 위한 툴입니다.

장점

  • 사용자 친화적이고 손쉬운 AUTOSAR 소프트웨어 컴포넌트(SWC) 설계
  • 다양한 그래픽 편집 기능
  • AUTOSAR conformity를 위한 소프트웨어 컴포넌트 검사
  • ARXML를 통한 LINK 모델 기반 개발 툴
  • AUTOSAR 3.x 및 4.x 프로젝트 지원

응용 분야

소프트웨어 컴포넌트 (SWC) 아키텍처 설계

  • 다양한 레이아웃 기능을 사용하여 소프트웨어 컴포넌트(SWC)를 그래픽적으로 정의
  • 포트 인터페이스와 데이터 타입 정의
  • Service Needs 및 통신 규격으로 포트 프로토타입을 정의 (예: 초기 값 및 타임아웃)
  • Composition SWC 생성
  • 수동 및 자동으로 소프트웨어 컴포넌트(SWC)에 링크
펼치기
  • Activation 이벤트와 포트 엑세스를 사용해 Runnable entity 생성
  • Exclusive Area 설정
  • 내부적으로 실행 가능한 변수, Per-instance 메모리와 캘리브레이션 파라미터를 정의
  • Service needs 정의(예: NV 메모리에 대한 엑세스)
  • 수동 및 자동으로 소프트웨어 컴포넌트(SWC)에 연결.
펼치기
  • SWC 포트와 네트워크 신호 사이의 데이터 매핑 디스플레이
  • 신호 및 포트별 디스플레이
  • 수동으로 데이터 매핑 생성
  • 이름을 기반으로 데이터 매핑을 자동으로 생성
  • 네트워크 신호에 맞는 포트 프로토타입 생성
  • End-to-End Protection 및 SOME/IP를 위한 데이터 변환기능 지원
펼치기
  • 소프트웨어 컴포넌트(SWC)의 종합적인 일관성 검사
  • SWC 템플릿 및 RTE에 대한 AUTOSAR 규격의 일관성 규칙 반영
펼치기

각 사용 사례에 적합한 DaVainci 제품 개요

일반 사용자 그룹

전문가 사용자 그룹

펼치기

버전 4.3의 특징

프로젝트 병합 기능 개선

  • 개별 SwConnector에 대한 병합 여부를 유연하게 결정할 수 있습니다.

보다 편리해진 DPA 프로젝트 내 에러 검출 기능

  • 프로젝트 로드 중 누락된 파일을 알려주는 기능이 더욱 향상되었습니다.

기능

  • OEM이 제공한 입력 데이터가 변경된 후 SWC 아키텍처를 업데이트하기 위한 import 기능
펼치기
  • 소프트웨어 컴포넌트(SWC) 사이의 커넥터 자동 생성
  • SWC와 네트워크 신호 사이의 데이터 맵핑 자동 생성

  • 일반적인 OEM 네이밍 규칙에 맞추어 설계된 이름-기반 검색 알고리즘

펼치기
  • SWC 아키텍처 분석을 통해 ECU 내의 데이터 교환 표시
  • 개별 데이터 요소 및 네트워크 신호 수준에서 통신 관계의 상세한 분석
펼치기
  • 공유된 ARXML 파일을 DCF 라이브러리로 이동
  • DCF 라이브러리의 쓰기 보호된 로딩을 위한 메커니즘 포함

DaVinci Developer는 MathWorks 파트너 프로그램의 일부입니다.

펼치기

옵션

CPG 옵션: Contract-Phase 생성

  • C 언어 기반 어플리케이션을 위한 헤더 파일과 실행 템플릿 파일 생성
  • 소프트웨어 컴포넌트 description이 변경된 후 SWC 업데이트
  • 참고: CPG 옵션을 사용하는 경우, MICROSAR RTE generator 없이 Contract Phase 생성을 실시할 수 있습니다.

제품 정보

Fact Sheet:

펼치기
  권장 최소
프로세서 Quad-Core Dual-Core
메모리 (RAM) 16 GB 8 GB
해상도 1280 × 1024 1024 × 768
운영체제 Windows 7, 8.1, 10 (64-Bit) Windows 7 (64-Bit)
디스크 SSD HDD
펼치기

MICROSAR RTE 설정을 위해 적합한 DaVinci Developer 버전이 필요합니다. KnowledgeBase의 적합성 Matrix에서 여러분이 필요한 DaVinci Developer의 버전을 찾을 수 있습니다.

펼치기

교육

AUTOSAR의 기본과 AUTOSAR 베이직 소프트웨어 및 툴에 대해 더 알고자 하십니까? 벡터는 1-5 일 과정의 모듈식 AUTOSAR Worshop을 제공합니다. 이 Workshop은 AUTOSAR 4 및 AUTOSAR 3에 대해 다룹니다. 예정된 모듈에 따라 이 Workshop은 다음을 제공합니다.

  • AUTOSAR 방법론을 학습할 수 있습니다.
  • ECU 개발의 주요 영역에 대한 통찰력을 얻을 수 있습니다.
  • 일부 OEM들의 사양을 알 수 있습니다.
  • ISO 26262에 따른 안전 관련 ECU를 위한 벡터 솔루션인 MICROSAR Safe을 소개합니다.

각 모듈에 대한 자세한 정보는 교육 포털을 참조하십시오.

버전 히스토리 (영문)

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
펼치기

문의

임베디드 소프트웨어 및 AUTOSAR 기술영업

벡터코리아 IT ㈜

서울특별시 용산구 한강대로 69
용산푸르지오써밋 업무동 9층
04378
한국

전화: +82 2 807 0600 Ext.4
팩스: +82 2 807 0601
이메일: embedded@kr.vector.com