Embedded Coder for MCU deployment in Simulink - Step-by-Step Execution

Concept Flow - Embedded Coder for MCU deployment

Model Design in Simulink

↓

Configure Embedded Coder Settings

↓

Generate C Code Automatically

↓

Build Code for MCU Target

↓

Deploy Code to MCU Hardware

↓

Run and Test on MCU

↓

Collect Data and Analyze Results

This flow shows how a Simulink model is designed, configured for Embedded Coder, code is generated, built, deployed to MCU, and tested with data collected for analysis.

Execution Sample

Simulink

model = 'simple_mcu_model';
load_system(model);
set_param(model, 'SystemTargetFile', 'ert.tlc');
rtwbuild(model);
deployToMCU();

This code loads a Simulink model, sets it to use Embedded Coder for MCU, builds the code, and deploys it to the MCU.

Execution Table

Step	Action	Parameter/Value	Result/Output
1	Load Simulink model	model = 'simple_mcu_model'	Model loaded into memory
2	Set target for Embedded Coder	SystemTargetFile = 'ert.tlc'	Model configured for MCU code generation
3	Build model	rtwbuild(model)	C code generated and compiled for MCU
4	Deploy code	deployToMCU()	Code flashed to MCU hardware
5	Run on MCU	Start MCU execution	MCU runs generated code
6	Collect data	Read MCU output	Data available for analysis
7	End	All steps completed	Deployment and testing finished

💡 Process ends after code runs on MCU and data is collected for analysis

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
model	''	'simple_mcu_model'	'simple_mcu_model'	'simple_mcu_model'	'simple_mcu_model'	'simple_mcu_model'	'simple_mcu_model'
SystemTargetFile	''	''	'ert.tlc'	'ert.tlc'	'ert.tlc'	'ert.tlc'	'ert.tlc'
code_generated	False	False	False	True	True	True	True
code_deployed	False	False	False	False	True	True	True
mcu_running	False	False	False	False	False	True	True
data_collected	False	False	False	False	False	False	True

Key Moments - 3 Insights

Why do we set 'SystemTargetFile' to 'ert.tlc' before building?

Setting 'SystemTargetFile' to 'ert.tlc' tells Simulink to use Embedded Coder for generating optimized C code for MCUs, as shown in step 2 of the execution table.

What happens if we try to deploy code before building it?

The code must be generated and compiled first (step 3) before deployment; deploying before building means no code exists to flash, so deployment (step 4) would fail.

How do we know the MCU is running the deployed code?

After deployment (step 4), starting the MCU execution (step 5) confirms the code runs; variable 'mcu_running' changes from False to True in the variable tracker.

Visual Quiz - 3 Questions

Look at the execution table, what is the result after step 3?

A Model loaded into memory

B Code flashed to MCU hardware

C C code generated and compiled for MCU

D Data available for analysis

💡 Hint

Check the 'Result/Output' column for step 3 in the execution table

At which step does the code get deployed to the MCU?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look for the action 'Deploy code' in the execution table

If 'code_generated' is False after step 3, what would happen next?

A Deployment would fail because no code exists

B MCU would run the code

C Deployment would succeed

D Data would be collected successfully

💡 Hint

Refer to the variable_tracker for 'code_generated' status and deployment step in execution_table

Concept Snapshot

Embedded Coder for MCU deployment:
- Design model in Simulink
- Set 'SystemTargetFile' to 'ert.tlc'
- Build model to generate MCU C code
- Deploy code to MCU hardware
- Run and collect data for analysis

Full Transcript

This visual execution trace shows how to deploy a Simulink model to a microcontroller unit (MCU) using Embedded Coder. First, the model is loaded into Simulink. Then, the target is set to Embedded Coder by assigning 'ert.tlc' to the SystemTargetFile parameter. Next, the model is built, which generates and compiles C code optimized for the MCU. After building, the code is deployed to the MCU hardware by flashing it. The MCU then runs the deployed code, and output data is collected for analysis. Variables like 'code_generated' and 'code_deployed' track progress through these steps. Key moments include understanding why setting the target is necessary before building, the importance of building before deployment, and confirming the MCU runs the code after deployment. The quiz questions reinforce understanding of these steps by referencing the execution table and variable states.