Model configuration for code generation in Simulink - Step-by-Step Execution

Concept Flow - Model configuration for code generation

Open Simulink Model

↓

Access Configuration Parameters

↓

Select Code Generation Tab

↓

Set System Target File

↓

Configure Code Generation Options

↓

Apply and Save Settings

↓

Generate Code

↓

Review Generated Code

This flow shows the steps to configure a Simulink model for code generation, from opening the model to reviewing the generated code.

Execution Sample

Simulink

open_system('myModel')
set_param('myModel','SystemTargetFile','ert.tlc')
set_param('myModel','GenerateReport','on')
rtwbuild('myModel')

This code opens a Simulink model, sets the system target file for Embedded Coder, enables report generation, and builds the model to generate code.

Execution Table

Step	Action	Parameter/Setting	Value	Result
1	Open model	Model name	'myModel'	Model 'myModel' opened
2	Set system target file	SystemTargetFile	'ert.tlc'	Code generation target set to Embedded Coder
3	Enable report generation	GenerateReport	'on'	Code generation report enabled
4	Build model	Command	rtwbuild('myModel')	Code generated successfully
5	Exit	Build status	Success	Code generation process completed

💡 Code generation completed successfully after applying configuration settings and building the model

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
ModelName	''	'myModel'	'myModel'	'myModel'	'myModel'	'myModel'
SystemTargetFile	''	''	'ert.tlc'	'ert.tlc'	'ert.tlc'	'ert.tlc'
GenerateReport	'off'	'off'	'off'	'on'	'on'	'on'
BuildStatus	''	''	''	''	'Success'	'Success'

Key Moments - 3 Insights

Why do we need to set the 'SystemTargetFile' parameter before generating code?

Setting 'SystemTargetFile' tells Simulink which code generation target to use, such as Embedded Coder ('ert.tlc'). Without this, code generation may not produce the desired output. See execution_table step 2.

What happens if 'GenerateReport' is not enabled?

If 'GenerateReport' is off, Simulink will generate code but will not create a detailed report explaining the code generation process. This is shown in execution_table step 3 where enabling it turns on report generation.

How do we know if code generation was successful?

The 'BuildStatus' variable changes to 'Success' after running rtwbuild, as shown in execution_table step 4 and 5, indicating code was generated without errors.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what value is assigned to 'SystemTargetFile'?

A 'grt.tlc'

B 'none'

C 'ert.tlc'

D 'slrt.tlc'

💡 Hint

Check the 'Value' column in execution_table row with Step 2.

At which step does the 'GenerateReport' parameter change from 'off' to 'on' according to variable_tracker?

A After Step 3

B After Step 2

C After Step 1

D After Step 4

💡 Hint

Look at the 'GenerateReport' row in variable_tracker and see when it changes.

If we skip setting 'SystemTargetFile', what is the likely outcome when running rtwbuild?

A Code generation will succeed with default settings

B Code generation will fail or produce incorrect code

C A report will be generated automatically

D Model will not open

💡 Hint

Refer to key_moments about importance of 'SystemTargetFile' setting.

Concept Snapshot

Model configuration for code generation in Simulink:
- Open model with open_system('modelName')
- Set 'SystemTargetFile' to specify code type (e.g., 'ert.tlc')
- Enable 'GenerateReport' to get code generation details
- Use rtwbuild('modelName') to generate code
- Check build status for success or errors

Full Transcript

This visual execution guide shows how to configure a Simulink model for code generation. First, the model is opened using open_system. Then, the system target file is set to 'ert.tlc' to specify Embedded Coder as the code generation target. Next, report generation is enabled by setting 'GenerateReport' to 'on'. The model is then built using rtwbuild, which generates the code. The build status is checked to confirm success. Variables like ModelName, SystemTargetFile, GenerateReport, and BuildStatus change step-by-step as shown in the variable tracker. Key moments clarify why setting the system target file and enabling reports matter. The quiz tests understanding of these steps and their effects.