To pass the ‘cfg’ struct as an input to the ‘experiment_demo_step()’ function, rather than using it as a global variable, you may replace the current 'Simulink.Parameter' object with a ‘Bus Inport’ in your Simulink model. The ‘inport’ should use the same bus type, ‘ModelConfigBus’, which defines the structure of the ‘cfg’ data. By making ‘cfg’ an explicit input signal instead of a parameter, Simulink will treat it as an input argument when generating code.
Next, in the Configuration Parameters, under ‘Code Generation’ > ‘Interface’, set the Code interface packaging option to ‘Reusable function’. This setting allows Simulink and Embedded Coder to generate a function interface where model inputs and outputs are passed as arguments, rather than accessed via global variables. Once configured this way, the generated ‘experiment_demo_step()’ function will accept ‘cfg’ as an input pointer.
As for the struct definition itself, Simulink automatically places the ‘ModelConfigBus’ type in the ‘experiment_demo_types.h’ header file. This is the correct and intended location for type definitions. If you need the struct to be accessible through ‘experiment_demo.h’, for integration purposes, ensure that ‘experiment_demo.h’ includes ‘experiment_demo_types.h’. It is not recommended to manually move the struct definition between files, as these are auto generated and subject to regeneration during code updates.
This method avoids the need for TLC customization, as Simulink's standard configuration options fully support passing structured data as function arguments when using bus signals and reusable function interfaces.
Please refer to the following documentation links for more information about the same: https://www.mathworks.com/help/ecoder/ug/control-data-interface-in-the-generated-code.html
I hope this answers your questions.
