Data Configured Within Library or AUTOSAR Model

If your model is a library model or a model configured with an AUTOSAR system target file, reconfigure code generation for data. For library models, reconfigure code generation for data in the context of models that use the library (see Code Interface Configuration). For AUTOSAR models, see Map AUTOSAR Elements for Code Generation (AUTOSAR Blockset).

To avoid losing the code configuration for data configured within the model, in an earlier release, load the model and create and run a MATLAB script that:

Storage Class TypeQualifier Property

If your model configures data objects with built-in storage classes, such as ExportedGlobal and ImportedExtern, and uses the storage class TypeQualifier property, when you load the model in release R2020b or later, Simulink issues a warning. To eliminate the warning and update a model to use a supported alternative, in an earlier release, load the model and create and run a MATLAB script that:

This example script loads model data objects from the base workspace, finds instances of data configured with the storage class TypeQualifier property, and changes the storage class setting to Const.

vars = who;

  for idx = 1:length(vars)
    thisVar = evalin('base',vars{idx});
    if (isa(thisVar,'Simulink.Parameter') && (isequal(thisVar.CoderInfo.TypeQualifier, 'const')))
      thisVar.CoderInfo.TypeQualifier = '';
      thisVar.CoderInfo.StorageClass = 'Custom';
      thisVar.CoderInfo.CustomStorageClass = 'Const';
    end
  end

Starting in R2020b, to include type qualifiers in the generated code, use the Code Mappings editor or code mappings API to associate data with a storage class that specifies use of the const or volatile keyword (see Choose Storage Class for Controlling Data Representation in Generated Code). If none of the available storage classes meets your application requirements and you are using Embedded Coder^®, define a new storage class by using the Embedded Coder Dictionary (see Define Service Interfaces, Storage Classes, Memory Sections, and Function Templates for Software Architecture). Then, map the model data to the new storage class.

Data Alignment for Code Generation

To preserve data alignment information configured for a model, represent data with data objects outside of the model. For example, open the model in a previous release of Simulink and perform the actions listed in this table.

Alternatively, create and run a MATLAB script that:

For example, this script checks whether Alignment is set for parameter, lookup table, and breakpoint data objects and captures the data objects found in MAT-file savedData.mat.

filename = 'savedData.mat';
varList = who;
tosaveVars = {};
for idx = 1 : length(varList)
   variable = eval(varList{idx});
   if ((isa(variable, 'Simulink.Parameter') || ...
       isa(variable, 'Simulink.LookupTable') || ...
       isa(variable, 'Simulink.Breakpoint')) && ...
       variable.CoderInfo.Alignment ~= -1)
       tosaveVars{end+1} = varList{idx};       
   end
end
if ~isempty(tosaveVars)
  save('savedData.mat', tosaveVars{:});
end

Evaluate the script in the model workspace with these commands:

mws = get_param(bdroot, 'ModelWorkspace');
evalin(mws, 'SaveMWSParamsWithAlignment');

For parameter objects in the model workspace, alternatively, you can use the Model Explorer interface to move the objects from the model workspace to the base workspace or a data dictionary. Then, select the Alignment property for the storage class.

For more information, see Optimize Performance of Memory Access by Using Data Alignment.

Code Configuration for Parameter Objects Initialized in Model Workspace

After loading a model in release R2020b or later and initializing the model workspace for the model from an external data source, such as a MAT-file, MATLAB file, or data dictionary, Simulink:

Use the Code Mappings editor or the code mappings API to get and set parameter code configuration settings. See Code Interface Configuration.

Code Configuration for Subsystem I/O Interface

In release R2020b or later, for individual subsystems from which you generate code and executable programs by right-clicking the Subsystem block, to include signal data in the generated subsystem code interface, configure the storage class and storage class properties for the subsystem input and output signals within the subsystem. If you configure the signals outside of the subsystem, the generated code does not include variables for the input and output interface data.

For more information, see Generate Code and Executables for Individual Subsystems.