Generated C code inspection in Simulink - Step-by-Step Execution

Concept Flow - Generated C code inspection

Simulink Model

↓

Code Generation

↓

Generated C Code

↓

Code Inspection

↓

Identify Variables, Functions, Logic

↓

Trace Execution Step-by-Step

↓

Understand Behavior and Outputs

Start from a Simulink model, generate C code, then inspect the code step-by-step to understand variables, functions, and logic.

Execution Sample

Simulink

void step() {
  y = a * x + b;
}

A simple generated C function computing output y from inputs a, x, and b.

Execution Table

Step	Variable	Value Before	Operation	Value After	Comment
1	a	2	Read input	2	Input parameter a
2	x	3	Read input	3	Input variable x
3	b	1	Read input	1	Input parameter b
4	y	undefined	Compute y = a * x + b	7	Calculate output y
5	Return	N/A	End of step function	N/A	Output y ready

💡 Step function completes after computing y.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
a	2	2	2	2	2	2
x	3	3	3	3	3	3
b	1	1	1	1	1	1
y	undefined	undefined	undefined	undefined	7	7

Key Moments - 2 Insights

Why does variable y have 'undefined' before step 4?

Because y is computed only at step 4, before that it has no assigned value as shown in execution_table row 4.

How do we know the inputs a, x, and b are read correctly?

Execution_table rows 1-3 show inputs a, x, and b are read with their initial values before computation.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of y after step 4?

A 6

B 7

C undefined

D 1

💡 Hint

Check the 'Value After' column for y at step 4 in execution_table.

At which step are the inputs a, x, and b read?

A Steps 1 to 3

B Step 4

C Step 5

D Before step 1

💡 Hint

Look at execution_table rows 1 to 3 for input reading.

If input b changed to 2, what would be the new value of y after step 4?

A 6

B 7

C 8

D 5

💡 Hint

Use the formula y = a * x + b with a=2, x=3, b=2 from variable_tracker.

Concept Snapshot

Generated C code inspection:
- Start from Simulink model
- Generate C code
- Identify variables and functions
- Trace step-by-step execution
- Understand how inputs produce outputs
- Confirm logic matches model behavior

Full Transcript

This visual execution shows how generated C code from a Simulink model is inspected step-by-step. We start with inputs a=2, x=3, b=1. The code reads these inputs, then computes y = a * x + b, resulting in y=7. Variables a, x, and b remain constant, while y changes from undefined to 7 after computation. Key moments clarify why y is undefined before calculation and confirm input reading steps. The quiz tests understanding of variable values at each step and how changing inputs affects outputs.

Practice

1. What is the main purpose of inspecting generated C code from a Simulink model?

easy

A. To run the Simulink model faster in simulation

B. To create new Simulink blocks automatically

C. To verify the correctness and understand the behavior of the generated code

D. To convert C code back into Simulink diagrams

Solution

1. Step 1: Understand the role of generated code inspection

   Generated C code inspection is used to check if the code matches the Simulink model's logic and to understand how the model is translated into code.

2. Step 2: Eliminate unrelated options

   Creating new blocks, speeding simulation, or converting code back to diagrams are not purposes of code inspection.

3. Final Answer:

   To verify the correctness and understand the behavior of the generated code -> Option C

4. Quick Check:

   Code inspection = verify and understand code [OK]

Hint: Code inspection checks correctness and logic match [OK]

Common Mistakes:

• Thinking code inspection creates new blocks
• Confusing code inspection with simulation speedup
• Assuming code inspection converts code back to diagrams

2. Which Simulink tool is primarily used to generate C code from a model?

easy

A. Simulink Profiler

B. Simulink Data Inspector

C. Simulink Real-Time

D. Simulink Coder

Solution

1. Step 1: Identify the tool for code generation

   Simulink Coder is the tool designed to generate C and C++ code from Simulink models.

2. Step 2: Confirm other tools' purposes

   Profiler measures performance, Data Inspector visualizes signals, Real-Time runs models on hardware, none generate code.

3. Final Answer:

   Simulink Coder -> Option D

4. Quick Check:

   Code generation tool = Simulink Coder [OK]

Hint: Simulink Coder generates C code from models [OK]

Common Mistakes:

• Confusing Profiler with code generator
• Mixing Data Inspector with code generation
• Assuming Real-Time generates code

3. Given the following snippet from generated C code, what does the variable rtU.inputSignal represent?

/* Model step function */
void model_step(void) {
  real_T output = rtU.inputSignal * 2.0;
  rtY.outputSignal = output;
}

medium

A. An output signal from the model

B. An input signal to the model

C. A local temporary variable

D. A constant value defined in the code

Solution

1. Step 1: Analyze variable naming conventions

   In generated code, rtU prefix usually denotes inputs to the model, so rtU.inputSignal is an input.

2. Step 2: Check usage in code

   The code multiplies rtU.inputSignal by 2 and assigns to output, confirming it is an input value.

3. Final Answer:

   An input signal to the model -> Option B

4. Quick Check:

   rtU = inputs, rtY = outputs [OK]

Hint: rtU prefix means input signals in generated code [OK]

Common Mistakes:

• Thinking rtU is output or local variable
• Assuming inputSignal is a constant
• Confusing variable scope

4. You find this line in generated C code:

int32_T counter = 0
counter += 1;

What is the error here?

medium

A. Missing semicolon after the first statement

B. Incorrect variable type for counter

C. counter cannot be incremented like this

D. Variable counter should be declared as float

Solution

1. Step 1: Check syntax of variable declaration

   The first line declares counter but misses a semicolon at the end, which is required in C.

2. Step 2: Validate increment statement

   The increment counter += 1; is correct syntax and valid for int32_T type.

3. Final Answer:

   Missing semicolon after the first statement -> Option A

4. Quick Check:

   Every C statement ends with ; [OK]

Hint: Check for missing semicolons in C code lines [OK]

Common Mistakes:

• Ignoring missing semicolon errors
• Thinking increment syntax is wrong
• Confusing variable types unnecessarily

5. You want to optimize generated C code by removing unused signals. Which step should you take in Simulink before generating code?

hard

A. Use the Code Mappings editor to mark unused signals as 'Exclude from code'

B. Enable signal logging for all signals

C. Increase the sample time of all blocks

D. Disable the Simulink Coder entirely

Solution

1. Step 1: Understand code optimization options

   Simulink allows marking signals as unused in the Code Mappings editor to exclude them from generated code.

2. Step 2: Evaluate other options

   Enabling logging increases code size, increasing sample time changes model behavior, disabling coder stops code generation.

3. Final Answer:

   Use the Code Mappings editor to mark unused signals as 'Exclude from code' -> Option A

4. Quick Check:

   Exclude unused signals via Code Mappings [OK]

Hint: Mark unused signals to exclude in Code Mappings editor [OK]

Common Mistakes:

• Enabling logging increases code size
• Changing sample time affects model timing
• Disabling coder stops code generation