Real-Time Workshop Embedded Coder Major Bug Fixes

Build Process Fixed to Allow ERT S-Function and Integer Support

In Release 14, the Real-Time Workshop build process failed if you set your configuration parameters as follows:

• RTW system target file on the Real-Time Workshop pane specified an ERT target
• You selected the Create Simulink (S-function) block option and cleared the Support floating-point numbers option on the Real- Time Workshop/Interface pane.

This is fixed in Release 14SP1.

Code Generated When Terminate function required and Generate reusable code Options Selected Now Compiles

In Release 14, if you configured a model such that you selected both the Terminate function required and Generate reusable code options on the Real-Time Workshop/Interface pane, Real- Time Workshop could generate code that would fail to compile. This is fixed in Release 14SP1.

Generation of an S-Function No Longer Fails If Inline Parameters Option Is Disabled

In Release 14, the Real-Time Workshop Embedded Coder could fail to generate an S-Function for an ERT target if you cleared (disabled) the Inline parameters option on the Optimization panel of the Configuration Parameters dialog. If a failure occurred, the coder generated an S-function C file that failed to compile, and an error message similar to the following would appear:

structure has no member named `InitialOutput'

This bug is fixed in Release 14SP1.

Incompatibility Between Model Reference and Suppress Error Status Option Corrected

In Release 14, Real Time Workshop Embedded Coder could generate code that fails to compile when both of the following conditions existed:

• The model used the Model Reference feature.
• You selected the Suppress error status in real-time model data structure option on the Interface pane under Real-Time Workshop on the Configuration Parameters dialog.

This problem has been fixed in Release 14SP1.

Invalid Code No Longer Generated for Data Store Memory Block

In previous releases, it was possible for the Data Store Memory block to generate uncompilable code if the associated data was defined to be of a nonaddressable custom storage class (for example, GetSet). This is fixed in Release 14SP1.

Problems with Data Initialization in Generated Code Fixed

The following problems with data initialization in generated code have been fixed in Release 14SP1:

• A regression introduced in Release 14 caused Real-Time Workshop to ignore the Remove root level I/O initialization option, and use the Remove internal state zero initialization option setting to control initialization of root level I/O instead.

• In earlier releases, Real-Time Workshop did not generate intialization code for internal states, regardless of whether you selected the Remove internal state zero initialization option, if all the data was of a floating-point type and you selected the Use memset to initialize floats and doubles to 0.0 option.

• The tooltip for Use memset to initialize floats and doubles to 0.0 did not state that it applied only to internal data for it to be accurate.

rtwlib Compilation Failures for ERT Targets Built With Compiler Optimizations Enabled and Complex Number Support Disabled Fixed

In Release 14, if both of the following conditions existed for an ERT target build, compilation of rtwlib would fail:

• You cleared (did not select) the Support complex numbers option on the Real-Time Workshop:Interface subpane of the Configuration Parameters dialog
• You specified compiler optimization options by including OPT_OPTS in the make command line

This is fixed in Release 14SP1.

Signals and States with Simulink Custom Storage Classes Now Have Dynamic Initialization By Default

Prior to Release 14SP1, the default setting for data initialization for predefined Simulink custom storage classes (CSCs) was Static except for Macro/ImportFromFile/GetSet. The default data initialization setting has been changed to Auto, such that:

• For parameters, Static initialization is used (no change).
• For signals and states, Dynamic initialization is used, which is consistent with the built-in Simulink storage classes.

Note that you can suppress dynamic initialization by selecting the following Configuration Parameters dialog options:

• Optimization->Data initialization->Remove root level I/O zero initialization - controls dynamic initializtaion of root level I/O
• Optimization->Data initialization->Remove internal state zero initialization - controls dynamic initialization of states and nonroot level I/O

Specification of Absolute and Relative Pathnames for Data with Custom Storage Class Allowed

In Release 14, you could not specify the full (absolute) or relative path for header files used by custom storage classes (for example, ExportToFile and ImportFromFile).

In Release 14SP1, you can specify header files for imported data by using just the file name (without any directories) or by using the absolute or relative path. The filename is used exactly as specified (no extension is added). If you specify a relative path, specify the path relative to the directory in which code generation is initiated.

For files generated by the Real-Time Workshop (such as the header file for exported data), you must specify the filename without any directories. If you do not provide the appropriate extension Real-Time Workshop automatically adds .h for header files and .c for source files.

uget_param and uset_param Being Obsoleted: Use get_param and set_param

In Release 14, the section "Utilities for Accessing Model Configuration Properties" in the Real-Time Workshop Embedded Coder documentation discussed use of the utility functions uget_param and uset_param to automate model configuration. These functions are being obsoleted. You should now use get_param and set_param instead, as explained in the Release 14SP1 documentation.