Why do I receive an error when I try to accelerate my Simulink model using the Simulink Performace Tools 1.2 (R13)?

I am trying to run my Simulink model in Accelerator mode, but I receive the following errors during the build process:

 Error delta8900_v7_acc_data.c: 10295  syntax error; found `,' expecting `}' 

 Error delta8900_v7_acc_data.c: 10295  skipping `,' `0.0' `,' `0.0' 

 Error delta8900_v7_acc_data.c: 10302  syntax error; found `,' expecting `}' 

 Error delta8900_v7_acc_data.c: 10302  skipping `,' `0.072' `,' `0.12' `,'

 `0.14' `,' `0.169' ... up to `}' 

 Error delta8900_v7_acc_data.c: 10313  syntax error; found `,' expecting `}' 

 Error delta8900_v7_acc_data.c: 10313  skipping `,' `7.4556841591033335E+003'

 `,' `2.8563659906730001E+004' `,' `4.6607701730703331E+004' `,'

 `8.2508179499100006E+004' ... up to `}' 

 Error delta8900_v7_acc_data.c: 10599  syntax error; found `,' expecting `}' 

 Error delta8900_v7_acc_data.c: 10599  skipping `,' `0.0' `,' `0.0' 

 Error delta8900_v7_acc_data.c: 10606  syntax error; found `,' expecting `}' 

 Error delta8900_v7_acc_data.c: 10606  skipping `,' `0.027' `,' `0.056' `,'

 `0.095' `,' `0.133' ... up to `}' 

 Error delta8900_v7_acc_data.c: 10617  syntax error; found `,' expecting `}' 

 Error delta8900_v7_acc_data.c: 10617  skipping `,' `1.2166393934021334E+005'

 `,' `1.3353855442912667E+005' `,' `1.4406191478139666E+005' `,'

 `1.5060556846779000E+005' ... up to `}' 

 12 errors, 0 warnings

Answer 1

[MathWorks Support Team]

This problem has been fixed in Simulink Performance Tools 1.3 (R13.0.1). If you recently installed Simulink Performance Tools 1.3 (R13.0.1) and are experiencing this problem, try reinstalling it and/or make sure you have Simulink and Simulink Performance Tools R13.0.1.

Before reinstalling, try using the command,

rehash toolboxcache

to update the MATLAB toolbox cache file. Thus, if you updated to R13.0.1 without using this command after making the upgrade, Simulink might still be using R13 files.

If you are using a previous version, there are no known workarounds.