Invalid MEX-file

Hi,

I am doing a very simple exercise LED blinking exercise using C2000 texas instrument microcontroller. I'm using Mac M1 but I installed a virtual machine and installed a Matlab for windows to be able to use Embedded Coder Support Package for TI C2000.

While doung the exercise, I excountered the following error:

### Starting build procedure for: c28069_blink

### Generating code and artifacts to 'Model specific' folder structure

### Generating code into build folder: \\mac\home\Documents\MATLAB\Examples\R2022b\texasinstrumentsc2000\GettingStartedF28M3xConcertoProcessorsExample\c28069_blink_ert_rtw

The model c28069_blink is configured to simulate flush-to-zero (FTZ) behavior, but is using normal mode simulation. To observe FTZ behavior, simulate the model using an accelerated mode.

Component:Simulink | Category:Model

### Invoking Target Language Compiler on c28069_blink.rtw

### Using System Target File: \\mac\home\Desktop\MatlabWin\rtw\c\ert\ert.tlc

### Loading TLC function libraries

### Initial pass through model to cache user defined code

.

### Caching model source code

### Writing header file c28069_blink_types.h

### Writing header file c28069_blink.h

### Writing header file rtwtypes.h

### Writing source file c28069_blink.c

### Writing header file c28069_blink_private.h

### Writing source file c28069_blink_data.c

### Writing header file rtmodel.h

### Writing source file ert_main.c

### TLC code generation complete (took 6.018s).

### Build procedure for c28069_blink aborted due to an error.

Build Summary

Top model targets built:

Model Action Rebuild Reason

========================================================================

c28069_blink Failed Code generation information file does not exist.

0 of 1 models built (0 models already up to date)

Build duration: 0h 0m 14.833s

Invalid MEX-file '\\mac\home\Desktop\MatlabWin\toolbox\stateflow\stateflow\sf.mexw64': The specified module could not be found.

Answer 1

[Muskan]

Hi,

As per my understanding the issue is because after Simulink generates code and compiles executable for the first time, it makes temporary files for faster compilation the second time. In this case it seems like the old files that were generated clashed with the code generation process. Try deleting the generated files and run the process again. This should help resolve the issue.