Release 6.1p1 July 2008 Last-Minute Information ========================================================================= Copyright (c) 2008 dSPACE GmbH, Germany Contents: 1. General 2. New Features and Problems Fixed by this Patch 3. Limitations ========================================================================= 1. General ------------------------------------------------------------------------- This patch can only be installed on an existing dSPACE Release 6.1. This document describes RTI and RTLib products and FlexRay Configruation Package contained on this patch. 2. New Features and Problems Fixed by this Patch ------------------------------------------------------------------------- a. RTI 1.) If the Serial Receive block (RX) is configured to use the NumBytes inport the sequence of the code generation can be incorrect. As a result a wrong number of receive bytes is read by the block. 2.) Bug fix for: On Korean OS the code generation for DS2210/DS2211 generates wrong code, because the special character ° (degree) in the tlc code could not be interpreted by RTW. b. FlexRay Configuration Package For full instructions on using the dSPACE FlexRay Configuration Tool and RTIFLEXRAYCONFIG contained on this patch please refer to: - "FlexRay Configuration Tool Reference" available under "Implementation - I/O Board Implementation Reference - FlexRay Implementation Reference" of the dSPACE HelpDesk. b.1 RTIFLEXRAYCONFIG 1.) This version of RTI FlexRay Configuration Blockset 1.11 supports the following dSPACE real-time systems: - Modular system based on a DS1005 with a DS4501 or DS4505 - Modular system based on a DS1006 with a DS4501 or DS4505 - MicroAutoBox 1401/1505/1506 or 1401/1505/1507 Each system must be equipped with FlexRay IP modules in one of the following types: - DECOMSYS::FlexIM(MFR4200) (1) - DECOMSYS::FlexIM(V11 IP-Core) (2) - DECOMSYS::FlexIM(E-Ray) (1): DECOMSYS::FlexIM2+ or DECOMSYS::FlexIM4+, V9.x (2): DECOMSYS::FlexIM4+, V11.x - DS4340(PFR4300) 2.) Update bit manipulation This version of RTI FlexRay Configuration Blockset 1.11 supports the manipulation of update bits used with FIBEX+. With the RTIFLEXRAYCONFIG UPDATE BIT SET simulink block it is possible to manipulate the update bits of PDUs. The blocks are generated into the Extra Blocks subsystem of a generated FlexRay configuration. 3.) Payload length manipulation This version of RTI FlexRay Configuration Blockset 1.11 supports the manipulation of the payload length of FlexRay frames. With the the RTIFLEXRAYCONFIG TX RAW DATA simulink block it is possible to modify the payload length of a transmit frame. With the the RTIFLEXRAYCONFIG RX RAW DATA simulink block it is possible to read the currently used payload length of a receive frame. The blocks are generated into the ECU specific subsystems of a generated FlexRay configuration. 4.) Creation of function-call triggered subsystems In this version of RTI FlexRay Configuration Blockset 1.11 for each application task trigger block a corresponding function-call triggered subsystem is generated within the FlexRay configuration. 5.) Wakeup Pattern The RTI FlexRay Configuration Blockset 1.11 includes a new RTI block which triggers a FlexRay controller to send wakeup pattern. The number and the characteristics of the wakeup symbol are taken from the FIBEX file and can not be configured within Simulink in this blockset version. 6.) RX Frame Status A new block RTIFLEXRAYCONFIG RX FRAME STATUS is added to the blockset. The block reads various status information of a received frame such as update bit value and nullframe state. b.2 FlexRay Configuration Tool: 1.) This version of FlexRay Configuration Tool supports the following dSPACE real-time systems: - Modular system based on a DS1005 with a DS4501 or DS4505 - Modular system based on a DS1006 with a DS4501 or DS4505 - MicroAutoBox 1401/1505/1506 Each system must be equipped with FlexRay IP modules in one of the following types: - DECOMSYS::FlexIM(MFR4200) (1) - DECOMSYS::FlexIM(V11 IP-Core) (2) - DECOMSYS::FlexIM(E-Ray) (1): DECOMSYS::FlexIM2+ or DECOMSYS::FlexIM4+, V9.x (2): DECOMSYS::FlexIM4+, V11.x - DS4340(PFR4300) 2.) The tool can create a CRC template file based on the current CRC configuration. Also the CRC configuration can be exported and imported. Frame ID's for frame specific calculation can be imported. 3.) Payload length manipulation of dynamic raw data frames. 4.) TRC file generation for monitoring, receiving and sending signals and raw data. See also section 3. for Last-Minute Limitations and Known Problems. 5.) Derivation of physical min/max values for signals with given coded min/max values and computation method identical, linear and texttable. 6.) XCP frames configuration (could be used with a corresponding RTI Bypass Blockset Version). 7.) The log file is written into the directory %DSPACE_ROOT%\Config. 8.) The FIBEX path can be saved relative to the project file. 9.) The ECU membership relation is documented in the report. 10.) Assignment of sending startup/sync frames to RX-Pool. 11.) The tool can be started with the following command line parameters: FlexRayConfigurationTool [] [] [-g] [-s] [-x] Specifies the project file to be loaded. Specifies the fibex file to be imported if no project file is specified or the fibex file referenced from the project file was not found. -g The code will be generated if a valid project was loaded. -s The project will be saved if it was changed. -x The tool will be closed automatically after all operations. Unchanged data will be lost. c. RTLib1401 / RTLib1005 / RTLib1006 1.) This patch fixes a problem with Task Deadline Violations inside the synchronization task of FlexRay when performing a restart of a FlexRay-controller with the Restart- or Membeship-Enable-Block of RTIFLEXRAYCONFIG. d. RTLib1603 1.) Problems fixed by this patch: Using the "/f32" option of the DOWN1603 tool can lead to a compiler error. e. RTILINMM 1.) Using RTILINMM and RTICAN / RICANMM can cause the LIN channel to cease working Due to a bug in the CAN Type 1 Firmware, the LIN channel will stop working for about 400 seconds 10 seconds after the simstate has changed to run ( no matter if the model has just been loaded or if the simstate has been switched). To solve this problem you have to install a new CAN Type 1 Firmware. f. RTICAN 1.) Lost messages for Gateway with not empty exclude list The RTICAN gateway block occasionaly fails to transport one or multiple messages after a message from the exclude list is filtered. g. RTICANMM 1.) DelayTimes do not work correctly 2.) User Variables remain in TRC file after deleting the MainBlock When deleting a RTICANMM MainBlock, the corresponding variable descriptions remain in the generated TRC file until a) a 'merge' is triggered manually from the GeneralSetup block, or b) the S-function for another MainBlock is created. This problem only occurs when using the user trace mechanism. Models using the newer TRC mechanism (BusSystems variable hierarchy) work correctly. 3.) Variant causes lost RX messages Using two Variant-MainSetups on one Controller will result in the loss of RX messages. 3. Limitations ------------------------------------------------------------------------- a. RTIFLEXRAYCONFIG 1.) RTIFLEXRAYCONFIG UPDATE BIT GET block With RTI FlexRay Configuration blockset 1.11 the block RTIFLEXRAYCONFIG UPDATE BIT GET is obsolete and it is removed from the RTI FlexRay Configuration library. This leads to unresolved library links (bad link) in older models using the RTIFLEXRAYCONFIG UPDATE BIT GET block. The removed RTIFLEXRAYCONFIG UPDATE BIT GET block can be replaced by the newly implemented RTIFLEXRAYCONFIG RX FRAME STATUS block which provides among others the update bit status of received frames. 2.) FlexRay IP module DECOMSYS::FlexIM(E-Ray) and RTIFLEXRAYCONFIG CONTROLLER STOP and RESTART blocks If the DECOMSYS::FlexIM(E-Ray) IP module resides in the protocol state 'READY' the controller has to be reset by the STOP block again before it can be restarted by the RESTART block. b. FlexRay Configuration Tool: 1.) The read and write access for signal with coded data type float64 is not supported for DS1006. ------------------------------------------------------------------------- End of File