Review the generated MEX function to verify that this code provides the same functionality as the original MATLAB code. It is a best practice to generate a MEX function before generating standalone code for your project.

Review the generated standalone code for run-time errors by setting the following options in the code configuration object:

cfg = coder.config('lib'); % or 'dll' or 'exe'
cfg.RuntimeChecks = 1;
codegen myFunction -config cfg

See RuntimeChecks in coder.CodeConfig.

Review the Extended Capabilities section in the reference pages for the functions you include in your code. The behavior of some MATLAB functions differ in the generated code causing the functions to produce different but equivalent output values. The code generator checks for differences in execution at run-time and reports them as potential differences. See Potential Differences Reporting.

Review calls to external C functions through coder.ceval. Verify that the data type, input, and output layout are correct. MATLAB uses a column-major layout by default.

Look for warnings produced during code generation.

To deploy the generated code, run the initialization function before calling the entry-point function. Call the terminate function after the entry-point function. See Use Generated Initialize and Terminate Functions.

If issues persist, try compiling the code by using the debug flag.

For MEX functions, add -g to the codegen command.

codegen myFunction -args {1,2} -g

For standalone code generation, create a coder.config object and modify it as shown.

cfg = coder.config('dll');  % or 'lib' or 'exe'
cfg.BuildConfiguration = 'Debug';
codegen myFunction -config cfg

For more information, see Debug Generated Code During SIL or PIL Execution (Embedded Coder).

Follow the recommended workflow to generate code while using the code generator. See Identify Entry-Point Functions and Check MATLAB Code.