Stateflow

Chapter 10
Debugging

Overview

Use the Stateflow Debugger to debug and animate the Stateflow diagrams in a particular machine.

It is a good idea to include debugging options in preliminary simulation target builds to ensure that the model is behaving as you expect, to evaluate code coverage, and to perform dynamic checking.

When you save the Stateflow diagram, all of the Debugger settings (including breakpoints) are saved.

Generally speaking, debugging options should be disabled for Real-Time Workshop and stand-alone targets. The Debugger does not interact with Real-Time Workshop or stand-alone targets and the overhead incurred from the added instrumented code is undesirable.

Typical Debugging Tasks

These are some typical debugging tasks you might want to accomplish:

• Animate Stateflow diagrams, set breakpoints, and debug runtime errors
• Evaluate coverage
• State inconsistencies
• Conflicting transitions
• Data range violations
• Cyclic behavior

Integrating Custom and Generated Code

Including Debugging in the Target Build