TargetLink Release 1 - dSPACE

Important NoticeThis document contains proprietary information that is protected by copyright. All rightsare reserved. Neither the documentation nor software may be copied, photocopied,reproduced, translated, or reduced to any electronic medium or machine-readable form, inwhole or in part, without the prior written consent of dSPACE GmbH.© Copyright 1999-2002 by:dSPACE GmbHTechnologiepark 25D-33100 PaderbornGermanyThis publication and the contents hereof are subject to change without notice. dSPACEGmbH makes no warranty of any kind with regard to this publication, including but notlimited to the implied warranties of merchantability or fitness for a particular purpose.dSPACE GmbH shall not be liable for errors contained herein or direct, indirect, special,incidental, or consequential damages in connection with the furnishing, performance, oruse of this publication.Brand names or product names are trademarks or registered trademarks of theirrespective companies or organizations.dSPACE GmbHTechnologiepark 25D-33100 PaderbornGermany- 2 -

1 Release DescriptionTargetLink Release 1.3p2 is the second patch for TargetLink Release 1.3. It includes the previous patch1.3p1 and all bug fixes of TargetLink Release 1.3 until Apr. 16, 2002.For a description of additional or changed features in TargetLink Release 1.3p2, refer to chapters 4, 5 and 6.- 4 -

2 Compatibility InformationTargetLink 1.3p2 was tested and is compatible to the following MATLAB ® environments:• MATLAB R11.1 with Simulink 3.0.1, and Stateflow 2.0.1• MATLAB R11.1 with Simulink 3.0.1, and Stateflow 3.0.4• MATLAB R12 with Simulink 4.0.0, and Stateflow 4.0.4• MATLAB R12.1 with Simulink 4.1.0, and Stateflow 4.1.1• MATLAB R12.1 with Simulink 4.1.1, and Stateflow 4.2.1The supported Windows platforms are:• Win 95 / 98 / Me / NT / 2000Note, that The MathWorks has not released MATLAB ® R11.x and R12.x for Windows XP. TargetLink 1.3p2does also not support Windows XP.For the latest compatibility information refer to the dSPACE web serverhttp://www.dspace.de/en/products/compatib.htm- 5 -

3 Download and Installation of Patch 1.3p2TargetLink Release 1.3p2 is distributed as a self-extracting ZIP archive, which is available from theTargetLink support area on the dSPACE Web server. The tl13p2.exe patch archive is split into 6 parts tomake download from the Web more reliable.An installation of TargetLink Release 1.3 must exist on your PC, before you can install the patch. You alsoneed to close MATLAB ® before invoking the update.1. Download the following files from http://www.dspace.de/Targetlk/support.htm, and save them to atemporary folder on your PC (e.g., c:\temp):invoke_tl13p2.battl13p2.part1tl13p2.part2tl13p2.part3tl13p2.part4tl13p2.part5tl13p2.part6(3 kB)(3.2 MB)(3.2 MB)(3.2 MB)(3.2 MB)(3.2 MB)(3.2 MB)Exit MATLAB ® , if still open.2. Execute invoke_tl13p2.bat to start the patch installation and to copy all required files to thecorresponding TargetLink folders. This command may take several minutes if a virus checker isenabled on your PC.3. TargetLink is now updated and ready to be started.4. During installation the tl13p2.exe self-extracting ZIP archive is created from tl13p2.part1-6.You may keep the tl13p2.exe file for later installation on other PCs in your department. Oncetl13p2.exe exists, the files listed above are no longer needed.- 6 -

4 Changes in TargetLink Release 1.3p2 compared to TargetLinkRelease 1.3p14.1 Stateflow 4.2.1 CompatibilityTargetLink 1.3p2 additionally supports the latest Stateflow ®information refer to chapter 2.Release 4.2.1. For detailed compatibility4.2 Excluding messages from the Message BrowserWith the commandtl_error_set('DefaultExcludedMessages',)a list of message numbers can be defined, which are initially excluded when the Message Browser opens.For example, this command can be placed in a startup M-script or in the pre-codegen-hook function.With a MATLAB ® clear all command the list of excluded messages is cleared!4.3 Hyphen Supported in Names of Generated FilesYou can now use hyphens in the names of generated files, for example, "my-file.c". This is supported for• FUNCTION block,• ADDFILE block,• tl_set command,• tl_get command,• file attribute of variable classes.The Simulink ® block name of the top-level TargetLink subsystem must not contain a hyphen as it must be avalid C identifier. If you wish to rename the C file generated for the top-level TargetLink subsystem, you mayplace a FUNCTION block into the subsystem.4.4 New option "view" for the ASAP2 File GeneratorThe new option "view" can be used in ASAP2 template files to customize the hierarchical appearance ofCHARACTERISTICs and MEASUREMENTs in the generated ASAP2 file.view = 'FunctionHierarchy';view = 'FlatList';The ASAP2 generator creates a hierarchical tree view. That meanseach CHARACTERISTIC and MEASUREMENT is assigned to thefunction where it is defined. It is possible that one variable appearsin multiple nodes of the tree, if it is referenced by more than onefunction.All CHARACTERISTICs and MEASUREMENTs are generated intoone flat list. Each variable appears only once.For more information refer to the ASAP2 template files in the configuration directory\matlab\tl\config- 7 -

4.5 Long User Type Names in Blocks DialogsThe width of the 'Type' popup in TargetLink Dialog boxes is now adapted to the string length of userdefined data type names. In previous versions it could happen that very long type names were clipped.4.6 Support for the Motorola HCS12 (Star12) Target with Cosmic CompilerA new Target Simulation Module (TSM) is available for the Motorola HCS12 processor (formerly calledStar12) with Cosmic Compiler Ver. 4.4.4.7 Support for the Motorola HC12 Target with Cosmic 4.4 CompilerThe Cosmic 4.4 compiler is now supported for target simulation with the HC12EVB evaluation board.- 8 -

5 Changes in TargetLink Release 1.3p1 compared to TargetLinkRelease 1.35.1 Improved Implementation of Stateflow Temporal LogicThe calculation of the required data type for temporal logic counters has been improved. Range propagationmechanisms are used in order to find the minimal data type that is necessary to implement the temporallogic counter.Additionally, TargetLink Release 1.3p1 now also accepts an expression with a floating-point result type asthe first argument of a temporal logic operator. The user should ensure that the expression passed as thefirst argument of a temporal logic operator always evaluates to an integral value. Otherwise, there might bedifferences between the floating-point and the fixed-point model behavior because the use of nonintegralvalues as the first argument of a temporal logic operator is not specified in the Stateflow semantics.5.2 Optional Replacement of Stateflow Graphical Functions by Custom CFunctionsTargetLink Release 1.3p1 now supports the replacement of Stateflow graphical functions by custom Cfunctions in production code. Function classes with storage attribute ‘extern’ can be selected for Stateflowgraphical functions. The custom C function can be provided using an ADDFILE block.If the function class specified for a Stateflow graphical function has the storage attribute ‘extern’, the nameproperties of the function and its parameters have the default setting ‘$O’.5.3 Fixed-Point Implementation of sqrt in StateflowIf the actual parameter of a call to ‘sqrt’ in Stateflow is a fixed-point expression, TargetLink Release 1.3p1generates a call to a fixed-point implementation of ‘sqrt’ instead of a call to the floating-point function ‘sqrt’implemented in the standard C library ‘math’.5.4 Optimization of Custom-Lookup Function CallsFor custom-lookup functions TargetLink Release 1.3p1 provides a new property called ‘movable’. Thisproperty specifies whether a call to the custom-lookup function can be optimized by moving it, for example,into a case of a switch statement or into an if/else branch of a conditional statement.The allowed values for this property are ‘yes’ and ‘no’, the default setting is ‘no’. The ‘movable’ propertycan be set in the custom-lookup script by using the ‘tlscript’ command.If the execution of a custom-lookup function does not have any side effects, the ‘movable’ property shouldalways be set to ‘yes’.5.5 Document Generator EnhancementsWith TargetLink Release 1.3p1 the Document Generator’s commands ‘Overview’, ‘TargetLinkSubsystems’ and ‘Simulation Results’ support the following new properties: ‘ImageMaxWidth’,‘ImageMaxHight’, ’TableWidth’, ‘FontSize’ and ‘SeparateFiles’ (‘TargetLink Subsystems’command only). These properties allow you to control the size of the inserted images as well as the width ofthe generated tables. Furthermore the font size used in the document can be set by the user. If desired, thedescription of each function can be generated into a separate HTML file.Additionally, the new 'AutodocCustomization' block, which is available from ‘tlsamples/AuxiliaryBlocks’, can be used to customize the generated documentation. It can be placed anywhere in a Simulink ®model and allows you to insert the following information into the generated documentation:- 9 -

• A user comment• A screen copy of the Simulink ® subsystem where the block resides• New chaptersDetailed information can be obtained from the block’s help.5.6 Standalone Model ManagerTargetLink Release 1.3p1 provides a new tool, called ‘Standalone Model Manager’. This tool can beinvoked from the corresponding block residing in ‘tlSamples/Auxiliary Blocks’. It allows thegeneration of a stand-alone S-function wrapper for the production code. The stand-alone S-function can becopied automatically into a destination model, where it can be used to perform simulations independent ofthe TargetLink environment. If required, all necessary header, source and library files needed to create areal-time application for the destination model can be copied to the specified directory. If a real-timeapplication is to be generated for the destination model with dSPACE RTI and Real-Time Workshop ® , thecorresponding user make file and variable description file (TRC-File) can also be generated. Detailedinformation can be obtained from the block’s help.5.7 Support for the SH2 Target with Hitachi 6.0 CompilerThe Hitachi 6.0 compiler is now supported for target simulation with the SH2EVB and SH2eEVB evaluationboards.- 10 -

6 Known Limitations6.1 Action Port Triggered or Enabled SubsystemsIf Simulink ® detects that an action port triggered system or an enabled system is not executed, it resets the‘reset’ outports of all internal child systems. In MATLAB R12.1 additionally all systems which are called viaa Function Call Generator or a Stateflow block are reset. This is not supported by TargetLink Release 1.3p2.TargetLink Release 1.3p2 resets only the ‘reset’ outports of the currently evaluated system.6.2 Function Call EventsAs in Simulink ® , event signals can be used only once. TargetLink Release 1.3p2 does not support demuxedand partially used event signals with a signal width greater than one. (The only exception is a Demux blockdirectly connected to a function call generator.)If the source of a function call event resides inside a nonvirtual subsystem, and the sink of the event liesoutside, the input values of a called system may encounter a one step delay compared to Simulink'sbehavior.6.3 For and While Iterator blocksTriggered subsystems are normally calculated at each iteration. In TargetLink Release 1.3p2 triggeredsubsystems (including D Flip-Flop and J-K Flip-Flop blocks) within for, while or do-while loops are notcalculated at each iteration even though the trigger condition is true.6.4 Multiple Default Transitions in Stateflow 4.2.0Multiple default transitions are not supported by TargetLink Release 1.3p2 when using Stateflow Release4.2.0. If you are using Stateflow 4.2.0 and your model contains multiple default transitions, apply thefollowing workaround for each node with multiple default transitions: Create a new unconditional defaulttransition which leads to a newly created junction. Connect the start points of all the old default transitionswith this new junction.6.5 Propagated Signal LabelsPropagated signal labels of Stateflow outputs work with TargetLink only if they are visible. Set ‘showpropagated signals’ to ‘on’ or ‘all’ if you want to be able to select these signals in bus selector blocks.6.6 Assignment BlockThe following applies for Assignment blocks with an external control input:The signals covered by each inport and the outport, respectively, must have the same scaling and data type.The control input signal must have an integer type.- 11 -

7 Known Problems ListFor a list of problems which have been fixed with TargetLink Release 1.3p2 compared to TargetLinkRelease 1.3, refer to the known problems listTL13p2_KnoProList.pdfwhich is available from the TargetLink support area on the dSPACE Web server:http://www.dspace.deCheck the Web support page regularly for the latest TargetLink news.If you encounter any problems when using TargetLink, send an e-mail tosupport.tl@dspace.de- 12 -