• 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. Custom IC Design
  3. A stochastic model in Verilog A for Monte Carlo simulat...

Stats

  • Locked Locked
  • Replies 29
  • Subscribers 125
  • Views 33243
  • 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

A stochastic model in Verilog A for Monte Carlo simulation

UUinfini
UUinfini over 11 years ago

 Hello Guys,

I have a problem for Veriglog A in Cadence, I hope you can help me. In fact I need to elaborate a stochastic model by coding in Verilog A executed under Cadence. My aim is to offer a model with which the customers can do the Monte Carlo Analysis. But I used the functions like "$random", "$temperature" etc. to generate a seed for obtaining a parameter which changes each time of simulation. But finally it changes just according to the real time of simulation, but not according to different times of simulation. Do you have any experiences like this? Thank you for you response.

Best regards,

UU

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    The first problem is that your "source.scs" should not have the ahdl_include statement in it. Since you've created a cellView in Virtuoso for that cell containing the veriloga code, the spectre netlister will automatically add the "ahdl_include" for you. So you've defined it twice because of this.

    The second issue is that (for some reason) the instance of source in your schematic seems to be passing seedin - which it shouldn't be. Did you set the value on the instance? I suspect that maybe there was an issue with the veriloga parser in MMSIM10.1 which meant that it mistakenly identified this cds_inherited_param as a normal parameter - I don't have that version to hand though so I can't test that.

    Could you use Tools->CDF->Edit in the CIW, set it to "Base", and pick the lib and "source" cell that you've created, and then use the "CDF Dump" button to dump out the CDF for the "source" cell, and then post it here (maybe as an attachment via the Options tab)? Then I can see what's going on in your case.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    The first problem is that your "source.scs" should not have the ahdl_include statement in it. Since you've created a cellView in Virtuoso for that cell containing the veriloga code, the spectre netlister will automatically add the "ahdl_include" for you. So you've defined it twice because of this.

    The second issue is that (for some reason) the instance of source in your schematic seems to be passing seedin - which it shouldn't be. Did you set the value on the instance? I suspect that maybe there was an issue with the veriloga parser in MMSIM10.1 which meant that it mistakenly identified this cds_inherited_param as a normal parameter - I don't have that version to hand though so I can't test that.

    Could you use Tools->CDF->Edit in the CIW, set it to "Base", and pick the lib and "source" cell that you've created, and then use the "CDF Dump" button to dump out the CDF for the "source" cell, and then post it here (maybe as an attachment via the Options tab)? Then I can see what's going on in your case.

    Kind Regards,

    Andrew.

    • 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