文本講義說(shuō)明案例simulink coder release notes

1、Release Notes for Simulink® CoderHow to Contact MathWorksWeb NewsgroupTechnical SupportProduct enhancement suggestions Bug reportsDocumentation error reportsOrder status, license renewals, passcodes Sales, pricing, and general informationcomp.soft-sys.suggest bugs doc service info(Phone)(Fax)Th

2、e MathWorks, Inc. 3 Apple Hill DriveNatick, MA 01760-2098For contact information about worldwide offices, see the MathWorks Web site.Release Notes for Simulink® Coder© COPYRIGHT 20112013 by The MathWorks, Inc.The software described in this document is furnished undernse agreement. The soft

3、ware may be usedor copied only under the terms of the license agreement. No part of this manual may be photocopied or reproduced in any form without prior written consent from The MathWorks, Inc.FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation by, for,

4、 or through the federal government of the United States. By accepting delivery of the Program or Documentation, the government hereby agrees that this software or documentation qualifies as commercial computer software or commercial computer software documentation as such terms are used or defined i

5、n FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms andconditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern the use, modification, reproduction, release, performance, display, and disclosure of the Program and Documen

6、tation by the federal government (or other entity acquiring for or through the federal government)and shall supersede anying contractual terms or conditions. If this License fails to meet thegovernments needs or is inconsistent in any respect with federal procurement law, the government agrees to re

7、turn the Program and Documentation, unused, to The MathWorks, Inc.Trademarksand Simulink are registered trademarks of The MathWorks, Inc. Seefor a list of additional trademarks. Other product or brand names may be trademarks or registered trademarks of their respective holders.PatentsMathWorks produ

8、cts are protected by one or more U.S. patents. Please see for more information.ContentsR2013aData, Function, and File Definition . . . . . . . .Optimized interfaces for Simulink functions called in Stateflow . . . . . . . . . . . . . . .Shortened system-generated identifier names . . . . .234Code Ge

9、neration. . . . . . . . . . . . .Shared utility name consistency across builds withum identifier length control . . . . . . .789bar . . . .Code Generation Advisor available onCode generation build when reusable library subsystemlink status changes . . . . . . . . . . . .1011s usable in mreference hi

10、erarchies . Protected mDeployment . . . . . . . . . . . . . . .Simplified multi-instance code with support for referenced12s . . . . . . . . . . . . . . . .m13External mode control panel improvements and C APIaccess . . . . . . . . . . . . . . . .15Hardware configuration relocation from Target Prefe

11、rences block to Configuration Parameters dialog . . . . .Support ending for Eclipse IDE in a future release . . .GRT malloc target to be removed in future release . . .171920Customization . . . . . . . . . . . . . . .MakeRTWSettingsObject mparameter removed . . .Check bug reports for issues and fixe

12、s . . . . . . .212223R2012bUnified and simplified code interface for ERT and GRT targets . . . . . . . . . . . . . . . .26iiiConvenient packNGo dialog for packaging generated code and artifacts . . . . . . . . . . . . . .Reusable code for subsystems shared by referenced30s . . . . . . . . . . . . .

13、. . .m31Code generation for protected ms for acceleratedsimulations and host targets . . . . . . . . .32Reduction of data copies with buses and more efficientfor-loops in generated code . . . . . . . . .33Unified rtiostream serial and TCP/IP target connectivity for all host platforms . . . . . . . .

14、 . . . .Constant parameters generated as individual constants to shared location . . . . . . . . . . . . .Code efficiency enhancements . . . . . . . . .Optimized code generation of Delay block . . . . . .Search improvements in code generation report . . . .GRT template makefile change for MAT-file l

15、ogging support . . . . . . . . . . . . . . . .Change for blocks that use TLC custom code functions in multirate subsystems . . . . . . . . . . .Mrtwdemo_f14 removed from software . . . . .Check bug reports for issues and fixes . . . . . . .343536373839404142 R2012aSimplified Call Interface for Gener

16、ated Code . . . . .Incremental Code Generation for Top-Level Ms. . .Minimal Header File Dependencies with packNGo Function . . . . . . . . . . . . . . .ASAP2 Enhancements for MReferencing and Structured Data . . . . . . . . . . . . .Serial External Mode Communication Using rtiostreamAPI . . . . . .

17、. . . . . . . . . . .Improved Data Transfer in External Mode Communication . . . . . . . . . . . . .Changes for Desktop IDEs and Desktop Targets . . . .Code Generation Report Enhancements . . . . . .44464748505152535455565758Keywords for Code Generation . . . . .NewImproved MAT-File Logging. . . . .

18、 . . . . .rtwdemo_f14 Being Removed in a Future Release . . .New and Enhanced Demos . . . . . . . . . .Check bug reports for issues and fixes . . . . . . .ivContents R2011bn-D Lookup Table Block Supports Tunable Table Size. .Complex Output Support in Generated Code for the Trigonometric Function Blo

19、ck . . . . . . . . .Code Optimizations for the Combinatorial Logic Block . .Code Optimizations for the Product Block . . . . . .Enhanced MISRA C Code Generation Support for Stateflow Charts . . . . . . . . . . . . . . . .Change for Constant Sample Time Signals in Generated Code . . . . . . . . . . .

20、 . . . . .New Code Generation Advisor Objective for GRTTargets . . . . . . . . . . . . . . . .Improved Integer and Fixed-Point Saturating Cast . . .Generate Multitasking Code for Concurrent Execution on Multicore Processors . . . . . . . . . . . .Changes for Desktop IDEs and Desktop Targets . . . .K

21、eyword UNUSED_PARAMETER . . . . . . 6061626364656667686970Target API for Verifying® Distributed ComputingServer (MDCS) Worker Configuration for ParallelBuilds . . . . . . . . . . . . . . . .71License Names Not Yet Updated for Coder ProductRestructuring . . . . . . . . . . . . .727374New and Enh

22、anced Demos . . . . . . . . . .Check bug reports for issues and fixes . . . . . . . R2011aCoder Product Restructuring . . . . . . . . . .Changes for Desktop IDEs and Desktop Targets . . . .Code Optimizations for Discrete State-Space Block, Product Block, and MinMax Block . . . . . . . . . .Ability t

23、o Share User-Defined Data Types Across768285s . . . . . . . . . . . . . . . .M86C API Provides Access to Root-Level Inputs andOutputs . . . . . . . . . . . . . . .87ASAP2 File Generation Supports Standard Axis Format for Lookup Tables . . . . . . . . . . . . .ASAP2 File Generation Enhancements for C

24、omputation Methods . . . . . . . . . . . . . . .Lookup Table Block Option to Remove Input Range Checks in Generated Code. . . . . . . . . . . .888990vReentrant Code Generation for Stateflow Charts That Use Events . . . . . . . . . . . . . . . .Redundant Check Code Removed for Stateflow Charts That U

25、se Temporal Operators. . . . . . . . . .Support for Multiple Asynchronous Function Calls Into a9192Block . . . . . . . . . . . . . .M9394Changes to ver Function Product Arguments . . . . .Updates to Target Language Compiler (TLC) Sems and Diagnostic Information . . . . . . . . .Change to Terminate F

26、unction for a Target Language Compiler (TLC) Block Implementation . . . . . .New and Enhanced Demos . . . . . . . . . .Check bug reports for issues and fixes . . . . . . .95969798viContentsR2013aVersion: 8.4New Features: Yes Bug Fixes: Yes1 R2013aData, Function, and File Definition2Optimized interfa

27、ces for Simulink® functions called in Stateflow®Optimized interfaces for Simulink functions called in StateflowPreviously, when subsystem input and output signals were used inside aStateflow® chart, terated code for the input and output signals wascopied into global variables. In R201

28、3a, when the Subsystem block parameter “Function packaging” is set to Inline, the subsystem inputs and outputs called within a Stateflow chart are now local variables. This optimization improves execution speed and memory usage.3 R2013aShortened system-generated identifier namesFor GRT targets, the

29、length of the system-generated identifier names are shortened to allow for more space for the user-specified components of the generated identifier names. The name changes provide a more consistent andpredictable nasystem that uses camel case, no underscores or plurals,and consistent abbreviations f

30、or both a type and a variable.The default for the system-generated identifiers per mare changed.4Before R2013aIn R2013aTypeBlockIO, BBTypeExternalInputsExtUTypeExternalInputSizesExtUSizeTypeExternalOutputsExtYTypeExternaOutputSizesExtYSizeTypeParametersPTypeConstBlockIOConstBConst TypeMachineLocalDa

31、taMachLocalConst TypeConstParam, ConstPConstPConst Type, Global VariableConstParamWithInit, ConstWithInitPConstInitPConst Type, Global VariableD_Work, DWorkDWType, Global VariableMassMatrixGlobalMassMatrixType, Global VariablePrevZCSigStates, PrevZCSigStatePrevZCXType, Global VariableContinuousState

32、s, XXType, Global VariableStateDisabled, XdisXDisType, Global VariableStateDerivatives, XdotXDotType, Global VariableShortened system-generated identifier namesThe default for the system-generated identifiers names per referenced m or reusable subsystem are changed.5Before R2013aIn R2013aTypertB, BB

33、Type, Global VariablertC, CConstBType, Global VariablertDW, DWDWType, Global VariablertMdlrefDWork ,MdlrefDWorkMdlRefDWType, Global VariablertP, PPType, Global VariablertRTM, RTMRTMType, Global VariablertX, XXType, Global VariablertXdis, XdisXDisType, Global VariablertXdot, XdotXDotType, Global Vari

34、ableBefore R2013aIn R2013aTypeZCSignalValues, ZCSignalValuesZCVType, Global VariableDefaultParametersDefaultPGlobal VariableGlobalTIDGlobalTIDGlobal VariableInvariantSignalsInvariantGlobal VariableMachineMachLocalGlobal VariableNSTAGESNSTAGESGlobal VariableObjectObjGlobal VariableBridgeBrdgGlobal Va

35、riableUUGlobal VariableUSizeUSizeGlobal VariableYYGlobal VariableYSizeYSizeGlobal Variable R2013aFor more information, see “Construction of Generated Identifiers”.6Before R2013aIn R2013aTypertZCE, ZCEZCEType, Global VariablertZCSV, ZCSVZCVType, Global VariableCode GenerationCode Generation7 R2013aSh

36、ared utility name consistency across builds with um identifier length controlIn R2013a, shared utility names remain consistent in terated codeacross multiple builds of your m. In addition, shared utility namesnow comply with theum identifier length parameter specified onthe Code Generation > Symb

37、ols pane in the Configuration Parametersdialog box. Theum identifier length parameter does not apply tofixed-point and DSP utilities.8Code Generation Advisor available on bar Code Generation Advisor available onTo launch the Code Generation Advisor, on the mbarbar, selectCode > C/C+ Code > Cod

38、e Generation Advisor. Alternatively, the Code Generation Advisor remains available in the Configuration Parameters dialogbox, on the Code Generation pane.For information about using the Code Generation Advisor to configure yourmto meet specific code generation objectives, see:“Application Objectives

39、” in Simulink® Coder“Application Objectives” in Embedded Coder®9 R2013aCode generation build when reusable library subsystem link status changesShared functions for a reusable library subsystem are generated only for resolved library links. If you enable or disable a library link for a reu

40、sablesubsystem, and then build your m, new code is generated.10 Protected ms usable in m reference hierarchies Protected m hierarchiess usable in mreferencePreviously, you could not protect a mand use it in a m hierarchy.referenceIn R2013a, you can use protected ms in a mreference hierarchy. Inaddit

41、ion, R2013a includes enhancements to the programmatic interface aswell as the dialog for m.To learn more about changes to the programmatic interface, seeRtect and to view the changes to the mSimulink.Mdialog, see “Create a Protected M”.11 R2013aDeployment12 Simplified multi-instance code

42、 with support for referenced ms Simplified multi-instance code with support forreferenced msR2013a provides simplified multi-instance code deployment for GRT targetswith support for referenced ms.In previous releases, to generate reentrant, reusable code with dynamicallocation of per-instance mgrt_m

43、alloc.tlc, for the mdata, you had to selepecialized target,. If you selected the GRT malloc target for am, you could not include referenced ms in your mdesign.Beginning in R2013a, you can generate reentrant, reusable code for a GRTmby selecting the mconfiguration option Generate reusablecode, which

44、is located on the Code Generation > Interface pane of the Configuration Parameters dialog box.When you select Generate reusable code for a GRT m, the build processgenerates reusable, multi-instance code that is reentrant, as follows:Terated m.c source file contains an allocation function thatdyna

45、mically allocates mdata for each instance of the m.Terated code passes the real-time mdata structure in, byreference, as an argument to mfunctions._step and the other mentry pointThe real-time mdata structure is exported with the mfile.h headerWith the new GRT moption Generate reusable code, you can

46、 generateand deploy multi-instance code for your m target, and you can include referenced mwithout selecting a specializeds in your mdesign.13 R2013aNote Use of the grt_malloc.tlc target is no longer recommended. For more information, see “GRT malloc target to be removed in future release” on page 2

47、0.14 External mode control panel improvements and C API access External mode control panel improvements and C API accessImproved External mode graphical controlsExternal mode dialog boxes are now consistent with other Simulink dialog boxes, with improved layout, ability to resize, and consistent set

48、s of buttons. The improved dialog boxes include the External Mode Control Panel and the subsidiary dialog boxes that you can open from it, External Signal & Triggering and Enable Data Archiving. Here is the improved Enable Data Archiving dialog box.To view the improved External mode dialog boxes

49、, open a mCode > External Mode Control Panel.and select15 R2013aC API access from External mode simulationsIn previous releases, the External mode and C API data interfaces for m code were mutually exclusive. Beginning in R2013a, you can generate codefor your mwith both the External mode and C AP

50、I interfaces enabled.Custom code now can access C API data structures during an External mode simulation.For more information, see “Generate External Mode and C API Data Interfaces”.16 Hardware configuration relocation from Target Preferences block to Configuration Parameters dialog Hardware configu

51、ration relocation from Target Preferences block to Configuration Parameters dialogThe contents of the Target Preferences block have been relocated to the new Target Hardware Resources tab on the Coder Target pane in the Configuration Parameters dialog box.The Target Preferences block has been remove

52、d from the Desktop Targets block library.If you open a m that contains a Target Preferences block, a warninginstructs you that the block is optional and can be removed from your m.Opening the Target Preferences block automatically displays the Target Hardware Resources tab.17 R2013aFor instructions on how to use Target Hardware Resources to build andrun a mon desktop system, see “MSetup”.For information about specific par