Setting Error Checking in the Debugging Window :: Debugging and Testing (Stateflow User's Guide)

Stateflow User's Guide

Setting Error Checking in the Debugging Window

The options in the Error checking options section of the Stateflow Debugging window insert generated code in the simulation target to provide breakpoints to catch different types of errors that might occur during simulation. Select any or all of the following error checking options:

State inconsistency -- Check for state inconsistency errors that are most commonly caused by the omission of a default transition to a substate in superstates with XOR decomposition. See Debugging State Inconsistencies for a complete description and example.
Transition Conflict -- Check whether there are two equally valid transition paths from the same source at any step in the simulation. See Debugging Conflicting Transitions for a complete description and example.
Data Range -- Check whether the minimum and maximum values you specified for a data in its properties dialog are exceeded. Also check whether fixed-point data overflows its base word size. See Debugging Data Range Violations for a complete description and example.
Detect Cycles -- Check whether a step or sequence of steps indefinitely repeats itself. See Debugging Cyclic Behavior for a complete description and example.

To include the supporting code designated for these debugging options in the simulation application, select the Enable debugging/animation check box in the Coder Options dialog for the simulation target. This is described in Configuring a Simulation Target for Stateflow.

Note You must rebuild the target for any changes to any of the settings referred to above to take effect.

Setting Breakpoints for Debugging Starting Simulation in the Debugging Window