Why are "test points" used in Code Generation ?

https://kr.mathworks.com/help/simulink/ug/working-with-test-points.html

above site, Documentation is saying that

"Test points are primarily intended for use when generating code from a model with Simulink Coder™. For more information about test points in the context of code generation, see Appearance of Test Points in the Generated Code (Simulink Coder)."

But I couldn't know how and why test points are used when we generate code, eventhough I follow the recommended URL and read that.

Therefore, I'd like to know the usage of test point in code generation step.

Answer 1

[Mark McBroom]

A test point results in a dedicated variable in the generated code that can then be monitored. Otherwise, Simulink Coder will try to use/reuse local variables to hold the values of intermediate signals in the Simulink model. The dedicated variable can the observed with a debugger or other similar types of tools to determine proper behavior of the generated code.

[MIN HOON]

Now, with your kind expression, I just now have sure to know that code generation can be seperated in two different concepts.

Is that right? Code generation for doing simulation in simulink is distingushied with for embedding to any ECU?

[Mark McBroom]

You are correct. The code that is generated for simulation is seperate from the code generated for embedding into an ECU.

[MIN HOON]

ok thanks!