Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15697
  • 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

Monte Carlo in ADE XL error

syen

Hi,

When I try running a nominal simulation (single run) on the simple resistor model (in "Cadence Verilog-A Language Reference", Version 6.1, Dec. 2006, pages 55-56) using ADEXL, I get this fatal error message:

   ERROR (SFE-2): "input.scs" 15: `I0': Attempt to override value of inherited parameter `monteresMINE' when instantiating a subcircuit.

where monteresMINE is the monteres in the Verilog-A reference mentioned above.

My goal is to run a MC simulation, hence the need for the statistical parameters.

I included the library for the statistical variations in the "Model libraries..." box under Setup. I ran the identical simulation using Virtuoso 5.1, and it ran just fine.

I'd appreciate any pointers you may have. Thanks!

  • There's a bug in the CDF generation when using (* cds_inherited_parameter *) in the Verilog-A model. What happens is that it adds a CDF parameter called monteres (or monteresMINE in your case), and then this gets netlisted on the instance.

    To workaround the problem, do Tools->CDF->Edit, pick "Base" CDF and edit the CDF of your cell (the one with the VerilogA model). Delete the monteresMINE parameter, and OK the forms.

    Now when you run the simulation, it should work. I've checked this myself.

    If you can send me a direct message with your email address, I can add a service request and CCR on your behalf (I couldn't find a CCR for this already) - I'd like to tie it to a real customer if possible.

    Regards,

    Andrew.

  • I filed CCR 922010 to get this fixed in a future release.

    Andrew.

  • Hi Andrew,

    Sorry for bringing this up for 5 years. But unfortunately I face the same bug and am not able to solve it using the methodology of deleting the monteres parameter followed by re-running the simulation.

    Any advice would be helpful.

  • OK, this was fixed in MMSIM 11.1 ISR17 in September 2012. Not sure what simulator version you're using as you didn't say (note, I didn't go back and check it's fixed - I'm assuming it was).

    Regards,

    Andrew.

  • Thanks Andrew. I updated my MMSIM version and the bug's fixed.

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.