DaVinci Developer 3.3.50 SP4

Contains the complete installation of DaVinci Developer 3.3.50 (SP4). For the operation a license of version 3.3 or higher is necessary. In case an according license is already activated on your PC no further renewal of this activation is necessary. For the code generation the MICROSAR RTE 2.22 is required.

Detailed overview of compatible MICROSAR RTE versions

With Service Pack 4 (Update to 3.3 Build 50), the following changes become effective:

Tool features

  • New Data Exchange Analysis view in the ECU-Project to get an overview of the resulting port data exchange, operation invocation or signal flow within the ECU
  • Port Defined Argument Values are now available at Application Components

Usability enhancements

  • Performance enhancements during loading/saving DCF workspace and ECU-C synchronization
  • Init-Runnable annotation is now supported in AUTOSAR 4 Admin-Data export
  • Category items in the Library View now have a 'SelectAll' function

Fixed issues

  • Editing port accesses using multiple selection led in a dialog error
  • AUTOSAR 3 import of enumerations didn't work if an enumeration value had the same name but a different position
  • Existing SWC implementation was removed during AUTOSAR 4 import if a SWC with the same name and empty structure was imported
  • Internal data constraint couldn't be edit if set to -INF or +INF
  • Error message 'tem not found' during AUTOSAR 4 import fixed if an existing data type with compu-method was updated without a compu-method
  • Wrong export of constant-reference item fixed if it actually did not reference a constant
  • Wrong export of the DEST attribute fixed if the component type is a complex device driver
  • The data-constraint reference wasn't saved on closing the dialog with 'OK' after creating a new calibration element prototype
  • Crash on re-opening a DCF workspace fixed that was caused by memory leaks
  • Name clash fixed during export of End-to-End protections on atomic ports
  • The 'Adapt connected port' functionality didn't consider all communication specification values like 'EnableUpdate'
  • Consistency check message #40329 'unsupported N:M communication' wasn't displayed anymore
  • Mapping of single signal to nested arrays and vice versa didn't work correctly
  • Task property 'generate schedule calls' wasn't stored in the ECU-C file
  • Invalid ComSignal/ISignalToIPDUMapping references were falsely reported if the corresponding ISignalTriggering did not reference a signal port
  • CalibrationSupport flag wasn't written to the ECU-C file for all atomic software components
  • In some cases the 'Find Results' properties opened the wrong property dialog

Limitations

  • For AUTOSAR 4 design the following functionality is currently not available:

    • Create Port Prototype from data mapping based on a given signal
    • Adapt Data Type for Data Element based on a given signal
    • Find unused data types

 

Categoría : Service Pack
Tamaño : 257.66 MB
Resumen MD5 : 6b030caad3ac23d1f91b6e2d7a5bc2ec
Descargar ahora pagina anterior