Compare System Target File Support Across Products - MATLAB & Simulink (original) (raw)

When you select a system target file (such as grt.tlc), the selection defines the run-time environment and the code generation features. Identify the system target file features that match your code generation workflow goals.

The code generator uses the system target file to produce code intended for execution on certain target hardware or on a certain operating system. The system target file invokes other run-time environment-specific files. For more information on configuring model code generation parameters for target hardware, see Configure Run-Time Environment Options.

Different types of system target files support a selection of generated code features. In the system target file, the value of the CodeFormat TLC variable and corresponding rtwgensettings.DerivedFrom field value identify the system target file type and generated code features. These selections apply your code generation control decisions at several points in the code generation process. Your selections include whether and how the model build generates:

• Certain data structures (for example, SimStruct orrtModel)
• Static or dynamic memory allocation code
• Calling interface for generated model functions

For custom system target file development, the CodeFormat value differs among code generation targets:

• If the system target file does not include a value for theCodeFormat TLC variable, the default value isRealTime for generic real-time target (GRT). The correspondingrtwgensettings.DerivedFrom field value is grt.tlc (default value).
• If you are developing a custom system target file and you have Embedded Coder software, consider setting the CodeFormat TLC variable value toEmbedded-C for embedded real-time target (ERT). The correspondingrtwgensettings.DerivedFrom field value is ert.tlc. The ERT system target file supports more generated code features than the GRT system target file.

This example shows how the value for the CodeFormat TLC variable and corresponding rtwgensettings.DerivedFrom field value are set inert.tlc.

%assign CodeFormat = "Embedded-C"

/% BEGIN_RTW_OPTIONS rtwgensettings.DerivedFrom = 'ert.tlc'; END_RTW_OPTIONS %/

Note

Use the value for the CodeFormat TLC variable with its correspondingrtwgensettings.DerivedFrom field value to generate code for the model. If you do not select a value explicitly, the default values apply. For thertwgensettings.DerivedFrom field, use 'ert.tlc' or'grt.tlc'. For more information, see System Target File Structure.

For a description of the optimized call interface generated by default for the GRT and ERT system target files, see Configure Generated C Function Interface for Model Entry-Point Functions.

Code generation with the GRT and ERT system target files uses the real-time model data structure (rtModel). This structure encapsulates model-specific information in a much more compact form than the simulation structure, SimStruct. Many efficient features of generated code depend on generation of rtModel rather than SimStruct, including:

• Integer absolute and elapsed timing services
• Independent timers for asynchronous tasks
• Generation of improved C API code for signal, state, and parameter monitoring
• Pruning the data structure to minimize its size (ERT-derived system target files only)

For a description of the rtModeldata structure, see Real-Time Model Data Structure.

Compare Product System Target Files

You can select from a range of system target files by using the System Target File Browser. This selection lets you experiment with configuration options and save your model with different configurations.

You cannot build or generate code for non-GRT system target files, unless you have the required software on your system. For example, you require Embedded Coder® for ERT system target files, Simulink® Desktop Real-Time™ for SLDRT system target files, and so on.

Selecting a system target file for your model selects either the toolchain approach or the template makefile approach for build process control. For more information about these approaches, see Approaches for Building Code Generated from Simulink Models.

System Target Files Available from System Target File Browser

Note

To create and build a Visual C++ Solution (.sln) file with Debug configuration, in theToolchain field, specify a CMake toolchain, for example, Microsoft Visual Studio Project 2019 | CMake (64-bit Windows) or Microsoft Visual Studio Project 2017 | CMake (64-bit Windows). For more information about CMake toolchains, see Configure CMake Build Process.

Compare Code Styles and STF Support

The code generator produces two styles of code. One code style is suitable for rapid prototyping (and simulation by using code generation). The other style is suitable for embedded applications. This table maps system target files to corresponding code styles.

Code Styles Listed by System Target File

Third-party vendors supply additional system target files to support code generation for their products. For more information about third-party products, see the vendor website or the MathWorks® Connections program web page: https://www.mathworks.com/products/connections.

Compare Generated Code Features by Product

The code generation process for real-time system target files (such as GRT) provides many embedded code optimizations. Selecting an ERT-based system target file offers more extensive features than GRT. The system target file selection determines the available features for the code generation product. As you select the code generation target that matches your development process, use this table to compare code generation features available with Simulink Coder and features available with Embedded Coder.

Compare Code Generation Features for Simulink Coder Versus Embedded Coder

Compare Generated Code Features by STF

The code generator supports a selection of generated code features for different types of system target files. In each system target file, the value of theCodeFormat TLC variable identifies the set of features.

This table summarizes how different system target files support applications.

This table summarizes the various options available for each System target file selection, with the exceptions noted.

Features Supported in Code Generated for System Target Files (STF)

| | System Target Files (STF)1 | | | | | | | | | | ---------------------------------------------- | ------- | ------- | --------------- | ----------- | -------- | --------- | ------------- | ----- | | Feature | grt.tlc | ert.tlc | ert_shrlib.tlc | rtwsfcn.tlc | rsim.tlc | sldrt.tlc | speedgoat.tlc | Other | | Static memory allocation | X | X | | X | X | X | | | | Dynamic memory allocation | X4, 5 | X4, 5 | X | X | X | | | | | Continuous time | X | X | X | X | X | X | | | | C/C++ MEX S-functions (noninlined) | X | X | X | X | X | X | | | | S-function (inlined) | X | X | X | X | X | X | X | | | Minimize RAM/ROM usage | X | X2 | X | | | | | | | Supports external mode | X | X | X | X | X | | | | | Rapid prototyping | X | X | X | X | | | | | | Production code | X | X2 | X3 | | | | | | | Batch parameter tuning and Monte Carlo methods | X | X | | | | | | | | System-level Simulator | X | | | | | | | | | Executes in hard real time | X3 | X3 | X | X | X5 | | | | | Non-real-time executable included | X | X | X | | | | | | | Multiple instances of model | X4, 5 | X4, 5 | X4 | X4, 5 | X4, 5 | | | | | Supports variable-step solvers | X | X | | | | | | | | Supports SIL/PIL6 | X | X | X | | | | | |

Notes

1. System Target Files:
   • grt.tlc — Generic real-time target
   • ert.tlc — Embedded real-time target
   • ert_shrlib.tlc — Embedded real-time target shared library
   • rtwsfcn.tlc (To be removed) — S-function target
   • rsim.tlc — Rapid simulation target
   • sldrt.tlc — Simulink Desktop Real-Time target
   • speedgoat.tlc — Simulink Real-Time target
   • Other — The Simulink Coder embedded real-time capabilities support other system target files
2. Does not apply to GRT-based system target files. Applies to only ERT-based system target files.
3. The default GRT and ERT rt_main files emulate execution of hard real time. When explicitly connected to a real-time clock, they execute in hard real time.
4. You can generate code for multiple instances of a Stateflow chart or subsystem containing a chart, except when the chart contains exported graphical functions.
5. In the Configuration Parameters dialog box, for the Code interface packaging field, select Reusable function.
6. Requires an Embedded Coder license.

See Also

Topics

• Configure a System Target File
• Configure STF-Related Code Generation Parameters
• Choose a Code Replacement Library
• Configure Language Standard for Target System