MATLAB: Is the include file generated incorrectly if I have “_” and “-” characters in the model name in Stateflow 5.1.1 and higher (R13SP1+)

coderdashhyphenstateflowunderscore

My include file is generated incorrectly if I have "_" and "-" characters in my model name in Stateflow 5.1.1 and higher (R13SP1+).

Best Answer

There is a bug in Stateflow 5.1.1 and higher (R13SP1+) that causes the include file to be generated incorrectly if the model name contains "_" or "-" characters. This occurs because Stateflow treats "-" characters as separators.

To work around this issue, remove all "_" and "-" characters from the model name.

Related Solutions

MATLAB: Does the Stateflow model crash when I try to run it in Stateflow 4.1 or 4.2.1 (R12.1)

This bug has been fixed for Release 14 (R14). For previous releases, please read below for any possible workarounds:

This problem has been fixed in Stateflow 5.1.1 (R13SP1). (R13SP1). If you are using a previous version, read the following:

Stateflow, by default, relies on the Lcc C compiler to compile Stateflow generated C code on a Microsoft Windows-based system. There is a bug in the Lcc C compiler that is encountered when trying to compile very large C files.

This bug causes large Stateflow models to crash during simulation. The bug in Lcc is triggered by the number of relocations in the generated object file. While this number is not directly related to the number of states, models exhibiting this problem usually had more than 500 states and generated C files in excess of 1MB.

Use one of the following methods to work around this problem:

1. Configure Stateflow to use a different C compiler. Use

mex -setup

from the MATLAB command line to choose another C compiler.

2. Disable debugging in Stateflow. From the target menu select Coder Options and uncheck the debugging check box.

3. Split large charts into multiple smaller charts.

MATLAB: Is the Stateflow Coder license erroneously checked out when I simulate a model with Stateflow charts using Stateflow 5.1.1 (R13SP1)

This problem has been fixed in Stateflow 5.1.2 (R13SP1+). There are no known workarounds for Stateflow 5.1.1 (R13SP1).

Best Answer

Related Solutions

MATLAB: Does the Stateflow model crash when I try to run it in Stateflow 4.1 or 4.2.1 (R12.1)

MATLAB: Is the Stateflow Coder license erroneously checked out when I simulate a model with Stateflow charts using Stateflow 5.1.1 (R13SP1)

Related Question