Documentation

To set the minimum signal or parameter width for generating a for loop, set configuration parameter Loop unrolling threshold to 2 or greater.

Loop unrolling threshold specifies the array size at which the code generator begins to use a for loop, instead of separate assignment statements, to assign values to the elements of a signal or parameter array. The default value is 5.

Loop unrolling threshold (Simulink Coder) in the Simulink^® documentation

To support complete definition of data and initialize internal and external data to zero, clear these configuration parameters:

Explicitly initialize all variables. If the run-time environment of the target system provides mechanisms to initialize all I/O and state variables, consider using the initialization of the target as an alternative to the suggested settings.

These configuration parameters are applicable only when the System target file is an ERT-based target.

Information about the following parameters in the Simulink documentation:

To support verifiable code, select configuration parameter Remove code from floating-point to integer conversions that wraps out-of-range values

Avoid overflows as opposed to handling them with wrapper code.

For blocks whose Saturate on integer overflow configuration parameter is cleared, deselecting Remove code from floating-point to integer conversions that wraps out-of-range values can add code that wraps out of range values, resulting in unreachable code that cannot be tested.

To support the robustness of the operations, clear configuration parameter Remove code that protects against division arithmetic exceptions.

Avoid division-by-zero exceptions. If you clear Remove code that protects against division arithmetic exceptions, the code generator produces code that guards against division by zero for fixed-point data.

This configuration parameter is applicable only when the System target file is an ERT-based target.

In the Configuration Parameters dialog box, on the Code Generation > Comments pane, select these parameters:

Include comments.

Simulink block comments.

Show eliminated blocks.

Verbose comments for 'Model default' storage class.

Requirements in block comments.

Including comments provides good traceability between the code and the model.

Including comments that describe the code for blocks provides good traceability between the code and the model.

Including comments that describe the code for blocks eliminated from a model provides good traceability between the code and the model.

Including the names of parameter variables and source blocks as comments in the model parameter structure declaration in model_prm.h provides good traceability between the code and the model.

Including requirement descriptions assigned to Simulink blocks as comments provides good traceability between the code and the model.

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Code Generation > Interface pane, set the Software environment, Code interface, and Data exchange interface parameters as follows:

Clear Support: non-finite numbers.

Clear Support: absolute time.

Clear Support: continuous time.

Clear Support: non-inlined S-functions.

Clear Classic call interface.

Select Single output / update function.

Clear Terminate function required.

Select Remove error status field in real-time model data structure.

Clear MAT-file logging.

Support for non-finite numbers is not recommended for real-time safety-related systems.

Support for absolute time is not recommended for real-time safety-related systems.

Support for continuous time is not recommended for real-time safety-related systems.

Support for non-inlined S-functions requires support of non-finite numbers, which is not recommended for real-time safety-related systems.

To eliminate model function calls compatible with the main program module of the pre-2012a GRT target that is not recommended for real-time safety-related systems; use an ERT based target instead.

To simplify the interface to the real-time operating system (RTOS) and simplify verification of the generated code by creating a single call to both the output and update functions.

To eliminate model_terminate function, which is not recommended for real-time safety-related systems.

To eliminate extra code for logging and monitoring error status that might not be reachable for testing.

To eliminate extra code for logging test points to a MAT file that is not supported by embedded targets.

In the Configuration Parameters dialog box, on the Code Generation > Code Style pane, set these parameters:

Set Parentheses level (Embedded Coder) to Maximum (Specify precedence with parentheses).

Select Preserve operand order in expression (Embedded Coder).

To prevent unexpected results.

To improve traceability of the generated code.

Decrease the effort to perform code review.