Stats

  • Locked Locked
  • Replies 8
  • Subscribers 64
  • Views 15460
  • 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

IFV Regresssion

archive

Hello ,

   I am using IFV to check the hook up in a large SOC .
   We have around 2000 assertions .  That means the total 
   assertion run takes so much time ( I am using a single IFV gui ) .

    Is there any workaround ? like simulations can we have batch mode 
    jobs for these assertion runs . We are using a farm of servers .  

Regards

Jentil Jose


Originally posted in cdnusers.org by jent
Parents

  • Good point!
    I would imagine that you could use the +nclibdirname+

    option to IFV, and run each session in a new directory.
    For example:

    Project dir:
    /projects/mysoc/ifv

    Run 1st session in:
    /projects/mysoc/ifv/run1
    Using command:
    ifv -f ../mysoc.ifv +nclibdirname+/projects/mysoc/ifv/INCA_libs

    Then each subsequent session in run2, run3... using the exact same +nclibdirname option.
    You may also need a +cdslib option to specify a common cds.lib file if you're using VHDL.

    I haven't tried this with IFV, but it works fine for IUS.

    If it works, can you let us know on the forum?


    Originally posted in cdnusers.org by stephenh
Reply

  • Good point!
    I would imagine that you could use the +nclibdirname+

    option to IFV, and run each session in a new directory.
    For example:

    Project dir:
    /projects/mysoc/ifv

    Run 1st session in:
    /projects/mysoc/ifv/run1
    Using command:
    ifv -f ../mysoc.ifv +nclibdirname+/projects/mysoc/ifv/INCA_libs

    Then each subsequent session in run2, run3... using the exact same +nclibdirname option.
    You may also need a +cdslib option to specify a common cds.lib file if you're using VHDL.

    I haven't tried this with IFV, but it works fine for IUS.

    If it works, can you let us know on the forum?


    Originally posted in cdnusers.org by stephenh
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.