Data and Function Interfaces

Map model data elements and functions to code definitions

To comply with code standards and guidelines and configure the representation of model data elements and entry-point functions for code generation, map model data elements and functions to predefined code definitions.

For an introduction, see C Code Generation Configuration for Model Interface Elements.

Tools

Code Mappings Editor

Associate model elements with code interface definitions

Objects

coder.mapping.api.CodeMapping Model data and function interface configuration for C code generation

Functions

expand all

Generated Entry Points

`model_initialize`	Generated C/C++ entry-point function that contains initialization code for a Simulink model
`model_reset`	Generated C/C++ entry-point function that contains reset code for a Simulink model
`model_step`	Generated C/C++ entry-point function that contains execution code for each step in a Simulink model
`model_terminate`	Generated C/C++ entry-point function that contains termination code for a Simulink model

Model Element Configuration for C Code Generation

Create and Find Code Mappings

`coder.mapping.api.get`	Get code mappings for model
`coder.mapping.utils.create`	Create code mappings object for configuring data and function interface for C and C++ code generation
`find`	Get model elements for the category of model code mappings

Default Configurations

`getDataDefault`	Get default storage class or storage class property setting for model data category
`setDataDefault`	Set default storage class and storage class property values for model data category

Root-Level Inport and Outport Configuration

`getInport`	Get code and calibration configuration from code mappings for root-level inport
`getOutport`	Get code and calibration configuration from code mappings for root-level outport
`setInport`	Configure root-level inports for code and calibration file (a2l) generation
`setOutport`	Configure root-level outport for code and calibration file (a2l) generation

Parameter Configuration

`getModelParameter`	Get code and calibration configuration from code mappings for model parameters
`setModelParameter`	Configure model parameter for code and calibration file (a2l) generation

Signal, State, and Data Store Configuration

`addSignal`	Add block output signal to model code mappings
`getDataStore`	Get code and calibration configuration from code mappings for local or shared local data store
`getSignal`	Get code and calibration configuration from code mappings for block output signal
`getState`	Get code and calibration configuration from code mappings for block state
`removeSignal`	Remove block output signal from model code mappings
`setDataStore`	Configure local or shared local data store for code and calibration file (a2l) generation
`setSignal`	Configure block signal data for code and calibration file (a2l) generation
`setState`	Configure block states for code and calibration file (a2l) generation

Topics

Configuration Fundamentals

C Code Generation Configuration for Model Interface Elements
Control the representation of model data elements and functions in generated C code.
Generate C++ Class Interface to Model or Subsystem Code
Generate a C++ class interface to code generated from a model or subsystem.
Code Definition and Mapping Limitations and Considerations
Restrictions, constraints, and considerations that apply to code definitions and code mappings.
Manage Multiple Code Mappings for a Model
Design models that are platform-neutral and ready to deploy to different run-time environments.
How Generated Code Exchanges Data with an Environment
The generated code exchanges signal, state, and parameter data with the calling environment through a data interface.
Migration of Model Data Configurations to Code Mappings
How Simulink^® migrates code definitions for models created before release R2020b to code mappings and related information to consider.

Data Configuration

Choose Data Configuration Approach
Make decisions about the design data used by your model based on your code generation requirements.
Configure Root-Level Inport Blocks for C Code Generation
Set the storage class and other relevant code generation properties for root-level Inport blocks.
Configure Root-Level Outport Blocks for C Code Generation
Set the storage class and other relevant code generation properties for root-level Outport blocks.
Configure Signal Data for C Code Generation
Set the storage class and other relevant code generation properties for signal data.
Configure Parameters for C Code Generation
Set the storage class and other relevant code generation properties for parameters.
Configure Block States for C Code Generation
Set the storage class and other relevant code generation properties for block states.
Configure Data Stores for C Code Generation
Set the storage class and other relevant code generation properties for data stores.
Choose Storage Class for Controlling Data Representation in Generated Code
Choose a storage class to apply to data elements in a model, such as signals, states, and block parameters.
Design Data Interface by Configuring Inport and Outport Blocks
Customize the data interface of a model to enable integration of the generated code with your own code and to improve code traceability and readability.

Function Configuration

Configure Generated C Function Interface for Model Entry-Point Functions
Learn about generated C entry-point functions, configuration options, and how to interface with them.
Control Data and Function Interface in Generated Code
Control how generated code exchanges data with a calling environment.
Rapid Prototyping Model Functions
Generate rapid prototyping code.

Data Access and Initialization

Create Tunable Calibration Parameter in the Generated Code
In the generated code, create tunable parameter data that you can access during rapid prototyping and calibration.
Reuse Parameter Data in Different Data Type Contexts
Reuse parameter data by creating a Simulink.Parameter object or numeric MATLAB^® variable that you can use in different data type contexts.
Limitations for Block Parameter Tunability in Generated Code
Limitations can prevent a block parameter from appearing in the generated code as tunable, which means you cannot interact with the parameter value after compiling the code.
Access Signal, State, and Parameter Data During Execution
As you iteratively develop a model, capture output signal and state data that model execution generates. Tune parameter values during execution to observe results on the outputs.
Switch Between Sets of Parameter Values During Simulation and Code Execution
Switch between independent sets of values for the same block parameters by storing the sets in an array of structures.
Preserve Variables in Generated Code
As you iteratively develop a model, you can tune block parameter values during simulation or execution of generated code to observe the results on signal and state values.
Configure Packaging of Parameter Arguments in Generated Code
Customize the implementation of parameter arguments in generated code.
Control Signal and State Initialization in the Generated Code
Generate code that enables you to store tunable initial conditions in memory, for example, for modeling a system that shuts down and restarts.
Initialization of Signal, State, and Parameter Data in the Generated Code
To match the numerics of a simulation in Simulink, the generated code assigns initial values to global data, especially for block states and parameters.

Featured Examples

Configure Model Data Interface for C Code Generation

Configure data elements in a model, such as block parameters and signal lines, so that corresponding variables appear in generated code.

Open Live Script

Generate Reentrant, Multi-Instance Code

Configure a model for reentrant, multi-instance code generation. Multiple programs can use reentrant code simultaneously. When you configure a model for reentrancy, the execution (step) entry-point function uses root-level input and output arguments instead of global data structures. After examining the configuration settings, generate and review the generated code.

Open Script