Release 5.4p1 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 5.4. 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.) Bug fix of an error during change of mask or workspace parameter in ControlDesk when using logical statements like 'MyParam <= 5' for mask parameters. Error message: Internal Error in APH (Code: 143 ) (Unable to get array 'DS_APH_ParamsToWrite') 2.) Bug fix for: Error during RTI build process when using comments in Simulink block or mask parameter definitions. The error only cccures when the option 'include mask and workspace parameters' is selected. Error message: RTI Build Error RTI_MASKPARAMMAP: Unable to evaluate Workspace parameter "comment" (referenced at least in block: "ParamComents/Subsystem") ---> Reason: "Error using ==> evalin Undefined function or variable 'coment'." 3.) 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. 4.) 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. 5.) Bug fix for: DS1103BIT_OUT causes compiler error under special conditions. Under certain circumstances, if the block DS1103BIT_OUT_Gx 'Initial output state' settings are set to different initialization states, the compiling process causes errors like: " COMPILING "model_data.c" COMPILING "D:\dspaceroot\MATLAB\RTI1103\C\rti_sim_engine.c" (E) C0020; ".\model_rti.c", line 121 pos 23; identifier "D" is undefined ds1103_bit_io_clear(D|S|1|1|0|3|_|D|I|O|3|_|C|L|E|A|R); ^ (E) C0020; ".\model_rti.c", line 121 pos 25; identifier "S" is undefined ds1103_bit_io_clear(D|S|1|1|0|3|_|D|I|O|3|_|C|L|E|A|R); ... (E) C0020; ".\model_rti.c", line 121 pos 53; identifier "A" is undefined ds1103_bit_io_clear(D|S|1|1|0|3|_|D|I|O|3|_|C|L|E|A|R); ^ (E) C0020; ".\model_rti.c", line 121 pos 55; identifier "R" is undefined ds1103_bit_io_clear(D|S|1|1|0|3|_|D|I|O|3|_|C|L|E|A|R); ^ 10 Errors COMPILING FAILED (1) MAKE PROCESS ABORTED *** Stopped RTI build procedure " 6.) Bug fix regarding DS5001 blocks: Check if frequency detection is in conflict with other DS5001 units, which access to channel 16. Check is now performed within one board specified by dialog blockparameter Board Number. 7.) DS2103 MUX ADC block causes compiler warning if option inline parameters is enabled: argument of type "const real_T *" is incompatible with parameter of type "dsfloat *" ds2103_out(DS2103_1_BASE, 1, &...); 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.7.2 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.) CRC Check for frames This version of RTI FlexRay Configuration Blockset 1.7.2 supports CRC check for frames. With the RTIFLEXRAYCONFIG RX FRAME CRC CONTROL and the RTIFLEXRAYCONFIG TX FRAME CRC CONTROL simulink block it is possible to enable and disable CRC check for individual frames. The blocks are generated into the Extra Blocks subsystem of a generated FlexRay configuration. 3.) Raw data access for frames with or without signals This version of RTI FlexRay Configuration Blockset 1.7.2 supports raw data acces for transmit and receive frames. With the RTIFLEXRAYCONFIG RX RAW DATA and the RTIFLEXRAYCONFIG TX RAW DATA simulink block it is possible to access the raw data of transmit and receive frames. The blocks are generated into the ECU specific subsystems of a generated FlexRay configuration. 4.) Enable/Disable of static frames This version of RTI FlexRay Configuration Blockset 1.7.2 supports enabling and disabling of static frames. With the RTIFLEXRAYCONFIG STATIC TX FRAME ENABLE block it is possible to enable or disable static frames. The block is generated into the Extra Blocks subsystem of a generated FlexRay configuration. Within this subsystem one RTIFLEXRAYCONFIG STATIC TX FRAME ENABLE block per ECU is generated. 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.) CRC Check for frames by user CRC C-code file see \MATLAB\RTIFLEXRAYCONFIG\FlexRayAL\crc_template.c 3.) Raw data access for frames with or without signals 4.) Enable/Disable of static frames Software Enable/Disable of a static frame A Null-Frame or old value (in regards to CHI code generator option) will be sent Hardware: Enable/Disable of buffers of static slots There is no bus activity within this slot 5.) TRC file generation for monitoring signals Signals selected for monitoring will not be visible per default in the monitoring subsystem in Simulink any more. For these signals a trace file will be generated so the signlas can be monitored directly with ControlDesk. To enable the block generation for monitoring signals switch the configurable signal property "Generate SL block" to True. 6.) Derivation of physikal data types for signals with a given computation method identical, linear and textable. For the computation method linear the physical data type will be derived if n0 and n1 is set. c. RTIRPCU 1.) Bug fix for block RPCU_MCPWM_CA_TPU: Under certain circumstance it is not possible to select a certain TPU even though all necessary TPU channels are routed. d. 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. 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.) RX Main block sporadically receives wrong data sent by a Gateway block on the same channel When using a Main block for receiving messages sent by a Gateway block on the same channel, the signal values of the received messages change arbitrarily. 2.) Compiler error in models with multiple gateway blocks Models containing multiple gateway blocks fail to compile with warning/error messages like the following: RTI1005 platform: (W) #A0307-D Symbol: rticanmm_gw_filter_func_c2 in file: already defined in file: (W) #A0307-D Symbol: rticanmm_gw_filter_func_c1 in file: already defined in file: RTI1006 platform: LINKING APPLICATION ... RTICANMM_gateway2_GW1_P0.o86: In function `rticanmm_gw_filter_func_c1': RTICANMM_gateway2_GW1_P0.o86(.text+0x1bb3): multiple definition of `rticanmm_gw_filter_func_c1' RTICANMM_gateway1_GW2_P0.o86(.text+0x1e18): first defined here RTICANMM_gateway2_GW1_P0.o86: In function `rticanmm_gw_filter_func_c2': RTICANMM_gateway2_GW1_P0.o86(.text+0x1c6c): multiple definition of `rticanmm_gw_filter_func_c2' RTICANMM_gateway1_GW2_P0.o86(.text+0x1ed1): first defined here 3.) DelayTimes do not work correctly 4.) Gateway block suspends working After downloading an application or changing its simState, the Gateway block temporarily stops working. At most 20 seconds after downloading or altering simState, the Gateway block resumes working. 5.) 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. Limitations ------------------------------------------------------------------------- No known limitations of this patch. ------------------------------------------------------------------------- End of File