Simulink Verification and Validation Bug Fixes
This document describes major bug fixes in this release.
Click on a problem area listed below to read how it has been fixed.
Coverage tool asserted when condition coverage not enabled for model using Fcn block
Extended Switch Block Semantics No Longer Causes a Segmentation Violation
Incorrect coverage for Multiport Switches with 0 Based Indexing
Model Coverage Tool Results for If Blocks
Problems reporting MCDC coverage for single input logic blocks
Switch block coverage and data types
Coverage tool asserted when condition coverage not enabled for model using Fcn block
When an Fcn block was included in a Simulink 5.0 (Release 13) model and
that model
had only decision coverage enabled (condition coverage is not enabled),
the coverage tool asserted when condition coverage was invoked for
internal use. This internal logic has been corrected.
Extended Switch Block Semantics No Longer Causes a Segmentation Violation
Specifying model coverage for a Simulink 5.0 (Release 13) model that used
a Switch block with the block parameter Criteria for passing first input
set to u2 ~= 0 received a segmentation violation. This
problem was due to extended Switch block semantics that were not
incorporated into the coverage tool. This has been fixed.
Incorrect coverage for Multiport Switches with 0 Based Indexing
The R13 release, the coverage tool incorrectly reported coverage for
the multiport switch when 0 based indexing was selected. This release
correctly implements coverage recording.
Model Coverage Tool Results for If Blocks
In previous releases, the Model Coverage tool did not report correct
coverage results for the If block in some cases. In particular, the
results were correct only if the block's condition expression was
input not equal to 0, i.e., u1 != 0, u2 != 0, etc. This release fixes
this problem.
Problems reporting MCDC coverage for single input logic blocks
In previous versions of the coverage tool an error was produced whenever a
logic block was configured with a single vector input and MCDC coverage
was enabled. This release fixes the problem and correctly reports coverage
Switch block coverage and data types
In earlier versions, the coverage reported for a switch block was not
accurate if the switch condition was "u2>thresh" or "u2>=thresh" and the
input signal was a data type other than double. In this release the
switch block coverage is accurate.