dSPACE Solutions for Control April 2006 TargetLink Release 2.1.6 Build-No. 2006042501 Last-Minute Information ============================================================ Copyright (c) 2006 dSPACE GmbH, Germany Contents: 1. Welcome 2. Installation Notes 3. Compatibility with Non-dSPACE Software 4. Using Other dSPACE Software and This Release Simultaneously 5. Licenses 6. New Features of TargetLink 2.1.6 7. Discontinued Features 8. Limitations 9. TargetLink Known Problems List 10. Any Questions? ============================================================ 1. Welcome ------------------------------------------------------------ TargetLink 2.1.6 is the first patch for TargetLink Release 2.1. It includes all bug fixes for TargetLink Release 2.1 up to April 20, 2006. It also aims to provide compatibility with MATLAB Release 2006a+ and to introduce some new TargetLink features. NOTE: We constantly strive to improve our products and to maintain compatibility with the latest MATLAB releases. During our compatibility tests performed with the MATLAB 2006a release, some incompatibilities were detected and communicated to The MathWorks. These incompatibilities do not occur with the current update MATLAB R2006a+. We therefore recommend that you install that release, which you can find at the Web site of The MathWorks. We would greatly appreciate your feedback, to help us to improve our products. Please send us any comments you might have concerning this release, the documentation, or dSPACE products in general. Just send an e-mail to: feedback@dspace.de 2. Installation Notes ------------------------------------------------------------ TargetLink 2.1.6 supports different MATLAB releases. Depending on the MATLAB version you intend to use, you need a Key Disk to install TargetLink 2.1.6. For MATLAB R14SP3, you can use one of the following Key Disks: - Key Disk for TargetLink 2.1.5 - Key Disk for TargetLink 2.1.6 For MATLAB 2006a, the TargetLink 2.1.6 Key Disk is required. To install this patch, carry out the following steps. A.) Make sure that TargetLink 2.1 or TargetLink 2.1.5 is installed for the MATLAB version you intend to use. B.) Run TL2.1.6_Setup.exe to update your existing TargetLink installation. C.) Follow the instructions given by the installation program. 3. Compatibility with Non-dSPACE Software ------------------------------------------------------------ Before installing dSPACE software, check the following prerequisites for compatibility with non-dSPACE software. The latest version available for each software product is supported, except where a different version is stated. - Supported Operating Systems - Windows XP, Windows 2000 (Service Pack 1) - Windows NT 4.0 NOTE: It is strongly recommended that you install the latest Service Packs. However, it is not recommended to work with Service Pack 4 under Windows NT 4.0 as it may cause problems when you use dSPACE and third-party software. - Supported MATLAB Releases Latest updates of compatibility information can be obtained from: http://www.dspace.com/goto?compatibility - MATLAB Ver. 7.2 with Simulink 6.4.1 and Stateflow 6.4.1 (R2006a+) - MATLAB Ver. 7.1 with Simulink 6.3 and Stateflow 6.3 (R14SP3) - MATLAB Ver. 7.0.x with Simulink 6.x and Stateflow 6.x (R14.x) - MATLAB Ver. 6.5.x with Simulink 5.x and Stateflow 5.x (R13.x) - Supported MATLAB MEX compiler - Microsoft Visual C/C++ Ver. 5.0, 6.0, 7.0 or Ver. 7.1 - LCC compiler as shipped with MATLAB 2006a, R13.x or R14.x NOTE: The compilers MSVC Ver. 8.0 and Open Watcom Ver. 1.3 are not supported, as they are not supported by the respective Simulink 32-bit versions. 4. Using Other dSPACE Software and This Release Simultaneously ------------------------------------------------------------ It is possible to use Solutions for Control and CalDesk with TargetLink 2.1.6 simultaneously. To do so, specify the same destination path (installation folder) during setup and install the products in the order of their release date. In addition to TargetLink 2.1, TargetLink 2.1.6 has been qualified for the following dSPACE releases: - Solutions for Control Release 5.1 - Solutions for Control Release 5.0 - CalDesk 1.3 5. Licenses ------------------------------------------------------------ - To use TargetLink 2.1.6 together with MATLAB R14SP3 or MATLAB R2006a, a separate license is required. Apart from that, the same license protection systems are used as for TargetLink 2.1. - For the dSPACE Floating Network License Server, a Windows Server 2003, Windows XP, Windows 2000, or Windows NT platform is required. Floating Network License users also have to update their existing Floating Network License Server to at least version 2.0. The most recent version can be obtained free of charge from: http://www.dspace.com/goto?FNLServer 6. New Features of TargetLink 2.1.6 ------------------------------------------------------------ - A2L File Export Module Supports Export of Variables of the Bitfield Data Type The A2L File Export module can export variables of the bitfield data type to an A2L file. After you start A2L file export, the data to be exported is written to the respective MEASUREMENT/CHARACTERISTIC entries in the A2L file. - A2L File Export Module Supports Export of EPROMIdentifier and EPROMIdentifierAddress Properties The A2L File Export module evaluates whether EPROMIdentifier and EPROMIdentifierAddress properties are available in the ///TargetInfo dSPACE Data Dictionary node. If so, these properties are generated to the EPK and ADDR_EPK entries in the A2L file as follows: ADDR_EPK -> Property value of EPROMIdentifierAddress EPK -> Property value of EPROMIdentifier - Interaction Between TargetLink Property Manager and DD Manager The TargetLink Property Manager provides three ways of accessing the dSPACE Data Dictionary. The first is via the DD button in the toolbar of the TargetLink Property Manager. The second is to access DD objects directly by right-clicking an object property in the Block Explorer and then clicking Show or Edit in the context menu. The third way is to double-click a DD object in the Property Editor. - Interaction Between TargetLink Block Dialog and DD Manager TargetLink 2.1.6 allows you to access DD objects via TargetLink block dialogs. You can select, edit, or jump to a specific DD object by right-clicking the Variable, Class, Type, or Scaling edit field. - Mark Compute-Through-Overflow (CTO) TargetLink supports the ‘compute-through-overflow’ calculation method, which avoids computations in unnecessary word lengths. Calculations that are computed using this method can optionally be marked by a code comment ("/* CTO */") in the generated code. To make the Code Generator insert code comments, use the command line option "PolyspaceSupport" in the tl_pre_codegen_hook.m file. This allows you to distinguish between CTOs used intentionally by TargetLink and possible overflow errors introduced by improper scaling or signal range specification. - New Combinations of Microcontrollers and Target Compilers Board Name | Supported Target Compiler ___________________|________________________________________ NEC F_Line-Drive It| NEC Compilers Ver. 2.5, and Ver. 2.72 | RapidPro Control | Microtec C/C++ Compiler for PowerPC Unit (DS1603) | Family Ver. 3.2 | WindRiver Diab Compiler for PowerPC | Ver. 5.3 | MPC5554DEMO | WindRiver Diab Compiler for PowerPC | Ver. 5.3 | AXIOM MPC5554 | Metrowerks CodeWarrior C/C++ | Compiler for Embedded PowerPC | Ver. 1.5 Renesas SH2 | SH2eEVB | Renesas SH Series C Compiler Ver. 9.0 EVB7058 | Renesas SH Series C Compiler Ver. 9.0 Note: For PIL simulations with the RapidPro Control Unit (DS1603), you need the USB driver from the Solutions for Control Release (Release 5.0 and later). Keep in mind that Windows NT 4.0 is not supported in this case. - Support of new Evaluation Board MCT HCS12DP512 T-Board (Freescale MC9S12DP512CPV) The MCT HCS12 T-Board (Freescale MC9S12DP256PV) is no longer supplied but still supported. It has been replaced by the MCT HCS12DP512 T-Board (Freescale MC9S12DP512CPV). Note that the memory layouts of the two boards are not compatible. However, the Target Simulation Module and the Target Optimization Module remain unchanged. - Order of Include Statements Given in Custom Look-Up Script is Used in the Generated Code The order of include statements you define in your custom look-up script is kept during code generation. Starting with TargetLink 2.1.6, include statements are no longer resorted. It is your responsibility to guarantee that variables are defined and declared before their first usage, particularly if there are dependencies between includes. - Redefinition of Code Generator Default Variable Classes Up to now, the Code Generator did not always use the variable class specified with the SLGlobal or SLGlobalInit filter criteria in the variable class template (for example, for output variables of blocks connected to a Simulink outport of a control-flow-controlled subsystem), but a modified SLLocal class. This made it difficult to have all global variables, for example, initialized in a restart function. This behavior was changed in TargetLink 2.1.6. The Code Generator now evaluates the SLGlobal or SLGlobalInit template for all global variables. If required, the previous behavior can be generated by using the "DeriveDefaultSymbolClasses" Code Generator option. - Support of Cascaded Merge Blocks Starting with TargetLink 2.1.6, cascaded Merge blocks are supported by the Code Generator. The block at the output of the Merge block cascade specifies the variable created for the cascade. If you do not make the specification in this block, the scaling parameters of the predecessor blocks of the cascade are used. Variable specifications made at any other block inside the cascade are not allowed and lead to an error message. - Improved Detection of Function Calls TargetLink analyses not only the signal source but also the signal destination. Function calls that are fed into a subsystem via the signal line are detected if the destination block of the line is a function call trigger port. This also applies if the function call source outside the TargetLink subsystem is not available. Because of this improved analysis, the conversion does not insert a TargetLink InPort block (as formerly happened, forcing you to remove it to continue working with TargetLink). 7. Discontinued Features ------------------------------------------------------------ The MCT HCS12 T-Board (Freescale MC9S12DP256PV) is no longer supplied but still supported. It has been replaced by the MCT HCS12DP512 T-Board (Freescale MC9S12DP512CPV). Note that the memory layouts of the two boards are not compatible. However, the Target Simulation Module and the Target Optimization Module remain unchanged. 8. Limitations ------------------------------------------------------------ - Cast Output Signal to TargetLink Type Option in Stand-Alone Mode The previous limitation, that the "Cast output signal to TargetLink type" option of TargetLink blocks does not have any effect in stand-alone mode, is no longer valid in its entirety. The limitation now applies only to the following TargetLink blocks: o Abs block o Fcn block o Direct Look-Up Table (n-D) block o Merge block o MultiPortSwitch o Rate Limiter block o Trigonometric Function block For MATLAB R13.x this applies also to the following TargetLink blocks: o Discrete-Time Integrator block o MinMax o Math For MATLAB R14, the proper functionality of the "Cast output signal to TargetLink type" option of the Math block also depends on the function selected in the block dialog. 9. TargetLink Known Problems List ------------------------------------------------------------ For a list of open problems in TL 2.1.6, refer to the Known Problems List on our Web site at: http://www.dspace.com/goto?Problems_tl You should check the Web support page regularly for the latest TargetLink news. If you encounter any problem when using TargetLink, send an e-mail to: support.tl@dspace.de 10. Any Questions? ------------------------------------------------------------ If you encounter any problems when using TargetLink: - Refer to the respective product manuals and online help - Then visit the Support section of our Web site at http://www.dspace.com/goto?support - Contact your distributor, or send us an e-mail at: support.tl@dspace.de ------------------------------------------------------------ End of File