There are at least two other ways.
- Once all the .m files are executed, you can use save() to save the base workspace to a .mat file. Next time, you use load() to load it. This might be faster if .m files have lots of "computing" involved. On the onter hand, .m files are text and easily visible. So the choice is case dependent.
- You can transfer your variables from .m file or base workspace to a Simulink Data Dictionary (SLDD, .sld) file and then "attach" it to the model. Search document for how to use it.
In any case, there is no direct way to save all the variables directly in the Simulink model file (.mdl or .slx). And it is not a good idea to do that.
A stretch way is to copy and past the .m text to the "PreLoadFcn" of the Simulink model so you could end up with one Simulink model file that includes both the model contents and base workspace variables.
Or if you are looking for convenience, then you can type all those .m file names in the "PreLoadFcn" of the model. All you need is to open the Simulink model and all the .m files will be automatically executed.
