dSPACE Release 5.4 July 2007 TargetLink 2.2.1 Last-Minute Information ===================================================================== Copyright (c) 2007 dSPACE GmbH, Germany Contents: 1. Welcome 2. Notes for Floating Network License Users 3. Compatibility with Non-dSPACE Software 4. Using CalDesk 1.3, 1.4, or 1.4.1 with TargetLink 2.2.1 5. Using RCP and HIL Software with TargetLink 2.2.1 6. TargetLink Compatibility with Java Virtual Machine 7. dSPACE Installation Manager 8. Licenses 9. Available Setup Versions 10. New Features of TargetLink 2.2.1 11. General Limitations 12. TargetLink Known Problems List 13. Any Questions? ===================================================================== 1. Welcome --------------------------------------------------------------------- Welcome to our new release, TargetLink 2.2.1. Before you start the installation, please read this ReadMe file. We constantly strive to improve our products, so your input is crucial. We welcome any feedback you might have concerning this Release, the documentation, or dSPACE products in general. Just send an e-mail to feedback@dspace.de 2. Notes for Floating Network License Users --------------------------------------------------------------------- Floating Network License users have to update their existing Floating Network License Server at least to version 2.0.1. The most recent version can be obtained free of charge from http://www.dspace.com/goto?FNLServer The setup for License Server Version 2.0.1 is located on this DVD in the folder \LicServer. 3. Compatibility with Non-dSPACE Software --------------------------------------------------------------------- Before installing dSPACE software, check the following prerequisites for compatibility with non-dSPACE software. Prerequisites for TargetLink 2.2.1: - Microsoft Windows 2000 (Service Pack 4) Microsoft Windows XP (32-bit version with Service Pack 2) - TargetLink 2.2.1 supports MATLAB R13SP2, R14SP2, R14SP2+, R14SP3, R2006a+, R2006b, and R2007a+. - MATLAB MEX compiler - Microsoft Visual C/C++ Ver. 5.0, 6.0, 7.0, or Ver. 7.1 - LCC compiler as shipped with MATLAB R2007a+, R2006x, R14.x, or R13.x - Watcom C/C++ Ver. 11 (only English versions) - A Windows NT, Windows 2000, or Windows XP platform is required for the dSPACE Floating Network License Server. Latest updates of compatibility information on this DVD and previous releases can be obtained from http://www.dspace.com/goto?compatibility 4. Using CalDesk 1.3, 1.4, or 1.4.1 with TargetLink 2.2.1 --------------------------------------------------------------------- It is possible to use CalDesk 1.3, 1.4, or 1.4.1 with TargetLink 2.2.1. Just specify the same destination path in both setups. 5. Using RCP and HIL Software with TargetLink 2.2.1 --------------------------------------------------------------------- For detailed information on how to use RCP and HIL software with TargetLink 2.2.1, refer to "Installing dSPACE Software" in the "dSPACE Release Quick Software Installation Guide". 6. TargetLink Compatibility with Java Virtual Machine --------------------------------------------------------------------- If you work with Windows 2000 and MATLAB R2007a+, the JVM 1.5.0_07 originally installed with MATLAB can cause errors that particularly impair work with TargetLink, although the same errors also occur without TargetLink. If so, it is mandatory to use JVM 1.5.0_12 in conjunction with TargetLink 2.2.1. You can install the JVM 1.5.0_12 from Tools\Java in the root folder of the DVD. To make MATLAB use this JVM, you must set the MATLAB_JAVA environment variable to the path of the JVM JVM 1.5.0_12. For all other supported MATLAB versions, it is strongly recommended to use Java Virtual Machine 1.4.2_08 as recommended for TargetLink 2.2. You can install the JVM 1.4.2_08 from Tools\Java in the root folder of the DVD. To make MATLAB use this JVM, you must set the MATLAB_JAVA environment variable to the path of the JVM 1.4.2_08. 7. dSPACE Installation Manager --------------------------------------------------------------------- If you want to use software from this release and older releases at the same time and on the same PC, you have to switch between installations in different subfolders with the dSPACE Installation Manager (see below for details). The dSPACE Installation Manager is supplied with the dSPACE software package and installed on your PC during installation. To start the dSPACE Installation Manager, choose Programs -> dSPACE Installation Manager from the Start menu, and click dSPACE Installation Manager. For further information on how to use the tool, refer to \Tools\InstallManager\InstallManager_Eng.pdf on this DVD. 8. Licenses --------------------------------------------------------------------- To use TargetLink 2.2.1 together with MATLAB R2007a+, a separate license is required. Apart from that, the same license protection systems are used as for TargetLink 2.2. 9. Available Setup Versions --------------------------------------------------------------------- Basically, two setup versions are available: - DVD Setup (available only on the DVD) - Update Setup (available only via Internet download) Use the DVD setup if you want to install any dSPACE products, to achieve compatibility with the latest MATLAB release, or to install new TargetLink features or Target Simulation Modules (TSM). The folder in which you want to install the software must not contain any other software. The update setup, which is available only via Internet download, allows you to update an existing TargetLink installation. This setup does not install any new features or Target Simulation Modules, nor performs a MATLAB Compatibility Update. 10. New Features of TargetLink 2.2.1 --------------------------------------------------------------------- - New Features of the TargetLink AUTOSAR Module TargetLink 2.2.1 comes with the following new features of the TargetLink AUTOSAR Module: * Support of AUTOSAR Release 2.0.0 SP3 * The AUTOSAR import/export tool of the dSPACE Data Dictionary (DD) holds AUTOSAR package information. For these purposes, you have to select the Enable package support checkbox in the import/export file dialog of the DD Manager. For typedefs, scalings, and interfaces, the AUTOSAR package information is stored in the Package custom string property at the GroupInfo object of the parent TypedefGroup/ScalingGroup/InterfaceGroup. For mode declaration groups and software components, the AUTOSAR package information is stored in the Package custom string property of the ModeDeclarationGroup/SoftwareComponent object. For example, if you want to define a typedef called my_typedef in the AUTOSAR package /my_path/my_package in the Data Dictionary, perform the following steps: 1. Create a typdef group called my_package. 2. Inside the my_package typedef group, create a GroupInfo object. 3. At the GroupInfo object, create a custom property of string type and name it Package. As the value of the Package custom property, enter the package name including the path: /my_path/my_package. 4. Create the my_typedef Typedef object in the my_package typedef group. If you want to define a software component called my_SWC in the AUTOSAR package /my_path/my_package in the Data Dictionary, perform the following steps: 1. Create a SoftwareComponent object called my_SWC. 2. At the SoftwareComponent object, create a custom property of string type and name it Package. As the value of the Package custom property, enter the package name including the path: /my_path/my_package. * TargetLink 2.2.1 lets you generate a TargetLink frame model for an SWC description in the DD or from an AUTOSAR XML description. The frame model contains Runnable blocks, Runnable InPort/OutPort blocks, and SWC Sender/Receiver Port blocks. In order to create a MyComponent.mdl TargetLink model from a given my_component.xml SWC description, you have to enter the following command in the MATLAB Command Window: tl_generate_swc_model('Model', 'MyComponent', 'SwcDescFileName', 'my_component.xml') * The conversion of TargetLink to Simulink is now supported for models containing AUTOSAR blocks. After conversion from TargetLink to Simulink, you can reconvert your model to TargetLink. If you do, TargetLink reinserts the AUTOSAR blocks which were removed during conversion from TargetLink to Simulink, and recovers all block data. NOTE: If the blocks contain invalid DD references during the model reconversion, TargetLink issues an error message. * TargetLink's Autoscaling tool can now be used in conjunction with models that contain TargetLink AUTOSAR blocks. Note that the AUTOSAR blocks themselves are not scaled but that range information is properly propagated back and forth. However, the TargetLink Client Port block is not supported by TargetLink's Autoscaling tool. * TargetLink 2.2.1 AUTOSAR import/export supports UUIDs for the following AUTOSAR elements: - ARRAY-TYPE - ATOMIC-SOFTWARE - COMPONENT-TYPE - BOOLEAN-TYPE - CLIENT-SERVER-INTERFACE - COMPU-METHOD - DATA-ELEMENT-PROTOTYPE - INTEGER-TYPE - INTER-RUNNABLE-VARIABLE - MODE-DECLARATION - MODE-DECLARATION-GROUP - OPERATION-PROTOTYPE - P-PORT-PROTOTYPE - PRIMITIVE-TYPE-WITH-SEMANTICS - R-PORT-PROTOTYPE - REAL-TYPE - RECORD-ELEMENT - RECORD-TYPE - RUNNABLE-ENTITY - SENDER-RECEIVER-INTERFACE - UNIT-SPEC * TargetLink 2.2.1 supports the specification of invalid values at typedefs. If you want to specify an invalid value for a typedef, you have to create a custom property named "InvalidValue", and store the invalid value at this custom property. * The AUTOSAR Module supports the following options: - EnablePackageSupport: If you activate this checkbox, during AUTOSAR export the AUTOSAR XML file to be generated is split up into several AUTOSAR XML files according to the specification in the DD. You can use the DD Package property to specify how the file is split. During AUTOSAR import, you can specify several AUTOSAR XMLfiles, and the structure of the files is represented in the DD where possible. - Subsystems: Specifies the subsystems which the AUTOSAR file is exported from, but in contrast to the File option, its value is a cell array of names. - Files: If the EnablePackageSupport checkbox is selected and several AUTOSAR XMLfiles are generated from one DD, the files must be passed in one AUTOSAR import call. You can do this with the Files option, which contains a cell array with the names of the AUTOSAR XML files to be imported. * AUTOSAR Modeling Guideline - AUTOSAR DD Master Template In TargetLink 2.2.1, the AUTOSAR DD Master Template has changed. To import and export an AUTOSAR SWC description properly, the TargetLink model must be based on the new AUTOSAR DD Master Template. If you already have an existing TargetLink 2.2 AUTOSAR model, open the model's DD file in the Data Dictionary Manager. Then start the Merge Explorer with the AUTOSAR DD Master Template and merge the content of the AUTOSAR DD Master Template with your original DD file. - Modeling of fixpoint types For smooth import/export scenarios, it is highly recommended that the types that are referenced by AUTOSAR objects (for example, by data elements of interfaces, operation arguments, interrunnable variables, ...) are always modeled as DD Typedef objects, i. e. scaling and min and max values are not specified at the individual data elements, but as constraints directly at the Typedef object. Scalings should be modeled as global scalings under the Scalings node in the DD and referenced by the Typedef objects. Each typedef with constraints should have its own Scaling object. - Merging External Functions TargetLink 2.2.1 lets you merge external functions with identically modeled interfaces, for example, functions resulting from subsystems which are duplicated in the model by copy & paste. To have TargetLink merge external functions, you have to enable the EnableExternFunctionMerge code generation option. For details on how to use code generation options, refer to "tl_pre_codegen_hook" in the TargetLink API Reference. By default, this option is turned off. NOTE: TargetLink does not verify if the subsystems whose functions are to be merged are identical. It only verifies if the following points match: * The settings in the Function blocks and * The settings of the blocks specifying the interface variables You must ensure that the subsystems representing the external functions to be merged are identical. If you merge external functions, you must note the following limitations: * Stateflow charts cannot be merged. * External functions cannot be merged if their interfaces contain bus ports that specify bus structs. * External functions that have pointers to structs as formal parameters cannot be merged with other subsystems. - Support of Change Detection for Stateflow Charts TargetLink 2.2.1 supports the change detection feature, which is new in MATLAB R2007a+. Limitation: If a Stateflow chart contains a graphical function which has exactly the same name as a valid change detection operator ('hasChanged', 'hasChangedFrom' or 'hasChangedTo'), the graphical function's name will conceal the name of the change detection operator, and the graphical function will be used instead of the change detection operator. This will lead to simulation differences between MIL and SIL/PIL simulations. - New Combinations of Microcontrollers and Target Compilers Board Name | Supported Target Compiler ___________________|________________________________________ Freescale | Metrowerks Code Warrior MC56F8367EVM | for MC56F83xx Version 8.1 | Renesas SDK72513 | Renesas Compiler Version 9.0.3 Evaluation Board | 11. General Limitations --------------------------------------------------------------------- - MATLAB versions supported by the TargetLink AUTOSAR module The TargetLink AUTOSAR module only supports MATLAB R14SP2, R14SP2+, R2006a+, R2006b, and R2007a+. - INIT section of Custom Code block may not be in production code The INIT section of a Custom Code block on the top level of the TargetLink subsystem may not result in production code. This will cause differences between MIL and SIL simulation. The INIT section of a Custom Code block only results in production code if one of the following conditions is met: * The Custom Code block resides in an enabled or ActionPort-triggered subsystem with "States when enabling" or "States when action is resumed" set to "reset". * The Custom Code block resides in the TargetLink subsystem or in an incremental subsystem whose Function block has the "Force init function" option activated. If the Custom Code block resides in the TargetLink subsystem, the missing production code INIT section may cause differences between MIL and SIL simulation. Solution: If a Custom Code block has an INIT section and resides in the TargetLink subsystem or in an incremental subsystem, insert a Function block and activate the "Force init function" option. 12. TargetLink Known Problems List --------------------------------------------------------------------- For a list of open problems in TargetLink 2.2.1, refer to the Known Problems List on our Web site at http://www.dspace.com/goto?Problems_tl Please check the Web support page regularly for the latest TargetLink news. 13. Any Questions? --------------------------------------------------------------------- If you encounter any problems when using TargetLink - Have a look at 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