Note   Additional Target function library values may be listed if you have created and registered target function libraries with the Real-Time Workshop® Embedded Coder™ software, or if you have licensed any Link or Target products. For more information on the Target function library values for Link or Target products, see your Link or Target product documentation.

Back to Top

Support: floating-point numbers

Specify whether to generate floating-point data and operations.

Settings

Default: on

On

Generates floating-point data and operations.

Off

Generates pure integer code. If you clear this option, an error occurs if the code generator encounters floating-point data or expressions. The error message reports offending blocks and parameters.

Dependencies

• This parameter only appears for ERT-based targets.

• Selecting this parameter enables Support: non-finite numbers and clearing this parameter disables Support: non-finite numbers.

• This parameter must be the same for top-level and referenced models.

Command-Line Information

Recommended Settings

Back to Top

Support: absolute time

Specify whether to generate and maintain integer counters for absolute and elapsed time values.

Settings

Default: on

On

Generates and maintains integer counters for blocks that require absolute or elapsed time values. Absolute time is the time from the start of program execution to the present time. An example of elapsed time is time elapsed between two trigger events.

If you select this option and the model does not include blocks that use time values, the target does not generate the counters.

Off

Does not generate integer counters to represent absolute or elapsed time values. If you do not select this option and the model includes blocks that require absolute or elapsed time values, an error occurs during code generation.

Dependencies

• This parameter only appears for ERT-based targets.

• You must select this parameter if your model includes blocks that require absolute or elapsed time values.

Command-Line Information

Recommended Settings

See Also

Timing Services

Back to Top

Support: non-finite numbers

Specify whether to generate nonfinite data and operations.

Settings

Default: on

On

Generates nonfinite data (for example, NaN and Inf) and related operations.

Off

Does not generate nonfinite data and operations. If you clear this option, an error occurs if the code generator encounters nonfinite data or expressions. The error message reports offending blocks and parameters.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter is enabled by Support: floating-point numbers.

• This parameter must be the same for top-level and referenced models.

Command-Line Information

Recommended Settings

Back to Top

Support: continuous time

Specify whether to generate code for blocks that use continuous time.

Settings

Default: off

On

Generates code for blocks that use continuous time.

Off

Does not generate code for blocks that use continuous time. If you do not select this option and the model includes blocks that use continuous time, an error occurs during code generation.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter must be on if your model includes blocks that require absolute or elapsed time values.

• This parameter must be off when generating an S-function wrapper for an ERT target; the code generator does not support continuous time for this target scenario.

Command-Line Information

Recommended Settings

See Also

• Support for Continuous Time Blocks, Continuous Solvers, and Stop Time

• Automatic S-Function Wrapper Generation

Back to Top

Support: complex numbers

Specify whether to generate complex data and operations.

Settings

Default: on

On

Generates complex numbers and related operations.

Off

Does not generate complex data and related operations. If you clear this option, an error occurs if the code generator encounters complex data or expressions. The error message reports offending blocks and parameters.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter must be the same for top-level and referenced models.

Command-Line Information

Recommended Settings

Back to Top

Support: non-inlined S-functions

Specify whether to generate code for noninlined S-functions.

Settings

Default: Off

On

Generates code for noninlined S-functions.

Off

Does not generate code for noninlined S-functions. If this parameter is off and the model includes a noninlined S-function, an error occurs during the build process.

Tip

• Inlining S-functions is highly advantageous in production code generation, for example, for implementing device drivers. In such cases, clear this option to enforce use of inlined S-functions for code generation.

• Noninlined S-functions require additional memory and computation resources, and can result in significant performance issues. Consider using an inlined S-function when efficiency is a concern.

Dependencies

• This parameter only appears for ERT-based targets.

• Selecting this parameter also selects Support: floating-point numbers and Support: non-finite numbers. If you clear Support: floating-point numbers or Support: non-finite numbers, a warning is displayed during code generation because these parameters are required by the S-function interface.

Command-Line Information

Recommended Settings

See Also

• Automatic S-Function Wrapper Generation

• Writing S-Functions for Real-Time Workshop^® Code Generation

Back to Top

GRT compatible call interface

Specify whether to generate model function calls compatible with the main program module of the GRT target.

Settings

Default: off

On

Generates model function calls that are compatible with the main program module of the GRT target (grt_main.c or grt_main.cpp).

This option provides a quick way to use ERT target features with a GRT-based custom target that has a main program module based on grt_main.c or grt_main.cpp.

Off

Disables the GRT compatible call interface.

Tips

The following are unsupported:

• Data type replacement

• Nonvirtual subsystem option Function with separate data

Dependencies

• This parameter only appears for ERT-based targets.

• Selecting this parameter also selects the required option Support: floating-point numbers. If you subsequently clear Support: floating-point numbers, an error is displayed during code generation.

• Selecting this parameter disables the incompatible option Single output/update function. Clearing this parameter enables Single output/update function.

Command-Line Information

Recommended Settings

See Also

Support for Continuous Time Blocks, Continuous Solvers, and Stop Time

Back to Top

Single output/update function

Specify whether to generate the model_step function.

Settings

Default: on

On

Generates the model_step function for a model. This function contains the output and update function code for all blocks in the model and is called by rt_OneStep to execute processing for one clock period of the model at interrupt level.

Off

Does not combine output and update function code for model blocks in a single function. Generates the code in model.output and model.update.

Tips

Errors or unexpected behavior can occur if a Model block is part of a cycle, the Model block is a direct feedthrough block, and an algebraic loop results. See Model Blocks and Direct Feedthrough for details.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter and GRT compatible call interface are mutually incompatible and cannot both be selected through the GUI. Selecting GRT compatible call interface disables this parameter and clearing GRT compatible call interface enables this parameter.

• When you use this parameter, you must clear the option Minimize algebraic loop occurrences on the Model Referencing pane.

Command-Line Information

Recommended Settings

See Also

rt_OneStep

Back to Top

Terminate function required

Specify whether to generate the model_terminate function.

Settings

Default: on

On

Generates a model_terminate function. This function contains all model termination code and should be called as part of system shutdown.

Off

Does not generate a model.terminate function. Suppresses the generation of this function if you designed your application to run indefinitely and does not require a terminate function.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter must be the same for top-level and referenced models.

Command-Line Information

Recommended Settings

See Also

model_terminate

Back to Top

Generate reusable code

Specify whether to generate reusable, reentrant code.

Settings

Default: off

On

Generates reusable, multi-instance code that is reentrant. The code generator passes model data structures (root-level inputs and outputs, block states, parameters, and external outputs) in, by reference, as arguments to model_step and other the model entry point functions. The data structures are also exported with model.h. For efficiency, the code generator passes in only data structures that are used. Therefore, when you select this option, the argument lists generated for the entry point functions vary according to model requirements.

Off

Does not generate reusable code. Model data structures are statically allocated and accessed by model entry point functions directly in the model code.

Tips

• Entry points are exported with model.h. To call the entry-point functions from hand-written code, add an #include model.h directive to the code. If this option is selected, you must examine the generated code to determine the calling interface required for these functions.

• When this option is selected, the code generator generates a pointer to the real-time model object (model_M).

• In some cases, when this option is selected, the code generator might generate code that compiles but is not reentrant. For example, if any signal, DWork structure, or parameter data has a storage class other than Auto, global data structures are generated.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter enables Reusable code error diagnostic and Pass root-level I/O as.

• You must clear this option if you are using:

  • The static ert_main.c module, rather than generating a main program

  • The model_step function prototype control capability

  • The subsystem parameter Function with separate data

  • A subsystem that

    • Has multiple ports that share the same source

    • Has a port used by multiple instances has different sample times, data types, complexity, frame status, or dimension across the instances

    • Has output marked as a global signal

    • For each instance contains identical blocks with different names or parameter settings

• This parameter has no effect on code generated for function-call subsystems.

Command-Line Information

Recommended Settings

See Also

• Model Entry Points

• Nonvirtual Subsystem Code Generation

• Code Reuse Limitations

• Determining Why Subsystem Code Is Not Reused

• Writing S-Functions That Support Code Reuse

• Static Main Program Module

• Controlling model_step Function Prototypes

• Nonvirtual Subsystem Modular Function Code Generation

• Exporting Function-Call Subsystems

• model_step

Back to Top

Reusable code error diagnostic

Select the severity level for diagnostics displayed when a model violates requirements for generating reusable code.

Settings

Default: Error

None

Proceed with build without displaying a diagnostic message.

Warning

Proceed with build after displaying a warning message.

Error

Abort build after displaying an error message.

Under certain conditions, the Real-Time Workshop Embedded Coder software might

• Generate code that compiles but is not reentrant. For example, if signal, DWork structure, or parameter data has a storage class other than Auto, global data structures are generated.

• Be unable to generate valid and compilable code. For example, if the model contains an S-function that is not code-reuse compliant or a subsystem triggered by a wide function-call trigger, the coder generates invalid code, displays an error message, and terminates the build.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter is enabled by Generate reusable code.

Command-Line Information

Recommended Settings

See Also

• Model Entry Points

• Nonvirtual Subsystem Code Generation

• Code Reuse Limitations

• Determining Why Subsystem Code Is Not Reused

• Nonvirtual Subsystem Modular Function Code Generation

Back to Top

Pass root-level I/O as

Control how root-level model input and output are passed to the model_step function.

Settings

Default: Individual arguments

Individual arguments

Passes each root-level model input and output value to model_step as a separate argument.

Structure reference

Packs all root-level model input into a struct and passes struct to model_step as an argument. Similarly, packs root-level model output into a second struct and passes it to model_step.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter is enabled by Generate reusable code.

Command-Line Information

Recommended Settings

See Also

• Model Entry Points

• Nonvirtual Subsystem Code Generation

• Nonvirtual Subsystem Modular Function Code Generation

• model_step

Back to Top

Suppress error status in real-time model data structure

Specify whether to log or monitor error status.

Settings

Default: off

On

Omits the error status field from the generated real-time model data structure rtModel. This option reduces memory usage.

Selecting this option can cause the code generator to completely omit the rtModel data structure from generated code.

Off

Includes an error status field in the generated real-time model data structure rtModel. You can use available macros to monitor the field for or set it with error message data.

Dependencies

• This parameter only appears for ERT-based targets.

• This parameter is cleared if you select the incompatible option MAT-file logging. If you subsequently select this parameter, an error is displayed during code generation.

• Selecting this parameter clears Support: continuous time.

• Setting of this parameter for multiple integrated models must match to avoid unexpected application behavior. For example, if you select the option for one model but not in another, an error status might not get registered by the integrated application.

Command-Line Information

Recommended Settings

See Also

rtModel Accessor Macros

Back to Top

Configure Step Function

Use the Configure Step Function button to open the Model Interface dialog box. This dialog box provides a way for you to specify whether the code generator is to use a default model_step function prototype or a model-specific C prototype. Based on your selection, you can preview and modify the function prototype.

Dependency

This parameter only appears for ERT-based targets.

See Also

• Controlling model_step Function Prototypes

• model_step

• Model Interface Dialog Box

Back to Top

Create Simulink (S-Function) block

Specify whether to generate an S-function block.

Settings

Default: off

On

Generates an S-function block to represent the model or subsystem. The coder generates an inlined C or C++ MEX S-function wrapper that calls existing hand-written code or code previously generated by the Real-Time Workshop software from within the Simulink^® product. S-function wrappers provide a standard interface between the Simulink product and externally written code, allowing you to integrate your code into a model with minimal modification.

When this option is selected, the Real-Time Workshop software:

1. Generates the S-function wrapper file model_sf.c (or .cpp) and places it in the build directory.

2. Builds the MEX-file model_sf.mexext and places it in your working directory.

3. Creates and opens an untitled model containing the generated S-Function block.

Off

Does not generate an S-function block.

Dependency

This parameter only appears for ERT-based targets.

Command-Line Information

Recommended Settings

See Also

• Automatic S-Function Wrapper Generation

• Techniques for Exporting Function-Call Subsystems

• Validating ERT Production Code on the MATLAB Host Computer Using Portable Word Sizes

Back to Top

Enable portable word sizes

Specify whether to allow portability across host and target processors that support different word sizes.

Settings

Default: off

On

Generates conditional processing macros that support compilation of generated code on a processor that supports a different word size than the target processor on which production code is intended to run (for example, a 32-bit host and a 16-bit target. This allows you to use the same generated code for both software-in-the-loop (SIL) testing on the host platform and production deployment on the target platform.

Off

Does not generate portable code.

Dependencies

• This parameter only appears for ERT-based targets.

• When you use this parameter, you should:

  • Select Create Simulink (S-Function) block

  • Set Emulation hardware on the Hardware Implementation pane to None

Command-Line Information

Recommended Settings

See Also

• Validating ERT Production Code on the MATLAB Host Computer Using Portable Word Sizes

• Tips for Optimizing the Generated Code

Back to Top

MAT-file logging

Specify whether to enable MAT-file logging.

Settings

Default: off

On

Enables MAT-file logging. When you select this option, the code generator saves system states, output, and simulation time at each model execution time step. The data is written to a MAT-file, named (by default) model.mat, where model is the name of your model.

Off

Disables MAT-file logging. Clearing this option has the following benefits:

• Eliminates overhead associated with supporting a file system, which typically is not needed for embedded applications

• Eliminates extra code and memory usage required to initialize, update, and clean up logging variables

• Under certain conditions, eliminates code and storage associated with root output ports

• Omits the comparison between the current time and stop time in the model_step, allowing the generated program to run indefinitely, regardless of the stop time setting

Dependencies

• This parameter only appears for ERT-based targets and the Tornado target.

• Selecting this parameter also selects the required options Support: floating-point numbers, Support: non-finite numbers, and Terminate function required. If you subsequently clear Support: floating-point numbers, Support: non-finite numbers, or Terminate function required, an error is displayed during code generation.

• Selecting this parameter clears the incompatible option Suppress error status in real-time model data structure. If you subsequently select Suppress error status in real-time model data structure, an error is displayed during code generation.

• Selecting this parameter enables MAT-file variable name modifier.

• Clear this option if you are using exported function calls.

Command-Line Information

Recommended Settings

See Also

Using Virtualized Output Ports Optimization

Dependency

When an ERT target is selected, this parameter is enabled by MAT-file logging.