Kista infrastructure for SystemC simulation and Time Analysis User Guidelines: Functional Validation back

Using KisTA:

    The KisTA library enables the creation of a validation facility by means of the call enable_functional_validation() which has to be called before the simulation start.
Once it has been done, then, the user can call set_functional_failure() from any user system or environment task during the simulation whenever a functional mismatch is detected.
The code detecting of the mismatch is left to the user.

A single call to  set_functional_failure() will set the functionality validator into a failure state,

This means that at the end of the simulation the KisTA functionality validation facility will report an error, indicating the issue.

Using KisTA-XML:

The KisTA-XML user can call  set_functional_failure() from within the task functional code (no matter system or environment), as long as such code is executed during the simulation phase.

Then from the configuration of the KisTA simulation, the user only need to set the functional_validaton tag:

<kista_configuration>
        ...
        <functional_validation value="true"/>
        ...
</kista_configuration>

If the functional validation option is not settled, then the default value is false and the functionality validator is not created by the KisTA-XML front-end.
Notice that this do not requires the user to remove calls to the set_functional_failure() function within the tasks code. They are simply ignored and the validations makes no effect.

If the validation is activated, then the error message is reported also in the XML output metrics file.
It is reported with non-fatal severity to, eventually enable tools like Multicube Explorer or MOST to continue an exploration and let later detect which solutions did not pass the functional validation.