• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Troubleshooting IFV

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 65
  • Views 16777
  • 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 IFV

JASK
JASK over 16 years ago

 Hi,

    I am new to IFV. I was trying to run the tutorial example (given in ifvtut1 in the docs), but I am facing some errors even at that point.

cd examples/ifv

ifv -f fifo_cntl.f +gui

IFV seems to compile the .vhdl file properly, and is about to launch the GUI window, when an error appears. 

formalverifier: *E,STRPIN:Could not initialize SimVision connection: SimVision process terminated before a connection was established. 

 

When I try without the +gui option too, it gives me an error.

formalverifier: *E,URSYST: Unrecognized system task (did not match built-in or user-defined names) $get_simulationscratch.

 

Has anyone come across this before? I would really appreciate any help in fixing this.

 

-Jayanand

PS: It's a university tool. Could it be an installation bug?

  • Cancel
Parents
  • tpylant
    tpylant over 16 years ago
    Message
     
    It would be helpful if you include what version you are using.

    Although it has been fixed in the latest releases, there was a problem if you got your IFV and IUS installation paths mixed. This would happen if you have your IUS path first. What happens is that you call IFV (that doesn’t exist in the IUS release) and so it gets the IFV executable from the IFV release directory. But then you call SimVision that does exist in the IUS release and so it gets a different version from the IUS release directory.

    Tim
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • tpylant
    tpylant over 16 years ago
    Message
     
    It would be helpful if you include what version you are using.

    Although it has been fixed in the latest releases, there was a problem if you got your IFV and IUS installation paths mixed. This would happen if you have your IUS path first. What happens is that you call IFV (that doesn’t exist in the IUS release) and so it gets the IFV executable from the IFV release directory. But then you call SimVision that does exist in the IUS release and so it gets a different version from the IUS release directory.

    Tim
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information