dSPACE SystemDesk 3.2 October 2013 Last-Minute Information ************************************************************************* Copyright (c) 2013 dSPACE GmbH, Germany Contents: 1. General 2. Improvements & fixed Problems 2.1 Improvements & fixed Problems by previous Patches 3. Limitations 4. Installing the Patch 1. General ************************************************************************* This patch can only be installed on an existing SystemDesk 3.2 installation (dSPACE Release 7.4). 2. Improvements & fixed Problems ************************************************************************* SystemDesk 3.2p5: Automation: - Fixed type in readable automation class name property. Demos: - New AR_PosControl Demo. Accelerate COM Task in AR_PosControl_2Ecus_Can_Sim. Please delete old AR_PosControl Demo file and unzip new Demo!!! RTE: - The invalid value of an array data type is now taken from the element type (AR array type) if available. - Com_Dsfral.h and dsfral_hlp.h are not used any more for AUTOSAR COM code generation. - Fixed problem with the RTE code generator terminating with an exception if using DataSendCompletedEvents for event messages and time out monitoring. - Fixed a problem with non compilable RTE code using data elements with the name "value". - Com_Dsfral.h and dsfral_hlp.h are not used anymore for AUTOSAR COM code generation. - Added missing trigger of I-PDU to COM-Code when minimum delay timer elapsed. - Fixed a problem when generating RTE code after deleting the "Type definition" string of per instance memories. - The RTE code generation will not be aborted with an error if require mode ports are used together with multiple instanced software components. - Dap_Entry and Dap_Exit functions are now generated when using RTE intervention services with Dap signals. - During the command 'Generate initial NvM configuration' now the same NvmRomBlockDataAddress is used for all instances of of a shared CalPrm. - The generation of the Dap-Signal to Dap-Group mapping was changed for RTE intervention services. - AUTOSAR Com: Triggered Signals are now sent to PDU-Router by Com Task. - Dap_Entry and Dap_Exit functions are now generated when using RTE intervention services with Dap signals. - The generation of the Dap-Signal to Dap-Group mapping was changed for RTE intervention services. - RTE intervention services with data access points can now be used unrestricted on SCALEXIO hardware. - IoHwAbstraction now supports rational scalings which define a linear computation. Simulation: - Fixed missing link to code coverage target directory. - Fixed version conflicts with VEOS 3.1 - V-ECU can now be stimulated via XCP. - Fixed deletion of bus topology on V-ECU rebuild if system contains several different bus types. - Fixed generated routing structure when using multiple lower layer bus protocols. - Fixed unexpected bit-shifting of signal buffer content in AUTOSAR COM if the same signal is triggered multiple times. - IPDUs are now transferred reliably via the idealized bus interface. - Reset VPU port values after restart of simulation. - Added messages for XCP errors. - Fixed compiler macro usage in PDU router when using code coverage during build process. - IDs of measurement rasters will be set up correctly for dSPACE SystemDesk experimentation. - Symbol Table for TriCore 1797 will no longer container local jump marks. - Fixed failure in internal simulator state machine. - Removed linker error when using data access points with array width equal to 1. - Fixed simulation time synchronization problem. SoftwareSystems: - Improved init value update usability. - Fixed rational conversion precision problems. Import/Export: - Fixed AUTOSAR import problem with non unique internal behaviour. Misc: - SystemDesk now uses a more recent licensing mechanism. - Fixed a problem in the license check. - Fixed a crash on disconnected network license server. 2.1 Improvements & fixed Problems by previous Patches ************************************************************************* SystemDesk 3.2p1: Automation: - Support refresh of the simulation system via COM automation. - Fixed error regarding multiple exports of A2L via automation. ContainerManager: - Add functionality to Help button of V-ECU Implementation Container Export Dialog. - Add new internal functionality, which allows the processing of V-ECU Impl. Containers as standard .NET stream. Diagrams: - Correct Drag & Drop behavior of CalPrm Interfaces for AtomicSwc, Composition, Adapter and CalPrm component ports. RTE: - A new validation rule checks whether the corresponding module configuration (CanIf, LinIf or FrIf) is available if the ECU is connected to a CAN, LIN or FlexRay cluster. - Fixed a problem generating RTE code for "Rte_Send.." intervention points. - A warning message is sent if an unsupported PDU type is found during the 'Update PduR configuration' command. - Fixed a refresh problem of the RTE intervention editor. - Fixed a problem opening the RTE configuration editor. - A limtitation when generating RTE code for array data types with a width of 1 has been removed. - Main function mappings are now removed from the SchM module configuration if at least one RteEvent triggers the mapped runnable. - Removed support for Dap header file generation by plug-in. File is generated during V-Ecu build. - Generation of loop variables in IoHwAb code corrected. - Editor for runnable mapping locks on changes in SchM module configuration. - Fixed a RTE code generation problem accesing mode switch variables. - In code of IoHwAb the corresponding RTE file is included only when signals are configured. - Handle error in case referenced elements in IO-Signals can not be resolved. - Fixed potetial precision problem during update of NvM configuration if .NET 4.5 framework is installed on the computer. - Fixed a problem during 'Auto Configure and Generate' command if a NvM module configuration is used in an ECU configuration. - Generation of a DEM basic software component for standard AUTOSAR module configurations is no longer possible. Generation for dSPACE DEM module configurations is still possible though. - Fixed a double runnable to task mapping issue. - Fixed a RTE intervention service problem when reading a status value from V-ECU data access point. - Fixed error when opening editor for runnable mapping without using SchM in ECU. - Updating RTE configuration before opening intervention editor. - Fixed a problem creating DataAccessPoints in combination with rational scalings. Simulation: - The code descriptors for VPUs can now be specified as relative paths. - Simulation time options of vpus now will be considered on build simulation system, so that on successful build the simulation time options are contained in the osa file. - Simulation time options of vpus now will be synchornized during refresh the simulaiton system with respect to the osa file. - Creating simulation variables from SWA elements will copy the DisplayIdentifier, if present. This is true for the following types: - StimulusVariable created from DataElement and OperationArgument. - Calibratable created from CalibrationElement and IBCalibrationParameter. - Measurement created from DataElement, InterrunnableVariable and OperationArgument. - Compiler warning "dereferencing type-punned pointer will break strict-aliasing rules" in Com_generated.c removed. - SystemDesk crash when closing stimulus variable dialog within the active experiment after simulation run has been completed. - When specifying XCP ports for an V-ECU which conflict with the XCP ports of an externally added V-ECU or environment VPU, the validation of the simulation system must fail. - The build state is being misinterpreted when the build process was stopped manually. - Bugfix in stimulation code generation. - Corrected byte order in A2L-file for PIL Boards using Big Endian. - Fixed crash when a client application resynchronizes a simulation system. - Fixed erroneous determination of time stamp ticks value. - XCP Byte order will be set correctly for target simulation modules with MOTOROLA chipset. - Fixed crash while saving osa-file. If a bus is no longer connected in the model, the bus will be disconnected in the simulation system as well. - Fixed COM port for PIL simulation. - Compiler version of the TSM identifier is being misinterpreted when opening a SystemDesk 3.1.x project in SystemDesk 3.2. - Fixed client synchronization when watching an OSA file which is currently been modified by the build. - Additional support of evaluation board InfineonTricore1791 using compiler Tasking 3.5R1. - Improved error handling in case of invalid simulation state transition. - Fixed code derivation issue that a build stops, when an operating system task is triggered by two alarms. - Fixed evaluation of shutdown hook parameter in os configuration. - Fixed compiler warnings in AUTOSAR Os when using Tasking 3.5 compiler. - A warning message was corrected when using multiple OsApplicationModes. - XCP Service does no longer rely on RTE type definition dependency. - If a VPU port changes his scalar or vectorial type, the VPU port will be changed correctly. - Shutdown function of simulator abstraction will not be redefined if user has configured one. - Fixed erroneous derivation of XCP timestamp during runtime. - Log messages will no longer set build result to invalid. - Fixed error message on accessing write protected osa files. - Trace files will only be merged with map files to a TRZ file if Real time testing support is required for the VPU. - C++ files are now supported if supported by TSM Compiler. - Fixed validation issue regarding multiple pdu ids associated with one controller. Transmitted PDUs will now have a unique PDU Id for each controller which transmits this PDU. Old simulations systems can not be simulated any more since they contain wrong compiled code and an erroneous meta model. - Rte mode switch event will no longer be triggered twice if the ECU State manager switches its mode from start to do run. - Fixed erroneous export of SDF file. - TRZ files will no longer be referenced from OSA application folder. - Fixed compiler errors during stimulation code generation in case of multiple instances of atomic software component type. System: - Fixed wrong context menu entry when more than one communication ports below a triggering were selected. - Fixed error that a communication controller or connector got deleted if being dropped on its own ECU. - Fixed error that a communication controller was in an undefined state and unusable after it was moved to another ECU per drag and drop. - Fixed error that occurred, when repeatedly changing the order of mapped Signals in a Signal Group. Import/Export: - During import of a DBC file now all necessary frame-, IPDU- and signal triggerings are created. - Data type invalid value now can be entered as physical value. - During import of a DBC or LDF file, imported units are now stored locally and not in the project library. - References from a container within a module configuration to an AUTOSAR Package are now exported correctly while exporting to an AUTOSAR file. - Fixed performance issue for A2L file export. - Unit display name now is imported properly via AUTOSAR. - AUTOSAR export of signal groups that are mapped to signal IPDUs now is possible. - Now communication ports for frames, IPDUs and signals are created during LDF file import. Validation: - Fixed an error where opening the Validation Rule Configuration Editor and closing it without saving would lead to an incorrect rule configuration being active. - Fixed error that validation rule "R209 Complex Signal Mapping Needs Manual Checking" produced an validation-error in case a complex signal mapping was incomplete (no signal group set). Misc: - Removed some element types from possible unused elements list and added missing usage relation. - Corrupt data types now are cleaned up when loading old projects. - Fixed registration / unregistration of SystemDesk protocol handler when switching SystemDesk versions via InstallationManager. - Fixed potential bitlength calculation precision problem if .NET 4.5 framework is installed on the computer. - The management of the menu bar and toolbar on adapted to ensure compatibility for. NET Framework 4.5 make. - The error messages shown while opening projects no longer appear behind the progress bar. - A SystemDesk 3.1 project without a network communication can now be migrated to SystemDesk 3.2. SystemDesk 3.2p2: ContainerManager: - For the additional use of *.o object files within a V-ECU Implementation Container the Workflow Definition (CTW) File has to be complemented. Change the condition of the block from $(ExtensionLower) == '.obj' to $(ExtensionLower) ~~ '\.(obj|o)'. Further information about Workflow Definition (CTW) File editability and configuration are described on page 39-56 of the Container Management Document. Demos: - No warning messages about undefined memory allocations in the AR_Fuelsys demo system. Diagram: - Deactivate edit mode for diagram elements during scrolling. RTE: - Fixed a selection problem for invalid status intervention points. - Changed handling of name conflicts for software component types during RTE generation. Now an error message is shown if a name conflict occurs and the RTE generation is canceled. - Fixed a code generation problem of the BSW scheduler when using multiply BSW module instances. - Minor bugfix in 'Update CanIf Configuration' command. - Fixed a RTE code generation problem for event messages with name "value". - No warning message is sent during RTE generation if the source files for the BSW scheduler component are missing. - Fixed error message "No path to resolve the reference value. Resolve path: ''" while opening SystemDesk 3.1 projects. - The RTE generator does not send an error message any more if two NV Block Service Needs use the same Default Block. - Fixed error message during RTE generation if no SchM module configuration is available. Simulation: - Container import will now abort build if a file category is unknown. For the additional use of *.o object files within a V-ECU Implementation Container the Workflow Definition (CTW) File has to be complemented. Change the condition of the block from $(ExtensionLower) == '.obj' to $(ExtensionLower) ~~ '\.(obj|o)'. Further information about Workflow Definition (CTW) File editability and configuration are described on page 39-56 of the Container Management Document. - Fixed wrong interpretation of messages with file system link. - After stopping a build, messages will no longer be submitted twice. - Fixed erroneous determination of time stamp ticks value. - Including VPUs from osa files which were built by a compiler that does not exist on the current system is now possible. - TaskCallCount is now measured and displayed correctly in experimentation tools. - Fixed wrong CSV export of measured data. - Measurement raster will be calculated correctly if an operating system task is triggered by multiple alarms. - Measurement raster will not be calculated if no operating system application mode has been specified. - In the event that multiple operating system application modes are available, measurement raster will not be calculated if OSDEFAULTAPPMODE (OSEK) has not been specified as default operating system application mode. - Fixed compiling issue in non-native operating system (usually for PIL platforms). - Provide offline simulation application (OSA) file name via COM automation. - Fixed compilation errors of ECU State manager if EcuM is used with NvM or Dem BSW module. - Change instance administration of VEOS Player. - Fixed code generation and compiler issues when using NvM. - Updating an externally added environment VPU or a V-ECU while SystemDesk is not started, does not result in a outdated simulation system, when SystemDesk is started for the next time. - Fixed simulator hangs or crashes after VPU has initiated a shutdown using AR BSW Stack (EcuM). - Switched off debug messages due to incompatible execution platforms. - Fixed erroneous evaluation of code coverage output files. SoftwareSystems: - Fixed compatibility problem with ClientSeverInterfaces. SystemDesk 3.2p3: ContainerManager: - During a container export the package group file assignment will be ignored. - During a V-ECU Implementation Container export the specified SwcImplementation which was specified within the Implementation Selection Editor will be used. Diagrams: - Added missing functionality for opening component diagrams out of a specified composition diagram. - Added missing functionality for opening a property dialogue out of a specified composition diagram. - Extend the maximum bitmap size. Import/Export: - Cleaned up datamodel after import. - AUTOSAR export no longer creates invalid xml files for specific AUTOSAR versions. - Char constants no longer result in invalid AUTOSAR xml files. - Can controllers now are properly imported via AUTOSAR. - Fixed import of frame triggerings reference in LIN schedule tables. RTE: - Cleaning of intervention context fixed to keep DapGroup settings - A Problem with RTE intervention point service custom code was fixed. - The default behaviour when exporting A2L variables with none unique names was changed. - The RTE code generator option "RteGenerateAutosarTypes" was introduced to suppress the generation of standard AUTOSAR types. - Connections between IoHwAb software component and any other software component (regardless of type) are now allowed. - The RTE code generator in compatibility mode stops with an internal error message when using the ComPortSpec option "NeverReceived" without any other. This problem was fixed. - The Plug-In method "Trigger OS Tasks" avoids the creation of more than one counters as far as possible. - A RTE problem with wrong init values for CAL parameter using mixed scalings was fixed. - If the main function of the ECU state manager (EcuM_MainFunction) is already mapped to a task, this mapping is kept during update of the EcuM software component. - Code generation for signals with a scaling having LSB = 2^0 and offset = 0 is corrected. - A2L-Export: Symbol link expression is generated using INT-Types instead of SINT-Types - A problem of the generated RTE code for more than 1024 RTE intervention services was fixed. Simulation: - Fixed inconsistent experiment panel after closing and reopening project. - Added event for the system builder to show that a build can be stopped by the user or not. - If the working directory (defined in IDE Project Configuration) of an V-ECU is not unique, an error message occurs. The error message is embedded in the validation rule (R744). - Simulation Time Options of external V-ECUs (imported V-ECUs) now are not overridden with default values on V-ECUs whose check box "Use simulation time options from OSA file" (in the property dialogue) is not checked. - Messages will now longer contain null values and may so cause invalid links in the message browser. - Fixed missing file links in messages. - Fixed crash when changing system name after the deletion of experiment. - Avoid exception during simulation startup when "Keep all old results" option is disabled. - Validation rule for XCP port configuration does not report an error, when the default XCP ports of a V-ECU conflict with the XCP ports of an imported environment VPU. - Now the correct validation message is displayed if VPUs with the same XCP Ports are validated. - Problems when generating VPUs with code size information solved. - Cloning of replay signal generator is time consuming when starting simulation. - Increased throughput of replay signals of stimulus variable. - Added check so that EcuM_Next will no longer be evaluated directly but the change of the value will be taken into account. - Shortened variable names in generated basic software module COM, CANIF, DAP and DSIDBUSIF to avoid errors with certain compilers. - Code coverage fails if the output path contains white spaces. - Prevent integration of ASM models via Simulink Model Integration functionality. System: - Fixed problem when adding existing IPduGroups to an ECU. Misc: - Added japanese documentation for the tutorial and the SystemDesk 3.2 Guide. SystemDesk 3.2p4: Automation: - Added properties for SignalTriggerings to ISignal and for FrameTriggerings to Frame in the Automation Interface. - Added automation methods for StructureDataTypes. - The property SystemSignalList in a SystemSignalGroup is added. Now it is possible to use Add, Remove, Names etc. on the list. - It is now possible to create connections within an EcuSwComposition via the automation. Diagrams: - Interfaces within a Component Diagram will not be deleted if an interface will be replaced within the ProjectManager. Documentation: - Updated user documentation. RTE: - Added a new RTE code generation mode "COMPATIBILITY_NO_SRC_OPT" to suppress any optimizations for components delivered as source code. - Fixed a problem where the generated RTE code of the API function "Rte_IWrite" was not compilable. - Fixed an A2L generation problem of calibration parameter without Scalings. - Added RTE code generation support for Data Element invalidation if the InvalidValue equals the InitValue. - Fixed an internal RTE code generator error in conjunction with acknowledgement events and the compatibility generation mode. - Corrected calculating addresses for nested Structures. - During update of the EcuM Software Component the temporary file 'EcuM_SWC.arxml' is now always a valid AUTOSAR file. - Improved RTE code generation for Rte_Call to avoid superfluous code. - Signals are updated with auto configure to correctly adapt changing direction of Operation Argument or Data Element. - The Update EcuM Software Component command does not try to create BSWConnections if the other software component is located in the Ecu_SW Composition. - Fixed a problem with the function "Generate Default Mapping", which leads to an invalid Runnable-Task Mapping for Client-Server Runnables. - Fixed an internal error that occurred during generation of the RTE SWC together with Intervention Point\Services for Operation Arguments. - Fixed problem storing large arrays in InitValues. - Fixed an error when using an enabled signal for multiple Intervention Services. - Fixed an RTE code generation issue when using Data Elements with name "value". - Fixed double declarations in the generated application header file. - The name of A2L array variables will now be generated by the RTE code generator without size characters "[]". - Fixed an internal error that occurred when calling the plug-in method "Generate Rte Component" and interfaces of an already existing RTE SWC have library links. - Fixed a problem when setting a RTE API status by a RTE Intervention Service. - Fixed a problem when setting an Operation Argument by a RTE Intervention Service. - Improving the error handling of the RTE code generator at detecting invalid (N:1) Mode Switch Connections. - Suppress build error when building Simulation System if a Dem Module Configuration is used in an V-ECU. - The RTE code generator now supports data invalidation for Data Elements with array types. - Changing the name template for RTE Service Ports. Now they are taken into account immediately when updating an existing RTE Component. - Fixed compile error of intervention services when using data elements with a complex data type. - Providing meta-data about generated c-symbols for per instance memories. Simulation: - Now XCP measurement raster is generated when using schedule tables. - Now Simulation can be started if the simulation system has not been built successfully. - Code size information must not be used for Host-PC TSM. - Fixed a problem with the simulation when OSIM_ShowMessage function was invoked in high frequency. - Fixed state changes in ECU State Manager BSW for HIL platforms when Os Configuration without startup-tasks are used. - Fixed multiple declaration of failure injection variables. - Fixed crash related to invalid Signal Mapping import messages. - Fixed incorrect Plotter visualization when using simulation step mode. - Fixed missing declaration of confirmation flag variable in generated COM code, regarding receive PDUs with ComIPDUSignalProcessing set to deferred. - When using Data Access Points, the A2L files will contain matching variables to access the variable. - Fixed addresses in ASAP2 files for elements in nested structures. - Improving simulations when long wait intervals during data reception slows down low sampled simulations. - EcuM Driver Init list three is called even if no NvM is configured. - Added functionality to display all compiler/linker warnings. - Creation of a new Simulation System enforces ignorance of existing OSA file now. - Fixed error handling when TSM configuration is missing. SoftwareSystems: - Changed categorization of Runnables to AUTOSAR 3.2.2 semantics. Import/Export: - New AUTOSAR option allows export of internal Data Type limits equal to base type boundaries. - Added 'UsesEndToEndProtection' support for ComSpecs. - DBC import will now import the cyclic timing information of dynamic and static parts. - Increased performance of A2L file export - Special data groups of IO signals in an exported arxml file will now be used correctly - Base type reference now is exported for floating point Data Types. Validation: - During update of the EcuM Software Component a warning message is sent if the EcuM minimum mode is activated but at least one Application Software Component uses the EcuM state request interface. - Validation rule 414 does not sent an error message any more if a V-ECU implementation is exported and a customer specific module configuration is used in the V-ECU. - A warning message is sent if a runnable mapping or main function mapping is removed because it is obsolete. This may happen if the Runnable or the triggering RTE Event is deleted. 3. Limitations ************************************************************************* SystemDesk projects saved by this Patch cannot be opened with previous versions of SystemDesk. Simulation: - GCC 3.4.2 Compiler is no longer supported. - It is possible to simulate Os configuration with schedule tables, but no measurement rasters are generated for these schedule tables. 4. Installing the Patch ************************************************************************* To install the patch, you must be logged on with administrator rights and all hotfixes of the current version have to be removed. Close your SystemDesk application and simply run executable file. The setup will automatically locate and patch the SystemDesk installation. After this patch is applied, the installed patch is shown in the splash screen, about box and the message browser. *************************************************************************