• 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. long simulation time problem

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 14710
  • 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

long simulation time problem

eyal
eyal over 16 years ago

hello all!

i need some advice  regarding the next scenario :

i need to verify a design that one of its task's is to scan 24k enteries memory in time interval of 1s and 10s, the design itself works at clock of 180 mhz.

the problem is that i can't simulate more than 10 ms and this itself takes about 3 hours.

i can't change the time scale of the simulation because the design is for fpga and contains the pll instansation.

i will be happy to hear from yours experience.

Eyal.

 

  • Cancel
Parents
  • adua
    adua over 16 years ago

     

    In the absence of specific details, the general performance suggestions are:

    - Look at the command line switches that can speed up the simulator. For example - -access, -linedebug switches should not be used for batch simulations.

    - Profile the simulation run (of about 10-15minutes). This can be done by simply adding "-profile" option to ncsim or irun. It generates ncprof.out and look at the areas where the actual time is being spend.

    If you can share more information about the environment (languages involved, any PLIs, RTL or gate level  etc), and the profiler output (ncprof.out), then we can help you with more performance suggestions specific to your case. Thanks.

    rgds,

    Amit.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • adua
    adua over 16 years ago

     

    In the absence of specific details, the general performance suggestions are:

    - Look at the command line switches that can speed up the simulator. For example - -access, -linedebug switches should not be used for batch simulations.

    - Profile the simulation run (of about 10-15minutes). This can be done by simply adding "-profile" option to ncsim or irun. It generates ncprof.out and look at the areas where the actual time is being spend.

    If you can share more information about the environment (languages involved, any PLIs, RTL or gate level  etc), and the profiler output (ncprof.out), then we can help you with more performance suggestions specific to your case. Thanks.

    rgds,

    Amit.

    • 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