{"id":14537,"date":"2023-06-01T14:43:19","date_gmt":"2023-06-01T18:43:19","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=14537"},"modified":"2023-06-08T12:51:00","modified_gmt":"2023-06-08T16:51:00","slug":"customizing-the-code-generated-from-simulink","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2023\/06\/01\/customizing-the-code-generated-from-simulink\/","title":{"rendered":"Customizing the Code Generated from Simulink"},"content":{"rendered":"
I want to start by giving you a heads up that guest blogger <\/span>Erin McGarrity<\/span><\/a> will be coming back soon with more posts about <\/span>Simulink Coder<\/span><\/a> and <\/span>Embedded Coder<\/span><\/a>. Before going deeper into code generation topics, I thought it would be a good idea to re-visit the basics of customizing the code generated from Simulink models using Embedded Coder.<\/span><\/div>
It has been almost 10 years since the last time I wrote a <\/span>basic introduction to code generation<\/span><\/a> on this blog. As you can imagine, things have changed a lot since then, so this week I am sharing the 2023 version of a basic introduction to Embedded Coder.<\/span><\/div>

Default Behavior<\/span><\/h2>
Let's take this simple example model and generate code for it using Embedded Coder<\/span><\/div>
\"\"<\/img><\/div>
By default, the \"step\" function for this model looks like this:<\/span><\/div>
\"\"<\/img><\/div>
While this code is valid, there are multiple reasons for wanting to customize it. <\/span><\/div>
For this example, I will make the generated code look more like what a human would write, using simple variables like <\/span>u<\/span> and <\/span>y<\/span> instead of grouping them in the structure <\/span>modelname_Y.<\/span><\/div>

Customizing Code using Simulink.Parameter and Simulink.Signal Objects<\/span><\/h2>
If I don't want the variables being stored in those <\/span>modelname_Y<\/span>, <\/span>modelname_P<\/span> and <\/span>modelname_DW<\/span> structures, the \"classic\" approach is to define <\/span>Simulink.Signal<\/span><\/a> and <\/span>Simulink.Parameter<\/span><\/a> objects for the different modeling elements and specify a different storage class:<\/span><\/div>
% Input signal<\/span><\/span><\/div><\/div>
u = Simulink.Signal;<\/span><\/span><\/div><\/div>
u.CoderInfo.StorageClass = <\/span>'ExportedGlobal'<\/span>;<\/span><\/span><\/div><\/div>
% Output Signal<\/span><\/span><\/div><\/div>
y = Simulink.Signal;<\/span><\/span><\/div><\/div>
y.CoderInfo.StorageClass = <\/span>'ExportedGlobal'<\/span>;<\/span><\/span><\/div><\/div>
% Unit Delay State<\/span><\/span><\/div><\/div>
x = Simulink.Signal;<\/span><\/span><\/div><\/div>
x.CoderInfo.StorageClass = <\/span>'ExportedGlobal'<\/span>;<\/span><\/span><\/div><\/div>
%Gain A<\/span><\/span><\/div><\/div>
a = Simulink.Parameter;<\/span><\/span><\/div><\/div>
a.CoderInfo.StorageClass = <\/span>'ExportedGlobal'<\/span>;<\/span><\/span><\/div><\/div>
a.Value = 0.1;<\/span><\/span><\/div><\/div>
%Gain B<\/span><\/span><\/div><\/div>
b = Simulink.Parameter;<\/span><\/span><\/div><\/div>
b.CoderInfo.StorageClass = <\/span>'ExportedGlobal'<\/span>;<\/span><\/span><\/div><\/div>
b.Value = 0.9;<\/span><\/span><\/div><\/div><\/div>
In the model, I associate those objects with signals and block properties:<\/span><\/div>
\"\"<\/img><\/div>
And the generated code now looks like this:<\/span><\/div>
\"\"<\/img><\/div>

Customizing Code using Code Mapping<\/span><\/h2>
A few years ago, we introduced the <\/span>Code Mapping<\/span><\/a> panel to give you a central location where you can configure how the different modeling elements in a Simulink model map to C code.<\/span><\/div>
To get started, you first launch the <\/span>Embedded Coder App<\/span><\/a>. This can be done from the Apps Gallery in the Simulink toolstrip, or using the keyboard shortcut <\/span>Ctrl+Shift+C<\/span>. As I described in a <\/span>previous post<\/span><\/a>, my favorite way to launch this kind of app is hitting <\/span>Ctrl+.<\/span> to launch the Actions search and type what I need:<\/span><\/div>
\"\"<\/img><\/div>
In the C Code tab, the Code Interface dropdown contains the Code Mapping related entries: <\/span><\/div>
\"\"<\/img><\/div>
The first thing I can try is changing the default storage class and see if I can get what I want. I set the Inports, Outports, States and External Parameters default storage class to <\/span>ExportedGlobal<\/span>:<\/span><\/div>
\"\"<\/img><\/div>
and now the code I get is:<\/span><\/div>
\"\"<\/img><\/div>
The data is not stored in structures anymore and the parameters are showing up as <\/span>a<\/span> and <\/span>b<\/span>, but I still need to do an additional step for the signals and states. <\/span><\/div>
Code Mapping works well teamed up with the <\/span>Property Inspector<\/span><\/a>. For Inputs, Outputs, Signals and States, Property Inspector allows me to specify the identifier I want.<\/span><\/div>
\"\"<\/img><\/div>
Once the identifiers have been specified for ports and states, I can generate code and confirm that it behaves as I expect:<\/span><\/div>
\"\"<\/img><\/div>
Note that those two techniques (parameter\/signal objects and Code Mapping) are not mutually exclusive. It is possible to specify code generation properties using signal and parameter objects on top of Code Mapping. This is useful if you want a finer granularity in your specification and\/or if you prefer to keep those specifications outside of the model file.<\/span><\/div>

Now it's your turn<\/span><\/h2>
I recommend visiting the <\/span>Code Mapping<\/span><\/a> documentation to read more on this topic.<\/span><\/div>
After reading this basic introduction, which other code generation topics would you like to see in future posts? Let us know in the comments below.<\/span><\/div>\r\n<\/div>