dSPACE Release 6.3 November 2008 TargetLink 2.3.1 Last-Minute Information ================================================================= Copyright (c) 2008 dSPACE GmbH, Germany Contents: 1. Welcome 2. Notes for Floating Network License Users 3. Compatibility with Non-dSPACE Software 4. Compatibility with dSPACE Software 5. dSPACE Installation Manager 6. Licenses 7. Available Setup Version 8. New Features of TargetLink 2.3.1 9. TargetLink Known Problem Reports List 10. Any Questions? ================================================================= 1. Welcome ----------------------------------------------------------------- Welcome to our new release, TargetLink 2.3.1. TargetLink 2.3.1 is the first patch for TargetLink Release 2.3. It is also part of dSPACE Release 6.3 and includes bug fixes for TargetLink Release 2.3 up to November 2008. It also aims to provide compatibility with MATLAB release R2008a and R2008b, and to introduce some new TargetLink features. 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.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.1 is located in the folder \LicServer on this DVD. NOTE: A Windows 2000, Windows XP or Windows Vista platform is required for the dSPACE Floating Network License Server. 3. Compatibility with Non-dSPACE Software ----------------------------------------------------------------- Before installing dSPACE software, check the following prerequisites for compatibility with non-dSPACE software. Prerequisites for TargetLink 2.3.1: - Supported Microsoft Operating Systems - Microsoft Windows 2000 Professional (with Service Pack 4) - Microsoft Windows XP Professional (32-bit version with Service Pack 2 or 3). Service Pack 3 is recommended. - Microsoft Windows Vista32 SP1 (32-bit version with Service Pack 1). Only the versions Windows Vista Business, Ultimate, and Enterprise are supported. The versions Windows Vista Home and Starter are not supported. - Supported MathWorks Releases - TMW Release R2008b - TMW Release R2008a - TMW Release R2007b+ - TMW Release R2007a+ - TMW Release R2006b - TMW Release R2006a+ - Supported MATLAB MEX Compiler for Host Simulation - Microsoft Visual C/C++ Ver. 6.0, 7.1, or Ver. 8.0 - LCC Compiler as shipped with the supported MATLAB versions Latest updates of compatibility information on this DVD and previous releases can be obtained from http://www.dspace.com/goto?compatibility 4. Compatibility with dSPACE Software ----------------------------------------------------------------- TargetLink 2.3.1 can be installed and used in combination with the following dSPACE releases: - dSPACE Release 6.3 - dSPACE Release 6.2 - dSPACE Release 6.1 - dSPACE Release 6.0 - dSPACE Release 5.4 - dSPACE Release 5.3 For detailed information on how to use CalDesk and RCP and HIL software with TargetLink 2.3.1, refer to "Installing dSPACE Software" in the "dSPACE Release Quick Software Installation Guide". 5. 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.pdf on this DVD. 6. Licenses ----------------------------------------------------------------- To use TargetLink 2.3.1 together with MATLAB R2008a or R2008b, a separate license is required. This license is checked when R2008a or R2008b is detected and also enables you to work with former MATLAB releases. Apart from that, the same license protection systems are used as for TargetLink 2.3. |MATLAB < R2008a |MATLAB R2008a |MATLAB R2008b __________________|________________|______________|______________ TL_MLCUR2008 | | | License available | OK | OK | OK | | | No TL_MLCUR2008 | | | License available | OK | fault | fault 7. Available Setup Version ----------------------------------------------------------------- With TargetLink 2.3.1, only an update setup is available (via DVD and Internet download). The update setup requires an existing TargetLink 2.3 installation, on top of which TargetLink 2.3.1 is installed. 8. New Features of TargetLink 2.3.1 ----------------------------------------------------------------- - New Features of the TargetLink AUTOSAR Module TargetLink 2.3.1 comes with the following new features of the TargetLink AUTOSAR Module: * TargetLink Support for AUTOSAR Release 3.0.2 The TargetLink AUTOSAR Blockset supports AUTOSAR Release 3.0.2 and continues support for AUTOSAR Release 2.1.4 and 2.0 SP3. For these standards, an AUTOSAR-compliant XML file can be imported, code for the software component can be generated, a simulation can be carried out, and an AUTOSAR-compliant XML file can be exported. TargetLink lets you select between AUTOSAR Release 3.0.2, 2.1.4 and 2.0 SP3 during export and import. By default, AUTOSAR Release 2.1.4 is assumed. This is important with reference to export, as the AUTOSAR-compliant XML file is directly generated in the code generation hook function. As a result, you cannot make changes there. Note: TargetLink does not support all the features specified in AUTOSAR Release 3.0.2. * Using the TargetLink AUTOSAR Block Library in Stand-Alone mode You can now use the TargetLink AUTOSAR Blockset in stand-alone mode for the purpose of modeling, offline simulation in Simulink as well as prototyping using RTW. Note that in future versions of TargetLink, it will no longer be possible to specify AUTOSAR-related information in block dialog elements in the stand-alone mode. Control design and simulation will naturally be possible but setting AUTOSAR-related data will require the full-featured mode and hence a TargetLink Base Suite license in future TargetLink versions. TargetLink 2.3.1 is an exception in that it allows the specification of AUTOSAR-related data in stand-alone mode entirely for technical reasons. Please take this into account when setting up your development processes. * Using the Stand-Alone Model Manager for AUTOSAR Models The Stand-Alone Model Manager, which can be used to wrap TargetLink code in an S-Function, now also supports models with TargetLink AUTOSAR blocks. There is a limitation: the build processes, whether for TargetLink S-functions or RTW code generation, can involve only one TargetLink subsystem or S-function at a time. * Generating a TargetLink Subsytem from an SWC Description File with Client-Server Communication TargetLink now supports client-server communication (unidirectional and bidirectional) when generating a TargetLink subsystem from an SWC description file. Runnable Inport and Outport blocks and Client Port blocks are added to the generated runnable subsystem and configured accordingly. The following new properties are available: - ForceClientPortUsage [{'off'},'on'] Lets you specify which kind of TargetLink AUTOSAR blocks are to be used to model client-server communication within a runnable subsystem. If this property is set to 'on', Client Port blocks are always used independently of the operation and of the number and kind of operation arguments. If it is set to 'off' (default), the following applies: * The operation is unidirectional and has ARGIN arguments only, a Runnable Outport Block is used. * The operation is unidirectional and has ARGOUT arguments only, a Runnable Inport block is used. - ModelClientServerPorts ['off',{'on'}] Lets you specify if SWC ReceiverPort and SWC SenderPort blocks are to be added to the SWC subsystem ('on') or not ('off') for client ports and server ports of the modeled software component. - TerminateInOutPorts ['off',{'on'}] Lets you specify if the inports of added Runnable Outport and Client Port blocks, and the outports of added Runnable Inport and Client Port blocks, are to be connected to the Simulink Ground or Simulink Terminator block ('on') or remain unconnected ('off'). TIP: To retrieve information on all the available options, type help tl_generate_swc_model in the MATLAB Command Window. * Merging SWC Descriptions with the Data Dictionary The AUTOSAR SWC-D Merge Explorer, which can be used to merge AUTOSAR software component descriptions with the current Data Dictionary and is available under the View menu of the Data Dictionary Manager, now allows the specification of import options for AUTOSAR XML import. Import options are stored as individual properties under /config/Autosar in the Data Dictionary. The property names are identical to those used in the API import function. If the DD node is missing, it is automatically created with default options upon first use of the AUTOSAR SWC-D Merge Explorer (recommended way to create the Data Dictionary node). Set the properties of the /config/Autosar node to specify AUTOSAR import options for the tool. * Defining an AUTOSAR-Compliant Type Structure As of TargetLink 2.3.1, you can suppress the generation of tl_basetypes.h when generating AUTOSAR software components. The advantage of this approach is that from the SWCs' point of view, the types are defined according to the AUTOSAR standard at the right point (definition reference /AUTOSAR). An easy way to suppress the generation of tl_basetypes.h is to load the AUTOSAR template dsdd_master_autosar.dd from dspaceroot/dsdd/config/ using the DD Merge Explorer. Then right-click the DD object (MT_tl_basetypes) that you want to merge into the open DD project file and select "Copy left (overwrite)" command from the context menu. As a result, the generation of tl_basetype.h is suppressed. - New Features of the Data Dictionary Manager * Object Duplication and Insertion It is now possible to duplicate an arbitrary object by selecting it in the Data Dictionary Manager and pressing Ctrl + D (or via context menu). The duplicated object is inserted below it. * Unsetting/Deleting Properties in the Object Explorer The Object Explorer of the Data Dictionary Manager now supports an unset/delete operation for properties. It is available via a right mouse click. - New Combinations of Microcontrollers and Target Compilers Board Name | Supported Target Compiler ____________|__________________________________________________ Freescale | Wind River Diab PowerPC Family C Compiler MPC5561EVB | version 5.6 (Diab56) | | Green Hills MPC55xx C Compiler | version 5.0 (GHS50) | | Metrowerks MPC55xx Family C Compiler CodeWarrior | version 2.3 (Met23) For a detailed list of supported C compilers for TargetLink 2.3.1, refer to the chapter Third-Party Software in the appendix of the Software Installation and Management Guide. 9. TargetLink Known Problem Reports List ----------------------------------------------------------------- For a list of open problems in TargetLink 2.3.1, refer to the Known Problem Reports 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. 10. 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