| Version 6.5 (R2006b) Real-Time Workshop® Software Release Notes | |
This table summarizes what's new in Version 6.5 (R2006b):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | Yes—Details labeled as Compatibility Considerations, below. See also Summary. | Bug
Reports Includes fixes | No |
New features and changes introduced in this version are
Show eliminated statements Model Configuration Option Renamed
Change to Default Settings for Multitasking Diagnostic Options
PreLookup Index Search and Interpolation (n-D) Using PreLookup Block Changes
The Real-Time Workshop software has added support for the Simulink® Report Generator™. You can use the Simulink Report Generator to document a code generation project in a variety of output formats: Rich Text Format (RTF), Extensible Markup Language (XML), and Hypertext Markup Language (HTML). By using the Real-Time Workshop codegen.rpt setup file and the components Code Generation Summary and Import Generated Code, you can generate a report that includes
Model name and version
Real-Time Workshop product version
List of generated source and header (include) files
Optimization and Real-Time Workshop target selection and build process configuration settings
Mapping of subsystem numbers to subsystem labels for models that include subsystems
Listings of generated and custom code for the model
To see how the Report Generator fits into the general Real-Time Workshop workflow, see Workflow for Developing Applications Using Real-Time Workshop Software. For details on using the Report Generator with the Real-Time Workshop product, see the tutorial in Documenting a Code Generation Project. See rtwReport for a description of the Real-Time Workshop function for generating a report from the MATLAB command line or from a script. For descriptions of the new Real-Time Workshop Report Generator components, see Code Generation Summary and Import Generated Code in the Simulink Report Generator documentation. For details on using Report Generator, see the Simulink Report Generator documentation.
The Real-Time Workshop V6.5 (R2006b) software introduces a new pack-and-go utility that you can use to relocate static and generated code files for a model to another development environment, such as a secure system or an integrated development environment (IDE) that does not include MATLAB and Simulink. This utility uses the tools for customizing post code generation build processing and a packNGo function to find and package all files needed to build an executable image for a model into a compressed file that you can relocate and unpack using a standard zip utility.
For more information on how to use the new utility, see Relocating Code to Another Development Environment.
The V6.5 (R2006b) Real-Time Workshop software supports a new Simulink.SubSystem.getChecksum command that you can use to determine why subsystem code is not reused.
For a discussion on the code generation aspects of this feature, see Determining Why Subsystem Code Is Not Reused in the Real-Time Workshop documentation. For a description of the command, see Simulink.SubSystem.getChecksum in the Simulink documentation.
In previous releases, an input signal connected to a Merge block could not specify any storage class except Auto. In R2006b, an input signal connected to a Merge block can specify a non-Auto storage class. This class must be the same for every non-Auto input or output signal connected to the block.
For information about the Merge block, see the Merge reference page in the Simulink documentation. For details about using Merge block signal storage classes in generated code, see the bullet for the Merge block under Other Optimization Tools and Techniques in the Real-Time Workshop documentation.
The Real-Time Workshop software is enhanced to apply a more consistent formatting style to the code that it generates, including integrated custom code. The new style rules for code generation formatting pertain to
Comments
Blank lines and spaces
Indentation
Line breaks
International characters
#define statements
Function definitions
Branching and looping structural statements
Structure definition and value initialization statements
No code generation readability enhancement affects the syntax or semantics of the code. Such changes affect only the physical code appearance. Therefore, applications and correctly engineered automated tests should be unaffected by any readability enhancements. However, automated tests that depended on the physical code layout may be affected. You should change such tests to operate only on functional properties of the code.
The Real-Time Workshop software provides code generation support for the new Simulink Legacy Code Tool. This tool speeds the creation of S-functions from legacy C or C++ code. For a list of related demos, see New and Enhanced Demos.
A new findIncludeFiles function has been added to the build information API. This function searches for include (header) files in all source and include paths recorded in a model's build information object and adds the files found, along with their full paths, to the build information object.
For information on how to use the functions in the build information API, see Customizing Post Code Generation Build Processing.
The Show eliminated statements option on the Real-Time Workshop > Comments pane of the Configuration Parameters dialog box has been renamed to Show eliminated blocks. The corresponding configuration parameter ShowEliminatedStatement is not affected by this change.
For new models created with Simulink V6.5 (R2006b) or later, the default value for the following multitasking diagnostic options on the Configuration Parameters dialog is set to error to avoid generation of code that might corrupt data or produce unpredictable behavior.
Diagnostics > Sample Time > Multitask conditionally executed subsystem
Diagnostics > Data Validity > Data Store Memory Block > Multitask data store
For more information about these multitasking diagnostic options, see Diagnostics Pane: Sample Time and Diagnostics Pane: Data Validity in the Simulink documentation.
For models created with a version of Simulink before V6.5 (R2006b), when the following conditions exist, Simulink displays a dialog box that reports the issue and suggests that you change the diagnostic setting to error, as recommended by the Model Advisor.
The Tasking mode for periodic sample times option on the Configuration Parameters Solver pane is set to MultiTasking or the model includes an asynchronous task.
The diagnostic setting that corresponds to the multitasking issue is set to a value other than error.
You use the Real-Time Workshop software to generate code for the model.
The Real-Time Workshop software detects a multitasking issue that might corrupt data or produce unpredictable behavior.
The dialog presents you with the following options.
| Button | Action |
|---|---|
| Change | Change the diagnostic setting to error. |
| Ignore | Leave the diagnostic setting as is. |
| Always ignore | Leave the diagnostic setting as is and do not show the dialog box again. |
In previous releases, the Parameter Pooling optimization was optional and was enabled by default. Due to internal improvements, disabling Parameter Pooling would no longer be useful in any context. The optimization is therefore part of standard R2006b operation, and has been removed from the user interface.
Upgrading a model to R2006b inherently provides the effect of enabling Parameter Pooling in previous releases. No compatibility considerations result from this change. If the optimization was disabled in an existing model, a warning is generated when the model is first upgraded to R2006b. This warning requires no action and can be ignored.
The Real-Time Workshop build process no longer uses the runtime library functions in c/libsrc to generate code for the PreLookup Index Search and Interpolation (n-D) Using PreLookup blocks. Instead, the Real-Time Workshop build process generates the lookup functions for the two blocks dynamically. In addition, if you enable the Utility function generation option on the Real-Time Workshop > Interface pane of the Configuration Parameters dialog box, the lookup functions are stored as shared utility functions.
To avoid possible ambiguity in the comments in generated code, do not use the following character patterns in block names:
/*
*/
New demos are
| Demo... | Shows How You Can... | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| rtwdemo_codegenrpt | Use the Simulink Report Generator to automatically document code you generate with the Real-Time Workshop software. | |||||||||
Collection of custom code demos:
| Call external legacy C and C++ functions (existing or custom code) that are external to a Simulink model. The demos use an unsupported Legacy Code Tool application programming interface (API) to register a legacy function prototype and create necessary files for an S-function that calls the specified legacy function during simulation and in generated code. The Legacy Code Tool allows you to:
|
| Version 6.6 (R2007a) Real-Time Workshop Software | Version 6.4.1 (R2006a+) Real-Time Workshop Software | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |