Stats

  • Locked Locked
  • Replies 0
  • Subscribers 65
  • Views 12657
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Troubleshooting JasperGold error EFSV032 regarding conflicting inferred results for activatability check of a fault.

anuraagkn

I am using the JasperGold FSV app to identify safe faults in a Verilog design. I am applying SystemVerilog assumptions in the verification task to represent application-derived constraints.

Sometimes for a fault for which the app has already inferred an 'Activatability' result, the app will infer a conflicting result. For example: 

> ERROR (EFSV032): Conflicting inferred results in fault (41059):
>     The existing check result for "Activatability" is "Unactivatable", conflicts with the result: "Activated" inferred from fault (42042).

Sometimes the "conflicting" result will not even be conflicting. For example:

> ERROR (EFSV032): Conflicting inferred results in fault (41059):
>     The existing check result for "Activatability" is "Unactivatable", conflicts with the result: "Unactivatable" inferred from fault (42041).

Such faults are still classed as safe upon completion of the verification task. I could remove these faults from the safe faults list just to be safe. However, I'd like to get rid of the errors completely.

I am looking for help in troubleshooting this error.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.